ETSI TS 100 392-18-3 V1.1.1 (2009-11)

Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D) and Direct Mode Operation (DMO); Part 18: Air interface optimized applications; Sub-part 3: Direct mode Over The Air Management protocol (DOTAM)

DTS/TETRA-03200

General Information

• Status: Published
• Publication Date: 08-Nov-2009
• Technical Committee: TCCE 3 - TCCE Air Interface and Network Protocols
• Current Stage: 12 - Completion
• Due Date: 23-Nov-2009
• Completion Date: 09-Nov-2009

Standards Content (Sample)

Technical Specification
Terrestrial Trunked Radio (TETRA);
Voice plus Data (V+D) and Direct Mode Operation (DMO);
Part 18: Air interface optimized applications;
Sub-part 3: Direct mode Over The Air Management
protocol (DOTAM)
2 ETSI TS 100 392-18-3 V1.1.1 (2009-11)

Reference
DTS/TETRA-03200
Keywords
air interface, DMO, management, TETRA, V+D
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2009.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
Contents
Intellectual Property Rights . 5
Foreword . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 8
3.3 Abbreviations . 8
4 Direct mode operation over the air management protocol . 8
4.1 General . 8
4.2 DOTAM protocol system architecture . 9
4.3 DOTAM protocol service description . 11
4.3.1 General on DOTAM services . 11
4.3.2 Services available at the DOTAM-SAP. 11
4.3.3 Service primitives at the DOTAM-SAP . 12
4.3.4 Service primitive parameters at the DOTAM-SAP . 12
4.3.5 State description . 12
5 DOTAM protocol description . . 12
5.1 Description of information elements . 12
5.1.1 Acknowledgement request . 12
5.1.2 Air interface encryption state . 13
5.1.3 DMO frequency . 13
5.1.4 DMO frequency mnemonic name . 13
5.1.5 DMO group status . 13
5.1.6 DMO group mnemonic name . 13
5.1.7 Encryption key number . 13
5.1.8 Group number . 14
5.1.9 Selected group . 14
5.1.10 Unique DMO group identifier . 14
5.2 Information flows . 14
5.2.1 General on information flows . 14
5.2.2 MS receiving DMO group assignment without an acknowledgement . 15
5.2.3 MS receiving DMO group assignment with an acknowledgement . 15
5.2.4 Deassignment of DMO group definitions . 16
5.2.5 Change of status of DMO group definitions . 16
5.2.6 Interrogation of DMO group definitions . 17
5.3 Functional entity actions . 17
5.3.1 FE1 actions . 17
5.3.2 FE2 actions . 18
5.3.3 FE3 actions . 19
5.4 Allocation of entities . 19
5.5 Procedures . 20
5.5.1 Relations to flow charts . 20
5.5.2 Moving from V+D to DMO and Powering on in DMO . 20
5.5.3 MS receiving DMO group assignment . 20
5.5.4 MS receiving DMO group deassignment . 21
5.5.5 MS receiving DMO group status change . 21
5.5.6 MS receiving DMO interrogation request . 22
5.5.7 MS receiving DOTAM control group address . 22
5.5.8 MS receiving PDU using DOTAM control group address . 22
5.6 Operational requirements . 23
ETSI
4 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
5.6.1 DMO capable MS . 23
5.6.2 DMO capable MS home SwMI . 23
6 DOTAM protocol coding requirements . 23
6.1 General on coding requirements . 23
6.2 DOTAM protocol PDU description tables . 24
6.2.1 ASSIGN PDU . 24
6.2.2 ASSIGN ACK PDU. 24
6.2.3 CHANGE STATUS PDU . 25
6.2.4 CHANGE STATUS ACK PDU . 25
6.2.5 DEASSIGN PDU . 26
6.2.6 DEASSIGN ACK PDU . 26
6.2.7 GROUP PROVIDE PDU . 27
6.2.8 GROUP PROVIDE ACK PDU . 27
6.2.9 INTERROGATE PDU . 28
6.2.10 INTERROGATE ACK PDU . 29
6.3 PDU information elements . 29
6.3.1 Acknowledgement request . 29
6.3.2 Air Interface encryption state. 30
6.3.3 DMO channel mnemonic name . 30
6.3.4 DMO frequency . 30
6.3.5 DMO group deassign type . 31
6.3.6 DMO group definition . 31
6.3.7 DMO group mnemonic name . 31
6.3.8 DMO group status . 32
6.3.9 DMO group status change type. 32
6.3.10 Encryption key number . 32
6.3.11 Group Short Subscriber Identity . 32
6.3.12 Interrogate type . 33
6.3.13 Maximum response time . 33
6.3.14 Mobile Network Identity . 33
6.3.15 PDU type . 34
6.3.16 Reserved information element present . 34
6.3.17 Result code. 35
6.3.18 Type 5 element identifier (informative) . 35
6.3.19 Unique DMO group identifier . 36
6.4 Type 5 information element description (informative). 36
6.4.1 Type 5 information element definition . 36
6.4.2 Type 5 element length . 37
6.4.3 Type 5 element length extension . 37
6.4.4 Type 5 information element . 37
7 Interactions with other services . 38
7.1 Direct mode . 38
7.2 Direct mode dual watch . 38
7.3 Intersystem interface . 38
Annex A (normative): Service or action not supported U/D FACILITY PDU option. 39
Annex B (normative): Service or action not supported SDS-TL PDU option . 40
Annex C (informative): Change Requests . . 41
History . 42

ETSI
5 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Terrestrial Trunked Radio
(TETRA).
The present document is part 18, sub-part 3 of a multi-part deliverable covering the Terrestrial Trunked
Radio (TETRA); the Voice plus Data (V+D), as identified below:
EN 300 392-1: "General network design";
EN 300 392-2: "Air Interface (AI)";
EN 300 392-3: "Interworking at the Inter-System Interface (ISI)";
ETS 300 392-4: "Gateways basic operation";
TS 100 392-5: "Peripheral Equipment Interface (PEI)";
TS 100 392-7: "Security";
EN 300 392-9: "General requirements for supplementary services";
EN 300 392-10: "Supplementary services stage 1";
TS 100 392-11: "Supplementary services stage 2";
TS 100 392-12: "Supplementary services stage 3";
ETS 300 392-13: "SDL model of the Air Interface (AI)";
ETS 300 392-14: "Protocol Implementation Conformance Statement (PICS) proforma specification";
TS 100 392-15: "TETRA frequency bands, duplex spacings and channel numbering";
TS 100 392-16: "Network Performance Metrics";
TR 100 392-17: "TETRA V+D and DMO specifications";
TS 100 392-18: "Air interface optimized applications".
Sub-part 1: "Location Information Protocol (LIP)";
Sub-part 2: "Net Assist Protocol (NAP)".
Sub-part 3: "Direct mode Over The Air Management protocol (DOTAM)".
NOTE: Part 10, sub-part 15 (Transfer of control), part 13 (SDL) and part 14 (PICS) of this multi-part deliverable
are in status "historical" and are not maintained.
ETSI
6 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
1 Scope
The present document defines the Direct mode operation Over The Air Management protocol for the TETRA V+D air
interface. It defines the following services:
• Direct Mode Operation over the air management service.
• Interrogation of Direct Mode Operation groups and their status.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI EN 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 1: General network design".
[2] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 2: Air Interface (AI)".
[3] ETSI EN 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 9: General requirements for supplementary services".
[4] ETSI TS 100 392-15: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 15: TETRA frequency bands, duplex spacings and channel numbering".
[5] ETSI EN 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".
[6] ETSI EN 300 396-6: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation (DMO);
Part 6: Security".
[7] ETSI EN 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);
Part 7: Security".
ETSI
7 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
[i.1] ETSI TS 100 392-18-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D) and Direct
Mode Operation (DMO); Part 18: Air interface optimized applications; Sub-part 1: Location
Information Protocol (LIP)".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in EN 300 392-2 [2] and EN 300 396-3 [5]
and the following apply:
assign: addition of group definition
assigned DMO group: DMO group with a valid parameter set, which has been assigned by a network operator
deassign: permanent removal of group definition
default DMO group: preferred DMO group which is selected when a mobile station switches from V+D to DMO
NOTE: A default DMO group is both, an assigned and a preferred DMO group.
DMO channel: Radio Frequency (RF) carrier for DMO usage
DMO group: DMO group defined by the parameter set: a TETRA group address, a mnemonic group name, a DMO
channel, and a mnemonic DMO channel name
NOTE: DMO groups contain some additional parameters to the above list that is seen on the user's point of view.
management server: entity that manages DMO equipment
management source: originator of DMO management commands
preferred DMO group: assigned DMO group which has been assigned to a specific organisation for preferred usage
NOTE: There can be multiple preferred DMO groups defined at the same time.
selected DMO group: DMO group that MS user has selected
NOTE: A selected DMO group is a default, a preferred or an assigned DMO group.
Switching And Management Infrastructure (SwMI): all of the TETRA equipment for a Voice plus Data (V+D)
network except for subscriber terminals
TETRA domain: all entities that are addressed using TETRA defined addresses
NOTE: This definition may cover entities that are not controlled by TETRA security features.
ETSI
8 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
3.2 Symbols
For the purposes of the present document, the following symbols apply:
ra relationship between management server entity and managed DMO entity
rb relationship between management source entity and management server entity
rc relationship between management source entity and managed DMO entity
rd relationship between communication management entity and management server entity
re relationship between authentication entity and management server entity
rf relationship between group number and radio resource management entity and management
server entity
rg relationship between communication management entity and authentication entity.
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
C Conditional
DGNA Dynamic Group Number Assignment
DMO Direct Mode Operation
DOTAM Direct mode operation Over The Air Management
FE Functional Entity
GTSI Group TETRA Subscriber Identity
ISDN Integrated Services Digital Network
ISSI Individual Short Subscriber Identity
ITSI Individual TETRA Subscriber Identity
M Mandatory
MNI Mobile Network Identity
MS Mobile Station
MS-ISDN Mobile Station ISDN number
OTAK Over The Air Keying
OTAR Over The Air Re-keying
PDU Protocol Data Unit
RF Radio Frequency
SAP Service Access Point
SCK Static Cipher Key
SDS-TL Short Data Service - Transport Layer
SS-DGNA Supplementary Service Dynamic Group Number Assignment
SwMI Switching And Management Infrastructure
V+D Voice plus Data system
4 Direct mode operation over the air management
protocol
4.1 General
The Direct mode operation Over The Air Management (DOTAM) is a TETRA air interface management protocol that
could utilize various transport mechanisms.
The present document defines "control messages" to set and modify MS behaviour in DMO.
The management protocol can be used in various system configurations including:
• SwMI to MS communication.
• Management server to MS communication.
• MS to management server communication.
ETSI
9 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
NOTE 1: Although DOTAM protocol can support direct MS to individual MS communication; the use of it may be
limited to specific situations and is outside the scope of the present document.
NOTE 2: DOTAM does not preclude the usage of pre-configured group and/or frequency settings. It is outside the
scope of the present document how DOTAM and pre-configured group and/or frequency settings may
interact.
The DOTAM protocol may be a member of various other MS over the air management services such as:
• DGNA - V+D group management;
• Phonebook management - ISSI & MS-ISDN management;
• Remote programming of Status message mnemonics;
• Remote programming of technical parameters (timers, etc.);
• Remote software upgrade;
• OTAR/OTAK.
The first on the list is covered by SS-DGNA. The second is in relation to the first one and to the present document, but
is outside the scope of the present document.
4.2 DOTAM protocol system architecture
The DOTAM protocol is used between various entities of the TETRA network. Physical entities identified for the
purpose of the present document are:
• Mobile Station (MS).
• Management server.
• SwMI.
• Management source.
The management server details are outside the scope of the present document.
The management information exchange contains scenarios:
• Management server to managed MS in the TETRA V+D domain.
• Management source equipment to Management server.
• Management source MS to managed MS in DMO without any action in any other entities.
For the purposes of the present document, the TETRA domain consists of entities that are addressable using TETRA
addressing and understand the binary format of the DOTAM protocol.
For the purposes of the present document protocol Functional Entities (FE) are used in some clauses instead of physical
entities:
FE1: Managed entity.
FE2: Management server entity.
FE3: Management source entity.
The following relationships exit between these FEs:
ra: Relationship between management server entity and managed entity.
rb: Relationship between management source entity and management server entity.
rc: Relationship between management source entity and managed entity.
ETSI
10 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
In figure 4.1 the management server FE2 acts as the source entity of management information and manages the FE1
entity.
Managed entity Management server
ra
FE1 FE2
Figure 4.1: Management server and managed entity relationship
In figure 4.2 the management source FE3 defines DMO groups and DMO frequencies for the managed entity FE1.
Managed entity Management server Management source
ra rb
FE1 FE2 FE3
Figure 4.2: Management source, management server, and managed entity relationship
In figure 4.3 a management source FE3 controls the managed entity FE1 without involvement of a management server.
NOTE: This optional arrangement may be used in special cases where a controlled end to end communication is
arranged and the management source is authorised. This usage is outside the scope of the present
document.
Managed entity Management source
rc
FE1 FE3
Figure 4.3: Management source and managed entity direct relationship
The management server entity can be sub-divided into sub-entities:
FE21: Communication management entity.
FE22: Management server entity.
FE23: Authentication entity.
FE24: Group number and radio resource management entity.
ETSI
11 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
The following relationships exit between these FEs:
rd: Relationship between communication management entity and management server entity.
re: Relationship between authentication entity and management server entity.
rf: Relationship between group number and radio resource management entity and management
server entity.
rg: Relationship between communication management entity and authentication entity.
Functional entity FE2 and its sub-entities FE21, FE22, FE23 and FE24 are presented in figure 4.4.
Communication Management server
management entity entity
rd
FE21 FE22
ra  rb
re
rg rf
FE23 FE24
Authentication Group number and
entity radio resource management
entity
Figure 4.4: Management server sub-entities relationships
4.3 DOTAM protocol service description
4.3.1 General on DOTAM services
The DOTAM protocol can support multiple services. Typical services are:
• Assignment of DMO group definition (addition of a DMO group and/or DMO frequency).
• Deassignment of DMO group definition (removal of a group).
• Allocation or status change of a DMO group.
• Interrogation of DMO group definitions.
4.3.2 Services available at the DOTAM-SAP
DOTAM-SAP at the management server offers services to the DOTAM manager entity and is accessible to the human
users. The man machine interface is outside the scope of the present document.
DOTAM-SAP at the MS is a conceptual service access point and is not intended to be accessible by human users.
ETSI
12 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
4.3.3 Service primitives at the DOTAM-SAP
Service primitives at the DOTAM-SAP define service access at management source:
DOTAM-Assign response: this primitive is used to acknowledge assignments.
DOTAM-Assign indication: this primitive is used to receive assignments.
DOTAM-Define confirmation: this primitive is used to receive acknowledgements to the DMO group and frequency
definition requests.
DOTAM-Define request: this primitive is used to send DMO group and frequency definition requests.
DOTAM-Interrogate confirmation: this primitive is used to receive DMO group interrogation results.
DOTAM-Interrogate indication: this primitive is used to receive DMO group interrogation requests.
DOTAM-Interrogate request: this primitive is used to send DMO group interrogation requests.
DOTAM-Interrogate response: this primitive is used to send DMO group interrogation results.
DOTAM-Remove confirmation: this primitive is used to receive DMO group removal results.
DOTAM-Remove indication: this primitive is used to receive DMO group removal requests.
DOTAM-Remove request: this primitive is used to send DMO group removal requests.
DOTAM-Remove response: this primitive is used to send DMO group removal responses.
DOTAM-Status request: this primitive is used to send DMO group status change requests.
DOTAM-Status indication: this primitive is used to receive DMO group status change requests.
DOTAM-Status response: this primitive is used to send response to the DMO group status change requests.
DOTAM-Status confirmation: this primitive is used to receive response to the DMO group status change requests.
4.3.4 Service primitive parameters at the DOTAM-SAP
As the present document does not define a physical access to the DOTAM-SAP, the description of the conceptual
service primitives is minimized and the service primitive parameters are implied by the information elements in the
PDUs, refer to clause 6.2.
4.3.5 State description
The location information protocol uses a single state at the FEs that does not link request and response together. At that
state DOTAM sends and receives all the service primitives and PDUs.
5 DOTAM protocol description
5.1 Description of information elements
5.1.1 Acknowledgement request
Acknowledgement request shall define whether a confirmation is expected for the message.
NOTE 1: Acknowledgement request in a "request" control message means that confirmation of receipt is requested
using the corresponding "response" control message.
NOTE 2: Behaviour on failure to receive a requested confirmation is not defined.
ETSI
13 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
5.1.2 Air interface encryption state
The Air interface encryption state defines security level of DMO communication, refer to EN 300 396-6 [6], clause 4.1.
5.1.3 DMO frequency
The DMO frequency shall comprise DMO carrier frequency (12 bits), Frequency band (4 bits) and Offset (2 bits).
5.1.4 DMO frequency mnemonic name
The DMO frequency mnemonic name is an optional information element that can be used at man machine interface to
identify the DMO frequency.
5.1.5 DMO group status
The DMO group status defines the purpose of a DMO group:
• Assigned, a DMO group with a valid parameter set.
NOTE 1: DMO groups are normally assigned by a network operator.
• Default, a preferred DMO group that is selected when a mobile station moves from V+D to DMO.
• Preferred, one or more assigned DMO groups that should be used in normal operations.
At the same time DMO group can be:
• selected, a DMO group selected for use; or
• not selected, any other than the selected DMO group.
NOTE 2: While in DMO mode the selection of a DMO group overrides the other DMO group settings, but does not
modify the status of any DMO group.
The DMO group status values form a hierarchical structure:
• Assigned DMO group is the base status.
• Preferred DMO group is an assigned DMO group that is nominated to be a preferred one.
• Default DMO group is a preferred DMO group and as such an assigned DMO group that is nominated to be a
default group.
Removal of the preferred DMO group status changes that group into an assigned DMO group; and removal of the
default DMO group status changes that group into a preferred DMO group unless defined otherwise in the protocol.
The support of default and preferred DMO groups is optional. If a default DMO group is supported then at least one
preferred DMO group shall be supported.
5.1.6 DMO group mnemonic name
The DMO group mnemonic name is an optional information element that can be used at man machine interface to
identify the DMO group.
5.1.7 Encryption key number
The Encryption key number defines the SCK that is used in encrypted DMO communication.
ETSI
14 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
5.1.8 Group number
The Group number shall comprise Country code (10 bits), Network code (14 bits) and Group Short Subscriber Identity
(24 bits) as defined in EN 300 392-1 [1], clause 7. Group number is a part of the Unique DMO group identity and is not
used as a separate information element in the PDUs.
5.1.9 Selected group
The selected group is the group that is used in DMO either due to default or selected DMO group action or DMO user
selection. DMO user may select any assigned DMO group. It is outside the scope of the present document whether
DMO user may select any assigned DMO group or only any of the preferred DMO groups.
5.1.10 Unique DMO group identifier
Parameters for identification of a DMO group contain:
• GTSI or GSSI.
• Group mnemonic name.
• DMO frequency.
• DMO channel mnemonic name.
• DMO group status.
• Encryption level.
DOTAM protocol uses as the unique DMO group identifier a GTSI and DMO frequency combination and some
additional bits.
NOTE: The MNI of the GTSI part of the Unique DMO group identifier may be implied in the PDU construction.
The Unique DMO group identifier is a label to a set of DMO group parameters and it supports any combination of those
parameters so that the whole set can be identified and managed using only it. E.g. there can be a DMO group that uses
the same GTSI and DMO frequency, but has two different security levels. On the users point of view those may be
separated by their group name, but on the DOTAM protocol point of view they are separated by their Unique DMO
group identifier.
5.2 Information flows
5.2.1 General on information flows
The information flows in clauses 5.2.2 to 5.2.5 present typical implementations of DOTAM protocol services. The
service primitives are defined in clause 4.3.3. The information flows use the PDU names as defined in clause 5.7 or
descriptive names, if no PDU is defined in the present protocol.
Information flows inside FE2 are outside the scope of the present document.
ETSI
15 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
5.2.2 MS receiving DMO group assignment without an acknowledgement
DMO capable MS may receive DMO group assignment without an acknowledgement request as presented in
figures 5.1 and 5.2. DOTAM entity in FE1 stores the parameters.
Information flows for change status and deassignment are the same as for the assignment.
MS Management server
FE1 FE2
DOTAM-Assign indication 101 ASSIGN 201 DOTAM-Assign request

Figure 5.1: MS receiving DMO assignment
MS Management server Management source
FE1 FE2 FE3
DOTAM-Assign indication 101 ASSIGN 202 ASSIGN 301 DOTAM-Assign request

Figure 5.2: MS receiving DMO assignment, separate management source
5.2.3 MS receiving DMO group assignment with an acknowledgement
DMO capable MS may receive a DMO group assignment and send an acknowledgement as presented in figures 5.3 to
5.5. The DOTAM entity stores the parameters.
Information flows for change status and deassignment are the same as for the assignment.
MS Management server
FE1 FE2
DOTAM-assing indication 102 ASSIGN 208 DOTAM-Assign request
DOTAM-Assign response 103 ASSIGN ACK 204 DOTAM-Assign confirmation
Note
NOTE: DOTAM-Assign confirmation is optional.

Figure 5.3: MS receiving DMO assignment and sending response to it
ETSI
16 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
MS Management server Management source
FE1 FE2 FE3
102 203 302
DOTAM-Assign indication ASSIGN ASSIGN DOTAM-Assign request
205 303
ASSIGN ACK DOTAM-Assign confirmation
DOTAM-Assign response 103 ASSIGN ACK 206

Figure 5.4: MS receiving DMO assignment and sending response to it - management source
receiving acknowledgement from the management server
MS Management server Management source
FE1 FE2 FE3
DOTAM-Assign indication 102 ASSIGN 203 ASSIGN 302 DOTAM-Assign request
DOTAM-Assign response 103 ASSIGN ACK 207 ASSIGN ACK 303 DOTAM-Assign confirmation

Figure 5.5: MS receiving DMO assignment and sending response to it - management source
receiving acknowledgement from the MS
5.2.4 Deassignment of DMO group definitions
DMO group can be deleted by DEASSIGN information flow as presented in figures 5.1 and 5.2 without
acknowledgements and in figures 5.3 to 5.5 with acknowledgements where ASSIGN information flows and service
primitives are replaced by the corresponding DEASSIGN information flows and service primitives.
5.2.5 Change of status of DMO group definitions
DMO group status can be modified by CHANGE STATUS information flow as presented in figures 5.1 and 5.2 without
acknowledgements and in figures 5.3 to 5.5 with acknowledgements where ASSIGN information flows and service
primitives are replaced by the corresponding CHANGE STATUS information flows and service primitives.
ETSI
17 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
5.2.6 Interrogation of DMO group definitions
Optionally, an MS may receive a request to report DMO group definitions at any time and may respond to it as
presented in figures 5.6 and 5.7.
MS Management server
FE1 FE2
DOTAM-Interrogate indication 110 INTERROGATE 210 DOTAM-Interrogate request
DOTAM-Interrogate response 111 INTERROGATE ACK 211 DOTAM-Interrogate confirmation
…etc. .etc. …etc.
DOTAM-Interrogate response 111 INTERROGATE ACK 211 DOTAM-Interrogate confirmation

Figure 5.6: Management server interrogates DMO groups
MS Management server Management source
FE1 FE2 FE3
110 212 311
DOTAM-Interrogate indication INTERROGATE INTERROGATE DOTAM-Interrogate request
DOTAM-Interrogate response 111 INTERROGATE ACK 213 INTERROGATE ACK 312 DOTAM-Interrogate confirmation

Figure 5.7: Management source interrogates DMO groups
5.3 Functional entity actions
5.3.1 FE1 actions
101: Upon reception of an assignment, FE1 shall store the DMO group definition for usage. If the DMO group
definition already exists then the new definition shall replace the old one.
Upon reception of a deassignment, FE1 shall remove the DMO group definition. FE1 may refuse to remove
DMO group assignment; the reasons for the refusal are outside the scope of the present document.
If the DMO group definition storage or deassignment fails, FE1 shall take no further action.
Upon reception of a DMO status, FE1 shall store the new status for usage. If the DMO group does not exist,
then FE1 shall ignore the DMO status definition.
If the DMO status value is not allowed in the FE1, then FE1 shall not change the status of the group and shall
take no further action.
ETSI
18 ETSI TS 100 392-18-3 V1.1.1 (2009-11)
102: Upon reception of an assignment, FE1 shall store the DMO group definition for usage and send an
acknowledgement (103). If the DMO group definition already exists, then the new definition shall replace the
old one.
Upon reception of a deassignment, FE1 shall remove the DMO group definition and send an acknowledgement
(103) as requested. FE1 may refuse to remove DMO group assignment; the reasons for the refusal are outside
the scope of the present document.
If the DMO group definition storage or removal fails,
...