SIST ETS 300 497-7 E2:2003

SLOVENSKI STANDARD
01-december-2003
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH'(&7±6NXSQLYPHVQLN&,±
.QMLåQLFDSUHVNXãDOQLKSULPHURY7&/±GHO$EVWUDNWQLSUHVNXãDOQLQL]$76]D
RPUHåQRSODVW1:.±3UHQRVQDUDGLMVND]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 2
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 February 1998
STANDARD Second Edition
Source: DECT Reference: RE/DECT-040094-7
ICS: 33.020
Key words: ATS, DECT, PIXIT, radio, testing
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 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 2
ETS 300 497-7: 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 3
ETS 300 497-7: February 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions, symbols and abbreviations.9
3.1 Definitions .9
3.2 DECT abbreviations.9
4 Abstract Test Method (ATM).10
4.1 ATM .10
4.2 DLC primitives.11
4.2.1 S-SAP primitives .11
4.2.2 B-SAP primitives .14
4.3 TC execution sequence .15
5 Untestable Test Purposes (TP).15
6 ATS conventions .15
6.1 Naming conventions .15
6.1.1 Declarations part .15
6.1.1.1 Test suite type, ASP and PDU type definitions.16
6.1.1.2 Test Suite Operations (TSO) definitions.16
6.1.1.3 Test suite selection expressions.16
6.1.1.4 Test Suite Parameter (TSP) declarations.16
6.1.1.5 Test Case Selection (TCS) expression definitions .16
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.17
6.1.1.10 Timer declarations.17
6.1.1.11 ASP type definitions.18
6.1.1.12 PDU type definitions .18
6.1.1.13 Alias definitions.18
6.1.2 Constraints part.18
6.1.3 Dynamic part .20
6.1.3.1 Test Case (TC) identifier .20
6.1.3.2 Test Step (TS) identifier.20
6.1.3.3 Default identifier.20
6.1.3.4 General aspects .20
6.1.3.5 ATS abbreviations .20
6.2 Implementation conventions .21
6.2.1 Declaration part .21
6.2.2 Constraint part.21
6.2.3 Dynamic part .22
6.2.4 Documentation .22
Annex A (normative): Abstract Test Suite (ATS) for NWK testing .23
A.1 The machine processable ATS (TTCN.MP) .23
A.2 The graphical ATS (TTCN.GR).23
Annex B (normative): Partial PIXIT proforma.24

Page 4
ETS 300 497-7: February 1998
B.1 Identification summary. 24
B.2 ATS summary. 24
B.3 Test laboratory. 24
B.4 Client identification. 24
B.5 SUT. 25
B.6 Protocol layer information. 25
B.6.1 Protocol identification . 25
B.6.2 IUT information. 26
Annex C (normative): Protocol Conformance Test Report (PCTR) proforma for DECT NWK . 30
C.1 Identification summary. 30
C.1.1 Protocol conformance test report. 30
C.1.2 IUT identification. 30
C.1.3 Testing environment. 30
C.1.4 Limits and reservation . 30
C.1.5 Comments. 31
C.2 IUT conformance status . 31
C.3 Static conformance summary. 31
C.4 Dynamic conformance summary. 31
C.5 Static conformance review report . 31
C.6 Test campaign report. 32
C.7 Observations. 34
Annex D (informative): Bibliography . 35
History. 36

Page 5
ETS 300 497-7: 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 6
ETS 300 497-7: February 1998
Blank page
Page 7
ETS 300 497-7: February 1998
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 parts 1 to 7 [12] to [18]) as
well as the ETSI rules for conformance testing (protocol and profile conformance testing specifications,
standardization methodology ETS 300 406 [10]) 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 Protocol Implementation Extra Information for Testing (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: "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 324-3: "Signalling Protocols and Switching (SPS); V interfaces at the
digital Local Exchange (LE); V5.1 interface for the support of Access Network
(AN); Part 3: Test Suite Structure and Test Purposes (TSS&TP) specification for
the network layer (AN side)".
[10] ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and
profile conformance testing specifications; Standardization methodology".
[11] ETS 300 444: "Digital European Cordless Telecommunications (DECT); Generic
Access Profile (GAP)".
Page 8
ETS 300 497-7: February 1998
[12] 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)).
[13] 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)).
[14] 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)).
[15] 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)).
[16] 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)).
[17] ISO/IEC 9646-6 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 6:
Protocol profile test specification".
[18] ISO/IEC 9646-7 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 7:
Implementation conformance statement".
[19] 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).
[20] TBR 6: "Digital Enhanced Cordless Telecommunications (DECT); General
terminal attachment requirements".
[21] TBR 10: "Digital Enhanced Cordless Telecommunications (DECT); General
terminal attachment requirements; Telephony applications".
[22] TBR 11: "Attachment requirements for terminal equipment for Digital Enhanced
Cordless Telecommunications (DECT) Public Access Profile (PAP)
applications".
[23] TBR 22: "Attachment requirements for terminal equipment for Digital Enhanced
Cordless Telecommunications (DECT) Generic Access Profile (GAP)
applications".
[24] ETR 141: "Methods for Testing and Specification (MTS); Protocol and profile
conformance testing specifications; The Tree and Tabular Combined Notation
(TTCN) style guide".
Page 9
ETS 300 497-7: February 1998
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of this ETS, the definitions given in ISO/IEC 9646-1 [12], ISO/IEC 9646-2 [13],
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 following abbreviations apply:
AC Authentication Code
AR Access Rights
ASP Abstract Service Primitive
ATS Abstract Test Suite
AU Authentication
BI Invalid Behaviour
BO Inopportune Behaviour
BV Valid Behaviour
CA Capability
CC Call Control
CH Ciphering
CI Call Information
CR Call Release
DECT Digital Enhanced Cordless Telecommunication
DLC Data Link Control
FT Fixed radio Termination
IC Incoming Call
ID Identification
IPEI International Portable Equipment Identity
IPUI International Portable User Identity
IUT Implementation Under Test
IWU Interworking Unit
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
LT Lower Tester
MAC Medium Access Control
ME Management Entity
MM Mobility Management
MO Connection Oriented Message Services
NWK Network layer
OC Outgoing Call
PARK Portable Access Rights Key
PCO Point of Control and Observation
PCTR Protocol Conformance Test Report
PDU Protocol Data Unit
PHL Physical Layer
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation Extra Information for Testing
PT Portable radio Termination
RPN Radio Fixed Part Number
RS Call Related Supplementary Services
SUT System Under Test
TCS Test Case Selection
TCV Test Case Variable
TP Test Purposes
TSC Test Suite Constant
TSO Test Suite Operation
Page 10
ETS 300 497-7: February 1998
TSP Test Suite Parameter
TSS Test Suite Structure
TSV Test Suite Variable
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 NWK
NWK-PDUs
IUT
DLC-
PCO/DSAP
DLC-
Primitives
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 Implementation Under Test (IUT).
DSAP: a unique Data Link Control (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 Abstract Service Primitives (ASPs) and
NWK Protocol Data Units (PDUs).

Page 11
ETS 300 497-7: February 1998
Upper layers/tester: no explicit Upper Tester (UT) exists in the test system. However, the System
Under Test (SUT) needs to carry out some UL functions to achieve some
effects of test co-ordination procedures. Designing ATS, the capability of the
Interworking Unit (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.
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 [4], subclause 8.3.2.3
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
message_unit PDU ETS 300 175-4 [4], 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 [4], subclause 8.3.2.3
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
message_unit PDU ETS 300 175-4 [4], 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 [4], subclause 8.3.2.8
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
encription_status CIPHER_STATUS ETS 300 175-4 [4], subclause 8.3.1
(INTEGER(0,1))
Page 12
ETS 300 497-7: February 1998
Table 4: DL_ENCRYPT_IND primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ENCRYPT_IND S-SAP ETS 300 175-4 [4], subclause 8.3.2.8
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
connection_identities CONNECTION_IDENTITIE ETS 300 175-4 [4], subclause 8.3.1
S
(OCTETSTRING)
encription_status CIPHER_STATUS ETS 300 175-4 [4], subclause 8.3.1
(INTEGER(0,1)
Table 5: DL_ENCRYPT_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ENCRYPT_REQ S-SAP ETS 300 175-4 [4], subclause 8.3.2.8
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
connection_identities CONNECTION_IDENTITIE ETS 300 175-4 [4], subclause 8.3.1
S
(OCTETSTRING)
encription_status CIPHER_STATUS ETS 300 175-4 [4], 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 [4], subclause 8.3.2.7
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
connection_identities CONNECTION_IDENTITIE ETS 300 175-4 [4], subclause 8.3.1
S
(OCTETSTRING)
encription_key ENCRYPTION_KEY ETS 300 175-4 [4], subclause 8.3.1
(BITSTRING[64])
Page 13
ETS 300 497-7: February 1998
Table 7: DL_ESTABLISH_CNF primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ESTABLISH_CNF S-SAP ETS 300 175-4 [4], subclause 8.3.2.1
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], 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 [4], subclause 8.3.2.1
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
establish_mode ESTABLISH_MODE ETS 300 175-4 [4], subclause 8.3.1
(INTEGER(0,1,2)
radio_fixed_part_number RADIO_FIXED_PART_NUMETS 300 175-4 [4], subclause 8.3.1
BER
(INTEGER)
message_unit PDU ETS 300 175-4 [4], subclause 8.3.1
Table 9: DL_ESTABLISH_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_ESTABLISH_REQ S-SAP ETS 300 175-4 [4], subclause 8.3.2.1
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
establish_mode ESTABLISH_MODE ETS 300 175-4 [4], subclause 8.3.1
(INTEGER(0,1,2)
radio_fixed_part_number RADIO_FIXED_PART_NUMETS 300 175-4 [4], subclause 8.3.1
BER
(INTEGER)
message_unit PDU ETS 300 175-4 [4], 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 [4], subclause 8.3.2.1
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
Page 14
ETS 300 497-7: February 1998
Table 11: DL_RELEASE_CNF primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_RELEASE_CNF S-SAP ETS 300 175-4 [4], subclause 8.3.2.2
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
release_mode RELEASE_MODE ETS 300 175-4 [4], 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 [4], subclause 8.3.2.2
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
release_mode RELEASE_MODE ETS 300 175-4 [4], subclause 8.3.1
(INTEGER(0,1)
Table 13: DL_RELEASE_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_RELEASE_REQ S-SAP ETS 300 175-4 [4], subclause 8.3.2.2
Service control information
Parameter name Type Comments
data_link_endpoint_identifier DATA_LINK_ENDPOINT_IDETS 300 175-4 [4], subclause 7.3.6
ENTIFIER
(INTEGER)
release_mode RELEASE_MODE ETS 300 175-4 [4], 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 [4], subclause 8.3.3.1
Service control information
Parameter name Type Comments
cluster_address_list CLUSTER_ADDRESS_LISTETS 300 175-4 [4], subclause 8.3.1
(OCTETSTRING)
message_unit PDU ETS 300 175-4 [4], subclause 8.3.1
extended_message_flag BIT_1 ETS 300 175-4 [4], subclause 8.3.1
(BITSTRING[1])
error_flag BIT_1 ETS 300 175-4 [4], subclause 8.3.1
(BITSTRING[1])
Page 15
ETS 300 497-7: February 1998
Table 15: DL_BROADCAST_REQ primitive
ASP Declaration
ASP NAME PCO TYPE COMMENTS
DL_BROADCAST_REQ B-SAP ETS 300 175-4 [4], subclause 8.3.3.1
Service control information
Parameter name Type Comments
cluster_address_list CLUSTER_ADDRESS_LISTETS 300 175-4 [4], subclause 8.3.1
(OCTETSTRING)
message_unit PDU ETS 300 175-4 [4], subclause 8.3.1
extended_message_flag BIT_1 ETS 300 175-4 [4], 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 (TP)
This clause gives a list of TP which are not implemented in the ATS (annex A) due to the chosen ATM or
other restrictions.
Table 16: Untestable TP (1)
Test Purpose Reference to ETS 300 497-7
TP/PT/MM/BV/PR-01
TP/PT/IS/BV-01
TP/PT/IS/BV-02
TP/PT/IS/BV-03
TP/PT/IS/BV-04
TP/PT/CL/BV-01
TP/PT/CL/BV-02
TP/PT/CL/BV-03
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 [10] and ETR 141 [24] 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.

Page 16
ETS 300 497-7: February 1998
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.
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 (TSP) 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 Protocol Implementation Conformance Statement (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.

Page 17
ETS 300 497-7: February 1998
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.
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 Medium Access Control (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) standardized:
- 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 standardized:
- 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.

Page 18
ETS 300 497-7: February 1998
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): cc e.g. CC-SETUP
Id names of PDUs which are used for invalid tests commence with "bi":
EXAMPLE 3: BI-CC-SETUP
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.

Page 19
ETS 300 497-7: February 1998
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".
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.

Page 20
ETS 300 497-7: February 1998
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 TP described in ETS 300 324-3 [9], subclause
5.1.1, with the exception that "TP" is replaced by "TC":
TP identifier: TPCCBI-04;
TC identifier: TCCCBI-04.
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
Page 21
ETS 300 497-7: February 1998
ind indication
info information
max maximum
min minimum
prop proprietary
req request
res response
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 Tree and Tabular Combined Notation (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.
In tables where structure types are used the information element and the relevant structured type have
always the same name, that allows to have the same structure as in the protocol standards is used to
document the relation between information elements in a table and their specific description in an other
clause of the protocol standard.
The following conventions apply to identifier names in the Structured Type definitions part:
- bits of bit sequences having a fixed value, meant to fill up the octet, are called fn, where n stands
for the octet number;
- extension flags, will be called extn, where n stands for the octet number.
6.2.2 Constraint part
The ASPs and PDUs are defined in a way that all relevant element are parameterized. That improves the
transparency of the constraints in the dynamic part, as all values which are relevant for the test are always
present.
Generally no modified constraints are used, this allows an easier reuse and adaptation of constraints if
they are reused in other 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.

Page 22
ETS 300 497-7: February 1998
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. FAIL verdicts are only assigned in the defau
...