Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 4: Protocol testing specification for Direct Mode Operation (DMO); Sub-part 7: Test Suite Structure and Test Purposes (TSS&TP) for Mobile Station to GateWay (MS-GW) Air Interface (AI)

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

Prizemni snopovni radio (TETRA) - Specifikacija za preskušanje skladnosti - 4. del: Specifikacija za preskušanje protokola za neposredno obratovanje (DMO) ¬- 7. poddel: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) za radijski vmesnik (AI) med mobilno postajo in prehodom (MS-GW)

General Information

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
ETS 300 394-4-7 E1:2003
English language
45 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 394-4-7 E1:2003
01-december-2003
Prizemni snopovni radio (TETRA) - Specifikacija za preskušanje skladnosti - 4. del:
Specifikacija za preskušanje protokola za neposredno obratovanje (DMO) ¬- 7.
poddel: Zgradba preskušalnega niza in nameni preskušanja (TSS&TP) za radijski
vmesnik (AI) med mobilno postajo in prehodom (MS-GW)
Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 4: Protocol
testing specification for Direct Mode Operation (DMO); Sub-part 7: Test Suite Structure
and Test Purposes (TSS&TP) for Mobile Station to GateWay (MS-GW) Air Interface (AI)
Ta slovenski standard je istoveten z: ETS 300 394-4-7 Edition 1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST ETS 300 394-4-7 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 394-4-7 E1:2003

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

SIST ETS 300 394-4-7 E1:2003
EUROPEAN ETS 300 394-4-7
TELECOMMUNICATION June 1999
STANDARD
Source: TETRA Reference: DE/TETRA 02009-4-7
ICS: 33.020
Key words: testing, protocol, radio, TETRA
Terrestrial Trunked Radio (TETRA);
Conformance testing specification;
Part 4: Protocol testing specification for
Direct Mode Operation (DMO);
Sub-part 7: Test Suite Structure and Test Purposes (TSS&TP)
for Mobile Station to GateWay (MS-GW) Air Interface (AI)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1999. All rights reserved.

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

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

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

SIST ETS 300 394-4-7 E1:2003
Page 3
ETS 300 394-4-7: 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). 10
5.1 Test purpose definition conventions. 10
5.1.1 Text and MSCs . 10
5.1.2 Preamble descriptions . 10
5.1.2.1 Preamble registration . 11
5.1.2.2 Preamble idle_to_TX_occupation: From Idle state to Call
Active TX Occupation. 13
5.1.2.3 Preamble idle_to_RX_occupation: From Idle state to Call
Active RX Occupation . 14
5.1.2.4 Preamble idle_to_RX_reservation . 16
5.1.2.5 Preamble idle_channel_occupation . 18
5.1.3 Layer 3 postamble descriptions . 19
5.1.3.1 Postamble TX_occupation_to_idle: From Call Active TX
Occupation state to Idle. 20
5.1.3.2 Postamble RX_occupation_to_idle: From Call Active RX
Occupation state to Idle. 20
5.1.3.3 Postamble RX_reservation_to_idle: From Call Active RX
Reserved state to Idle . 21
5.2 Test purpose naming conventions . 21
6 Test Purposes for the DMCC protocols of a DMO MS-GW . 22
6.1 DMCC Circuit Mode (CM) tests. 22
6.1.1 MS-GW CM capability tests. 22
6.1.2 MS-GW CM valid behaviour tests. 22
6.1.2.1 The IUT is in IDLE state, DMO channel is free . 23
6.1.2.2 IUT is in idle state, DMO channel is busy. 25
6.1.2.3 IUT is in TX occupation state . 25
6.1.2.4 IUT is in RX occupation state. 27
6.1.2.5 IUT is in RX reservation state . 28
6.1.3 MS-GW CM timer tests. 29
6.1.3.1 DT301 Response to DM-GSETUP timer . 29
6.1.3.2 DT302 Response DM-GCONNECT to DM-GSETUP
timer . 30
6.1.3.3 DT311 Call transaction timer. 30
6.1.3.4 DT308 Response DM-GPRE ACCEPT after receiving
DM-GACK . 30
6.1.3.5 DT309 Response DM-GTX ACCEPT after receiving DM-
GACK . 31
6.2 DMCC Short data service (SDS). 31
6.2.1 MS-GW SDS Capability tests . 31

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

SIST ETS 300 394-4-7 E1:2003
Page 4
ETS 300 394-4-7: June 1999
6.2.2 MS-GW SDS Valid behaviour tests.31
6.2.2.1 IUT is in idle state, channel is free.31
6.2.2.2 IUT is in idle state, channel is busy .33
6.2.2.3 IUT is in state TX occupation.34
6.2.2.4 IUT is in RX occupation state .34
6.2.2.5 IUT is in RX reservation state.36
6.2.3 MS-GW SDS Timer tests .37
6.2.3.1 DT316 Response to DM-SDS DATA timer.37
7 Test Purposes for the DMMM protocol of a DMO MS-GW.38
8 Test Purposes for the MAC protocol of a DMO MS-GW .39
8.1 MS-GW MAC capability tests .39
8.2 MS-GW MAC valid behaviour tests .39
8.2.1 DM channel usage procedures .39
8.2.2 Signalling messages procedures .41
8.3 MS-GW MAC timer tests .43
Annex A (informative): Bibliography.44
History.45

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

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

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

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

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

SIST ETS 300 394-4-7 E1:2003
Page 7
ETS 300 394-4-7: 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 7 deals with TSS&TP for a Mobile Station (MS) connected to a Gateway (MS-GW).
NOTE: Sub-part 8 deals with TSS&TP for the other part of the DMO Gateway, which is a
GateWay (GW) connecting the MS-GW to the Switching and Management
Infrastructure (SwMI) of a Voice plus Data (V+D) system.
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 [5] and
ISO/IEC 9646-2 [6], as well as the ETSI methodology for conformance testing, ETS 300 406 [7], 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: Protocol Implementation Conformance Statement (PICS)
proforma specification; Sub-part 3: Gateway Air Interface (AI)".
[4] ETS 300 394-4-1: "Terrestrial Trunked Radio (TETRA);Conformance testing
specification; Part 4: Protocol testing specification for Direct Mode Operation
(DMO); Sub-part 1: Test Suite Structure and Test Purposes (TSS&TP) for
Mobile Station to Mobile Station (MS-MS) Air Interface (AI)".
[5] ISO/IEC 9646-1 (1994): "Information technology; Open Systems
Interconnection; Conformance testing methodology and framework; Part 1:
General concepts". (See also ITU-T Recommendation X.290 (1991)).
[6] ISO/IEC 9646-2 (1994): "Information technology; Open Systems
Interconnection; Conformance testing methodology and framework;
Part 2: Abstract Test Suite specification". (See also ITU-T
Recommendation X.291 (1991)).
[7] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".

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

SIST ETS 300 394-4-7 E1:2003
Page 8
ETS 300 394-4-7: 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
DMMM Direct Mode Mobility Management
DMO Direct Mode of Operation
FCS Frame Check Sequence
GW Gateway
MAC Medium Access Control
MNI Mobile Network Identity
MS Mobile Station
NWK Network. Layer 3 of the TETRA protocol stack
SDS Short Data Services
SDU Service Data Unit
TX Transmit
RX Receive
3.3 ISO 9646 definitions
For the purposes of this ETS the following ISO/IEC 9646-1 [5] 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/IEC 9646-1 [5] 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 this ETS, or
are referenced from another document.
Here is the list of the TSS components for the part dealing with an MS connected to a GateWay
(DMO MS-GW):
at layer 3 also named NWK layer:
Direct Mode Call Control (DMCC):
Circuit Mode (CM): new component;
Short Data Service (SDS): derived from DMO MS-MS TPs in ETS 300 394-4-1 [4].
Direct Mode Mobility Management (DMMM): new component.
at layer 2:
MAC layer: derived from DMO MS-MS TPs in ETS 300 394-4-1 [4].

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

SIST ETS 300 394-4-7 E1:2003
Page 9
ETS 300 394-4-7: June 1999
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:
MS connected to a gateway GW (DMO_MSGW_NWK):
Direct Mode Call Control (DMCC):
Circuit mode (CM):
Capability tests (CA);
Valid Behaviour tests (BV):
from Idle state(ID);
from Idle state, channel busy (IB);
from TX occupation State (TXO);
from RX occupation State (RO);
from TX Reservation (TR);
from RX Reservation State (RR).
Timer Tests (TI).
Short Data Service (SDS):
Capability tests (CA);
Valid Behaviour tests (BV):
from Idle state(ID);
from Idle state, channel busy (IB);
from RX Occupation State (RO);
from TX Reservation State (TR);
from RX Reservation State (RR).
Timer Tests (TI).
Direct Mode Mobility Management (DMMM).
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 an MS connected to a gateway, layer 2 contains the MAC only and is structured as follows:
MS connected to a gateway MAC layer (DMO_DMO_MSGW_MAC):
Capability tests (CA);
Valid behaviour tests (BV):
Channel usage (CU);
Signalling messages (SM);
Traffic mode (TM).
Timer tests (TI).
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.

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

SIST ETS 300 394-4-7 E1:2003
Page 10
ETS 300 394-4-7: June 1999
5 Introduction to Test Purposes (TPs)
The test purposes for each test suite are defined in clause 6 of this ETS for NWK layer and MAC layer.
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
Pass criteria visible action to be observed at PCO to declare that the IUT passes the test and
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.
"None" or name of the postamble to bring the IUT back to idle state,
Postamble
for example: RX_occupation_to_idle.
The preambles and postambles are described using MSCs and are shown in the following paragraphs.
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.

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

SIST ETS 300 394-4-7 E1:2003
Page 11
ETS 300 394-4-7: June 1999
5.1.2.1 Preamble registration
Without registration invitation
MSC Registration_uninvited_supp
IUT Tester
/*
NOT
PREAMBLE:
REGISTERED
Bring the IUT from Not Registered state to
Registration Accepted state when
un−invited registration is supported
< IMP!DM_REGISTER_REQUEST>
*/
DM_GREGISTER_REQUEST
DM_GREGISTER ACCEPT
REGISTRATION
ACCEPTED

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

SIST ETS 300 394-4-7 E1:2003
Page 12
ETS 300 394-4-7: June 1999
With registration invitation
MSC Registration_invited_supp
IUT Tester
/*
NOT
PREAMBLE:
REGISTERED
Bring the IUT from Not Registered state to
Registration Accepted state when
invited registration is supported
*/
DPRES_SYNC
layer 2 PDU − registration invited
DM_GREGISTER_REQUEST
DM_GREGISTER ACCEPT
REGISTRATION
ACCEPTED

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

SIST ETS 300 394-4-7 E1:2003
Page 13
ETS 300 394-4-7: June 1999
5.1.2.2 Preamble idle_to_TX_occupation: From Idle state to Call Active TX Occupation
Without presence check
MSC Idle_to_TX_OCCUPATION_npc
IUT Tester
/*
Registration
PREAMBLE:
preamble
Bring the IUT from IDLE state to
TX_OCCUPATION state
*/
IDLE

DM_GSETUP
DM_GACK
DM_GCONNECT
DM_SETUP
TX_OCCUPATION

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

SIST ETS 300 394-4-7 E1:2003
Page 14
ETS 300 394-4-7: June 1999
5.1.2.3 Preamble idle_to_RX_occupation: From Idle state to Call Active RX Occupation
With presence check
MSC Idle_to_RX_RESERVATION_wpc
IUT Tester
/*
PREAMBLE: idle_to_RX_occupation
Bring the IUT from IDLE state to
RX_RESERVATION state when
set−up with presence check is
supported
*/
RX_OCCUPATION
DM_TX_CEASED
RX_RESERVATION

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

SIST ETS 300 394-4-7 E1:2003
Page 15
ETS 300 394-4-7: June 1999
Without presence check
MSC Idle_to_RX_OCCUPATION_npc
IUT Tester
/*
PREAMBLE:
IDLE
Bring the IUT from IDLE state to
RX_OCCUPATION state when
set−up without presence check
is supported
DM_SETUP
*/
RX_OCCUPATION

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

SIST ETS 300 394-4-7 E1:2003
Page 16
ETS 300 394-4-7: June 1999
5.1.2.4 Preamble idle_to_RX_reservation
By passing through RX occupation state
MSC Idle_to_RX_RESERVATION_wpc
IUT Tester
/*
PREAMBLE: idle_to_RX_occupation
Bring the IUT from IDLE state to
RX_RESERVATION state when
set−up with presence check is
supported
*/
RX_OCCUPATION
DM_TX_CEASED
RX_RESERVATION

---------------------- Page: 18 ----------------------

SIST ETS 300 394-4-7 E1:2003
Page 17
ETS 300 394-4-7: June 1999
By passing through TX occupation state
MSC Idle_to_RX_RESERVATION_TX
IUT Tester
/*
idle_to_TX_occupation
PREAMBLE:
Bring the IUT from IDLE state to
RX_RESERVATION state when
set−up supported
*/
TX_OCCUPATION
< IMP!DM_TX_CEASED>
DM_TX_CEASED
RX_RESERVATION

---------------------- Page: 19 ----------------------

SIST ETS 300 394-4-7 E1:2003
Page 18
ETS 300 394-4-7: June 1999
5.1.2.5 Preamble idle_channel_occupation
Without presence check
MSC Idle_channel_occupation_wpc
MS’ Tester IUT
/*
PREAMBLE:
Set up the channel to be occupied
with the tester as the master of
IDLE
the channel while the IUT is still
in state IDLE.
*/
DM_SETUP_PRES
DM_CONNECT
DM_CONNECT_ACK
/*
Channel occupied
*/

---------------------- Page: 20 ----------------------

SIST ETS 300 394-4-7 E1:2003
Page 19
ETS 300 394-4-7: June 1999
With presence check
MSC Idle_channel_occupation_npc
IUT Tester MS’
IDLE
/*
PREAMBLE:
Set up the channel to be occupied
with the tester as the master of
the channel while the IUT is still
in state IDLE.
DM_SETUP
*/
/*
Channel occupied
*/
5.1.3 Layer 3 postamble descriptions
Postambles are used to bring the IUT from the state ending the test, to the idle state.

---------------------- Page: 21 ----------------------

SIST ETS 300 394-4-7 E1:2003
Page 20
ETS 300 394-4-7: June 1999
5.1.3.1 Postamble TX_occupation_to_idle: From Call Active TX Occupation state to Idle
MSC From_TX_OCCUPATION_to_IDLE
IUT Tester
TX OCCUPATION
/*
POSTAMBLE:
Bring the IUT from 
TX OCCUPATION state to
IDLE state caused by a
DMCC_RELEASE
*/
DM_RELEASE
IDLE
5.1.3.2 Postamble RX_occupation_to_idle: From Call Active RX Occupation state to Idle
MSC From_RX_OCCUPATION_to_IDLE
IUT Tester
RX OCCUPATION
/*
POSTAMBLE:
Bring the IUT from 
RX OCCUPATION state to
IDLE state
*/
IDLE

---------------------- Page: 22 ----------------------

SIST ETS 300 394-4-7 E1:2003
Page 21
ETS 300 394-4-7: June 1999
5.1.3.3 Postamble RX_reservation_to_idle: From Call Active RX Reserved state to Idle
MSC From_RX_RESERVED_to_IDLE
IUT Tester
RX RESERVED
/*
POSTAMBLE:
Bring the IUT from 
RX RESERVED state to
IDLE state
*/
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 [4])
MSGW MS connected to a gateway
GATE Gateway
REPx
Repeater type x (see ETS 300 394-4-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: 23 ----------------------

SIST ETS 300 394-4-7 E1:2003
Page 22
ETS 300 394-4-7: June 1999
6 Test Purposes for the DMCC protocols of a DMO MS-GW
In this clause, the IUT is an MS connected to a gateway. The tester is a gateway. The interface between
the MS and the gateway is being tested.
6.1 DMCC Circuit Mode (CM) tests
Test group objective: To test the behaviour of the DMCC CM entity of the IUT.
Condition: IUT implements the CM.
6.1.1 MS-GW CM capability tests
To test the basic capabilities of the CM module of the IUT, when operating in group address mode
(without presence check) or in individual address mode (with or without presence check).
DMO_MSGW_DMCC_CM_CA_01 Reference: ETS 300 396-5 [2], 6.2.1.1, 6.2.4.1
Purpose Set-up and release a group call.
The tester issues an implicit send to cause the IUT to initiate a group call.
Test description
Pass criteria 1 The IUT sends DM-GSETUP to the tester.
Test description The tester sends back a DM-GACK followed by DM-GCONNECT.
The IUT sends DM-SETUP PDU to the tester.
Pass criteria 2
Test description The tester issues an implicit send to cause the IUT to initiate a call release.
The IUT sends DM-RELEASE PDU to the tester.
Pass criteria 3
Selection A.7/1 Initiate call set-up on group address.
ETS 300 396-8-3 [3]
Preamble None.
Postamble None.
DMO_MSGW_DMCC_CM_CA_02 Reference: ETS 300 396-5 [2], 6.2.1.1, 6.2.4.1
Establish and terminate an individual call
Purpose
Test description The tester issues an implicit send to cause the IUT to initiate an individual
call.
The IUT sends DM-GSETUP to the tester.
Pass criteria 1
Test description The tester sends back a DM-GACK followed by DM-GCONNECT.
Pass criteria 2 The IUT sends DM-SETUP PDU to the tester.
The tester issues an implicit send to cause the IUT to initiate a call release.
Test description
Pass criteria 3 The IUT sends DM-RELEASE PDU to the tester.
A.7/3 Initiate call set-up on individual address.
Selection
ETS 300 396-8-3 [3]
None.
Preamble
Postamble None.

---------------------- Page: 24 ----------------------

SIST ETS 300 394-4-7 E1:2003
Page 23
ETS 300 394-4-7: June 1999
6.1.2 MS-GW CM valid behaviour tests
6.1.2.1 The IUT is in IDLE state, DMO channel is free
DMO_MSGW_DMCC_CM_BV_ID_01 Reference: ETS 300 396-5 [2], 6.2.2.1
Receive an incoming group call without presence check.
Purpose
Test description The tester sends DM-SETUP PDU to the IUT, which brings the IUT to CALL
ACTIVE RX OCCUPATION state.
To check that IUT reaches CALL ACTIVE RX OCCUPATION state, the
Pass criteria
tester sends DM-TX CEASED which brings the IUT to CALL ACTIVE RX
RESERVATION state. Then, during the reservation period, the tester issues
an implicit send to cause the IUT to issue a call set-up. Verify that before
attempting the call set-up, the IUT issues a DM-GTX REQUEST to initiate a
changeover.
Selection A.8/1 Accept call without presence check.
ETS 300 396-8-3 [3]
Preamble None.
Tester issues a DM-GREJECT followed by RX_Reservation_to_idle.
Postamble
DMO_MSGW_DMCC_CM_BV_ID_02 Reference: ETS 300 396-5 [2], 6.2.2.2
Purpose Receive an incoming individual call with presence check.
Test description The tester sends DM-SETUP PRES to the IUT which sends back DM-
CONNECT. The tester responds with DM-CONNECT ACK. This brings the
IUT to CALL ACTIVE RX OCCUPATION state.
To check that IUT reaches CALL ACTIVE RX OCCUPATION state, the
Pass criteria
tester sends DM-TX CEASED which brings the IUT to "call active RX
reservation" state. Then, during the reservation period, the tester issues an
implicit send to cause the IUT to issue a call set-up. Verify that before
attempting the call set-up, the IUT issues a DM-GTX REQUEST to initiate a
changeover.
Selection A.8/2 Accept call with presence check.
ETS 300 396-8-3 [3]
Preamble None.
Tester issues a DM-REJECT followed by RX_Reservation_to_idle.
Postamble
DMO_MSGW_DMCC_CM_BV_ID_03 Reference: ETS 300 396-5 [2], 6.2.1.1
Purpose Release
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.