SIST ETS 300 396-8-1 E1:2003

SLOVENSKI STANDARD
01-december-2003
3UL]HPQLVQRSRYQLUDGLR7(75$7HKQLþQH]DKWHYH]DQHSRVUHGQRREUDWRYDQMH
'02GHO,]MDYDRVNODGQRVWLL]YHGEHSURWRNROD3,&63URIRUPD
VSHFLILNDFLMDSRGGHO5DGLMVNLYPHVQLN$,PHGPRELOQLPDSRVWDMDPD0606
Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation
(DMO); Part 8: Protocol Implementation Conformance Statement (PICS) proforma
specification; Sub-part 1: Mobile Station to Mobile Station (MS-MS) Air Interface (AI)
Ta slovenski standard je istoveten z: ETS 300 396-8-1 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-1
TELECOMMUNICATION January 2000
STANDARD
Source: TETRA Reference: DE/TETRA-02007-8-1
ICS: 33.020
Key words: ICS, PICS, DMO, MS, TETRA, radio
Terrestrial Trunked Radio (TETRA);
Technical requirements for Direct Mode Operation (DMO);
Part 8: Protocol Implementation Conformance Statement (PICS)
proforma specification;
Sub-part 1: Mobile Station to Mobile Station (MS-MS)
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.:+33492944200- Fax:+33493654716
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 2000. All rights reserved.

Page 2
ETS 300 396-8-1: January 2000
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-1: January 2000
Contents
Foreword.5
Introduction.5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Conformance to this Protocol Implementation Conformance Statement (PICS) proforma
specification.8
Annex A (normative): Protocol ICS proforma (PICS) for ETS 300 396-3.9
A.1 Guidance for completing the PICS proforma .9
A.1.1 Purposes and structure.9
A.1.2 Abbreviations and conventions .9
A.1.3 Instructions for completing the PICS proforma.11
A.2 Identification of the implementation.11
A.2.1 Date of the statement.11
A.2.2 IUT identification .11
A.2.3 SUT identification.11
A.2.4 Product supplier .12
A.2.5 Client (if different from product supplier).12
A.2.6 PICS contact person .12
A.3 Identification of the protocol .13
A.4 Global statement of conformance .13
A.5 DMCC at layer 3 .13
A.5.1 DMCC major capabilities .13
A.5.2 Circuit mode call .13
A.5.3 Circuit mode call set-up .14
A.5.4 Circuit mode services offered .15
A.5.5 Short data services .15
A.5.6 Type of short data service.16
A.5.7 Data transmission .17
A.5.8 SDS user defined data.17
A.5.9 DMCC PDUs.18
A.5.10 DMCC PDU parameters .19
A.5.10.1 DM-SETUP.20
A.5.10.2 DM-SETUP PRES.20
A.5.10.3 DM-CONNECT.21
A.5.10.4 DM-DISCONNECT.21
A.5.10.5 DM-CONNECT ACK .21
A.5.10.6 DM-OCCUPIED.22
A.5.10.7 DM-RELEASE .22
A.5.10.8 DM-TX CEASED .22
A.5.10.9 DM-TX REQUEST.23
A.5.10.10 DM-TX ACCEPT .23
A.5.10.11 DM-PREEMPT .23

Page 4
ETS 300 396-8-1: January 2000
A.5.10.12 DM-PRE ACCEPT . 23
A.5.10.13 DM-REJECT . 24
A.5.10.14 DM-INFO. 24
A.5.10.15 DM-SDS UDATA. 24
A.5.10.16 DM-SDS DATA . 25
A.5.10.17 DM-SDS ACK . 26
A.5.11 DMCC constants . 26
A.5.12 DMCC timers. 27
A.6 DLL at layer 2. 27
A.6.1 DM-Medium Access Control (MAC) features . 27
A.6.2 DM-MAC procedures. 28
A.6.3 DM-MAC PDUs .33
A.6.4 DM-MAC PDU parameters. 33
A.6.4.1 DMAC-SYNC in Signalling Channel (SCH)/S . 34
A.6.4.2 DMAC-SYNC in SCH/H . 34
A.6.4.3 DMAC-DATA. 35
A.6.4.4 DMAC-FRAG . 35
A.6.4.5 DMAC-END. 35
A.6.4.6 DMAC-U SIGNAL . 35
A.6.5 DM-MAC generated messages. 36
A.6.6 DM-MAC generated message parameters . 36
A.6.6.1 DM-RESERVED . 36
A.6.6.2 DM-SDS OCCUPIED. 36
A.6.6.3 DM-TIMING REQUEST . 37
A.6.6.4 DM-TIMING ACK . 37
A.6.7 DM-MAC constants . 37
A.6.8 DM-MAC timers. 39
History. 40

Page 5
ETS 300 396-8-1: January 2000
Foreword
This European Telecommunication Standard (ETS) has been produced by the Terrestrial Trunked Radio
(TETRA) Project of the European Telecommunications Standards Institute (ETSI).
The present document is part 8 of a multi-part ETS covering the Direct Mode Operation (DMO) of TETRA,
as identified below:
Part 1: "General network design";
Part 2: "Radio aspects";
Part 3: "Mobile Station to Mobile Station (MS-MS) Air Interface (AI) protocol";
Part 4: "Type 1 repeater air interface";
Part 5: "Gateway air interface";
Part 6: "Security";
Part 7: "Type 2 repeater air interface";
Part 8: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 9: "Service and Description Language (SDL) model";
Part 10: "Managed Direct Mode Operation (DMO)".
Transposition dates
Date of adoption of this ETS: 31 December 1999
Date of latest announcement of this ETS (doa):
31 March 2000
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 September 2000
Date of withdrawal of any conflicting National Standard (dow): 30 September 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 6
ETS 300 396-8-1: January 2000
Blank page
Page 7
ETS 300 396-8-1: January 2000
1 Scope
This European Telecommunication Standard (ETS) provides the Protocol Implementation Conformance
Statement (PICS) proforma for the TETRA Direct Mode Operation (DMO), Mobile Station to Mobile
Station (MS-MS) Air Interface (AI) protocol, defined in ETS 300 396-3 [1] in compliance with the relevant
requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [4] and
ETS 300 406 [2].
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 396-3 (1998): "Terrestrial Trunked Radio (TETRA); Technical
requirements for Direct Mode Operation (DMO); Part 3: Mobile Station to Mobile
Station (MS-MS) Air Interface (AI) protocol".
[2] ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol
and profile conformance testing specifications; Standardization methodology".
[3] ISO/IEC 9646-1 (1994): "Information technology; Open systems interconnection;
Conformance testing methodology and framework; Part 1: General concepts".
[4] 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-3 [1];
- terms defined in ISO/IEC 9646-1 [3] and in ISO/IEC 9646-7 [4].
In particular, the following terms defined in ISO/IEC 9646-1 [3] 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 8
ETS 300 396-8-1: January 2000
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AI Air Interface
DLL Data Link Layer
DM Direct Mode
DMCC Direct Mode Call Control
DMO Direct Mode Operation
FCS Frame Check Sequence
ICS Implementation Conformance Statement
IUT Implementation Under Test
LCH Linearization Channel
MAC Medium Access Control
OTAR Over The Air Re-keying
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
SCH Signalling Channel
SCS System Conformance Statement
SDS Short Data Service
SDU Service Data Unit
SUT System Under Test
TPNI Transmitting Party Number Identification
TSI TETRA Subscriber Identity
4 Conformance to this Protocol Implementation Conformance Statement
(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 9
ETS 300 396-8-1: January 2000
Annex A (normative): Protocol ICS proforma (PICS) for ETS 300 396-3
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-3 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;
- Direct Mode Call Control (DMCC) protocol layer 3 part:
- circuit mode calls;
- short data service;
- Data Link Layer (DLL) protocol layer 2 part.
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.
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, 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;

Page 10
ETS 300 396-8-1: January 2000
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 a
unique conditional status expression which is defined immediately following the
table.
Reference column
The reference column makes reference to ETS 300 396-3, 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, 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 System Conformance Statement (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 1: ?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, support for a received Protocol Data Unit (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 is 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.

Page 11
ETS 300 396-8-1: January 2000
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.
EXAMPLE 2: A.5/4 is the reference to the answer of item 4 in table 5 of annex A.
EXAMPLE 3: 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.
Prerequisite line
A prerequisite line takes the form: Prerequisite: .
A prerequisite 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 IUT identification
IUT name:
.........................................................................................................................................................................
IUT version:
A.2.3 SUT identification
SUT name:
.........................................................................................................................................................................
Hardware configuration:
.........................................................................................................................................................................
.........................................................................................................................................................................

Page 12
ETS 300 396-8-1: January 2000
Operating system:
........................................................................................................................................................................
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 13
ETS 300 396-8-1: January 2000
Additional information:
.........................................................................................................................................................................
.........................................................................................................................................................................
A.3 Identification of the protocol
This PICS proforma applies to the following standard:
ETS 300 396-3 (1998): "Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode
Operation (DMO); Part 3: Mobile Station to Mobile Station (MS-MS) Air Interface (AI) protocol".
This ETS contains two layers of the protocol stack, DMCC at layer 3 and Data Link Layer (DLL) at layer 2.
Each layer 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 or the DLL one or both.
A.4 Global statement of conformance
Are all mandatory capabilities of DMCC implemented? (Yes/No/(n/a)).
Are all mandatory capabilities of DLL 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 two questions indicates that the
questions related to that protocol does not apply.
A.5 DMCC at layer 3
A.5.1 DMCC major capabilities
The supplier of the implementation shall state the support of the implementation for each of the following
protocol services, in table A.1.
Table A.1: DMCC services
Item Service Reference Status Support
1 Circuit mode call 6.2, 4.4 o.1
2 Short Data Service (SDS) 6.3, 4.4 o.1
o.1: It is mandatory to support at least one of these items
A.5.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.2.

Page 14
ETS 300 396-8-1: January 2000
Table A.2: Circuit mode protocol features
Prerequisite: A.1/1 -- circuit mode call
Item Protocol features Reference Status Support
5.2 o.2
1 Group address call capability
2 Individual address call capability 5.2 o.2
Initiate call set-up without presence 6.2.1.1 o
check
4 Initiate call set-up with presence 6.2.2.1 o
check
Accept call set-up without presence 6.2.1.2 m
check
6 Accept call set-up with presence 6.2.2.2 o
check
Master end of call transmission 6.2.4.1 c201
8 Receive end of call transmission 6.2.4.2 m
9 Master call termination 6.2.4.1, 6.2.5.1 c201
10 Receive call termination 6.2.4.2, 6.2.5.2 m
11 Accept call pre-emption 6.2.4.1, 6.2.5.1 c201
Initiate pre-emption in ongoing call 6.2.4.2, 6.2.5.3 o
13 Initiate a new call by pre-emption 6.2.6 o
14 Initiate call change-over 6.2.5.2 o
15 Accept call change-over 6.2.5.1 c201
16 Late entry by called party 6.2.3.2 o
Receive Transmitting Party Number 6.2.4.3 m
Identification (TPNI) in call setup
18 Suppress TPNI in call setup 6.2.4.3 o
Receive inter-MNI call 6.2.4.3 m
20 Initiate inter-MNI call 6.2.4.3 o
o.2: It is mandatory to support at least one of these items
c201: IF A.2/3 OR A.2/4 -- If initiation of call set-up with or without presence check supported
THEN m -- then mandatory
ELSE n/a
A.5.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.3 to A.4.
Table A.3: Circuit mode call set-up procedures - Group call
Prerequisite: A.2/1 AND A.2/3 -- Initiate group call set-up
Item Set-up procedure Reference Status Support
1 Group call address 6.2.1.1 m
2 Call on temporary group address 6.2.1.3 o

Page 15
ETS 300 396-8-1: January 2000
Table A.4: Circuit mode call set-up procedures - Individual call
Prerequisite: A.2/2 -- Individual address call capability
Item Set-up procedure Reference Status Support
Initiate Individual call without presence 6.2.1.1 c401
check
2 Initiate Individual call with presence check 6.2.2.1 c402
c401: IF A.2/3 THEN o ELSE n/a -- If initiate call set-up without presence check then optional
c402: IF A.2/4 THEN m ELSE n/a -- If initiate call set-up with presence check then mandatory
A.5.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.5.
Table A.5: Circuit mode services offered
Prerequisite: A.1/1 -- circuit mode call
Item Circuit mode service Reference Status Support
1 Circuit mode speech: 5.4 o.3
Circuit mode data unprotected: 7.2 5.4 o.3
3 Circuit mode data low protection: 4.8, N=1 5.4 o.3
4 Circuit mode data low protection: 4.8, N=4 5.4 o.3
5 Circuit mode data low protection: 4.8, N=8 5.4 o.3
6 Circuit mode data high protection: 2.4, N=1 5.4 o.3
7 Circuit mode data high protection: 2.4, N=4 5.4 o.3
Circuit mode data high protection: 2.4, N=8 5.4 o.3
9 Clear end-to-end transmission 5.4 o.4
10 End to end encrypted transmission 5.4 o.4
11 Normal priority call 5.4 m
12 High priority call 5.4 o
13 Pre-emptive priority call 5.4 o
14 Emergency pre-emptive priority call 5.4 o
15 Recent user priority service 5.4 o
o.3: It is mandatory to support at least one of these items
o.4: It is mandatory to support at least one of these items
A.5.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.6.
Table A.6: Short data services
Prerequisite: A.1/2 -- Short Data Services
Item Short data service Reference Status Support
1 Send data (note 1) 6.3.1 o.5
Receive data (note 2) 6.3.2 o.5
3 Extended error protection (Frame 6.3.4 m
Check Sequence (FCS))
NOTE 1: Capability to originate short data transaction as master.
NOTE 2: Capability to receive short data transaction as slave.
o.5: It is mandatory to support at least one of these items

Page 16
ETS 300 396-8-1: January 2000
A.5.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.7 to A.11.
Table A.7: Type of short data service
Prerequisite: A.1/2 -- Short Data Services
Item Type of short data service Reference Status Support
1 Group address SDS capability 6.3 o.6
2 Individual address SDS capability 6.3 o.6
Pre-defined short data messages (i.e. 6.3 o.7
status messages)
4 User-defined short data messages 6.3 o.7
Over The Air Re-keying (OTAR) (note) 6.3 o.7
6 Enable/disable (note) 6.3 o.7
7 Additional addressing (receive) 6.3.3 c701
8 Additional addressing (send) 6.3.3 c702
NOTE: The detailed PICS proforma for DMO security is defined in a
separate PICS proforma covering security aspects.
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
c701: IF A.6/2 THEN m ELSE n/a -- If receive SDS supported then mandatory
c702: IF A.6/1 THEN o ELSE n/a -- If send SDS supported then optional
Table A.8: Send short data service on group address
Prerequisite: A.6/1 AND A.7/1 -- Group address SDS capability
Item SDS on group address Reference Status Support
Unacknowledged data service 6.3 m
Table A.9: Send short data service on individual address
Prerequisite: A.6/1 AND A.7/2 -- Individual address SDS capability
Item SDS on individual address Reference Status Support
Unacknowledged data service 6.3 o.8
2 Acknowledged data service 6.3 o.8
Extraction of data if included in ACK 6.3 c901
o.8: It is mandatory to support at least one of these items
c901: IF A.9/2 -- If the sending of acknowledged short data supported
THEN m -- then mandatory
ELSE n/a
Table A.10: Receive short data service on group address
Prerequisite: A.6/2 AND A.7/1 -- Group address SDS capability
Item SDS on group address Reference Status Support
Unacknowledged data service 6.3 m
Page 17
ETS 300 396-8-1: January 2000
Table A.11: Receive short data service on individual address
Prerequisite: A.6/2 AND A.7/2 -- Individual address SDS capability
Item SDS on individual address Reference Status Support
Unacknowledged data service 6.3 o.9
2 Acknowledged data service 6.3 o.9
3 Including data in ACK 6.3 o
o.9: It is mandatory to support at least one of these items
A.5.7 Data transmission
The supplier of the implementation shall state the support of the implementation for each of the following
services for sending data, in table A.12.
Table A.12: Sending data services
Prerequisite: A.6/1 -- Send data using SDS
Item Send data Reference Status Support
1 Send short data on a free channel 6.3.1.1 m
Send short data after pre-emption of a 6.3.1.2 o
circuit mode call (new call)
3 Send short data stealing from circuit 6.3.1.3 c1201
mode transmission
Send short data after pre-emption of a 6.3.1.4.1 c1202
circuit mode call (ongoing call)
5 Send short data after changeover of a 6.3.1.4.2 c1202
circuit mode call
Send short data as master of a circuit 6.3.1.4.3 c1202
mode call
c1201: IF A.2/3 OR A.2/4 -- If initiate CM call set-up supported
THEN o -- then optional
ELSE n/a
c1202: IF A.1/1 -- If CM call supported then optional
THEN o
ELSE n/a
A.5.8 SDS user defined data
The supplier of the implementation shall state the support of the implementation for each of the following
types of SDSs, in table A.13.
Table A.13: SDS user defined data
Prerequisite: A.7/4 -- User defined short data
Item Circuit mode service Reference Status Support
1 User defined data 1 (16 bits) 5.4 o.10
2 User defined data 2 (32 bits) 5.4 o.10
3 User defined data 3 (64 bits) 5.4 o.10
4 User defined data 4 (up to 2047 bits) 5.4 o.10
o.10: It is mandatory to support at least one of these items

Page 18
ETS 300 396-8-1: January 2000
A.5.9 DMCC PDUs
The supplier of the implementation shall state the support of the implementation for each of the following
circuit mode and SDS PDUs, in tables A.14 to A.15.
Table A.14: Circuit mode call and pre-emption PDUs
Item PDU Reference Sending Receiving
Status Support Status Support
1 DM-SETUP 9.5.1 c1401 c1402
2 DM-SETUP PRES 9.5.2 c1403 c1404
DM-CONNECT 9.5.3 c1404 c1403
4 DM-DISCONNECT 9.5.4 c1404 c1403
5 DM-CONNECT ACK 9.5.5 c1403 c1404
DM-OCCUPIED 9.5.6 c1405 c1402
7 DM-RELEASE 9.5.7 c1405 c1402
8 DM-TX CEASED 9.5.8 c1405 c1402
DM-TX REQUEST 9.5.9 c1406 c1405
10 DM-TX ACCEPT 9.5.10 c1405 c1412
11 DM-PREEMPT 9.5.11 c1407 c1411
DM-PRE ACCEPT 9.5.12 c1411 c1413
13 DM-REJECT 9.5.13 c1409 c1410
14 DM-INFO 9.5.14 c1408 c1402
c1401: IF A.2/3 -- If initiate call setup without presence check
THEN m -- supported then mandatory
ELSE n/a
c1402: IF A.1/1 -- If circuit mode call supported
THEN m -- then mandatory
ELSE n/a
c1403: IF A.4/2 -- If individual call setup with presence check supported
THEN m -- then mandatory
ELSE n/a
c1404: IF A.2/6 -- If accept of call set-up with presence check supported
THEN m -- then mandatory
ELSE n/a
c1405: IF A.2/3 OR A.2/4 -- If initiate call set-up with or without presence check supported
THEN m -- then mandatory
ELSE n/a
c1406: IF A.2/14 OR A.12/5 -- If CM or SDS call changeover supported
THEN m -- then mandatory
ELSE n/a
c1407: IF A.2/12 OR A.2/13 -- If initiation of CM or SDS pre-emption is supported
OR A.12/2 OR A.12/4
THEN m -- then mandatory
ELSE n/a
c1408: IF A.2/18 -- If sending of TPNI can be suppressed then
THEN m -- mandatory else
ELSE o -- optional
c1409: IF A.2/3 OR A.2/4 -- If initiate CM call supported
THEN m -- then mandatory
ELSE IF A.11/2 OR A.11/3. -- If receive acknowledged SDS supported
THEN o -- then optional
ELSE n/a
c1410: IF A.2/12 OR A.2/13 OR A.2/14-- If request changeover or pre-emption
OR A.9/2 OR A.9/3 -- or send acknowledged short data supported
THEN m -- then mandatory
ELSE n/a
Page 19
ETS 300 396-8-1: January 2000
c1411: IF A.2/3 OR A.2/4 -- If initiation of CM or SDS call
OR A.6/1 -- supported
THEN m -- then mandatory
ELSE n/a
c1412: IF A.1/1 OR A.12/5 -- If circuit mode call or send SDS after changeover supported
THEN m -- then mandatory
ELSE n/a
c1413: IF A.1/1 OR A.12/2 -- If circuit mode call or send SDS after pre-emption supported
OR A.12/4
THEN m -- then mandatory
ELSE n/a
Table A.15: Specific SDS PDUs
Prerequisite: A.1/2 -- Short Data Services
Item PDU Reference Sending Receiving
Status Support Status Support
DM-SDS UDATA 9.5.15 c1501 c1503
2 DM-SDS DATA 9.5.16 c1502 c1504
3 DM-SDS ACK 9.5.17 c1504 c1502
c1501: IF A.8/1 OR A.9/1 -- If sending of unacknowledged SDS with group or individual address
THEN m -- supported then mandatory
ELSE n/a
c1502: IF A.9/2 OR A.9/3 -- If sending of acknowledged data service with or without data in ACK
THEN m -- supported then mandatory
ELSE n/a
c1503: IF A.10/1 OR A.11/1 -- If receiving of unacknowledged supported
THEN m -- then mandatory
ELSE n/a
c1504: IF A.11/2 OR A.11/3 -- If receiving of acknowledged data service supported
THEN m -- then mandatory
ELSE n/a
A.5.10 DMCC PDU parameters
The supplier of the implementation shall state the support of the implementation for each of the following
DMCC PDU elements, in tables A.16 to A.32.

Page 20
ETS 300 396-8-1: January 2000
A.5.10.1 DM-SETUP
Table A.16: DM-SETUP PDU contents
Prerequisite: A.1/1 -- Circuit mode call
Item Elements Reference Status Support
Message dependent elements
Timing flag m
1 9.6.22
2 Linearization Channel (LCH) in m
9.6.5
frame3flag
3 Pre-emption flag 9.6.10 m
Power class m
4 9.6.8
5 Power control flag m
9.6.9
6 Reserved m
9.5.1
7 Circuit mode type 9.6.3 m
8 Reserved 9.5.1 m
Priority level m
9 9.6.11
DM-Service Data Unit (SDU)
elements
10 End-to-end encryption flag 9.7.8 m
Call type flag
11 9.7.5 m
External source flag
12 9.7.9 m
13 Reserved
9.5.1 m
A.5.10.2 DM-SETUP PRES
Table A.17: DM-SETUP PRES PDU contents
Prerequisite: A.14/2a OR A.14/2b -- DM-SETUP PRES PDU
Item Elements Reference Status Support
Message dependent elements
1 Reserved 9.5.2 m
2 Power class 9.6.8 m
Power control flag m
3 9.6.9
Reserved m
4 9.5.2
5 Circuit mode type m
9.6.3
6 Reserved 9.5.2 m
7 Priority level 9.6.11 m
DM-SDU elements
End-to-end encryption flag
8 9.7.8 m
9 Call type flag
9.7.5 m
10 External source flag 9.7.9 m
11 Reserved 9.5.2 m
Page 21
ETS 300 396-8-1: January 2000
A.5.10.3 DM-CONNECT
Table A.18: DM-CONNECT PDU contents
Prerequisite: A.14/3a OR A.14/3b -- DM-CONNECT PDU
Item Elements Reference Status Support
Message dependent elements
Circuit mode type 9.6.3 m
2 Reserved 9.5.3 m
DM-SDU elements
Reserved m
3 9.5.3
A.5.10.4 DM-DISCONNECT
Table A.19: DM-DISCONNECT PDU contents
Prerequisite: A.14/4a OR A.14/4b -- DM-DISCONNECT PDU
Item Elements Reference Status Support
DM-SDU elements
1 Disconnect cause m
9.7.7
A.5.10.5 DM-CONNECT ACK
Table A.20: DM-CONNECT ACK PDU contents
Prerequisite: A.14/5a OR A.14/5b -- DM-CONNECT ACK PDU
Item Elements Reference Status Support
Message dependent elements
Timing flag 9.6.22 m
2 LCHinframe3flag 9.6.5 m
3 Pre-emption flag 9.6.10 m
4 Power class 9.6.8 m
5 Power control flag 9.6.9 m
Reserved 9.5.5 m
7 Circuit mode type 9.6.3 m
8 Reserved 9.5.5 m
9 Priority level 9.6.11 m
DM-SDU elements
10 End-to-end encryption flag
9.7.8 m
11 Call type flag 9.7.5 m
12 External source flag 9.7.9 m
Reserved
13 9.5.5 m
Page 22
ETS 300 396-8-1: January 2000
A.5.10.6 DM-OCCUPIED
Table A.21: DM-OCCUPIED PDU contents
Prerequisite: A.1/1 -- Circuit mode call
Item Elements Reference Status Support
Message dependent elements
Timing flag m
1 9.6.22
2 LCHinframe3flag m
9.6.5
3 Pre-emption flag 9.6.10 m
4 Power class 9.6.8 m
Power control flag m
5 9.6.9
Reserved m
6 9.5.6
7 Circuit mode type m
9.6.3
8 Reserved 9.5.6 m
9 Priority level 9.6.11 m
DM-SDU elements
End-to-end encryption flag
10 9.7.8 m
11 Call type flag
9.7.5 m
12 External source flag 9.7.9 m
13 Reserved 9.5.6 m
A.5.10.7 DM-RELEASE
Table A.22: DM-RELEASE PDU contents
Prerequisite: A.1/1 -- Circuit mode call
Item Elements Reference Status Support
DM-SDU elements
Release cause m
1 9.7.15
A.5.10.8 DM-TX CEASED
Table A.23: DM-TX CEASED contents
Prerequisite: A.1/1 -- Circuit mode call
Item Elements Reference Status Support
Message dependent elements
Reservation time remaining m
1 9.6.15
Timing flag m
2 9.6.22
3 Requests flag m
9.6.14
4 Changeover requests flag 9.6.1 m
5 Requests bitmap 9.6.13 m
Recent user priority flag m
6 9.6.12
Timing change announced m
7 9.6.20
8 Timing adjustment m
9.6.19
9 Priority level 9.6.11 m
DM-SDU elements
10 Cease cause 9.7.6 m
SIST ETS 300 396-8-1 E
...