SIST ETS 300 394-2-1:1999
(Main)Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 2: Protocol testing specification for Voice plus Data (V+D); Sub-part 1: Test suite structure and test purposes
Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 2: Protocol testing specification for Voice plus Data (V+D); Sub-part 1: Test suite structure and test purposes
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šalnega protokola za govor in podatke (V+D) -1. poglavje: Zgradba preskušalnega niza (TSS) in nameni preskušanja (TP)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 394-2-1:1999
01-julij-1999
Prizemni snopovni radio (TETRA) - Specifikacija za preskušanje skladnosti - 2. del:
Specifikacija preskušalnega protokola za govor in podatke (V+D) -1. poglavje:
Zgradba preskušalnega niza (TSS) in nameni preskušanja (TP)
Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 2: Protocol
testing specification for Voice plus Data (V+D); Sub-part 1: Test suite structure and test
purposes
Ta slovenski standard je istoveten z: ETS 300 394-2-1 Edition 1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST ETS 300 394-2-1: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-1:1999
---------------------- Page: 2 ----------------------
SIST ETS 300 394-2-1:1999
EUROPEAN ETS 300 394-2-1
TELECOMMUNICATION February 1998
STANDARD
Source: TETRA Reference: DE/RES-06009-2-1
ICS: 33.020
Key words: TETRA, V+D, protocol, testing, voice, data, TSS&TP
Terrestrial Trunked Radio (TETRA);
Conformance testing specification;
Part 2: Protocol testing specification for Voice plus Data (V+D);
Sub-part 1: Test suite structure and test purposes
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.
---------------------- Page: 3 ----------------------
SIST ETS 300 394-2-1:1999
Page 2
ETS 300 394-2-1: 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-1:1999
Page 3
ETS 300 394-2-1: 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 Test Suite Structure (TSS) .9
4.1 Network (NWK) layer.9
4.1.1 Network (NWK) layer TSS overview .9
4.1.2 NWK layer test groups .10
4.2 Logical Link Control (LLC) layer.11
4.2.1 Logical Link Control (LLC) layer TSS overview.11
4.2.2 LLC layer test groups .11
4.3 Medium Access Control (MAC) layer.12
4.3.1 Medium Access Control (MAC) layer TSS overview.12
4.3.2 MAC layer test groups.12
4.4 Test group description .12
5 Introduction to Test Purposes (TPs) .13
5.1 Test purpose definition conventions .13
5.2 Test purpose naming conventions.14
6 NWK layer test purposes .14
6.1 Circuit Mode Control Entity (CMCE) .14
6.1.1 Individual call.14
6.1.1.1 Capability tests .14
6.1.1.1.1 Call setup.15
6.1.1.1.2 Call disconnection.16
6.1.1.2 Valid behaviour tests .17
6.1.1.2.1 Outgoing call.17
6.1.1.2.2 Colliding calls.18
6.1.1.2.3 Call maintenance .18
6.1.1.2.3.1 Transmission control.18
6.1.1.2.3.2 Call modification .20
6.1.1.3 Invalid behaviour tests.20
6.1.1.3.1 Call setup.20
6.1.1.3.2 Call maintenance .21
6.1.1.3.3 Call disconnection.21
6.1.1.4 Timer tests.22
6.1.2 Group call .25
6.1.2.1 Capability tests .25
6.1.2.1.1 Call setup.25
6.1.2.1.2 Call disconnection.25
6.1.2.2 Valid behaviour tests .26
6.1.2.2.1 Outgoing call.26
6.1.2.2.2 Colliding calls.26
6.1.2.2.3 Call maintenance .27
6.1.2.2.3.1 Transmission control.27
6.1.2.2.3.2 Call restoration.28
6.1.2.2.4 Call disconnection.29
6.1.2.3 Timer tests.29
---------------------- Page: 5 ----------------------
SIST ETS 300 394-2-1:1999
Page 4
ETS 300 394-2-1: February 1998
6.1.3 Short Data Service (SDS). 31
6.1.3.1 Incoming messages. 31
6.1.3.2 Outgoing messages. 31
6.2 Mobility Management (MM). 32
6.2.1 Capability tests. 32
6.2.2 Valid behaviour tests . 33
6.2.2.1 Registration. 33
6.2.2.2 Enable/disable. 35
6.2.2.3 Energy economy mode . 36
6.2.2.4 Attachment/detachment of group identities. 37
6.2.3 Invalid behaviour tests . 38
6.2.4 Timer tests. 39
6.3 Specific Connectionless Network Protocol (SCLNP) . 39
6.3.1 Capability tests. 39
6.4 Mobile Link Entity (MLE) . 40
6.4.1 Capability tests. 40
6.4.1.1 Cell reselection. 40
6.4.2 Valid behaviour tests . 41
6.4.2.1 Cell reselection. 41
6.4.2.2 Network broadcast . 44
6.4.2.3 Call restoration. 44
6.4.3 Timer tests. 45
7 LLC layer test purposes. 46
7.1 Capability tests . 46
7.1.1 Basic link, acknowledged service . 46
7.1.2 Basic link, unacknowledged service . 48
7.1.3 Advanced link, acknowledged service. 49
7.1.3.1 Link establishment . 49
7.1.3.2 Data transfer . 50
7.1.3.3 Link release. 52
7.2 Valid behaviour tests. 53
7.2.1 Basic link, acknowledged service . 53
7.2.2 Basic link, unacknowledged service . 54
7.2.3 Advanced link, acknowledged service. 54
7.2.3.1 Link establishment . 54
7.2.3.2 Data transfer . 55
7.2.3.3 Link release. 57
7.3 Invalid behaviour tests. 58
7.3.1 Basic link, acknowledged service . 58
7.3.2 Basic link, unacknowledged service . 58
7.3.3 Advanced link, acknowledged service. 59
7.4 Timer tests . 60
7.4.1 Basic link, acknowledged service . 60
7.4.2 Advanced link, acknowledged service. 60
8 MAC layer test purposes . 61
8.1 Capability tests . 61
8.2 Valid behaviour tests. 61
8.2.1 Minimum mode . 61
8.2.2 Addressing. 62
8.2.3 Random access. 62
8.2.4 Reserved access . 62
8.3 Invalid behaviour tests. 63
8.3.1 Addressing. 63
8.3.2 Minimum mode . 64
8.3.3 Random access. 64
8.4 Timer tests . 64
History. 66
---------------------- Page: 6 ----------------------
SIST ETS 300 394-2-1:1999
Page 5
ETS 300 394-2-1: 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-1:1999
Page 6
ETS 300 394-2-1: February 1998
Blank page
---------------------- Page: 8 ----------------------
SIST ETS 300 394-2-1:1999
Page 7
ETS 300 394-2-1: February 1998
1 Scope
This European Telecommunication Standard (ETS) contains the Test Suite Structure (TSS) and Test
Purposes (TPs) to test the TETRA Voice plus Data (V+D) protocols.
The conformance testing of Connection Oriented Network Protocol (CONP) is outside the scope of this
ETS. Instead, existing test specifications for that protocol should be applied.
The testing of supplementary services is outside the scope of this ETS.
The TPs presented in this ETS are applicable to TETRA MSs supporting optional security as specified in
ETS 300 392-7 [3], taking into account the restrictions described in more detail further on in this ETS.
However, the actual testing of security features is outside the scope of this ETS.
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] and
ISO/IEC 9646-2 [5], as well as the ETSI methodology for conformance testing, ETS 300 406 [6], are used
as the basis for the test methodology.
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 392-1: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA) system; Voice plus Data (V+D); Part 1: General
Network Design".
[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".
[3] ETS 300 392-7: "Radio Equipment and Systems (RES); Trans-European
Trunked Radio (TETRA) system; Voice plus Data (V+D); Part 7: Security".
[4] 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)).
[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] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".
---------------------- Page: 9 ----------------------
SIST ETS 300 394-2-1:1999
Page 8
ETS 300 394-2-1: 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:
CMCE Circuit Mode Control Entity
CONP Connection Oriented Network Protocol
FCS Frame Check Sequence
ITSI Individual TETRA Subscriber Identity
LACC Location Area Country Code
LANC Location Area Network Code
LLC Logical Link Control
MAC Medium Access Control
MCC Mobile Country Code
MLE Mobile Link Entity
MM Mobility Management
MNC Mobile Network Code
MS Mobile Station
NWK Network. Layer 3 of the TETRA protocol stack
SCLNP Specific Connectionless Network Protocol
SDS Short Data Services sub entity within CMCE
SDU Service Data Unit
SwMI Switching and Management Infrastructure
3.3 ISO 9646 definitions
For the purposes of this ETS, the following ISO 9646-1 [4] definitions apply:
Implementation Conformance Statement (ICS)
Implementation Under Test (IUT)
Implementation eXtra Information for Testing (IXIT)
Protocol Implementation Conformance Statement (PICS)
Protocol Implementation eXtra Information for Testing (PIXIT)
3.4 ISO 9646 abbreviations
For the purposes of this ETS, the following ISO 9646-1 [4] abbreviations apply:
IUT Implementation Under Test
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
TP Test Purpose
TSS Test Suite Structure
---------------------- Page: 10 ----------------------
SIST ETS 300 394-2-1:1999
Page 9
ETS 300 394-2-1: February 1998
4 Test Suite Structure (TSS)
4.1 Network (NWK) layer
4.1.1 Network (NWK) layer TSS overview
The NWK layer test suite, as illustrated in figure 1, is structured as a tree with a first level defined as NWK
representing the whole test suite for TETRA V+D network layer protocols.
IC
NWK CMCE CA
SU
BV
OC
CD
BI SU
CC
TI
MA
MA
TC
CM
CD
GC
CA
SU
BV OC
CD
TI
CC
SDS
MA
IC TC
OG CD
CR
CA
MM
RE
BV
EN
BI
EE
TI
AT
SCLNP CA
MLE
CA CR
BV CR
TI
NB
RE
Figure 1: NWK layer TSS
---------------------- Page: 11 ----------------------
SIST ETS 300 394-2-1:1999
Page 10
ETS 300 394-2-1: February 1998
4.1.2 NWK layer test groups
The test groups are organized in several levels. The first level separates the NWK layer in different
protocols. The second level generally separates protocol test in four functional test groups according to
the type of testing: Capability test (CA), Valid Behaviour (BV), Invalid Behaviour (BI), and Timer tests (TI).
The purpose of these test groups is explained in subclause 4.4. Exceptionally, the second level of the
CMCE protocol creates functional modules which are then further on divided into these four functional test
groups, i.e. CA, BV, BI, and TI. Further levels of the test subgroups are used to form more detailed
division of protocol requirements, generally protocol procedures are used for naming the subgroups.
The following list defines the NWK layer test group names and identifiers used for those:
Circuit Mode Control Entity (CMCE)
Individual Call (IC)
Capability tests (CA)
Call Setup (SU)
Call Disconnection (CD)
Valid Behaviour tests (BV)
Outgoing Call (OC)
Colliding Calls (CC)
Call Maintenance (MA)
Transmission Control (TC)
Call Modification (CM)
Invalid Behaviour tests (BI)
Call Setup (SU)
Call Maintenance (MA)
Call Disconnection (CD)
Timer Tests (TI)
Group Call (GC)
Capability tests (CA)
Call Setup (SU)
Call Disconnection (CD)
Valid Behaviour tests (BV)
Outgoing Call (OC)
Colliding Calls (CC)
Call Maintenance (MA)
Transmission Control (TC)
Call Restoration (CR)
Call Disconnection (CD)
Timer Tests (TI)
Short Data Service (SDS)
Incoming messages (IC)
Outgoing messages (OG)
Mobility Management (MM)
Capability tests (CA)
Valid Behaviour tests (BV)
Registration (RE)
Enable/disable (EN)
Energy Economy Mode (EE)
Attachment/detachment of group identities (AT)
Invalid Behaviour tests (BI)
Timer tests (TI)
Specific Connectionless Network Protocol (SCLNP)
Capability tests (CA)
Mobile Link Entity (MLE)
Capability tests (CA)
Cell Reselection (CR)
Valid Behaviour tests (BV)
Cell Reselection (CR)
Network Broadcast (NB)
Call restoration (RE)
Timer tests (TI)
---------------------- Page: 12 ----------------------
SIST ETS 300 394-2-1:1999
Page 11
ETS 300 394-2-1: February 1998
4.2 Logical Link Control (LLC) layer
4.2.1 Logical Link Control (LLC) layer TSS overview
The LLC layer TSS is illustrated in figure 2.
LLC CA BA
BA BU
BV
BA BU AA LE
BI
AA LE
BU
DT
DT
AA LR
TI BA LR
AA
Figure 2: LLC layer TSS
4.2.2 LLC layer test groups
The first level of the LLC test groups separates the LLC test suite in four functional test groups: CA, BV,
BI, and TI. The second level splits the test suite into different LLC services. Further levels of the test
subgroups are used to form more detailed division of protocol requirements.
The following list defines the LLC layer test group names and identifiers:
Capability tests (CA)
Basic link, Acknowledged service (BA)
Basic link, Unacknowledged service (BU)
Advanced link, Acknowledged service (AA)
Link Establishment (LE)
Data Transfer (DT)
Link Release (LR)
Valid Behaviour tests (BV)
Basic link, Acknowledged service (BA)
Basic link, Unacknowledged service (BU)
Advanced link, Acknowledged service (AA)
Link Establishment (LE)
Data Transfer (DT)
Link Release (LR)
Invalid Behaviour tests (BI)
Basic link, Acknowledged service (BA)
Basic link, Unacknowledged service (BU)
Advanced link, Acknowledged service (AA)
Timer tests (TI)
Basic link, Acknowledged service (BA)
Advanced link, Acknowledged service (AA)
---------------------- Page: 13 ----------------------
SIST ETS 300 394-2-1:1999
Page 12
ETS 300 394-2-1: February 1998
4.3 Medium Access Control (MAC) layer
4.3.1 Medium Access Control (MAC) layer TSS overview
The MAC layer TSS is illustrated in figure 3.
MAC CA
BV MI
AD
BI
AD
RA
MI
TI
RE
RA
Figure 3: MAC layer TSS
4.3.2 MAC layer test groups
The first level of the MAC test groups separates the MAC test suite in four functional test groups: CA, BV,
BI, and TI. The second level of the test subgroups is used to form a division of protocol requirements.
The following list defines the MAC layer test group names and identifiers:
Capability tests (CA)
Valid behaviour tests (BV)
Minimum mode (MI)
Addressing (AD)
Random access (RA)
Reserved access (RE)
Invalid behaviour tests (BI)
Addressing (AD)
Minimum mode (MI)
Random access (RA)
Timer tests (TI)
4.4 Test group description
Capability (CA) tests provide limited testing that the observable capabilities of the IUT are in accordance
with the static conformance requirements and the additional capabilities claimed in the PICS/PIXIT. In
particular, this test group can be regarded as a set of spot checks for all the capabilities of the IUT stated
in the PICS/PIXIT. Scope of the test group is the observable capabilities of the IUT with respect to NWK
layer connection, call control, and the mobility management.
The Valid Behaviour (BV) group tests an IUT in response to valid behaviour of the test system. "Valid"
means that a test event is syntactically and contextually correct. All test cases in the valid behaviour group
are intended to verify as thoroughly as possible the various functions of the protocol.
The Invalid Behaviour (BI) group is intended to verify that the IUT is able to react properly in case an
invalid protocol data unit (message) occurring. Invalid PDU here means syntactically or semantically
invalid test events generated by the test system. A syntactically or semantically invalid test event
regardless of the current state is not allowed. Inopportune test cases are also included in this test group.
These are intended to verify that the IUT is able to react properly in case an inopportune test event
occurring. Such an event is syntactically correct, but occurs when it is not allowed.
Different timers and counters are defined to supervise the various state transitions. The Timer (TI) test
group is intended to verify that the IUT is reacting properly to an expiry of one of the timers or to a counter
mismatch.
---------------------- Page: 14 ----------------------
SIST ETS 300 394-2-1:1999
Page 13
ETS 300 394-2-1: February 1998
5 Introduction to Test Purposes (TPs)
The test purposes for each test suite are defined in this ETS in clauses 6, 7, and 8 for NWK layer, LLC
layer and MAC layer respectively.
5.1 Test purpose definition conventions
The test purposes are defined following particular rules as shown in the table 1.
Table 1: Test purpose definition rules
TP Id Reference
Condition
Initial state
Stimulus
Expected behaviour
TP Id: The TP Id is a unique identifier it shall be specified according to the TP naming
conventions defined in the subclause below.
Reference: The reference should contain the references of the subject to be validated by
the actual TP (specification reference, clause, paragraph).
Condition: The conditions applying to selecting the test purpose
Initial State: Defines in which initial state the IUT has to be, in order to apply the TP.
Stimulus: The stimulus defines the test event to which the TP is related.
Expected behaviour: Definition of the events that are expected from the IUT to conform to the base
specification.
---------------------- Page: 15 ----------------------
SIST ETS 300 394-2-1:1999
Page 14
ETS 300 394-2-1: February 1998
5.2 Test purpose naming conventions
The identifier of the test purpose is built according to table 2:
Table 2: Test purpose naming convention
TP/////
= test suite NWK Network layer
LLC Logical Link Control layer
MAC Medium Access Control layer
= functional module or For NWK layer:
subentity (NWK layer only) CMCE/IC Circuit Mode Control Entity/Individual Call
CMCE/GC Circuit Mode Control Entity/Group Call
CMCE/SDS Circuit Mode Control Entity/Short Data Srv.
MM Mobility Management
SCLNP Specific Connectionless Network Protocol
MLE Mobile Link Entity
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) Test Purpose Number
6 NWK layer test purposes
6.1 Circuit Mode Control Entity (CMCE)
Test group objective:
To test the behaviour of the CMCE module of the IUT.
Condition: IUT implements the CMCE
6.1.1 Individual call
Test group objective:
To test the behaviour of the CMCE module of the IUT, when operating in individual call mode.
Condition: IUT supports individual call
6.1.1.1 Capability tests
Test group objective:
To test the basic capabilities of the CMCE module of the IUT, when operating in individual call mode.
---------------------- Page: 16 ----------------------
SIST ETS 300 394-2-1:1999
Page 15
ETS 300 394-2-1: February 1998
6.1.1.1.1 Call setup
Test group objective:
To test the basic capabilities of the CMCE module of the IUT during call setup, when operating in
individual call mode.
TP/NWK/CMCE/IC/CA/SU-01 Reference: ETS 300 392-2 [2], subclauses 14.4.2, 14.5.1.1, 14.5.1.1.1
Condition: IUT supports incoming call with on hook/off hook signalling
Initial state: Call Control in state IDLE and IUT registered
Stimulus: Incoming call in IDLE state
Verify that, when the IUT receives a D-SETUP PDU indicating on
hook/off hook signalling, it enters the MT-CALL-SETUP state and sends
a U-ALERT PDU.
TP/NWK/CMCE/IC/CA/SU-02 Reference: ETS 300 392-2 [2], subclauses 14.4.2, 14.5.1.1, 14.5.1.1.1
Condition: IUT supports incoming call with on hook/off hook signalling
Initial state: MT-CALL SETUP
Stimulus: Incoming call answered
Verify that, having received an incoming call and issued a U-ALERT
PDU, when the called user application ha
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Prizemni snopovni radio (TETRA) - Specifikacija za preskušanje skladnosti - 2. del: Specifikacija preskušalnega protokola za govor in podatke (V+D) -1. poglavje: Zgradba preskušalnega niza (TSS) in nameni preskušanja (TP)Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 2: Protocol testing specification for Voice plus Data (V+D); Sub-part 1: Test suite structure and test purposes33.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-1 E13SIST ETS 300 394-2-1:1999en01-PDM-19993SIST ETS 300 394-2-1:1999SLOVENSKI
STANDARD
SIST ETS 300 394-2-1:1999
EUROPEANETS 300 394-2-1TELECOMMUNICATIONFebruary 1998STANDARDSource: TETRAReference: DE/RES-06009-2-1ICS:33.020Key words:TETRA, V+D, protocol, testing, voice, data, TSS&TPTerrestrial Trunked Radio (TETRA);Conformance testing specification;Part 2: Protocol testing specification for Voice plus Data (V+D);Sub-part 1: Test suite structure and test purposesETSIEuropean 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: secretariat@etsi.frTel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16Copyright 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-1:1999
Page 2ETS 300 394-2-1: 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-1:1999
Page 3ETS 300 394-2-1: February 1998ContentsForeword.51Scope.72Normative references.73Definitions and abbreviations.83.1TETRA definitions.83.2TETRA abbreviations.83.3ISO 9646 definitions.83.4ISO 9646 abbreviations.84Test Suite Structure (TSS).94.1Network (NWK) layer.94.1.1Network (NWK) layer TSS overview.94.1.2NWK layer test groups.104.2Logical Link Control (LLC) layer.114.2.1Logical Link Control (LLC) layer TSS overview.114.2.2LLC layer test groups.114.3Medium Access Control (MAC) layer.124.3.1Medium Access Control (MAC) layer TSS overview.124.3.2MAC layer test groups.124.4Test group description.125Introduction to Test Purposes (TPs).135.1Test purpose definition conventions.135.2Test purpose naming conventions.146NWK layer test purposes.146.1Circuit Mode Control Entity (CMCE).146.1.1Individual call.146.1.1.1Capability tests.146.1.1.1.1Call setup.156.1.1.1.2Call disconnection.166.1.1.2Valid behaviour tests.176.1.1.2.1Outgoing call.176.1.1.2.2Colliding calls.186.1.1.2.3Call maintenance.186.1.1.2.3.1Transmission control.186.1.1.2.3.2Call modification.206.1.1.3Invalid behaviour tests.206.1.1.3.1Call setup.206.1.1.3.2Call maintenance.216.1.1.3.3Call disconnection.216.1.1.4Timer tests.226.1.2Group call.256.1.2.1Capability tests.256.1.2.1.1Call setup.256.1.2.1.2Call disconnection.256.1.2.2Valid behaviour tests.266.1.2.2.1Outgoing call.266.1.2.2.2Colliding calls.266.1.2.2.3Call maintenance.276.1.2.2.3.1 Transmission control.276.1.2.2.3.2Call restoration.286.1.2.2.4Call disconnection.296.1.2.3Timer tests.29SIST ETS 300 394-2-1:1999
Page 4ETS 300 394-2-1: February 19986.1.3Short Data Service (SDS).316.1.3.1Incoming messages.316.1.3.2Outgoing messages.316.2Mobility Management (MM).326.2.1Capability tests.326.2.2Valid behaviour tests.336.2.2.1Registration.336.2.2.2Enable/disable.356.2.2.3Energy economy mode.366.2.2.4Attachment/detachment of group identities.376.2.3Invalid behaviour tests.386.2.4Timer tests.396.3Specific Connectionless Network Protocol (SCLNP).396.3.1Capability tests.396.4Mobile Link Entity (MLE).406.4.1Capability tests.406.4.1.1Cell reselection.406.4.2Valid behaviour tests.416.4.2.1Cell reselection.416.4.2.2Network broadcast.446.4.2.3Call restoration.446.4.3Timer tests.457LLC layer test purposes.467.1Capability tests.467.1.1Basic link, acknowledged service.467.1.2Basic link, unacknowledged service.487.1.3Advanced link, acknowledged service.497.1.3.1Link establishment.497.1.3.2Data transfer.507.1.3.3Link release.527.2Valid behaviour tests.537.2.1Basic link, acknowledged service.537.2.2Basic link, unacknowledged service.547.2.3Advanced link, acknowledged service.547.2.3.1Link establishment.547.2.3.2Data transfer.557.2.3.3Link release.577.3Invalid behaviour tests.587.3.1Basic link, acknowledged service.587.3.2Basic link, unacknowledged service.587.3.3Advanced link, acknowledged service.597.4Timer tests.607.4.1Basic link, acknowledged service.607.4.2Advanced link, acknowledged service.608MAC layer test purposes.618.1Capability tests.618.2Valid behaviour tests.618.2.1Minimum mode.618.2.2Addressing.628.2.3Random access.628.2.4Reserved access.628.3Invalid behaviour tests.638.3.1Addressing.638.3.2Minimum mode.648.3.3Random access.648.4Timer tests.64History.66SIST ETS 300 394-2-1:1999
Page 5ETS 300 394-2-1: 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-1:1999
Page 6ETS 300 394-2-1: February 1998Blank pageSIST ETS 300 394-2-1:1999
Page 7ETS 300 394-2-1: February 19981ScopeThis European Telecommunication Standard (ETS) contains the Test Suite Structure (TSS) and TestPurposes (TPs) to test the TETRA Voice plus Data (V+D) protocols.The conformance testing of Connection Oriented Network Protocol (CONP) is outside the scope of thisETS. Instead, existing test specifications for that protocol should be applied.The testing of supplementary services is outside the scope of this ETS.The TPs presented in this ETS are applicable to TETRA MSs supporting optional security as specified inETS 300 392-7 [3], taking into account the restrictions described in more detail further on in this ETS.However, the actual testing of security features is outside the scope of this ETS.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 [4] andISO/IEC 9646-2 [5], as well as the ETSI methodology for conformance testing, ETS 300 406 [6], are usedas the basis for the test methodology.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 392-1: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA) system; Voice plus Data (V+D); Part 1: GeneralNetwork Design".[2]ETS 300 392-2: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA) system; Voice plus Data (V+D); Part 2: Air Interface".[3]ETS 300 392-7: "Radio Equipment and Systems (RES); Trans-EuropeanTrunked Radio (TETRA) system; Voice plus Data (V+D); Part 7: Security".[4]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)).[5]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)).[6]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocoland profile conformance testing specifications; Standardization methodology".SIST ETS 300 394-2-1:1999
Page 8ETS 300 394-2-1: 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:CMCECircuit Mode Control EntityCONPConnection Oriented Network ProtocolFCSFrame Check SequenceITSIIndividual TETRA Subscriber IdentityLACCLocation Area Country CodeLANCLocation Area Network CodeLLCLogical Link ControlMACMedium Access ControlMCCMobile Country CodeMLEMobile Link EntityMMMobility ManagementMNCMobile Network CodeMSMobile StationNWKNetwork. Layer 3 of the TETRA protocol stackSCLNPSpecific Connectionless Network ProtocolSDSShort Data Services sub entity within CMCESDUService Data UnitSwMISwitching and Management Infrastructure3.3ISO 9646 definitionsFor the purposes of this ETS, the following ISO 9646-1 [4] definitions apply:Implementation Conformance Statement (ICS)Implementation Under Test (IUT)Implementation eXtra Information for Testing (IXIT)Protocol Implementation Conformance Statement (PICS)Protocol Implementation eXtra Information for Testing (PIXIT)3.4ISO 9646 abbreviationsFor the purposes of this ETS, the following ISO 9646-1 [4] abbreviations apply:IUTImplementation Under TestPDUProtocol Data UnitPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureSIST ETS 300 394-2-1:1999
Page 9ETS 300 394-2-1: February 19984Test Suite Structure (TSS)4.1Network (NWK) layer4.1.1Network (NWK) layer TSS overviewThe NWK layer test suite, as illustrated in figure 1, is structured as a tree with a first level defined as NWKrepresenting the whole test suite for TETRA V+D network layer protocols.CMCEMLEBVBIBVTITICAMMCMNWKSCLNPOCICGCSDSTCMASUMACCBVCRTICAOCTCMACDSUCDSUCDBVBITICAREENEEATCACRNBCACCOGICCDRECRFigure 1: NWK layer TSSSIST ETS 300 394-2-1:1999
Page 10ETS 300 394-2-1: February 19984.1.2NWK layer test groupsThe test groups are organized in several levels. The first level separates the NWK layer in differentprotocols. The second level generally separates protocol test in four functional test groups according tothe type of testing: Capability test (CA), Valid Behaviour (BV), Invalid Behaviour (BI), and Timer tests (TI).The purpose of these test groups is explained in subclause 4.4. Exceptionally, the second level of theCMCE protocol creates functional modules which are then further on divided into these four functional testgroups, i.e. CA, BV, BI, and TI. Further levels of the test subgroups are used to form more detaileddivision of protocol requirements, generally protocol procedures are used for naming the subgroups.The following list defines the NWK layer test group names and identifiers used for those:Circuit Mode Control Entity (CMCE)Individual Call (IC)Capability tests (CA)Call Setup (SU)Call Disconnection (CD)Valid Behaviour tests (BV)Outgoing Call (OC)Colliding Calls (CC)Call Maintenance (MA)Transmission Control (TC)Call Modification (CM)Invalid Behaviour tests (BI)Call Setup (SU)Call Maintenance (MA)Call Disconnection (CD)Timer Tests (TI)Group Call (GC)Capability tests (CA)Call Setup (SU)Call Disconnection (CD)Valid Behaviour tests (BV)Outgoing Call (OC)Colliding Calls (CC)Call Maintenance (MA)Transmission Control (TC)Call Restoration (CR)Call Disconnection (CD)Timer Tests (TI)Short Data Service (SDS)Incoming messages (IC)Outgoing messages (OG)Mobility Management (MM)Capability tests (CA)Valid Behaviour tests (BV)Registration (RE)Enable/disable (EN)Energy Economy Mode (EE)Attachment/detachment of group identities (AT)Invalid Behaviour tests (BI)Timer tests (TI)Specific Connectionless Network Protocol (SCLNP)Capability tests (CA)Mobile Link Entity (MLE)Capability tests (CA)Cell Reselection (CR)Valid Behaviour tests (BV)Cell Reselection (CR)Network Broadcast (NB)Call restoration (RE)Timer tests (TI)SIST ETS 300 394-2-1:1999
Page 11ETS 300 394-2-1: February 19984.2Logical Link Control (LLC) layer4.2.1Logical Link Control (LLC) layer TSS overviewThe LLC layer TSS is illustrated in figure 2.BVBITICALLCBUBAAABUBAAALEDTLRBU BA AA LEDTLRBAAAFigure 2: LLC layer TSS4.2.2LLC layer test groupsThe first level of the LLC test groups separates the LLC test suite in four functional test groups: CA, BV,BI, and TI. The second level splits the test suite into different LLC services. Further levels of the testsubgroups are used to form more detailed division of protocol requirements.The following list defines the LLC layer test group names and identifiers:Capability tests (CA)Basic link, Acknowledged service (BA)Basic link, Unacknowledged service (BU)Advanced link, Acknowledged service (AA)Link Establishment (LE)Data Transfer (DT)Link Release (LR)Valid Behaviour tests (BV)Basic link, Acknowledged service (BA)Basic link, Unacknowledged service (BU)Advanced link, Acknowledged service (AA)Link Establishment (LE)Data Transfer (DT)Link Release (LR)Invalid Behaviour tests (BI)Basic link, Acknowledged service (BA)Basic link, Unacknowledged service (BU)Advanced link, Acknowledged service (AA)Timer tests (TI)Basic link, Acknowledged service (BA)Advanced link, Acknowledged service (AA)SIST ETS 300 394-2-1:1999
Page 12ETS 300 394-2-1: February 19984.3Medium Access Control (MAC) layer4.3.1Medium Access Control (MAC) layer TSS overviewThe MAC layer TSS is illustrated in figure 3.BVBITICAMACMIADRARERAADMIFigure 3: MAC layer TSS4.3.2MAC layer test groupsThe first level of the MAC test groups separates the MAC test suite in four functional test groups: CA, BV,BI, and TI. The second level of the test subgroups is used to form a division of protocol requirements.The following list defines the MAC layer test group names and identifiers:Capability tests (CA)Valid behaviour tests (BV)Minimum mode (MI)Addressing (AD)Random access (RA)Reserved access (RE)Invalid behaviour tests (BI)Addressing (AD)Minimum mode (MI)Random access (RA)Timer tests (TI)4.4Test group descriptionCapability (CA) tests provide limited testing that the observable capabilities of the IUT are in accordancewith the static conformance requirements and the additional capabilities claimed in the PICS/PIXIT. Inparticular, this test group can be regarded as a set of spot checks for all the capabilities of the IUT statedin the PICS/PIXIT. Scope of the test group is the observable capabilities of the IUT with respect to NWKlayer connection, call control, and the mobility management.The Valid Behaviour (BV) group tests an IUT in response to valid behaviour of the test system. "Valid"means that a test event is syntactically and contextually correct. All test cases in the valid behaviour groupare intended to verify as thoroughly as possible the various functions of the protocol.The Invalid Behaviour (BI) group is intended to verify that the IUT is able to react properly in case aninvalid protocol data unit (message) occurring. Invalid PDU here means syntactically or semanticallyinvalid test events generated by the test system. A syntactically or semantically invalid test eventregardless of the current state is not allowed. Inopportune test cases are also included in this test group.These are intended to verify that the IUT is able to react properly in case an inopportune test eventoccurring. Such an event is syntactically correct, but occurs when it is not allowed.Different timers and counters are defined to supervise the various state transitions. The Timer (TI) testgroup is intended to verify that the IUT is reacting properly to an expiry of one of the timers or to a countermismatch.SIST ETS 300 394-2-1:1999
Page 13ETS 300 394-2-1: February 19985Introduction to Test Purposes (TPs)The test purposes for each test suite are defined in this ETS in clauses 6, 7, and 8 for NWK layer, LLClayer and MAC layer respectively.5.1Test purpose definition conventionsThe test purposes are defined following particular rules as shown in the table 1.Table 1: Test purpose definition rulesTP IdReferenceConditionInitial stateStimulusExpected behaviourTP Id:The TP Id is a unique identifier it shall be specified according to the TP namingconventions defined in the subclause below.Reference:The reference should contain the references of the subject to be validated bythe actual TP (specification reference, clause, paragraph).Condition:The conditions applying to selecting the test purposeInitial State:Defines in which initial state the IUT has to be, in order to apply the TP.Stimulus:The stimulus defines the test event to which the TP is related.Expected behaviour:Definition of the events that are expected from the IUT to conform to the basespecification.SIST ETS 300 394-2-1:1999
Page 14ETS 300 394-2-1: February 19985.2Test purpose naming conventionsThe identifier of the test purpose is built according to table 2:Table 2: Test purpose naming conventionTP/////= test suiteNWKNetwork layerLLCLogical Link Control layerMACMedium Access Control layer= functional module orFor NWK layer:subentity (NWK layer only)CMCE/ICCircuit Mode Control Entity/Individual CallCMCE/GCCircuit Mode Control Entity/Group CallCMCE/SDSCircuit Mode Control Entity/Short Data Srv.MMMobility ManagementSCLNPSpecific Connectionless Network ProtocolMLEMobile Link Entityx= 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)Test Purpose Number6NWK layer test purposes6.1Circuit Mode Control Entity (CMCE)Test group objective:To test the behaviour of the CMCE module of the IUT.Condition: IUT implements the CMCE6.1.1Individual callTest group objective:To test the behaviour of the CMCE module of the IUT, when operating in individual call mode.Condition: IUT supports individual call6.1.1.1Capability testsTest group objective:To test the basic capabilities of the CMCE module of the IUT, when operating in individual call mode.SIST ETS 300 394-2-1:1999
Page 15ETS 300 394-2-1: February 19986.1.1.1.1Call setupTest group objective:To test the basic capabilities of the CMCE module of the IUT during call setup, when operating inindividual call mode.TP/NWK/CMCE/IC/CA/SU-01Reference: ETS 300 392-2 [2], subclauses 14.4.2, 14.5.1.1, 14.5.1.1.1Condition: IUT supports incoming call with on hook/off hook signallingInitial state:Call Control in state IDLE and IUT registeredStimulus: Incoming call in IDLE stateVerify that, when the IUT receives a D-SETUP PDU indicating onhook/off hook signalling, it enters the MT-CALL-SETUP state and sendsa U-ALERT PDU.TP/NWK/CMCE/IC/CA/SU-02Reference: ETS 300 392-2 [2], subclauses 14.4.2, 14.5.1.1, 14.5.1.1.1Condition: IUT supports incoming call with on hook/off hook signallingInitial state:MT-CALL SETUPStimulus: Incoming call answeredVerify that, having received an incoming call and issued a U-ALERTPDU, when the called user application has answered, the IUT sends aU-CONNECT PDU and accepts a D-CONNECT-ACKNOWLEDGE PDUin return, entering the CALL-ACTIVE state.TP/NWK/CMCE/IC/CA/SU-03Reference: ETS 300 392-2 [2], subclauses 14.4.2, 14.5.1.1, 14.5.1.1.1Condition: IUT supports incoming call with direct setup signallingInitial state:Call Control in state IDLE and IUT registeredStimulus: Incoming call in IDLE stateVerify that, when the IUT receives a D-SETUP PDU indicating directsetup signalling, it sends a U-CONNECT PDU and accepts aD-CONNECT-ACKNOWLEDGE PDU in return, entering the CALL-ACTIVE state.TP/NWK/CMCE/IC/CA/SU-04Reference: ETS 300 392-2 [2], subclauses 14.4.2, 14.5.1.1, 14.5.1.1.2Condition: IUT supports outgoing call requesting on hook/off hooksignallingInitial state:Call Control in state IDLE and IUT registeredStimulus: Outgoing call from IDLE stateVerify that, when the IUT initiates an outgoing call indicating on hook/offhook signalling, it sends a U-SETUP PDU, enters MO-CALL-SETUPstate and accepts in response a D-ALERT PDU followed by aD-CONNECT PDU, entering the CALL-ACTIVE state.SIST ETS 300 394-2-1:1999
Page 16ETS 300 394-2-1: February 1998TP/NWK/CMCE/IC/CA/SU-05Reference: ETS 300 392-2 [2], subclauses 14.4.2, 14.5.1.1, 14.5.1.1.2Condition: IUT supports outgoing call requesting direct setup signallingInitial state:Call Control in state IDLE and IUT registeredStimulus: Outgoing call from IDLE stateVerify that, when the IUT initiates an outgoing call indicating direct setupsignalling, it sends a U-SETUP PDU, enters MO-CALL-SETUP state andaccepts in response a D-CONNECT PDU, entering the CALL-ACTIVEstate.6.1.1.1.2Call disconnectionTest group objective:To test the basic capabilities of the CMCE module of the IUT during call disconnection, when operating
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.