SIST ETS 300 396-5 E1:2003

• Abstract:

  To define the technical requirements for DMO gateways.

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Mandate: BC-T-344
• Mandate: T-172
• Ref Project: ETSI ETS 300 396-5 ed.1 (2000-01) - Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 5: Gateway air interface

SIST ETS 300 396-5 E1:2003 is the SIST version of ETS 300 396-5 Edition 1 for Terrestrial Trunked Radio (TETRA) Direct Mode Operation (DMO). It specifies the gateway air interface used to connect Direct Mode Mobile Stations (DM-MS) to the TETRA Voice plus Data (V+D) system, including both DM-GATE and DM-REP/GATE implementations. Engineers use it to design, integrate and test gateway call control, short data, mobility management, and the DM radio link.

What does SIST ETS 300 396-5 E1:2003 specify?

SIST ETS 300 396-5 E1:2003 focuses on the Direct Mode gateway air interface. It covers how a gateway relays traffic between the DM and V+D sides, and it applies to a standalone DM-GATE as well as a combined DM-REP/GATE.

The document says the gateway may use either a type 1A repeater, operating on a single DM RF carrier, or a type 1B repeater, operating on a pair of duplex-spaced DM RF carriers. The choice of the DM RF carrier(s) is not standardized in this part.

The standard is organized into clauses 1 to 17, followed by two normative annexes. Early clauses define the scope, references, terms and protocol overview; the middle clauses describe DM-MS and gateway services and protocols; later clauses cover gateway call control, mobility management, U-plane conversion, layer 2 behavior, PDU coding, radio aspects, and the gateway V+D protocol stack.

Annex	What it covers
Annex A	DM timers and constants in the DM-MS and gateway, including layer 2 and layer 3 values and maximum frame transmission counts
Annex B	V+D elements required for DM gateway operation, including DM-MS address and U-MM STATUS / D-MM STATUS elements

What are the key requirements of SIST ETS 300 396-5 E1:2003?

The main requirement is that the gateway shall interwork between the DM and V+D air interfaces and support only one call at a time on the DM side. In practice, that means gateway implementations must be built around a single active call context, not multiple parallel DM calls on the same DM RF resource.

• Clause 4 and 13 - The gateway relays information between Ud and Um and behaves either as DM-GATE or DM-REP/GATE. This matters because the same protocol model has to work for both a direct gateway and a repeater/gateway combination.
• Clauses 4.2, 8.4 and 13.4 - A DM channel can be free, occupied, reserved, or in a registration phase. The access rules change with each state, so terminals and gateways need state-aware channel surveillance before they transmit.
• Clauses 6.2 and 9.3 - Outgoing call set-up through a gateway is a two-phase process. The DM-MS first sends DM-GSETUP and waits for DM-GACK or DM-GCONNECT; after DM-GCONNECT, the DM-MS becomes master and sends DM-SETUP. This is important because implementers must handle the temporary reservation phase and the master/slave role change.
• Clauses 6.2, 9.3 and 13.4 - The document defines procedures for incoming calls, late entry, occupation, reservation, pre-emption and changeover using PDUs such as DM-OCCUPIED, DM-TX REQUEST, DM-PREEMPT, DM-GTX REQUEST, DM-GPREEMPT and DM-GRELEASE. In practice, these procedures decide who may talk, when a call can be interrupted, and how new traffic gains access.
• Clauses 6.3 and 9.4 - Short Data Service (SDS) can be sent on a free channel, by pre-emption, during circuit mode transmission, or as a transaction within an ongoing call. For acknowledged short data, the confirm seen by the DM side reflects successful delivery to the gateway or V+D side, not direct receipt by the called terminal.
• Clauses 6.4, 10 and Annex B - DMMM is optional on the DM-MS, but when used it supports registration and gateway presence information. The gateway also registers to the SwMI using its own ITSI, and registration can be solicited or unsolicited, accepted or rejected, or cancelled. This matters for identity management and for deciding whether a terminal is allowed to attach to the gateway.
• Clauses 7, 8, 12, 13 and Annex A - Layer 2 defines SAPs, primitives and procedures for addressing, fragmentation and reconstruction, fill-bit handling, random access, air interface encryption, timing change, and slot/frame numbering changes. Annex A provides the timers, constants and transmission limits that make these procedures work consistently in real implementations.
• Clauses 14 to 17 - The standard defines gateway-specific PDU formats, information element coding, radio aspects for DM-MS and gateway, synchronization, channel coding and scrambling, and the gateway V+D protocol stack. This is the material used when building interoperable equipment and when writing test cases.

What terms does SIST ETS 300 396-5 E1:2003 define?

• Direct Mode Operation (DMO) - The TETRA mode in which DM-MSs communicate directly on the DM air interface, with optional interworking through a gateway or repeater.
• Direct Mode Gateway (DM-GATE) - A gateway that bridges DM traffic and signalling to the V+D system.
• Direct Mode Repeater/Gateway (DM-REP/GATE) - A combined repeater and gateway implementation used to relay DM communications between DM and V+D, either as type 1A or type 1B.
• Direct Mode Call Control (DMCC) - The layer 3 entity that handles DM calls and short data messages for a DM-MS operating with a gateway.
• Direct Mode Mobility Management (DMMM) - The optional layer 3 entity that handles registration and gateway presence information for a DM-MS.
• Direct Mode Mobile Station (DM-MS) - A mobile station operating in DMO.
• Group Short Subscriber Identity (GSSI) - The group identity used in the DMMM service and in gateway-related registration handling.
• Individual TETRA Subscriber Identity (ITSI) - The individual identity used when the gateway registers to the SwMI.

Who uses SIST ETS 300 396-5 E1:2003?

Gateway manufacturers, TETRA terminal vendors, system integrators, network operators and test laboratories use SIST ETS 300 396-5 E1:2003. They use it to build gateway behavior, verify call set-up and release, implement short data and registration handling, and check DM-side radio and timing behavior.

It is especially relevant when equipment must interwork between Direct Mode and a TETRA V+D network. It also matters to labs and quality teams writing interoperability and protocol tests for DM-GATE and DM-REP/GATE equipment.

What changed in SIST ETS 300 396-5 E1:2003 from the previous edition?

SIST ETS 300 396-5 E1:2003 is identified as identical to ETS 300 396-5 Edition 1.

Which standards are used with SIST ETS 300 396-5 E1:2003?

Standard	What it contributes
ETS 300 396-1	General DMO network design and overall architectural context
ETS 300 396-2	DMO radio aspects that complement the gateway air interface requirements
ETS 300 396-3	The base DMO MS-MS air interface protocol that this gateway part builds on and adapts
ETS 300 392-2	V+D-side protocol detail, especially the call-control behavior referenced for gateway operation
ETS 300 396-6	MM security PDUs used in the short-data and security-related mappings

What does the SIST ETS 300 396-5 E1:2003 document contain?

The document contains the gateway-side protocol model in detail, including service descriptions, service primitives and state machines for DM-MS and gateway behavior. It also contains the procedures for circuit mode calls, short data, registration, pre-emption, changeover and mobility management.

It provides PDU descriptions and information element coding for gateway-specific DM messages, along with mappings between DMO and V+D information elements. Annex A supplies timers and constants, and Annex B lists the V+D elements needed for DM gateway operation.

The later clauses cover the radio aspects of both the DM-MS and the gateway, including modulation, frequency bands, synchronization, channel coding, scrambling and channel multiplexing. These parts are used when implementing equipment and when checking interoperability, timing and radio performance.

SLOVENSKI STANDARD
01-december-2003
3UL]HPQLVQRSRYQLUDGLR7(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: ETS 300 396-5 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-5
TELECOMMUNICATION January 2000
STANDARD
Source: TETRA Reference: DE/TETRA-02007-5
ICS: 33.020
Key words: DMO, radio, security, TETRA
Terrestrial Trunked Radio (TETRA);
Technical requirements for Direct Mode Operation (DMO);
Part 5: Gateway air interface
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: [e-mail] - http://www.etsi.org
Tel.:[phone]- Fax:[phone]
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-5: 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-5: January 2000
Contents
Foreword.19
1 Scope .21
2 Normative references.21
3 Definitions and abbreviations .22
3.1 Definitions .22
3.2 Abbreviations .24
4 Overview of protocol.25
4.1 General .25
4.2 The DM channel.26
4.3 DM call procedures for operation with a gateway .27
4.3.1 Constraints on the frame structure.29
4.3.2 Setting up a call through a DM-GATE .29
4.3.2.1 Group call from V+D to DM-MS via a DM-GATE.29
4.3.2.3 Individual call from V+D MS to DM-MS via a DM-GATE .36
4.3.2.4 Individual call from DM-MS to V+D MS via a DM-GATE .39
4.3.5 Short Data Service through a gateway.48
4.3.6 Group call from DM-MS via DM-REP/GATE.48
5 DM-MS layer 3 service description (for operation with a gateway) .50
5.1 Introduction .50
5.2 Services offered at the DMCC-SAP.50
5.3 Description of primitives at the DMCC-SAP.50
5.4 Description of parameters at the DMCC-SAP .51
5.5 States for DMCC-SAP .51
5.6 Services offered at the DMMM-SAP.51
5.7 Description of primitives at the DMMM-SAP.52
5.7.1 DMMM-REGISTRATION primitive .52
5.7.2 DMMM-REPORT primitive .53
5.8 Description of parameters at the DMMM-SAP.53
6 DM-MS layer 3 protocol (for operation with a gateway).53
6.1 Introduction .53
6.1.1 DMCC protocol states .54
6.1.2 DMMM protocol states.54
6.1.2.1 NOT-REGISTERED.54
6.1.2.2 WAIT-REGISTRATION .54
6.1.2.3 REGISTRATION-ACCEPTED.54
6.1.2.4 REGISTRATION-REJECTED .54
6.2 Circuit mode calls.54
6.2.1 Procedures for outgoing call set-up through a gateway .55
6.2.1.1 Outgoing call set-up.55
6.2.1.2 Temporary group address .57
6.2.1.3 Layer 3 addressing in DM-GSETUP PDU .57
6.2.1.3.1 Called party address .57
6.2.1.3.2 Area selection .57
6.2.1.3.3 Calls to external subscribers.57
6.2.1.3.4 Calling party address .57
6.2.2 Procedures for incoming call set-up.57
6.2.2.1 Incoming call set-up without presence check .57
6.2.2.2 Incoming call set-up with presence check .57
6.2.2.3 Transmitting Party Number Identification (TPNI) during
incoming call set-up.58
6.2.3 Usage of DM-OCCUPIED PDU.58

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

Page 5
ETS 300 396-5: January 2000
7.3.2.2.1 DMC-CONFIGURE primitive.69
7.3.2.2.2 DMC-REPORT primitive .69
7.3.3 Services at the DMD-SAP .69
7.3.3.1 Services provided to the U-plane application.69
7.3.3.2 Service primitives at the DMD-SAP .69
7.4 Parameter listing .70
8 DM-MS layer 2 protocol (for operation with a gateway).71
8.1 Introduction .71
8.1.1 Functions of lower MAC .71
8.1.2 Functions of upper MAC.71
8.2 Interface between lower and upper MAC.71
8.2.1 Logical channels defined at the DMV-SAP.71
8.2.2 Service primitives at the DMV-SAP.71
8.2.3 PDU mapping of the logical channels at the DMV-SAP .71
8.2.4 Scrambling mechanism.72
8.2.5 PDU error detection.72
8.2.6 Modes of operation.72
8.3 Basic capabilities of the physical layer.72
8.3.1 DM-MS capabilities.72
8.3.1.1 DM only and dual mode capable MS operation.72
8.3.1.2 Dual watch capable MS operation .73
8.4 Usage of DM channel with gateway.73
8.4.1 Definition of DM channel .74
8.4.1.1 DM channel arrangement .74
8.4.1.1.1 DM channel arrangement for
operation with a DM-GATE .74
8.4.1.1.2 DM channel arrangement for
operation with a type 1A
DM-REP/GATE.74
8.4.1.1.3 DM channel arrangement for
operation with a type 1B
DM-REP/GATE.74
8.4.1.2 DM channel operation.74
8.4.2 DM channel states.75
8.4.2.1 DM channel state definitions.76
8.4.2.2 DM-MS channel surveillance procedures .76
8.4.2.2.1 Initial determination of DM channel
state .76
8.4.2.2.2 DM-MS channel surveillance in idle
mode.76
8.4.2.2.3 DM-MS channel surveillance at call
set-up (circuit mode call or short data
message) .76
8.4.2.2.4 DM-MS channel surveillance for
registration outside the registration
phase .77
8.4.2.3 Master DM-MS channel surveillance procedures during a
call transaction.78
8.4.2.4 Slave DM-MS channel surveillance procedures during a
call.78
8.4.2.4.1 Slave MS channel surveillance during
call transaction .78
8.4.2.4.2 Slave MS signal quality measurement
during call transaction .78
8.4.2.4.3 Slave MS channel surveillance during
reservation .79
8.4.3 DM-MAC states .79
8.4.3.1 DM-MAC state definitions .79
8.4.3.2 Criteria for changing DM-MAC state.80
8.4.4 DM-MS channel monitoring procedures.81
8.4.4.1 DM channel when setting up a circuit mode call through a
gateway.81

Page 6
ETS 300 396-5: January 2000
8.4.4.2 DM channel when receiving a circuit mode call set-up
from a gateway. 81
8.4.4.3 DM channel in occupation during a circuit mode call. 81
8.4.4.4 DM channel in reservation during a circuit mode call. 82
8.4.4.5 DM channel in occupation during an SDS call . 82
8.4.4.6 DM channel during pre-emption signalling. 82
8.4.4.7 DM channel during registration phase . 83
8.4.4.8 DM channel in occupation for an unsolicited registration. 83
8.4.5 Transmission of layer 3 messages by DM-MAC. 83
8.4.5.1 Transmission of C-plane messages by DM-MAC. 83
8.4.5.1.1 Transmitting DM-SETUP. 83
8.4.5.1.2 Transmitting DM-SETUP PRES. 83
8.4.5.1.3 Transmitting DM-CONNECT. 83
8.4.5.1.4 Transmitting DM-DISCONNECT. 84
8.4.5.1.5 Transmitting DM-CONNECT ACK . 84
8.4.5.1.6 Transmitting DM-RELEASE . 84
8.4.5.1.7 Transmitting DM-OCCUPIED. 84
8.4.5.1.8 Transmitting DM-TX CEASED . 84
8.4.5.1.9 Transmitting DM-TX REQUEST. 84
8.4.5.1.10 Transmitting response to DM-TX
REQUEST . 84
8.4.5.1.11 Transmitting DM-PREEMPT . 85
8.4.5.1.12 Transmitting response to
DM-PREEMPT . 85
8.4.5.1.13 Transmitting DM-SDS UDATA and
DM-SDS DATA. 85
8.4.5.1.14 Transmitting response to DM-SDS
DATA. 85
8.4.5.1.15 Transmitting DM-INFO . 85
8.4.5.1.16 Transmitting DM-GSETUP. 85
8.4.5.1.17 Transmitting DM-GTX REQUEST. 86
8.4.5.1.18 Transmitting DM-GPREEMPT . 86
8.4.5.1.19 Transmitting DM-GREGISTER
REQUEST . 87
8.4.5.1.20 Transmitting DM-GCANCEL ACK. 87
8.4.5.2 Transmission of U-plane messages by DM-MAC. 87
8.4.6 Transmission of layer 2 messages generated by DM-MAC . 88
8.4.6.1 Transmitting DM-RESERVED. 88
8.4.6.2 Transmitting DM-SDS OCCUPIED . 88
8.4.6.3 Transmitting DM-TIMING REQUEST . 88
8.4.6.4 Transmitting DM-TIMING ACK . 88
8.4.7 General DM-MAC procedures . 88
8.4.7.1 DM-MAC repeat transmissions . 88
8.4.7.2 DM-MAC frame countdown procedure . 88
8.4.7.3 Use of timers. 88
8.4.7.4 Linearization. 88
8.4.7.5 Fragmentation. 89
8.4.7.6 Fill bit indication. 89
8.4.7.7 Selection of pseudo address. 89
8.4.7.8 Slot flag indication . 90
8.4.7.9 Requests bitmap . 90
8.4.7.10 Dual watch operation. 90
8.4.7.11 Air interface encryption. 90
8.4.7.12 Channel A or B operation. 90
8.4.7.13 Sending short data as a transaction within a circuit mode
call. 90
8.4.7.14 SDS and registration transaction time remaining. 90
8.4.7.14.1 SDS time remaining . 90
8.4.7.14.2 Registration transaction time
remaining. 90
8.4.7.15 Timing change procedure . 90
8.4.7.16 Timing change at changeover or pre-emption . 91
8.4.7.17 Modification of slot/frame numbering by gateway. 91

Page 7
ETS 300 396-5: January 2000
8.4.7.18 Modification of channel timing by gateway .91
8.5 MAC procedures for transfer of signalling messages.91
8.5.1 Formation of MAC PDU.91
8.5.2 Addressing.92
8.5.2.1 Transmission of message.92
8.5.2.1.1 Addressing in synchronization burst
carrying gateway-specific message .92
8.5.2.1.2 Addressing in synchronization burst
carrying non-gateway-specific
message .93
8.5.2.1.3 Lifetime of pseudo SSI.93
8.5.2.1.4 Additional elements in synchronization
burst .94
8.5.2.1.5 Addressing in normal burst .95
8.5.2.2 Reception of message.95
8.5.2.3 Usage of MNI.96
8.5.3 Use of air interface encryption.96
8.5.4 Fragmentation and reconstruction.96
8.5.4.1 Fragmentation by a DM-MS.96
8.5.4.2 Reconstruction by a DM-MS.97
8.5.5 Fill bit addition and deletion .98
8.5.6 Transmission and reception of messages by layer 2 unacknowledged
service .98
8.5.6.1 Transmission of message.100
8.5.6.2 Reception of message.100
8.5.7 Random access protocol during occupation and reservation periods.102
8.5.7.1 Introduction .102
8.5.7.2 Procedures for master DM-MS.103
8.5.7.2.1 Indicating frames available for
requests .103
8.5.7.2.2 Monitoring frames available for
requests .103
8.5.7.2.3 Response to pre-emption request .104
8.5.7.2.4 Response to timing change request .104
8.5.7.2.5 Response to DM-GRELEASE
message .104
8.5.7.3 Procedures for requesting DM-MS .104
8.5.8 Procedures for sending messages during registration phase .106
8.5.8.1 Procedures for registering DM-MS during registration
phase .106
8.5.8.1.1 Preparing for registration access .106
8.5.8.1.2 First transmission of solicited
registration request .106
8.5.8.1.3 Valid access slots .106
8.5.8.1.4 Waiting for response.106
8.5.8.1.5 Subsequent transmission of request .107
8.5.8.1.6 Abandoning registration access
attempt.107
8.5.8.2 Procedures for pre-empting DM-MS during registration
phase .107
8.5.8.2.1 Preparing for random access.107
8.5.8.2.2 First transmission of pre-emption
request .107
8.5.8.2.3 Valid slots for pre-emption .107
8.5.8.2.4 Waiting for response.107
8.5.8.2.5 Subsequent transmission of request .108
8.5.8.2.6 Abandoning random access attempt .108
8.6 MAC procedures in traffic mode .108
8.6.1 Introduction.108
8.6.2 Criteria for transmission and reception of traffic.109
8.6.3 Change of U-plane mode .109
8.6.3.1 Call set-up by DM-MS.109
8.6.3.2 Incoming call set-up.109

Page 8
ETS 300 396-5: January 2000
8.6.3.2.1 Incoming call set-up without presence
check . 109
8.6.3.2.2 Incoming call set-up with presence
check . 110
8.6.3.3 Late entry . 110
8.6.3.4 End of traffic transmission. 110
8.6.3.4.1 Master DM-MS . 110
8.6.3.4.2 Slave DM-MS . 110
8.6.4 Exchange of information at the DMD-SAP . 110
8.6.5 Stealing from circuit mode capacity. 110
9 Gateway layer 3 call control procedures. 110
9.1 Introduction. 110
9.2 Gateway call control states. 111
9.2.1 Gateway V+D call control states. 111
9.2.1.1 IDLE . 111
9.2.1.2 MO-CALL-SETUP. 111
9.2.1.3 MT-CALL-SETUP. 111
9.2.1.4 CALL ACTIVE . 111
9.2.1.5 CALL DISCONNECT . 111
9.2.1.6 WAIT . 111
9.2.2 Gateway DM call control states . 111
9.2.2.1 IDLE . 111
9.2.2.2 CALL SETUP NORMAL ORIGINATING. 112
9.2.2.3 CALL SETUP PRES_CHECK ORIGINATING. 112
9.2.2.4 CALL SETUP TERMINATING . 112
9.2.2.5 PRE-EMPTION . 112
9.2.2.6 CALL ACTIVE TX OCCUPATION . 112
9.2.2.7 CALL ACTIVE TX RESERVATION. 112
9.2.2.8 CALL ACTIVE RX OCCUPATION . 112
9.2.2.9 WAIT RSP OCCUPATION. 112
9.2.2.10 ACK'D SHORT DATA INITIATED. 112
9.2.2.11 UNACK'D SHORT DATA INITIATED. 112
9.3 Layer 3 circuit mode call control procedures. 112
9.3.1 Incoming call set-up from V+D . 113
9.3.1.1 Incoming individual call set-up from V+D. 113
9.3.1.2 Incoming group call set-up from V+D. 116
9.3.2 Outgoing call set-up to V+D. 117
9.3.2.1 Outgoing call to V+D set-up procedures . 117
9.3.2.2 Colliding call set-up signalling over the V+D air interface
(Um) . 119
9.3.2.3 Unsuccessful call set-up to V+D . 120
9.3.3 Call maintenance procedures . 120
9.3.3.1 End of transmission. 120
9.3.3.1.1 Reception of DM-TX CEASED PDU
from current master DM-MS. 120
9.3.3.1.2 Reception of D-TX CEASED PDU
from V+D . 121
9.3.3.1.3 Gateway initiated DM-TX CEASED. 121
9.3.3.2 Reception of D-TX INTERRUPT from V+D . 121
9.3.3.3 Incoming V+D transmission during DM channel
reservation . 122
9.3.3.4 Reception of a DM request to transmit during DM channel
reservation . 122
9.3.3.4.1 Response to valid DM-GTX
REQUEST (or DM-GPREEMPT) PDU122
9.3.3.4.2 Response to valid DM-TX REQUEST
(or DM-PREEMPT) PDU. 124
9.3.3.5 V+D permission to transmit withdrawn during a call . 125
9.3.3.6 V+D permission to continue with withdrawn call . 125
9.3.3.7 SwMI initiated call continuation . 126
9.3.3.8 Call modification. 126
9.3.3.8.1 DM-MS initiated call modification . 126

Page 9
ETS 300 396-5: January 2000
9.3.3.8.2 SwMI initiated call modification .126
9.3.3.9 Call disconnection.126
9.3.3.9.1 Reception of DM-RELEASE from
current master DM-MS (or call lost).126
9.3.3.9.2 Call disconnection by SwMI .127
9.3.3.9.3 Expiry of call length timer.127
9.3.3.10 V+D call restoration .128
9.3.3.11 Unsolicited D-TX GRANTED PDU .128
9.3.3.12 Extension and end of reservation period .128
9.3.4 Gateway pre-emption procedures .129
9.3.4.1 DM-MS pre-emption of a gateway operating as master .129
9.3.4.1.1 New call pre-emption during call
set-up .129
9.3.4.1.2 New call pre-emption during DM
channel occupation .129
9.3.4.1.3 New call pre-emption during DM
channel reservation.130
9.3.4.1.4 DM-MS pre-emption during DM
channel occupation to continue
existing call .130
9.3.4.1.5 DM-MS pre-emption during DM
channel occupation to send short data
within ongoing call.132
9.3.4.2 Pre-emption procedures during gateway slave operation .133
9.3.4.2.1 Transmission interrupt from V+D.133
9.3.4.2.2 Pre-emption initiated by gateway
during an ongoing call.134
9.3.4.2.3 New call pre-emption by gateway .135
9.3.4.2.4 Pre-emption by another DM-MS .135
9.4 Layer 3 short data service procedures.136
9.4.1 Incoming SDS message from V+D .136
9.4.1.1 Transmission of short data message from V+D using DM
unacknowledged service .136
9.4.1.2 Transmission of short data message from V+D using DM
acknowledged service .136
9.4.1.3 Pre-emption of DM unacknowledged or acknowledged
SDS transaction.137
9.4.1.4 Transmission of short data message from V+D during DM
channel occupation.138
9.4.1.5 Transmission of short data message from V+D during DM
channel reservation .138
9.4.2 Outgoing DM SDS message to V+D .138
9.4.2.1 Reception of outgoing SDS message on DM channel.138
9.4.2.1.1 Reception of outgoing
unacknowledged SDS message on
DM channel.139
9.4.2.1.2 Reception of outgoing acknowledged
SDS message on DM channel.139
9.4.2.2 Reception of DM short data sent within ongoing call.140
9.5 Addressing methods on V+D air interface .140
9.5.1 Receiving group call from V+D.140
9.5.2 Receiving individual call from V+D .141
9.5.3 Call set-up to V+D .141
9.6 Information element mapping between V+D and DM PDUs.141
9.6.1 V+D communication type - DMO call type flag mapping.141
9.6.2 V+D call priority - DMO priority mapping .142
9.6.3 V+D short data type identifier - DMO short data type identifier mapping .142
9.6.4 V+D TX demand priority - DMO priority level mapping .142
10 Gateway layer 3 mobility management procedures .142
10.1 Introduction .142
10.2 Gateway MM states .142
10.2.1 MM protocol states - V+D.142

Page 10
ETS 300 396-5: January 2000
10.2.2 MM protocol states - DM. 143
10.2.2.1 REGISTRATIONS SOLICITED. 143
10.2.2.2 REGISTRATIONS NOT PERMITTED . 143
10.2.2.3 REGISTRATIONS PERMITTED. 143
10.3 Gateway MM procedures . 143
10.3.1 Gateway registration to SwMI . 143
10.3.2 Gateway MM procedures on DM . 143
10.3.3 Receiving DM registration requests. 144
10.3.3.1 Solicited registration requests . 144
10.3.3.2 Unsolicited registration requests . 145
10.3.4 Registration cancellation. 145
10.3.5 Procedures for U-MM STATUS and D-MM STATUS. 146
10.3.5.1 Procedures for sending U-MM STATUS. 146
10.3.5.2 Procedures for receiving D-MM STATUS . 146
11 Gateway U-plane converter . 146
11.1 Introduction. 146
11.2 Start of call transaction. 147
11.2.1 Call transaction from DM to V+D . 147
11.2.2 Call transaction from V+D to DM . 147
11.3 U-plane conversion during call transaction . 148
11.3.1 U-plane conversion from DM to V+D. 148
11.3.2 U-plane conversion from V+D to DM. 149
11.4 Stopping transmission/reception . 149
11.4.1 Call transaction from DM to V+D . 149
11.4.2 Call transaction from V+D to DM . 150
12 Gateway DM layer 2 service description. 150
12.1 Introduction. 150
12.2 Gateway DM layer 2 architecture . 150
12.2.1 Lower layer management in layer 2. 150
12.3 Service descriptions . 151
12.3.1 Services at the GMA-SAP. 151
12.3.1.1 Services provided to layer 3. 151
12.3.1.1.1 Protocol control function for delivery of
received message . 151
12.3.1.2 Service primitives at the GMA-SAP . 151
12.3.1.2.1 GMA-REPORT primitive. 151
12.3.1.2.2 GMA-UNITDATA primitive . 151
12.3.2 Services at the GMC-SAP . 152
12.3.2.1 Services provided to layer 3. 152
12.3.2.2 Service primitives at the GMC-SAP . 152
12.3.2.2.1 GMC-CONFIGURE primitive. 152
12.3.2.2.2 GMC-REPORT primitive . 152
12.3.3 Services at the GMD-SAP . 152
12.3.3.1 Services provided to the U-plane converter . 152
12.3.3.2 Service primitives at the GMD-SAP . 152
12.3.3.2.1 GMD-REPORT primitive . 152
12.3.3.2.2 GMD-UNITDATA primitive . 153
12.4 Parameter listing . 153
13 Gateway DM layer 2 protocol. 154
13.1 Introduction. 154
13.1.1 Functions of lower MAC. 154
13.1.2 Functions of upper MAC . 155
13.2 Interface between lower and upper MAC . 155
13.3 Basic capabilities of the gateway physical layer. 156
13.3.1 DM-GATE capabilities. 156
13.3.2 Type 1A DM-REP/GATE capabilities. 157
13.3.2.1 Type 1A DM-REP/GATE: DM RF carrier in same
sub-band as V+D downlink carrier . 157
13.3.2.2 Type 1A DM-REP/GATE: DM RF carrier in same
sub-band as V+D uplink carrier. 157

Page 11
ETS 300 396-5: January 2000
13.3.2.3 Type 1A DM-REP/GATE: DM RF carrier not in either V+D
sub-band.158
13.3.3 Type 1B DM-REP/GATE capabilities .158
13.4 Usage of DM channel .159
13.4.1 Gateway operation.159
13.4.1.1 DM-GATE operation .159
13.4.1.2 DM-REP/GATE operation.160
13.4.1.2.1 Type 1A DM-REP/GATE: DM RF
carrier in same sub-band as V+D
downlink carrier.161
13.4.1.2.2 Type 1A DM-REP/GATE: DM RF
carrier in same sub-band as V+D
uplink carrier .161
13.4.1.2.3 Type 1A DM-REP/GATE (if DM RF
carrier not in V+D sub-band) or
type 1B DM-REP/GATE.162
13.4.2 Gateway states.162
13.4.2.1 Gateway state definitions.163
13.4.2.2 Gateway channel surveillance procedures .164
13.4.2.2.1 Channel surveillance when idle on a
free channel (i.e. in state 1) .164
13.4.2.2.2 Channel surveillance when idle on a
busy channel (i.e. in state 2, 3 or 4).164
13.4.2.2.3 Channel surveillance when idle at
DM-MS call set-up .165
13.4.2.2.4 Channel surveillance before call
set-up by gateway (circuit mode call or
short data).166
13.4.2.2.5 Channel surveillance before
registration phase .167
13.4.2.2.6 Channel surveillance before
registration cancellation .167
13.4.2.3 Channel surveillance when active during a call .167
13.4.3 Criteria for changing gateway sta
...