Abstract

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

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 Documents

Standard

SIST EN 300 757 V1.4.1:2003

English language (106 pages)
Preview
Preview
e-Library read for
×1 day

SIST EN 300 757 V1.4.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 LRMS point-to-point and point-to-multipoint messaging, and the GSM-like SMS point-to-point profile built on LRMS, for DECT systems and their interworking units.

What does SIST EN 300 757 V1.4.1:2003 specify?

SIST EN 300 757 V1.4.1:2003 defines how DECT carries slow messaging traffic, including acknowledged and unacknowledged transfers, and how SMS-PTP is implemented on top of LRMS. It covers requirements for the PHY, MAC, DLC and NWK layers, plus management entity requirements and generic interworking conventions.

The document is organized into clauses 1 to 7, with annexes for lower-layer mapping, profile selection coding, and typical message sequences.

AnnexWhat it covers
Annex ASupport of MMSP by the DECT lower layers, including mapping rules and segmentation
Annex BProfile selection coding for BASICSERVICE, IWU-ATTRIBUTES and CONNECTIONATTRIBUTES
Annex CTypical message mapping sequences for SMS-RP
Annex DBibliography

What are the key requirements of SIST EN 300 757 V1.4.1:2003?

SIST EN 300 757 V1.4.1:2003 makes LRMSPTP mandatory and LRMSPTM optional. In practice, a compliant product must support point-to-point messaging, while point-to-multipoint broadcast messaging is only needed if that service is claimed.

Clause 5 requires the DECT physical layer of EN 300 444 and the common interface parts of EN 300 175 to be used with the profile-specific rules. This matters because the profile is not a stand-alone messaging scheme - it is tied to the DECT air interface and its channel handling.

Clause 5.5 places the messaging functions on the C-plane and not the U-plane, and sets a minimum DLC frame length of 63 octets. For implementers, that means the messaging stack must be built around DECT control and link procedures, not user-plane traffic.

Clause 5.6 defines how network-layer data is carried. For PTP, the <<IWU-TO-IWU>> information element carries application data in the active CC state, and longer messages use <<SEGMENTED-INFO>> when the message exceeds 58 octets. For PTM, CLMS-VARIABLE is used with <<PORTABLEIDENTITY>>, and segmentation applies only to <<IWU-TO-IWU>>.

Clause 5.8 and clause 6 define MMSP as a stateless messaging protocol split into C-MMS and M-MMS. For PTP, it provides setup, send, retrieve, status, extended command and escape command primitives; for PTM, only MMS-SEND, MMS-STATUS, MMS-EXT-CMD and MMS-ESC-CMD apply.

Clause 6.3.2.9 and 6.3.2.10 define message correlation using the MMS-messageidentifier and MultipartParentMessageID. This is important when a message is split across transports or when several replies belong to one transaction.

Clause 7 defines SMS-PTP operation over LRMSPTP, including incoming message storage, encapsulation, mapping of SMS transfers onto CC transactions, and authentication and ciphering. That is the part to check when the goal is DECT transport of GSM-like short messages.

What terms does SIST EN 300 757 V1.4.1:2003 define?

Multiframe - a repeating sequence of 16 TDMA frames used to carry slow or sporadic information such as paging.

Service class 1 - local-area operation where terminals are pre-registered and service parameters are implicit from a profile-defined list.

Service class 2 - roaming operation where terminals may move between fixed parts and service parameters are selected explicitly at request time.

SMS-SC - the logical entity that stores and forwards short messages.

TDMA frame - a 10 ms frame containing 24 full slots in the DECT timing structure.

MMSP - the Multimedia Messaging Service Protocol, used here as the messaging layer for LRMS interworking.

MCE - the Message Control Entity, which controls message forwarding and status on the outside network side.

Who uses SIST EN 300 757 V1.4.1:2003?

SIST EN 300 757 V1.4.1:2003 is used by DECT terminal and fixed-part designers, messaging platform developers, and interworking unit engineers. It is also relevant to service providers and integrators who need DECT paging, private or public roaming messaging, or GSM-like SMS transport over DECT.

What changed in SIST EN 300 757 V1.4.1:2003 from the previous edition?

SIST EN 300 757 V1.4.1:2003 replaces former ETS 300 757, known as the E.2 profile, and former ETS 301 678, known as CTMFP2.

Which standards are used with SIST EN 300 757 V1.4.1:2003?

The profile is built on EN 300 175 parts 1 to 8, which provide the DECT common interface, including PHY, MAC, DLC, NWK, identities, security and speech coding. EN 300 444 provides GAP support, ETS 300 559 is the GSM SMS reference, ISO/IEC 8073 is the transport service reference, and ETS 300 764 plus TS 101 863-5 are named interworking profile references for SMS.

What does the SIST EN 300 757 V1.4.1:2003 document contain?

The document includes service and performance objectives, supported service and procedure tables, protocol parameters, message definitions, timer values, and frame structures. It also describes MMSP procedures such as send, retrieve, status, extended command and escape command, together with the CC-based interworking model.

Annex A gives the mapping between MMSP and the DECT lower layers, including profile-specific information elements and network-layer segmentation rules. Annex B defines profile selection coding, and Annex C shows typical SMS-RP message mapping sequences used for implementation and testing.

Buy Documents

Standard

SIST EN 300 757 V1.4.1:2003

English language (106 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified

Sponsored listings

Frequently Asked Questions

SIST EN 300 757 V1.4.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: Clean up conflicting coding in basic service information element in the CC setup message. Clean up references.

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

SIST EN 300 757 V1.4.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.4.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.4.1SIST EN 300 757 V1.4.1:2003en01-december-2003SIST EN 300 757 V1.4.1:2003SLOVENSKI
STANDARD
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.817.7.2.3Exceptionalcases.817.7.2.3.1Timerexpiry.817.7.2.3.2Receiptofarequestforlinkrelease.817.7.2.3.3Receiptofanindicationforaconnectionrelease.817.7.2.3.4DLCwantstomakeaconnectionhandover.817.7.3ClassBlinkrelease.817.7.3.1Associatedprocedures.837.7.3.1.1LLMEU-planerelease.837.7.3.1.2LLMEreleaseaMACconnection.837.7.3.1.3Timermanagement.847.7.3.2Exceptionalcases.847.7.3.2.1Timerexpiry.847.7.3.2.2Receiptofanindicationforaconnectionrelease.847.7.3.2.3Collisionofidenticaltransmittedandreceivedcommands.847.7.4ClassBlinksuspensionandresumption.847.7.4.1Unacknowledgedsuspend.847.7.4.2ClassBlinkresumption.847.7.4.3Associatedprocedures.857.7.4.3.1Timermanagement.857.7.4.4Exceptionalcases.857.7.4.4.1Timerexpiry.857.7.4.4.2Receiptofanindicationforaconnectionrelease.857.7.5ClassBlinkre-establishment.857.7.5.1Associatedprocedures.877.7.5.1.1Timermanagement.877.7.5.2Exceptionalcases.887.7.5.2.1Timerexpiry.887.7.5.2.2Receiptofarequestforlinkrelease.887.7.5.2.3Receiptofanindicationforaconnectionrelease.887.7.5.2.4Collisionofidenticaltransmittedandreceivedcommands.887.8MAClayerprocedures.887.9PHYlayerrequirements.887.10Managementprocedures.887.10.1Broadcastattributemanagement.88AnnexA(normative):SupportofMMSPbytheDECTlowerlayers.89A.1Profile-specificinformationelements.89A.1.1MMSGenericHeaderinformationelement.89A.1.2MMSObjectHeaderinformationelement.93A.1.3MMSExtendedHeaderinformationelement.97A.2MMSPmessageimplementation.98A.2.1General.98A.2.2C-MMSprimitivesmappingrules.99A.2.2.1LRMSPTPC-MMSprimitives.99A.2.2.2LRMSPTMC-MMSprimitives.99A.2.3M-MMSmessagemappingrules.99SIST EN 300 757 V1.4.1:2003

ETSIETSIEN300757V1.4.1(2002-04)7A.2.3.1GeneralrulesforLRMSPTP.99A.2.3.2GeneralrulesforLRMSPTM.99A.2.3.3Informationelementmappingrules.99A.3NetworklayersegmentationrulesforLRMSPTP.100A.3.1Procedureatthesendingside.100A.3.2Procedureatthereceivingside.100AnnexB(normative):Profileselectioncoding.101B.1<>coding.101B.2<>coding.101B.3<>coding.102AnnexC(informative):Typicalmessagemappingsequences.103C.1SummaryofSMS-RPrequirements.103C.2Messagesequences.103AnnexD(informative):Bibliography.105History.106SIST EN 300 757 V1.4.1:2003

ETSIETSIEN300757V1.4.1(2002-04)8IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://webapp.etsi.org/IPR/home.asp).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSIProjectDigitalEnhancedCordlessTelecommunications(DECT).NationaltranspositiondatesDateofadoptionofthisEN:5April2002DateoflatestannouncementofthisEN(doa):31July2002DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31January2003DateofwithdrawalofanyconflictingNationalStandard(dow):31January2003IntroductionThepresentdocumentreplacestheformerETS300757,knownastheE.2profile,andtheformerETS301678,knownasCTMFP2.ItdefinesprofilesforDigitalEnhancedCordlessTelecommunications(DECT)systemsconformingtoEN300175parts1[1]to8[8].Itispartofafamilyofprofilesaimedatthegeneralconnectionofterminalssupportingnon-voiceservicestoafixedinfrastructure,privateandpublic.SIST EN 300 757 V1.4.1:2003

ETSIETSIEN300757V1.4.1(2002-04)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),Point-to-point(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.Figure1.1showstheprotocolsdefinedinthepresentdocument.PHLMACDLCNWKLRMSPTPLRMSPTMMMSPGSMSMSSMSSMSIWUorapplicationLRMSPTPIWUorapplicationLRMSPTMIWUorapplicationFigure1.1SIST EN 300 757 V1.4.1:2003

ETSIETSIEN300757V1.4.1(2002-04)10TheSMSorLRMSapplicationsareoutsidethescopeofthepresentdocument.SoisthenetworkbehindtheFP.AnyinformationprovidedconcerningapplicationsorthenetworkbehindtheFPisprovidedforinformative,descriptivereasonsonly.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublicationand/oreditionnumberorversionnumber)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.[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:"Digitalcellulartelecommunicationssystem(Phase2)(GSM);Point-to-Point(PP)ShortMessageService(SMS)supportonmobileradiointerface(GSM04.11)".[11]ISO/IEC8073:"Informationtechnology--OpenSystemsInterconnection--Protocolforprovidingtheconnection-modetransportservice".[12]ETSIETS300764:"DigitalEnhancedCordlessTelecommunications(DECT);GlobalSystemforMobilecommunications(GSM);DECT/GSMInterworkingProfile(IWP);Implementationofshortmessageservice,point-to-pointandcellbroadcast".[13]ETSITS101863-5:"DigitalEnhancedCordlessTelecommunications(DECT);DECT/UMTSInterworkingProfile(IWP);Part5:SMSPoint-to-PointandCellBroadcast".SIST EN 300 757 V1.4.1:2003

ETSIETSIEN300757V1.4.1(2002-04)113Definitions,symbolsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:multiframe:repeatingsequenceof16successiveTimeDivisionMultipleAccess(TDMA)frames,thatallowslowrateorsporadicinformationtobemultiplexed(e.g.basicsysteminformationorpaging)serviceclass1:localareaapplications,forwhichterminalsarepre-registeredoff-airwithoneormorespecificfixedparts,andestablishmentofserviceanduserparametersisthereforeimplicit,accordingtoaprofile-definedlistserviceclass2:privateandpublicroamingapplicationsforwhichterminalsmaymovebetweenfixedpartswithinagivendomainandforwhichassociationofserviceparametersisexplicitatthetimeofservicerequestSMS-SC:logicalentityabletostoreandforwardshortmessagesTDMAframe:time-divisionmultiplexof10msduration,containing24successivefullslotsNOTE:ATDMAframestartswiththefirstbitperiodoffullslot0andendswiththelastbitperiodoffullslot23.3.2SymbolsForthepurposesofthepresentdocument,thefollowingsymbolsapplyforprocedures,featuresifnotexplicitlyotherwises
...