SIST EN 300 396-5 V1.2.1:2006

• Abstract:

  The multi-part deliverable EN 300 396 defines the TErrestrial Trunked RAdio (TETRA) Direct Mode Operation(DMO). It specifies the basic air interface, the inter-working between Direct Mode (DM) groups via repeaters, and inter-working with the TETRA Voice plus Data (V+D) system via gateways. It also specifies the security aspects in TETRA DMO, and the intrinsic services that are supported in addition to the basic bearer and teleservices. The present document applies to the TETRA DMO Gateway (DM-GATE) air interface and contains the specifications of the physical, Data Link Layer (DLL) and the network layer according to the ISO model. The specifications contained herein apply to a gateway, both as a standalone unit (DM-GATE) and also to a Direct Mode Repeater/Gateway (DM-REP/GATE) combined implementation. In the case of a combined implementation the repeater part of the gateway may be either a type 1A repeater, operating on a single RF carrier, or a type 1B repeater, operating on a pair of duplex-spaced RF carriers. They also cover the operation of a Direct Mode Mobile Station (DM-MS) with the gateway. NOTE: The specifications for a Direct Mode type 1 repeater (either type 1A DM-REP or type 1B DM-REP) are provided in EN 300 396-4 [4]. The protocol for a DM-MS operating through a gateway is specified in clauses 5 through 8, 14 and 15. Much of this protocol is defined in the form of a "delta document" relative to the specification provided in EN 300 396-2 [2] and EN 300 396-3 [3] for direct MS-MS operation. These clauses define where the protocol in EN 300 396-2 [2] and EN 300 396-3 [3] applies without change, or where it applies with the specified amendments, replacements or additions. Where no reference to EN 300 396-2 [2] or EN 300 396-3 [3] exists, the clause should be regarded as independent. The protocol for the gateway is specified in clauses 9 to 13, 16 and 17. The normative annex mainly specifies the parameter values used in the protocol.

• Status: Published
• Publication Date: 30-Jun-2006
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: MOC - Mobile Communications
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jul-2006
• Due Date: 01-Jul-2006
• Completion Date: 01-Jul-2006
• Ref Project: ETSI EN 300 396-5 V1.2.1 (2006-05) - Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 5: Gateway air interface

SIST EN 300 396-5 V1.2.1:2006 is the Slovenian adoption of ETSI EN 300 396-5 for Terrestrial Trunked Radio (TETRA) Direct Mode Operation (DMO). It specifies the gateway air interface for DMO, including how a Direct Mode Mobile Station (DM-MS) works through a DM-GATE or a combined DM-REP/GATE, and it defines the physical, Data Link Layer (DLL) and network-layer behavior needed for that interworking.

What does SIST EN 300 396-5 V1.2.1:2006 specify?

SIST EN 300 396-5 V1.2.1:2006 specifies the TETRA DMO gateway air interface and the protocol behavior for a DM-MS operating through a gateway. It focuses on the DMO side of gateway interworking, and it also covers how the gateway connects DMO to TETRA Voice plus Data (V+D) operation.

The document is organized into clauses for the scope, references, definitions and abbreviations, protocol overview, DM-MS services and protocol, gateway call control and mobility management, U-plane conversion, layer 2 protocol and service descriptions, PDU descriptions, radio aspects for DM-MS and gateway, and a gateway TMO protocol stack. Annex A provides timers and constants, and Annex B provides the TMO elements needed for DM gateway operation.

Annex	What it covers
Annex A (normative)	DM timers and constants for the DM-MS and the gateway, including layer 3 and layer 2 values and maximum frame transmissions
Annex B (normative)	TMO elements required for DM gateway operation, including DM-MS address handling and D-MM STATUS / U-MM STATUS PDUs

The scope also makes the document's role clear: much of the DM-MS protocol is written as a delta relative to EN 300 396-2 and EN 300 396-3, while the gateway-specific protocol is defined here in its own clauses.

What are the key requirements of SIST EN 300 396-5 V1.2.1:2006?

SIST EN 300 396-5 V1.2.1:2006 is the detailed rule set for gateway-based DMO communication. The most important point for implementers is that the document separates DM-MS behavior, gateway behavior, and the mapping between DMO and TMO, so both ends of the link can be built and tested against the same call, data, and mobility procedures.

Channel states and call behavior

Clause 4 describes the DM channel as free, occupied, reserved, or in a registration phase. In practice, this means equipment must make transmit and receive decisions based on the current channel state, not just on whether the channel looks idle.

Clause 4.3 lays out the main call scenarios through a gateway, including group calls, individual calls, changeover, pre-emption, and Short Data Service. For engineers, this is the part that shows how a call moves from set-up to active use and how the gateway handles interruptions or priority changes.

DM-MS service and layer 3 behavior

Clause 5 defines the DM-MS service access points and the service primitives used by the user application, including DMCC-SAP and DMMM-SAP. The DMMM-REGISTRATION primitive uses a serviced identity, so the DM-MS must present the correct identity information when it registers through a gateway.

Clause 6 gives the DM-MS layer 3 protocol for operation with a gateway. It covers outgoing and incoming call set-up, occupation, reservation, Short Data Service, mobility management, and the use of DMA-UNITDATA for layer 3 messages. In practice, this is the logic that determines when a DM-MS sets up a call, accepts a call, reports registration status, or reacts to pre-emption and release events.

DM-MS layer 2 and MAC handling

Clauses 7 and 8 define the DM-MS layer 2 service description and protocol for gateway operation. They cover logical channels, PDU mapping, scrambling, error detection, DM-MAC states, channel surveillance, fragmentation, fill bits, dual watch operation, air interface encryption, and channel A or B operation.

This matters because gateway interworking depends on precise timing and message handling at layer 2. The DM-MS must monitor the channel, maintain synchronization, and send or receive the right PDUs in the right channel state, especially during calls, reservation periods, registration, and pre-emption.

Gateway call control and mobility management

Clause 9 describes gateway layer 3 call control. It includes states for call set-up, active calls, disconnect, pre-emption, and Short Data Service, and it covers incoming and outgoing calls between DMO and TMO. It also maps TMO communication type, call priority, short data type identifiers, and TX demand priority to their DMO equivalents.

Clause 10 defines gateway mobility management on both the TMO and DM sides. It covers gateway registration to SwMI, solicited and unsolicited registration requests from DM, registration cancellation, and U-MM STATUS / D-MM STATUS procedures. In practice, this is how the gateway keeps its registration and access state aligned with both domains.

U-plane conversion and implementation data

Clause 11 describes the U-plane converter in the gateway. It transfers U-plane traffic and U-plane signalling between the DM and TMO sides and specifies what happens when a call transaction starts or stops in either direction.

Clauses 12 and 13 describe the gateway DM layer 2 services and protocols, including DM-REP/GATE retransmission behavior, channel surveillance, registration-phase operation, traffic mode behavior, and message transfer procedures. Clause 14 then gives the PDU descriptions and information element coding, while Clauses 15 and 16 define the radio aspects of the DM-MS and the gateway. Annex A and Annex B provide the timer, constant, and TMO-side element values that implementers need for conformance and interoperability work.

What terms does SIST EN 300 396-5 V1.2.1:2006 define?

• Direct Mode Operation (DMO) - TETRA operation in which communication is handled in direct mode, including gateway interworking.
• Direct Mode Mobile Station (DM-MS) - a mobile station operating on the DMO side of the system and using the procedures defined for gateway operation.
• Trunked Mode Mobile Station (TM-MS) - the physical grouping of mobile equipment used to obtain TETRA TM services.
• DM-GATE - a standalone gateway unit covered by the document for DMO air-interface operation.
• DM-REP/GATE - a combined Direct Mode-REPeater and gateway implementation; the scope treats type 1A and type 1B repeater variants within this combined case.
• Short Data Service (SDS) - the short data transfer service supported through gateway procedures, including acknowledged and unacknowledged handling.
• Gateway presence signal - the signal used to indicate gateway presence and, in the protocol overview, to support a registration phase on the DM channel.

Who uses SIST EN 300 396-5 V1.2.1:2006?

SIST EN 300 396-5 V1.2.1:2006 is used by teams that design, integrate, test, or buy TETRA DMO gateway equipment. Typical users include:

• radio equipment manufacturers developing DM-GATE, DM-REP/GATE, and DM-MS implementations
• system integrators connecting DMO operation to TETRA V+D environments
• test laboratories checking call setup, mobility management, SDS, pre-emption, and radio behavior
• quality and compliance teams verifying that layer 2, layer 3, and radio-side behavior match the gateway procedures
• purchasers and technical evaluators comparing gateway-capable TETRA equipment for interoperability

Which standards are used with SIST EN 300 396-5 V1.2.1:2006?

• ETSI EN 300 396-2 - provides the direct MS-MS operation baseline that this part uses as a delta reference for many DM-MS procedures.
• ETSI EN 300 396-3 - provides the direct mode MS-MS protocol baseline and service descriptions that are reused or amended for gateway operation.
• ETSI EN 300 396-4 - provides the specifications for a Direct Mode type 1 repeater, which the scope points to for repeater-specific behavior.
• ETSI EN 300 396-6 - provides the security part of TETRA DMO.
• ETS 300 396-1 - provides a brief overview of the general architecture and the layers in the EN 300 396 family.

What does the SIST EN 300 396-5 V1.2.1:2006 document contain?

SIST EN 300 396-5 V1.2.1:2006 contains protocol descriptions, state machines, and message procedures for gateway-based DMO. It includes call setup examples, call maintenance behavior, pre-emption handling, Short Data Service procedures, and mobility management flows.

The document also contains layer 2 and layer 3 service primitives, PDU definitions, and message coding rules. These are the parts that engineers use when building or testing interoperability between DM-MS equipment and a gateway.

For the radio side, the document includes transmission, reception, synchronization, coding, multiplexing, and link-control requirements for both the DM-MS and the gateway. Annex A and Annex B add the timer, constant, and TMO-element tables that support implementation and conformance checking.

SLOVENSKI STANDARD
01-julij-2006
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: EN 300 396-5 Version 1.2.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 Standard (Telecommunications series)

Terrestrial Trunked Radio (TETRA);
Technical requirements for Direct Mode Operation (DMO);
Part 5: Gateway air interface
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.: [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 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
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
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
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
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.83
8.4.5.1.8 Transmitting DM-TX CEASED.83
8.4.5.1.9 Transmitting DM-TX REQUEST.83
8.4.5.1.10 Transmitting response to DM-TX REQUEST.83
8.4.5.1.11 Transmitting DM-PREEMPT.83
8.4.5.1.12 Transmitting response to DM-PREEMPT.84
8.4.5.1.13 Transmitting DM-SDS UDATA and DM-SDS DATA.84
8.4.5.1.14 Transmitting response to DM-SDS DATA .84
8.4.5.1.15 Transmitting DM-INFO.84
8.4.5.1.16 Transmitting DM-GSETUP.84
8.4.5.1.17 Transmitting DM-GTX REQUEST.85
8.4.5.1.18 Transmitting DM-GPREEMPT.86
8.4.5.1.19 Transmitting DM-GREGISTER REQUEST.86
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 .87
8.4.6.1 Transmitting DM-RESERVED.87
8.4.6.2 Transmitting DM-SDS OCCUPIED .87
8.4.6.3 Transmitting DM-TIMING REQUEST .87
8.4.6.4 Transmitting DM-TIMING ACK.87
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 .89
8.4.7.9 Requests bitmap.89
8.4.7.10 Dual watch operation.89
8.4.7.11 Air interface encryption .89
8.4.7.12 Channel A or B operation .89
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.90
8.4.7.17 Modification of slot/frame numbering by gateway.91
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.92
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.94
8.5.2.2 Reception of message.94
8.5.2.3 Usage of MNI.95
8.5.3 Use of air interface encryption.95
8.5.4 Fragmentation and reconstruction.95
8.5.4.1 Fragmentation by a DM-MS .95
8.5.4.2 Reconstruction by a DM-MS .96
8.5.5 Fill bit addition and deletion.97
ETSI
7 ETSI EN 300 396-5 V1.2.1 (2006-05)
8.5.6 Transmission and reception of messages by layer 2 unacknowledged service .98
8.5.6.1 Transmission of message.99
8.5.6.2 Reception of message.99
8.5.7 Random access protocol during occupation and reservation periods.101
8.5.7.1 Introduction.101
8.5.7.2 Procedures for master DM-MS .102
8.5.7.2.1 Indicating frames available for requests .102
8.5.7.2.2 Monitoring frames available for requests .102
8.5.7.2.3 Response to pre-emption request.103
8.5.7.2.4 Response to timing change request.103
8.5.7.2.5 Response to DM-GRELEASE message .103
8.5.7.3 Procedures for requesting DM-MS .103
8.5.8 Procedures for sending messages during registration phase .105
8.5.8.1 Procedures for registering DM-MS during registration phase .105
8.5.8.1.1 Preparing for registration access.105
8.5.8.1.2 First transmission of solicited registration request .105
8.5.8.1.3 Valid access slots.105
8.5.8.1.4 Waiting for response.105
8.5.8.1.5 Subsequent transmission of request.106
8.5.8.1.6 Abandoning registration access attempt .106
8.5.8.2 Procedures for pre-empting DM-MS during registration phase.106
8.5.8.2.1 Preparing for random access.106
8.5.8.2.2 First transmission of pre-emption request .106
8.5.8.2.3 Valid slots for pre-emption.106
8.5.8.2.4 Waiting for response.106
8.5.8.2.5 Subsequent transmission of request.107
8.5.8.2.6 Abandoning random access attempt .107
8.6 MAC procedures in traffic mode.108
8.6.1 Introduction.108
8.6.2 Criteria for transmission and reception of traffic.108
8.6.3 Change of U-plane mode .108
8.6.3.1 Call set-up by DM-MS.108
8.6.3.2 Incoming call set-up.108
8.6.3.2.1 Incoming call set-up without presence check .108
8.6.3.2.2 Incoming call set-up with presence check .109
8.6.3.3 Late entry.109
8.6.3.4 End of traffic transmission .109
8.6.3.4.1 Master DM-MS.109
8.6.3.4.2 Slave DM-MS.109
8.6.4 Exchange of information at the DMD-SAP.109
8.6.5 Stealing from circuit mode capacity .109
9 Gateway layer 3 call control procedures .109
9.1 Introduction.109
9.2 Gateway call control states.110
9.2.1 Gateway TMO call control states .
...