SIST EN 300 396-8-4 V1.1.1:2003

• Abstract:

  To produce a PICS proforma for Direct Mode Operation of Repeater type 2

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.10 - Terrestrial Trunked Radio (TETRA)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Mandate: BC-T-344
• Mandate: T-172
• Ref Project: ETSI EN 300 396-8-4 V1.1.1 (2001-01) - Terrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 8: Protocol Implementation Conformance Statement (PICS) proforma specification; Sub-part 4: Type 2 repeater Air Interface (AI)

SIST EN 300 396-8-4 V1.1.1:2003 is the Slovenian adoption of EN 300 396-8-4, published by SIST. It specifies the Protocol Implementation Conformance Statement (PICS) proforma for Terrestrial Trunked Radio (TETRA) Direct Mode Operation (DMO) with a Type 2 repeater, so suppliers can state which MS-REP2 and DM-REP2 capabilities their implementation supports.

What does SIST EN 300 396-8-4 V1.1.1:2003 specify?

SIST EN 300 396-8-4 V1.1.1:2003 specifies a standardized PICS questionnaire for TETRA DMO implementations that work with a Type 2 repeater. It tells suppliers what to declare for the MS-REP2 and DM-REP2 protocol parts, and it follows the conformance-testing guidance named in the references.

The document is organized into four main clauses:

• Scope
• References
• Definitions and abbreviations
• Conformance to this PICS proforma

Annex A is normative and contains the full PICS proforma, including the completion guidance and the tables to be filled in.

What are the key requirements of SIST EN 300 396-8-4 V1.1.1:2003?

The central requirement is that any PICS claiming conformance to this standard must be technically equivalent to the proforma in Annex A and keep the same numbering, naming, and order. In practice, this lets a test lab or buyer compare implementations on a like-for-like basis.

Annex A.1 sets the completion rules. The tables use item numbers, item descriptions, status, references, support answers, and allowed values, and the supplier must answer with the prescribed notation such as mandatory, optional, not applicable, prohibited, qualified optional, or conditional. That matters because many answers depend on other choices, so the form shows when a feature becomes required or not relevant.

A.2 asks for identification of the implementation, the system under test, the supplier, the client if different, and a contact person. This gives traceability for the exact product version and configuration being declared.

A.3 and A.4 split the scope into two protocol parts: MS-REP2, which covers DMO mobile station behavior with a Type 2 repeater, and DM-REP2, which covers the Type 2 repeater layer 2 protocol. The global conformance questions ask whether all mandatory capabilities are implemented, so a supplier can state conformance clearly before test submission.

A.5 requires the supplier to declare the implementation role:

• MS-REP2
• DM-REP2

At least one role must be supported. This matters because some products are only mobile stations, while others are only repeaters.

A.6 covers MS-REP2 in two layers. It asks for support of Direct Mode Call Control (DMCC) services such as circuit mode call and Short Data Service (SDS), then drills down into call setup, call services, SDS types, user-defined data, PDUs, constants, and timers. In practice, this is where a supplier shows whether the device supports voice, data, presence check, pre-emption, and the timing behavior needed for interoperability.

A.7 covers DM-REP2 at layer 2. It asks for major services, MAC features, procedures, PDUs, generated messages, constants, and timers for the repeater. This tells the reader how the repeater handles channel use, retransmission, synchronization, and traffic mode behavior.

A.8 lists the PDU parameters for both MS-REP2 and DM-REP2. These tables show which message elements belong to each PDU, including fields tied to encryption, additional addressing, short data types, and message control. That helps test teams verify that the implementation can parse and generate the right protocol data.

What terms does SIST EN 300 396-8-4 V1.1.1:2003 define?

ICS (Implementation Conformance Statement) - A supplier statement that lists which capabilities an implementation supports.

ICS proforma - A questionnaire form that becomes an ICS when it is completed for a specific implementation or system.

PICS (Protocol Implementation Conformance Statement) - An ICS for a claimed implementation of a protocol specification.

IUT (Implementation Under Test) - The implementation whose conformance is being described and tested.

SUT (System Under Test) - The system that contains the IUT and the hardware/software environment around it.

MS-REP2 - The DM-MS role that supports operation with a Type 2 DM-REP.

DM-REP2 - The Type 2 repeater protocol, covered here at layer 2.

Who uses SIST EN 300 396-8-4 V1.1.1:2003?

SIST EN 300 396-8-4 V1.1.1:2003 is used by suppliers of TETRA DMO equipment, especially manufacturers of mobile stations and Type 2 repeaters. It is also used by conformance test engineers, quality managers, and buyers who need a structured declaration of what a product supports.

The document is practical when preparing test submissions, documenting supported roles and features, and checking whether a product supports circuit mode call, SDS, PDUs, timers, and repeater functions.

What changed in SIST EN 300 396-8-4 V1.1.1:2003 from the previous edition?

The history records that the document was first processed as ETS 300 396-8-4, then converted into an EN during the Vote stage. It was published as EN 300 396-8-4 V1.1.1 after that conversion.

Which standards are used with SIST EN 300 396-8-4 V1.1.1:2003?

• EN 300 396-7 - The main Type 2 repeater air interface specification that this PICS proforma applies to.
• ETS 300 396-3 - A related DMO air interface protocol reference used in item references inside the tables.
• EN 300 396-8-2 - The PICS proforma for Type 1 repeater air interface, used as a model for the wording and structure in this part.
• ETS 300 406 - The ETSI testing and specification methodology referenced for conformance testing practice.
• ISO/IEC 9646-1 - Gives the general concepts for conformance testing.
• ISO/IEC 9646-7 - Gives the rules for Implementation Conformance Statements and questionnaire-style proformas.
• EN 300 396-4 - Supplies related DMO terminology and definitions used alongside this part.

What does the SIST EN 300 396-8-4 V1.1.1:2003 document contain?

Annex A contains the complete PICS proforma, starting with guidance on how to complete it and then moving through identification fields, protocol identification, global conformance, and role selection. It then provides detailed tables for MS-REP2 and DM-REP2 capabilities, including services, procedures, PDUs, constants, timers, and message parameters.

The tables use prerequisites and conditional expressions so the supplier only answers items that apply to the chosen feature set. This makes the form suitable for design review, test preparation, and conformance documentation without rewriting the protocol itself.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.REUDWRYDQMHRIRUPDTerrestrial Trunked Radio (TETRA); Technical requirements for Direct Mode Operation (DMO); Part 8: Protocol Implementation Conformance Statement (PICS) proforma specification; Sub-part 4: Type 2 repeater Air Interface (AI)33.070.10Prizemni snopovni radio (TETRA)Terrestrial Trunked Radio (TETRA)ICS:Ta slovenski standard je istoveten z:EN 300 396-8-4 Version 1.1.1SIST EN 300 396-8-4 V1.1.1:2003en01-december-2003SIST EN 300 396-8-4 V1.1.1:2003SLOVENSKI
STANDARD
ETSIEN300396-8-4V1.1.1(2001-01)EuropeanStandard(Telecommunicationsseries)TerrestrialTrunkedRadio(TETRA);TechnicalrequirementsforDirectModeOperation(DMO);Part8:ProtocolImplementationConformanceStatement(PICS)proformaspecification;Sub-part4:Type2repeaterAirInterface(AI)SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)2ReferenceDEN/TETRA-02007-8-4KeywordsDMO,ICS,PICS,radio,TETRAETSI650RoutedesLuciolesF-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.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)3ContentsIntellectualPropertyRights.5Foreword.5Introduction.61Scope.72References.73Definitionsandabbreviations.73.1Definitions.73.2Abbreviations.84ConformancetothisPICSproformaspecification.8AnnexA(normative):ProtocolICSproforma(PICS)forEN300396-4.9A.1GuidanceforcompletingthePICSproforma.9A.1.1Purposesandstructure.9A.1.2Abbreviationsandconventions.9A.1.3InstructionsforcompletingthePICSproforma.11A.2Identificationoftheimplementation.11A.2.1Dateofthestatement.11A.2.2ImplementationUnderTest(IUT)identification.11A.2.3SystemUnderTest(SUT)identification.12A.2.4Productsupplier.12A.2.5Client(ifdifferentfromproductsupplier).12A.2.6PICScontactperson.13A.3IdentificationoftheProtocol.13A.4Globalstatementofconformance.13A.5Roles.14A.6ProtocolsforDM-MSsupportingoperationwithatype2DM-REP(MS-REP2).14A.6.1MS-REP2DirectModeCallControl(DMCC)atLayer3.14A.6.1.1DMCCmajorcapabilities.14A.6.1.2Circuitmodecall.15A.6.1.3Circuitmodecallset-up.15A.6.1.4Circuitmodeservicesoffered.16A.6.1.5Shortdataservices.16A.6.1.6Typeofshortdataservice.17A.6.1.7Datatransmission.18A.6.1.8SDSuserdefineddata.18A.6.1.9DMCCPDUs.19A.6.1.10DMCCconstants.21A.6.1.11DMCCtimers.22A.6.2MS-REP2Datalinklayer(DLL)atLayer2.23A.6.2.1MS-REP2MACfeatures.23A.6.2.2MS-REP2-MACprocedures.23A.6.2.3MS-REP2MACPDUs.27A.6.2.4MS-REP2MACgeneratedmessages.28A.6.2.5MS-REP2MACconstants.28A.6.2.6MS-REP2MACtimers.30A.7DM-REPtype2Protocol(DM-REP2).31A.7.1DM-REP2Datalinklayer(DLL)atLayer2.31A.7.1.1Majorservices.31A.7.1.2DM-REP2MACfeatures.31SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)4A.7.1.3DM-REP2MACprocedures.32A.7.1.4DM-REP2MACPDUs.34A.7.1.5DM-REP2MACgeneratedmessages.34A.7.1.6DM-REP2MACconstants.34A.7.1.7DM-REP2MACtimers.35A.8PDUparametersforMS-REP2andDM-REP2usedinDMCCatlayer3andDLLatlayer2.36A.8.1MS-REP2PDUparametersforDMCCatlayer3.36A.8.1.1DM-SETUP.36A.8.1.2DM-SETUPPRES.36A.8.1.3DM-CONNECT.37A.8.1.4DM-DISCONNECT.37A.8.1.5DM-CONNECTACK.37A.8.1.6DM-OCCUPIED.38A.8.1.7DM-RELEASE.38A.8.1.8DM-TXCEASED.38A.8.1.9DM-TXREQUEST.39A.8.1.10DM-TXACCEPT.39A.8.1.11DM-PREEMPT.39A.8.1.12DM-PREACCEPT.39A.8.1.13DM-REJECT.39A.8.1.14DM-INFO.40A.8.1.15DM-SDSUDATA.40A.8.1.16DM-SDSDATA.41A.8.1.17DM-SDSACK.41A.8.2MS-REP2andDM-REP2PDUparametersforDLLatlayer2.42A.8.2.1DMAC-SYNCinSCH/S.42A.8.2.2DPRES-SYNCPDU.43A.8.2.3DMAC-DATA.44A.8.2.4DMAC-FRAG.44A.8.2.5DMAC-END.44A.8.2.6DMAC-USIGNAL.44A.8.3DM-MACgeneratedmessageparameters.45A.8.3.1DM-RESERVED.45A.8.3.2DM-SDSOCCUPIED.45A.8.3.3DM-TIMINGREQUEST.45A.8.3.4DM-TIMINGACK.45History.46SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)5IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSIProjectTerrestrialTrunkedRadio(TETRA).ThepresentdocumenthadbeensubmittedtoPublicEnquiryasETS300396-8-4.DuringtheprocessingforVoteitwasconvertedintoanEN.Thepresentdocumentispart8ofamulti-partdeliverablecoveringtheTerrestrialTrunkedRadio(TETRA);TechnicalrequirementsforDirectModeOperation(DMO);asidentifiedbelow:Part1:"Generalnetworkdesign";Part2:"Radioaspects";Part3:"MobileStationtoMobileStation(MS-MS)AirInterface(AI)protocol";Part4:"Type1repeaterairinterface";Part5:"Gatewayairinterface";Part6:"Security";Part7:"Type2repeaterairinterface";Part8:"ProtocolImplementationConformanceStatement(PICS)proformaspecification";Part9:"ServiceandDescriptionLanguage(SDL)model";Part10:"ManagedDirectModeOperation(DMO)".NationaltranspositiondatesDateofadoptionofthisEN:22December2000DateoflatestannouncementofthisEN(doa):31March2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30September2001DateofwithdrawalofanyconflictingNationalStandard(dow):30September2001SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)6IntroductionToevaluateconformanceofaparticularimplementation,itisnecessarytohaveastatementofwhichcapabilitiesandoptionshavebeenimplementedforatelecommunicationspecification.SuchastatementiscalledanImplementationConformanceStatement(ICS).SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)71ScopeThepresentdocumetprovidestheProtocolImplementationConformanceStatement(PICS)proformaforTETRADirectModeOperation(DMO)MobileStations(MS)connectedtoType2repeater(MS-REP2)andforTETRADirectModeOperationType2repeater(DM-REP2),definedinEN300396-7[1]incompliancewiththerelevantrequirements,andinaccordancewiththerelevantguidancegiveninISO/IEC9646-7[6]andETS300406[4].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[1]ETSIEN300396-7:"TerrestrialTrunkedRadio(TETRA);TechnicalrequirementsforDirectModeOperation(DMO);Part7:Type2repeaterairinterface".[2]ETSIETS300396-3:"TerrestrialTrunkedRadio(TETRA);TechnicalrequirementsforDirectModeOperation(DMO);Part3:MobileStationtoMobileStation(MS-MS)AirInterface(AI)protocol".[3]ETSIEN300396-8-2:"TerrestrialTrunkedRadio(TETRA);TechnicalrequirementsforDirectModeOperation(DMO);Part8:ProtocolImplementationConformanceStatement(PICS)proformaspecification;Sub-part2:Type1repeaterAirInterface(AI)".[4]ETSIETS300406:"MethodsforTestingandSpecification(MTS);Protocolandprofileconformancetestingspecifications;Standardizationmethodology".[5]ISO/IEC9646-1(1994):"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part1:Generalconcepts".[6]ISO/IEC9646-7(1995):"Informationtechnology-Opensystemsinterconnection-Conformancetestingmethodologyandframework-Part7:ImplementationConformanceStatements".[7]ETSIEN300396-4:"TerrestrialTrunkedRadio(TETRA);TechnicalrequirementsforDirectModeOperation(DMO);Part4:Type1repeaterairinterface".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninEN300396-4[7],ISO/IEC9646-1[5],ISO/IEC9646-7[6]andthefollowingapply.ImplementationConformanceStatement(ICS):statementmadebythesupplierofanimplementationorsystemclaimedtoconformtoagivenspecification,statingwhichcapabilitieshavebeenimplemented.TheICScantakeseveralforms:protocolICS,profileICS,profilespecificICS,informationobjectICS,etc.ICSproforma:document,intheformofaquestionnaire,whichwhencompletedforanimplementationorsystembecomesanICSProtocolICS(PICS):ICSforanimplementationorsystemclaimedtoconformtoagivenprotocolspecificationSIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)83.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ICSImplementationConformanceStatementIUTImplementationUnderTestPICSProtocolImplementationConformanceStatementSCSSystemConformanceStatementSUTSystemUnderTest4ConformancetothisPICSproformaspecificationIfitclaimstoconformtothepresentdocument,theactualPICSproformatobefilledinbyasuppliershallbetechnicallyequivalenttothetextofthePICSproformagiveninannexA,andshallpreservethenumbering/namingandorderingoftheproformaitems.APICSwhichconformstothepresentdocumentshallbeaconformingPICSproformacompletedinaccordancewiththeguidanceforcompletiongiveninclauseA.1.SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)9AnnexA(normative):ProtocolICSproforma(PICS)forEN300396-4Notwithstandingtheprovisionsofthecopyrightclauserelatedtothetextofthepresentdocument,ETSIgrantsthatusersofthepresentdocumentmayfreelyreproducethePICSproformainthisannexsothatitcanbeusedforitsintendedpurposesandmayfurtherpublishthecompletedPICS.A.1GuidanceforcompletingthePICSproformaA.1.1PurposesandstructureThepurposeofthisPICSproformaistoprovideamechanismwherebyasupplierofanimplementationoftherequirementsdefinedinEN300396-7[1]mayprovideinformationabouttheimplementationinastandardizedmanner.ThePICSproformaissubdividedintoclausesforthefollowingcategoriesofinformation:• guidanceforcompletingthePICSproforma;• identificationoftheimplementation;• identificationoftheProtocol;• globalstatementofconformance;• identificationoftheroles,MS-REP2orDM-REP2;• MS-REP2layer3protocolpart;• MS-REP2protocollayer2part;• DM-REP2part.A.1.2AbbreviationsandconventionsThePICSproformacontainedinthisannexiscomprisedofinformationintabularforminaccordancewiththeguidelinespresentedinISO/IEC9646-7[6].ItemcolumnTheitemcolumncontainsanumberwhichidentifiestheiteminthetable.ItemdescriptioncolumnTheitemdescriptioncolumndescribesinfreetexteachrespectiveitem(e.g.parameters,timers,etc.).Itimplicitlymeans"issupportedbytheimplementation?".StatuscolumnThefollowingnotations,definedinISO/IEC9646-7[6],areusedforthestatuscolumn:mmandatory-thecapabilityisrequiredtobesupported;ooptional-thecapabilitymaybesupportedornot;n/anotapplicable-inthegivencontext,itisimpossibletousethecapability;xprohibited(excluded)-thereisarequirementnottousethiscapabilityinthegivencontext;SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)10o.iqualifiedoptional-formutuallyexclusiveorselectableoptionsfromaset."i"isanintegerwhichidentifiesauniquegroupofrelatedoptionalitemsandthelogicoftheirselectionwhichisdefinedimmediatelyfollowingthetable;ciconditional-therequirementonthecapability("m","o","x"or"n/a")dependsonthesupportofotheroptionalorconditionalitems."i"isanintegeridentifyingauniqueconditionalstatusexpressionwhichisdefinedimmediatelyfollowingthetable.ReferencecolumnThereferencecolumnmakesreferencetoEN300396-7[1],exceptwhereexplicitlystatedotherwise.SupportcolumnThesupportcolumnshallbefilledinbythesupplieroftheimplementation.Thefollowingcommonnotations,definedinISO/IEC9646-7[6],areusedforthesupportcolumn:Yorysupportedbytheimplementation;Nornnotsupportedbytheimplementation;N/A,n/aor-noanswerrequired(allowedonlyifthestatusisn/a,directlyorafterevaluationofaconditionalstatus).IfthisPICSproformaiscompletedinordertodescribeamultiple-profilesupportinasystem,itisnecessarytobeabletoanswerthatacapabilityissupportedforoneprofileandnotsupportedforanother.Inthatcase,thesuppliershallentertheuniquereferencetoaconditionalexpression,precededby"?"(e.g.?3).Thisexpressionshallbegiveninthespaceforcommentsprovidedatthebottomofthetable.ItusespredicatesdefinedintheSCS,eachofwhichreferstoasingleprofileandwhichtakesthevalueTRUEifandonlyifthatprofileistobeused.EXAMPLE:?3:IFprof1THENYELSENItisalsopossibletoprovideacommenttoananswerinthespaceprovidedatthebottomofthetable.NOTE:AsstatedinISO/IEC9646-7[6],supportforareceivedPDUrequirestheabilitytoparseallvalidparametersofthatPDU.SupportingaPDUwhilehavingnoabilitytoparseavalidparameterisnon-conformant.SupportforaparameteronaPDUmeansthatthesemanticsofthatparameteraresupported.ValuesallowedcolumnThevaluesallowedcolumncontainsthetype,thelist,therange,orthelengthofvaluesallowed.Thefollowingnotationsareused:• rangeofvalues:.example:5.20• listofvalues:,,.,example:2,4,6,8,9example:'1101'B,'1011'B,'1111'Bexample:'0A'H,'34'H,'2F'H• listofnamedvalues:(),(),.,(example:reject(1),accept(2)• length:size(.)example:size(1.8)SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)11ValuessupportedcolumnThevaluessupportedcolumnshallbefilledinbythesupplieroftheimplementation.Inthiscolumn,thevaluesortherangesofvaluessupportedbytheimplementationshallbeindicated.ReferencestoitemsForeachpossibleitemanswer(answerinthesupportcolumn)withinthePICSproformaauniquereferenceexists,used,forexample,intheconditionalexpressions.Itisdefinedasthetableidentifier,followedbyasoliduscharacter"/",followedbytheitemnumberinthetable.Ifthereismorethanonesupportcolumninatable,thecolumnsarediscriminatedbyletters(a,b,etc.),respectively.EXAMPLE1:A.5/4isthereferencetotheanswerofitem4intable5ofannexA.EXAMPLE2:A.6/3bisthereferencetothesecondanswer(i.e.inthesecondsupportcolumn)ofitem3intable6ofannexA.PrerequisitelineAprerequisitelinetakestheform:Prerequisite:.AprerequisitelineafteraclauseortabletitleindicatesthatthewholeclauseorthewholetableisnotrequiredtobecompletedifthepredicateisFALSE.A.1.3InstructionsforcompletingthePICSproformaThesupplieroftheimplementationshallcompletethePICSproformaineachofthespacesprovided.Inparticular,anexplicitanswershallbeentered,ineachofthesupportorsupportedcolumnboxesprovided,usingthenotationdescribedinclauseA.1.2.Ifnecessary,thesuppliermayprovideadditionalcommentsinspaceatthebottomofthetables,orseparatelyonsheetsofpaper.MoredetailedinstructionsaregivenatthebeginningofthedifferentclausesofthePICSproforma.A.2IdentificationoftheimplementationIdentificationoftheImplementationUnderTest(IUT)andthesysteminwhichitresides(theSystemUnderTest(SUT))shouldbefilledinsoastoprovideasmuchdetailaspossibleregardingversionnumbersandconfigurationoptions.Theproductsupplierinformationandclientinformationshouldbothbefillediniftheyaredifferent.ApersonwhocananswerqueriesregardinginformationsuppliedinthePICSshouldbenamedasthecontactperson.A.2.1DateofthestatementA.2.2ImplementationUnderTest(IUT)identificationIUTname:.IUTversion:.SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)12A.2.3SystemUnderTest(SUT)identificationSUTname:.Hardwareconfiguration:.Operatingsystem:.A.2.4ProductsupplierName:.Address:.Telephonenumber:.Facsimilenumber:.E-mailaddress:.Additionalinformation:.A.2.5Client(ifdifferentfromproductsupplier)Name:.Address:.Telephonenumber:.Facsimilenumber:.E-mailaddress:.Additionalinformation:.SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)13A.2.6PICScontactperson(ApersontocontactifthereareanyqueriesconcerningthecontentofthePICS)Name:.Telephonenumber:.Facsimilenumber:.E-mailaddress:.Additionalinformation:.A.3IdentificationoftheProtocolThisPICSproformaappliestothefollowingstandard:EN300396-7[1]:"TerrestrialTrunkedRadio(TETRA);TechnicalrequirementsforDirectModeOperation(DMO);Part7:Type2repeaterairinterface".Thisproformacoverstwolayersoftheprotocolstack,DirectModeCallControl(DMCC)atlayer3andDataLinkLayer(DLL)atlayer2fortheDM-MSoperatingwithatype2repeater(MS-REP2),andonelayeronly(layer2)ofthetype2DM-REPprotocol(DM-REP2).EachofthesepartsisaddressedinadifferentsectionofthepresentPICS.Whensubmittinganimplementationfortest,theimplementerisrequiredtoanswerthequestionsofthesection(s)oftheproformapertainingtothepart(s)oftheprotocolsubmittedtothetest,i.e.theMS-REP2sectionand/ortheDM-REP2section.A.4GlobalstatementofconformanceAreallmandatorycapabilitiesoftheDM-MSforoperationwithatype2DM-REPimplemented?(Yes/No/(n/a))Areallmandatorycapabilitiesofthetype2RepeaterLayer2Protocolimplemented?(Yes/No/(n/a))NOTE:Answering"No"toanyofthesequestionsindicatesnon-conformancetotheProtocolspecification.Non-supportedmandatorycapabilitiesaretobeidentifiedinthePICS,withanexplanationofwhytheimplementationisnon-conforming,onpagesattachedtothePICSproforma.Answering"n/a"toanyofthesequestionsindicatesthatthequestionsrelatedtothatpartdoesnotapply.SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)14A.5RolesThesupplieroftheimplementationshallstatetheroleoftheimplementation,intableA.1.TableA.1:RolesItemRoleReferenceStatusSupport1DM-MSsupportingoperationwithatype2DM-REP(MS-REP2)4.1o.12Type2Repeater(Layer2protocolofaDM-REP2)4.1o.1o.1:Itismandatorytosupportatleastoneoftheseitems.A.6ProtocolsforDM-MSsupportingoperationwithatype2DM-REP(MS-REP2)A.6.1MS-REP2DirectModeCallControl(DMCC)atLayer3ThisclauseisderivedfromclauseA.6ofEN300396-8-2[3]whichcontainsthePICSforaDM-MSsupportingoperationwithatype1repeater(MS-REP1).Onmanyoccasions,referencesaretakenfromthisdocument,tobemorepreciseinthedescriptionoftheconformancerequirements.A.6.1.1DMCCmajorcapabilitiesThesupplieroftheMS-REP2implementationshallstatethesupportoftheimplementationforeachofthefollowingprotocolservices,intableA.2.TableA.2:DMCCservicesPrerequisite:A.1/1--MS-REP2ItemServiceReferencefrom[3]StatusSupport1Circuitmodecall6.2o.22ShortDataService(SDS)6.3o.2o.2:Itismandatorytosupportatleastoneoftheseitems.SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)15A.6.1.2CircuitmodecallThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingcircuitmodecallprotocolfeatures,intableA.3.TableA.3:CircuitmodeprotocolfeaturesPrerequisite:A.2/1--circuitmodecallItemProtocolfeaturesReferencefrom[3]StatusSupport1Groupaddresscallcapability5.2o.32Individualaddresscallcapability5.2o.33Initiatecallset-upwithoutpresencecheck6.2.1.1o4Initiatecallset-upwithpresencecheck6.2.2.1o5Acceptcallset-upwithoutpresencecheck6.2.1.2m6Acceptcallset-upwithpresencecheck6.2.2.2o7Masterendofcalltransmission6.2.4.1c3018Receiveendofcalltransmission6.2.4.2m9Mastercalltermination6.2.4.1,6.2.5.1c30110Receivecalltermination6.2.4.2,6.2.5.2m11Acceptcallpre-emption6.2.4.1,6.2.5.1c30112Initiatepre-emptioninongoingcall6.2.4.2o13Initiateanewcallbypre-emption6.2.6o14Initiatecallchange-over6.2.5.2o15Acceptcallchange-over6.2.5.1c30116Lateentrybycalledparty6.2.3.2o17ReceiveTPNIincallset-up6.2.4.3m18SuppressTPNIincallset-up6.2.4.3o19Receiveinter-MNIcall6.2.4.3m20Initiateinter-MNIcall6.2.4.3oo.3:Itismandatorytosupportatleastoneoftheseitems.c301:IFA.3/3ORA.3/4--Ifinitiationofcallset-upwithorwithoutpresencechecksupportedTHENm--thenmandatoryELSEn/aA.6.1.3Circuitmodecallset-upThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingcircuitmodecallset-upprocedures,intablesA.4toA.5.TableA.4:Circuitmodecallset-upprocedures-GroupcallPrerequisite:A.3/1ANDA.3/3--Initiategroupcallset-upItemSet-upprocedureReferencefrom[3]StatusSupport1Groupcalladdress6.2.1.1m2Callontemporarygroupaddress6.2.1.3oSIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)16TableA.5:Circuitmodecallset-upprocedures-IndividualcallPrerequisite:A.3/2--IndividualaddresscallcapabilityItemset-upprocedureReferencefrom[3]StatusSupport1Individualcallwithoutpresencecheck6.2.1.1c5012Individualcallwithpresencecheck6.2.2.1c502c501:IFA.3/3THENoELSEn/a--Ifinitiatecallset-upwithoutpresencecheckthenoptionalc502:IFA.3/4THENmELSEn/a--Ifinitiatecallset-upwithpresencecheckthenmandatoryA.6.1.4CircuitmodeservicesofferedThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingcircuitmodeservices,intableA.6TableA.6:CircuitmodeservicesofferedPrerequisite:A.2/1--circuitmodecallItemCircuitmodeserviceReferencefrom[3]StatusSupport1Circuitmodespeech:5.4o.42Circuitmodedataunprotected:7.25.4o.43Circuitmodedatalowprotection:4.8,N=15.4o.44Circuitmodedatalowprotection:4.8,N=45.4o.45Circuitmodedatalowprotection:4.8,N=85.4o.46Circuitmodedatahighprotection:2.4,N=15.4o.47Circuitmodedatahighprotection:2.4,N=45.4o.48Circuitmodedatahighprotection:2.4,N=85.4o.49Clearmodetransmission5.2o.510Endtoendencryptedtransmission5.2o.511Normalprioritycall5.4m12Highprioritycall5.4o13Pre-emptiveprioritycall5.4o14Emergencypre-emptiveprioritycall5.4o15Recentuserpriorityservice5.4oo.4:Itismandatorytosupportatleastoneoftheseitems.o.5:Itismandatorytosupportatleastoneoftheseitems.A.6.1.5ShortdataservicesThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingshortdataservices,intableA.7.TableA.7:ShortDataServicesPrerequisite:A.2/2--ShortDataServicesItemShortdataserviceReferencefrom[3]StatusSupport1Senddata(note1)6.3.1o.62Receivedata(note2)6.3.2o.63Extendederrorprotection(FCS)6.3.4mNOTE1:CapabilitytooriginateshortdatatransactionasmasterNOTE2:Capabilitytoreceiveshortdatatransactionasslaveo.6:Itismandatorytosupportatleastoneoftheseitems.SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)17A.6.1.6TypeofshortdataserviceThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingtypesofSDSs,intablesA.8toA.12.TableA.8:TypeofshortdataservicePrerequisite:A.2/2--ShortDataServicesItemTypeofshortdataserviceReferencefrom[3]StatusSupport1GroupaddressSDScapability6.3o.72IndividualaddressSDScapability6.3o.73Pre-definedshortdatamessages6.3o.84User-definedshortdatamessages6.3o.85OTAR(note)6.3o.86Enable/disable(note)6.3o.87Additionaladdressing(receive)6.3.3c8018Additionaladdressing(send)6.3.3c802NOTE:ThedetailedPICSproformaforDMOsecurityisdefinedinaseparatePICSproformacoveringsecurityaspects.o.7:Itismandatorytosupportatleastoneoftheseitems.o.8:Itismandatorytosupportatleastoneoftheseitems.c801:IFA.7/2THENmELSEn/a--IfreceiveSDSsupportedthenmandatoryc802:IFA.7/1THENoELSEn/a--IfsendSDSsupportedthenoptionalTableA.9:SendshortdataserviceongroupaddressPrerequisite:A.7/1ANDA.8/1--GroupaddressSDScapabilityItemSDSongroupaddressReferencefrom[3]StatusSupport1Unacknowledgeddataservice6.3mTableA.10:SendshortdataserviceonindividualaddressPrerequisite:A.7/1ANDA.8/2--IndividualaddressSDScapabilityItemSDSonindividualaddressReferencefrom[3]StatusSupport1Unacknowledgeddataservice6.3o.92Acknowledgeddataservice6.3o.93ExtractionofdataifincludedinACK6.3c1001o.9:Itismandatorytosupportatleastoneoftheseitems.c1001:IFA.10/2--IfthesendingofacknowledgedshortdataservicesupportedTHENm--thenmandatoryELSEn/aTableA.11:ReceiveshortdataserviceongroupaddressPrerequisite:A.7/2ANDA.8/1--GroupaddressSDScapabilityItemSDSongroupaddressReferencefrom[3]StatusSupport1Unacknowledgeddataservice6.3mSIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)18TableA.12:ReceiveshortdataserviceonindividualaddressPrerequisite:A.7/2ANDA.8/2--IndividualaddressSDScapabilityItemSDSonindividualaddressReferencefrom[3]StatusSupport1Unacknowledgeddataservice6.3o.102Acknowledgeddataservice6.3o.103IncludingdatainACK6.3oo.10:Itismandatorytosupportatleastoneoftheseitems.A.6.1.7DatatransmissionThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingservicesforsendingdata,intableA.13.TableA.13:SendingdataservicesPrerequisite:A.7/1--SenddatausingSDSItemSenddataReferencefrom[3]StatusSupport1Sendshortdataonafreechannel6.3.1.1m2Sendshortdataafterpre-emptionofacircuitmodecall(newcall)6.3.1.2o3Sendshortdatastealingfromcircuitmodetransmission6.3.1.3c13014Sendshortdataafterpre-emptionofacircuitmodecall(ongoingcall)6.3.1.4.1c13025Sendshortdataafterchangeoverofacircuitmodecall6.3.1.4.2c13026Sendshortdataasmasterofacircuitmodecall6.3.1.4.3c1302c1301:IFA.3/3ORA.3/4--IfinitiateCMcallset-upsupportedTHENo--thenoptionalELSEn/ac1302:IFA.2/1--IfCMcallsupportedthenoptionalTHENoELSEn/aA.6.1.8SDSuserdefineddataThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingtypesofSDSs,intableA.14.TableA.14:SDSuserdefineddataPrerequisite:A.8/4--UserdefinedshortdataItemCircuitmodeserviceReferencefrom[3]StatusSupport1Userdefineddata1(16bits)5.4o.112Userdefineddata2(32bits)5.4o.113Userdefineddata3(64bits)5.4o.114Userdefineddata4(upto2047bits)5.4o.11o.11:Itismandatorytosupportatleastoneoftheseitems.SIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)19A.6.1.9DMCCPDUsThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingcircuitmodeandSDSPDUs,intablesA.15toA.16.TableA.15:CircuitModecallandpre-emptionPDUsItemPDUReferenceSendingReceivingfromETS300396-3[2]StatusSupportStatusSupport1DM-SETUP9.5.1c1501c15022DM-SETUPPRES9.5.2c1503c15043DM-CONNECT9.5.3c1504c15034DM-DISCONNECT9.5.4c1504c15035DM-CONNECTACK9.5.5c1503c15046DM-OCCUPIED9.5.6c1505c15027DM-RELEASE9.5.7c1505c15028DM-TXCEASED9.5.8c1505c15029DM-TXREQUEST9.5.9c1506c150510DM-TXACCEPT9.5.10c1505c151211DM-PREEMPT9.5.11c1507c151112DM-PREACCEPT9.5.12c1511c151313DM-REJECT9.5.13c1509c151014DM-INFO9.5.14c1508c1502c1501:IFA.3/1ORA.5/1--Ifgroupcallorindividualcallset-upwithoutpresencecheckTHENm--supportedthenmandatoryELSEn/ac1502:IFA.2/1--IfcircuitmodecallsupportedTHENm--thenmandatoryELSEn/ac1503:IFA.5/2--Ifindividualcallset-upwithpresencechecksupportedTHENm--thenmandatoryELSEn/ac1504:IFA.3/6--Ifacceptofcallset-upwithpresencechecksupportedTHENm--thenmandatoryELSEn/ac1505:IFA.3/3ORA.3/4--Ifinitiatecallset-upwithorwithoutpresencechecksupportedTHENm--thenmandatoryELSEn/ac1506:IFA.3/14ORA.13/5--IfCMorSDScallchangeoversupportedTHENm--thenmandatoryELSEn/ac1507:IFA.3/10ORA.3/13--IfinitiationofCMorSDSpre-emptionissupportedORA.13/2ORA.13/4THENm--thenmandatoryELSEn/ac1508:IFA.3/18--IfsendingofTPNIcanbesuppressedthenTHENm--mandatoryelseELSEo--optionalc1509:IFA.3/3ORA.3/4--IfinitiateCMcallsupportedTHENm--thenmandatoryELSEIFA.12/2ORA.12/3--IfreceiveacknowledgedSDSsupportedTHENo--thenoptionalELSEn/ac1510:IFA.2/1OR--IfcircuitmodecallorsendacknowledgedshortdataA.10/2ORA.10/3--supportedTHENm--thenmandatoryELSEn/aSIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)20c1511:IFA.3/3OR--IfinitiationofCMorSDScallA.3/4ORA.7/1--supportedTHENm--thenmandatoryELSEn/ac1512:IFA.2/1ORA.13/5--IfcircuitmodecallorsendSDSafterchangeoversupportedTHENm--thenmandatoryELSEn/ac1513:IFA.2/1ORA.13/2--IfcircuitmodecallorsendSDSafterpre-emptionsupportedORA.13/4THENm--thenmandatoryELSEn/aTableA.16:SpecificSDSPDUsPrerequisite:A.2/2--ShortDataServicesItemPDUReferenceSendingReceivingfromdocument[2]StatusSupportStatusSupport1DM-SDSUDATA9.5.15c1601c16032DM-SDSDATA9.5.16c1602c16043DM-SDSACK9.5.17c1604c1602c1601:IFA.9/1ORA.10/1--IfsendingofunacknowledgedSDSwithgrouporindividualaddressTHENm--supportedthenmandatoryELSEn/ac1602:IFA.10/2ORA.10/3--IfsendingofacknowledgeddataservicewithorwithoutdatainTHENm--ACKsupportedthenmandatoryELSEn/ac1603:IFA.11/1ORA.12/1--IfreceivingofunacknowledgedsupportedTHENm--thenmandatoryELSEn/ac1604:IFA.12/2ORA.12/3--IfreceivingofacknowledgeddataservicesupportedTHENm--thenmandatoryELSEn/aSIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)21A.6.1.10DMCCconstantsThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingDMCCconstants,intableA.17.TableA.17:DMCCconstantsItemConstantsReferencefrom[3]StatusSupportValuerangesAllowedSupported1DN303--DM-SETUPPRES--retriesA.2c17011.32DN314--DM-SDSUDATA--retriesA.2c17021.63DN315--DM-SDSDATA--retrieson--negativeresponseA.2c17032.64DN316--DM-SDSDATA--retriesonno--responseA.2c17031.45DN304--DM-SETUPorDM---SETUPPRES--retriesonDM---REP2linkfailureA.2c17041.36DN317--DM-SDSDATAor--DM-SDSUDATA--retriesonDM---REP2linkfailureA.2c17051.3c1701:IFA.5/2THENmELSEn/a--Ifcallset-upwithpresencechecksupportedthen--mandatoryc1702:IFA.9/1ORA.10/1--IfunacknowledgedSDSsupportedforTHENmELSEn/a--grouporindividualaddressthenmandatoryc1703:IFA.10/2ORA.10/3--IfacknowledgedSDSsupportedwithorwithoutTHENmELSEn/a--datainACKthenmandatoryc1704:IFA.2/3ORA.2/4--Ifinitiatecallset-upwithoutpresenceORwithpresencecheckTHENmELSEn/a--thenmandatoryc1705:IFA.6/1THENm--IfSendDatathenmandatoryELSEn/aSIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)22A.6.1.11DMCCtimersThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingDMCCtimers,intableA.18.TableA.18:DMCCtimersItemTimerReferencefrom[3]StatusSupportValuesDefaultSupported1DT303--WaitDM---SETUP--PRES--responseA.1c1801250--mSec2DT307--WaitDM---CONNECT--ACKA.1c1802350--mSec3DT311--Call--transaction--timeA.1c1803300--Sec4DT314--SDSfailure--timerA.1c1804500--mSec5DT316--WaitDM---SDSDATA--responseA.1c1805400--mSecc1801:IFA.3/4--Ifinitiationofcallset-upwithpresencechecksupportedTHENm--thenmandatoryELSEn/ac1802:IFA.3/6--Ifacceptcallset-upwithpresencechecksupportedTHENm--thenmandatoryELSEn/ac1803:IFA.3/3ORA.3/4--IfinitiateCMcallset-upsupportedTHENm--thenmandatoryELSEn/ac1804:IFA.7/1--IfSDSsenddatasupportedTHENm--thenmandatoryELSEn/ac1805:IFA.10/2ORA.10/3--IfacknowledgedSDSsupportedwithorwithoutTHENm--datainACK.thenmandatoryELSEn/aSIST EN 300 396-8-4 V1.1.1:2003

ETSIETSIEN300396-8-4V1.1.1(2001-01)23A.6.2MS-REP2Datalinklayer(DLL)atLayer2A.6.2.1MS-REP2MACfeaturesThesupplieroftheimplementationshallstatethesupportoftheimplementationforeachofthefollowingMS-REP2MACfeatures,intableA.19.TableA.19:MS-REP2MACfeaturesPrereq
...