ETSI ETS 300 497-7 ed.1 (1996-08)

SLOVENSKI STANDARD
01-julij-1999
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH'(&76NXSQLYPHVQLN&,
NQMLåQLFDSUHVNXãDOQLKSULPHURY7&/GHO$EVWUDNWQLSUHVNXãDOQLQL]$76]D
RPUHåQRSODVW1:.SUHQRVQDUDGLMVND]DNOMXþLWHY37
Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Test
Case Library (TCL); Part 7: Abstract Test Suite (ATS) for Network (NWK) layer- Portable
radio Termination (PT)
Ta slovenski standard je istoveten z: ETS 300 497-7 Edition 1
ICS:
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-7
TELECOMMUNICATION August 1996
STANDARD
Source: ETSI TC-RES Reference: DE/RES-03026-7
ICS: 33.020, 33.060.50
Key words: Abstract Test Suites, DECT, GAP
Radio Equipment and Systems (RES);
Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI) Test Case Library (TCL);
Part 7: Abstract Test Suite (ATS) for Network (NWK) 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 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-7: 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-7: August 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions, symbols and abbreviations.9
3.1 DECT definitions.9
3.2 DECT abbreviations.9
3.3 ISO 9646 definitions.10
3.4 ISO 9646 abbreviations .10
4 Abstract Test Method (ATM).11
4.1 ATM .11
4.2 DLC primitives.12
4.2.1 S-SAP primitives .12
4.2.2 B-SAP primitives .15
4.3 TC execution sequence .15
5 Untestable Test Purposes (TPs).15
5.1 Control protocol.15
6 ATS conventions .16
6.1 Naming conventions .16
6.1.1 Declarations part .16
6.1.1.1 Test suite type, ASP and PDU type definitions.16
6.1.1.2 Test Suite Operations (TSO) definitions.17
6.1.1.3 Test suite selection expressions.17
6.1.1.4 Test suite parameter declarations .17
6.1.1.5 Test Case Selection (TCS) expression definitions .17
6.1.1.6 Test Suite Constant (TSC) declarations.17
6.1.1.7 Test Suite Variable (TSV) declarations .17
6.1.1.8 Test Case Variable (TCV) declarations.17
6.1.1.9 Point of Control and Observation (PCO) declarations.18
6.1.1.10 Timer declarations.18
6.1.1.11 ASP type definitions.18
6.1.1.12 PDU type definitions .18
6.1.1.13 Alias definitions.19
6.1.2 Constraints part.19
6.1.3 Dynamic part .20
6.1.3.1 Test Case (TC) identifier .20
6.1.3.2 Test Step (TS) identifier.21
6.1.3.3 Default identifier.21
6.1.3.4 General aspects .21
6.1.3.5 ATS abbreviations .21
6.2 Implementation conventions .22
6.2.1 Declaration part .22
6.2.2 Constraint part.22
6.2.3 Dynamic part .23
6.2.4 Documentation .23
Annex A (normative): Abstract Test Suite (ATS) for NWK testing .24
A.1 The machine processable ATS (TTCN.MP) .24
A.2 The graphical ATS (TTCN.GR).24

Page 4
ETS 300 497-7: August 1996
Annex B (normative): Partial PIXIT proforma . 401
B.1 Identification summary. 401
B.2 ATS summary. 401
B.3 Test laboratory. 401
B.4 Client identification. 401
B.5 SUT. 401
B.6 Protocol layer information. 402
B.6.1 Protocol identification . 402
B.6.2 IUT information. 402
Annex C (normative): Protocol Conformance Test Report (PCTR) Proforma for DECT NWK . 406
C.1 Identification summary. 406
C.1.1 Protocol conformance test report. 406
C.1.2 IUT identification. 406
C.1.3 Testing environment. 406
C.1.4 Limits and reservation . 406
C.1.5 Comments. 407
C.2 IUT Conformance status. 407
C.3 Static conformance summary. 407
C.4 Dynamic conformance summary. 407
C.5 Static conformance review report . 407
C.6 Test campaign report. 408
C.7 Observations. 410
Annex D (informative): Bibliography . 411
History. 412

Page 5
ETS 300 497-7: 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-7: August 1996
Blank page
Page 7
ETS 300 497-7: August 1996
1 Scope
This European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) to test the
Network (NWK) layer, Portable radio Termination (PT).
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. Part 7
of this test specification contains the Abstract Test Suite for testing of the NWK layer at the PT.
The ISO standard for the methodology of conformance testing (ISO/IEC 9646) as well as the ETSI rules
for conformance testing (protocol and profile conformance testing specifications, standardization
methodology ETS 300 406) are used as basis for the test methodology.
Test specifications for the Physical Layer (PHL) are provided in other DECT standards.
Annex B provides the Partial PIXIT Proforma.
2 Normative references
This ETS incorporates by dated and 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".
[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)".

Page 8
ETS 300 497-7: August 1996
[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".
[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".

Page 9
ETS 300 497-7: August 1996
[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".
3 Definitions, symbols and abbreviations
3.1 DECT definitions
For the purposes of this ETS, the definitions given in ISO/IEC 9646-1 [21], ISO/IEC 9646-2 [22],
ETS 300 175-1 [1], ETS 300 175-5 [5], ETS 300 175-6 [6] and ETS 300 175-7 [7] apply.
3.2 DECT abbreviations
For the purposes of this ETS, the NWK layer abbreviations defined in ETS 300 175-5 [5] and the following
abbreviations apply:
AC Authentication Code
AR Access Rights
AU Authentication
CA Capability
CC Call Control
CCSM Call Control State Machine
CI Call Information
CH Ciphering
CR Call Release
CTS Conformance Testing Services
DECT Digital Enhanced Cordless Telecommunication
DLC Data Link Control layer
ETSI European Telecommunications Standards Institute
FT Fixed radio termination
Page 10
ETS 300 497-7: August 1996
GAP Generic Access Profile
IC Incoming Call
ID Identification
IPUI International Portable User Identity
IPEI International Portable Equipment Identity
KA Key Allocation
LC Link Control entity
LE Connection oriented Link Establishment
LL ConnectionLess Link control
LO Location
LR Connection oriented Link Release
LS Connection oriented Link Suspend and resume
MAC Medium Access Control layer
ME Management Entity
ML ConnectionLess Message Services
MM Mobility Management
MO Connection Oriented Message Services
NWK Network layer
OC Outgoing Call
PAP Public Access Profile
PARK Portable Access Rights Key
PM Packet Mode
PR Parameter Retrieval
PT Portable radio termination
RPN Radio Fixed Part Number
RS Call Related Supplementary Services
SC Service Change
UAK User Authentication KeY
3.3 ISO 9646 definitions
For the purposes of this ETS, the following ISO 9646 definitions apply:
Implementation Under Test (IUT)
System Under Test (SUT)
Abstract Test Suite (ATS)
Point of Control and Observation (PCO)
Protocol Implementation Conformance Statement (PICS)
Protocol Implementation eXtra Information for Testing (PIXIT)
Lower Tester (LT)
Upper Tester (UT)
3.4 ISO 9646 abbreviations
For the purposes of this ETS, the following ISO 9646 abbreviations apply:
ATS Abstract Test Suite
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
IWU InterWorking Unit
LT Lower Tester
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statements
PIXIT Protocol Implementation eXtra Information for Testing
SUT System Under Test
TP Test Purpose
Page 11
ETS 300 497-7: August 1996
TSO Test Suite Operation
TSP Test Suite Parameter
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
4 Abstract Test Method (ATM)
This clause describes the ATM, the Point of Control and Observation (PCO) used to test the NWK layer of
the PT.
4.1 ATM
SUT
Test System
Portable Termination
Upper
LT
Layers
DECT NW K
NW K-PDUs
IU T
DLC-
PCO/DSAP
DLC-
Prim itives
DECT DLC layer
DECT DLC layer DECT DLC layer
DECT MAC layer
DECT MAC layer
DECT PHL and radio communication
Figure 1: Remote Single Layer Test Method Embedded variant
LT1: a lower tester (LT1) is located in a remote DECT test system. It controls and
observes the behaviour of the IUT.
DSAP: a unique DLC SAP is defined at the DECT interface and used to exchange
service data of the NWK protocol.
PCO: the PCO for Network Layer testing is located on the DSAP. All test events at the
PCO are specified in terms of DLC ASPs and NWK PDUs.
Upper layers/tester: no explicit Upper Tester (UT) exists in the test system. However, the SUT needs
to carry out some UL functions to achieve some effects of test co-ordination
procedures. Designing ATS, the capability of the IWU, such as PSTN, ISDN or
GSM IWUs might be taken into account. An example of such controls could be
to provoke restarting of the IUT through the Q interface.

Page 12
ETS 300 497-7: August 1996
4.2 DLC primitives
In this subclause the DSAP primitives are defined according to ETS 300 175-4 [4], subclause 8.3.2 (S-
SAP primitives) and ETS 300 175-4 [4], subclause 8.3.3 (B-SAP primitives).
4.2.1 S-SAP primitives
Table 1: DL_DATA_IND primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_DATA_IND S-SAP ETS 300 175-4 [5], subclause 8.3.2.3
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
message_unit PDU ETS 300 175-4 [5], subclause 8.3.1
Table 2: DL_DATA_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_DATA_REQ S-SAP ETS 300 175-4 [5], subclause 8.3.2.3
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
message_unit PDU ETS 300 175-4 [5], subclause 8.3.1
Table 3: DL_ENCRYPT_CNF primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ENCRYPT_CNF S-SAP ETS 300 175-4 [5], subclause 8.3.2.8
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
encription_status CIPHER_STATUS ETS 300 175-4 [5], subclause 8.3.1
(INTEGER(0,1))
Table 4: DL_ENCRYPT_IND primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ENCRYPT_IND S-SAP ETS 300 175-4 [5], subclause 8.3.2.8
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
connection_identities CONNECTION_IDENTITIE ETS 300 175-4 [5], subclause 8.3.1
S
(OCTETSTRING)
encription_status CIPHER_STATUS ETS 300 175-4 [5], subclause 8.3.1
(INTEGER(0,1)
Page 13
ETS 300 497-7: August 1996
Table 5: DL_ENCRYPT_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ENCRYPT_REQ S-SAP ETS 300 175-4 [5], subclause 8.3.2.8
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
connection_identities CONNECTION_IDENTITIE ETS 300 175-4 [5], subclause 8.3.1
S
(OCTETSTRING)
encription_status CIPHER_STATUS ETS 300 175-4 [5], subclause 8.3.1
(INTEGER(0,1)
Table 6: DL_ENC_KEY_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ENC_KEY_REQ S-SAP ETS 300 175-4 [5], subclause 8.3.2.7
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], 7.3.6
ENTIFIER
(INTEGER)
connection_identities CONNECTION_IDENTITIE ETS 300 175-4 [5], 8.3.1
S
(OCTETSTRING)
encription_key ENCRYPTION_KEY ETS 300 175-4 [5], 8.3.1
(BITSTRING[64])
Table 7: DL_ESTABLISH_CNF primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ESTABLISH_CNF S-SAP ETS 300 175-4 [5], subclause 8.3.2.1
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
Table 8: DL_ESTABLISH_IND primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ESTABLISH_IND S-SAP ETS 300 175-4 [5], subclause 8.3.2.1
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
establish_mode ESTABLISH_MODE ETS 300 175-4 [5], subclause 8.3.1
(INTEGER(0,1,2)
radio_fixed_part_number RADIO_FIXED_PART_NUMETS 300 175-4 [5], subclause 8.3.1
BER
(INTEGER)
message_unit PDU ETS 300 175-4 [5], subclause 8.3.1

Page 14
ETS 300 497-7: August 1996
Table 9: DL_ESTABLISH_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ESTABLISH_REQ S-SAP ETS 300 175-4 [5], subclause 8.3.2.1
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
establish_mode ESTABLISH_MODE ETS 300 175-4 [5], subclause 8.3.1
(INTEGER(0,1,2)
radio_fixed_part_number RADIO_FIXED_PART_NUMETS 300 175-4 [5], subclause 8.3.1
BER
(INTEGER)
message_unit PDU ETS 300 175-4 [5], subclause 8.3.1
Table 10: DL_ESTABLISH_RES primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ESTABLISH_RES S-SAP ETS 300 175-4 [5], subclause 8.3.2.1
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
Table 11: DL_RELEASE_CNF primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_RELEASE_CNF S-SAP ETS 300 175-4 [5], subclause 8.3.2.2
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
release_mode RELEASE_MODE ETS 300 175-4 [5], subclause 8.3.1
(INTEGER(0,1)
Table 12: DL_RELEASE_IND primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_RELEASE_IND S-SAP ETS 300 175-4 [5], subclause 8.3.2.2
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
release_mode RELEASE_MODE ETS 300 175-4 [5], subclause 8.3.1
(INTEGER(0,1)
Page 15
ETS 300 497-7: August 1996
Table 13: DL_RELEASE_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_RELEASE_REQ S-SAP ETS 300 175-4 [5], subclause 8.3.2.2
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [5], subclause 7.3.6
ENTIFIER
(INTEGER)
release_mode RELEASE_MODE ETS 300 175-4 [5], subclause 8.3.1
(INTEGER(0,1)
4.2.2 B-SAP primitives
Table 14: DL_BROADCAST_IND primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_BROADCAST_IND B-SAP ETS 300 175-4 [5], subclause 8.3.3.1
Service control information
Parameter name Type Comments
cluster_address_list CLUSTER_ADDRESS_LISTETS 300 175-4 [5], subclause 8.3.1
(OCTETSTRING)
message_unit PDU ETS 300 175-4 [5], subclause 8.3.1
extended_message_flag BIT_1 ETS 300 175-4 [5], subclause 8.3.1
(BITSTRING[1])
error_flag BIT_1 ETS 300 175-4 [5], subclause 8.3.1
(BITSTRING[1])
Table 15: DL_BROADCAST_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_BROADCAST_REQ B-SAP ETS 300 175-4 [5], subclause 8.3.3.1
Service control information
Parameter name Type Comments
cluster_address_list CLUSTER_ADDRESS_LISTETS 300 175-4 [5], subclause 8.3.1
(OCTETSTRING)
message_unit PDU ETS 300 175-4 [5], subclause 8.3.1
extended_message_flag BIT_1 ETS 300 175-4 [5], subclause 8.3.1
(BITSTRING[1])
4.3 TC execution sequence
The test cases can be executed in any order with no restrictions.
5 Untestable Test Purposes (TPs)
This clause gives a list of TPs which are not implemented in the ATS (annex A) due to the chosen ATM or
other restrictions.
5.1 Control protocol
There are no untestable TPs in this ATS.

Page 16
ETS 300 497-7: August 1996
6 ATS conventions
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 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 [29] 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.
The following general rules apply:
- identifiers shall be written in lowercase;
- type declarations shall be written in uppercase;
- constraints shall be written with the first letter in uppercase, and the rest in lowercase.
Information elements are coded in the order from top to bottom and from right to left, in order to make the
encoding and decoding easier.
6.1.1.1 Test suite type, ASP and PDU type definitions
The test suite type-definitions, the ASP type definitions and the PDU type definitions shall be written in
uppercase. Identifier names of structured type definitions and of the ASP and PDU type definitions, shall
be written in lowercase.
Types related to a certain higher layer entity shall commence with a protocol identifier to define which
entity they belong to.
EXAMPLE 1: Call Control: cc e.g. CC_SETUP
Id names of Structured Types which are used for invalid tests commence with "bi":
EXAMPLE 2: Bi_cc_setup_tx01
The following ASP primitives are not defined in this ETS.
- DL_UNIT_DATA;
- DL_SUSPEND;
- DL_RESUME;
- DL_EXPEDITED.
Page 17
ETS 300 497-7: August 1996
The following primitives are defined, but not used in this test suite:
- DL_BROADCAST_IND;
- DL_ESTABLISH_CFM;
- DL_ESTABLISH_RES.
6.1.1.2 Test Suite Operations (TSO) definitions
The TSO identifiers are composed of a string in uppercase letters starting by the string "TSO_" (e.g.
TSO_INTEGER_TO_O_1).
6.1.1.3 Test suite selection expressions
All selection expression names for test groups are to be preceded with the prefix "SENG_".
All selection expression names for test cases are to be preceded with the prefix "SENC_".
6.1.1.4 Test suite parameter declarations
The TSP identifiers are composed of a string in uppercase letters starting by the string "TSP_" (e.g.
TSP_WINDOW_SIZE).
If the TSP references a PICS item, the letter "C" is added to the standard prefix (e.g.
TSPC_PICS_ITEM_S23).
If the TSP references a PIXIT item, the letter "X" is added to the standard prefix (e.g.
TSPX_PIXIT_ITEM_2).
Exception: If the TSP represents a system parameter or value, only the name defined in the
specifications is used (e.g. V_S = send sequence variable).
Complete names as defined in the specifications are used.
6.1.1.5 Test Case Selection (TCS) expression definitions
The naming conventions for the TCS expression definitions use almost the same rules as the TSP, except
for the prefix that is "TCS_". Also they are logical combinations of the TSP definitions.
6.1.1.6 Test Suite Constant (TSC) declarations
The TSC identifiers are composed of a string in uppercase letters starting by the string "TSC_" (e.g.
TSC_RETRY).
Exception: If the TSC represents a system parameter or value, only the name defined in the
specifications is used (e.g. N250).
Complete names as defined in the specifications are used.
6.1.1.7 Test Suite Variable (TSV) declarations
The TSV identifiers are composed of a string in uppercase letters starting by the string "TSV_".
Complete names as defined in the specifications are used.
6.1.1.8 Test Case Variable (TCV) declarations
The TCV identifiers are composed of a string in uppercase letters starting by the string "TCV_".
EXAMPLE: TCV_CRVALUE.
Complete names as defined in the specifications are used.

Page 18
ETS 300 497-7: August 1996
6.1.1.9 Point of Control and Observation (PCO) declarations
The PCO 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.
6.1.1.10 Timer declarations
Two types of timers can be identified:
1) standardised:
- those defined in the standard, e.g. T302. They 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: T302_max, T302_min, and T302.
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 capital letters.
EXAMPLE 2: T_RESP represents a timer for controlling the response time of the IUT.
6.1.1.11 ASP type definitions
The identifier of an ASP uses exactly the same name as the name defined in the specifications. It is
written in uppercase, 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-CO_DATA_REQ for an ASP containing a layer 2b PDU passed to layer
2a.
6.1.1.12 PDU type definitions
The identifier of a PDU is given in a string in uppercase letters, representing 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.
Id names of PDUs commence with a protocol identifier to define which protocol they belong to. The
following identifiers are used:
- Call Control: cc e.g. CC-SETUP
Id names of PDUs which are used for invalid tests commence with "bi":
EXAMPLE 3: BI-CC-SETUP
Page 19
ETS 300 497-7: August 1996
6.1.1.13 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.
The identifier of an alias consists of a string in capital letters indicating the message, followed by two
lowercase letters "r" or "s" indicating if the message should be sent or received by the tester.
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 identifier 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.
Structured type constraints declarations are divided into:
- receive constraints:
the receive constraints are noted down as "name_rx*". The receive constraints are
subdivided into:
- receive base constraints:
they are noted down as "name_rx_base";
- receive special constraints:
they are noted down as "name_rx_", where is a
descriptive name (e.g. "Signal_rx_alerting_on");
- transmit constraints:
the transmit constraints are noted down as "name_tx_", where is a
descriptive name. (e.g. "Signal_tx_alerting_off");
If a certain structured type constraint is valid for both receiving and transmitting, because it contains no
wildcards, and the receiving constraint should exactly match, the constraint will be noted down as:
- "_extention" Example: "Portable_id_ipui".

Page 20
ETS 300 497-7: August 1996
PDU Constraints Declarations are divided into:
- receive constraints:
- the receive constraints are noted down as "name_rx*". The receive constraints are
subdivided into:
- receive base constraints:
- they are noted down as "name_rx_base". They constrain all allowed values, and
for the optional fields, the "IF_PRESENT" keyword is added;
- receive special constraints:
- they are noted down as "name_rx0n", where n is a sequence number;
- transmit constraints:
- the transmit constraints are noted down as "name_tx", where n is a sequence number. They
can be subdivided into:
- transmit base constraints:
- they are noted down as "name_tx_base". They constrain all mandatory fields to
all allowed values in the standard, and they constrain all optional fields to
"OMIT";
- transmit special constraints:
- they are noted down as "name_tx0n" where n is a sequence number. They shall
not contain any wildcards.
Derived constraints shall not be more than 1 level deep. They shall only be derived directly from the base
constraint.
The test suite is not ready yet to handle PDU"s with empty information elements. For every receive
constraint, also a information element constraint with an empty parameter list should be added.
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 (TC) identifier
The identifier of the TCs is built in the same way as for the TPs described in ETS 300 324-3 [3], subclause
5.1.1, with the exception that "TP" is replaced by "TC":
TP identifier: TPCCBI-04;
TC identifier: TCCCBI-04.
Page 21
ETS 300 497-7: August 1996
6.1.3.2 Test Step (TS) identifier
The TS identifier is built with two strings of capital letters joined by underscore character. The first string
indicates the main function of the TS, e.g. PR for preamble, PO for postamble, CS for check state and
STP for general step. The second string indicates the meaning of the step.
In some TCs, test steps as well as local trees can be used. To allow an easy distinguishing of them the
following naming applies:
- LTS_[local_tree_name] local tree;
- STP_[test_step_name] test step.
TSs are grouped together according to their functionality: CC, MM, LC or ME.
6.1.3.3 Default identifier
The default identifiers begin with the prefix "DF_", followed by a string in capital letters.
6.1.3.4 General aspects
Final verdicts will only be assigned in defaults and in postambles.
All verdict assignments are labelled. To allow an exact identification in which table the verdict was
assigned, the following name convention is applied:
B test Body
CS Check State test steps
D Default
E Error handling test steps
PO POstamble
PR PReamble
S test Step
Also combinations of labels are possible:
EXAMPLE: DPR --> label which is used in a default for preambles.
6.1.3.5 ATS abbreviations
These abbreviations are used to shorten identifier names:
ack acknowledgement
auth authentication
algo algorithm
cc call control
cfm confirm
est establish
ext extension
id identification
ind indication
info information
max maximum
min minimum
prop proprietary
req request
res response
Page 22
ETS 300 497-7: August 1996
The following keywords will NOT be abbreviated in identifier names:
address(es);
attribute(s);
identity;
number(s);
character(s).
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
...