ETSI EN 300 943 V7.0.1 (2000-01)
Digital cellular telecommunications system (Phase 2+) (GSM); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface (GSM 04.12 version 7.0.1 Release 1998)
Digital cellular telecommunications system (Phase 2+) (GSM); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface (GSM 04.12 version 7.0.1 Release 1998)
REN/SMG-030412Q7
Digitalni celični telekomunikacijski sistem (faza 2+) – Podpora celične radiodifuzije storitev kratkih sporočil (SMSCB) pri mobilnem radijskem vmesniku (GSM 04.12, različica 7.0.1, izdaja 1998)
General Information
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); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface (GSM 04.12 version 7.0.1 Release 1998)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)ICS:Ta slovenski standard je istoveten z:EN 300 943 Version 7.0.1SIST EN 300 943 V7.0.1:2003en01-december-2003SIST EN 300 943 V7.0.1:2003SLOVENSKI
STANDARD
SIST EN 300 943 V7.0.1:2003
ETSIEN300943V7.0.1(2000-01)EuropeanStandard(Telecommunicationsseries)Digitalcellulartelecommunicationssystem(Phase2+);ShortMessageServiceCellBroadcast(SMSCB)supportonthemobileradiointerface(GSM04.12version7.0.1Release1998)GLOBALSYSTEMFORMOBILECOMMUNICATIONSRSIST EN 300 943 V7.0.1:2003
ETSIETSIEN300943V7.0.1(2000-01)2(GSM04.12version7.0.1Release1998)ReferenceREN/SMG-030412Q7KeywordsDigitalcellulartelecommunicationssystem,GlobalSystemforMobilecommunications(GSM)ETSIPostaladdressF-06921SophiaAntipolisCedex-FRANCEOfficeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88Internetsecretariat@etsi.frIndividualcopiesofthisETSIdeliverablecanbedownloadedfromhttp://www.etsi.orgIfyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frImportantnoticeThisETSIdeliverablemaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.CopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 943 V7.0.1:2003
ETSIETSIEN300943V7.0.1(2000-01)3(GSM04.12version7.0.1Release1998)ContentsIntellectualPropertyRights.4Foreword.41Scope.51.1References.51.2Abbreviations.52Generaldescription.52.1SchedulingInformation.63MessageformatonBTS-MSInterface.63.1General.63.2Formatconvention.73.2.1Numberingconvention.73.2.2Orderofbittransmission.73.3Blockcontent.73.3.1BlockType.73.4SMSCBMessage.83.5ScheduleMessage.83.5.1Header.93.5.2NewCBSMSMessageBitmap.93.5.3NewCBSMSMessageDescription.93.5.4OtherMessageDescriptions.103.5.5Messagedescriptionencoding.103.5.5.1FirsttransmissionofanSMSCBwithintheSchedulePeriod.103.5.5.2Retransmissionindication.113.5.5.3FreeMessageSlot,optionalreading.113.5.5.4FreeMessageSlot,readingadvised.113.5.5.5ReservedCodepoints.11AnnexA(informative):SampleImplementationofSMSCBDRXMode.12History.14SIST EN 300 943 V7.0.1:2003
ETSIETSIEN300943V7.0.1(2000-01)4(GSM04.12version7.0.1Release1998)IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbytheSpecialMobileGroup(SMG).ThepresentdocumentdescribeshowtheShortMessageServiceCellBroadcast(SMSCB)issupportedoverthemobileradiointerfacewithinthedigitalcellulartelecommunicationssystem(Phase2+).ThecontentsofthepresentdocumentissubjecttocontinuingworkwithinSMGandmaychangefollowingformalSMGapproval.ShouldSMGmodifythecontentsofthepresentdocument,itwillbere-releasedwithanidentifyingchangeofreleasedateandanincreaseinversionnumberasfollows:Version7.x.ywhere:7indicatesRelease1998ofGSMPhase2+.xtheseconddigitisincrementedforallchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.ythethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthespecification.ThespecificationfromwhichthepresentdocumenthasbeenderivedwasoriginallybasedonCEPTdocumentation,hencethepresentationofthepresentdocumentmaynotbeentirelyinaccordancewiththeETSIdraftingrules.NationaltranspositiondatesDateofadoptionofthisEN:31December1999DateoflatestannouncementofthisEN(doa):31March2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):30September2000DateofwithdrawalofanyconflictingNationalStandard(dow):30September2000SIST EN 300 943 V7.0.1:2003
ETSIETSIEN300943V7.0.1(2000-01)5(GSM04.12version7.0.1Release1998)1ScopeThepresentdocumentdescribeshowtheShortMessageServiceCellBroadcast(SMSCB)(Teleservice23asspecifiedinGSM02.03)issupportedoverthemobileradiointerface.1.1ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.•Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.•Foraspecificreference,subsequentrevisionsdonotapply.•Foranon-specificreference,thelatestversionapplies.•Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.•ForthisRelease1998document,referencestoGSMdocumentsareforRelease1998versions(version7.x.y).[1]GSM01.04:"Digitalcellulartelecommunicationsystem(Phase2+);Abbreviationsandacronyms".[2]GSM02.03:"Digitalcellulartelecommunicationsystem(Phase2+);TeleservicessupportedbyaGSMPublicLandMobileNetwork(PLMN)".[3]GSM03.41:"Digitalcellulartelecommunicationsystem(Phase2+);TechnicalrealizationofShortMessageServiceCellBroadcast(SMSCB)".[4]GSM04.04:"Digitalcellulartelecommunicationsystem;layer1Generalrequirements".[5]GSM04.06:"Digitalcellulartelecommunicationsystem;MobileStation-BaseStationSystem(MS-BSS)interfaceDataLink(DL)layerspecification".[6]GSM05.02:"Digitalcellulartelecommunicationsystem(Phase2+);Multiplexingandmultipleaccessontheradiopath".1.2AbbreviationsAbbreviationsusedinthepresentdocumentarelistedinGSM01.04.2GeneraldescriptionSMSCBisaserviceinwhichshortmessagesmaybebroadcastfromaPLMNtoMobileStations(MS)s.SMSCBmessagescomefromdifferentsources(e.g.trafficreports,weatherreports).ThesourceandsubjectoftheSMSCBmessageisidentifiedbyamessageidentifierintheSMSCBmessageheader.AsequencenumberintheSMSCBmessageheaderenablestheMStodeterminewhenanewmessagefromagivensourceisavailable.SMSCBmessagesarenotacknowledgedbytheMS.ReceptionofSMSCBmessagesbytheMSisonlypossibleinidlemode.ThegeographicalareaoverwhicheachSMSCBmessageistransmittedisselectedbythePLMNoperator,byagreementwiththeprovideroftheinformation.ASMSCBmessageisanend-to-endmessagethatisformattedby/fortheSMSCBapplication,andwhichisintendedforcustomerviewing.ItsformatisdescribedindetailinGSM03.41.ACBmessageisanymessagesentonthebasicorextendedCBCH(seeGSM05.02).ItcanbeanoccurrenceofaSMSCBmessage,oraschedulemessage.SIST EN 300 943 V7.0.1:2003
ETSIETSIEN300943V7.0.1(2000-01)6(GSM04.12version7.0.1Release1998)TheSMSCellBroadcastserviceisdesignedtominimizethebatteryusagerequirementsforaMS.AMScanreadthefirstpartofaCBmessageandthendecidewhetherornottoreadtherestofthemessage.Inaddition,thenetworkmaybroadcastScheduleMessages,providinginformationinadvanceabouttheCBmessagesthatwillbesentimmediatelyafterwards.TheMSmayusethisschedulinginformationtorestrictreceptiontothosemessagesthecustomerisinterestedinreceiving.ThisSMSCBDRXfeatureisoptionalinthenetworkandtheMS.2.1SchedulingInformationThenetworksupportingtheSMSCBDRXfeaturetransmitsScheduleMessages.AScheduleMessageincludesinformationaboutanumberofimmediatelyfollowingconsecutiveCBmessages,plannedforthatcell.ThelengthoftimecoveredbytheCBmessagesreferredtoinaScheduleMessageiscalledtheSchedulePeriodofthatmessage.ForoptimumDRX,anewScheduleMessageshouldfollowthelastmessageofaSchedulePeriod.WhennoinformationisknownaboutaCBmessage,e.g.,becausenoScheduleMessagehasbeenreceivedreferringtothatCBmessage,aMSshallread(atleast)thefirstpartoftheCBmessage.ScheduleMessagesshallbesentonthebasicandextendedCBCHindependently.Thenetworkmayoverridethepublishedscheduletotransmitnewhigh-prioritySMSCBmessages.However,afteranyscheduledeviation,thenetworkshallresumetheschedule,bytransmittingthescheduledCBmessagesatthescheduledtimeslistedintheScheduleMessage.TheScheduleMessagecontainsaMessageDescriptionforeachCBmessagetobebroadcastduringtheschedulingperiod,inorderoftransmission.ThepositionofaCBmessageiscalledthe"messageslotnumber"oftheCBmessage,anditindicatesthepositionoftheCBmessagewithinthescheduleperiod.EachMessageDescriptionincludesvariousinformation,includingforSMSCBmessagesdirectlyorindirectlyallorpartoftheirmessageidentifier,andwhetheranoccurrenceisarepetitionornot.EachScheduleMessageincludesaBeginSlotNumberfieldandanEndSlotNumberfield.TheEndSlotNumberfieldindicatesthelengthofthescheduleperiod(i.e.,specificallythenumberofCBmessageslotsaboutwhichinformationisprovided).InthecasewherethenetworkusesScheduleMessagestodescribeallmessageslotsinadvance,thefirstScheduleMessageofthenextscheduleperiodwillbetransmittedinthemessageslotpointedbyEndSlotNumberplus1.TheBeginSlotNumberisdefinedtoallowthenetworktobroadcastseveralScheduleMessagesreferringtothesamescheduleperiod.TheBeginSlotNumberfieldindicatesthemessageslotnumberoftheCBmessagefollowingthereceivedScheduleMessage.ThenetworksmaysendunscheduledScheduleMessagesduringemptymessageslots.ThenetworkneedonlyupdatetheBeginSlotNumberinanunscheduledScheduleMessagetoreflectthecurrentoffsetwithintheScheduleMessageofthenextmessagetobetransmitted.3MessageformatonBTS-MSInterface3.1GeneralACBmessageconsistsofa88octetsofinformation.The88octetblockissegmentedintofour22octetblocks.A1octetBlocktypeisaddedasaheadertoeach22octetblock.Theoverallblocksarethus23octetsinlength.ThemessageblocksaresentonthechannelallocatedasCBCHbyGSM05.02.ThetimingofthemessagesisdefinedinGSM05.02.Ifthenetworkhasnocellbroadcastinformationtotransmit,thenitmaychoosetotransmitanullmessage.SIST EN 300 943 V7.0.1:2003
ETSIETSIEN300943V7.0.1(2000-01)7(GSM04.12version7.0.1Release1998)3.2Formatconvention3.2.1NumberingconventionThebasicconventionusedinthistechnicalspecificationisillustratedinfigure1.Thebitsaregroupedintooctets.Thebitsofanoctetareshownhorizontallyandarenumberedfrom1to8.Multipleoctetsareshownverticallyandarenumberedfrom1to23.87654321Octet:1223Figure1/GSM04.12:Formatconvention3.2.2OrderofbittransmissionThemessageblocksaresentontheCBCHasdefinedinGSM05.02usingthecodingdefinedforthatchannel.TheorderofbittransmissionisdefinedinGSM04.04.3.3BlockcontentThe23octetblocksarecodedasfollows:87654321Octet:Blocktype12Information23Figure2/GSM04.12:Blockcontent3.3.1BlockTypeThepurposeoftheBlockTypeistoidentifythefunctionoftheblockandmessagebeingsent.Theblocktypeiscodedasshowninfigure3/GSM04.12.87654321Octet:SpareLPDLBSequenceNumber1001Figure3/GSM04.12:Blockty
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.