SIST ETS 300 394-4-8 E1:2003

• Abstract:

  Protocol conformance testing (TTCN) for mobile stations to be used for Direct Mode operation

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 394-4-8 ed.1 (1999-06) - Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 4: Protocol testing specification for Direct Mode Operation (DMO); Sub-part 8: Test Suite Structure and Test Purposes (TSS&TP) for Direct Mode Gateway (DM-GATE)

SIST ETS 300 394-4-8 E1:2003 is the Slovenian adoption of ETS 300 394-4-8 Edition 1, published by ETSI for Terrestrial Trunked Radio (TETRA). It is a protocol conformance testing specification for Direct Mode Operation (DMO) and defines the Test Suite Structure and Test Purposes for a Direct Mode Gateway (DM-GATE) that connects the MS-GW to the Switching and Management Infrastructure (SwMI) of a Voice plus Data (V+D) system.

What does SIST ETS 300 394-4-8 E1:2003 specify?

SIST ETS 300 394-4-8 E1:2003 specifies the conformance test structure and test purposes used to check DMO gateway behavior at the protocol level. In practice, it tells a test lab which gateway functions to exercise, how to organize the cases, and how to judge pass or fail.

The document is organized around the test framework used for TETRA DMO approval testing:

• Clause 1 sets the scope and states that security features are outside the scope.
• Clause 2 lists the normative references.
• Clause 3 gives the definitions and abbreviations.
• Clause 4 defines the Test Suite Structure (TSS).
• Clause 5 introduces the Test Purposes (TPs), including naming rules and preamble/postamble conventions.
• Clauses 6 to 10 contain the gateway test purposes for call control, SDS, MM, MLE, LLC and MAC.
• Annex A is an informative bibliography.

The scope is focused on the gateway side of DMO. The sub-part covers the gateway that bridges an MS-GW and a V+D SwMI, and it is intended as a basis for approval tests with a high probability of air interface interoperability between equipment from different manufacturers.

What are the key requirements of SIST ETS 300 394-4-8 E1:2003?

SIST ETS 300 394-4-8 E1:2003 does not define product performance limits in the usual sense. Instead, it defines the test purposes and the structure that a conformance test suite must follow, so that an implementation can be checked in a repeatable way.

Clause 4 - how the test suite is structured

Clause 4 divides the TSS into gateway functions at layer 3 and layer 2. At layer 3, the document separates Gateway Call Control (GWCC), Gateway Mobility Management (GMM) and Mobile Link Entity (MLE). At layer 2, it covers Logical Link Control (LLC) and Medium Access Control (MAC). This matters because a gateway implementation can be evaluated by protocol area instead of as one large block.

Clause 4.3 also explains the three main test group types:

• Capability tests (CA) check that the observable capabilities match the conformance requirements and the claimed options in PICS/PIXIT.
• Valid Behaviour tests (BV) check the response to valid, syntactically and contextually correct test events.
• Timer tests (TI) check the reaction to timer expiry or counter mismatch.

For a buyer or quality manager, this tells you that the suite is aimed at both declared features and state-dependent behavior, not only at basic connectivity.

Clause 5 - how each test purpose is written

Clause 5 defines what each TP table contains: the TP name, its reference, purpose, test description, visible pass action, selection expression, preamble and postamble. This is important in practice because the test case can only be selected if the implementation claims the relevant option in the PICS/PIXIT.

Clause 5 also defines the TP naming convention. The identifier shows the suite type, functional entity, optional test group, test type, optional subgroup and sequence number. That makes each case traceable during test preparation, reporting and automation.

Preambles and postambles are described with Message Sequence Charts (MSCs). They are used to bring the Implementation Under Test (IUT) into the right state before the test and back to idle afterwards.

Clause 6 - gateway call control and SDS behavior

Clause 6 is the largest technical part. It covers Gateway Call Control for Circuit Mode (CM), including call set-up, call disconnection, call collision, control of transmission and timer behavior. It also covers Short Data Service (SDS).

In practice, the call control tests verify that the gateway:

• accepts and generates the expected call control PDUs,
• reaches the expected call states such as CALL ACTIVE and IDLE,
• resolves collisions by giving priority to one call and releasing the other,
• reacts correctly when transmission is granted, withdrawn, interrupted or demanded,
• times out correctly when call setup or connection procedures are not completed.

The SDS cases check both incoming and outgoing short data, for pre-defined and user-defined messages, using group or individual addressing. That matters if the gateway is expected to carry short signaling messages as part of DMO operation.

Clause 7 - gateway mobility management

Clause 7 covers GMM behavior. It checks registration-related procedures, including when no registration is required, when the gateway must initiate registration, and when registration is required before accepting calls.

The clause also checks the contents of U-LOCATION UPDATE DEMAND in different registration situations and the forwarding of DM-MS identity information to the SwMI. For implementers, this means the gateway must not only register, but register with the right procedure and parameters.

Clauses 8 to 10 - lower-layer test purposes

Clauses 8, 9 and 10 apply the test purposes for MLE, LLC and MAC by reference to ETS 300 394-2-1. This shows that the gateway sub-part reuses the V+D testing structure for lower-layer behavior instead of redefining it.

What terms does SIST ETS 300 394-4-8 E1:2003 define?

• Direct Mode Operation (DMO) - the TETRA mode where terminals communicate directly rather than through the network.
• Direct Mode Gateway (DM-GATE) - the gateway function tested by this sub-part, linking DMO with the V+D SwMI.
• Switching and Management Infrastructure (SwMI) - the V+D network side that the gateway connects to.
• Implementation Under Test (IUT) - the gateway or protocol implementation being exercised by the test.
• Protocol Implementation Conformance Statement (PICS) - the statement used to select which test cases apply to an implementation.
• Protocol Implementation eXtra Information for Testing (PIXIT) - extra implementation details needed to run the tests correctly.
• Test Suite Structure (TSS) - the organized grouping of test cases by protocol and function.
• Test Purpose (TP) - the statement of what each test case is intended to verify.

Who uses SIST ETS 300 394-4-8 E1:2003?

SIST ETS 300 394-4-8 E1:2003 is used by conformance test laboratories, TETRA equipment manufacturers, gateway vendors, and operators or integrators who need to verify interoperability at the DMO gateway interface.

It is especially relevant for teams preparing approval tests, building automated TTCN-based test suites, reviewing PICS/PIXIT data, or checking whether a gateway handles call control, registration and short data correctly against the V+D network side.

What changed in SIST ETS 300 394-4-8 E1:2003 from the previous edition?

SIST ETS 300 394-4-8 E1:2003 is identical to ETS 300 394-4-8 Edition 1, the first edition of this sub-part. The document history identifies it as the June 1999 first edition.

Which standards are used with SIST ETS 300 394-4-8 E1:2003?

Standard	What it contributes
ETS 300 396-5	Technical requirements for DMO gateways, used throughout the test references.
ETS 300 396-8-3	PICS proforma for DM-GATE, used for selection expressions and test applicability.
ETS 300 392-2	V+D air interface requirements, used in mobility management references.
ETS 300 394-2-1	V+D protocol testing specification, source of several derived or reused test purposes.
ISO/IEC 9646-1	General concepts for conformance testing methodology.
ISO/IEC 9646-2	Abstract Test Suite specification rules.
ETS 300 406	ETSI methodology for protocol and profile conformance testing specifications.
ETS 300 394-4-1	Companion DMO part referenced in the TP naming convention examples.
ETS 300 394-4-4	Companion DMO part referenced in the TP naming convention examples.

What does the SIST ETS 300 394-4-8 E1:2003 document contain?

The document contains the TSS framework, TP naming rules, preamble and postamble MSCs, and the gateway test purposes for CM call control, SDS and MM. It also points to the lower-layer MLE, LLC and MAC test purposes that are taken from ETS 300 394-2-1.

The detailed test cases show the message exchanges to be observed, the state transitions to confirm, and the timer expiries to check. Annex A adds a short bibliography, and the closing pages give the publication history.

SLOVENSKI STANDARD
01-december-2003
Prizemni snopovni radio (TETRA) - Specifikacija za preskušanje skladnosti - 4. del:
Specifikacija za preskušanje protokola za neposredno obratovanje (DMO) ¬- 8.
poddel: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) za
neposredni prehod (DM-GATE)
Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 4: Protocol
testing specification for Direct Mode Operation (DMO); Sub-part 8: Test Suite Structure
and Test Purposes (TSS&TP) for Direct Mode Gateway (DM-GATE)
Ta slovenski standard je istoveten z: ETS 300 394-4-8 Edition 1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 394-4-8
TELECOMMUNICATION June 1999
STANDARD
Source: TETRA Reference: DE/TETRA-02009-4-8
ICS: 33.020
Key words: ICS, PICS, TETRA
Terrestrial Trunked Radio (TETRA);
Conformance testing specification;
Part 4: Protocol testing specification for
Direct Mode Operation (DMO);
Sub-part 8: Test Suite Structure and Test Purposes (TSS&TP)
for Direct Mode Gateway (DM-GATE)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: [e-mail] - http://www.etsi.org
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1999. All rights reserved.

Page 2
ETS 300 394-4-8: June 1999
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.

Page 3
ETS 300 394-4-8: June 1999
Contents
Foreword . 5
1 Scope. 7
2 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). 8
4.1 NWK layer or Layer 3 test groups . 9
4.2 Layer 2 test groups. 9
4.3 Test group description. 9
5 Introduction to Test Purposes (TPs). 9
5.1 Test purpose definition conventions. 10
5.1.1 Text and MSCs . 10
5.1.2 Preamble descriptions . 11
5.1.2.1 Preamble RegisterHome. 11
5.1.2.2 Preamble Idle_To_TX_Active_IC: From Idle state to Call
Active TX Occupation. 12
5.1.2.3 Preamble Idle_To_RX_Active: From Idle state to Call
Active RX Occupation . 13
5.1.2.4 Preamble Idle_to_TXR_Active . 13
5.1.3 Postamble descriptions. 14
5.1.3.1 Postamble DisconnectCall: From Call Active to Idle. 14
5.1.3.2 Postamble PST_RegisterHome_Visit: end registration
procedure . 14
5.1.3.3 Postamble SendRelease. 15
5.2 Test purpose naming conventions . 15
6 Test Purposes for the Call Control protocol of a DMO GATEWAY: GWCC . 16
6.1 Circuit Mode (CM) Call Control test purposes. 16
6.1.1 Call set up . 16
6.1.2 Call disconnection. 19
6.1.3 Call collision . 19
6.1.4 Control of transmission . 20
6.1.5 Timer tests . 22
6.2 Short Data Service (SDS) test purposes. 23
7 Test Purposes for the MM protocol of a DMO GATEWAY. 24
7.1 Capability test purposes . 24
7.2 Valid behaviour test purposes . 25
7.2.1 MSGW initiated registration procedures. 25
7.2.2 V+D initiated registration procedures. 26
7.2.3 Forwarding DM-MS registration procedures to SwMI. 26
8 Test Purposes for the MLE protocol of a DMO GATEWAY. 27
9 Test Purposes for the LLC protocol of a DMO GATEWAY . 27
10 Test Purposes for the MAC protocol of a DMO GATEWAY. 27

Page 4
ETS 300 394-4-8: June 1999
Annex A (informative): Bibliography.28
History.29

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

Page 6
ETS 300 394-4-8: June 1999
Blank page
Page 7
ETS 300 394-4-8: June 1999
1 Scope
This ETS contains the Test Specifications: Test Suite Structure and Test Purposes (TSS&TPs) and the
Abstract Test Suites (ATSs) to test conformity of products to the TETRA Direct Mode Operation (DMO)
protocols. This ETS is divided into several parts, each one dealing with one TSS&TP or one ATS for the
test of a layer 2 or layer 3 protocol for DMO.
This present sub-part 8 deals with TSS&TP for a GateWay (GW) connecting the MS-GW to the Switching
and Management Infrastructure (SwMI) of a V+D system.
NOTE: Sub-part 7 deals with TSS&TP for the other part of the DMO Gateway, which is a
Mobile Station (MS) connected to a Gateway (MS-GW).
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 [6] and
ISO/IEC 9646-2 [7], as well as the ETSI methodology for conformance testing, ETS 300 406 [8], are used
as the basis for the test methodology.
2 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] Void.
[2] ETS 300 396-5: "Terrestrial Trunked Radio (TETRA); Technical requirements
for Direct Mode Operation (DMO); Part 5: Gateways".
[3] ETS 300 396-8-3: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation
(DMO); Part 8: PICS proforma; Sub-part 3: Direct Mode Gateway (DM-GATE)".
[4] ETS 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 2: Air Interface (AI)".
[5] ETS 300 394-2-1: "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".
[6] ISO/IEC 9646-1 (1994): "Information technology; Open Systems
Interconnection; Conformance Testing Methodology and Framework; Part 1:
General Concepts". (See also ITU-T Recommendation X.290).
[7] ISO/IEC 9646-2 (1994): "Information technology; Open Systems
Interconnection; Conformance Testing Methodology and Framework; Part 2:
Abstract Test Suite Specification". (See also ITU-T Recommendation X.291).
[8] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".

Page 8
ETS 300 394-4-8: June 1999
3 Definitions and abbreviations
3.1 TETRA definitions
For the purposes of this ETS, the definitions given in ETS 300 396-5 [2] apply.
3.2 TETRA abbreviations
For the purposes of this ETS the following TETRA abbreviations apply:
CM Circuit Mode
DMCC Direct Mode Call Control
DMO Direct Mode of Operation
GCC Gateway Call Control
GMM Gateway Mobility Management
GW Gateway
LLC Logical Link Control
MAC Medium Access Control
MLE Mobile Link entity
MNI Mobile Network Identity
MS Mobile Station
MSC Message Sequence Chart
NWK NetWorK. Layer 3 of the TETRA protocol stack
SDS Short Data Services
TX Transmit
RX Receive
3.3 ISO 9646 definitions
For the purposes of this ETS the following ISO 9646-1 [6] 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 [6] 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
4 Test Suite Structure (TSS)
This TSS contains several components, some are specific of the gateway functionality and are new, while
others are derived or form a subset of other TETRA specifications. TPs are either included in the present
document, or are referenced into another document.

Page 9
ETS 300 394-4-8: June 1999
Here is the list of the TSS components:
at layer 3 also named NTW layer:
Gateway Call Control (GCC):
CM: derived from V+D CMCE TPs in ETS 300 394-2-1 [5];
SDS: derived from V+D CMCE TPs in ETS 300 394-2-1 [5].
Gateway Mobility Management (GMM): derived from V+D MM TPs in ETS 300 394-2-1 [5];
Mobile Link Entity (MLE): subset of V+D MLE in ETS 300 394-2-1 [5].
at layer 2:
LLC: subset of V+D LLC in ETS 300 394-2-1 [5];
MAC: subset of V+D MLE in ETS 300 394-2-1 [5].
4.1 NWK layer or Layer 3 test groups
The first level separates the NWK layer (or layer 3) in different protocols (Circuit mode, Short Data
Service). Next level splits protocol testing into functional test groups according to the type of testing:
Capability test (CA), Valid Behaviour (BV) and Timer tests (TI). Further level classifies the possible
operations in each protocol condition or state.
The following list defines the NWK layer test group names and identifiers used for those:
Gateway (DMO_GATE):
Gateway Call Control (GWCC):
Circuit mode (CM):
Call set-up (SU);
Call disconnection (CD);
Call collision (CC);
Control of Transmission (CT);
Timer Tests (TI);
Short Data Service (SDS).
Gateway Mobility Management (GWMM):
Capability tests (CA);
Valid Behaviour tests (BV).
Mobile link entity (MLE): derived from V+D MS MLE.
4.2 Layer 2 test groups
The first level of the Layer 2 test groups separates the test suite in functional test groups: CA, BV and TI.
The second level of the test subgroups is used to form a division of protocol requirements.
In the case of a Gateway, the layer 2 contains the LLC and the MAC, and the TSS as well as the TPs of
both protocols are derived from the V+D identical components. See ETS 300 394-2-1 [5].
4.3 Test group description
Capability (CA) tests provide limited testing that the observable capabilities of the IUT are in accordance
with the conformance requirements and the additional capabilities claimed in the PICS/PIXIT.
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.
Different timers 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.
5 Introduction to Test Purposes (TPs)
The test purposes for each test suite are defined in clause 6 of the present document for NWK layer and
MAC layer.
Page 10
ETS 300 394-4-8: June 1999
5.1 Test purpose definition conventions
5.1.1 Text and MSCs
Each TP is described in a table that contains the following information:
Table 0
TP-Name Reference: reference to the paragraph number of
The TP name is a unique identifier, specification ETS 300 396-5 [2] stating this conformance
specified according to the TP naming requirement.
conventions defined in the subclause For example: ETS 300 396-5 [2], 6.2.5.1
below. (it is also the name of the
corresponding test case)
Purpose purpose of the test itself, indicating for example the test performed against a
requirement of the protocol, described by this test purpose.
Example: test of changeover initiated from RX reservation state
Test description body of the test
visible action to be observed at PCO to declare that the IUT passes the test and
Pass criteria
conforms to the specifications
Selection expression based on ETS 300 396-8-3 [3] PICS statements, used to select or
deselect the corresponding test case according to the options of the
implementation.
Preamble "None" or name of the preamble procedure bringing the IUT from idle state to the
state required to run the test.
For example: idle_to_RX_reservation
Postamble "None" or name of the postamble to bring the IUT back to idle state,
for example: RX_occupation_to_idle.
The preambles and postambles are described using MSCs and are shown in the following paragraphs.

Page 11
ETS 300 394-4-8: June 1999
5.1.2 Preamble descriptions
Preambles are used to bring the IUT from the idle state to the state where the test takes place. As the
protocol has different options, as for instance the use of presence check or the absence of presence
check, there are several ways to reach a given state. The preamble has to be chosen according to the IUT
capabilities and the implemented options.
5.1.2.1 Preamble RegisterHome
MSC RegisterHome
IUT Tester
NOT REGISTERED
IMP_U_LOCATION_UPDATE_DEMAND
U_LOCATION_UPDATE_DEMAND
D_LOCATION_UPDATE_ACCEPT
REGISTERED
Page 12
ETS 300 394-4-8: June 1999
5.1.2.2 Preamble Idle_To_TX_Active_IC: From Idle state to Call Active TX Occupation
MSC Idle_To_TX_Active_IC
IUT Tester
RegisterHome
D_SETUP
U_CONNECT
D_CONNECT ACKNOWLEDGE
TX Granted
CALL ACTIVE
TX OCCUPATION
Page 13
ETS 300 394-4-8: June 1999
5.1.2.3 Preamble Idle_To_RX_Active: From Idle state to Call Active RX Occupation
MSC Idle_To_RX_Active_OC
IUT Tester
RegisterHome
IMP_U_SETUP
U_SETUP
D_CALL_PROCEEDING
D_CONNECT
TXGranted to Gateway
CALL ACTIVE
RX OCCUPATION
5.1.2.4 Preamble Idle_to_TXR_Active
MSC Idle_To_TXR_Active
IUT Tester
Idle_To_TX_Active_IC
D_TX_CEASED
CALL ACTIVE
TX RESERVATION
Page 14
ETS 300 394-4-8: June 1999
5.1.3 Postamble descriptions
Postambles are used to bring the IUT from the state ending the test, to the idle state.
5.1.3.1 Postamble DisconnectCall: From Call Active to Idle
MSC DisconnectCAll
IUT Tester
D_DISCONNECT
U_RELEASE
IDLE
5.1.3.2 Postamble PST_RegisterHome_Visit: end registration procedure
MSC PST_RegisterHome_Visit
IUT Tester
D_LOCATION_UPDATE_ACCEPT
REGISTERED
Page 15
ETS 300 394-4-8: June 1999
5.1.3.3 Postamble SendRelease
MSC SendRelease
IUT Tester
D_RELEASE
IDLE
5.2 Test purpose naming conventions
The identifier of the test purpose is built according to table 1.
Table 1: Test purpose naming convention
DMO//////
= test suite type MSMS MS to MS (see ETS 300 394-4-1 [])
MSGW MS connected to a gateway
GATE Gateway
REPx Repeater type x (see ETS 300 394-4-4 [])
= functional entity in a layer DMCC Direct Mode Call Control (layer 3)
MAC Upper MAC (layer 2)
= test group letters such as: abbreviation of the group name (optional)
CM Circuit Mode (layer 3)
SDS Short Data Service (layer 3)
tt = Type of testing CA Capability Tests
BV Valid Behaviour Tests
BI Invalid Behaviour Tests
TI Timer expiry and counter mismatch tests
= test subgroup letters abbreviation of the subgroup name
(optional)
= sequential number 01-99 Test Purpose Number

Page 16
ETS 300 394-4-8: June 1999
6 Test Purposes for the Call Control protocol of a DMO GATEWAY: GWCC
In this section, the IUT is a gateway. The tester is a SwMI of a V+D network. The interface between the
gateway and the SwMI is being tested.
6.1 Circuit Mode (CM) Call Control test purposes
6.1.1 Call set up
DMO_GATE_GWCC_CM_BV_SU_01 Reference: ETS 300 396-5 [2], 9.3.2.1, case iii)
Purpose Individual outgoing call set-up, TX granted to Gateway
The tester issues an implicit send to cause the IUT to initiate a call set-up.
Test description
The IUT sends U-SETUP PDU to the tester, which accepts it by sending the
D-CALL PROCEEDING then D-CONNECT PDU with TX granted to Gateway.
Pass criteria Check that the IUT reaches the CALL ACTIVE state. To do it, the tester
sends D-DISCONNECT PDU to the IUT, which answers with U-RELEASE
PDU).
Selection A.39/4 Accept Call from DM without presence check
ETS 300 396-8-3 [3]
Preamble RegisterHome
Postamble DisconnectCall
DMO_GATE_GWCC_CM_BV_SU_02 Reference: ETS 300 396-5 [2], 9.3.2.1, case i)
Purpose Individual outgoing call set-up, TX granted to called
Test description The tester issues an implicit send to cause the IUT to initiate a call set-up.
The IUT sends U-SETUP PDU to the tester, which accepts it by sending the
D-CALL PROCEEDING then D-CONNECT PDU with TX granted to called.
Check that the IUT reaches the CALL ACTIVE state. To do it, the tester
Pass criteria
sends D-DISCONNECT PDU to the IUT, which answers with U-RELEASE
PDU)
A.39/4 Accept Call from DM without presence check
Selection
ETS 300 396-8-3 [3]
RegisterHome
Preamble
Postamble DisconnectCall
DMO_GATE_GWCC_CM_BV_SU_03 Reference: ETS 300 396-5 [2], 9.3.2.1, case ii)
Individual outgoing call set-up, TX granted to no party
Purpose
Test description The tester issues an implicit send to cause the IUT to initiate a call set-up.
The IUT sends U-SETUP PDU to the tester, which accepts it by sending the
D-CALL PROCEEDING then D-CONNECT PDU with TX granted to no party.
Pass criteria Check that the IUT reaches the CALL ACTIVE state. To do it, the tester
sends D-DISCONNECT PDU to the IUT, which answers with U-RELEASE
PDU)
Selection A.39/4 Accept Call from DM without presence check
ETS 300 396-8-3 [3]
Preamble RegisterHome
DisconnectCall
Postamble
Page 17
ETS 300 394-4-8: June 1999
DMO_GATE_GWCC_CM_BV_SU_04 Reference: ETS 300 396-5 [2], 9.3.1.1
Purpose Individual incoming call set-up, TX granted to V+D (calling)
The tester issues D-SETUP PDU.
Test description
Pass criteria 1 Check that the IUT accepts it by sending the U-CONNECT PDU.
Test description The tester issues D-CONNECT ACKNOWLEDGE PDU with TX granted to
V+D.
Check that the IUT reaches the CALL ACTIV
...