SIST EN 300 396-4 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. This part applies to the TETRA DMO Repeater (DM-REP) 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 DM-REP as a stand-alone unit supporting a single call on the air interface (type 1 DM-REP). They also cover the operation of a Direct Mode Mobile Station (DM-MS) with a type 1 DM-REP. NOTE 1: The specifications for a Direct Mode Repeater/Gateway (DM-REP/GATE) combined implementation are provided in EN 300 396-5 [5], together with the specifications for a Direct Mode Gateway (DM-GATE). NOTE 2: The specifications for a DM-REP as a stand-alone unit supporting two calls on the air interface (type 2 DM-REP) are provided in EN 300 396-7 [7]. The protocol for a DM-MS operating with a type 1 DM-REP is specified in clauses 5 through 8, 10 and 11. Much of this protocol is defined in the form of a "delta document" relative to the specifications 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 DM-REP is specified in clauses 9 and 12. 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-4 V1.3.1 (2006-05) - Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 4: Type 1 repeater air interface

SIST EN 300 396-4 V1.3.1:2006 is the SIST adoption of ETSI EN 300 396-4 for Terrestrial Trunked Radio (TETRA) Direct Mode Operation (DMO). It specifies the type 1 Direct Mode REPeater (DM-REP) air interface and the Direct Mode-Mobile Station (DM-MS) procedures used when mobiles work through that repeater. In practice, it defines the physical layer, Data Link Layer (DLL) and network-layer behavior needed for calls, short data and repeater retransmission.

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

SIST EN 300 396-4 V1.3.1:2006 specifies DMO operation through a type 1 DM-REP. The document applies to a DM-REP as a stand-alone unit supporting a single call on the air interface, and it also covers the operation of a DM-MS with a type 1 DM-REP.

The scope ties this part to the wider EN 300 396 series. The standard fits into a multi-part DMO framework that covers the basic air interface, repeater inter-working, gateway inter-working with the TETRA Voice plus Data (V+D) system, security, and additional services.

The document is organized into clauses for protocol overview, DM-MS service description, DM-MS protocol, DM-REP protocol, PDU descriptions, and radio aspects. Annex A gives timers and constants for DM-MS and DM-REP, Annex B covers SDS-Transport Layer (SDS-TL) use in DMO, and Annex C is a bibliography.

Annex	What it covers
Annex A	Timers and constants in DM-MS and DM-REP
Annex B	SDS-TL use in DMO
Annex C	Bibliography

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

Repeater model and channel structure

SIST EN 300 396-4 V1.3.1:2006 defines a type 1 DM-REP as a repeater that supports normal mode operation on the air interface. It distinguishes type 1A DM-REP, which uses one RF carrier, from type 1B DM-REP, which uses a duplex-spaced pair of RF carriers with separate uplink and downlink paths.

That distinction matters because equipment design and frequency planning depend on whether the same carrier is used in both directions or whether the repeater separates uplink and downlink. Clause 4 and clauses 9, 11 and 12 describe the operating model for both DM-MSs and the DM-REP.

The DM channel is treated as free, occupied, or reserved. Clause 4.2 explains that a DM-MS must make access and call decisions based on that state, so terminal logic has to detect the current channel condition before trying to set up or join a call.

Presence signal, repeater address and access

The DM-REP may transmit a presence signal to announce that it is switched on and available. Clause 4 says this signal can carry the repeater's 10-bit repeater address and may indicate which DM-MSs are permitted to use the repeater.

This matters in practice because a DM-MS needs the correct repeater address before making a call through the DM-REP. The set-up message includes that address, so planners and users need a way to provision or learn it in advance.

Frame timing, master and slave links

Clause 4.3.1 sets out the frame structure constraints for type 1 DM-REP operation. The master link and slave link are offset in time, and specific frames and slots are reserved for synchronization, occupation and reservation signaling.

That timing is central to implementation because a DM-MS must place signaling and traffic in the right slot at the right time. The same timing rules appear again in the layer 2 procedures, including frame countdown, random access, linearization and retransmission behavior.

Call setup, changeover and pre-emption

Clause 4.3 and clause 6 describe call setup with and without presence check, call changeover, pre-emption and call termination. The DM-REP protocol is a delta against EN 300 396-3, so many procedures reuse the direct MS-MS rules but add repeater-specific behavior.

In practice, this means a call can fail if the calling DM-MS does not see its set-up message repeated on the slave link, or if the link to the DM-REP is lost during occupation or reservation. Pre-emption transfers the master role to the requesting DM-MS, which is the mechanism used when a higher-priority user needs the channel.

Short Data Service and SDS-TL

Clause 4.3.6 and clause 6.3 cover Short Data Service (SDS) through a type 1 DM-REP. The document distinguishes unacknowledged and acknowledged short data, and it also covers short data sent as a transaction within a circuit mode call.

For implementers, the important point is that short data is not just carried once - the DM-REP may need to retransmit it, and the DM-MS may need to repeat transmission if the link establishment is not confirmed. Annex B adds the SDS-TL use in DMO, so data handling is defined beyond the basic SDS message exchange.

Layer 2, PDUs and parameter values

Clauses 8, 9 and 10 define the Data Link Layer behavior for both the DM-MS and the DM-REP. They cover logical channels, scrambling, error detection, random access, retransmission of signaling messages, and the PDUs used on the air interface.

Clause 10 is especially important for interoperability because it gives the information element coding used by the protocol. It also fixes values such as the System code used by compliant DM-MSs and DM-REPs, and it defines repeater-specific elements such as the repeater address, MNI, validity time, URT, repeater operating modes and the DN232 and DN233 frame counts used for retransmission.

Radio behavior and synchronization

Clauses 11 and 12 cover the radio aspects for the DM-MS and the type 1 DM-REP. They reference modulation and channel coding from EN 300 396-2, then add repeater-specific channel multiplexing, synchronization and transmitter or receiver behavior.

That matters because timing, frequency reference and power behavior have to be consistent across the mobile and the repeater. Clause 12 also states that a DM-REP transmits at its nominal power, and clause 11 makes adaptive DM-MS RF power control optional for operation through a type 1 DM-REP.

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

• call - A complete sequence of related call transactions between DM-MSs using the repeater protocol.
• DM-REP - A Direct Mode REPeater that extends coverage by relaying communication between two or more DM-MSs.
• type 1 DM-REP - A DM-REP that supports normal mode operation on the air interface, either as type 1A on one carrier or type 1B on a duplex-spaced pair.
• occupation - The time when a call transaction is in progress on a channel.
• pre-emption - The transfer of the master role to the requesting DM-MS.
• DMCC - The Direct Mode Call Control entity that handles layer 3 call and SDS procedures in the DM-MS.
• DSB - A Direct Mode Synchronization Burst used for synchronization and signaling on the DM air interface.
• SDS-TL - The SDS-Transport Layer used for SDS operation in DMO.

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

This standard is used by:

• TETRA terminal designers - to implement DM-MS behavior through a type 1 DM-REP.
• Repeater designers - to build type 1A or type 1B DM-REPs with the required air-interface, timing and retransmission behavior.
• System integrators and radio planners - to choose channel arrangements, repeater presence signaling and timing relationships.
• Test and certification teams - to verify protocol behavior, PDU coding, synchronization and radio performance.
• Quality managers and buyers - to check that equipment supports the required DMO repeater mode and the correct companion parts of EN 300 396.

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

SIST EN 300 396-4 V1.3.1:2006 is used with other parts of the EN 300 396 series:

• ETSI ETS 300 396-1 - gives the general network design for TETRA DMO.
• ETSI EN 300 396-2 - supplies the baseline radio, channel coding, multiplexing and link-control framework that this part adapts.
• ETSI EN 300 396-3 - gives the direct MS-MS procedures that this part reuses with repeater-specific changes.
• ETSI EN 300 396-5 - covers the combined DM-REP/GATE implementation and DM-GATE.
• ETSI EN 300 396-6 - covers security in TETRA DMO.
• ETSI EN 300 396-7 - covers the type 2 repeater air interface.
• ETSI EN 300 396-10 - covers Managed Direct Mode Operation (M-DMO).

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

The document contains protocol overviews, service descriptions, detailed layer 2 and layer 3 procedures, and radio-interface rules for operation through a type 1 DM-REP. Clause 4 gives the operating model and example call sequences, including setup, changeover, pre-emption and SDS cases.

Clauses 5 to 9 define the DM-MS and DM-REP service access points, protocol states, retransmission behavior and random access procedures. Clause 10 defines the PDUs and information element coding used on the air interface.

Clauses 11 and 12 cover modulation, frequency arrangement, synchronization, channel coding, channel multiplexing and link control. Annex A lists timers and constants, and Annex B defines how SDS-TL is used in DMO.

SLOVENSKI STANDARD
01-julij-2006
3UL]HPQLVQRSRYQLUDGLR7(75$±7HKQLþQH]DKWHYH]DQHSRVUHGQLQDþLQ
GHORYDQMD'02±GHO5DGLMVNLYPHVQLNWLSD]DSRQDYOMDOQLNHUHSHWLWRUMH
Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation
(DMO); Part 4: Type 1 repeater air interface
Ta slovenski standard je istoveten z: EN 300 396-4 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 4: Type 1 repeater air interface

2 ETSI EN 300 396-4 V1.3.1 (2006-05)

Reference
REN/TETRA-08079-4
Keywords
TETRA, DMO, protocol, radio, air interface
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-4 V1.3.1 (2006-05)
Contents
Intellectual Property Rights.10
Foreword.10
1 Scope.11
2 References.11
3 Definitions and abbreviations.12
3.1 Definitions.12
3.2 Abbreviations.15
4 Overview of protocol.16
4.1 General.16
4.2 The DM channel.18
4.3 DM call procedures for operation with a type 1 DM-REP .19
4.3.1 Constraints on the frame structure .20
4.3.2 Setting up a call .20
4.3.2.1 Call set-up without presence check.21
4.3.2.2 Call set-up with presence check .22
4.3.3 Changeover in a call .22
4.3.4 Pre-emption of a DM call .23
4.3.5 Terminating a call .24
4.3.6 DM short data call .24
4.3.6.1 Unacknowledged short data message.24
4.3.6.2 Acknowledged short data message .25
5 DM-MS layer 3 service description for operation with a type 1 DM-REP.26
5.1 Introduction.26
5.2 Services offered.26
5.3 Primitive description.26
5.4 Parameter description.26
5.5 States for DMCC-SAP.26
6 DM-MS layer 3 protocol for operation with a type 1 DM-REP.27
6.1 Introduction.27
6.1.1 DMCC protocol states .27
6.2 Circuit mode calls.27
6.2.1 Procedures for call set-up without presence check .27
6.2.1.1 Outgoing call.27
6.2.1.2 Incoming call.28
6.2.1.3 Temporary group address.28
6.2.2 Procedures for call set-up with presence check .28
6.2.2.1 Outgoing call.28
6.2.2.2 Incoming call.28
6.2.3 Usage of DM-OCCUPIED PDU .28
6.2.3.1 Sending of DM-OCCUPIED PDU by master DM-MS.28
6.2.3.2 Late entry by slave DM-MS.28
6.2.4 Procedures during occupation.29
6.2.4.1 Master DM-MS.29
6.2.4.2 Slave DM-MS.29
6.2.4.3 Transmitting Party Number Identification (TPNI).29
6.2.5 Procedures during reservation.29
6.2.5.1 Master DM-MS.29
6.2.5.2 Slave DM-MS.30
6.2.5.3 Pre-emption of short data sent as a transaction within a circuit mode call.30
6.2.6 Procedures to set up a new call by pre-emption.30
6.3 Short Data Service (SDS) procedures .30
6.3.1 Sending short data.30
6.3.1.1 Sending short data on a free channel.30
ETSI
4 ETSI EN 300 396-4 V1.3.1 (2006-05)
6.3.1.1.1 Sending unacknowledged short data on a free channel .30
6.3.1.1.2 Sending acknowledged short data on a free channel .31
6.3.1.2 Sending short data by pre-emption.31
6.3.1.3 Sending short data during circuit mode transmission.31
6.3.1.4 Sending short data as a transaction within a circuit mode call.31
6.3.2 Receiving short data.31
6.3.2.1 Receiving unacknowledged short data.31
6.3.2.2 Receiving acknowledged short data.31
6.3.3 Additional addressing.32
6.3.4 Extended error protection .32
6.3.5 SDS-TL service in DMO .32
6.4 Usage of DMA-UNITDATA primitive.32
6.5 General procedures.32
6.5.1 Usage restriction type and validity time .32
7 DM-MS layer 2 service description for operation with a type 1 DM-REP.33
7.1 Introduction.33
7.2 Layer 2 architecture.33
7.3 Service descriptions.33
7.3.1 Services at the DMA-SAP .33
7.3.1.1 Services provided to layer 3.33
7.3.1.2 Service primitives at the DMA-SAP .34
7.3.2 Services at the DMC-SAP .34
7.3.2.1 Services provided to layer 3.34
7.3.2.2 Service primitives at the DMC-SAP .34
7.3.2.2.1 DMC-CONFIGURE primitive.34
7.3.2.2.2 DMC-REPORT primitive.34
7.3.3 Services at the DMD-SAP .34
7.3.3.1 Services provided to the U-plane application.34
7.3.3.2 Service primitives at the DMD-SAP .34
7.4 Parameter listing.35
8 DM-MS layer 2 protocol for operation with a type 1 DM-REP.35
8.1 Introduction.35
8.1.1 Functions of lower MAC .35
8.1.2 Functions of upper MAC .35
8.2 Interface between lower and upper MAC.36
8.2.1 Logical channels defined at the DMV-SAP.36
8.2.2 Service primitives at the DMV-SAP.36
8.2.3 PDU mapping of the logical channels at the DMV-SAP.36
8.2.4 Scrambling mechanism.36
8.2.5 PDU error detection.37
8.2.6 Modes of operation .37
8.3 Basic capabilities of the physical layer.37
8.3.1 DM-MS capabilities.37
8.3.1.1 DM only and dual mode capable MS operation.37
8.3.1.2 Dual watch capable MS operation .38
8.3.1.2.1 Full Dual Watch Mobile Station (F-DW-MS).38
8.3.1.2.2 Idle Dual Watch Mobile Station (I-DW-MS) .38
8.4 Usage of DM channel with type 1 DM-REP.38
8.4.1 Definition of DM channel.39
8.4.1.1 DM channel arrangement.39
8.4.1.2 DM channel operation.39
8.4.2 DM-MAC states.40
8.4.2.1 DM-MAC state definitions .40
8.4.2.2 DM-MS channel surveillance procedures .40
8.4.2.2.1 Initial determination of DM channel state .40
8.4.2.2.2 Fast call set-up surveillance in idle mode.41
8.4.2.2.3 DM-MS channel surveillance at call set-up.41
8.4.2.3 Master DM-MS channel maintenance procedures during a call .41
8.4.2.4 Slave DM-MS channel maintenance procedures during a call.42
8.4.2.4.1 Slave MS channel maintenance during call transaction .42
ETSI
5 ETSI EN 300 396-4 V1.3.1 (2006-05)
8.4.2.4.2 Slave MS signal quality measurement during call transaction .42
8.4.2.4.3 Slave MS channel maintenance during reservation .42
8.4.3 Criteria for changing DM-MAC state.42
8.4.3.1 Criteria for changing DM-MAC state for master DM-MS.42
8.4.3.2 Criteria for changing DM-MAC state for slave DM-MS.43
8.4.3.3 Criteria for changing DM-MAC state for idle DM-MS .43
8.4.4 DM-MS channel monitoring procedures .43
8.4.4.1 DM channel during initial call set-up and new call transaction by current master MS.43
8.4.4.2 DM channel during call set-up with presence check.43
8.4.4.3 DM channel in occupation during a circuit mode call.44
8.4.4.4 DM channel in reservation during a circuit mode call .44
8.4.4.5 DM channel in occupation during an SDS call .44
8.4.4.6 DM channel usage during pre-emption signalling .45
8.4.4.7 DM channel usage during timing change request signalling.45
8.4.5 Transmission of layer 3 messages by DM-MAC.45
8.4.5.1 Transmission of C-plane messages by DM-MAC.45
8.4.5.2 Transmission of U-plane messages by DM-MAC .46
8.4.6 Transmission of layer 2 messages generated by DM-MAC .46
8.4.7 General DM-MAC procedures .46
8.4.7.1 DM-MAC repeat transmissions .46
8.4.7.2 DM-MAC frame countdown procedure.46
8.4.7.3 Use of timers .46
8.4.7.4 Linearization.46
8.4.7.5 Fragmentation.47
8.4.7.6 Fill bit indication.47
8.4.7.7 Selection of pseudo address .47
8.4.7.8 Slot flag indication .47
8.4.7.9 Requests bitmap.47
8.4.7.10 DM aspects of dual watch operation .48
8.4.7.10.1 Full and idle dual watch operation.48
8.4.7.10.2 DM aspects of full dual watch operation.48
8.4.7.10.3 DM aspects of idle dual watch operation .49
8.4.7.11 Air interface encryption .49
8.4.7.12 Channel A or B operation .49
8.4.7.13 Sending short data as a transaction within a circuit mode call.49
8.4.7.14 SDS time remaining .49
8.4.7.15 Timing change procedure.49
8.4.7.16 Timing change at changeover or pre-emption.49
8.5 MAC procedures for transfer of signalling messages.50
8.5.1 Formation of MAC PDU .50
8.5.2 Addressing.50
8.5.2.1 Transmission of message.50
8.5.2.1.1 Addressing in synchronization burst .50
8.5.2.1.2 Addressing in normal burst.50
8.5.2.2 Reception of message.51
8.5.3 Use of air interface encryption.51
8.5.4 Fragmentation and reconstruction.52
8.5.4.1 Fragmentation.52
8.5.4.2 Reconstruction.53
8.5.5 Fill bit addition and deletion.53
8.5.6 Transmission and reception of messages by layer 2 .53
8.5.6.1 Transmission of message.54
8.5.6.2 Reception of message.55
8.5.7 Random access protocol .56
8.5.7.1 Introduction.56
8.5.7.2 Procedures for master DM-MS .56
8.5.7.2.1 Indicating frames available for requests .56
8.5.7.2.2 Monitoring frames available for requests .57
8.5.7.2.3 Response to pre-emption or changeover request .57
8.5.7.2.4 Response to timing change request.58
8.5.7.3 Procedures for requesting DM-MS .58
8.5.7.3.1 Preparing for random access.58
ETSI
6 ETSI EN 300 396-4 V1.3.1 (2006-05)
8.5.7.3.2 First transmission of request.58
8.5.7.3.3 Valid access slots.58
8.5.7.3.4 Waiting for response.58
8.5.7.3.5 Subsequent transmission of request.59
8.5.7.3.6 Abandoning random access attempt .59
8.6 MAC procedures in traffic mode.59
8.6.1 Introduction.59
8.6.2 Criteria for transmission and reception of traffic.59
8.6.3 Change of U-plane mode .59
8.6.3.1 Call set-up without presence check.59
8.6.3.1.1 Outgoing call.59
8.6.3.1.2 Incoming call.60
8.6.3.2 Call set-up with presence check .60
8.6.3.2.1 Outgoing call.60
8.6.3.2.2 Incoming call.60
8.6.3.3 Late entry.60
8.6.3.4 End of traffic transmission .60
8.6.3.4.1 Master DM-MS.60
8.6.3.4.2 Slave DM-MS.61
8.6.4 Exchange of information at the DMD-SAP.61
8.6.5 Stealing from circuit mode capacity .61
9 DM-REP layer 2 protocol for a type 1 DM-REP .61
9.1 Introduction.61
9.1.1 Functions of lower MAC .61
9.1.2 Functions of upper MAC .62
9.2 Interface between lower and upper MAC.62
9.3 Basic capabilities of the DM-REP physical layer.62
9.4 Usage of DM channel.63
9.4.1 DM-REP operation.63
9.4.1.1 Channel structure.63
9.4.1.2 Channel synchronization.63
9.4.2 DM-REP states.63
9.4.2.1 DM-REP state definitions .64
9.4.2.2 DM-REP channel surveillance procedures.64
9.4.2.2.1 DM-REP channel surveillance when idle on a channel in unknown or free state (i.e. in state 0
or 1) .64
9.4.2.2.2 DM-REP channel surveillance when idle on a busy channel (i.e. in state 2).65
9.4.2.2.3 DM-REP channel surveillance when idle at DM-MS call set-up .65
9.4.2.3 DM-REP channel maintenance when active during a call .66
9.4.3 Criteria for changing DM-REP state.66
9.4.3.1 Criteria for changing DM-REP state for active DM-REP.66
9.4.3.2 Criteria for changing DM-REP state for idle DM-REP .67
9.4.4 DM-REP channel monitoring procedures.68
9.4.4.1 DM channel during call set-up with presence check.68
9.4.4.2 DM channel in occupation during a circuit mode call.69
9.4.4.3 DM channel in reservation during a circuit mode call .69
9.4.4.4 DM channel in occupation during an SDS call .69
9.4.4.5 DM channel following pre-emption or changeover acceptance.70
9.4.4.6 DM channel following timing change announcement.70
9.4.5 DM-REP presence signal.71
9.4.5.1 Channel free.71
9.4.5.2 Channel in occupation.72
9.4.5.3 Channel in reservation.72
9.4.6 DM-REP linearization.73
9.5 DM-REP procedures for re-transmission of signalling messages .73
9.5.1 Re-transmission of signalling messages received from the master DM-MS .74
9.5.1.1 Re-transmission of master DM-MS signalling messages received in a DSB.74
9.5.1.1.1 General procedures.74
9.5.1.1.2 Re-transmission of DM-SETUP or DM-SETUP PRES message.74
9.5.1.1.3 Re-transmission of DM-SDS DATA or DM-SDS UDATA message .75
9.5.1.1.4 Re-transmission of other messages in a DSB when not using multi-slot regeneration.76
ETSI
7 ETSI EN 300 396-4 V1.3.1 (2006-05)
9.5.1.1.5 Re-transmission of other messages in a DSB during traffic transmission with multi-slot
regeneration .76
9.5.1.2 Re-transmission of master DM-MS signalling messages received in a DNB .76
9.5.1.2.1 Call transaction without multi-slot regeneration .76
9.5.1.2.2 Call transaction with multi-slot regeneration.77
9.5.1.3 Regeneration of missing repetitions on the slave link.77
9.5.2 Re-transmission of signalling messages received from a slave DM-MS.78
9.5.2.1 General procedures.78
9.5.2.2 Re-transmission of response messages from a slave DM-MS.78
9.5.2.3 Re-transmission of random access request.79
9.5.3 DM-REP signalling mechanisms.79
9.5.3.1 Frame countdown procedure.79
9.5.3.2 Fill bit addition and deletion .80
9.5.3.3 Null PDU.80
9.5.3.4 Air interface encryption .80
9.5.3.5 Timing change procedure.80
9.5.3.6 Random access procedures for DM-REP.80
9.6 DM-REP procedures in traffic mode.81
9.6.1 Introduction.81
9.6.2 Change of U-plane mode .81
9.6.2.1 Set-up without presence check.81
9.6.2.1.1 Switching into traffic mode .81
9.6.2.1.2 Link establishment failure .81
9.6.2.2 Set-up with presence check.82
9.6.2.3 End of traffic transmission .82
9.6.3 DM-REP traffic operation when active in traffic mode.82
9.6.3.1 Reception of TCH and STCH on the master link.82
9.6.3.2 Re-transmission of TCH and STCH on the slave link.83
9.6.3.2.1 Call transaction without multi-slot regeneration .83
9.6.3.2.2 Call transaction with multi-slot regeneration.84
10 PDU descriptions.84
10.1 Layer 2 PDUs sent in DSB.84
10.1.1 DMAC-SYNC PDU.84
10.1.2 DPRES-SYNC PDU.85
10.2 Layer 2 PDUs sent in DNB .86
10.3 Layer 2 information element coding .86
10.3.1 Addressing for URT = 0010 .86
10.3.2 Addressing for URT = 0011 .87
10.3.3 Addressing for URT = 0100 or 0101 .87
2 2
10.3.4 Addressing for URT = 0110 .87
10.3.5 Channel state.
...