ETSI EN 300 757 V1.2.1 (2001-01)
Digital Enhanced Cordless Telecommunications (DECT); Low Rate Messaging Service (LRMS) including Short Messaging Service (SMS)
Digital Enhanced Cordless Telecommunications (DECT); Low Rate Messaging Service (LRMS) including Short Messaging Service (SMS)
REN/DECT-A0176
Digitalne izboljšane brezvrvične telekomunikacije (DECT) – Nizkohitrostna storitev sporočanja (LRMS), vključno s storitvijo kratkih sporočil (SMS)
General Information
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital Enhanced Cordless Telecommunications (DECT); Low Rate Messaging Service (LRMS) including Short Messaging Service (SMS)33.070.30'(&7Digital Enhanced Cordless Telecommunications (DECT)ICS:Ta slovenski standard je istoveten z:EN 300 757 Version 1.2.1SIST EN 300 757 V1.2.1:2003en01-december-2003SIST EN 300 757 V1.2.1:2003SLOVENSKI
STANDARD
SIST EN 300 757 V1.2.1:2003
ETSIEN300757V1.2.1(2001-01)EuropeanStandard(Telecommunicationsseries)DigitalEnhancedCordlessTelecommunications(DECT);LowRateMessagingService(LRMS)includingShortMessageService(SMS)SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)2ReferenceREN/DECT-A0176Keywordsdata,DECT,profile,SMSETSI650RoutedesLuciolesF-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.©EuropeanTelecommunicationsStandardsInstitute2001.Allrightsreserved.SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)3ContentsIntellectualPropertyRights.8Foreword.8Introduction.81Scope.92References.103Definitions,symbolsandabbreviations.113.1Definitions.113.2Symbols.113.3Abbreviations.114Descriptionofservices.134.1General.134.2LowRateMessagingService(LRMS).134.2.1Point-To-Point(PTP).134.2.2Point-To-Multipoint(PTM).144.3ShortMessageService(SMS).144.4Serviceobjectives.145LowRateMessagingService(LRMS).155.1Referenceconfiguration.155.2Functionaldescription.165.2.1General.165.2.2ExceptionsforPoint-To-Multipoint(PTM)service.165.2.2.1MMSrelationstooutsidenetworks(horizontalmodel).165.2.2.2Architecture.165.2.2.3MMSrelationstotheupper/lowerlayers(verticalmodel).165.2.2.4Phasesofthehorizontalinteractions.165.3Physicallayerrequirements.175.4MAClayerrequirements.175.4.1RequirementsPoint-To-Point(PTP)service.175.4.2RequirementsPoint-To-Multipoint(PTM)service.175.4.3Capabilities.185.4.3.1Services.185.4.3.2Protocolparameters.185.4.3.3Messages.195.4.3.4Messageparameters.215.4.3.5Functionsimplemented.225.4.3.6Timersupport.235.4.3.7Proceduresupport.235.5DLClayerrequirements.245.5.1RequirementsC-planePoint-To-Point(PTP)service.245.5.2RequirementsC-planePoint-To-Multipoint(PTM)service.245.5.3RequirementsU-plane.255.5.4Capabilities.255.5.4.1C-planeservices.255.5.4.2C-planeprocedures.255.5.4.2.1Pointtopointacknowledgedoperation.255.5.4.2.2Unacknowledgedoperation.275.5.4.2.3Broadcastoperation.275.5.4.2.4Managementprocedures.275.5.4.3C-planePDUframestructure.285.5.4.4C-planemessages.295.5.4.5C-planetimers.335.5.4.6C-planeprotocolerrorhandling.335.6Networklayerrequirements.34SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)45.6.1RequirementsPoint-To-Point(PTP)service.345.6.2RequirementsPoint-To-Multipoint(PTM)service.345.7Managemententityrequirements.345.8Genericinterworkingconventions.355.8.1MMSPprocedures.355.8.2MultimediaMessagingService-ServiceAccessPoint(MMS-SAP).355.8.3MMSPprimitivesPoint-ToPoint(PTM)service.355.8.3.1C-MMSprimitives.355.8.3.2M-MMSprimitives.365.8.3.3Parameters.365.8.4MMSPprimitivesPoint-To-MultipointSerive.365.8.4.1M-MMSprimitives.365.8.4.2Parameters.366MMSPprotocoldefinition.366.1General.366.2Functionaldescription.376.2.1General.376.2.2MMSrelationstooutsidenetworks(horizontalmodel).376.2.3Architecture.386.2.3.1General.386.2.3.2MMSPcallcontrolpart(C-MMS).396.2.3.3MMSPmessagingpart(M-MMS).396.2.4MMSrelationstotheupper/lowerlayers(verticalmodel).396.2.4.1General.396.2.4.2MMSrelationtotheDECTupperlayers.406.2.4.2.1General.406.2.4.2.2M-MMS.406.2.4.2.3C-MMS.416.2.5MMSrelationstooutsidenetworks(verticalandhorizontalmodel).416.2.5.1General.416.2.5.2Phasesofthehorizontalinteractions.416.2.5.2.1General.416.2.5.2.2PPoriginatedoutgoingMMScall.416.2.5.2.3ExampleofatypicalPPinitiatedmessage.436.2.5.2.4PPterminatedincomingMMScall.436.3MMSPprotocolmessagesandprocedures.446.3.1C-MMSmessagesandprocedures.446.3.2M-MMS.446.3.2.1SummaryoftheM-MMSmessages.446.3.2.2MMSSENDprocedure.446.3.2.2.1{MMS-SEND}messagecontents.456.3.2.2.2{MMS-SEND-RPY}messagecontents.456.3.2.3MMSSEND-REQprocedure.466.3.2.3.1{MMS-SEND-REQ}messagecontents.466.3.2.3.2{MMS-SEND-RPY}messagecontents.476.3.2.4MMSRETRIEVEprocedure.476.3.2.4.1{MMS-RETRIEVE}messagecontents.486.3.2.4.2{MMS-RETRIEVE-RPY}messagecontents.486.3.2.5MMSRETRIEVE-HDRprocedure.486.3.2.5.1{MMS-RETRIEVE-HDR}messagecontents.496.3.2.5.2{MMS-RETRIEVE-RPY}messagecontents.496.3.2.6MMS-EXT-CMDprocedure.506.3.2.6.1{MMS-EXT-CMD}messagecontents.506.3.2.6.2{MMS-EXT-CMD-RPY}messagecontents.516.3.2.7MMS-STATUSprocedures.516.3.2.7.1{MMS-STATUS}messagecontents.526.3.2.7.2{MMS-STATUS-RPY}messagecontents.526.3.2.8MMS-ESC-CMDprocedure.526.3.2.8.1{MMS-ESC-CMD}messagecontents.536.3.2.8.2{MMS-ESC-CMD-RPY}messagecontents.536.3.2.8.3Genericinterworkingconventionsforthe{MMS-ESC-CMD}commandandreply.53SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)56.3.2.9ProceduresfortheuseoftheMMS-messageidentifier.546.3.2.10Multi-partmessageprocedures.546.3.2.10.1Multi-partsendprocedures.546.3.2.10.2Multi-partretrieveprocedures.556.3.2.11UnsupportedMMScommandandIEcompatibilityprocedures.556.3.2.11.1UnsupportedMMScommandsprocedure.556.3.2.11.2UnsupportedInformationelementsprocedure.556.4MMSPinformationelements.556.4.1SummaryofM-MMSPinformationelements.556.5ParametersofM-MMSPserviceprimitives.566.5.1M_MMS_SEND-{req,ind}.566.5.2M_MMS_SEND_REQ-{req,ind}.576.5.3M_MMS_SEND_RPY-{req,ind}.576.5.4M_MMS_RETRIEVE-{req,ind}.586.5.5M_MMS_RETRIEVE_RPY-{req,ind}.586.5.6M_MMS_EXT_CMD-{req,ind}.596.5.7M_MMS_EXT_CMD_RPY-{req,ind}.596.5.8M_MMS_STATUS-{req,ind}.606.5.9M_MMS_STATUS_RPY-{req,ind}.606.5.10M_MMS_ESC_CMD-{req,ind}.616.5.11M_MMS_ESC_CMD_RPY-{req,ind}.617ShortMessageService(SMS).627.1Featureandservicedefinitions.627.1.1Applicationfeatures.627.1.2MMSfeatures.627.1.3NWKfeatures.627.1.4DLCservices.627.2Generalrequirements.627.2.1Referenceconfigurations.627.2.2Protocolarchitecture.627.3Interoperabilityrequirements.637.3.1Applicationfeatures.637.3.2MMSfeatures.647.3.3NWKfeatures.647.3.4DLCservices.647.3.5MACservices.647.3.6PHLservices.647.3.7Applicationfeaturetoproceduremapping.657.3.8MMSfeaturetoproceduremapping.657.3.9NWKfeaturetoproceduremapping.657.3.10DLCfeaturetoproceduremapping.667.4Applicationprocedures.667.4.1Incomingmessagestorage.667.4.2Messageencapsulation.667.4.3Generalinterworkingrequirements.667.4.3.1MappingofSMSmessagetransfersontoCC-transactions.667.4.3.2Authenticationandciphering.667.4.4Message/primitiveinterworking.677.5MMSprocedures.677.5.1Messagingsendprocedure.677.6NWKlayerproceduredescriptions.697.6.1Summaryofoutgoingcallmessages,normalcase.697.6.2Outgoingmessagingcallrequest.697.6.3Outgoingmessagingcallconnect.697.6.4Summaryofincomingcallmessages,normalcase.707.6.5Incomingmessagingcallrequest.707.6.6Incomingmessagingcallconnect.717.6.7Messagetransfer.717.6.8Terminalcapabilityindication.727.7DLClayerprocedures.727.7.1ClassBlinkestablishment.72SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)67.7.1.1Associatedprocedures.747.7.1.1.1Timermanagement.747.7.1.1.2Re-transmissioncountermanagement.747.7.1.1.3Multipleframeoperationvariablesmanagement.747.7.1.2Exceptionalcases.757.7.1.2.1Timerexpiry.757.7.1.2.2Receiptofarequestforlinkrelease.757.7.1.2.3Receiptofanindicationforaconnectionrelease.757.7.2ClassBmultipleframeoperation.757.7.2.1ClassBmultipleframeoperationwithsegmentreassemble.787.7.2.2Associatedprocedures.787.7.2.2.1Timermanagement.787.7.2.2.2Re-transmissioncountermanagement.787.7.2.2.3Multipleframeoperationvariablesmanagement.787.7.2.2.4Exceptionhandling.787.7.2.3Exceptionalcases.787.7.2.3.1Timerexpiry.787.7.2.3.2Receiptofarequestforlinkrelease.787.7.2.3.3Receiptofanindicationforaconnectionrelease.797.7.2.3.4DLCwantstomakeaconnectionhandover.797.7.3ClassBlinkrelease.797.7.3.1Associatedprocedures.817.7.3.1.1LLMEU-planerelease.817.7.3.1.2LLMEreleaseaMACconnection.817.7.3.1.3Timermanagement.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.