Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 5: Gateway air interface

REN/TETRA-08079-5

Prizemni snopovni radio (TETRA) – Tehnične zahteve za neposredni način delovanja (DMO) – 5. del: Radijski vmesnik prehoda

General Information

Status
Published
Publication Date
16-May-2006
Current Stage
12 - Completion
Due Date
12-May-2006
Completion Date
17-May-2006
Mandate

Buy Standard

Standard
EN 300 396-5 V1.2.1:2006
English language
275 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST EN 300 396-5 V1.2.1:2006
01-julij-2006
3UL]HPQLVQRSRYQLUDGLR 7(75$ ±7HKQLþQH]DKWHYH]DQHSRVUHGQLQDþLQ
GHORYDQMD '02 ±GHO5DGLMVNLYPHVQLNSUHKRGD
Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation
(DMO); Part 5: Gateway air interface
Ta slovenski standard je istoveten z: EN 300 396-5 Version 1.2.1
ICS:
33.070.10 Prizemni snopovni radio Terrestrial Trunked Radio
(TETRA) (TETRA)
SIST EN 300 396-5 V1.2.1:2006 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST EN 300 396-5 V1.2.1:2006

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

SIST EN 300 396-5 V1.2.1:2006

ETSI EN 300 396-5 V1.2.1 (2006-05)
European Standard (Telecommunications series)


Terrestrial Trunked Radio (TETRA);
Technical requirements for Direct Mode Operation (DMO);
Part 5: Gateway air interface

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

SIST EN 300 396-5 V1.2.1:2006
 2 ETSI EN 300 396-5 V1.2.1 (2006-05)



Reference
REN/TETRA-08079-5
Keywords
air interface, gateway, protocol, radio, TETRA
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

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 2006.
All rights reserved.

TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI 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.
ETSI

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

SIST EN 300 396-5 V1.2.1:2006
 3 ETSI EN 300 396-5 V1.2.1 (2006-05)
Contents
Intellectual Property Rights.16
Foreword.16
1 Scope.17
2 References.17
3 Definitions and abbreviations.18
3.1 Definitions.18
3.2 Abbreviations.21
4 Overview of protocol.23
4.1 General.23
4.2 The DM channel.24
4.3 DM call procedures for operation with a gateway.25
4.3.1 Constraints on the frame structure .27
4.3.2 Setting up a call through a DM-GATE .27
4.3.2.1 Group call from TMO to DM-MS via a DM-GATE.28
4.3.2.2 Group call from DM-MS via a DM-GATE.30
4.3.2.3 Individual call from TM-MS to DM-MS via a DM-GATE .32
4.3.2.4 Individual call from DM-MS to TM-MS via a DM-GATE .35
4.3.3 Changeover in a call via a DM-GATE.37
4.3.4 Pre-emption of a direct mode call through a DM-GATE.39
4.3.5 Short Data Service through a gateway.40
4.3.6 Group call from DM-MS via DM-REP/GATE.41
5 DM-MS layer 3 service description (for operation with a gateway).42
5.1 Introduction.42
5.2 Services offered at the DMCC-SAP.42
5.3 Description of primitives at the DMCC-SAP.43
5.4 Description of parameters at the DMCC-SAP.43
5.5 States for DMCC-SAP.44
5.6 Services offered at the DMMM-SAP .44
5.7 Description of primitives at the DMMM-SAP .45
5.7.1 DMMM-REGISTRATION primitive.45
5.7.2 DMMM-REPORT primitive.46
5.8 Description of parameters at the DMMM-SAP.46
6 DM-MS layer 3 protocol (for operation with a gateway).47
6.1 Introduction.47
6.1.1 DMCC protocol states .47
6.1.2 DMMM protocol states.47
6.1.2.1 NOT-REGISTERED.47
6.1.2.2 WAIT-REGISTRATION.47
6.1.2.3 REGISTRATION-ACCEPTED.47
6.1.2.4 REGISTRATION-REJECTED.47
6.2 Circuit mode calls.48
6.2.1 Procedures for outgoing call set-up through a gateway .48
6.2.1.1 Outgoing call set-up .48
6.2.1.2 Temporary group address.51
6.2.1.3 Layer 3 addressing in DM-GSETUP PDU.51
6.2.1.3.1 Called party address .51
6.2.1.3.2 Area selection.51
6.2.1.3.3 Calls to external subscribers .51
6.2.1.3.4 Calling party address .51
6.2.2 Procedures for incoming call set-up.51
6.2.2.1 Incoming call set-up without presence check.51
6.2.2.2 Incoming call set-up with presence check.51
6.2.2.3 Transmitting Party Number Identification (TPNI) during incoming call set-up .52
ETSI

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

SIST EN 300 396-5 V1.2.1:2006
 4 ETSI EN 300 396-5 V1.2.1 (2006-05)
6.2.3 Usage of DM-OCCUPIED PDU .52
6.2.3.1 Sending of DM-OCCUPIED PDU by master DM-MS.52
6.2.3.2 Late entry by slave DM-MS.52
6.2.4 Procedures during occupation.52
6.2.4.1 Master DM-MS.52
6.2.4.2 Slave DM-MS.53
6.2.4.3 Transmitting Party Number Identification (TPNI) during occupation .54
6.2.4.3.1 Master DM-MS.54
6.2.4.3.2 Slave DM-MS.55
6.2.5 Procedures during reservation.55
6.2.5.1 Master DM-MS.55
6.2.5.2 Slave DM-MS.55
6.2.5.3 Pre-emption of short data sent as a transaction within a circuit mode call.56
6.2.6 Procedures to set up a new call by pre-emption.56
6.3 Short Data Service (SDS) procedures .56
6.3.1 Sending short data.57
6.3.1.1 Sending short data on a free channel.57
6.3.1.1.1 Sending unacknowledged short data on a free channel .57
6.3.1.1.2 Sending acknowledged short data on a free channel .57
6.3.1.2 Sending short data by pre-emption.58
6.3.1.3 Sending short data during circuit mode transmission.58
6.3.1.4 Sending short data as a transaction within a circuit mode call.58
6.3.1.4.1 Pre-emption to send short data as a transaction within a circuit mode call .58
6.3.1.4.2 Changeover to send short data as a transaction within a circuit mode call.58
6.3.1.4.3 Sending the short data as master of the circuit mode call.58
6.3.2 Receiving short data.59
6.3.2.1 Receiving unacknowledged short data.59
6.3.2.2 Receiving acknowledged short data.59
6.3.3 Additional addressing.59
6.3.3.1 DM-MS sending short data .59
6.3.3.2 DM-MS receiving short data.59
6.3.4 Extended error protection .59
6.3.5 SDS-TL service in DMO .59
6.3.5.1 Service primitives at the DMTL-SAP .60
6.3.5.2 DMTL-SDS primitives' parameters .60
6.3.5.3 DMTL-SDS PDUs.60
6.3.5.4 DMTL-SDS procedures.60
6.4 Procedures for mobility management.60
6.4.1 Solicited registration.60
6.4.2 Unsolicited registration.61
6.4.3 Cancellation of registration by gateway.61
6.4.4 Other criteria for DMMM state change .62
6.4.5 Action on entering state REGISTRATION-REJECTED.62
6.4.6 Layer 3 addressing in DM-GREGISTER REQUEST PDU.62
6.5 Usage of DMA-UNITDATA primitive.62
6.5.1 Sending a DMCC PDU.62
6.5.2 Sending a DMMM PDU .63
6.5.3 Protocol control function for delivery of received message .63
6.6 General procedures.63
6.6.1 Usage restriction type and validity time .63
7 DM-MS layer 2 service description (for operation with a gateway).64
7.1 Introduction.64
7.2 Layer 2 architecture.64
7.3 Service descriptions.64
7.3.1 Services at the DMA-SAP .64
7.3.1.1 Services provided to layer 3.64
7.3.1.2 Service primitives at the DMA-SAP .64
7.3.1.2.1 DMA-REPORT primitive.64
7.3.1.2.2 DMA-UNITDATA primitive.65
7.3.2 Services at the DMC-SAP .65
7.3.2.1 Services provided to layer 3.65
ETSI

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

SIST EN 300 396-5 V1.2.1:2006
 5 ETSI EN 300 396-5 V1.2.1 (2006-05)
7.3.2.2 Service primitives at the DMC-SAP .65
7.3.2.2.1 DMC-CONFIGURE primitive.65
7.3.2.2.2 DMC-REPORT primitive.65
7.3.3 Services at the DMD-SAP .66
7.3.3.1 Services provided to the U-plane application.66
7.3.3.2 Service primitives at the DMD-SAP .66
7.4 Parameter listing.66
8 DM-MS layer 2 protocol (for operation with a gateway).67
8.1 Introduction.67
8.1.1 Functions of lower MAC .67
8.1.2 Functions of upper MAC .67
8.2 Interface between lower and upper MAC.68
8.2.1 Logical channels defined at the DMV-SAP.68
8.2.2 Service primitives at the DMV-SAP.68
8.2.3 PDU mapping of the logical channels at the DMV-SAP.68
8.2.4 Scrambling mechanism.68
8.2.5 PDU error detection.69
8.2.6 Modes of operation .69
8.3 Basic capabilities of the physical layer.69
8.3.1 DM-MS capabilities.69
8.3.1.1 DM only and dual mode capable MS operation.69
8.3.1.2 Dual watch capable MS operation .69
8.4 Usage of DM channel with gateway.69
8.4.1 Definition of DM channel.70
8.4.1.1 DM channel arrangement.70
8.4.1.1.1 DM channel arrangement for operation with a DM-GATE.70
8.4.1.1.2 DM channel arrangement for operation with a type 1A DM-REP/GATE.70
8.4.1.1.3 DM channel arrangement for operation with a type 1B DM-REP/GATE.71
8.4.1.2 DM channel operation.71
8.4.2 DM-MAC states.72
8.4.2.1 DM-MAC state definitions .72
8.4.2.2 DM-MS channel surveillance procedures .73
8.4.2.2.1 Initial determination of DM channel state .73
8.4.2.2.1.1 Initial determination of state of carrier.73
8.4.2.2.1.2 Determination of state of one DM channel when other DM channel is busy .74
8.4.2.2.2 Fast call set-up surveillance in idle mode.74
8.4.2.2.2.1 Fast call set-up surveillance when idle on a free carrier .74
8.4.2.2.2.2 Fast call set-up surveillance when idle on a carrier that is not free.75
8.4.2.2.3 DM-MS channel surveillance at call set-up (circuit mode call or short data message) .75
8.4.2.2.4 DM-MS channel surveillance for registration outside the registration phase.75
8.4.2.3 Master DM-MS channel maintenance procedures during a call transaction.76
8.4.2.4 Slave DM-MS channel maintenance procedures during a call.77
8.4.2.4.1 Slave MS channel maintenance during call transaction .77
8.4.2.4.2 Slave MS signal quality measurement during call transaction .77
8.4.2.4.3 Slave MS channel maintenance during reservation .77
8.4.3 Criteria for changing DM-MAC states .77
8.4.3.1 Criteria for changing DM-MAC state for master DM-MS.77
8.4.3.2 Criteria for changing DM-MAC state for slave DM-MS.77
8.4.3.3 Criteria for changing DM-MAC state for idle DM-MS .78
8.4.4 DM-MS channel monitoring procedures .79
8.4.4.1 DM channel when setting up a circuit mode call through a gateway.79
8.4.4.2 DM channel when receiving a circuit mode call set-up from a gateway.80
8.4.4.3 DM channel in occupation during a circuit mode call.80
8.4.4.4 DM channel in reservation during a circuit mode call .80
8.4.4.5 DM channel in occupation during an SDS call .80
8.4.4.6 DM channel during pre-emption signalling .81
8.4.4.7 DM channel during registration phase .81
8.4.4.8 DM channel in occupation for an unsolicited registration .81
8.4.5 Transmission of layer 3 messages by DM-MAC.82
8.4.5.1 Transmission of C-plane messages by DM-MAC.82
8.4.5.1.1 Transmitting DM-SETUP.82
ETSI

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

SIST EN 300 396-5 V1.2.1:2006
 6 ETSI EN 300 396-5 V1.2.1 (2006-05)
8.4.5.1.2 Transmitting DM-SETUP PRES.82
8.4.5.1.3 Transmitting DM-CONNECT.82
8.4.5.1.4 Transmitting DM-DISCONNECT.82
8.4.5.1.5 Transmitting DM-CONNECT ACK.82
8.4.5.1.6 Transmitting DM-RELEASE.82
8.4.5.1.7 Transmitting DM-OCCUPIED.
...

Questions, Comments and Discussion

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