SIST ETS 300 497-5 E1:2003

SLOVENSKI STANDARD
01-december-2003
5DGLMVNDRSUHPDLQVLVWHPL5(6±'LJLWDOQHL]EROMãDQHEUH]YUYLþQH
WHOHNRPXQLNDFLMH'(&7±6NXSQLYPHVQLN&,±.QMLåQLFDSUHVNXãDOQLKSULPHURY
7&/±GHO$EVWUDNWQLSUHVNXãDOQLQL]$76±3ODVWNUPLOMHQMDSRGDWNRYQLK
SRYH]DY'/&
Radio Equipment and Systems (RES); Digital Enhanced Cordless Telecommunications
(DECT); Common Interface (CI) Test Case Library (TCL);Part 5: Abstract Test Suite
(ATS) - Data Link Control (DLC) layer
Ta slovenski standard je istoveten z: ETS 300 497-5 Edition 1
ICS:
33.060.20 Sprejemna in oddajna Receiving and transmitting
oprema equipment
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 497-5
TELECOMMUNICATION August 1996
STANDARD
Source: ETSI TC-RES Reference: DE/RES-03026-5
ICS: 33.020, 33.060.50
Key words: Abstract Test Suites, DECT, DLC
Radio Equipment and Systems (RES);
Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI) Test Case Library (TCL);
Part 5: Abstract Test Suite (ATS) - Data Link Control (DLC) layer
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 92 94 42 00 - Fax: +33 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 1996. All rights reserved.

Page 2
ETS 300 497-5: August 1996
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 3
ETS 300 497-5: August 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .10
3.1 DECT definitions.10
3.2 DECT abbreviations.11
3.3 ISO definitions.12
3.4 ISO abbreviations .12
4 Abstract Test Method (ATM).13
5 Untestable Test Purposes (TPs).14
6 ATS Conventions .14
6.1 Naming conventions .14
6.1.1 Declarations part .14
6.1.1.1 Test suite type and structured type definitions .14
6.1.1.2 Test suite operations definitions .14
6.1.1.3 Test suite parameter declarations .15
6.1.1.4 Test case selection expression definitions .15
6.1.1.5 Test suite constant declarations.15
6.1.1.6 Test suite variable declarations .15
6.1.1.7 Test case variable declarations .15
6.1.1.8 PCO declarations.15
6.1.1.9 Timer declarations.16
6.1.1.10 ASP type definitions.16
6.1.1.11 PDU type definitions .16
6.1.1.12 Alias definitions.16
6.1.2 Constraints part.17
6.1.3 Dynamic part .17
6.1.3.1 Test Case identifier.17
6.1.3.2 Test step identifier .17
6.1.3.3 Default identifier.18
6.1.3.4 General aspects .18
6.1.3.5 ATS abbreviations .18
6.2 Implementation conventions .18
6.2.1 Declaration part .18
6.2.2 Constraint part.19
6.2.3 Dynamic part .19
6.2.4 Documentation .20
7 Test case and test purpose mapping.20
Annex A (normative): ATS for DECT DLC .21
A.1 The machine processable ATS (TTCN.MP) .21
A.2 The graphical ATS (TTCN.GR).21
Annex B (normative): Partial PIXIT proforma for DECT DLC .169
B.1 Identification summary .169

Page 4
ETS 300 497-5: August 1996
B.2 ATS summary. 169
B.3 Test laboratory. 169
B.4 Client identification. 169
B.5 SUT. 169
B.6 Protocol layer information. 170
B.6.1 Protocol identification . 170
B.6.2 IUT information. 170
B.6.2.1 General configuration . 170
B.6.2.2 Parameter values. 170
B.6.2.3 Timer values . 170
B.6.2.4 Network parameter values. 171
B.6.3 Procedural Information. 171
B.6.3.1 Class U procedural information . 171
B.6.3.2 Class A procedural information . 172
B.6.3.3 Paging procedural information. 173
B.6.3.4 Class 0 procedural information. 174
B.6.3.5 Class 1 procedural information. 174
Annex C (normative): Protocol Conformance Test Report (PCTR) Proforma for DECT DLC . 175
C.1 Identification summary. 175
C.1.1 Protocol conformance test report. 175
C.1.2 IUT identification. 175
C.1.3 Testing environment. 175
C.1.4 Limits and reservation . 176
C.1.5 Comments. 176
C.2 IUT Conformance status. 176
C.3 Static conformance summary. 176
C.4 Dynamic conformance summary. 176
C.5 Static conformance review report . 177
C.6 Test campaign report. 177
C.7 Observations. 178
Annex D (informative): Bibliography . 179
History. 180

Page 5
ETS 300 497-5: August 1996
Foreword
This European Telecommunication Standard (ETS) has been produced by the Radio Equipment and
Systems (RES) Technical Committee of the European Telecommunications Standards Institute (ETSI).
The DECT Test Specification multipart ETS comprises nine parts, as follows:
Part 1: "Part 1: Test Suite Structure (TSS) and Test Purposes (TP) for Medium Access Control
(MAC) layer".
Part 2: "Part 2: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Portable radio
Termination (PT)".
Part 3: "Part 3: Abstract Test Suite (ATS) for Medium Access Control (MAC) layer - Fixed radio
Termination (FT)".
Part 4: "Part 4: Test Suite Structure (TSS) and Test Purposes (TP) - Data Link Control (DLC) layer".
Part 5: "Part 5: Abstract Test Suite (ATS) - Data Link Control (DLC) layer".
Part 6: "Part 6: Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Portable
radio Termination (PT)".
Part 7: "Part 7: Abstract Test Suite (ATS) for Network (NWK) layer - Portable radio Termination
(PT)".
Part 8: "Part 8: Test Suite Structure (TSS) and Test Purposes (TP) - Network (NWK) layer - Fixed
radio Termination (FT)".
Part 9: "Part 9: Abstract Test Suite (ATS) for Network (NWK) layer - Fixed radio Termination (FT)".
Transposition dates
Date of adoption of this ETS: 16 August 1996
Date of latest announcement of this ETS (doa): 30 November 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 May 1997
Date of withdrawal of any conflicting National Standard (dow): 31 May 1997

Page 6
ETS 300 497-5: August 1996
Blank page
Page 7
ETS 300 497-5: August 1996
1 Scope
This European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) to test the
DECT DLC 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.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 [21], ISO/IEC 9646-2 [22],
ISO/IEC 9646-3 [23] and ISO/IEC 9646-5 [25]) as well as the ETSI rules for conformance testing
(ETS 300 406 [29] and ETR 141 [30]) are used as basis for the test methodology.
Test specifications for the Physical Layer (PHL), Medium Access Control Layer (MAC), and Network Layer
(NWK) are provided in other the DECT standards.
Annex A provides the Tree and Tabular Combined Notation (TTCN) part of this ATS.
Annex B provides the Partial Protocol Implementation eXtra Information for Testing (PIXIT) Proforma of
this ATS.
Annex C 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 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 1: Overview".
[2] ETS 300 175-2 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 2: Physical
layer".
[3] ETS 300 175-3 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 3: Medium
access control layer".
[4] ETS 300 175-4 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 4: Data link
control layer".
[5] ETS 300 175-5 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 5: Network
layer".
[6] ETS 300 175-6 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 6: Identities
and addressing".
[7] ETS 300 175-7 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 7: Security
features".
[8] ETS 300 175-8 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 8: Speech
coding and transmission".
Page 8
ETS 300 497-5: August 1996
[9] ETS 300 175-9 (1992): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Common interface; Part 9: Public
access profile".
[10] ETS 300 444: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Generic Access Profile (GAP)".
[11] ETS 300 370: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications/Global System for Mobile communications
(DECT/GSM) inter-working profile; Access and mapping (Protocol/procedure
description for 3,1 kHz speech service)".
[12] ETS 300 434: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT) and Integrated Services Digital Network
(ISDN) inter-working for end system configuration".
[13] ETS 300 331: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); DECT Authentication Module (DAM)".
[14] CCITT Recommendation G.726 (1991): "40, 32, 24, 16 kbit/s adaptive
differential pulse code modulation (ADPCM)".
[15.20] Reserved values.
[21] 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)).
[22] 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)).
[23] 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)).
[24] 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)).
[25] 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)).
[26] ISO/IEC 9646-6 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 6:
Protocol profile test specification".
[27] ISO/IEC 9646-7 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation conformance statement".
[28] ISO 7498: "Information Processing Systems - Open Systems Interconnection -
Basic Reference model".
[29] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".

Page 9
ETS 300 497-5: August 1996
[30] 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)".
[31.40] Reserved values.
[41] I-ETS 300 176: "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Approval test specification".
[42] TBR 6: "Radio Equipment and Systems (RES); Digital European Cordless
Telecommunications (DECT); General terminal attachment requirements".
[43] TBR 10: "Radio Equipment and Systems (RES); Digital European Cordless
Telecommunications (DECT); General terminal attachment requirements:
Telephony applications".
[44] TBR 11 (1992): "Radio Equipment and Systems (RES); Attachment
requirements for terminal equipment for Digital European Cordless
Telecommunications (DECT) Public Access Profile (PAP) applications".
[45] ETS 300 323 (1994): "Radio Equipment and Systems (RES); Digital European
Cordless Telecommunications (DECT); Public Access Profile (PAP) test
specification".
[46] ETS 300 476: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI); Protocol
Implementation Conformance Statement (PICS) proforma".
[47] ETS 300 497: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Common Interface (CI) Test Case
Library (TCL)".
[48] ETS 300 474: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Generic Access Profile (GAP); Profile
requirement list and profile specific Implementation Conformance Statement
(ICS) proforma".
[49] ETS 300 494: "Radio Equipment and Systems (RES); Digital Enhanced
Cordless Telecommunications (DECT); Generic Access Profile (GAP); Profile
Test Specification (PTS)".
[50] TBR 22: "Radio Equipment and Systems (RES); Attachment requirements for
terminal equipment for Digital Enhanced Cordless Telecommunications (DECT)
Generic Access Profile (GAP) applications".

Page 10
ETS 300 497-5: August 1996
3 Definitions and abbreviations
Refer to ETS 300 175-1 [1] for the main DECT listing of definitions, symbols and abbreviations. For the
purposes of this ETS, the following definitions apply:
3.1 DECT definitions
C-plane: The control plane of the DECT protocol stacks, which contains all of the internal DECT protocol
control, but may also include some external user information.
NOTE 1: The C-plane stack always contains protocol entities up to and including the network
layer.
DLC data link (DLC link): An association between two DLC layer entities. This can either be one
C-plane association or one U-plane association.
NOTE 2: This is not the same as a MAC connection.
DLC Frame: The format used to structure all messages that are exchanged between DLC layer peer
entities.
NOTE 3: Different DLC frames are used in the C-plane and the U-plane, and there is more than
one format of DLC frame in each plane.
Fixed radio Termination (FT): A logical group of functions that contains all of the DECT processes and
procedures on the fixed side of the DECT air interface.
NOTE 4: A FT only includes elements that are defined in the ETS 300 175 [1] to [9]. This
includes radio transmission elements (layer 1) together with a selection of layer 2 and
layer 3 elements.
flow control: The mechanism that is used to regulate the flow of data between two peer entities.
fragment: One of the service data units that is produced by the process of fragmentation.
NOTE 5: This is not the same as a segment.
fragmentation: The process of dividing a protocol data unit into more than one service data unit for
delivery to a lower layer. The reverse process is recombination.
NOTE 6: This is not the same as segmentation.
Lower Layer Management Entity (LLME): A management entity that spans a number of lower layers,
and is used to describe all control activities which do not follow the rules of layering.
NOTE 7: The DECT LLME spans the network layer, the DLC layer, the MAC layer and the
physical layer.
Portable radio Termination (PT): A logical group of functions that contains all of the DECT processes
and procedures on the portable side of the DECT air interface.
NOTE 8: A PT only includes elements that are defined in ETS 300 175 [1] to [9]. This includes
radio transmission elements (layer 1) together with a selection of layer 2 and layer 3
elements.
Radio Fixed Part (RFP): One physical sub-group of a fixed part that contains all the radio end points (one
or more) that are connected to a single system of antennas.
segment: One of the pieces of data that is produced by the process of segmentation.
NOTE 9: In general, one segment only represents a portion of a complete message.

Page 11
ETS 300 497-5: August 1996
segmentation: The process of partitioning one service data unit from a higher layer into more than one
protocol data unit. The reverse process is assembly.
sequencing (sequence numbering): The process of adding a sequence number to a set of data packets
so that the packets can be reassembled in the correct order, regardless of the order in which they are
received. See also segmentation.
U-plane: The user plane of the DECT protocol stacks. This plane contains most of the end-to-end
(external) user information and user control.
NOTE 10: The U-plane protocols do not include any internal DECT protocol control, and it may be
null at the network layer and at the DLC layers for some services.
3.2 DECT abbreviations
For the purposes of this ETS, the following DECT abbreviations apply:
ALI Assigned Link Identifier. A LAPC operational state
ARQ Automatic Repeat Request
ASM Assigned Link Identifier with Synchronous Mode
BRAT Basic Rate Adaptation service
C-Plane Control Plane. See definitions
C/L ConnectionLess mode. See definitions
C/O Connection Oriented mode. See definitions
DECT Digital Enhanced Cordless Telecommunications
DLC Data Link Control
FB Frame Buffer (unprotected)
N
FB Frame Buffer (protected)
P
FMID Fixed part MAC Identity. (MAC layer)
FP Fixed Part. See definitions
FREL Frame RELay service
FSWI Frame SWItching service
FT Fixed radio Termination. See definitions
LAPC a DLC layer C-plane protocol entity
Lb a DLC layer C-plane protocol entity
Lc a DLC layer C-plane protocol entity
LLME Lower Layer Management Entity (see definitions)
MAC Medium Access Control
NWK Network
PDU Protocol Data Unit
PMID Portable Part MAC Identity (MAC layer)
PP Portable Part. See definitions
PT Portable radio Termination. See definitions
RFP Radio Fixed Part (see definitions)
SAP Service Access Point
SAPI Service Access Point Identifier
SDU Service Data Unit
SEL Selective
SRAT Secondary Rate Adaptation service
TDMA Time Division Multiple Access
TRUP Transparent Unprotected service
ULI Unassigned Link Identifier
U-Plane User Plane (see definitions)

Page 12
ETS 300 497-5: August 1996
3.3 ISO definitions
For the purposes of this ETS, the following ISO definitions apply:
Implementation Under Test (IUT): See ISO/IEC 9646-1 [21];
System Under Test (SUT): See ISO/IEC 9646-1 [21];
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [21];
Point of Control and Observation (PCO): See ISO/IEC 9646-1 [21];
Protocol Conformance Test Report (PCTR): See ISO/IEC 9646-5 [25];
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [21];
Protocol Implementation eXtra Information for Testing (PIXIT): See ISO/IEC 9646-1 [21];
PCTR proforma: See ISO/IEC 9646-5 [25];
PICS proforma: See ISO/IEC 9646-1 [21];
PIXIT proforma: See ISO/IEC 9646-1 [21];
Lower Tester (LT): See ISO/IEC 9646-1 [21];
Upper Tester (UT): See ISO/IEC 9646-1 [21];
Network layer (NWK): See ISO 7498 [28];
Physical Layer (PHL): See ISO 7498 [28].
3.4 ISO abbreviations
For the purposes of this ETS, the following ISO abbreviations apply:
ASP Abstract Service Primitive
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA Capability tests
ETS European Telecommunication Standard
ISO International Organisation for Standardisation
IUT Implementation Under Test
LT Lower Tester
NWK Network Layer
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statements
PIXIT Protocol Implementation eXtra Information for Testing
SUT System Under Test
TC Test Case
TP Test Purpose
TSS Test Suite Structure
UT Upper Tester
Page 13
ETS 300 497-5: August 1996
4 Abstract Test Method (ATM)
This clause describes the ATM used for testing the DECT DLC protocol. It is the embedded variant of
Remote Single (RSE) layer test method. The RSE test method has been selected, because:
- this test method implies no specific requirements from the IUT;
- the Upper Service Access Point (USAP) of the IUT cannot be directly observed;
- the variety of the possible DECT implementations is a serious technical obstacle for the adoption of
a different ATM;
- this test method places the minimum limitations in the realisation of conformance testing.
The embedded variant of the remote test method provides sufficient control of the IUT DLC behaviour,
through NWK layer messages conveyed by DLC frames.
SUT
Test System
Upper
LT Layers
NW K-PDUs
For im plicit test
coordination
in ASPs w ith DECT
M CEI and if
NW K
necessary
Service Type
DLC-PDUs
!MAC ASPs
Fragmentation
?MAC ASPs
Recombination
DECT
Subset of Lc entity
IUT
MSAP -PCO
and FBx entities DLC
MAC-CO-DATA
primitives
DECT MAC layer
DECT MAC layer
DECT PHL and radio communication
Figure 1: RS test Method embedded variant
LT A lower tester (LT) is located in a remote DECT test system. It controls and
observes the behaviour of the IUT.
MSAP A unique MAC SAP is defined at the DECT interface and used to exchange
service data of the DLC protocol. To avoid the complexity of data fragmentation
and recombination testing, the SAP is defined below this functions of the DLC
layer.
PCO The PCO for DLC layer testing is located on the MSAP. All test events at the
PCO are specified in terms of MAC ASPs and DLC layer PDUs.
Notional UT No explicit upper tester (UT) exists in the system under test. Nevertheless,
some network messages are sent to the SUT for the need of the co-ordination
procedures. The network layer of the SUT is used as a notional UT as defined in
ISO 9646.
The MSAP primitives are defined according to ETS 300 175-3 [3] clause 8 and associated subclauses.

Page 14
ETS 300 497-5: August 1996
5 Untestable Test Purposes (TPs)
Due to the ATMs chosen for this ATS or other restrictions, the test purposes in table 1 have been
identified as being in the untestable category, and therefore have not been derived into final test case:
Table 1: Untestable TPs
Test purpose Reason
No procedure can be defined to determine if, after receiving the first UI frame, the
IUT considers the class U link as established. It is an internal state of the DLC layer
TPUV_000
of the IUT.
No procedure can be defined to determine if, after receiving an upward release, the
IUT considers the class U link as released. It is an internal state of the DLC layer of
TPUV_001
the IUT.
Test for connection handover needs some clarification and agreement from the
TPAV_007
respective RES03 subgroup before that are written.
Test for connection handover needs some clarification and agreement from the
TPAV_008
respective RES03 subgroup before that are written.
Test for connection handover needs some clarification and agreement from the
TPAV_009
respective RES03 subgroup before that are written.
Test for connection handover needs some clarification and agreement from the
TPAV_010
respective RES03 subgroup before that are written.
Prioritised queuing of broadcast message between normal and expedited data is not
testable. It is very difficult to define a procedure in the IUT to force it, to transmit
normal and expedited data in a sufficient short time. It is, also, very difficult for the
TPLC_002
tester to transmit normal and expedited data in sufficient short time and to define a
procedure to verify the correct order of the reception in the IUT.
6 ATS Conventions
This clause describes the conventions applied to define the ATS and gives the naming conventions
chosen for the different elements of the ATS.
The ATS conventions are intended to give a better understanding of the ATS but they describe also the
conventions made for the development of the ATS, thus for any later maintenance purposes or further
development of the ATS the conventions described in this clause shall be considered.
The ATS conventions contain two subclauses, 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.
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 Test suite type and structured type definitions
The test suite type and test suite structured type identifiers describe the information elements, and are
written in uppercase:
EXAMPLE: PROTOCOL_DISCRIMINATOR simple type.
FILLSTRING structured type
6.1.1.2 Test suite operations definitions
The test suite operation identifiers are composed of string in lowercase letters starting by the uppercase
string "TSO_".
EXAMPLE: TSO_compute _checksum.

Page 15
ETS 300 497-5: August 1996
6.1.1.3 Test suite parameter declarations
The test suite parameter identifiers are composed of string in lowercase letters starting by the uppercase
string "TSP_".
EXAMPLE: TSP_window_size.
If the test suite parameter references a PICS item, the letter "C" is added to the standard prefix.
EXAMPLE: TSPC_pics_item_s23.
If the test suite parameter references a PIXIT item, the letter "X" is added to the standard prefix.
EXAMPLE: TSPX_pixit_item_2.
Complete names as defined in the specifications are used.
6.1.1.4 Test case selection expression definitions
The naming conventions for the test case selection expression definitions use free text starting with an
uppercase letter. The name of the expression shall explain clearly the selection rule. The test case
selection expressions are logical combinations of the test suite parameters definitions.
Certain test cases are selected only when the IUT is a FT part or a PT part. Therefore, to cover all test
cases applicable to the implementation, it is necessary to change the relevant test suite parameter for
running the desired test cases.
6.1.1.5 Test suite constant declarations
The test suite constant identifiers are composed of string in lowercase letters starting by the uppercase
string "TSC_".
EXAMPLE: TSC_retry.
Complete names as defined in the specifications are used.
6.1.1.6 Test suite variable declarations
The test suite variable identifiers are composed of string in lowercase letters starting by the uppercase
string "TSV_".
EXAMPLE: TSV_count.
Exception: If the test suite variable represents a system parameter or value, the name defined in the
specifications is used.
EXAMPLE: VR,VS.
6.1.1.7 Test case variable declarations
The test case variable identifiers are composed of string in lowercase letters starting by the uppercase
string "TCV_".
EXAMPLE: TCV_cr_value.
6.1.1.8 PCO declarations
The point of control and observation identifiers are composed of two or four capital letters, beginning with
"L", as there are only LTs.
EXAMPLE: LMAC represents a PCO on MAC interface as LT in the test equipment.
LDLC represents a PCO on DLC interface as LT in the test equipment.

Page 16
ETS 300 497-5: August 1996
6.1.1.9 Timer declarations
Two kinds of timers can be distinguished:
1) standardised:
Those defined in the standard, e.g. DL_04, use exactly the same name as in the standard,
beginning with a capital "T".
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: TDL_04_max, TDL_04_min, and TDL_04.
2) not standardised:
Those not defined in the 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.10 ASP type definitions
The identifier of an ASP uses exactly the nearest name as the name defined in the specifications. It is
written in uppercases, finishing by an underscore character ("_"), and three capital letters indicating
whether it is a request, an indication, a response or a confirmation primitive.
EXAMPLE: DL_RELEASE_REQ for an ASP containing a layer 3 release request passed to
layer 2;
MAC_DATA_REQ for an ASP containing a layer 2b PDU passed to layer 2a.
6.1.1.11 PDU type definitions
The identifier of a PDU is given in a string in uppercase letters, which represents the layer message.
EXAMPLE 1: RR for the Receive Ready layer 2 message;
DISCONNECT for the DISCONNECT layer 3 message.
Where the message is a composite word, an underscore character ("_") appears in the string.
EXAMPLE 2: RELEASE_COMPLETE is the RELEASE COMPLETE layer 3 message.
6.1.1.12 Alias definitions
These are used to make the sending and receiving of PDUs within ASPs more understandable when
writing the dynamic part of the test suite. This is done by giving the ASP an alias. The alias name indicates
the PDU carried by the ASP and whether it is sent or received by the tester.
No alias are used in the test suite.

Page 17
ETS 300 497-5: August 1996
6.1.2 Constraints part
This subclause describes the naming conventions chosen for the elements of the ATS constraints part.
Constraint identifiers commence with uppercase. The remaining part of the Id name is written in
lowercase.
Identifier names of elements concerning the same subject have equivalent names in the declaration and
the constraint part:
- Declaration Part: CC_SETUP;
- Constraint Part: Cc_setup.
The name of the modified constraint describes the particularity of the modified constraint:
EXAMPLE: Cc_setup_mand_only (modified Cc_setup with only the mandatory Information
Elements).
If formal parameter lists are used, the variable names are written in lowercase. The variable name is the
same as the name of the element it is representing.
6.1.3 Dynamic part
This subclause describes the naming conventions chosen for the elements of the ATS dynamic part.
6.1.3.1 Test Case identifier
The identifier of a test case is built according to table 2:
Table 2: TC naming convention
Identifier: TC--x-
= functional module U Control plane Class U services
A Control plane Class A services
B Control plane Class B services
L Control plane Broadcast services
0 User plane transmission Class 0
1 User plane transmission Class 1
2 User plane transmission Class 2
3 User plane transmission Class 3
x = Type of testing CA CA, Capability tests
BV BV, Valid Behaviour tests
BO BO, Inopportune Behaviour tests
BI BI, Invalid Behaviour tests
= sequential number (000-999) test case Number
6.1.3.2 Test step identifier
The test step identifier is built with a string of lowercase letters leaded by a string of capital letter and
joined by an underscore character. The first string indicates the main function of the test step; e.g. PR for
preamble, PO for postamble, LTS for local tree name and STP for general step. The second string
indicates the meaning of the step.
EXAMPLES: PR_name;
PO_name;
LTS_name;
STP_name.
Page 18
ETS 300 497-5: August 1996
6.1.3.3 Default identifier
The Default identifiers begin with the prefix "DF_", followed by a string in lowercase letters.
6.1.3.4 General aspects
All verdict assignments are labelled. To allow an exact identification in which table the verdict was
assigned, the following name convention is applied:
TB test Body;
DF Default;
EH Error handling test steps;
PO POstamble;
PR PReamble;
TS test step.
6.1.3.5 ATS abbreviations
These abbreviations are used to shorten identifier names:
addr address
ack acknowledgement
cau cause
cc call control
chn channel
est establish
ind indication
mety message type
mod modified
par parameter
pd protocol discriminator
req request
rsp response
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 specifications. 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. ASPs) is used to reference to the
protocol specification.
The detailed comments are used to describe any particularity of the table.
In the ASP and PDU declarations, the comments column is used to identify if an element is mandatory or
optional:
- M: mandatory;
- O: optional.
In the ASP and PDU declarations the comments column is further used to give information about the
element value, in particular if the element contains a fixed spare value.

Page 19
ETS 300 497-5: August 1996
6.2.2 Constraint part
The ASPs and PDUs are defined in a way that all relevant element are parametrized. 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 DECT profile test specifications.
The comment line of a constraint contains always the reference to the used specifications.
The detailed comments sector is used to describe any particularity of the table.
6.2.3 Dynamic part
Some TCs need a particular initialisation of the IUT environment conditions to run the actual test, e.g. for
testing re-provisioning procedures. Such message sequence can be quite complicated and long. In cases
where a local test step (LTS) facilitates the TC structure, the preamble and the condition setting are
described in a LTS called LTS_pre_step. All LTS_pre_steps are described in the detailed comment part of
the TTCN table.
Some TCs need after the actual test a particular re-initialization of the IUT, e.g. after re-provisioning. Such
message sequence can be quite complicated and long. In cases where a local test step (LTS) facilitates
the TC structure, the postamble and the re-initialization are described in a LTS called LTS_post_step. All
LTS_post_steps are described in the detailed comment part of the TTCN table.
All events which are defined as a conformance requirements by the TP, cause a preliminary verdict PASS
if the requirement is met.
All invalid events are handled in the default tree. Only FAIL verdicts can be 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.
Test steps do not contain a default. That allows to apply them with no restrictions regarding the error
handling.
All verdict assignments are labelled. According to ISO 9646-3 [23], annex E.2, labels should be written to
the conformance log. This allows to identify were the test failed. To allow an exact identification in which
table the verdict was assigned, the naming convention as described in subclause 6.1.3.4 is applied.
The labels of the same type are numbered sequentially if they are in the same TC, test step or default.
TPs which are listed in the untestable TP list, or which reference to an other TP, e.g. BV TPs which were
already defined as CA TPs, are not considered in the ATS, thus these TC identifiers are missing in the
ATS and the numbering of the TCs is not always continues.

Page 20
ETS 300 497-5: August 1996
6.2.4 Documentation
The comment line of the TC or test step header contains a reference to the relevant protocol specification.
The comment column of the dynamic behaviour part is used to number the test events which are relevant
for the particular test or test operation.
Based on the numbering in the comment column all for the TC relevant events are described in the
detailed comments part of each TTCN table.
Test procedures which cover a conformance requirement and lead to a preliminary or final verdict
assignment ar
...