SIST ETS 300 396-8-3 E1:2003

SLOVENSKI STANDARD
01-december-2003
3UL]HPQLVQRSRYQLUDGLR7(75$7HKQLþQH]DKWHYH]DQHSRVUHGQRREUDWRYDQMH
'02GHO,]MDYDRVNODGQRVWLL]YHGEHSURWRNROD3,&63URIRUPD
VSHFLILNDFLMDSRGGHO3UHKRGUDGLMVNHJDYPHVQLND$,
Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation
(DMO); Part 8: Protocol Implementation Conformance Statement (PICS) proforma
specification; Sub-part 3: Gateway Air Interface (AI)
Ta slovenski standard je istoveten z: ETS 300 396-8-3 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 396-8-3
TELECOMMUNICATION June 1999
STANDARD
Source: TETRA Reference: DE/TETRA-02007-8-3
ICS: 33.020
Key words: ICS, PICS, TETRA
Terrestrial Trunked Radio (TETRA);
Technical requirements for Direct Mode Operation (DMO);
Part 8: Protocol Implementation Conformance Statement (PICS)
proforma specification;
Sub-part 3: Gateway 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 2
ETS 300 396-8-3: 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 396-8-3: June 1999
Contents
Foreword . 7
Introduction . 7
1 Scope. 9
2 References. 9
3 Definitions and abbreviations. 9
3.1 Definitions. 9
3.2 Abbreviations. 10
4 Conformance to this PICS proforma specification. 10
Annex A (normative): Protocol ICS proforma (PICS) for ETS 300 396-5 . 11
A.1 Guidance for completing the PICS proforma.11
A.1.1 Purposes and structure .11
A.1.2 Abbreviations and conventions. 11
A.1.3 Instructions for completing the PICS proforma . 13
A.2 Identification of the implementation . 13
A.2.1 Date of the statement . 13
A.2.2 Implementation Under Test (IUT) identification. 13
A.2.3 System Under Test (SUT) identification. 13
A.2.4 Product supplier. 14
A.2.5 Client (if different from product supplier) . 14
A.2.6 PICS contact person. 14
A.3 Identification of the Protocol. 15
A.4 Global statement of conformance. 15
A.5 Types . 15
A.6 DM-MS. 16
A.6.1 DM-MS Layer 3 . 16
A.6.1.1 Direct Mode Call Control (DMCC). 16
A.6.1.1.1 DMCC major capabilities. 16
A.6.1.1.2 Circuit mode call. 16
A.6.1.1.3 Circuit mode call set-up. 17
A.6.1.1.4 Circuit mode services offered. 18
A.6.1.1.5 Short data services. 18
A.6.1.1.6 Type of short data service. 18
A.6.1.1.7 Data transmission . 20
A.6.1.1.8 SDS user defined data . 20
A.6.1.1.9 DMCC PDUs . 21
A.6.1.2 Direct Mode Mobility Management (DMMM) . 22
A.6.1.2.1 DMMM major capabilities. 22
A.6.1.2.2 DMMM PDUs . 22
A.6.1.3 Layer 3 constants in DM-MS. 23
A.6.1.4 Layer 3 timers in DM-MS . 23
A.6.2 DM-MS MAC Layer . 25
A.6.2.1 DM-MAC features . 25

Page 4
ETS 300 396-8-3: June 1999
A.6.2.2 DM-MAC procedures.25
A.6.2.3 DM-MAC PDUs .30
A.6.2.4 DM-MAC generated messages.30
A.6.2.5 Layer 2 constants in DM-MS .31
A.6.2.6 Layer 2 timers in DM-MS.33
A.7 Gateway .34
A.7.1 Gateway Layer 3.34
A.7.1.1 Gateway call control .34
A.7.1.1.1 Gateway circuit mode call control.34
A.7.1.1.2 Gateway circuit mode call types .35
A.7.1.1.3 Gateway circuit mode services over DMO interface.36
A.7.1.1.4 Gateway short data services .37
A.7.1.1.5 Gateway type of short data service .37
A.7.1.1.6 Data transmission.38
A.7.1.1.7 Gateway call control PDUs .38
A.7.1.2 Gateway Mobility Management (MM).41
A.7.1.2.1 MM major capabilities.41
A.7.1.2.2 Gateway DM registration .41
A.7.1.2.3 Gateway MM PDUs .41
A.7.1.3 Layer 3 constants in gateway .42
A.7.1.4 Layer 3 DM timers in gateway.42
A.7.2 Gateway DM Layer 2 .43
A.7.2.1 Gateway DM-MAC features .43
A.7.2.2 Gateway DM-MAC procedures .44
A.7.2.3 Gateway DM-MAC PDUs .50
A.7.2.4 Gateway MAC generated messages.50
A.7.2.5 Layer 2 DM constants in gateway .50
A.7.2.6 Layer 2 DM timers in gateway.53
A.7.3 Gateway V+D.54
A.7.3.1 Gateway V+D MLE.54
A.7.3.2 Gateway V+D LLC.54
A.7.3.3 Gateway V+D MAC .54
A.8 PDUs.54
A.8.1 Layer 3 PDUs.54
A.8.1.1 Circuit mode PDU parameters .54
A.8.1.1.1 DM-SETUP.55
A.8.1.1.2 DM-SETUP PRES .55
A.8.1.1.3 DM-CONNECT .56
A.8.1.1.4 DM-DISCONNECT .56
A.8.1.1.5 DM-CONNECT ACK.56
A.8.1.1.6 DM-OCCUPIED.57
A.8.1.1.7 DM-RELEASE .57
A.8.1.1.8 DM-TX CEASED .57
A.8.1.1.9 DM-TX REQUEST.58
A.8.1.1.10 DM-TX ACCEPT.58
A.8.1.1.11 DM-PREEMPT.58
A.8.1.1.12 DM-PRE ACCEPT.58
A.8.1.1.13 DM-REJECT.59
A.8.1.1.14 DM-INFO .59
A.8.1.1.15 DM-SDS UDATA .59
A.8.1.1.16 DM-SDS DATA.60
A.8.1.1.17 DM-SDS ACK .61
A.8.1.1.18 DM-GSETUP .61
A.8.1.1.19 DM-GCONNECT .62
A.8.1.1.20 DM-GACK.62
A.8.1.1.21 DM-GRELEASE.62
A.8.1.1.22 DM-GTX REQUEST.63
A.8.1.1.23 DM-GTX ACCEPT.63
A.8.1.1.24 DM-GPREEMPT.64
A.8.1.1.25 DM-GPRE ACCEPT .64
A.8.1.1.26 DM-GREJECT .64

Page 5
ETS 300 396-8-3: June 1999
A.8.1.2 Mobility management PDU parameters. 64
A.8.1.2.1 DM-GREGISTER REQUEST. 65
A.8.1.2.2 DM-GREGISTER ACCEPT. 65
A.8.1.2.3 DM-GREGISTER REJECT . 65
A.8.1.2.4 DM-GREGISTER CANCEL. 66
A.8.1.2.5 DM-GCANCEL ACK. 66
A.8.1.3 Specifics gateway PDU parameters over V+D . 66
A.8.1.3.1 D-ATTACH/DETACH DM-MS IDENTITY
ACKNOWLEDGEMENT . 66
A.8.1.3.2 D-CALL PROCEEDING . 67
A.8.1.3.3 D-CONNECT. 67
A.8.1.3.4 D-CONNECT ACK . 68
A.8.1.3.5 D-LOCATION UPDATE ACCEPT. 68
A.8.1.3.6 D-LOCATION UPDATE REJECT . 68
A.8.1.3.7 D-RELEASE. 69
A.8.1.3.8 D-SETUP. 69
A.8.1.3.9 D-SDS DATA. 70
A.8.1.3.10 D-STATUS . 70
A.8.1.3.11 D-TX CEASED . 70
A.8.1.3.12 D-TX GRANTED . 71
A.8.1.3.13 D-TX INTERRUPT . 71
A.8.1.3.14 U-ATTACH/DETACH DM-MS IDENTITY . 71
A.8.1.3.15 U-CONNECT. 72
A.8.1.3.16 U-LOCATION UPDATE DEMAND. 72
A.8.1.3.17 U-DISCONNECT. 72
A.8.1.3.18 U-SDS DATA. 73
A.8.1.3.19 U-SETUP. 73
A.8.1.3.20 U-STATUS . 74
A.8.1.3.21 U-TX CEASED . 74
A.8.1.3.22 U-TX DEMAND . 74
A.8.2 Layer 2 PDUs . 74
A.8.2.1 DM-MAC PDU parameters . 74
A.8.2.1.1 DMAC-SYNC in SCH/S. 75
A.8.2.1.2 DMAC-SYNC in SCH/H. 75
A.8.2.1.3 DMAC-DATA. 76
A.8.2.1.4 DMAC-FRAG. 76
A.8.2.1.5 DMAC-END. 76
A.8.2.1.6 DMAC-U SIGNAL. 76
A.8.2.1.7 DPRES-SYNC in SCH/S . 77
A.8.2.1.8 DPRES-SYNC in SCH/H. 77
A.8.2.2 DM-MAC generated message parameters. 78
A.8.2.2.1 DM-RESERVED. 78
A.8.2.2.2 DM-SDS OCCUPIED . 78
A.8.2.2.3 DM-TIMING ACK . 78
History . 79

Page 6
ETS 300 396-8-3: June 1999
Blank page
Page 7
ETS 300 396-8-3: 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 is a multi-part standard and will consist of the following parts:
Part 1: "General network design";
Part 2: "Radio aspects";
Part 3: "Mobile Station to Mobile Station (MS-MS) Air Interface (AI) protocol";
Part 4: "Repeater type 1";
Part 5: "Gateways";
Part 6: "Security";
Part 7: "Repeater type 2";
Part 8: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 9: "Service and Description Language (SDL) model".
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
Introduction
To evaluate conformance of a particular implementation, it is necessary to have a statement of which
capabilities and options have been implemented for a telecommunication specification. Such a statement
is called an Implementation Conformance Statement (ICS).

Page 8
ETS 300 396-8-3: June 1999
Blank page
Page 9
ETS 300 396-8-3: June 1999
1 Scope
This European Telecommunication Standard (ETS) provides the Protocol Implementation Conformance
Statement (PICS) proforma for the TETRA Direct Mode Operation (DMO) Gateway Air Interface (AI)
protocol, defined in ETS 300 396-5 [1] in compliance with the relevant requirements, and in accordance
with the relevant guidance given in ISO/IEC 9646-7 [7] and ETS 300 406 [5].
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] ETS 300 396-5 (1996): "Terrestrial Trunked Radio (TETRA); Technical
requirements for Direct Mode Operation (DMO); Part 5: Gateways".
[2] ETS 300 396-3: "Terrestrial Trunked Radio (TETRA); Technical requirements
for Direct Mode Operation (DMO); Part 3: Mobile Station to Mobile Station
(MS-MS) Air Interface (AI) protocol".
[3] ETS 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 2: Air Interface (AI)".
[4] ETS 300 392-14: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 14: Protocol Implementation Conformance Statement (PICS) proforma
specification".
[5] ETS 300 406 (1995): "Methods for testing and Specification (MTS); Protocol and
profile conformance testing specifications; Standardization methodology".
[6] ISO/IEC 9646-1 (1994): "Information technology; Open systems interconnection;
Conformance testing methodology and framework; Part 1: General concepts".
[7] ISO/IEC 9646-7 (1995): "Information technology; Open systems interconnection;
Conformance testing methodology and framework; Part 7: Implementation
Conformance Statements".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
- terms defined in ETS 300 396-5 [1];
- terms defined in ISO/IEC 9646-1 [6] and in ISO/IEC 9646-7 [7].
In particular, the following terms defined in ISO/IEC 9646-1 [6] apply:
Implementation Conformance Statement (ICS): statement made by the supplier of an implementation
or system claimed to conform to a given specification, stating which capabilities have been implemented.
The ICS can take several forms: protocol ICS, profile ICS, profile specific ICS, information object ICS, etc.
ICS proforma: document, in the form of a questionnaire, which when completed for an implementation or
system becomes an ICS
Protocol ICS (PICS): ICS for an implementation or system claimed to conform to a given protocol
specification
Page 10
ETS 300 396-8-3: June 1999
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AI Air Interface
CMCE Circuit Mode Control Entity
CONP Connection Oriented Network Protocol
DMCC Direct Mode Call Control
DM-MAC Direct Mode Medium Access Control
DMMM Direct Mode Mobility Management
DM-MS Direct Mode Mobile Station
DMO Direct Mode Operation
FCS Frame Check Sequence
ICS Implementation Conformance Statement
IUT Implementation Under Test
KSG Key Stream Generator
LLC Logical Link Control
MAC Medium Access Control
MLE Mobile Link Entity
MM Mobility management
MNI Mobile Network Identity
MS Mobile Station
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
SCLNP Specific Connection Less Network Protocol
SCS System Conformance Statement
SDS Short Data Service
SSI Short Subscriber Identity
SUT System Under Test
SwMI Switching and Management Infrastructure
TPNI Transmitting Party Number Identification
TSI TETRA Subscriber Identity
URT Usage Restriction Type
V+D Voice plus Data
4 Conformance to this PICS proforma specification
If it claims to conform to this ETS, the actual PICS proforma to be filled in by a supplier shall be technically
equivalent to the text of the PICS proforma given in annex A, and shall preserve the numbering/naming
and ordering of the proforma items.
A PICS which conforms to this ETS shall be a conforming PICS proforma completed in accordance with
the guidance for completion given in clause A.1.

Page 11
ETS 300 396-8-3: June 1999
Annex A (normative): Protocol ICS proforma (PICS) for ETS 300 396-5
Notwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grants that
users of this ETS may freely reproduce the PICS proforma in this annex so that it can be used for its
intended purposes and may further publish the completed PICS.
A.1 Guidance for completing the PICS proforma
A.1.1 Purposes and structure
The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of
the requirements defined in ETS 300 396-5 [1] may provide information about the implementation in a
standardized manner.
The PICS proforma is subdivided into subclauses for the following categories of information:
- guidance for completing the PICS proforma;
- identification of the implementation;
- identification of the Protocol;
- global statement of conformance;
- identification of the roles, DM-MS or DM-Gateway;
- DM-MS layer 3 and layer2 protocol part;
- DM-Gateway layer 3 and layer 2 on DM side protocol part;
- DM-MS and DM-Gateway PDUs.
A.1.2 Abbreviations and conventions
The PICS proforma contained in this annex is comprised of information in tabular form in accordance with
the guidelines presented in ISO/IEC 9646-7 [7].
Item column: The item column contains a number which identifies the item in the table.
Item description column: The item description column describes in free text each respective item (e.g.
parameters, timers, etc.). It implicitly means "is supported by the implementation?".
Status column: The following notations, defined in ISO/IEC 9646-7 [7], are used for the status column:
m mandatory - the capability is required to be supported.
o optional - the capability may be supported or not.
n/a not applicable - in the given context, it is impossible to use the capability.
x prohibited (excluded) - there is a requirement not to use this capability in the
given context.
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is
an integer which identifies an unique group of related optional items and the
logic of their selection which is defined immediately following the table.
ci conditional - the requirement on the capability ("m", "o", "x" or "n/a") depends on
the support of other optional or conditional items. "i" is an integer identifying an
unique conditional status expression which is defined immediately following the
table.
Page 12
ETS 300 396-8-3: June 1999
Reference column
The reference column makes reference to ETS 300 396-5 [1], except where explicitly stated otherwise.
Support column
The support column shall be filled in by the supplier of the implementation. The following common
notations, defined in ISO/IEC 9646-7 [7], are used for the support column:
Y or y supported by the implementation.
N or n not supported by the implementation.
N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation
of a conditional status).
If this PICS proforma is completed in order to describe a multiple-profile support in a system, it is
necessary to be able to answer that a capability is supported for one profile and not supported for another.
In that case, the supplier shall enter the unique reference to a conditional expression, preceded by "?"
(e.g. ?3). This expression shall be given in the space for comments provided at the bottom of the table. It
uses predicates defined in the SCS, each of which refers to a single profile and which takes the value
TRUE if and only if that profile is to be used.
EXAMPLE: ?3: IF prof1 THEN Y ELSE N.
It is also possible to provide a comment to an answer in the space provided at the bottom of the table.
NOTE: As stated in ISO/IEC 9646-7 [7], support for a received PDU requires the ability to
parse all valid parameters of that PDU. Supporting a PDU while having no ability to
parse a valid parameter is non-conformant. Support for a parameter on a PDU means
that the semantics of that parameter are supported.
Values allowed column
The values allowed column contains the type, the list, the range, or the length of values allowed. The
following notations are used:
- range of values: . ;
example: 5 . 20.
- list of values: , , ., ;
example: 2, 4, 6, 8, 9;
example: '1101'B, '1011'B, '1111'B;
example: '0A'H, '34'H, '2F'H.
- list of named values: (), (), ., (;
example: reject(1), accept(2).
- length: size ( . );
example: size (1 . 8).
Values supported column
The values supported column shall be filled in by the supplier of the implementation. In this column, the
values or the ranges of values supported by the implementation shall be indicated.
References to items
For each possible item answer (answer in the support column) within the PICS proforma a unique
reference exists, used, for example, in the conditional expressions. It is defined as the table identifier,
followed by a solidus character "/", followed by the item number in the table. If there is more than one
support column in a table, the columns are discriminated by letters (a, b, etc.), respectively.

Page 13
ETS 300 396-8-3: June 1999
EXAMPLE 1: A.5/4 is the reference to the answer of item 4 in table 5 of annex A.
EXAMPLE 2: A.6/3b is the reference to the second answer (i.e. in the second support column)
of item 3 in table 6 of annex A.
Pre-requisite line
A Pre-requisite line takes the form: Pre-requisite: .
A Pre-requisite line after a clause or table title indicates that the whole clause or the whole table is not
required to be completed if the predicate is FALSE.
A.1.3 Instructions for completing the PICS proforma
The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. In
particular, an explicit answer shall be entered, in each of the support or supported column boxes provided,
using the notation described in subclause A.1.2.
If necessary, the supplier may provide additional comments in space at the bottom of the tables, or
separately on sheets of paper.
More detailed instructions are given at the beginning of the different subclauses of the PICS proforma.
A.2 Identification of the implementation
Identification of the Implementation Under Test (IUT) and the system in which it resides (the System
Under Test (SUT)) should be filled in so as to provide as much detail as possible regarding version
numbers and configuration options.
The product supplier information and client information should both be filled in if they are different.
A person who can answer queries regarding information supplied in the PICS should be named as the
contact person.
A.2.1 Date of the statement
A.2.2 Implementation Under Test (IUT) identification
IUT name:
........................................................................................................................................................................
IUT version:
A.2.3 System Under Test (SUT) identification
SUT name:
........................................................................................................................................................................
Hardware configuration:
........................................................................................................................................................................
........................................................................................................................................................................
Operating system:
........................................................................................................................................................................

Page 14
ETS 300 396-8-3: June 1999
A.2.4 Product supplier
Name:
Address:
.........................................................................................................................................................................
.........................................................................................................................................................................
Telephone number:
Facsimile number:
E-mail address:
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
A.2.5 Client (if different from product supplier)
Name:
Address:
.........................................................................................................................................................................
.........................................................................................................................................................................
Telephone number:
Facsimile number:
E-mail address:
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
A.2.6 PICS contact person
(A person to contact if there are any queries concerning the content of the PICS)
Name:
Telephone number:
Facsimile number:
E-mail address:
Page 15
ETS 300 396-8-3: June 1999
Additional information:
........................................................................................................................................................................
........................................................................................................................................................................
A.3 Identification of the Protocol
This PICS proforma applies to the following standard:
ETS 300 396-5 (1996): "Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode
Operation (DMO); Part 5: Gateways" [1].
This ETS contains two layers of the protocol stack, Direct Mode Call Control (DMCC) at layer 3 and Data
Link Layer (DLL) at layer 2 for the DM-MS operating through a gateway, and the DM-Gateway protocol.
Each of these parts is addressed in a different section of the present PICS. When submitting an
implementation for test, the implementer is required to answer the questions of the section(s) of the
proforma pertaining to the part(s) of the protocol submitted to the test, i.e. the DMCC section, the DLL
section or a gateway.
A.4 Global statement of conformance
Are all mandatory capabilities of the DM-MS for operation through a DM-Gateway implemented?
(Yes/No/(n/a)).
Are all mandatory capabilities of the DM-Gateway implemented? (Yes/No/(n/a)).
NOTE: Answering "No" to any of these questions indicates non-conformance to the Protocol
specification. Non-supported mandatory capabilities are to be identified in the PICS,
with an explanation of why the implementation is non-conforming, on pages attached
to the PICS proforma. Answering "n/a" to any of these questions indicates that the
questions related to that part does not apply.
A.5 Types
The supplier of the implementation shall state the type of the implementation, in table A.1.
Table A.1: Implementation type
Item Type Reference Status Support
1 DM-MS 6, 9 o.1
2 Gateway 6, 9 o.1
o.1: It is mandatory to support at least one of these items.
The supplier of the implementation shall state the gateway type of the implementation, in table A.2.
Table A.2: Type of gateway
Pre-requisite: A.1/2 -- Gateway
Item Type Reference Status Support
DM-Gateway (DM-GATE) 4.1 o.2
1 DM-Gateway with a type 1 4.1 o.2
Repeater (type 1 DM-REP/GATE)
DM-Gateway with a type 2 4.1 o.2
Repeater (type 2 DM-REP/GATE)
o.2: It is mandatory to support at least one of these items.
The supplier of the implementation shall state the DM-MS type of the implementation, in table A.3.

Page 16
ETS 300 396-8-3: June 1999
Table A.3: Type of DM-MS
Pre-requisite: A.1/1 -- DM-MS
Item Type Reference Status Support
1 DM-MS supporting operation via a6o.3
DM-Gateway (DM-GATE)
DM-MS supporting operation via a6o.3
combined DM-Gateway with a
Repeater (DM-REP/GATE)
o.3: It is mandatory to support at least one of these items.
A.6 DM-MS
A.6.1 DM-MS Layer 3
The supplier of the implementation shall state the support of the DM-MS implementation for the following
protocols, in table A.4.
Table A.4: DM-MS Layer 3 protocols
Pre-requisite: A.1/1 -- DM-MS
Item Protocol Reference Status Support
1 Direct Mode Call Control (DMCC) 6.1 m
Direct Mode Mobility Management 6.1 o
(DMMM)
A.6.1.1 Direct Mode Call Control (DMCC)
A.6.1.1.1 DMCC major capabilities
The supplier of the implementation shall state the support of the implementation for each of the following
DMCC services, in table A.5.
Table A.5: DMCC services
Pre-requisite: A.4/1 -- DMCC
Item DMCC service Reference Status Support
1 Circuit mode call 6.2 o.4
2 Short Data Service (SDS) 6.3 o.4
o.4: It is mandatory to support at least one of these items.
A.6.1.1.2 Circuit mode call
The supplier of the implementation shall state the support of the implementation for each of the following
circuit mode call protocol features, in table A.6.

Page 17
ETS 300 396-8-3: June 1999
Table A.6: Circuit mode protocol features
Pre-requisite: A.5/1 -- circuit mode call
Item Protocol feature Reference Status Support
1 Group address call capability 5.2 o.5
Individual address call capability 5.2 o.5
3 Initiate call set-up without presence check 6.2.1.1 c601
Accept call set-up 6.2.2 m
5 Master end of call transmission 6.2.4.1 c602
6 Receive end of call transmission 6.2.4.2 m
Master call termination 6.2.4.1 c602
8 Receive call termination 6.2.4.2, 6.2.5.2 m
Accept call pre-emption 6.2.4.1 c602
10 Initiate pre-emption in ongoing call 6.2.4.2 o
11 Initiate pre-emption for a new call 6.2.6 o
Initiate call change-over 6.2.5.2 o
13 Late entry by called party 6.2.3 o
Receive TPNI in call set-up 6.2.2.3 m
15 Suppress TPNI in call set-up 6.2.4.3 o
16 Address to external user capability 6.2.1.3.3 o
(beyond the V+D system)
o.5: It is mandatory to support at least one of these items.
c601: IF A.4/2 -- If Direct Mode Mobility Management supported;
THEN o -- then optional;
ELSE n/a.
c602: IF A.6/3 -- If Initiate call set-up supported;
THEN m -- then mandatory;
ELSE n/a.
A.6.1.1.3 Circuit mode call set-up
The supplier of the implementation shall state the support of the implementation for each of the following
circuit mode call set-up procedures, in tables A.7 and A.8.
Table A.7: Circuit mode call set-up procedures
Pre-requisite: A.6/3 -- Initiate call set-up without presence check
Item Call set-up procedure Reference Status Support
1 Initiate call set-up on group address 6.2.1.1 c701
2 Initiate call set-up on temporary group 6.2.1.2 o
address
Initiate call set-up on individual call address 6.2.1.1 c702
c701: IF A.6/1 -- If group address call capability supported;
THEN m -- then mandatory;
ELSE n/a.
c702: IF A.6/2 -- If individual address call capability supported;
THEN m -- then mandatory;
ELSE n/a.
Table A.8: Accept circuit mode call procedures
Pre-requisite: A.6/4 -- Accept call set-up
Item Accept call set-up procedure Reference Status Support
Accept call without presence check 6.2.2.1 c801
2 Accept call with presence check 6.2.2.2 c802
3 Receive TPNI in call set-up 6.2.1.3.4 m

Page 18
ETS 300 396-8-3: June 1999
c801: IF A.6 /1 -- If group address call capability supported;
THEN m -- then mandatory;
ELSE n/a.
c802: IF A.6 /2 -- If individual address call capability supported;
THEN m -- then mandatory;
ELSE n/a.
A.6.1.1.4 Circuit mode services offered
The supplier of the implementation shall state the support of the implementation for each of the following
circuit mode services, in table A.9.
Table A.9: Circuit mode services offered
Pre-requisite: A.5/1 -- circuit mode call
Item Circuit mode service Reference Status Support
1 Circuit mode speech: 5.4 o.6
2 Circuit mode data unprotected: 7.2 5.4 o.6
3 Circuit mode data low protection: 4.8, N=1 5.4 o.6
4 Circuit mode data low protection: 4.8, N=4 5.4 o.6
5 Circuit mode data low protection: 4.8, N=8 5.4 o.6
Circuit mode data high protection: 2.4, N=1 5.4 o.6
7 Circuit mode data high protection: 2.4, N=4 5.4 o.6
8 Circuit mode data high protection: 2.4, N=8 5.4 o.6
Clear mode transmission 5.2 o.7
10 End to end encrypted transmission 5.2 o.7
11 Normal priority call 5.4 m
High priority call 5.4 o.8
13 Pre-emptive priority call 5.4 o.8
14 Emergency pre-emptive priority call 5.4 o.8
Recent user priority service 5.4 o
o.6: It is mandatory to support at least one of these items.
o.7: It is mandatory to support at least one of these items.
o.8: It is mandatory to support at least one of these items.
A.6.1.1.5 Short data services
The supplier of the implementation shall state the support of the implementation for each of the following
short data services, in table A.10.
Table A.10: Short Data Services
Pre-requisite: A.5/2 -- Short Data Service
Item Short data service Reference Status Support
Send data (note 1) 6.3.1 o.9
2 Receive data (note 2) 6.3.2 o.9
Extended error protection (FCS) 6.3.4 m
NOTE 1: Capability to initiate short data transaction as master.
NOTE 2: Capability to receive short data transaction as slave.
o.9: It is mandatory to support at least one of these items.
A.6.1.1.6 Type of short data service
The supplier of the implementation shall state the support of the implementation for each of the following
types of SDSs, in tables A.11 to A.15.

Page 19
ETS 300 396-8-3: June 1999
Table A.11: Type of short data service
Pre-requisite: A.5/2 -- Short Data Service
Item Type of short data service Reference Status Support
1 Group address SDS capability 6.3 o.10
Individual address SDS capability 6.3 o.10
3 Pre-defined short data messages 6.3 o.11
4 User-defined short data messages 6.3 o.11
OTAR (note) 6.3 o.11
6 Enable/disable (note) 6.3 o.11
Additional addressing (receive) 6.3.3.2 c1101
8 Additional addressing (send) 6.3.3.1 c1102
NOTE: The detailed PICS proforma for DMO security is defined in a
separate PICS proforma covering security aspects.
o.10: It is mandatory to support at least one of these items.
o.11: It is mandatory to support at least one of these items.
c1101: IF A.10/2 -- If receive SDS supported;
THEN m -- then mandatory;
ELSE n/a.
c1102: IF A.10/1 -- If send SDS supported;
THEN o -- then optional;
ELSE n/a.
Table A.12: Send short data service on group address
Pre-requisite: A.10/1 AND A.11/1 AND A.4/2
-- Send SDS and SDS group address and Mobility Management
Item Send SDS on group address Reference Status Support
Unacknowledged data service 6.3.1 o.12
2 Acknowledged data service 6.3.1 o.12
Extraction of data included in ACK 6.3.1 c1201
o.12: It is mandatory to support at least one of these items.
c1201: IF A.12/2 -- Acknowledged data service supported;
THEN m -- then mandatory;
ELSE n/a.
Table A.13: Send short data service on individual address
Pre-requisite: A.10/1 AND A.11/2 AND A.4/2
-- Send SDS and SDS individual address and Mobility Management
Item Send SDS on individual address Reference Status Support
1 Unacknowledged data service 6.3.1 o.13
Acknowledged data service 6.3.1 o.13
3 Extraction of data included in ACK 6.3.1 c1301
o.13: It is mandatory to support at least one of these items.
c1301: IF A.13/2 -- Acknowledged data service supported;
THEN m -- then mandatory;
ELSE n/a.
Page 20
ETS 300 396-8-3: June 1999
Table A.14: Receive short data service on group address
Pre-requisite
...