SIST EN 300 396-3 V1.3.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 Mobile Station - Mobile Station (MS-MS) air interface and contains the specifications of the Data Link Layer (DLL) and the network layer according to the ISO model. It establishes the services, messages and protocols used for voice and circuit mode data calls and short data transfer, starting with the upper layers:; it defines and specifies the protocol used by the layer 3 entity to communicate across the air interface;; it defines and specifies the services and protocol used in the DLL.; The normative annexes mainly specify the parameter values used in the protocol.

• Status: Published
• Publication Date: 31-Oct-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-Nov-2006
• Due Date: 01-Nov-2006
• Completion Date: 01-Nov-2006
• Ref Project: ETSI EN 300 396-3 V1.3.1 (2006-08) - Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 3: Mobile Station to Mobile Station (MS-MS) Air Interface (AI) protocol

SIST EN 300 396-3 V1.3.1:2006 is the Slovenian adoption of ETSI EN 300 396-3 V1.3.1, a TETRA Direct Mode Operation (DMO) standard. It specifies the Mobile Station to Mobile Station (MS-MS) air interface protocol, including the Data Link Layer (DLL) and layer 3 procedures for voice, circuit mode data, and short data. It is aimed at people implementing, testing, or buying TETRA direct-mode mobile stations.

What does SIST EN 300 396-3 V1.3.1:2006 specify?

SIST EN 300 396-3 V1.3.1:2006 specifies the MS-MS part of TETRA DMO. The scope places this part within the EN 300 396 series, which covers DMO, repeater inter-working, gateway inter-working with TETRA Voice plus Data (V+D), security aspects, and intrinsic services.

This part focuses on the protocol between the mobile stations themselves. It describes the services, messages, and procedures used across the air interface, starting with layer 3 and the DLL, and its annexes mainly give the parameter values used by the protocol.

The document is organized into clauses 1 to 9 and annexes A to F.

Annex	What it covers
Annex A	Layer 3 timers and constants, Layer 2 timers and constants, and the maximum number of frame transmissions by DM-MAC
Annex B	Mathematical definition of FCS
Annex C	Limitations of Dual Watch operation
Annex D	Use of threshold in channel surveillance procedures
Annex E	SDS-TL use in DMO
Annex F	Change requests

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

SIST EN 300 396-3 V1.3.1:2006 defines how a DM-MS behaves when it sets up, maintains, changes over, or releases a direct-mode call, and how it sends and receives short data. The most important practical point is that the standard ties user-visible call behavior to specific protocol states, PDUs, timers, and channel conditions.

Call setup, occupation, reservation, and pre-emption

Clause 4 describes the DM channel and the basic call sequence. In normal mode, one DM channel exists on a DM RF carrier; in frequency efficient mode, channel A and channel B may exist on the same carrier. The master DM-MS sends signalling in Direct Mode Synchronization Bursts (DSBs) and traffic in Direct Mode Normal Bursts (DNBs), so implementers must keep timing and burst type aligned with the current channel state.

Clause 6 defines circuit mode call procedures. A call may be individual or group, and individual calls support setup with or without presence check. This matters because the terminal must follow different call setup and acceptance behavior depending on whether it is calling one station or a group, and whether presence checking is used.

Clause 6 also defines pre-emption. Pre-emption transfers the master role to the requesting DM-MS, either to take over an ongoing call or to start a new call. In practice, this is the mechanism that lets a higher-priority user claim the channel, so the terminal must evaluate priority and channel state before acting.

Short Data Service

Clause 6.3 defines the Short Data Service (SDS). SIST EN 300 396-3 V1.3.1:2006 supports user-defined short messages and predefined 16-bit status messages. It distinguishes unacknowledged service, which can be used to a group and may be used to an individual DM-MS, from acknowledged service, which may be used to an individual DM-MS.

This matters because the sender must choose between reach and feedback. For unacknowledged SDS, the calling DMCC can request repeated transmission of the complete message; for acknowledged SDS, the calling DMCC must handle retransmission if no response is received. Clause 6.3.5 also defines SDS-TL use in DMO, including store-and-forward behavior.

Layer 3 services and primitives

Clause 5 describes the layer 3 services exposed at the DMCC-SAP. The DMCC supports individual and group circuit mode call transmission and reception in simplex mode, call setup with and without presence check, clear and encrypted circuit mode operation, pre-emption, and both user-defined and predefined short data.

The clause is written in terms of primitives such as DMCC-SETUP, DMCC-RELEASE, DMCC-SDS DATA, DMCC-SDS UNITDATA, DMCC-TPNI, and DMCC-TX CEASED. For implementers, these primitives are the application-facing interface that turns radio events into software actions and status reports.

Layer 2 structure and access points

Clause 7 defines the DLL architecture and its service access points. The DLL is split into upper MAC and lower MAC. The upper MAC handles higher protocol functions, while the lower MAC performs channel coding and interleaving. The clause also defines the DMA-SAP, DMC-SAP, DMD-SAP, and related parameters.

This matters because the MS software must separate control-plane signaling from user-plane traffic. Clause 7.4 lists parameters such as destination address, priority, reservation time, new call pre-emption, and stolen indication, which are the protocol values that drive channel decisions and traffic handling.

Channel mapping, modes of operation, and dual watch

Clause 8 maps logical channels to bursts. SCH/S and SCH/H use parts of the DSB, SCH/F uses the DNB, STCH uses DNB plus slot flag, TCH uses DNB, and LCH uses DLB. The same clause defines the DM-MS modes of operation, including signalling mode and traffic mode, so a terminal has to switch burst handling at the right times.

Clause 8.3 describes DM-MS capabilities, including DM only, dual mode capable operation, and Dual Watch. An Idle Dual Watch Mobile Station (I-DW-MS) must be able to switch between the selected DM channel frequency and the TMO channel frequency within 0,5 of a timeslot duration. In practice, that requirement affects RF timing, battery use, and whether a terminal can keep listening to TMO while supporting DMO.

State control, surveillance, and timing

Clause 8.4 defines DM-MAC states such as free, occupied, reserved, and unknown, and describes channel surveillance and state changes. The master DM-MS sets timing reference, frame numbering, and channel behavior, while a slave DM-MS follows the channel state and monitoring rules.

This is important because a DM-MS cannot simply transmit whenever it wants. It must watch for DSBs, determine whether the channel is free or busy, and apply the state-transition rules before call setup, late entry, or call continuation.

Signalling PDUs and coding

Clause 9 describes the PDUs used on the air interface and the coding of the information elements in them. It covers layer 2 PDUs in DSB and DNB, layer 2 messages generated by layer 2, and layer 3 PDUs such as DM-SETUP, DM-CONNECT, DM-OCCUPIED, DM-RELEASE, DM-PREEMPT, DM-REJECT, DM-SDS UDATA, DM-SDS DATA, and DM-SDS ACK.

For implementers, this clause is the bit-level reference for interop. It shows which fields exist, how they are encoded, and how protocol state is reflected in the transmitted message.

What terms does SIST EN 300 396-3 V1.3.1:2006 define?

• Direct Mode Operation (DMO): TETRA operation in which mobile stations communicate directly without an intervening base station, and this part specifies the MS-MS air interface for that mode.
• call: A complete sequence of related call transactions between DM-MSs; it may be an individual call between two stations or a group call involving two or more stations.
• DM channel: A grouping of timeslots in the DM multiplex structure on one DM RF carrier; in frequency efficient mode, channels A and B share the carrier.
• Direct Mode Call Control (DMCC): The layer 3 entity that controls call setup, release, pre-emption, and short data procedures in direct mode.
• pre-emption: The transfer of the master role to the requesting DM-MS, used when a higher-priority station needs the channel.
• presence signal: A message sent by a DM-REP or DM-GATEway to indicate its presence on an RF carrier.
• DUal Mode switchable Mobile Station (DU-MS): A mobile station that can operate in TETRA DMO or TETRA TMO, one mode at a time.

Who uses SIST EN 300 396-3 V1.3.1:2006?

SIST EN 300 396-3 V1.3.1:2006 is used by radio engineers who design TETRA mobile stations and by software developers who implement DMCC, MAC, and PDU handling. Test laboratories use it to verify call setup, channel access, pre-emption, short data exchange, encryption-related behavior, and timing.

It is also relevant to quality managers and buyers who need to check whether a product supports DMO MS-MS behavior, including simplex circuit mode calls, SDS, and Dual Watch-related functions. Integrators and system planners use it when they need direct-mode operation with repeaters or gateways referenced by the wider EN 300 396 series.

Which standards are used with SIST EN 300 396-3 V1.3.1:2006?

The document cites other EN 300 396 parts and related TETRA standards as inputs to specific procedures:

• EN 300 396-1 - gives the general architecture of the DMO protocol and the overall layer structure.
• EN 300 396-2 - provides the DSB structure and timing referenced for call setup and channel signaling.
• EN 300 396-4 and EN 300 396-7 - support communication via DM-REP.
• EN 300 396-5 - supports communication via DM-GATE and DM-REP/GATE.
• EN 300 396-6 - is used for security criteria when assessing pre-emption.
• EN 300 396-10 - is referenced for DPRES-SYNC.
• EN 300 392-2 - provides status number definitions and related protocol details.

What does the SIST EN 300 396-3 V1.3.1:2006 document contain?

The document contains service definitions, protocol state descriptions, PDU formats, and bit-level coding rules for TETRA DMO MS-MS operation. It uses primitive tables to describe the parameters carried between layer 3, the DLL, and the user application.

It also includes call-flow figures, state diagrams for circuit mode calls and SDS, MAC procedures for random access and traffic mode, and logical-channel mappings to DSB, DNB, STCH, TCH, and LCH. Annex B gives the mathematical definition of the FCS, while Annex E shows how SDS-TL is used in DMO, including store-and-forward behavior.

For implementation and testing, the most useful parts are the parameter tables, the message and PDU descriptions, and the procedures that explain when a DM-MS shall transmit, listen, retry, or change state.

SLOVENSKI STANDARD
01-november-2006
3UL]HPQLVQRSRYQLUDGLR7(75$±7HKQLþQH]DKWHYH]DQHSRVUHGQLQDþLQ]YH]H
'02±GHO3URWRNROUDGLMVNHJDYPHVQLND$,RGPRELOQHSRVWDMHGRPRELOQH
SRVWDMH0606
Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation
(DMO); Part 3: Mobile Station to Mobile Station (MS-MS) Air Interface (AI) protocol
Ta slovenski standard je istoveten z: EN 300 396-3 Version 1.3.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 3: Mobile Station to Mobile Station (MS-MS)
Air Interface (AI) protocol
2 ETSI EN 300 396-3 V1.3.1 (2006-08)

Reference
REN/TETRA-08162
Keywords
air interface, 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-3 V1.3.1 (2006-08)
Contents
Intellectual Property Rights.11
Foreword.11
1 Scope.12
2 References.12
3 Definitions and abbreviations.13
3.1 Definitions.13
3.2 Abbreviations.15
4 Overview of protocol.17
4.1 General.17
4.2 The DM channel.17
4.3 DM call procedures .18
4.3.1 Constraints on the frame structure .19
4.3.2 Setting up a call .19
4.3.2.1 Call set-up without presence check.19
4.3.2.1.1 Basic procedure.19
4.3.2.1.2 Procedure in frequency efficient mode.20
4.3.2.2 Call set-up with presence check .21
4.3.3 Changeover in a call .21
4.3.4 Pre-emption of a DM call .22
4.3.5 Terminating a call .23
4.3.6 DM short data call .23
4.3.6.1 Unacknowledged short data message.23
4.3.6.2 Acknowledged short data message .24
4.4 DM protocol layering .24
5 Layer 3 service description.25
5.1 Introduction.25
5.2 Services offered.25
5.3 Primitive description.26
5.3.1 DMCC-COMPLETE primitive.26
5.3.2 DMCC-RELEASE primitive.27
5.3.3 DMCC-REPORT primitive.27
5.3.4 DMCC-SDS DATA primitive .27
5.3.5 DMCC-SDS REPORT primitive.28
5.3.6 DMCC-SDS UNITDATA primitive.28
5.3.7 DMCC-SETUP primitive.29
5.3.8 DMCC-TPNI primitive.30
5.3.9 DMCC-TX CEASED primitive.30
5.4 Parameter description.30
5.5 States for DMCC-SAP.35
6 Layer 3 protocol .36
6.1 Introduction.36
6.1.1 DMCC protocol states .36
6.1.1.1 IDLE.36
6.1.1.2 CALL SETUP NORMAL ORIGINATING.36
6.1.1.3 CALL SETUP NORMAL TERMINATING .36
6.1.1.4 CALL SETUP PRES_CHECK ORIGINATING.36
6.1.1.5 CALL SETUP PRES_CHECK TERMINATING.36
6.1.1.6 PRE-EMPTION.36
6.1.1.7 CALL ACTIVE TX OCCUPATION.36
6.1.1.8 CALL ACTIVE TX RESERVATION.37
6.1.1.9 CALL ACTIVE RX OCCUPATION.37
6.1.1.10 CALL ACTIVE RX RESERVATION.37
6.1.1.11 WAIT RSP OCCUPATION .37
ETSI
4 ETSI EN 300 396-3 V1.3.1 (2006-08)
6.1.1.12 WAIT RSP RESERVATION.37
6.1.1.13 ACK'D SHORT DATA INITIATED.37
6.1.1.14 UNACK'D SHORT DATA INITIATED.37
6.2 Circuit mode calls.37
6.2.1 Procedures for call set-up without presence check .38
6.2.1.1 Outgoing call.38
6.2.1.2 Incoming call.40
6.2.1.3 Temporary group address.41
6.2.2 Procedures for call set-up with presence check .41
6.2.2.1 Outgoing call.41
6.2.2.2 Incoming call.43
6.2.3 Usage of DM-OCCUPIED PDU .44
6.2.3.1 Sending of DM-OCCUPIED PDU by master DM-MS.44
6.2.3.2 Late entry by slave DM-MS.44
6.2.4 Procedures during occupation.44
6.2.4.1 Master DM-MS.44
6.2.4.2 Slave DM-MS.45
6.2.4.3 Transmitting Party Number Identification (TPNI).47
6.2.5 Procedures during reservation.47
6.2.5.1 Master DM-MS.47
6.2.5.2 Slave DM-MS.49
6.2.5.3 Pre-emption of short data sent as a transaction within a circuit mode call.51
6.2.6 Procedures to set up a new call by pre-emption.51
6.3 Short Data Service (SDS) procedures .52
6.3.1 Sending short data.53
6.3.1.1 Sending short data on a free channel.53
6.3.1.1.1 Sending unacknowledged short data on a free channel .53
6.3.1.1.2 Sending acknowledged short data on a free channel .55
6.3.1.2 Sending short data by pre-emption.57
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.59
6.3.1.4.1 Pre-emption to send short data as a transaction within a circuit mode call .59
6.3.1.4.2 Changeover to send short data as a transaction within a circuit mode call.60
6.3.1.4.3 Sending the short data as master of the circuit mode call.60
6.3.2 Receiving short data.60
6.3.2.1 Receiving unacknowledged short data.60
6.3.2.2 Receiving acknowledged short data.61
6.3.3 Additional addressing.61
6.3.4 Extended error protection .61
6.3.5 SDS-TL service in DMO .62
6.3.5.1 Service primitives at the DMTL-SDS-SAP .62
6.3.5.2 DMTL-SDS primitives' parameters .65
6.3.5.3 DMTL-SDS PDUs.67
6.3.5.4 DMTL-SDS procedures.67
6.4 Usage of DMA-UNITDATA primitive.70
7 Layer 2 service description.71
7.1 Introduction.71
7.2 Layer 2 architecture.72
7.2.1 Lower layer management in layer 2.73
7.3 Service descriptions.73
7.3.1 Services at the DMA-SAP .73
7.3.1.1 Services provided to layer 3.73
7.3.1.2 Service primitives at the DMA-SAP .74
7.3.1.2.1 DMA-REPORT primitive.74
7.3.1.2.2 DMA-UNITDATA primitive.74
7.3.2 Services at the DMC-SAP .75
7.3.2.1 Services provided to layer 3.75
7.3.2.2 Service primitives at the DMC-SAP .75
7.3.2.2.1 DMC-CONFIGURE primitive.76
7.3.2.2.2 DMC-REPORT primitive.76
7.3.3 Services at the DMD-SAP .76
ETSI
5 ETSI EN 300 396-3 V1.3.1 (2006-08)
7.3.3.1 Services provided to the U-plane application.76
7.3.3.2 Service primitives at the DMD-SAP .76
7.3.3.2.1 DMD-REPORT primitive.77
7.3.3.2.2 DMD-UNITDATA primitive.77
7.4 Parameter listing.77
7.4.1 Air interface encryption information .77
7.4.2 Air interface encryption state.77
7.4.2A Called party in ongoing call.78
7.4.3 Call release.78
7.4.4 Call set-up after pre-emption or changeover.78
7.4.5 Changeover request held during occupation.78
7.4.5A Channel selection information .78
7.4.6 Circuit mode information.78
7.4.7 Circuit mode type.78
7.4.8 Communication type.78
7.4.9 Destination address.78
7.4.10 Destination address type .79
7.4.10A DM channel.79
7.4.11 DM-SDU.79
7.4.12 DM-SDU length.79
7.4.12A Dual watch information.79
7.4.13 FCS flag.79
7.4.14 Half slot condition .79
7.4.15 Half slot content.79
7.4.16 Half slot importance.79
7.4.17 Half slot position.79
7.4.18 Half slot synchronization .80
7.4.19 Handle to the request .80
7.4.20 Immediate retransmission.80
7.4.21 Incomplete DM-SDS DATA/ACK received .80
7.4.21A Lower layer quality information .80
7.4.21B Master of ongoing call .80
7.4.22 Message type.80
7.4.23 New call pre-emption.80
7.4.24 Number of repeats.81
7.4.25 Priority.81
7.4.26 Priority of ongoing call .81
7.4.27 Recent user changeover request.81
7.4.28 Recent user priority.81
7.4.29 Report.81
7.4.30 Reservation time.81
7.4.31 SDS transaction type.81
7.4.32 Source address.81
7.4.33 Source address type .81
7.4.34 Stealing priority.82
7.4.35 Stolen indication.82
7.4.36 Type of pre-emption .82
7.4.37 Valid addresses.82
8 Layer 2 protocol .82
8.1 Introduction.82
8.1.1 Functions of lower MAC .82
8.1.2 Functions of upper MAC .83
8.2 Interface between lower and upper MAC.83
8.2.1 Logical channels defined at the DMV-SAP.83
8.2.2 Service primitives at the DMV-SAP.84
8.2.3 PDU mapping of the logical channels at the DMV-SAP.85
8.2.4 Scrambling mechanism.86
8.2.5 PDU error detection.86
8.2.6 Modes of operation .87
8.2.6.1 DM-MS modes of operation .87
8.2.6.1.1 Idle mode.87
ETSI
6 ETSI EN 300 396-3 V1.3.1 (2006-08)
8.2.6.1.2 Signalling mode.87
8.2.6.1.3 Traffic mode.87
8.2.6.2 Operation in traffic mode .88
8.2.6.2.1 Traffic transmission.88
8.2.6.2.2 Stealing mechanism.89
8.2.6.3 Selection of the mode of operation .89
8.3 Basic capabilities of the Physical Layer (PL).90
8.3.1 DM-MS capabilities.90
8.3.1.1 DM only and dual mode capable MS operation.90
8.3.1.2 Dual watch capable MS operation .91
8.3.1.2.1 Full Dual Watch Mobile Station (F-DW-MS).91
8.3.1.2.2 Idle Dual Watch Mobile Station (I-DW-MS) .91
8.4 Usage of DM channel.91
8.4.1 Definition of DM channel.91
8.4.1.1 DM channel arrangement.91
8.4.1.2 DM channel A operation.91
8.4.1.3 DM channel B operation .92
8.4.2 DM-MAC states.93
8.4.2.1 DM-MAC state definitions .93
8.4.2.2 DM-MS channel surveillance procedures .94
8.4.2.2.1 Initial determination of DM channel state .94
8.4.2.2.2 Fast call set-up surveillance in idle mode.96
8.4.2.2.3 DM-MS channel surveillance at call set-up.99
8.4.2.3 Master DM-MS channel maintenance procedures during a call .101
8.4.2.4 Slave DM-MS channel maintenance procedures during a call.101
8.4.2.4.1 Slave MS channel maintenance during call transaction .102
8.4.2.4.2 Slave MS signal quality measurement during call transaction .102
8.4.2.4.3 Slave MS channel maintenance during reservation .102
8.4.2.5 Additional master MS procedures in frequency efficient mode.102
8.4.2.5.1 Channel A master MS procedures .103
8.4.2.5.2 Channel B master MS procedures .103
8.4.3 Criteria for changing DM-MAC state.103
8.4.3.1 Criteria for changing DM-MAC state for master DM-MS.103
8.4.3.2 Criteria for changing DM-MAC state for slave DM-MS.104
8.4.3.3 Criteria for changing DM-MAC state for idle DM-MS .105
8.4.4 DM-MS channel monitoring procedures .107
8.4.4.1 DM channel during call set-up with presence check.108
8.4.4.2 DM channel in occupation during a circuit mode call.108
8.4.4.3 DM channel in reservation during a circuit mode call .108
8.4.4.4 DM channel in occupation during an SDS call .108
8.4.4.5 DM channel usage during pre-emption signalling .109
8.4.4.6 DM channel usage during timing change request signalling.109
8.4.5 Transmission of layer 3 messages by DM-MAC.109
8.4.5.1 Transmission of C-plane messages by DM-MAC.109
8.4.5.1.1 Transmitting DM-SETUP.109
8.4.5.1.2 Transmitting DM-SETUP PRES.110
8.4.5.1.3 Transmitting DM-CONNECT.111
8.4.5.1.4 Transmitting DM-DISCONNECT.111
8.4.5.1.5 Transmitting DM-CONNECT ACK.111
8.4.5.1.6 Transmitting DM-RELEASE.111
8.4.5.1.7 Transmitting DM-OCCUPIED.112
8.4.5.1.8 Transmitting DM-TX CEASED.112
8.4.5.1.9 Transmitting DM-TX REQUEST.113
8.4.5.1.10 Transmitting response to DM-TX REQUEST.113
8.4.5.1.11 Transmitting DM-PREEMPT.114
8.4.5.1.12 Transmitting response to DM-PREEMPT.114
8.4.5.1.13 Transmitting DM-SDS UDATA and DM-SDS DATA.115
8.4.5.1.14 Transmitting response to DM-SDS DATA .116
8.4.5.1.15 Transmitting DM-INFO.116
8.4.5.2 Transmission of U-plane messages by DM-MAC .116
8.4.6 Transmission of layer 2 messages generated by DM-MAC .116
8.4.6.1 Transmitting DM-RESERVED.117
ETSI
7 ETSI EN 300 396-3 V1.3.1 (2006-08)
8.4.6.2 Transmitting DM-SDS OCCUPIED .117
8.4.6.3 Transmitting DM-TIMING REQUEST .118
8.4.6.4 Transmitting DM-TIMING ACK.118
8.4.7 General DM-MAC procedures .118
8.4.7.1 DM-MAC repeat transmissions .118
8.4.7.2 DM-MAC frame countdown procedure.118
8.4.7.3 Use of timers .119
8.4.7.4 Linearization.119
8.4.7.5 Fragmentation.119
8.4.7.6 Fill bit indication.119
8.4.7.7 Selection of pseudo address .119
8.4.7.8 Slot flag indication .120
8.4.7.9 Requests bitmap.120
8.4.7.10 DM aspects of dual watch operation .120
8.4.7.10.1 Full and idle dual watch operation.120
8.4.7.10.2 DM aspects of full dual watch operation.120
8.4.7.10.3 DM aspects of idle dual watch operation .124
8.4.7.11 Air interface encryption .126
8.4.7.12 Channel A or B operation .126
8.4.7.13 Sending short data as a transaction within a circuit mode call.126
8.4.7.14 SDS time remaining .127
8.4.7.15 Timing change procedure.127
8.4.7.16 Timing change at changeover or pre-emption.129
8.5 MAC procedures for transfer of signalling messages.129
8.5.1 Formation of MAC PDU .129
8.5.2 Addressing.130
8.5.2.1 Transmission of message.130
8.5.2.1.1 Addressing in synchronization burst .130
8.5.2.1.2 Addressing in normal burst.132
8.5.2.2 Reception of message.132
8.5.3 Use of air interface encryption.133
8.5.4 Fragmentation and reconstruction.134
8.5.4.1 Fragmentation.134
8.5.4.2 Reconstruction.135
8.5.5 Fill bit addition and deletion.136
8.5.5.1 Fill bit addition.136
8.
...