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

CR SMG#31

Digitalni celični telekomunikacijski sistem (faza 2+) – Mobilna postaja – Vmesnik sistema baznih postaj (MS-BSS) – Specifikacija podatkovne povezovalne (DL) plasti (GSM 04.06, različica 6.2.1, izdaja 1997)

General Information

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
EN 300 938 V6.2.1:2003
English language
58 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

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 6.2.1 Release 1997)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)ICS:Ta slovenski standard je istoveten z:EN 300 938 Version 6.2.1SIST EN 300 938 V6.2.1:2003en01-december-2003SIST EN 300 938 V6.2.1:2003SLOVENSKI
STANDARD



SIST EN 300 938 V6.2.1:2003



ETSIEN300938V6.2.1(2000-09)EuropeanStandard(Telecommunicationsseries)Digitalcellulartelecommunicationssystem(Phase2+);MobileStation-BaseStationSystem(MS-BSS)interface;DataLink(DL)layerspecification(GSM04.06version6.2.1Release1997)GLOBALSYSTEMFORMOBILECOMMUNICATIONSRSIST EN 300 938 V6.2.1:2003



ETSIETSIEN300938V6.2.1(2000-09)2(GSM04.06version6.2.1Release1997)ReferenceREN/SMG-020406Q6R2KeywordsDigitalcellulartelecommunicationssystem,GlobalSystemforMobilecommunications(GSM)ETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:+33492944200Fax:+33493654716SiretN°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:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 938 V6.2.1:2003



ETSIETSIEN300938V6.2.1(2000-09)3(GSM04.06version6.2.1Release1997)ContentsIntellectualPropertyRights.7Foreword.70Scope.80.1References.80.2Abbreviations.81General.91.1Options.92Framestructureforpeer-to-peercommunication.102.1General.102.2Framedelimitationandfillbits.122.3Addressfield.132.4Controlfield.132.5Lengthindicatorfield.132.5aShortL2headertype1.132.6Informationfield.132.7Transparency.132.8Formatconvention.132.8.1Numberingconvention.132.8.2Orderofbittransmission.142.8.3Fieldmappingconvention.143ElementsofproceduresandformatsoffieldsforDataLinkLayerpeer-to-peercommunication.143.1General.143.2Addressfieldformat.143.3Addressfieldvariables.153.3.1Addressfieldextensionbit(EA).153.3.2Command/responsefieldbit(C/R).153.3.3Serviceaccesspointidentifier(SAPI).153.4Controlfieldformats.163.4.1Informationtransferformat-I.163.4.2Supervisoryformat-S.163.4.3Unnumberedformat-U.163.4aShortL2headertype1.173.5Controlfieldparametersandassociatedstatevariables.173.5.1Poll/Finalbit.173.5.2Multipleframeoperation-variablesandsequencenumbers.173.5.2.1Modulus.173.5.2.2SendstatevariableV(S).173.5.2.3AcknowledgestatevariableV(A).173.5.2.4SendsequencenumberN(S).183.5.2.5ReceivestatevariableV(R).183.5.2.6ReceivesequencenumberN(R).183.5.2.7Otherparametersandvariables.183.5.3Unacknowledgedoperationvariablesandparameters.183.6Lengthindicatorfieldformat.183.7Lengthindicatorfieldvariables.193.7.1Lengthindicatorfieldextensionbit(EL).193.7.2Moredatabit(M).193.7.3Lengthindicator(L).193.8Commandsandresponses.193.8.1Information(I)commands.193.8.2Setasynchronousbalancedmode(SABM)command.203.8.3Disconnect(DISC)command.203.8.4Unnumberedinformation(UI)command.213.8.5Receiveready(RR)command/response.21SIST EN 300 938 V6.2.1:2003



ETSIETSIEN300938V6.2.1(2000-09)4(GSM04.06version6.2.1Release1997)3.8.6Reject(REJ)command/response.213.8.7Receivenotready(RNR)command/response.213.8.8Unnumberedacknowledgement(UA)response.223.8.9Disconnectedmode(DM)response.224Elementsforlayer-to-layercommunication.224.1Definitionofprimitivesandparameters.224.1.1Genericnames.224.1.1.1DL-ESTABLISH.224.1.1.2DL-RELEASE.234.1.1.3DL-DATA.234.1.1.4DL-UNITDATA.234.1.1.5DL-SUSPEND.234.1.1.6DL-RESUME.234.1.1.7DL-RECONNECT.234.1.1.8DL-RANDOMACCESS.234.1.1.9MDL-RELEASE.234.1.1.10MDL-ERROR.234.1.1.11PH-DATA.234.1.1.12PH-RANDOMACCESS.244.1.1.13PH-CONNECT.244.1.1.14PH-READY-TO-SEND.244.1.1.15PH-EMPTY-FRAME.244.1.2Primitivestypes.244.1.2.1REQUEST.244.1.2.2INDICATION.244.1.2.3RESPONSE.244.1.2.4CONFIRM.244.1.3Parameterdefinition.254.1.3.1Messageunit.254.1.3.2Channeltype.254.1.3.3ServiceAccessPoint.254.1.3.4Releasemode.264.1.3.5Errorcause.264.1.3.6Establishmode.264.1.3.7L2headertype.264.2Primitiveprocedures.305Definitionofthepeer-to-peerprotocolLAPDm.305.1General.305.2GeneralProtocolProcedures.315.2.1Unacknowledgedinformationtransfer.315.2.2Acknowledgedmultipleframeinformationtransfer.325.3Proceduresforunacknowledgedinformationtransfer.325.3.1General.325.3.2Transmissionofunacknowledgedinformation.325.3.3Receiptofunacknowledgedinformation.325.4Proceduresforestablishmentandreleaseofmultipleframeoperation.325.4.1Establishmentofmultipleframeoperation.325.4.1.1General.325.4.1.2Normalestablishmentprocedures.335.4.1.3ProcedureonexpiryoftimerT200:Normalestablishment.345.4.1.4Contentionresolutionestablishmentprocedure.345.4.1.5ProcedureonexpiryoftimerT200:contentionresolution(MSonly).355.4.2Informationtransfer.365.4.2.1Generalrequirements.365.4.2.2Errorconditions.365.4.2.3Fillframes.375.4.3Suspensionandresumptionofmultipleframeoperation.375.4.3.1General.375.4.3.2Suspension.385.4.3.3Resumption.38SIST EN 300 938 V6.2.1:2003



ETSIETSIEN300938V6.2.1(2000-09)5(GSM04.06version6.2.1Release1997)5.4.3.3.1Procedureafterchannelchange.385.4.3.3.2Procedureafterreturningtotheoldchannel(MSonly).395.4.4Terminationofmultipleframeoperation.395.4.4.1General.395.4.4.2Normalreleaseprocedure.395.4.4.3ProcedureonexpiryoftimerT200fornormalrelease.405.4.4.4Localendreleaseprocedure.405.4.5Idlestate.405.4.6Collisionofunnumberedcommandsandresponses.415.4.6.1Identicaltransmittedandreceivedcommands.415.4.6.2Differenttransmittedandreceivedcommands.415.4.6.3UnsolicitedDMresponseandSABMorDISCcommand.415.5Proceduresforinformationtransferinmultipleframeoperation.415.5.1TransmittingIframes.415.5.2ReceivingIframes.425.5.2.1PbitofthereceivedIframesetto"1".425.5.2.2PbitofthereceivedIframesetto"0".425.5.3Receivingacknowledgement.435.5.3.1OnreceiptofavalidIframe.435.5.3.2ReceivingsupervisorycommandframeswiththePbitsetto"1".435.5.4ReceivingREJframes.435.5.4.1ReceiptofavalidREJframe.435.5.4.2Transmittingframes.445.5.5ReceivingRNRframe.445.5.6Datalinklayerownreceiverbusycondition.465.5.7Waitingacknowledgement.465.6Abnormalreleaseandre-establishmentofmultipleframeoperation.475.6.1Criteriaforre-establishment.475.6.2Criteriaforabnormalrelease.475.6.3Proceduresforre-establishment.475.6.4Proceduresforabnormalrelease.475.7Exceptionconditionreportingandrecoveryformultipleframeoperation.485.7.1N(S)sequenceerror.485.7.2Timerrecovery.485.7.3Invalidframecondition.485.7.4N(R)sequenceerror.495.8Listofsystemparameters.495.8.1TimerT200.495.8.1.1ForSAPI=0andSAPI=3.495.8.1.2ForSAPIsotherthan0or3.495.8.2Maximumnumberofretransmissions(N200).505.8.2.1ForSAPI=0and3.505.8.2.2ForSAPIsotherthan0or3.505.8.3MaximumnumberofoctetsinanI,UI,SABMandUAframepartiallyorentirelyavailablefortheinformationfield(N201).505.8.4MaximumnumberofoutstandingIframes(k).505.8.5MaximumnumberofoctetsinaLayer3message.505.9Systemperformancerequirements.516SpecialprotocoloperationonSAPI=0andSAPI=3.52AnnexA(normative):Randomaccessprocedures.53A.1Descriptionoftheprocedure.53A.1.1ProcedureintheMS.53A.1.2ProcedureintheBS.53SIST EN 300 938 V6.2.1:2003



ETSIETSIEN300938V6.2.1(2000-09)6(GSM04.06version6.2.1Release1997)A.2Format.53AnnexG(normative):Handlingofframeswithparametererrorsintheaddress,controlandlengthindicatorfields.54G.1General.54G.2Parametererrorsintheaddressfield.54G.2.1UnallocatedSAPI.54G.2.2WrongvalueoftheC/Rbit.54G.2.3EAbitsetto"0".54G.3Parametererrorsinthecontrolfield.55G.3.1Supervisoryframes.55G.3.2Unnumberedframes.55G.4Parametererrorsinthelengthindicatorfield.55G.4.1ELbiterror.55G.4.2Informationframes.55G.4.3Supervisoryframes.56G.4.4DISCandDMframes.56G.4.5SABMUAandUIframes.56AnnexH(informative):ChangeRequestHistory.57History.
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.