ETSI ETS 300 938 ed.5 (2000-09)

Digital cellular telecommunications system (Phase 2+) (GSM); Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification (GSM 04.06 version 5.4.1 Release 1996)

RE/SMG-030406QR3

Digitalni celični telekomunikacijski sistem (faza 2+) – Mobilna postaja – Vmesnik sistema bazne postaje (MS-BSS) – Specifikacija podatkovne povezovalne plasti (GSM 04.06, različica 5.4.1, izdaja 1996)

General Information

• Status: Published
• Publication Date: 06-Sep-2000
• Technical Committee: SMG 3 - Network Aspects
• Current Stage: 12 - Completion
• Due Date: 28-Jul-2000
• Completion Date: 07-Sep-2000
• Ref Project: SIST ETS 300 938 E5:2003 - Digital cellular telecommunications system (Phase 2+) (GSM); Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification (GSM 04.06 version 5.4.1 Release 1996)

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital cellular telecommunications system (Phase 2+) (GSM); Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification (GSM 04.06 version 5.4.1 Release 1996)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)ICS:Ta slovenski standard je istoveten z:ETS 300 938 Edition 5SIST ETS 300 938 E5:2003en01-december-2003SIST ETS 300 938 E5:2003SLOVENSKI
STANDARD



SIST ETS 300 938 E5:2003



EUROPEANETS300938TELECOMMUNICATIONAugust2000STANDARDFifthEditionSource:SMGReference:RE/SMG-030406QR3ICS:33.020Keywords:Digitalcellulartelecommunicationssystem,GlobalSystemforMobilecommunications(GSM)GLOBALSYSTEMFORMOBILECOMMUNICATIONSRDigitalcellulartelecommunicationssystem(Phase2+);MobileStation-BaseStationSystem(MS-BSS)interface;DataLink(DL)layerspecification(GSM04.06version5.4.1Release1996)ETSIEuropeanTelecommunicationsStandardsInstituteETSISecretariatPostaladdress:F-06921SophiaAntipolisCEDEX-FRANCEOfficeaddress:650RoutedesLucioles-SophiaAntipolis-Valbonne-FRANCEInternet:[e-mail]-http://www.etsi.orgTel.:[phone]-Fax:[phone]CopyrightNotification:Nopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST ETS 300 938 E5:2003



Page2ETS300938(GSM04.06version5.4.1Release1996):August2000Whilsteverycarehasbeentakeninthepreparationandpublicationofthepresentdocument,errorsincontent,typographicalorotherwise,mayoccur.Ifyouhavecommentsconcerningitsaccuracy,pleasewriteto"ETSIStandardsMakingSupportDept."attheaddressshownonthetitlepage.SIST ETS 300 938 E5:2003



Page3ETS300938(GSM04.06version5.4.1Release1996):August2000ContentsIntellectualPropertyRights.7Foreword.70Scope.90.1Normativereferences.90.2Abbreviations.91General.101.1Options.102Framestructureforpeer-to-peercommunication.112.1General.112.2Framedelimitationandfillbits.132.3Addressfield.142.4Controlfield.142.5Lengthindicatorfield.142.5aShortL2headertype1.142.6Informationfield.142.7Transparency.142.8Formatconvention.142.8.1Numberingconvention.142.8.2Orderofbittransmission.152.8.3Fieldmappingconvention.153ElementsofproceduresandformatsoffieldsforDataLinkLayerpeer-to-peercommunication.153.1General.153.2Addressfieldformat.163.3Addressfieldvariables.163.3.1Addressfieldextensionbit(EA).163.3.2Command/responsefieldbit(C/R).163.3.3Serviceaccesspointidentifier(SAPI).163.4Controlfieldformats.173.4.1Informationtransferformat-I.173.4.2Supervisoryformat-S.173.4.3Unnumberedformat-U.173.4aShortL2headertype1.183.5Controlfieldparametersandassociatedstatevariables.183.5.1Poll/Finalbit.183.5.2Multipleframeoperation-variablesandsequencenumbers.183.5.2.1Modulus.183.5.2.2SendstatevariableV(S).183.5.2.3AcknowledgestatevariableV(A).183.5.2.4SendsequencenumberN(S).193.5.2.5ReceivestatevariableV(R).193.5.2.6ReceivesequencenumberN(R).193.5.2.7Otherparametersandvariables.193.5.3Unacknowledgedoperationvariablesandparameters.193.6Lengthindicatorfieldformat.193.7Lengthindicatorfieldvariables.203.7.1Lengthindicatorfieldextensionbit(EL).203.7.2Moredatabit(M).203.7.3Lengthindicator(L).203.8Commandsandresponses.203.8.1Information(I)commands.203.8.2Setasynchronousbalancedmode(SABM)command.21SIST ETS 300 938 E5:2003



Page4ETS300938(GSM04.06version5.4.1Release1996):August20003.8.3Disconnect(DISC)command.223.8.4Unnumberedinformation(UI)command.223.8.5Receiveready(RR)command/response.223.8.6Reject(REJ)command/response.233.8.7Receivenotready(RNR)command/response.233.8.8Unnumberedacknowledgement(UA)response.233.8.9Disconnectedmode(DM)response.234Elementsforlayer-to-layercommunication.244.1Definitionofprimitivesandparameters.244.1.1Genericnames.244.1.1.1DL-ESTABLISH.244.1.1.2DL-RELEASE.244.1.1.3DL-DATA.244.1.1.4DL-UNITDATA.244.1.1.5DL-SUSPEND.244.1.1.6DL-RESUME.244.1.1.7DL-RECONNECT.254.1.1.8DL-RANDOMACCESS.254.1.1.9MDL-RELEASE.254.1.1.10MDL-ERROR.254.1.1.11PH-DATA.254.1.1.12PH-RANDOMACCESS.254.1.1.13PH-CONNECT.254.1.1.14PH-READY-TO-SEND.254.1.1.15PH-EMPTY-FRAME.254.1.2Primitivestypes.254.1.2.1REQUEST.254.1.2.2INDICATION.264.1.2.3RESPONSE.264.1.2.4CONFIRM.264.1.3Parameterdefinition.264.1.3.1Messageunit.264.1.3.2Channeltype.274.1.3.3ServiceAccessPoint.274.1.3.4Releasemode.274.1.3.5Errorcause.274.1.3.6Establishmode.274.1.3.7L2headertype.274.2Primitiveprocedures.315Definitionofthepeer-to-peerprotocolLAPDm.325.1General.325.2GeneralProtocolProcedures.335.2.1Unacknowledgedinformationtransfer.335.2.2Acknowledgedmultipleframeinformationtransfer.335.3Proceduresforunacknowledgedinformationtransfer.335.3.1General.335.3.2Transmissionofunacknowledgedinformation.335.3.3Receiptofunacknowledgedinformation.335.4Proceduresforestablishmentandreleaseofmultipleframeoperation.345.4.1Establishmentofmultipleframeoperation.345.4.1.1General.345.4.1.2Normalestablishmentprocedures.345.4.1.3ProcedureonexpiryoftimerT200:Normalestablishment355.4.1.4Contentionresolutionestablishmentprocedure.355.4.1.5ProcedureonexpiryoftimerT200:contentionresolution(MSonly).375.4.2Informationtransfer.375.4.2.1Generalrequirements.375.4.2.2Errorconditions.385.4.2.3Fillframes.395.4.3Suspensionandresumptionofmultipleframeoperation.39SIST ETS 300 938 E5:2003



Page5ETS300938(GSM04.06version5.4.1Release1996):August20005.4.3.1General.395.4.3.2Suspension.405.4.3.3Resumption.405.4.3.3.1Procedureafterchannelchange.405.4.3.3.2Procedureafterreturningtotheoldchannel(MSonly).415.4.4Terminationofmultipleframeoperation.425.4.4.1General.425.4.4.2Normalreleaseprocedure.425.4.4.3ProcedureonexpiryoftimerT200fornormalrelease.425.4.4.4Localendreleaseprocedure.435.4.5Idlestate.435.4.6Collisionofunnumberedcommandsandresponses.435.4.6.1Identicaltransmittedandreceivedcommands.435.4.6.2Differenttransmittedandreceivedcommands.445.4.6.3UnsolicitedDMresponseandSABMorDISCcommand.445.5Proceduresforinformationtransferinmultipleframeoperation.445.5.1TransmittingIframes.445.5.2ReceivingIframes.455.5.2.1PbitofthereceivedIframesetto"1".455.5.2.2PbitofthereceivedIframesetto"0".455.5.3Receivingacknowledgement.465.5.3.1OnreceiptofavalidIframe.465.5.3.2ReceivingsupervisorycommandframeswiththePbitsetto"1".465.5.4ReceivingREJframes.465.5.4.1ReceiptofavalidREJframe.465.5.4.2Transmittingframes.475.5.5ReceivingRNRframe.475.5.6Datalinklayerownreceiverbusycondition.495.5.7Waitingacknowledgement.495.6Abnormalreleaseandre-establishmentofmultipleframeoperation.505.6.1Criteriaforre-establishment.505.6.2Criteriaforabnormalrelease.505.6.3Proceduresforre-establishment.505.6.4Proceduresforabnormalrelease.505.7Exceptionconditionreportingandrecoveryformultipleframeoperation.515.7.1N(S)sequenceerror.515.7.2Timerrecovery.515.7.3Invalidframecondition.525.7.4N(R)sequenceerror.525.8Listofsystemparameters.525.8.1TimerT200.525.8.1.1ForSAPI=0andSAPI=3.525.8.1.2ForSAPIsotherthan0or3.535.8.2Maximumnumberofretransmissions(N200).535.8.2.1ForSAPI=0and3.535.8.2.2ForSAPIsotherthan0or3.535.8.3MaximumnumberofoctetsinanI,UI,SABMandUAframepartiallyorentirelyavailablefortheinformationfield(N201).535.8.4MaximumnumberofoutstandingIframes(k).535.8.5MaximumnumberofoctetsinaLayer3message.545.9Systemperformancerequirements.546SpecialprotocoloperationonSAPI=0andSAPI=3.55AnnexA(normative):Randomaccessprocedures.56A.1Descriptionoftheprocedure.56A.1.1ProcedureintheMS.56A.1.2ProcedureintheBS.56A.2Format.56SIST ETS 300 938 E5:2003



Page6ETS300938(GSM04.06version5.4.1Release1996):August2000AnnexG(normative):Handlingofframeswithparametererrorsintheaddress,controlandlengthindicatorfields.57G.1General.57G.2Parametererrorsintheaddressfield.57G.2.1UnallocatedSAPI.57G.2.2WrongvalueoftheC/Rbit.57G.2.3EAbitsetto"0".57G.3Parametererrorsinthecontrolfield.57G.3.1Supervisoryframes.57G.3.2Unnumberedframes.58G.4Parametererrorsinthelengthindicatorfield.58G.4.1ELbiterror.58G.4.2Informationframes.58G.4.3Supervisoryframes.58G.4.4DISCandDMframes.58G.4.5SABMUAandUIframes.58AnnexH(informative):Documentchangehistory.59History.60SIST ETS 300 938 E5:2003



Page7ETS300938(GSM04.06version5.4.1Release1996):August2000IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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.ForewordThisEuropeanTelecommunicationStandard(ETS)hasbeenproducedbyETSITechnicalCommitteeSpecialMobileGroup(SMG).ThisETSdefinesthedatalinklayerprotocoloftheMobileStation-BaseStationSystem(MS-BSS)interfacewithinthedigitalcellulartelecommunicationssystem.ThecontentsofthepresentdocumentmaybesubjecttocontinuingworkwithinSMGandmaychangefollowingformalSMGapproval.ShouldSMGmodifythecontentsofthepresentdocumentitwillthenbere-submittedforformalapprovalproceduresbyETSIwithanidentifyingchangeofreleasedateandanincreaseinversionnumberasfollows:Version5.x.ywhere:5GSMPhase2+Release1996.xtheseconddigitisincrementedforchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.;ythethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthespecification.ThespecificationfromwhichthisETShasbeenderivedwasoriginallybasedonCEPTdocumentation,hencethepresentationofthisETSmaynotbeentirelyinaccordancewiththeETSIdraftingrules.AnnexesBtoFweredeletedfromtheoriginalspecification,however,forreferencingpurposestheannexnumberinghasbeenmaintained.TranspositiondatesDateofadoptionofthisETS:21July2000DateoflatestannouncementofthisETS(doa):31October2000DateoflatestpublicationofnewNationalStandardorendorsementofthisETS(dop/e):30April2001DateofwithdrawalofanyconflictingNationalStandard(dow):30April2001SIST ETS 300 938 E5:2003



Page8ETS300938(GSM04.06version5.4.1Release1996):August2000BlankpageSIST ETS 300 938 E5:2003



Page9ETS300938(GSM04.06version5.4.1Release1996):August20000ScopeThisEuropeanTelecommunicationStandard(ETS)definesadatalinklayerprotocoltobeusedforsignalling,andpossiblyalsoforotherapplications,ontheMS-BSinterface.0.1NormativereferencesThisETSincorporatesbydatedandundatedreference,provisionsfromotherpublications.Thesenormativereferencesarecitedattheappropriateplacesinthetextandthepublicationsarelistedhereafter.Fordatedreferences,subsequentamendmentstoorrevisionsofanyofthesepublicationsapplytothisETSonlywhenincorporatedinitbyamendmentorrevision.Forundatedreferences,thelatesteditionofthepublicationreferredtoapplies.[1]GSM01.04(ETR350):"Digitalcellulartelecommunicationssystem(Phase2+);Abbreviationsandacronyms".[2]GSM04.01:"Digitalcellulartelecommunicationssystem;MobileStation-BaseStationSystem(MS-BSS)interface;Generalaspectsandprinciples".[3]GSM04.03:"Digitalcellulartelecommunicationssystem(Phase2+);MobileStation-BaseStationSystem(MS-BSS)interfaceChannelstructuresandaccesscapabilities".[4]GSM04.04(ETS300936):"Digitalcellulartelecommunicationssystem;Layer1Generalrequirements".[5]GSM04.05(ETS300937):"Digitalcellulartelecommunicationssystem;DataLink(DL)layerGeneralaspects".[6]GSM04.07(ETS300939):"Digitalcellulartelecommunicationssystem(Phase2+);Mobileradiointerfacesignallinglayer3;Generalaspects".[7]GSM04.08(ETS300940):"Digitalcellulartelecommunicationssystem(Phase2+);Mobileradiointerfacelayer3specification".[8]GSM04.10(ETS300941):"Digitalcellulartelecommunicationssystem;Mobileradiointerfacelayer3Supplementaryservicesspecification;Generalaspects".[9]GSM04.12(ETS300943):"Digitalcellulartelecommunicationssystem(Phase2+);ShortMessageServiceCellBroadcast(SMSCB)supportonthemobileradiointerface".[10]GSM05.02(ETS300908):"Digitalcellulartelecommunicationssystem(Phase2+);Multiplexingandmultipleaccessontheradiopath".[11]GSM08.56:"Digitalcellulartelecommunicationssystem;BaseStationController-BaseTransceiverStation(BSC-BTS)interface;Layer2specification".[12]GSM08.58:"Digitalcellulartelecommunicationssystem(Phase2+);BaseStationController-BaseTransceiverStation(BSC-BTS)interface;Layer3specification".[13]CCITTRecommendationZ.100:"Specificationanddescriptionlanguage(SDL)".0.2AbbreviationsAbbreviationsusedinthisETSarelistedinGSM01.04.SIST ETS 300 938 E5:2003



Page10ETS300938(GSM04.06version5.4.1Release1996):August20001GeneralThisETSdescribestheframestructure,elementsofprocedure,formatoffieldsandproceduresfortheproperoperationoftheLinkAccessProcedureontheDmchannel,LAPDm.NOTE1:ThetermDmchannelisusedforconveniencetodesignatethecollectionofallthevarioussignallingchannelsrequiredintheGSMsystem.SeealsoGSM04.03.Theconcepts,terminology,overviewdescriptionofLAPDmfunctionsandprocedures,andtherelationshipwithotherTechnicalSpecificationsaredescribedingeneraltermsinGSM04.05.TheframeformatsdefinedforLAPDmarebasedonthosedefinedforLAPD.However,thereareimportantdifferencesbetweenLAPDmandLAPD,inparticularwithregardtoframedelimitationmethodsandtransparencymechanisms.Thesedifferencesarenecessaryforoperationwithintheconstraintssetbytheradiopath.LAPDmsupportstwomodesofoperation:-unacknowledgedoperationusingUIframes;-acknowledgedoperationusingthemultipleframeprocedure.Asachoiceofimplementation,thetwomodesofoperationmaybeimplementedindependentlyofeachother.Thisispossiblesincethereisnointeractionsbetweenthetwomodes,otherthanqueuingatthetransmitter,evenwhentheycoexistonthesamephysicalchannel.ForBCCHsandCCCHsonlytheunacknowledgedmodeofoperationneedstobeimplemented.LAPDmisusedforinformationsentonthecontrolchannelsBCCH,AGCH,NCH,PCH,FACCH,SACCHandSDCCHasdefinedinGSM04.03.NOTE2:AGCH,NCHandPCHaresometimesreferredtobythecollectivenameCCCHandFACCH,SACCHandSDCCHare,similarly,referredtobythecollectivenameDCCH.LAPDmmayalsobeusedonothertypesofchannel.NOTE3:AsstatedinGSM04.05,theterm"datalinklayer"isusedinthemaintextofthisTechnicalSpecification.However,mainlyinfiguresandtables,theterms"layer2"and"L2"areusedasabbreviations.Furthermore,inaccordancewithGSM04.07andGSM04.08,theterm"layer3"isusedtoindicatethelayerabovethedatalinklayer.ThisTechnicalSpecificationisorganizedasfollows:Theframestructureforpeer-to-peercommunicationisgiveninclause2.Theelementsofprocedureandformatsoffieldsaregiveninclause3.Theelementsoflayer-to-layercommunicationarecontainedinclause4.Thedetailsofthepeer-to-peerproceduresaregiveninclause5.Section6summarizesthespecialprotocoloperationsusedmandatorilywithSAPI=0andSAP=3.ThespecificationfortherandomaccesschanneliscontainedinannexA,eventhoughitisnotaLAPDmfunction.ThispartoftheETSisdescriptiveanddoesnotconstraintheimplementationoftherandomaccessfunction.TheprocedureisusedforCHANNELREQUESTontheRACHandHANDOVERACCESSonthemainDCCH.(AnnexesBtoFaredeleted).AnnexGgivesanoverviewofactionstakenonframescontainingparametererrors.1.1OptionsSupportofshortL2headertype1isanoptioninboththemobilestationandthenetwork;undercertainconditionsthesupportismandatory,asspecifiedinotherSpecifications.Alayer2protocolentitynotimplementingshortL2headertype1shalldiagnoseanE/AbiterrorandproceedasdefinedinannexG.2.3.SIST ETS 300 938 E5:2003



Page11ETS300938(GSM04.06version5.4.1Release1996):August20002Framestructureforpeer-to-peercommunication2.1GeneralAlldatalinklayerpeer-to-peerexchangesareinframesconformingtooneoftheformatsshowninfigure1.Severalformattypesareshowninthefigure:-FormatAisusedonDCCHsforframeswherethereisnoinformationfield.-FormatsB,BterandB4areusedonDCCHsforframescontaininganinformationfield:-formatBterisusedonrequestofhigherlayersifandonlyifshortL2headertype1issupportedandaUIcommandistobetransmittedonSAPI0;-formatB4isusedforUIframestransmittedbythenetworkonSACCH;-formatBisappliedinallothercases.-FormatBbisisusedonlyonBCCH,PCH,NCH,andAGCH.-InadditionthereisaFormatCfortransmissionofrandomaccesssignals.FormatCframesaredescribedinannexA.FormatA,B,Bbis,BterandB4framesaredescribedintheremainderofthisETS.Bit87654321OctetNo1:Addressfield:kControlfieldk+1k+2:Lengthindicatorfield:nn+1:Fillbits:N201+nFormattypeAFigure1/GSM04.06(sheet1of3):GeneralframeformatsSIST ETS 300 938 E5:2003



Page12ETS300938(GSM04.06version5.4.1Release1996):August2000Bit87654321OctetNo1:Addressfield:kControlfieldk+1k+2:Lengthindicatorfield:nn+1:Informationfiel
...