ETSI ETS 300 394-5-3 ed.1 (1999-07)

Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 5: Security; Sub-part 3: Abstract Test Suite (ATS)

DE/TETRA-06009-5-3

Prizemni snopovni radio (TETRA) – Specifikacija za preskušanje skladnosti – 5. del: Varnost – 3. poddel: Abstraktni preskušalni niz (ATS)

General Information

• Status: Published
• Publication Date: 07-Jul-1999
• Technical Committee: TCCE 6 - TCCE Security
• Current Stage: 13 - TB decision to make document historical
• Due Date: 20-Mar-2003
• Completion Date: 20-Mar-2003
• Mandate: BC-T-344
• Ref Project: SIST ETS 300 394-5-3 E1:2003 - Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 5: Security; Sub-part 3: Abstract Test Suite (ATS)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 394-5-3 E1:2003
01-december-2003
Prizemni snopovni radio (TETRA) – Specifikacija za preskušanje skladnosti – 5.
del: Varnost – 3. poddel: Abstraktni preskušalni niz (ATS)
Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 5: Security;
Sub-part 3: Abstract Test Suite (ATS)
Ta slovenski standard je istoveten z: ETS 300 394-5-3 Edition 1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST ETS 300 394-5-3 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-5-3 E1:2003

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

SIST ETS 300 394-5-3 E1:2003
EUROPEAN ETS 300 394-5-3
TELECOMMUNICATION July 1999
STANDARD
Source: TETRA Reference: DE/TETRA-06009-5-3
ICS: 33.020
Key words: TETRA, V+D, security, testing, TTCN, ATS
Terrestrial Trunked Radio (TETRA);
Conformance testing specification;
Part 5: Security;
Sub-part 3: Abstract Test Suite (ATS)
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: [e-mail] - http://www.etsi.org
Tel.: [phone] - Fax: [phone]
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-5-3 E1:2003
Page 2
ETS 300 394-5-3: July 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-5-3 E1:2003
Page 3
ETS 300 394-5-3: July 1999
Contents
Foreword . 7
1 Scope. 9
2 Normative references . 9
3 Definitions and abbreviations. 10
3.1 TETRA definitions . 10
3.2 TETRA abbreviations . 10
3.3 ISO 9646 definitions . 10
3.4 ISO 9646 abbreviations. 11
4 Abstract Test Method (ATM). 11
4.1 Lower Tester (LT). 12
4.2 Upper Tester (UT) . 12
4.3 Test Co-ordination Procedures (TCP). 12
4.4 Point of Control and Observation (PCO) . 13
5 ATS conventions. 13
5.1 Naming conventions. 13
5.1.1 Declarations part. 13
5.1.1.1 Test suite type and structured type definitions. 13
5.1.1.2 Test suite operations definitions. 13
5.1.1.3 Test suite parameter declarations. 13
5.1.1.4 Test case selection expression definitions. 14
5.1.1.5 Test suite constant declarations. 14
5.1.1.6 Test suite variable declarations. 14
5.1.1.7 Test case variable declarations. 14
5.1.1.8 PCO declarations . 14
5.1.1.9 Timer declarations. 14
5.1.1.10 ASP type definitions . 15
5.1.1.11 PDU type definitions. 15
5.1.1.12 Alias definitions . 15
5.1.2 Constraints part. 15
5.1.3 Dynamic part. 16
5.1.3.1 Test case identifier . 16
5.1.3.2 Test step identifier. 16
5.1.3.3 Default identifier . 16
5.2 TC and TP mapping . 17
Annex A (normative): ATS for TETRA V+D security NWK layers and TETRA V+D security link layer 18
A.1 The TTCN Graphical form (TTCN.GR). 18
A.2 The TTCN Machine Processable form (TTCN.MP). 18
Annex B (normative): ATS for TETRA DMO security NWK layers and TETRA DMO security link
layer. 19
B.1 The TTCN Graphical form (TTCN.GR). 19
B.2 The TTCN Machine Processable form (TTCN.MP). 19
Annex C (normative): Partial PIXIT proforma for TETRA V+D security. 20
C.1 Identification summary. 20

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

SIST ETS 300 394-5-3 E1:2003
Page 4
ETS 300 394-5-3: July 1999
C.2 ATS summary .20
C.3 Test laboratory .20
C.4 Client identification .20
C.5 SUT .21
C.6 Protocol layer information.21
C.6.1 Protocol identification.21
C.6.2 IUT information .21
C.6.2.1 Implicit send events.21
C.6.2.2 Parameter values .22
Annex D (normative): Partial PIXIT proforma for TETRA DMO security.24
D.1 Identification summary .24
D.2 ATS summary .24
D.3 Test laboratory .24
D.4 Client identification .24
D.5 SUT .25
D.6 Protocol layer information.25
D.6.1 Protocol identification.25
D.6.2 IUT information .25
D.6.2.1 Implicit send events.25
D.6.2.2 Parameter values .26
Annex E (normative): Protocol Conformance Test Report (PCTR) proforma for TETRA V+D
security .27
E.1 Identification summary .27
E.1.1 Protocol conformance test report.27
E.1.2 IUT identification .27
E.1.3 Testing environment .27
E.1.4 Limits and reservation.27
E.1.5 Comments .28
E.2 IUT conformance status.28
E.3 Static conformance summary.28
E.4 Dynamic conformance summary.28
E.5 Static conformance review report.28
E.6 Test campaign report .29
E.7 Observations .32
Annex F (normative): Protocol Conformance Test Report (PCTR) proforma for TETRA DMO
security .33
F.1 Identification summary .33
F.1.1 Protocol conformance test report.33
F.1.2 IUT identification .33
F.1.3 Testing environment .33
F.1.4 Limits and reservation.33

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

SIST ETS 300 394-5-3 E1:2003
Page 5
ETS 300 394-5-3: July 1999
F.1.5 Comments. 34
F.2 IUT conformance status. 34
F.3 Static conformance summary . 34
F.4 Dynamic conformance summary . 34
F.5 Static conformance review report . 34
F.6 Test campaign report. 35
F.7 Observations. 36
Annex G (informative): Bibliography. 37
History . 38

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

SIST ETS 300 394-5-3 E1:2003
Page 6
ETS 300 394-5-3: July 1999
Blank page

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

SIST ETS 300 394-5-3 E1:2003
Page 7
ETS 300 394-5-3: July 1999
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio
(TETRA) Project of the European Telecommunications Standards Institute (ETSI).
Every ETS prepared by ETSI is a voluntary standard. This ETS contains text concerning conformance
testing of the equipment to which it relates. This text should be considered only as guidance and does not
make this ETS mandatory.
This ETS is a multi-part standard and will consist of the following parts:
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: 25 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: 9 ----------------------

SIST ETS 300 394-5-3 E1:2003
Page 8
ETS 300 394-5-3: July 1999
Blank page

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

SIST ETS 300 394-5-3 E1:2003
Page 9
ETS 300 394-5-3: July 1999
1 Scope
This ETS contains two Abstract Test Suites (ATSs) to test the TETRA security V+D and DMO protocols.
The protocols are specified, respectively, in ETS 300 392-7 [2] and ETS 300 396-6 [3]. The Test Suite
Structure (TSS) and Test Purposes (TPs) for these ATSs are defined in ETS 300 394-5-2 [1].
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 [4], ISO/IEC 9646-2 [5],
ISO/IEC 9646-3 [6] and ISO/IEC 9646-5 [7], as well as the ETSI rules for conformance testing,
ETS 300 406 [9] and ETR 141 [10], are used as a basis for the test methodology.
Annex A and B provide the Tree and Tabular Combined Notation (TTCN) part of these ATSs.
Annex C and D provides the Partial Protocol Implementation eXtra Information for Testing (PIXIT)
Proforma of these ATSs.
Annex E and F provides the Protocol Conformance Test Report (PCTR) Proforma of these ATSs.
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 394-5-2: "Terrestrial Trunked Radio (TETRA); Conformance testing
specification; Part 5: Security; Sub-part 2: Protocol testing specification for
TETRA security".
[2] ETS 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 7: Security".
[3] ETS 300 396-6: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation
(DMO); Part 6: Security".
[4] ISO/IEC 9646-1 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1:
General Concepts". (See also CCITT Recommendation X.290 (1991))
[5] 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)).
[6] ISO/IEC 9646-3 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 3:
The Tree and Tabular Combined Notation (TTCN)". (See also CCITT
Recommendation X.292 (1992)).
[7] 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)).
[8] ISO/IEC 9646-6 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 6:
Protocol profile test specification".

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

SIST ETS 300 394-5-3 E1:2003
Page 10
ETS 300 394-5-3: July 1999
[9] ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and
profile conformance testing specifications; Standardization methodology".
[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 394-5 [1] apply.
3.2 TETRA abbreviations
For the purposes of this ETS the following TETRA abbreviations apply:
CC Call Control
CMCE Circuit Mode Control Entity
DM Direct Mode
DMO Direct Mode Operation
MAC Medium Access Control
MLE Mobile Link Entity
MM Mobility Management
MS Mobile Station
PC Protocol Control
SCLNP Specific ConnectionLess Network Protocol
SDS Short Data Service
SDU Service Data Unit
3.3 ISO 9646 definitions
For the purposes of this ETS the following ISO/IEC 9646-1 [4] 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 [6] definitions apply:
TTCN.GR
TTCN.MP
For the purposes of this ETS the following ISO/IEC 9646-5 [7] definitions apply:
Protocol Conformance Test Report (PCTR)
PCTR proforma

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

SIST ETS 300 394-5-3 E1:2003
Page 11
ETS 300 394-5-3: July 1999
3.4 ISO 9646 abbreviations
For the purposes of this ETS the following ISO/IEC 9646-1 [4] abbreviations apply:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
IUT Implementation Under Test
LT Lower Tester
NWK Network Layer
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 [7] abbreviations apply:
PCTR Protocol Conformance Test Report
4 Abstract Test Method (ATM)
This clause describes the ATM used for testing the V+D and DM security protocol. It is the embedded
variant of the remote test method used in Single Party Testing (SPyT) context, as defined in
ISO/IEC 9646-2 [2], clause 11. This test method has been selected, because:
- this test method implies no specific requirements from 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 realisation of conformance testing.
Operations at NetWorK (NWK) layer in the V+D and DM security protocol (for example authentication)
affect the content of the link layer PDUs (i.e. MAC PDUs). Therefore link layer test cases have been
defined to observe the status of the MAC header when conveying NWK layer information elements.

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

SIST ETS 300 394-5-3 E1:2003
Page 12
ETS 300 394-5-3: July 1999
The selected test method used to test the NWK layer is illustrated in figure 1.
Test system SUT
Upper
UT
TCP
layers
LT
TETRA
NWK- PDUs
NWK
IUT
PCO
ASPs
TETRA LLC layer TETRA LLC layer
TETRA MAC layer TETRA MAC layer
TETRA physical layer and radio communication
Figure 1: Remote SPyT test method for TETRA Security NWK layer
The selected test method used to test the DM link layer is illustrated in figure 2.
SUT
Test system
Upper
UT
TCP
layers
LT
LINK-PDUs
TETRA
LINK IUT
PCO
ASPs
TETRA physical layer and radio communication
Figure 2: Remote SPyT test method for V+D TETRA Security link layer
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 TETRA NWK layer or LINK layer and the layers
above inside the System Under Test (SUT) are used implicitly for testing the NWK layer or LINK layer.
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 NWK and
LINK layers.

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

SIST ETS 300 394-5-3 E1:2003
Page 13
ETS 300 394-5-3: July 1999
4.4 Point of Control and Observation (PCO)
The PCOs for the V+D NWK layer testing are located inside the NWK protocols. Two different test
configurations are assumed. One for testing the upper protocols in NWK layer Mobility Management (MM)
and another one for invoking Mobile Link Entity (MLE). In the first case PCOs for upper protocols are to be
used with test system providing the underlying MLE functionality and in the latter case the PCO inside
MLE protocol is to be used. Additionally some Abstract Service Primitives (ASPs) are defined for control
and observation purposes. Two other PCOs were defined to test the state of the IUT using the Circuit
Mode Control Entity (CMCE) protocol: one to use the call control and an other one to use the Short Data
Service (SDS).
The PCO defined for the DM link layer testing is located in the link protocol for testing the MAC header
PDUs.
The PCO defined for testing the DM security protocol is located in the NWK layer inside the Short Data
Service protocol.
5 ATS conventions
This clause describes the conventions applied to define the ATSs and gives the naming conventions
chosen for the different elements of the ATSs.
The ATSs conventions are intended to give a better understanding of the ATSs but they describe also the
conventions made for the development of the ATSs, thus for any later maintenance purposes or further
development of the ATSs, 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: CellIdentifierType 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_ENCRYPT_SDU
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.

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

SIST ETS 300 394-5-3 E1:2003
Page 14
ETS 300 394-5-3: July 1999
If the test suite parameter references a PICS item, the prefix "PIC_" is used.
EXAMPLE 1: PIC_OTAR_CCK_SUPP
If the test suite parameter references a PIXIT item, the prefix "PIX_" is used.
EXAMPLE 2: PIX_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 test suite parameter definitions.
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_TETRA_VERSION
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_".
EXAMPLE: tsv_llc_ul_sdu_nmbr
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_".
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: LMM Represents a PCO on NWK interface for call control PDUs as
LT in the test equipment.
5.1.1.9 Timer declarations
Two kinds of timers can be distinguished:
1) standardized:
Those defined in the standard, e.g. T.316, use the same name as in the standard, beginning with a
capital "T", except that the dot is replaced by an underscore.
As there is a tolerance margin accepted for these timers, two values are needed:
- the maximum value allowed, which will use the suffix "_Max";
- the minimum value allowed, which will use the suffix "_Min";
EXAMPLE 1: T316_Max

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

SIST ETS 300 394-5-3 E1:2003
Page 15
ETS 300 394-5-3: July 1999
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 392-7 [2] or ETS 300 396-6 [3] when a
corresponding definition exists. If not, a free name is used.
EXAMPLE: MLE_ACTIVATE_confirm_RegistrationReq
RESET_MS.
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 1: D_ENABLE for the D-STATUS layer 3 PDU reception;
U_AUTHENTICATION_DEMAND for the DISCONNECT layer 3 PDU transmission.
Where the message is a composite word, an und
...