SIST ETS 300 394-2-3:1999

Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 2: Protocol testing specification for Voice plus Data (V+D); Sub-part 3: Abstract Test Suite (ATS) for Logical Link Control (LLC)

Protocol conformance testing (TTCN) for mobile & base stations Voice & Data (V+D) and for Packet Data Optimised (PDO). 2/95 Item split into: Part 2: Protocol conformance testing (V+D) Part 3: Protocol conformance testing (PDO)

Prizemni snopovni radio (TETRA) - Specifikacija za preskušanje skladnosti - 2. del: Specifikacija preskuševalnega protokola za govor in podatke (V+D) - 2-3 del: Abstraktni preskušalni niz (ATS) za krmiljenje logičnih povezav (LLC)

General Information

• Status: Published
• Publication Date: 30-Jun-1999
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: RES - Radio equipment and systems
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jul-1999
• Due Date: 01-Jul-1999
• Completion Date: 01-Jul-1999
• Mandate: BC-T-344
• Ref Project: ETSI ETS 300 394-2-3 ed.1 (1998-02) - Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 2: Protocol testing specification for Voice plus Data (V+D); Sub-part 3: Abstract Test Suite (ATS) for Logical Link Control (LLC)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 394-2-3:1999
01-julij-1999
3UL]HPQLVQRSRYQLUDGLR7(75$6SHFLILNDFLMD]DSUHVNXãDQMHVNODGQRVWLGHO
6SHFLILNDFLMDSUHVNXãHYDOQHJDSURWRNROD]DJRYRULQSRGDWNH9'GHO
$EVWUDNWQLSUHVNXãDOQLQL]$76]DNUPLOMHQMHORJLþQLKSRYH]DY//&
Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 2: Protocol
testing specification for Voice plus Data (V+D); Sub-part 3: Abstract Test Suite (ATS) for
Logical Link Control (LLC)
Ta slovenski standard je istoveten z: ETS 300 394-2-3 Edition 1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST ETS 300 394-2-3:1999 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 394-2-3:1999

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

SIST ETS 300 394-2-3:1999
EUROPEAN ETS 300 394-2-3
TELECOMMUNICATION February 1998
STANDARD
Source: TETRA Reference: DE/RES-06009-2-3
ICS: 33.020
Key words: TETRA, V+D, protocol, testing, voice, data, ATS
Terrestrial Trunked Radio (TETRA);
Conformance testing specification;
Part 2: Protocol testing specification for Voice plus Data (V+D);
Sub-part 3: Abstract Test Suite (ATS) for
Logical Link Control (LLC)
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: [e-mail]
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 1998. All rights reserved.

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

SIST ETS 300 394-2-3:1999
Page 2
ETS 300 394-2-3: 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: 4 ----------------------

SIST ETS 300 394-2-3:1999
Page 3
ETS 300 394-2-3: February 1998
Contents
Foreword .5
1 Scope .7
2 Normative references.7
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 .8
4 Abstract Test Method (ATM).9
4.1 Lower Tester (LT) .9
4.2 Upper Tester (UT).9
4.3 Test Co-ordination Procedures (TCP) .10
4.4 Point of Control and Observation (PCO) .10
5 ATS conventions .10
5.1 Naming conventions .10
5.1.1 Declarations part .10
5.1.1.1 Test suite type and structured type definitions .10
5.1.1.2 Test suite operations definitions .10
5.1.1.3 Test suite parameter declarations .10
5.1.1.4 Test case selection expression definitions .11
5.1.1.5 Test suite constant declarations.11
5.1.1.6 Test suite variable declarations .11
5.1.1.7 Test case variable declarations .11
5.1.1.8 PCO declarations.11
5.1.1.9 Timer declarations.11
5.1.1.10 ASP type definitions.12
5.1.1.11 PDU type definitions .12
5.1.1.12 Alias definitions.12
5.1.2 Constraints part.12
5.1.3 Dynamic part .12
5.1.3.1 Test case identifier .13
5.1.3.2 Test step identifier .13
5.1.3.3 Default identifier.13
5.2 Implementation conventions .13
5.3 TC and TP mapping.13
Annex A (normative): ATS for TETRA LLC.14
A.1 The TTCN Graphical form (TTCN.GR) .14
A.2 The TTCN Machine Processable form (TTCN.MP) .14
Annex B (normative): Partial PIXIT proforma for TETRA LLC.15
B.1 Identification summary .15
B.2 ATS summary .15
B.3 Test laboratory .15
B.4 Client identification .15

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

SIST ETS 300 394-2-3:1999
Page 4
ETS 300 394-2-3: February 1998
B.5 SUT. 16
B.6 Protocol layer information. 16
B.6.1 Protocol identification . 16
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 LLC . 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-2-3:1999
Page 5
ETS 300 394-2-3: February 1998
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 will consist of two parts with various sub-parts:
Part 1: "Radio";
Part 2: "Protocol testing specification for Voice plus Data (V+D)".
Transposition dates
Date of adoption of this ETS: 6 February 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: 7 ----------------------

SIST ETS 300 394-2-3:1999
Page 6
ETS 300 394-2-3: February 1998
Blank page

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

SIST ETS 300 394-2-3:1999
Page 7
ETS 300 394-2-3: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) to test the
TETRA Logical Link Control (LLC) layer. The LLC protocol is specified in ETS 300 392-2 [2]. The Test
Suite Structure (TSS) and Test Purposes (TPs) for this ATS are defined in ETS 300 394-2-1 [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 [3], ISO/IEC 9646-2 [4],
ISO/IEC 9646-3 [5] and ISO/IEC 9646-5 [6], as well as the ETSI rules for conformance testing,
ETS 300 406 [8] and ETR 141 (see annex D), are used as a basis for the test methodology.
Annex A provides the Tree and Tabular Combined Notation (TTCN) part of this ATS.
Annex B provides the Partial Protocol Implementation eXtra Information for Testing (PIXIT) Proforma of
this ATS.
Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of this ATS.
2 Normative references
This ETS incorporates by dated 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-2-1: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA) system; Conformance testing specification; Part 2:
Protocol testing specification for Voice plus Data (V+D); Part 2-1: Test suite
structure and test purposes".
[2] ETS 300 392-2: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA) system; Voice plus Data (V+D); Part 2: Air Interface
(AI)".
[3] 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)).
[4] 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)).
[5] 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)).
[6] 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)).
[7] ISO/IEC 9646-6 (1991): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 6:
Protocol profile test specification".
[8] ETS 300 406: "Methods for Testing and Specification (MTS); Protocol and
profile conformance testing specifications; Standardization methodology".

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

SIST ETS 300 394-2-3:1999
Page 8
ETS 300 394-2-3: February 1998
3 Definitions and abbreviations
3.1 TETRA definitions
For the purposes of this ETS, the definitions given in ETS 300 392-2 [2] apply.
3.2 TETRA abbreviations
For the purposes of this ETS, the following TETRA abbreviations apply:
LLC Logical Link Control
MAC Medium Access Control
MS Mobile Station
SDU Service Data Unit
3.3 ISO 9646 definitions
For the purposes of this ETS, the following ISO/IEC 9646-1 [3] 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 [5] definitions apply:
TTCN.GR
TTCN.MP
For the purposes of this ETS, the following ISO/IEC 9646-5 [6] definitions apply:
Protocol Conformance Test Report (PCTR)
PCTR proforma
3.4 ISO 9646 abbreviations
For the purposes of this ETS, the following ISO/IEC 9646-1 [3] 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

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

SIST ETS 300 394-2-3:1999
Page 9
ETS 300 394-2-3: February 1998
TC Test Case
TP Test Purpose
TSS Test Suite Structure
TTCN Tree and Tabular Combined Notation
UT Upper Tester
For the purposes of this ETS, the following ISO/IEC 9646-5 [6] abbreviations apply:
PCTR Protocol Conformance Test Report
4 Abstract Test Method (ATM)
This clause describes the ATM used for testing the TETRA LLC 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 [4], 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 realization of conformance testing.
The selected test method is illustrated in figure 1.
SUT
Test system
Upper
TCP
layers
LT
UT
NWK- PDUs
TETRA
NW K
LLC- PDUs
TETRA
IUT
LLC
PCO
ASPs
TETRA MAC layer TETRA MAC layer
TETRA physical layer and radio communication
Figure 1: Remote SPyT test method for TETRA LLC
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 Network (NWK) layer and the layers
above inside the System Under Test (SUT) are used implicitly for testing the LLC layer.

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

SIST ETS 300 394-2-3:1999
Page 10
ETS 300 394-2-3: February 1998
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 LLC
layer.
In addition to the implicit send events, some NWK layer Protocol Data Units (PDUs) sent inside the LLC
Service Data Units (SDUs) to the IUT are used for test co-ordination purposes. These PDUs, as sent to
the IUT, should produce NWK layer responses, which then further on should cause LLC PDU
transmissions by the IUT that are observable by the LT.
4.4 Point of Control and Observation (PCO)
The PCO for LLC layer testing is located inside the LLC protocol, i.e. between the different LLC protocol
subentities and the formatter subentity. All test events at the PCO are specified in terms of LLC layer
PDUs. The mapping of the LLC PDUs to possible Medium Access Control (MAC) layer service primitives
is left to the test implementation.
5 ATS conventions
This clause describes the conventions applied to define the ATS and gives the naming conventions
chosen for the different elements of the ATS.
The ATS conventions are intended to give a better understanding of the ATS but they describe also the
conventions made for the development of the ATS, thus for any later maintenance purposes or further
development of the ATS, the conventions described in this clause shall be considered.
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: DisconnectionReportType simple type
FCS_Type simple type
AcknowledgementBlockType 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_CALCULATE_FCS
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: PIC_BL_UNACKNOWLEDGED_DATA_TRANSMISSION

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

SIST ETS 300 394-2-3:1999
Page 11
ETS 300 394-2-3: February 1998
If the test suite parameter references a PIXIT item, the prefix "PIX_" is used.
EXAMPLE: PIX_ALA_ACCEPTABLE_QOS
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_BL_SDU_NUMBER_RANGE
Complete names as defined in the protocol specification 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_ns
If the test suite variable represents a system parameter or value, the name defined in the protocol
specification 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_fcs
5.1.1.8 PCO declarations
The only point of control and observation is named LLLC, with "L" referring to LT.
5.1.1.9 Timer declarations
Two kinds of timers can be distinguished:
1) standardized:
Those defined in the standard, e.g. T.251, 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: T_251_Min, T_251_Max

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

SIST ETS 300 394-2-3:1999
Page 12
ETS 300 394-2-3: February 1998
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_UserResponse
5.1.1.10 ASP type definitions
No ASP definitions are used in the ATS.
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: BL_DATA for the BL-DATA layer 2 PDU reception and transmission.
Where the message is a composite word, an underscore character appears in the string.
EXAMPLE 2: AL_FINAL_AR is the AL-FINAL-AR layer 2 message.
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: BL_DATA
- Constraint part: D_BL_DATA_NoResponseRequired
The constraints used in uplink direction, i.e. received by the test system, and downlink direction, i.e. sent
by the test system, are distinguished with prefixes U_ and D_ respectively.
When 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: D_AL_DISC (cpa_LinkNumber: LinkNumberType)
5.1.3 Dynamic part
This subclause describes the naming conventions chosen for the elements of the ATS dynamic part.

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

SIST ETS 300 394-2-3:1999
Page 13
ETS 300 394-2-3: February 1998
5.1.3.1 Test case identifier
The identifier of a TC is built according to table 1.
Table 1: TC naming convention
___
= test suite LLC Logical Link Control layer
x = Type of testing CA Capability tests
BV Valid Behaviour tests
BI Invalid Behaviour tests
TI Timer expiry and counter mismatch tests
s = test subgroup as defined in the test suite structure
(as many subgroups as required)
  = sequential number (01-99) TC 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 and LTS for local tree name. The second string indicates the meaning of the step. The
implicit send events in the ATS are only used in test steps with prefix IMP.
EXAMPLES: PRE_IUT_Reset
LTS_ReceiveNextSegment
IMP_ALA_ConnectionSetup
5.1.3.3 Default identifier
Only one default identifier is used, namely: OtherwiseFail.
5.2 Implementation conventions
Fully functional underlying MAC protocol is assumed from the test system.
The LLC PDUs are assumed to be mapped to MAC layer service primitives in the test system
implementation and therefore are not part of the ATS.
All PDUs sent to the IUT should be sent using valid individual address, including the BL-UDATA PDUs.
The test system is assumed to be configured so, that it sends valid D-MLE-SYNC and D-MLE-SYSINFO
PDUs to the IUT. The BS service details element in the D-MLE-SYSINFO PDU should require registration
on the cell, so that the IUT starts registration after power up as defined in the ATS in preamble
PRE_RESET_AND_REGISTER. Also, the advanced link support in the same element is required to be
set on for the advanced link test cases. Other elements are to be configured according to the capabilities
of the IUT.
5.3 TC and TP mapping
There is a one-to-one mapping between the TC identifiers and the TP identifiers. The correspondence
rule is given by the following examples:
TP identifier TC identifier
TP/LLC/CA/BA-01 LLC_CA_BA_01
TP/LLC/BV/AA/LR-02 LLC_BV_AA_LR_02
TP/LLC/TI/AA-01 LLC_TI_AA_01

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

SIST ETS 300 394-2-3:1999
Page 14
ETS 300 394-2-3: February 1998
Annex A (normative): ATS for TETRA LLC
The ATS is written in TTCN according to ISO/IEC 9646-3 [5].
As the ATS was developed on a separate TTCN tool the TTCN tables are not completely referenced in
the contents table of this ETS. 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 a Postscript file (LLC.PS contained in archive
39423e1.LZH) which accompanies this ETS.
A.2 The TTCN Machine Processable form (TTCN.MP)
The TTCN.MP representation corresponding to this ATS is contained in an ASCII text file (LLC.MP
contained in archive 39423e1.LZH) which accompanies this ETS.
NOTE: According to ISO/IEC 9646-3 [5], 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: 16 ----------------------

SIST ETS 300 394-2-3:1999
Page 15
ETS 300 394-2-3: February 1998
Annex B (normative): Partial PIXIT proforma for TETRA LLC
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-6 [7]. Any additional information needed can be found in
this international standard document.
B.1 Identification summary
Table B.1
PIXIT number:
Test laboratory name:
Date of issue:
Issued to:
B.2 ATS summary
Table B.2
Protocol specification: ETS 300 392-2
Protocol to be tested:
ATS specification: ETS 300 394-2-3
Abstract test method: Remote test method, embedded variant
B.3 Test laboratory
Table B.3
Test laboratory identification:
Test laboratory manager:
Means of testing:
SAP address:
B.4 Client identification
Table B
...

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.//&Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 2: Protocol testing specification for Voice plus Data (V+D); Sub-part 3: Abstract Test Suite (ATS) for Logical Link Control (LLC)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)33.020Telekomunikacije na splošnoTelecommunications in generalICS:Ta slovenski standard je istoveten z:ETS 300 394-2-3 E13SIST ETS 300 394-2-3:1999en01-PDM-19993SIST ETS 300 394-2-3:1999SLOVENSKI
STANDARD



SIST ETS 300 394-2-3:1999



EUROPEANETS 300 394-2-3TELECOMMUNICATIONFebruary 1998STANDARDSource: TETRAReference: DE/RES-06009-2-3ICS:33.020Key words:TETRA, V+D, protocol, testing, voice, data, ATSTerrestrial Trunked Radio (TETRA);Conformance testing specification;Part 2: Protocol testing specification for Voice plus Data (V+D);Sub-part 3: Abstract Test Suite (ATS) forLogical Link Control (LLC)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998. All rights reserved.SIST ETS 300 394-2-3:1999



Page 2ETS 300 394-2-3: February 1998Whilst 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.SIST ETS 300 394-2-3:1999



Page 3ETS 300 394-2-3: February 1998ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1TETRA definitions.83.2TETRA abbreviations.83.3ISO 9646 definitions.83.4ISO 9646 abbreviations.84Abstract Test Method (ATM).94.1Lower Tester (LT).94.2Upper Tester (UT).94.3Test Co-ordination Procedures (TCP).104.4Point of Control and Observation (PCO).105ATS conventions.105.1Naming conventions.105.1.1Declarations part.105.1.1.1Test suite type and structured type definitions.105.1.1.2Test suite operations definitions.105.1.1.3Test suite parameter declarations.105.1.1.4Test case selection expression definitions.115.1.1.5Test suite constant declarations.115.1.1.6Test suite variable declarations.115.1.1.7Test case variable declarations.115.1.1.8PCO declarations.115.1.1.9Timer declarations.115.1.1.10ASP type definitions.125.1.1.11PDU type definitions.125.1.1.12Alias definitions.125.1.2Constraints part.125.1.3Dynamic part.125.1.3.1Test case identifier.135.1.3.2Test step identifier.135.1.3.3Default identifier.135.2Implementation conventions.135.3TC and TP mapping.13Annex A (normative):ATS for TETRA LLC.14A.1The TTCN Graphical form (TTCN.GR).14A.2The TTCN Machine Processable form (TTCN.MP).14Annex B (normative):Partial PIXIT proforma for TETRA LLC.15B.1Identification summary.15B.2ATS summary.15B.3Test laboratory.15B.4Client identification.15SIST ETS 300 394-2-3:1999



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



Page 5ETS 300 394-2-3: February 1998ForewordThis 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 conformancetesting of the equipment to which it relates. This text should be considered only as guidance and does notmake this ETS mandatory.This ETS will consist of two parts with various sub-parts:Part 1:"Radio";Part 2:"Protocol testing specification for Voice plus Data (V+D)".Transposition datesDate of adoption of this ETS:6 February 1998Date of latest announcement of this ETS (doa):31 May 1998Date of latest publication of new National Standardor endorsement of this ETS (dop/e):30 November 1998Date of withdrawal of any conflicting National Standard (dow):30 November 1998SIST ETS 300 394-2-3:1999



Page 6ETS 300 394-2-3: February 1998Blank pageSIST ETS 300 394-2-3:1999



Page 7ETS 300 394-2-3: February 19981ScopeThis European Telecommunication Standard (ETS) contains the Abstract Test Suite (ATS) to test theTETRA Logical Link Control (LLC) layer. The LLC protocol is specified in ETS 300 392-2 [2]. The TestSuite Structure (TSS) and Test Purposes (TPs) for this ATS are defined in ETS 300 394-2-1 [1].The objective of this test specification is to provide a basis for approval tests for TETRA equipment givinga 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 [3], ISO/IEC 9646-2 [4],ISO/IEC 9646-3 [5] and ISO/IEC 9646-5 [6], as well as the ETSI rules for conformance testing,ETS 300 406 [8] and ETR 141 (see annex D), are used as a basis for the test methodology.Annex A provides the Tree and Tabular Combined Notation (TTCN) part of this ATS.Annex B provides the Partial Protocol Implementation eXtra Information for Testing (PIXIT) Proforma ofthis ATS.Annex C provides the Protocol Conformance Test Report (PCTR) Proforma of this ATS.2Normative referencesThis ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this ETS only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]ETS 300 394-2-1: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA) system; Conformance testing specification; Part 2:Protocol testing specification for Voice plus Data (V+D); Part 2-1: Test suitestructure and test purposes".[2]ETS 300 392-2: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA) system; Voice plus Data (V+D); Part 2: Air Interface(AI)".[3]ISO/IEC 9646-1 (1991): "Information technology - Open SystemsInterconnection - Conformance Testing Methodology and Framework - Part 1:General Concepts" (see also CCITT Recommendation X.290 (1991)).[4]ISO/IEC 9646-2 (1991): "Information technology - Open SystemsInterconnection - Conformance Testing Methodology and Framework - Part 2:Abstract Test Suite Specification" (see also CCITT Recommendation X.291(1991)).[5]ISO/IEC 9646-3 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 3:The tree and tabular combined notation" (see also CCITT RecommendationX.292 (1992)).[6]ISO/IEC 9646-5 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 5:Requirements on test laboratories and clients for the conformance assessmentprocess" (see also CCITT Recommendation X.292 (1992)).[7]ISO/IEC 9646-6 (1991): "Information technology - Open SystemsInterconnection - Conformance testing methodology and framework - Part 6:Protocol profile test specification".[8]ETS 300 406: "Methods for Testing and Specification (MTS); Protocol andprofile conformance testing specifications; Standardization methodology".SIST ETS 300 394-2-3:1999



Page 8ETS 300 394-2-3: February 19983Definitions and abbreviations3.1TETRA definitionsFor the purposes of this ETS, the definitions given in ETS 300 392-2 [2] apply.3.2TETRA abbreviationsFor the purposes of this ETS, the following TETRA abbreviations apply:LLCLogical Link ControlMACMedium Access ControlMSMobile StationSDUService Data Unit3.3ISO 9646 definitionsFor the purposes of this ETS, the following ISO/IEC 9646-1 [3] 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 proformaPIXIT proformaPoint 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 [5] definitions apply:TTCN.GRTTCN.MPFor the purposes of this ETS, the following ISO/IEC 9646-5 [6] definitions apply:Protocol Conformance Test Report (PCTR)PCTR proforma3.4ISO 9646 abbreviationsFor the purposes of this ETS, the following ISO/IEC 9646-1 [3] abbreviations apply:ASPAbstract Service PrimitiveATMAbstract Test MethodATSAbstract Test SuiteIUTImplementation Under TestLTLower TesterNWKNetwork LayerPCOPoint of Control and ObservationPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementsPIXITProtocol Implementation eXtra Information for TestingSAPService Access PointSPyTSingle Party TestingSUTSystem Under TestSIST ETS 300 394-2-3:1999



Page 9ETS 300 394-2-3: February 1998TCTest CaseTPTest PurposeTSSTest Suite StructureTTCNTree and Tabular Combined NotationUTUpper TesterFor the purposes of this ETS, the following ISO/IEC 9646-5 [6] abbreviations apply:PCTRProtocol Conformance Test Report4Abstract Test Method (ATM)This clause describes the ATM used for testing the TETRA LLC protocol. It is the embedded variant of theremote test method used in Single Party Testing (SPyT) context, as defined in ISO/IEC 9646-2 [4], clause11. 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 adoptionof a different ATM;-this test method places minimum limitations in the realization of conformance testing.The selected test method is illustrated in figure 1.Test systemSUTUpperlayersIUTNWK- PDUsTETRA physical layer and radio communicationLLC- PDUsUTPCOASPsTETRANWK TETRA LLCTETRA MAC layerTETRA MAC layerTCP LT
Figure 1: Remote SPyT test method for TETRA LLC4.1Lower Tester (LT)A LT is located in a remote TETRA test system. It controls and observes the behaviour of the IUT.4.2Upper Tester (UT)There is no explicit UT in the remote test method, but the TETRA Network (NWK) layer and the layersabove inside the System Under Test (SUT) are used implicitly for testing the LLC layer.SIST ETS 300 394-2-3:1999



Page 10ETS 300 394-2-3: February 19984.3Test Co-ordination Procedures (TCP)The implicit send events defined by the provider of an implementation in annex B serve the purpose of theTCP. They are used as an input to the IUT communicating with the UT to initiate test events at the LLClayer.In addition to the implicit send events, some NWK layer Protocol Data Units (PDUs) sent inside the LLCService Data Units (SDUs) to the IUT are used for test co-ordination purposes. These PDUs, as sent tothe IUT, should produce NWK layer responses, which then further on should cause LLC PDUtransmissions by the IUT that are observable by the LT.4.4Point of Control and Observation (PCO)The PCO for LLC layer testing is located inside the LLC protocol, i.e. between the different LLC protocolsubentities and the formatter subentity. All test events at the PCO are specified in terms of LLC layerPDUs. The mapping of the LLC PDUs to possible Medium Access Control (MAC) layer service primitivesis left to the test implementation.5ATS conventionsThis clause describes the conventions applied to define the ATS and gives the naming conventionschosen for the different elements of the ATS.The ATS conventions are intended to give a better understanding of the ATS but they describe also theconventions made for the development of the ATS, thus for any later maintenance purposes or furtherdevelopment of the ATS, the conventions described in this clause shall be considered.5.1Naming conventions5.1.1Declarations partThis subclause describes the naming conventions chosen for the elements of the ATS declarations part.5.1.1.1Test suite type and structured type definitionsThe test suite type and test suite structured type identifiers describe the information elements, and eachwhole word included in the name is written in lowercase starting by an uppercase letter:EXAMPLE:DisconnectionReportTypesimple typeFCS_Typesimple typeAcknowledgementBlockTypestructured typeIn the case an abbreviation is included in the declaration name, there is an underscore ("_") before and/orafter it, separating it from the rest of the identifier. This rule with abbreviations apply to all the namingconventions in the whole test suite.5.1.1.2Test suite operations definitionsThe test suite operation identifiers are composed of strings in uppercase letters starting by the uppercasestring "TSO_". The different strings in the definition are separated with underscores.EXAMPLE:TSO_CALCULATE_FCS5.1.1.3Test suite parameter declarationsThe test suite parameter identifiers are composed of strings in uppercase letters starting by the uppercasestring "PIC_" or "PIX_" and separated by underscores.If the test suite parameter references a PICS item, the prefix "PIC_" is used.EXAMPLE:PIC_BL_UNACKNOWLEDGED_DATA_TRANSMISSIONSIST ETS 300 394-2-3:1999



Page 11ETS 300 394-2-3: February 1998If the test suite parameter references a PIXIT item, the prefix "PIX_" is used.EXAMPLE:PIX_ALA_ACCEPTABLE_QOSComplete names as defined in the specifications are used.5.1.1.4Test case selection expression definitionsThe naming conventions for the test case selection expression definitions use free text starting with anuppercase letter. The name of the expression shall explain clearly the selection rule. The test caseselection expressions are generally logical combinations of the test suite parameter definitions.5.1.1.5Test suite constant declarationsThe test suite constant identifiers are composed of strings in uppercase letters starting by the uppercasestring "TSC_".EXAMPLE:TSC_BL_SDU_NUMBER_RANGEComplete names as defined in the protocol specification are used. However, in the parameters including adot character, the dot is replaced by an underscore.5.1.1.6Test suite variable declarationsThe test suite variable identifiers are composed of string in lowercase letters starting by the lowercasestring "tsv_".EXAMPLE:tsv_nsIf the test suite variable represents a system parameter or value, the name defined in the protocolspecification is used. However, in the variables including a dot character, the dot is replaced by anunderscore.5.1.1.7Test case variable declarationsThe test case variable identifiers are composed of strings in lowercase letters starting by the lowercasestring "tcv_".EXAMPLE:tcv_fcs5.1.1.8PCO declarationsThe only point of control and observation is named LLLC, with "L" referring to LT.5.1.1.9Timer declarationsTwo kinds of timers can be distinguished:1)standardized:Those defined in the standard, e.g. T.251, use the same name as in the standard, beginning witha 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:T_251_Min, T_251_MaxSIST ETS 300 394-2-3:1999



Page 12ETS 300 394-2-3: February 19982)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 inthe following string starting with an uppercase letter.EXAMPLE 2:T_IUT_ResponseT_UserResponse5.1.1.10ASP type definitionsNo ASP definitions are used in the ATS.5.1.1.11PDU type definitionsThe identifier of a PDU is given in a string in uppercase letters, which represents the layer message.EXAMPLE 1:BL_DATAfor the BL-DATA layer 2 PDU reception and transmission.Where the message is a composite word, an underscore character appears in the string.EXAMPLE 2:AL_FINAL_AR is the AL-FINAL-AR layer 2 message.5.1.1.12Alias definitionsNo alias definitions are used in the test suite.5.1.2Constraints partThis 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 thebeginning 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 andthe constraint part:-Declaration part:BL_DATA-Constraint part:D_BL_DATA_NoResponseRequiredThe constraints used in uplink direction, i.e. received by the test system, and downlink direction, i.e. sentby the test system, are distinguished with prefixes U_ and D_ respectively.When formal parameter lists are used, the variable names are written in lowercase. The variable name isthe same as the name of the element it is representing starting with prefix "cpa_".EXAMPLE:D_AL_DISC (cpa_LinkNumber: LinkNumberType)5.1.3Dynamic partThis subclause describes the naming conventions chosen for the elements of the ATS dynamic part.SIST ETS 300 394-2-3:1999



Page 13ETS 300 394-2-3: February 19985.1.3.1Test case identifierThe identifier of a TC is built according to table 1.Table 1: TC naming convention___= test suiteLLCLogical Link Control layerx=
Type of testingCACapability testsBVValid Behaviour testsBIInvalid Behaviour testsTITimer expiry and counter mismatch testss= test subgroupas defined in the test suite structure(as many subgroups as required)
=
sequential number(01-99)TC Number5.1.3.2Test step identifierThe test step identifier is built with a string of lowercase letters leaded by a string of capital letter andjoined by an underscore character. The first string indicates the main function of the test step; e.g. PREfor preamble and LTS for local tree name. The second string indicates the meaning of the step. Theimplicit send events in the ATS are only used in test steps with prefix IMP.EXAMPLES:PRE_IUT_ResetLTS_ReceiveNextSegmentIMP_ALA_ConnectionSetup5.1.3.3Default identifierOnly one default identifier is used, namely: OtherwiseFail.5.2Implementation conventionsFully functional underlying MAC protocol is assumed from the test system.The LLC PDUs are assumed to be mapped to MAC layer service primitives in the test systemimplementation and therefore are not part of the ATS.All PDUs sent to the IUT should be sent using valid individual address, including the BL-UDATA PDUs.The test system is assumed to be configured so, that it sends valid D-MLE-SYNC and D-MLE-SYSINFOPDUs to the IUT. The BS service details element in the D-MLE-SYSINFO PDU should require registrationon the cell, so that the IUT starts registration after power up as defined in the ATS in preamblePRE_RESET_AND_REGISTER. Also, the advanced link support in the same element is required to beset on for the advanced link test cases. Other elements are to be configured according to the capabilitiesof the IUT.5.3TC and TP mappingThere is a one-to-one mapping between the TC identifiers and the TP identifiers. The correspondencerule is given by the following examples:TP identifierTC identifierTP/LLC/CA/BA-01LLC_CA_BA_01TP/LLC/BV/AA/LR-02LLC_BV_AA_LR_02TP/LLC/TI/AA-01LLC_TI_AA_01SIST ETS 300 394-2-3:1999



Page 14ETS 300 394-2-3: February 1998Annex A (normative):ATS for TETRA LLCThe ATS is written in TTCN according to ISO/IEC 9646-3 [5].As the ATS was developed on a separate TTCN tool the TTCN tables are not completely referenced inthe contents table of this ETS. The ATS itself contains a test suite overview part which provides additionalinformation and references.A.1The TTCN Graphical form (TTCN.GR)The TTCN.GR representation of this ATS is contained in a Postscript file (LLC.PS contained in archive39423e1.LZH) which accompanies this ETS.A.2The TTCN Machine Processable form (TTCN.MP)The TTCN.MP representation corresponding to this ATS is contained in an ASCII text file (LLC.MPcontained in archive 39423e1.LZH) which accompanies this ETS.NOTE:According to ISO/IEC 9646-3 [5], in case of a conflict in interpretation of theoperational semantics of TTCN.GR and TTCN.MP, the operational semantics of theTTCN.GR representation takes precedence.SIST ETS 300 394-2-3:1999



Page 15ETS 300 394-2-3: February 1998Annex B (normative):Partial PIXIT proforma for TETRA LLCNotwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants thatusers of this ETS may freely reproduce the PIXIT proforma in this annex so that it can be used for itsintended purposes and may further publish the completed PIXIT.The PIXIT proforma is based on ISO/IEC 9646-6 [7]. Any additional information needed can be found inthis international standard document.B.1Identification summaryTable B.1PIXIT number:Test laboratory name:Date of issue:Issued to:B.2ATS summaryTable B.2Protocol specification:ETS 300 392-2Protocol to be tested:ATS specification:ETS 300 394-2-3Abstract test method:Remote test method, embedded variantB.3Test laboratoryTable B.3Test laboratory identification:Test laboratory manager:Means of testing:SAP address:B.4Client identificationTable B.4Client identification:Client test manager:Test facilities required:SIST ETS 300 394-2-3:1999



Page 16ETS 300 394-2-3: February 1998B.5SUTTable B.5Name:Version:SCS number:Machine configuration:Operating system identification:IUT identification:PICS reference for IUT:Limitations of the SUT:Environmental conditions:B.6Protocol layer informationB.6.1Protocol identificationTable B.6Name:TETRA - Logical Link Control (LLC) layer - ETS 300 392-2Version:PICS references:SIST ETS 300 394-2-3:1999



Page 17ETS 300 394-2-3: February 1998B.6.2IUT informationB.6.2.1Implicit send eventsTable B.7: Implicit send eventsItemPIXIT(see note)Related implicit send message(PDU)Invocation descriptionor reference1IMP_BLA_DataTransmissionThis implicit send corresponds to the IUTinitiating the basic link acknowledged datatransmission. The resulting PDU may be one ofthe following: BL-DATA, BL-DATA-FCS, BL-ADATA or BL-ADATA-FCS. BL-ADATA or BL-ADATA-FCS PDUs should appear only whenthe IUT has received data to be acknowledged.2IMP_BLU_DataTransmissionThis implicit send corresponds to the IUTinitiating the basic link unacknowledged datatransmission. The resulting PDU may be one ofthe following: BL-UDATA, BL-UDATA-FCS.3IMP_ALA_ConnectionSetupThis implicit send corresponds to the IUTinitiating the advanced link acknowledgedservice connection setup procedure. Theresulting PDU should be AL-SETUP.4IMP_ALA_DisconnectionThis implicit send corresponds to the IUTinitiating the advanced link acknowledgedservice disconnection procedure. The resultingPDU should be AL-DISC.5IMP_ALA_DataTransmissionThis implicit send corresponds to the IUTinitiating the advanced link acknowledgedservice data transfer procedure for onesegmented or unsegmented SDU. Theresulting PDUs should be for the first segmentsAL-DATA or AL-DATA-AR PDUs and for thelast segment AL-FINAL
...