Digital Enhanced Cordless Telecommunications (DECT); Low Rate Messaging Service (LRMS) including Short Messaging Service (SMS)

Clean up conflicting coding in basic service information element in the CC setup message. Clean up references.

Digitalne izboljšane brezvrvične telekomunikacije (DECT) – Nizkohitrostna storitev sporočanja (LRMS), vključno s storitvijo kratkih sporočil (SMS)

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 757 V1.4.1:2003
English language
106 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 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.4.1SIST EN 300 757 V1.4.1:2003en01-december-2003SIST EN 300 757 V1.4.1:2003SLOVENSKI
STANDARD



SIST EN 300 757 V1.4.1:2003



ETSIEN300757V1.4.1(2002-04)EuropeanStandard(Telecommunicationsseries)DigitalEnhancedCordlessTelecommunications(DECT);LowRateMessagingService(LRMS)includingShortMessagingService(SMS)SIST EN 300 757 V1.4.1:2003



ETSIETSIEN300757V1.4.1(2002-04)2ReferenceREN/DECT-A0210Keywordsdata,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://portal.etsi.org/tb/status/status.aspIfyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frCopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2002.Allrightsreserved.DECTTM,PLUGTESTSTMandUMTSTMareTradeMarksofETSIregisteredforthebenefitofitsMembers.TIPHONTMandtheTIPHONlogoareTradeMarkscurrentlybeingregisteredbyETSIforthebenefitofitsMembers.3GPPTMisaTradeMarkofETSIregisteredforthebenefitofitsMembersandofthe3GPPOrganizationalPartners.SIST EN 300 757 V1.4.1:2003



ETSIETSIEN300757V1.4.1(2002-04)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.155.2.1General.155.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.165.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.235.4.3.6Timersupport.245.4.3.7Proceduresupport.245.5DLClayerrequirements.255.5.1RequirementsC-planePoint-To-Point(PTP)service.255.5.2RequirementsC-planePoint-To-Multipoint(PTM)service.255.5.3RequirementsU-plane.265.5.4Capabilities.265.5.4.1C-planeservices.265.5.4.2C-planeprocedures.265.5.4.2.1Point-to-pointacknowledgedoperation.265.5.4.2.2Unacknowledgedoperation.285.5.4.2.3Broadcastoperation.285.5.4.2.4Managementprocedures.285.5.4.3C-planePDUframestructure.295.5.4.4C-planemessages.305.5.4.5C-planetimers.355.5.4.6C-planeprotocolerrorhandling.355.6Networklayerrequirements.36SIST EN 300 757 V1.4.1:2003



ETSIETSIEN300757V1.4.1(2002-04)45.6.1RequirementsPoint-To-Point(PTP)service.365.6.2RequirementsPoint-To-Multipoint(PTM)service.365.7Managemententityrequirements.365.8Genericinterworkingconventions.365.8.1MMSPprocedures.365.8.2MultimediaMessagingService-ServiceAccessPoint(MMS-SAP).375.8.3MMSPprimitivesPoint-ToPoint(PTP)service.375.8.3.1C-MMSprimitives.375.8.3.2M-MMSprimitives.385.8.3.3Parameters.385.8.4MMSPprimitivesPoint-To-Multipoint(PTM)Service.385.8.4.1M-MMSprimitives.385.8.4.2Parameters.386MMSPprotocoldefinition.396.1General.396.2Functionaldescription.396.2.1General.396.2.2MMSrelationstooutsidenetworks(horizontalmodel).406.2.3Architecture.416.2.3.1General.416.2.3.2MMSPcallcontrolpart(C-MMS).416.2.3.3MMSPmessagingpart(M-MMS).416.2.4MMSrelationstotheupper/lowerlayers(verticalmodel).426.2.4.1General.426.2.4.2MMSrelationtotheDECTupperlayers.436.2.4.2.1General.436.2.4.2.2M-MMS.436.2.4.2.3C-MMS.436.2.5MMSrelationstooutsidenetworks(verticalandhorizontalmodel).436.2.5.1General.436.2.5.2Phasesofthehorizontalinteractions.436.2.5.2.1General.436.2.5.2.2PPoriginatedoutgoingMMScall.446.2.5.2.3ExampleofatypicalPPinitiatedmessage.456.2.5.2.4PPterminatedincomingMMScall.456.3MMSPprotocolmessagesandprocedures.466.3.1C-MMSmessagesandprocedures.466.3.2M-MMS.466.3.2.1SummaryoftheM-MMSmessages.466.3.2.2MMSSENDprocedure.476.3.2.2.1{MMS-SEND}messagecontents.476.3.2.2.2{MMS-SEND-RPY}messagecontents.486.3.2.3MMSSEND-REQprocedure.486.3.2.3.1{MMS-SEND-REQ}messagecontents.496.3.2.3.2{MMS-SEND-RPY}messagecontents.496.3.2.4MMSRETRIEVEprocedure.496.3.2.4.1{MMS-RETRIEVE}messagecontents.506.3.2.4.2{MMS-RETRIEVE-RPY}messagecontents.506.3.2.5MMSRETRIEVE-HDRprocedure.516.3.2.5.1{MMS-RETRIEVE-HDR}messagecontents.516.3.2.5.2{MMS-RETRIEVE-RPY}messagecontents.526.3.2.6MMS-EXT-CMDprocedure.526.3.2.6.1{MMS-EXT-CMD}messagecontents.536.3.2.6.2{MMS-EXT-CMD-RPY}messagecontents.536.3.2.7MMS-STATUSprocedures.536.3.2.7.1{MMS-STATUS}messagecontents.546.3.2.7.2{MMS-STATUS-RPY}messagecontents.546.3.2.8MMS-ESC-CMDprocedure.556.3.2.8.1{MMS-ESC-CMD}messagecontents.556.3.2.8.2{MMS-ESC-CMD-RPY}messagecontents.566.3.2.8.3Genericinterworkingconventionsforthe{MMS-ESC-CMD}commandandreply.56SIST EN 300 757 V1.4.1:2003



ETSIETSIEN300757V1.4.1(2002-04)56.3.2.9ProceduresfortheuseoftheMMS-messageidentifier.566.3.2.10Multi-partmessageprocedures.566.3.2.10.1Multi-partsendprocedures.576.3.2.10.2Multi-partretrieveprocedures.576.3.2.11UnsupportedMMScommandandIEcompatibilityprocedures.576.3.2.11.1UnsupportedMMScommandsprocedure.576.3.2.11.2UnsupportedInformationelementsprocedure.576.4MMSPinformationelements.586.4.1SummaryofM-MMSPinformationelements.586.5ParametersofM-MMSPserviceprimitives.586.5.1M_MMS_SEND-{req,ind}.596.5.2M_MMS_SEND_REQ-{req,ind}.596.5.3M_MMS_SEND_RPY-{req,ind}.606.5.4M_MMS_RETRIEVE-{req,ind}.606.5.5M_MMS_RETRIEVE_RPY-{req,ind}.616.5.6M_MMS_EXT_CMD-{req,ind}.616.5.7M_MMS_EXT_CMD_RPY-{req,ind}.626.5.8M_MMS_STATUS-{req,ind}.626.5.9M_MMS_STATUS_RPY-{req,ind}.636.5.10M_MMS_ESC_CMD-{req,ind}.636.5.11M_MMS_ESC_CMD_RPY-{req,ind}.647ShortMessageService(SMS).647.1Featureandservicedefinitions.647.1.1Applicationfeatures.647.1.2MMSfeatures.647.1.3NWKfeatures.647.1.4DLCservices.647.2Generalrequirements.657.2.1Referenceconfigurations.657.2.2Protocolarchitecture.657.3Interoperabilityrequirements.667.3.1Applicationfeatures.667.3.2MMSfeatures.667.3.3NWKfeatures.667.3.4DLCservices.667.3.5MACservices.677.3.6PHLservices.677.3.7Applicationfeaturetoproceduremapping.677.3.8MMSfeaturetoproceduremapping.677.3.9NWKfeaturetoproceduremapping.687.3.10DLCfeaturetoproceduremapping.687.4Applicationprocedures.697.4.1Incomingmessagestorage.697.4.2Messageencapsulation.697.4.3Generalinterworkingrequirements.697.4.3.1MappingofSMSmessagetransfersontoCC-transactions.697.4.3.2Authenticationandciphering.697.4.4Message/primitiveinterworking.697.5MMSprocedures.697.5.1Messagingsendprocedure.707.6NWKlayerproceduredescriptions.717.6.1Summaryofoutgoingcallmessages,normalcase.717.6.2Outgoingmessagingcallrequest.717.6.3Outgoingmessagingcallconnect.727.6.4Summaryofincomingcallmessages,normalcase.727.6.5Incomingmessagingcallrequest.727.6.6Incomingmessagingcallconnect.737.6.7Messagetransfer.737.6.8Terminalcapabilityindication.747.7DLClayerprocedures.747.7.1ClassBlinkestablishment.74SIST EN 300 757 V1.4.1:2003



ETSIETSIEN300757V1.4.1(2002-04)67.7.1.1Associatedprocedures.767.7.1.1.1Timermanagement.767.7.1.1.2Re-transmissioncountermanagement.767.7.1.1.3Multipleframeoperationvariablesmanagement.767.7.1.2Exceptionalcases.777.7.1.2.1Timerexpiry.777.7.1.2.2Receiptofarequestforlinkrelease.777.7.1.2.3Receiptofanindicationforaconnectionrelease.777.7.2ClassBmultipleframeoperation.777.7.2.1ClassBmultipleframeoperationwithsegmentreassemble.807.7.2.2Associatedprocedures.807.7.2.2.1Timermanagement.807.7.2.2.2Re-transmissioncountermanagement.817.7.2.2.3Multipleframeoperationvariablesmanagement.817.7.2.2.4Exceptionhandling.
...

Questions, Comments and Discussion

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