SIST EN 300 757 V1.2.1:2003
(Main)Digital Enhanced Cordless Telecommunications (DECT); Low Rate Messaging Service (LRMS) including Short Messaging Service (SMS)
- Abstract
Maintenance update to include approved change requests. Supporting ETSI Member Organisations; Siemens, Alcatel, Ascom, Philips.
- 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
SIST EN 300 757 V1.2.1:2003 is the Slovenian adoption of the ETSI European Standard for Digital Enhanced Cordless Telecommunications (DECT) Low Rate Messaging Service (LRMS), including Short Messaging Service (SMS). It specifies how DECT systems carry slow, acknowledged or unacknowledged message objects over point-to-point and point-to-multipoint links, for implementers of DECT terminals, Fixed Parts and interworking units. It is aimed at messaging, paging and GSM-like SMS interworking.
What does SIST EN 300 757 V1.2.1:2003 specify?
SIST EN 300 757 V1.2.1:2003 specifies the DECT LRMS profile and the SMS-PTP profile built on top of it. It covers the Physical (PHY), Medium Access Control (MAC), Data Link Control (DLC) and Network (NWK) layers, plus management entity requirements and generic interworking conventions.
The standard is organized into these main parts:
- Clause 1 - Scope
- Clause 2 - References
- Clause 3 - Definitions, symbols and abbreviations
- Clause 4 - Description of services
- Clause 5 - Low Rate MessagingService (LRMS)
- Clause 6 - MMSP protocol definition
- Clause 7 - Short Message Service (SMS)
- Annex A - Support of MMSP by the DECT lower layers
- Annex B - Profileselection coding
- Annex C - Typical message mapping sequences
The scope includes point-to-point and point-to-multipoint messaging, with SMS-PTP split into SMS-Mobile Originated (SMS-MO) and SMS-Mobile Terminated (SMS-MT). Cell Broadcast is outside the scope. Applications and the network behind the Fixed Part are also outside the scope.
| Annex | What it covers |
|---|---|
| Annex A | MMSP support by the DECT lower layers, including profile-specific information elements, message mapping and segmentation rules |
| Annex B | Profileselection coding for <>, <> and <> |
| Annex C | Typical message mapping sequences for SMS-RP requirements |
What are the key requirements of SIST EN 300 757 V1.2.1:2003?
SIST EN 300 757 V1.2.1:2003 defines a layered DECT messaging profile in which LRMS carries small user data units and MMSP provides the message control behavior. In practice, this means an implementation has to choose the right service mode, carry the right message elements and use the correct DECT procedures at each layer.
- Clause 4 defines two LRMS services: LRMSPTP and LRMSPTM. LRMSPTP is mandatory if the profile is supported; LRMSPTM is optional. This matters because PTP is for one-to-one messaging, while PTM is for broadcast-style delivery from FP to PP.
- Clause 4 also states that LRMSPTP may be acknowledged or unacknowledged, while LRMSPTM is unacknowledged. For a buyer or engineer, that affects whether delivery confirmation and reply handling are needed.
- Clause 5.3 and 5.4 tie the profile to EN 300 444 and EN 300 175-3. LRMSPTP uses the CS channel if no other profile is present, and LRMSPTM uses CLF or CLS. The fixed and portable sides also have capability bits for LRMS and broadcast support, so the radio profile has to be signaled correctly.
- Clause 5.5 keeps protocol control on the C-plane and does not use the U-plane. The minimum DLC frame length is 63 octets. That means implementation effort goes into control-plane procedures, not user-plane transport.
- Clause 5.6 maps user information into NWK messages. For PTP, application data goes in <> inside {IWU-INFO}; for PTM, {CLMS-VARIABLE} carries <>, <>, <> and <>. This is the interoperability point where payload format and segmentation matter.
- Clause 6 defines MMSP as a stateless protocol split into C-MMS and M-MMS, with access through MMS-SAP primitives. For PTM, only {MMS-SEND}, {MMS-STATUS}, {MMS-EXT-CMD} and {MMS-ESC-CMD} apply. That limits what a broadcast implementation can request or return.
- Clause 7 maps SMS over LRMSPTP using GSM-like SMS protocols up to SMS-RP. It also includes incoming message storage, encapsulation, authentication, ciphering and the mapping of SMS message transfers onto CC transactions. In practice, this is the part needed to interwork with SMS services and service centers.
What terms does SIST EN 300 757 V1.2.1:2003 define?
- Low Rate Messaging Service (LRMS) - The DECT messaging service for slow transfer of multimedia message objects, including SMS.
- Short Message Service (SMS) - The GSM-like short-message service carried over LRMS Point-To-Point.
- Point-To-Point (PTP) - A one-to-one messaging mode that may be acknowledged or unacknowledged.
- Point-To-Multipoint (PTM) - A one-to-many messaging mode from Fixed Part to Portable Parts, without acknowledgements.
- Multimedia Messaging Service Protocol (MMSP) - The stateless protocol that carries message control and message transfer between MMS entities.
- Message Control Entity (MCE) - The outside-network server that stores, forwards and controls messages.
- Interworking Unit (IWU) - The function that bridges DECT messaging with the outside network.
- Fixed Part (FP) - The DECT fixed-side entity that provides the radio and interworking role for messaging services.
Who uses SIST EN 300 757 V1.2.1:2003?
SIST EN 300 757 V1.2.1:2003 is used by DECT equipment designers, protocol developers and system integrators who need LRMS or SMS interworking. It is also relevant to test labs, quality teams and buyers checking whether a product supports the required DECT messaging behavior.
Typical users include:
- DECT terminal and Fixed Part manufacturers
- Interworking unit and messaging gateway developers
- Messaging service providers and network operators
- Test and certification laboratories
- Quality managers verifying feature support and interoperability
- Buyers selecting DECT equipment for paging or short-message services
What changed in SIST EN 300 757 V1.2.1:2003 from the previous edition?
This edition is a maintenance update that includes approved change requests. It replaces the former ETS 300 757, known as the E.2 profile, and the former ETS 301 678, known as CTMFP2.
Which standards are used with SIST EN 300 757 V1.2.1:2003?
The standard cites these companion documents and uses them to define the underlying DECT and SMS behavior:
- EN 300 175-1 to EN 300 175-8 - the DECT Common Interface parts for overview, PHY, MAC, DLC, NWK, identities and addressing, security features, and speech coding/transmission
- EN 300 444 - the DECT Generic Access Profile (GAP)
- ETS 300 559 - GSM SMS support on the mobile radio interface, used for the SMS-RP model
What does the SIST EN 300 757 V1.2.1:2003 document contain?
The document contains service objectives tables, reference configurations and detailed capability matrices for LRMSPTP, LRMSPTM and SMS. It also includes message and procedure definitions for MMSP, with separate treatment of send, retrieve, status and extended command behavior.
Several tables define supported services, protocol parameters, messages, message parameters, timers and error handling. The figures show the LRMS reference configuration, MMS horizontal and vertical models, and the typical MMS message exchange sequences.
Annex A gives the lower-layer support for MMSP, including profile-specific information elements and segmentation rules. Annex B provides profile-selection coding, and Annex C gives typical message mapping sequences for SMS-RP behavior.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 300 757 V1.2.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital Enhanced Cordless Telecommunications (DECT); Low Rate Messaging Service (LRMS) including Short Messaging Service (SMS)". This standard covers: Maintenance update to include approved change requests. Supporting ETSI Member Organisations; Siemens, Alcatel, Ascom, Philips.
Maintenance update to include approved change requests. Supporting ETSI Member Organisations; Siemens, Alcatel, Ascom, Philips.
SIST EN 300 757 V1.2.1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 757 V1.2.1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
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
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.817.7.3.2Exceptionalcases.817.7.3.2.1Timerexpiry.817.7.3.2.2Receiptofanindicationforaconnectionrelease.827.7.3.3.3Collisionofidenticaltransmittedandreceivedcommands.827.7.4ClassBlinksuspensionandresumption.827.7.4.1Unacknowledgedsuspend.827.7.4.2ClassBlinkresumption.827.7.4.3Associatedprocedures.827.7.4.3.1Timermanagement.827.7.4.4Exceptionalcases.827.7.4.4.1Timerexpiry.827.7.4.4.2Receiptofanindicationforaconnectionrelease.837.7.5ClassBlinkre-establishment.837.7.5.1Associatedprocedures.857.7.5.1.1Timermanagement.857.7.5.2Exceptionalcases.857.7.5.2.1Timerexpiry.857.7.5.2.2Receiptofarequestforlinkrelease.857.7.5.2.3Receiptofanindicationforaconnectionrelease.857.7.5.2.4Collisionofidenticaltransmittedandreceivedcommands.857.8MAClayerprocedures.867.9PHYlayerrequirements.867.10Managementprocedures.867.10.1Broadcastattributemanagement.86AnnexA(normative):SupportofMMSPbytheDECTlowerlayers.87A.1Profile-specificinformationelements.87A.1.1MMSGenericHeaderinformationelement.87A.1.2MMSObjectHeaderinformationelement.91A.1.3MMSExtendedHeaderinformationelement.96A.2MMSPmessageimplementation.97A.2.1General.97A.2.2C-MMSprimitivesmappingrules.97A.2.2.1LRMSPTPC-MMSprimitives.97A.2.2.2LRMSPTMC-MMSprimitives.97A.2.3M-MMSmessagemappingrules.97SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)7A.2.3.1GeneralrulesforLRMSPTP.97A.2.3.2GeneralrulesforLRMSPTM.97A.2.3.3Informationelementmappingrules.98A.3NetworklayersegmentationrulesforLRMSPTP.98A.3.1Procedureatthesendingside.98A.3.2Procedureatthereceivingside.99AnnexB(informative):Profileselectioncoding.100B.1<>coding.100B.2<>coding.100B.3<>coding.100AnnexC(informative):Typicalmessagemappingsequences.102C.1SummaryofSMS-RPrequirements.102C.2Messagesequences.102Bibliography.104History.105SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)8IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.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)hasbeenproducedbyETSIProjectDigitalEnhancedCordlessTelecommunications(DECT).NationaltranspositiondatesDateofadoptionofthisEN:19January2001DateoflatestannouncementofthisEN(doa):30April2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31October2001DateofwithdrawalofanyconflictingNationalStandard(dow):31October2001IntroductionThepresentdocumentreplacestheformerETS300757,knownastheE.2profile,andtheformerETS301678,knownasCTMFP2.ItdefinesprofilesforDigitalEnhancedCordlessTelecommunications(DECT)systemsconformingtoEN300175parts1[1]to8[8].Itispartofafamilyofprofilesaimedatthegeneralconnectionofterminalssupportingnon-voiceservicestoafixedinfrastructure,privateandpublic.SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)91ScopeTheLowRateMessagingService(LRMS),specifiedinthepresentdocument,providesameansfortheslow,acknowledgedorunacknowledged,transferofmultimediamessageobjects,includingtheShortMessageService(SMS).Itprovidesbothpoint-to-pointandpoint-to-multipointmessaging.Thisservicemaybeusedforprivateandpublicroamingapplications.ThepresentdocumentdefinestherequirementsonthePhysical(PHY),MediumAccessControl(MAC),DataLinkControl(DLC)andNetwork(NWK)layersofDECT.Thestandardalsospecifiesmanagemententityrequirementsandgenericinterworkingconventions,whichensuretheefficientuseoftheDECTspectrum.ThepresentdocumentfurthermandateshowtoimplementaGSMlikeShortMessageService(SMS),PointtoPoint(PTP),whichusesasub-setoftheLowRateMessagingService(LRMS)mentionedbeforeasabearerservice.SMS-PTPincludesthefollowingtwoservices:-SMSMobileOriginated(SMS-MO),fortransportofshortmessagesfromPTtoFT;-SMSMobileTerminated(SMS-MT),fortransportofshortmessagesfromFTtoPT.TheShortMessageService,CellBroadcastisoutsidethescopeofthepresentdocument.Inordertofacilitatere-useofexcisingGSMServiceCentres,thepresentdocumentappliestheupperGSMprotocolsup-toandincludingtheGSMSMS-RPprotocol.Therefore,interworkingfunctionshandlingtheencapsulationofGSMSMS-RPmessagesarespecified.Thefollowingpictureshowstheprotocolsdefinedinthepresentdocument.PHLMACDLCNWKLRMSPTPLRMSPTMMMSPGSMSMSSMSSMSIWUorapplicationLRMSPTPIWUorapplicationLRMSPTMIWUorapplicationSIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)10TheSMSorLRMSapplicationsareoutsidethescopeofthepresentdocument.SoisthenetworkbehindtheFP.AnyinformationprovidedconcerningapplicationsorthenetworkbehindtheFPisprovidedforinformative,descriptivereasonsonly.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIEN300175-1:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part1:Overview".[2]ETSIEN300175-2:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part2:PhysicalLayer(PHL)".[3]ETSIEN300175-3:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part3:MediumAccessControl(MAC)layer".[4]ETSIEN300175-4:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part4:DataLinkControl(DLC)layer".[5]ETSIEN300175-5:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part5:Network(NWK)layer".[6]ETSIEN300175-6:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part6:Identitiesandaddressing".[7]ETSIEN300175-7:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part7:Securityfeatures".[8]ETSIEN300175-8:"DigitalEnhancedCordlessTelecommunications(DECT);CommonInterface(CI);Part8:Speechcodingandtransmission".[9]ETSIEN300444:"DigitalEnhancedCordlessTelecommunications(DECT);GenericAccessProfile(GAP)".[10]ETSIETS300559:"Europeandigitalcellulartelecommunicationssystem(Phase2);Point-to-Point(PP)ShortMessageService(SMS)supportonmobileradiointerface(GSM04.11)".SIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)113Definitions,symbolsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply.multiframe:repeatingsequenceof16successiveTimeDivisionMultipleAccess(TDMA)frames,thatallowslowrateorsporadicinformationtobemultiplexed(e.g.basicsysteminformationorpaging)serviceclass1:localareaapplications,forwhichterminalsarepre-registeredoff-airwithoneormorespecificfixedparts,andestablishmentofserviceanduserparametersisthereforeimplicit,accordingtoaprofile-definedlistserviceclass2:privateandpublicroamingapplicationsforwhichterminalsmaymovebetweenfixedpartswithinagivendomainandforwhichassociationofserviceparametersisexplicitatthetimeofservicerequestSMS-SC:SMSShortMessageCenter.ItisthelogicalentityabletostoreandforwardshortmessagesTDMAframe:time-divisionmultiplexof10msduration,containing24successivefullslots.ATDMAframestartswiththefirstbitperiodoffullslot0andendswiththelastbitperiodoffullslot233.2SymbolsThesymbolsdefinedinthisclauseareappliedforprocedures,features,servicesinthepresentdocumentifnotexplicitlyotherwisestated.Theinterpretationofstatuscolumnsinalltablesisasfollows:Mformandatorytosupport(provisionmandatory,processmandatory);Oforoptionaltosupport(provisionoptional,processmandatory);Iforout-of-scope(provisionoptional,processoptional)notsubjectfortesting;Cforconditionaltosupport(processmandatory);N/Afornon-applicable(inthegivencontextthespecificationmakesitimpossibletousethiscapability).Provisionmandatory,processmandatorymeansthattheindicatedfeature,serviceorprocedureshallbeimplementedasdescribedinthepresentdocument,andmaybesubjecttotesting.Provisionoptional,processmandatorymeansthattheindicatedfeature,serviceorproceduremaybeimplemented,andifimplemented,thefeature,serviceorprocedureshallbeimplementedasdescribedinthepresentdocument,andmaybesubjecttotesting.3.3AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:ACKAcknowledgementADPCMAdaptivePulseCodeModulationCCCallControlCFhigherlayersignallingChannel(Fast)CLMSConnectionlessMessageServiceC-planeControlPlaneCTMCordlessTerminalMobilityCShigherlayersignallingChannel(Slow)DAMDECTAuthenticationModuleDECTDigitalEnhancedCordlessTelecommunicationsDLCDataLinkControlFPFixedPartFTFixedradioTerminationFTPFileTransferProtocolGAPGenericAccessProfileGSMGlobalSystemforMobilecommunicationHTTPHyperTextTransferProtocolSIST EN 300 757 V1.2.1:2003
ETSIETSIEN300757V1.2.1(2001-01)12IEInformationElementIPhigherlayerInformationchannel(Protected)IWFInterworkingFunctionsIWUInterworkingUnitLAPLinkAccessProcedureLAP-CLinkAccessProcedure(Control)LCELinkControlEntityLLNLogicalLinkNumber(DLClayer)LRMSLowRateMessagingServiceMMACcontrolchannelMACMediumAccessControlMCEMessageControlEntityMMSPMultimediaMessagingServiceProtocolMNCCMobileNetworkCallControlMOMobileOriginatedMTMobileTerminatedNLFNewLinkFlagNWKNetworkPPagingchannelPDUProtocolDataUnitPHLPhysicalLayerPHYPhysicalPPPortablePartPTPortableradioTerminationPTMPoint-To-MultipointPTPPoint-To-PointQsysteminformationchannelRFPRadioFixedPartRFPIRadioFixedPartIdentifierSAPServiceAccessPointSAPISer
...