ETSI ETS 300 394-4-10 ed.1 (1999-06)

SLOVENSKI STANDARD
SIST ETS 300 394-4-10 E1:2003
01-december-2003
3UL]HPQLVQRSRYQLUDGLR7(75$6SHFLILNDFLMD]DSUHVNXãDQMHVNODGQRVWLGHO
6SHFLILNDFLMD]DSUHVNXãDQMHSURWRNROD]DQHSRVUHGQRREUDWRYDQMH'02¤
SRGGHO$EVWUDNWQLSUHVNXãDOQLQL]$76]DQHSRVUHGQRGHOXMRþLSUHKRG'0
*$7(
Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 4: Protocol
testing specification for Direct Mode Operation (DMO); Sub-part 10: Abstract Test Suite
(ATS) for Direct Mode Gateway (DM-GATE)
Ta slovenski standard je istoveten z: ETS 300 394-4-10 Edition 1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST ETS 300 394-4-10 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 394-4-10 E1:2003

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

SIST ETS 300 394-4-10 E1:2003
EUROPEAN ETS 300 394-4-10
TELECOMMUNICATION June 1999
STANDARD
Source: TETRA Reference: DE/TETRA-02009-4-10
ICS: 33.020
Key words: TETRA, protocol, testing, TTCN, radio
Terrestrial Trunked Radio (TETRA);
Conformance testing specification;
Part 4: Protocol testing specification for
Direct Mode Operation (DMO);
Sub-part 10: Abstract Test Suite (ATS)
for Direct Mode Gateway (DM-GATE)
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
Internet: secretariat@etsi.fr - http://www.etsi.org
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 1999. All rights reserved.

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

SIST ETS 300 394-4-10 E1:2003
Page 2
ETS 300 394-4-10: June 1999
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 Standards Making Support Dept." at the address shown on the title page.

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

SIST ETS 300 394-4-10 E1:2003
Page 3
ETS 300 394-4-10: June 1999
Contents
Foreword . 5
1 Scope. 7
2 References. 7
2.1 Normative references. 7
2.2 Other references . 8
3 Definitions and abbreviations. 8
3.1 TETRA definitions . 8
3.2 TETRA abbreviations .8
3.3 ISO 9646 definitions . 8
3.4 ISO 9646 abbreviations.9
4 Abstract Test Method (ATM). 9
4.1 Lower Tester (LT). 10
4.2 Upper Tester (UT) . 10
4.3 Test Co-ordination Procedures (TCP). 10
4.4 Point of Control and Observation (PCO) . 10
4.5 Non-testable test purposes and implementation matters. 10
5 ATS conventions. 11
5.1 Naming conventions. 11
5.1.1 Declarations part. 11
5.1.1.1 Test suite type and structured type definitions. 11
5.1.1.2 Test suite operations definitions. 11
5.1.1.3 Test suite parameter declarations. 11
5.1.1.4 Test case selection expression definitions. 11
5.1.1.5 Test suite constant declarations. 12
5.1.1.6 Test suite variable declarations. 12
5.1.1.7 Test case variable declarations. 12
5.1.1.8 PCO declarations . 12
5.1.1.9 Timer declarations. 12
5.1.1.10 ASP type definitions . 12
5.1.1.11 PDU type definitions. 13
5.1.1.12 Alias definitions . 13
5.1.2 Constraints part. 13
5.1.3 Dynamic part. 14
5.1.3.1 Test case identifier . 14
5.1.3.2 Test step identifier. 14
5.1.3.3 Default identifier . 14
5.2 TC and TP naming . 14
Annex A (normative): ATS for TETRA DMO Gateway MAC layer. 15
A.1 The TTCN Graphical form (TTCN.GR). 15
A.2 The TTCN Machine Processable form (TTCN.MP). 15
Annex B (normative): Partial PIXIT proforma for TETRA DMO Gateway MAC layer protocol . 16
B.1 Identification summary. 16
B.2 ATS summary . 16
B.3 Test laboratory . 16

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

SIST ETS 300 394-4-10 E1:2003
Page 4
ETS 300 394-4-10: June 1999
B.4 Client identification .16
B.5 SUT .17
B.6 Protocol layer information.17
B.6.1 Protocol identification.17
B.6.2 IUT information .17
B.6.2.1 Implicit send events.17
B.6.2.2 Parameter values .18
Annex C (normative): Protocol Conformance Test Report (PCTR) proforma for TETRA DMO
Gateway MAC layer protocol.19
C.1 Identification summary .19
C.1.1 Protocol conformance test report.19
C.1.2 IUT identification .19
C.1.3 Testing environment .19
C.1.4 Limits and reservation.20
C.1.5 Comments .20
C.2 IUT conformance status.20
C.3 Static conformance summary.20
C.4 Dynamic conformance summary.20
C.5 Static conformance review report.21
C.6 Test campaign report .22
C.7 Observations .23
Annex D (informative): Bibliography.24
History.25

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

SIST ETS 300 394-4-10 E1:2003
Page 5
ETS 300 394-4-10: June 1999
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio
(TETRA) Project of the European Telecommunications Standards Institute (ETSI).
This ETS consists of 4 parts as follows:
Part 1: "Radio";
Part 2: "Protocol testing specification for Voice plus Data (V+D)";
Part 4: "Protocol testing specification for Direct Mode Operation (DMO)";
Part 5: "Security".
Transposition dates
Date of adoption of this ETS: 4 June 1999
Date of latest announcement of this ETS (doa): 30 September 1999
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 March 2000
Date of withdrawal of any conflicting National Standard (dow): 31 March 2000

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

SIST ETS 300 394-4-10 E1:2003
Page 6
ETS 300 394-4-10: June 1999
Blank page

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

SIST ETS 300 394-4-10 E1:2003
Page 7
ETS 300 394-4-10: June 1999
1 Scope
This ETS contains the Abstract Test Suites (ATS) to test the Terrestrial Trunked Radio (TETRA) Direct
Mode Operation (DMO) Gateway V+D interface at layer 3, i.e. the GateWay Call Control (GWCC) and the
GateWay Mobility Management (GWMM) protocol. The GWCC and GWMM protocols are specified in
ETS 300 396-1 [1] and in ETS 300 396-5 [2]. The Test Suite Structure and Test Purposes (TSS&TPs) for
these ATSs are defined in ETS 300 394-4-8 [4].
The objective of this test specification is to provide a basis for approval tests for TETRA equipment giving
a high probability of air interface inter-operability between different manufacturer's TETRA equipment.
The ISO standard for the methodology of conformance testing, ISO/IEC 9646-1 [6], ISO/IEC 9646-2 [7],
ISO/IEC 9646-3 [8] and ISO/IEC 9646-5 [9], as well as the ETSI rules for conformance testing,
ETS 300 406 [5] and ETR 141 [10] are used as a basis for the test methodology.
Annex A provides the Tree and Tabular Combined Notation (TTCN) part of this ATS in an electronic file.
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 References
2.1 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 396-1: "Terrestrial Trunked Radio (TETRA); Technical requirements
for Direct Mode Operation (DMO); Part 1: General network design".
[2] ETS 300 396-5: "Terrestrial Trunked Radio (TETRA); Technical requirements
for Direct Mode Operation (DMO); Part 5: Gateways".
[3] ETS 300 396-8-3: "Terrestrial Trunked Radio (TETRA); Conformance testing
specification; Part 4: Protocol testing specification for Direct Mode Operation
(DMO); Sub-part 8: Test Suite Structure and Test Purposes (TSS&TP) for Direct
Mode Gateway (DM-GATE)".
[4] ETS 300 394-4-8 (1998): "Terrestrial Trunked Radio (TETRA); Part 4: Protocol
testing specification for Direct Mode Operation (DMO); Sub-part 8: Test Suite
Structure and Test Purposes for Direct Mode Gateway (DM-GATE)".
[5] ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and
profile conformance testing specifications; Standardization methodology".
[6] ISO/IEC 9646-1 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1:
General concepts". (See also ITU-T Recommendation X.290 (1991)).
[7] ISO/IEC 9646-2 (1994): "Information technology; Open Systems
Interconnection; Conformance testing methodology and framework; Part 2:
Abstract Test Suite Specification". (See also ITU-T
Recommendation X.291 (1991)).

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

SIST ETS 300 394-4-10 E1:2003
Page 8
ETS 300 394-4-10: June 1999
[8] ISO/IEC 9646-3 (1994): "Information technology; Open Systems
Interconnection; Conformance testing methodology and framework; Part 3: The
Tree and Tabular Combined Notation (TTCN)". (See also
ITU-T Recommendation X.292 (1992)).
[9] ISO/IEC 9646-5 (1994): "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 ITU-T Recommendation X.292 (1992)).
2.2 Other references
[10] ETR 141 (1994): "Methods for Testing and Specification (MTS); Protocol and
profile conformance testing specifications; The Tree and Tabular Combined
Notation (TTCN) style guide".
3 Definitions and abbreviations
3.1 TETRA definitions
For the purposes of this ETS, the definitions given in ETS 300 396-5 [2] apply.
3.2 TETRA abbreviations
For the purposes of this ETS the following TETRA abbreviations apply:
GWCC GateWay Call Control
GWMM GateWay Mobility Management
MAC Medium Access Control
MS Mobile Station
MS-GW Mobile Station Gateway
SDS Short Data Service
3.3 ISO 9646 definitions
For the purposes of this ETS the following ISO/IEC 9646-1 [6] definitions apply:
Abstract Test Suite (ATS)
Abstract Test Method (ATM)
Implementation Conformance Statement (ICS)
Implementation Under Test (IUT)
Implementation eXtra Information for Testing (IXIT)
Lower Tester (LT)
PICS proforma
PIXIT proforma
Point of Control and Observation (PCO)
Protocol Implementation Conformance Statement (PICS)
Protocol Implementation eXtra Information for Testing (PIXIT)
Service Access Point (SAP)
Single Party Testing (SPyT)
System Under Test (SUT)
Upper Tester (UT)
For the purposes of this ETS the following ISO/IEC 9646-3 [8] definitions apply:
TTCN.GR
TTCN.MP
For the purposes of this ETS the following ISO/IEC 9646-5 [9] definitions apply:
Protocol Conformance Test Report (PCTR)
PCTR proforma

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

SIST ETS 300 394-4-10 E1:2003
Page 9
ETS 300 394-4-10: June 1999
3.4 ISO 9646 abbreviations
For the purposes of this ETS the following ISO/IEC 9646-1 [6] abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
IUT Implementation Under Test
LT Lower Tester
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statements
PIXIT Protocol Implementation eXtra Information for Testing
SAP Service Access Point
SPyT Single Party Testing
SUT System Under Test
TC Test Case
TP Test Purpose
TTCN Tree and Tabular Combined Notation
TSS Test Suite Structure
UT Upper Tester
For the purposes of this ETS the following ISO/IEC 9646-5 [9] abbreviations apply:
PCTR Protocol Conformance Test Report
4 Abstract Test Method (ATM)
This clause describes the ATM used for testing the GWCC and GWMM. The test method selected is the
embedded variant of the remote test method used in Single Party Testing (SPyT) context, as defined in
ISO/IEC 9646-2 [7], clause 11. This test method has been selected, because:
- it does not imply specific requirements to the Implementation Under Test (IUT);
- the upper Service Access Point (SAP) of the IUT cannot be directly observed;
- the variety of the possible TETRA implementations is a serious technical obstacle for the adoption
of a different ATM;
- this test method places minimum limitations in the realization of conformance testing.

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

SIST ETS 300 394-4-10 E1:2003
Page 10
ETS 300 394-4-10: June 1999
The selected test method is illustrated in figure 1.
Test system SUT
Upper
UT
TCP
layers
LT
GWCC- PDUs
GWCC
GWMM- PDUs
IUT
GWMM
PCO
ASPs
V+D MAC layer V+D MAC layer
TETRA physical layer and radio communication
Figure 1: Remote SPyT test method for TETRA DMO GWCC and GWMM protocols
4.1 Lower Tester (LT)
A LT is located in a remote TETRA test system. It controls and observes the behaviour of the IUT.
4.2 Upper Tester (UT)
There is no explicit UT in the remote test method, but the layers above inside the System Under Test
(SUT) are used implicitly for testing the GWMM and GWCC.
4.3 Test Co-ordination Procedures (TCP)
The implicit send events defined by the provider of an implementation in annex B serve the purpose of the
TCP. They are used as an input to the IUT communicating with the UT to initiate test events at the V+D
MLE layer.
4.4 Point of Control and Observation (PCO)
All test events at the PCO carrying service user data are specified in terms of GWCC and GWMM layer
PDUs. Only few Abstract Service Primitives (ASPs) are used for control or observation purposes.
4.5 Non-testable test purposes and implementation matters
The purpose of this ATS is to test the V+D interface of the gateway. The observable behaviour on the V+D
Air Interface (AI) in some cases is dependent on the behaviour on the DMO AI of the gateway. This
interface is not controlled by the test system, so it is assumed that the behaviour on the DMO AI is always
consistent with the requirement for this interface. However it also means that some of the test purposes
he following test purposes have been identified as being non-testable in the
become non-testable. T
selected test configuration, and therefore no abstract test cases are specified for the test purposes:
DMO_GATE_GWCC_CM_BV_TI_03 and DMO_GATE_GWCC_CM_BV_TI_06.
For test suite implementation, the upper layer may be realized as a MS-GW or as a simulation of its valid
behaviour, in order to test the dynamic behaviour of the gateway on the V+D AI.

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

SIST ETS 300 394-4-10 E1:2003
Page 11
ETS 300 394-4-10: June 1999
5 ATS conventions
This clause describes the conventions applied to define the two ATSs and gives the naming conventions
chosen for the different elements of the ATSs.
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.
5.1 Naming conventions
5.1.1 Declarations part
This subclause describes the naming conventions chosen for the elements of the ATS declarations part.
5.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 each
whole word included in the name is written in lowercase starting by an uppercase letter:
EXAMPLE: Priority_Level_Type simple type;
SSI_Type simple type;
ITSI_Type structured type.
In the case an abbreviation is included in the declaration name, there is an underscore ("_") before and/or
after it, separating it from the rest of the identifier. This rule with abbreviations apply to all the naming
conventions in the whole test suite.
5.1.1.2 Test suite operations definitions
The test suite operation identifiers are composed of strings in uppercase letters starting by the uppercase
string "TSO_". The different strings in the definition are separated with underscores.
EXAMPLE: TSO_UPLANE_IS_TRANSMITTING.
5.1.1.3 Test suite parameter declarations
The test suite parameter identifiers are composed of strings in uppercase letters starting by the uppercase
string "PIC_" or "PIX_" and separated by underscores.
If the test suite parameter references a PICS item, the prefix "PIC_" is used.
EXAMPLE 1: PIC_CIRCUIT_MODE_CALL.
If the test suite parameter references a PIXIT item, the prefix "PIX_" is used.
EXAMPLE 2: PIX_DM_MS_ITSI.
Complete names as defined in the specifications are used.
5.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 generally logical combinations of the PICS element definitions.

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

SIST ETS 300 394-4-10 E1:2003
Page 12
ETS 300 394-4-10: June 1999
5.1.1.5 Test suite constant declarations
The test suite constant identifiers are composed of strings in uppercase letters starting by the uppercase
string "TSC_".
EXAMPLE: TSC_MS_VITSI.
Complete names as defined in the specifications are used. However, in the parameters including a dot
character, the dot is replaced by an underscore.
5.1.1.6 Test suite variable declarations
The test suite variable identifiers are composed of string in lowercase letters starting by the lowercase
string "tsv_".
If the test suite variable represents a system parameter or value, the name defined in the specifications is
used. However, in the variables including a dot character, the dot is replaced by an underscore.
5.1.1.7 Test case variable declarations
The test case variable identifiers are composed of strings in lowercase letters starting by the lowercase
string "tcv_".
EXAMPLE: tcv_result.
5.1.1.8 PCO declarations
The point of control and observation identifiers are composed of three to six capital letters, beginning with
an "L", as there are only LTs.
EXAMPLE: LGWCC Represents a PCO on GWCC module for PDUs.
5.1.1.9 Timer declarations
Two kinds of timers can be distinguished:
1) standardized:
Those defined in the standard, e.g. T303, use the same name as in the standard, beginning with
capital "T".
As there is a tolerance margin accepted for these timers, two values are needed:
- the minimum value allowed, which will use the suffix "_Min";
- the maximum value allowed, which will use the suffix "_Max".
EXAMPLE 1: T303_Min, T303_Max.
2) non-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 lowercase letters with each word in the
following string starting with an uppercase letter.
EXAMPLE 2: T_IUT_Response;
T_NoResponse.
5.1.1.10 ASP type definitions
ASP definitions follow the specification in the ETS 300 396-5 [2] when a corresponding definition exists. If
not, a free name is used.

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

SIST ETS 300 394-4-10 E1:2003
Page 13
ETS 300 394-4-10: June 1999
5.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: U_SETUP_Type for the U-SETUP layer 3 PDU;
D_DISCONNECT_Type for the D-DISCONNECT layer 3 PDU.
5.1.1.12 Alias definitions
No alias definitions are used in the test suite.
5.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 name is separated from the
beginning with an underscore and is written in lowercase with each word starting with an uppercase letter.
Identifier names of elements concerning the same subject have equivalent names in the declaration and
the constraint part.
- Declaration part: D_CONNECT_Type;
- Constraint part: D_CONNECT_Direct.
The name of the modified constraint describes the particularity of the modified constraint:
EXAMPLE 1: - Declaration part: U_SETUP_Type;
- Constraint part: U_SETUP_GC_Direct.
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 starting with prefix "cpa_".
EXAMPLE 2: cpa_location_update_type.

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

SIST ETS 300 394-4-10 E1:2003
Page 14
ETS 300 394-4-10: June 1999
5.1.3 Dynamic part
This subclause describes the naming conventions chosen for the elements of the ATS dynamic part.
5.1.3.1 Test case identifier
The identifier of a TC is built according to the test purpose name, as in table 1.
Table 1: TC naming convention
DMO//////
= test suite type MSMS MS to MS (see 300 394-4-1)
MSGW MS connected to a gateway
GATE Gateway
REPx Repeater type x (see 300 394-4-4)
= functional entity in a layer DMCC Direct Mode Call Control (layer 3)
MAC Upper MAC (layer 2)
= test group letters such as: abbreviation of the group name (optional)
CM Circuit Mode (layer 3)
SDS Short Data Service (layer 3)
tt = Type of testing CA Capability Tests
BV Valid Behaviour Tests
BI Invalid Behaviour Tests
TI Timer expiry and counter mismatch tests
= test subgroup letters abbreviation of the subgroup name
(optional)
= sequential number 01-99 Test Purpose Number
5.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. PRE
for preamble, PST for postamble, CS for check state steps, LTS for local tree name and STP for general
step. The second string indicates the meaning of the step.
EXAMPLES: PRE_Idle_To_Active;
PST_DisconnectCall;
CS_Check_Idle.
5.1.3.3 Default identifier
Two default identifiers are used, namely OtherwiseFail.
5.2 TC and TP naming
There is a single name for both the TC identifiers and the TP identifiers.

---------------------- Page: 16 ----------------------

SIST ETS 300 394-4-10 E1:2003
Page 15
ETS 300 394-4-10: June 1999
Annex A (normative): ATS for TETRA DMO Gateway MAC layer
The ATS is written in TTCN according to ISO/IEC 9646-3 [8].
The ATS itself contains a test suite overview part which provides additional information and references.
A.1 The TTCN Graphical form (TTCN.GR)
The TTCN.GR representation of this ATS is contained in an Adobe Portable Document Format™ file
(dmo_gate.PDF contained in archive 3944ae1.ZIP) which accompanies the present document.
A.2 The TTCN Machine Processable form (TTCN.MP)
The TTCN.MP representation corresponding to this ATS is contained in an ASCII file (dmo_gate.MP
contained in archive 3944ae1.ZIP) which accompanies the present document.
NOTE: According to ISO/IEC 9646-3 [8], in case of a conflict in interpretation of the
operational semantics of TTCN.GR and TTCN.MP, the operational semantics of the
TTCN.GR representation takes precedence.

---------------------- Page: 17 ----------------------

SIST ETS 300 394-4-10 E1:2003
Page 16
ETS 300 394-4-10: June 1999
Annex B (normative): Partial PIXIT proforma for TETRA DMO Gateway MAC
layer protocol
Notwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants that
users of this ETS may freely reproduce the PIXIT proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PIXIT.
The PIXIT proforma is based on ISO/IEC 9646-5 [
...