SIST EN 300 396-4 V1.2.1:2003

• Abstract:

  Option to DE/RES-06001 for Direct Mode Operation of mobile terminals with or without network coverage. Split on 2/95 into three parts: Part 1: General network design Part 2: Air interface Part 3: Security

• 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: T-172
• Ref Project: ETSI EN 300 396-4 V1.2.1 (2000-12) - Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 4: Type 1 repeater air interface

Overview

SIST EN 300 396-4 V1.2.1:2003 specifies the technical requirements for Direct Mode Operation (DMO) in Terrestrial Trunked Radio (TETRA) systems, focusing on the Type 1 repeater air interface. Developed by the Slovenian Institute for Standardization (SIST) and harmonized with European EN 300 396-4, this standard plays an important role in enabling direct, reliable communication between TETRA mobile terminals with or without centralized network coverage. TETRA DMO is essential for mission-critical applications where robust voice and short data message communication is required, particularly when users are outside the coverage area of the main network or network infrastructure is not present.

This part - Part 4 - builds on prior parts dedicated to network design, the air interface, and security, providing a framework for how mobile terminals interact through a type 1 DMO repeater, ensuring interoperability, operational effectiveness, and security.

Key Topics

• Direct Mode Operation (DMO): Operation mode where TETRA terminals communicate directly with each other, bypassing the main TETRA infrastructure - vital in remote or emergency situations.
• Type 1 DMO Repeater: Technical definitions for a repeater that receives and retransmits DMO signals, extending the communication range and overcoming physical obstructions.
• Air Interface Requirements: Defines how signals are exchanged, including synchronization, channel structure, message handling, addressing, and channel surveillance procedures.
• Call Procedures: Covers processes for call setup (with or without presence check), changeover, pre-emption, and termination in the context of a type 1 DMO repeater.
• Short Data Service (SDS): Support for critical messaging, enabling unacknowledged and acknowledged short data exchanges in direct mode.
• Signalling and MAC Procedures: Focus on mechanisms for message transmission, error protection, encryption, addressing, and frame structure to ensure secure and reliable communications.
• Channel Surveillance: Describes methods for monitoring and managing channels to ensure efficient utilization and prompt reaction to communication requests.
• Interoperability: Ensures TETRA terminals and repeaters from different vendors can operate together within a standardized environment.

Applications

Adherence to SIST EN 300 396-4 V1.2.1:2003 offers substantial practical value in fields requiring resilient, on-demand communications:

• Public Safety and Emergency Services: Fire, police, and ambulance units benefit from direct communications when network infrastructure is unavailable or compromised.
• Utilities and Transport: Enables secure and reliable team communication across dispersed locations, such as railway operations or electrical grid maintenance crews.
• Industrial and Event Security: Facilitates secure on-site communication, even in remote areas or complex indoor environments.
• Disaster Response: Essential for coordinated operations where rapid deployment and infrastructure independence are critical.

Implementing the standard ensures clear guidelines for system integrators, manufacturers, and operators, supporting reliable TETRA direct mode repeater solutions.

Related Standards

For comprehensive TETRA DMO system design and deployment, the following related standards should be consulted:

• SIST EN 300 396-1: General network design for TETRA Direct Mode Operation
• SIST EN 300 396-2: TETRA Air Interface technical requirements
• SIST EN 300 396-3: TETRA Security aspects within DMO
• ETSI EN 300 394 series: Broader TETRA functional and performance requirements
• ETSI TS 100 392 series: Additional DMO protocol and interoperability specifications

These standards collectively support best practices for robust, interoperable, and secure TETRA solutions, ensuring that communications remain available and effective in any situation.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.QDþLQTerrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 4: Type 1 repeater air interface33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 396-4 Version 1.2.1SIST EN 300 396-4 V1.2.1:2003en01-december-2003SIST EN 300 396-4 V1.2.1:2003SLOVENSKI
STANDARD
ETSIEN300396-4V1.2.1(2000-12)EuropeanStandard(Telecommunicationsseries)TerrestrialTrunkedRadio(TETRA);TechnicalrequirementsforDirectModeOperation(DMO);Part4:Type1repeaterairinterfaceSIST EN 300 396-4 V1.2.1:2003

ETSIETSIEN300396-4V1.2.1(2000-12)2ReferenceDEN/TETRA-02007-4KeywordsTETRA,radio,securityETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 396-4 V1.2.1:2003

ETSIETSIEN300396-4V1.2.1(2000-12)3ContentsIntellectualPropertyRights.9Foreword.91Scope.102References.103Definitionsandabbreviations.113.1Definitions.113.2Abbreviations.134Overviewofprotocol.144.1General.144.2TheDMchannel.164.3DMcallproceduresforoperationwithatype1DM-REP.164.3.1Constraintsontheframestructure.184.3.2Settingupacall.184.3.2.1Callset-upwithoutpresencecheck.194.3.2.2Callset-upwithpresencecheck.204.3.3Changeoverinacall.214.3.4Pre-emptionofaDMcall.224.3.5Terminatingacall.224.3.6DMshortdatacall.234.3.6.1Unacknowledgedshortdatamessage.234.3.6.2Acknowledgedshortdatamessage.235DM-MSlayer3servicedescriptionforoperationwithatype1DM-REP.245.1Introduction.245.2Servicesoffered.245.3Primitivedescription.255.4Parameterdescription.255.5StatesforDMCC-SAP.256DM-MSlayer3protocolforoperationwithatype1DM-REP.256.1Introduction.256.1.1DMCCprotocolstates.256.2Circuitmodecalls.266.2.1Proceduresforcallset-upwithoutpresencecheck.266.2.1.1Outgoingcall.266.2.1.2Incomingcall.266.2.1.3Temporarygroupaddress.266.2.2Proceduresforcallset-upwithpresencecheck.266.2.2.1Outgoingcall.266.2.2.2Incomingcall.276.2.3UsageofDM-OCCUPIEDPDU.276.2.3.1SendingofDM-OCCUPIEDPDUbymasterDM-MS.276.2.3.2LateentrybyslaveDM-MS.276.2.4Proceduresduringoccupation.276.2.4.1MasterDM-MS.276.2.4.2SlaveDM-MS.276.2.4.3TransmittingPartyNumberIdentification(TPNI).276.2.5Proceduresduringreservation.276.2.5.1MasterDM-MS.276.2.5.2SlaveDM-MS.276.2.5.3Pre-emptionofshortdatasentasatransactionwithinacircuitmodecall.276.2.6Procedurestosetupanewcallbypre-emption.286.3ShortDataService(SDS)procedures.286.3.1Sendingshortdata.286.3.1.1Sendingshortdataonafreechannel.28SIST EN 300 396-4 V1.2.1:2003

ETSIETSIEN300396-4V1.2.1(2000-12)46.3.1.1.1Sendingunacknowledgedshortdataonafreechannel.286.3.1.1.2Sendingacknowledgedshortdataonafreechannel.296.3.1.2Sendingshortdatabypre-emption.296.3.1.3Sendingshortdataduringcircuitmodetransmission.296.3.1.4Sendingshortdataasatransactionwithinacircuitmodecall.296.3.2Receivingshortdata.296.3.2.1Receivingunacknowledgedshortdata.296.3.2.2Receivingacknowledgedshortdata.296.3.3Additionaladdressing.296.3.4Extendederrorprotection.296.4UsageofDMA-UNITDATAprimitive.307DM-MSlayer2servicedescriptionforoperationwithatype1DM-REP.307.1Introduction.307.2Layer2architecture.307.3Servicedescriptions.307.3.1ServicesattheDMA-SAP.307.3.1.1Servicesprovidedtolayer3.307.3.1.2ServiceprimitivesattheDMA-SAP.317.3.2ServicesattheDMC-SAP.317.3.2.1Servicesprovidedtolayer3.317.3.2.2ServiceprimitivesattheDMC-SAP.317.3.2.2.1DMC-CONFIGUREprimitive.317.3.2.2.2DMC-REPORTprimitive.317.3.3ServicesattheDMD-SAP.317.3.3.1ServicesprovidedtotheU-planeapplication.317.3.3.2ServiceprimitivesattheDMD-SAP.317.4Parameterlisting.328DM-MSlayer2protocolforoperationwithatype1DM-REP.328.1Introduction.328.1.1FunctionsoflowerMAC.328.1.2FunctionsofupperMAC.328.2InterfacebetweenlowerandupperMAC.338.2.1LogicalchannelsdefinedattheDMV-SAP.338.2.2ServiceprimitivesattheDMV-SAP.338.2.3PDUmappingofthelogicalchannelsattheDMV-SAP.338.2.4Scramblingmechanism.338.2.5PDUerrordetection.338.2.6Modesofoperation.348.3Basiccapabilitiesofthephysicallayer.348.3.1DM-MScapabilities.348.3.1.1DMonlyanddualmodecapableMSoperation.348.3.1.2DualwatchcapableMSoperation.348.4UsageofDMchannelwithtype1DM-REP.358.4.1DefinitionofDMchannel.358.4.1.1DMchannelarrangement.358.4.1.2DMchanneloperation.358.4.2DMchannelstates.368.4.2.1DMchannelstatedefinitions.368.4.2.2DM-MSchannelsurveillanceprocedures.378.4.2.2.1InitialdeterminationofDMchannelstate.378.4.2.2.2DM-MSchannelsurveillanceinidlemode.378.4.2.2.3DM-MSchannelsurveillanceatcallset-up.378.4.2.3MasterDM-MSchannelsurveillanceproceduresduringacall.388.4.2.4SlaveDM-MSchannelsurveillanceproceduresduringacall.388.4.2.4.1SlaveMSchannelsurveillanceduringcalltransaction.398.4.2.4.2SlaveMSsignalqualitymeasurementduringcalltransaction.398.4.2.4.3SlaveMSchannelsurveillanceduringreservation.398.4.3DM-MACstates.398.4.3.1DM-MACstatedefinitions.398.4.3.2CriteriaforchangingDM-MACstate.39SIST EN 300 396-4 V1.2.1:2003

ETSIETSIEN300396-4V1.2.1(2000-12)58.4.4DM-MSchannelmonitoringprocedures.398.4.4.1DMchannelduringinitialcallset-upandnewcalltransactionbycurrentmasterMS.408.4.4.2DMchannelduringcallset-upwithpresencecheck.408.4.4.3DMchannelinoccupationduringacircuitmodecall.408.4.4.4DMchannelinreservationduringacircuitmodecall.408.4.4.5DMchannelinoccupationduringanSDScall.418.4.4.6DMchannelusageduringpre-emptionsignalling.418.4.4.7DMchannelusageduringtimingchangerequestsignalling.418.4.5Transmissionoflayer3messagesbyDM-MAC.418.4.5.1TransmissionofC-planemessagesbyDM-MAC.418.4.5.2TransmissionofU-planemessagesbyDM-MAC.428.4.6Transmissionoflayer2messagesgeneratedbyDM-MAC.428.4.7GeneralDM-MACprocedures.428.4.7.1DM-MACrepeattransmissions.428.4.7.2DM-MACframecountdownprocedure.428.4.7.3Useoftimers.428.4.7.4Linearization.428.4.7.5Fragmentation.438.4.7.6Fillbitindication.438.4.7.7Selectionofpseudoaddress.438.4.7.8Slotflagindication.438.4.7.9Requestsbitmap.438.4.7.10DMaspectsofdualwatchoperation.448.4.7.10.1Modelofoperation.448.4.7.10.2Dualwatchsynchronization.448.4.7.10.3Dualwatchprecedencerules.458.4.7.11Airinterfaceencryption.458.4.7.12ChannelAorBoperation.458.4.7.13Sendingshortdataasatransactionwithinacircuitmodecall.458.4.7.14SDStimeremaining.458.4.7.15Timingchangeprocedure.458.4.7.16Timingchangeatchangeoverorpre-emption.468.5MACproceduresfortransferofsignallingmessages.468.5.1FormationofMACPDU.468.5.2Addressing.468.5.2.1Transmissionofmessage.468.5.2.1.1Addressinginsynchronizationburst.468.5.2.1.2Addressinginnormalburst.478.5.2.2Receptionofmessage.478.5.3Useofairinterfaceencryption.478.5.4Fragmentationandreconstruction.488.5.4.1Fragmentation.488.5.4.2Reconstruction.498.5.5Fillbitadditionanddeletion.498.5.6Transmissionandreceptionofmessagesbylayer2.498.5.6.1Transmissionofmessage.508.5.6.2Receptionofmessage.518.5.7Randomaccessprotocol.528.5.7.1Introduction.528.5.7.2ProceduresformasterDM-MS.528.5.7.2.1Indicatingframesavailableforrequests.528.5.7.2.2Monitoringframesavailableforrequests.538.5.7.2.3Responsetopre-emptionorchangeoverrequest.538.5.7.2.4Responsetotimingchangerequest.548.5.7.3ProceduresforrequestingDM-MS.548.5.7.3.1Preparingforrandomaccess.548.5.7.3.2Firsttransmissionofrequest.548.5.7.3.3Validaccessslots.548.5.7.3.4Waitingforresponse.548.5.7.3.5Subsequenttransmissionofrequest.558.5.7.3.6Abandoningrandomaccessattempt.558.6MACproceduresintrafficmode.55SIST EN 300 396-4 V1.2.1:2003

ETSIETSIEN300396-4V1.2.1(2000-12)68.6.1Introduction.558.6.2Criteriafortransmissionandreceptionoftraffic.558.6.3ChangeofU-planemode.558.6.3.1Callset-upwithoutpresencecheck.558.6.3.1.1Outgoingcall.558.6.3.1.2Incomingcall.568.6.3.2Callset-upwithpresencecheck.568.6.3.2.1Outgoingcall.568.6.3.2.2Incomingcall.568.6.3.3Lateentry.568.6.3.4Endoftraffictransmission.568.6.3.4.1MasterDM-MS.568.6.3.4.2SlaveDM-MS.568.6.4ExchangeofinformationattheDMD-SAP.578.6.5Stealingfromcircuitmodecapacity.579DM-REPlayer2protocolforatype1DM-REP.579.1Introduction.579.1.1FunctionsoflowerMAC.579.1.2FunctionsofupperMAC.589.2InterfacebetweenlowerandupperMAC.589.3BasiccapabilitiesoftheDM-REPphysicallayer.589.4UsageofDMchannel.599.4.1DM-REPoperation.599.4.1.1Channelstructure.599.4.1.2Channelsynchronization.599.4.2DM-REPstates.599.4.2.1DM-REPstatedefinitions.609.4.2.2DM-REPchannelsurveillanceprocedures.609.4.2.2.1DM-REPchannelsurveillancewhenidleonafreechannel(i.e.instate1).609.4.2.2.2DM-REPchannelsurveillancewhenidleonabusychannel(i.e.instate2).619.4.2.2.3DM-REPchannelsurveillancewhenidleatDM-MScallset-up.619.4.2.3DM-REPchannelsurveillancewhenactiveduringacall.629.4.3CriteriaforchangingDM-REPstate.629.4.4DM-REPchannelmonitoringprocedures.639.4.4.1DMchannelduringcallset-upwithpresencecheck.639.4.4.2DMchannelinoccupationduringacircuitmodecall.639.4.4.3DMchannelinreservationduringacircuitmodecall.649.4.4.4DMchannelinoccupationduringanSDScall.649.4.4.5DMchannelfollowingpre-emptionorchangeoveracceptance.659.4.4.6DMchannelfollowingtimingchangeannouncement.659.4.5DM-REPpresencesignal.669.4.5.1Channelfree.669.4.5.2Channelinoccupation.669.4.5.3Channelinreservation.679.4.6DM-REPlinearization.679.5DM-REPproceduresforre-transmissionofsignallingmessages.689.5.1Re-transmissionofsignallingmessagesreceivedfromthemasterDM-MS.689.5.1.1Re-transmissionofmasterDM-MSsignallingmessagesreceivedinaDSB.689.5.1.1.1Generalprocedures.689.5.1.1.2Re-transmissionofDM-SETUPorDM-SETUPPRESmessage.699.5.1.1.3Re-transmissionofDM-SDSDATAorDM-SDSUDATAmessage.699.5.1.1.4Re-transmissionofothermessagesinaDSBwhennotusingmulti-slotregeneration.709.5.1.1.5Re-transmissionofothermessagesinaDSBduringtraffictransmissionwithmulti-slotregeneration.709.5.1.2Re-transmissionofmasterDM-MSsignallingmessagesreceivedinaDNB.719.5.1.2.1Calltransactionwithoutmulti-slotregeneration.719.5.1.2.2Calltransactionwithmulti-slotregeneration.719.5.1.3Regenerationofadditionalrepetitionsontheslavelink.729.5.2Re-transmissionofsignallingmessagesreceivedfromaslaveDM-MS.729.5.2.1Generalprocedures.729.5.2.2Re-transmissionofresponsemessagesfromaslaveDM-MS.73SIST EN 300 396-4 V1.2.1:2003

ETSIETSIEN300396-4V1.2.1(2000-12)79.5.2.3Re-transmissionofrandomaccessrequest.739.5.3DM-REPsignallingmechanisms.749.5.3.1Framecountdownprocedure.749.5.3.2Fillbitadditionanddeletion.749.5.3.3NullPDU.749.5.3.4Airinterfaceencryption.749.5.3.5Timingchangeprocedure.759.5.3.6RandomaccessproceduresforDM-REP.759.6DM-REPproceduresintrafficmode.759.6.1Introduction.759.6.2ChangeofU-planemode.769.6.2.1Set-upwithoutpresencecheck.769.6.2.1.1Switchingintotrafficmode.769.6.2.1.2Linkestablishmentfailure.769.6.2.2Set-upwithpresencecheck.769.6.2.3Endoftraffictransmission.779.6.3DM-REPtrafficoperationwhenactiveintrafficmode.779.6.3.1ReceptionofTCHandSTCHonthemasterlink.779.6.3.2Re-transmissionofTCHandSTCHontheslavelink.789.6.3.2.1Calltransactionwithoutmulti-slotregeneration.789.6.3.2.2Calltransactionwithmulti-slotregeneration.7810PDUdescriptions.7910.1Layer2PDUssentinDSB.7910.1.1DMAC-SYNCPDU.7910.1.2DPRES-SYNCPDU.8010.2Layer2PDUssentinDNB.8110.3Layer2informationelementcoding.8110.3.1AddressingforURT=00102.8110.3.2AddressingforURT=00112.8110.3.3AddressingforURT=01002or01012.8210.3.4AddressingforURT=01102.8210.3.5Channelstate.8210.3.6Channelusage.8310.3.7MaximumDM-MSpowerclass.8310.3.8M-DMOflag.8310.3.9MNIofDM-REP.8310.3.10Numberofvaliditytimeunits.8410.3.11Presencesignaldualwatchsynchronizationflag.8410.3.12Repeateroperatingmodes.8410.3.13Spacingofuplink.8510.3.14Two-frequencyrepeaterflag.8510.3.15Usagerestrictiontype(URT).8510.3.16Validitytimeunit.8610.3.17ValueofDT254.8610.3.18ValuesofDN232andDN233.8610.4Messagesgeneratedbylayer2.8710.5Layer3PDUs.8710.6Messagedependentelementscoding.8810.6.1Dualwatchsynchronizationflag.8910.6.2Two-frequencycallflag.8910.7DM-SDUelementscoding.9011RadioaspectsofDM-MSforoperationwithatype1DM-REP.9011.1Introduction.9011.2Modulation.9011.3Radiotransmissionandreception.9011.3.1Introduction.9011.3.2Frequencybandsandchannelarrangement.9011.3.3Referencetestplanes.9011.3.4Transmittercharacteristics.9111.3.5Receivercharacteristics.91SIST EN 300 396-4 V1.2.1:2003

ETSIETSIEN300396-4V1.2.1(2000-12)811.3.6Transmitter/receiverperformance.9111.4Radiosub-systemsynchronization.9111.4.1Introduction.9111.4.2DefinitionsandgeneralrequirementsforsynchronizationofDM-MSs.9111.4.3Timebasecounters.9211.4.4RequirementsforthefrequencyreferencesourceofDMmobiles.9211.4.5RequirementsforthesynchronizationofaslaveDMmobile.9211.4.6SynchronizationrequirementsforamasterMSoperatingonchannelBinfrequencyefficientmode.9211.5Channelcodingandscrambling.9211.6ChannelmultiplexingforDMoperationthroughatype1DM-REP.9211.7Radiosub-systemlinkcontrol.9312Radioaspectsofatype1DM-REP.9312.1Introduction.9312.2Modulation.
...