SIST EN 300 943 V7.0.1:2003
(Main)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)
- Abstract
Upgrade from Phase 2+ to Release 1998
- 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 943 V7.0.1:2003 is the Slovenian adoption of ETSI EN 300 943 version 7.0.1 for GSM Release 1998. It specifies how Short Message Service Cell Broadcast (SMSCB) is supported on the GSM mobile radio interface, including the message format and scheduling information used between the network and the Mobile Station (MS).
What does SIST EN 300 943 V7.0.1:2003 specify?
SIST EN 300 943 V7.0.1:2003 specifies SMSCB support on the mobile radio interface for Teleservice 23. It focuses on how broadcast cell messages are carried, identified, scheduled, and received in GSM Phase 2+ Release 1998.
The document is organized into a scope, references, abbreviations, a general description, message format on the BTS-MS interface, and one informative annex.
| Annex | What it covers |
|---|---|
| Annex A | Sample implementation of SMSCB DRX mode on the network side and the MS side |
The end-to-end SMSCB application format is defined in GSM 03.41, while this standard concentrates on the radio-interface support needed to carry it.
What are the key requirements of SIST EN 300 943 V7.0.1:2003?
SMSCB service behavior
SIST EN 300 943 V7.0.1:2003 says SMSCB messages are broadcast from a PLMN to MSs and are not acknowledged. Reception is possible only in idle mode, so the terminal must treat SMSCB as one-way broadcast traffic rather than as a dialog service.
Clause 2 also says the message header carries the message identifier and sequence number. In practice, that is what lets an MS recognize the source and tell whether a broadcast is a new message or a repeated one.
Scheduling and DRX support
Clause 2.1 defines Schedule Messages, which tell an MS what CB messages are planned for the following schedule period. The network uses them to support SMSCB DRX, so a terminal can read only the slots it is interested in and save battery.
The schedule information is carried on both the basic and extended CBCH independently. If the network deviates from the published schedule, it must return to the schedule afterwards, which matters for predictable reception in real networks.
Block and message format
Clause 3.1 says a CB message contains 88 octets of information split into four 22-octet blocks, each with a 1-octet BlockType header. That framing is the basic over-the-air structure that implementers must parse on the CBCH.
Clause 3.3.1 defines the BlockType fields. The Link Protocol Discriminator (LPD) must be 01, the LastBlock (LB) bit marks the end of SMSCB information, and reserved sequence values are ignored. This prevents a receiver from misreading unrelated traffic or malformed blocks.
SMSCB and Schedule Message coding
Clause 3.4 says an SMSCB message uses four consecutive blocks, and a null message is indicated by sequence number 1111. Clause 3.5 says a Schedule Message also uses four consecutive blocks and may be padded with hex 2B after the used part.
Clause 3.5.1 constrains BeginSlotNumber and EndSlotNumber to the schedule period, with EndSlotNumber greater than or equal to BeginSlotNumber. That allows the MS to determine the slot range that the schedule covers and to reject invalid schedule headers.
Message descriptions and slot handling
Clauses 3.5.2 to 3.5.5 define a 48-slot bitmap and the message-description encodings that tell the MS what each slot contains. The bitmap marks new messages, repeated messages, and free slots, while the Message Description Type (MDT) distinguishes first transmissions, retransmissions, and free-message slots.
In practice, this is the part that supports efficient DRX. A terminal can skip slots marked as optional reading, read slots marked as reading advised, and use the message identifier to focus only on messages of interest.
What terms does SIST EN 300 943 V7.0.1:2003 define?
- Short Message Service Cell Broadcast (SMSCB) - A GSM service that broadcasts short messages from a PLMN to multiple MSs.
- Mobile Station (MS) - The receiving terminal that can read SMSCB messages in idle mode and use scheduling to save battery.
- Public Land Mobile Network (PLMN) - The network that broadcasts SMSCB messages and selects the geographical area for transmission.
- CB message - A message sent on the basic or extended CBCH; it can be an SMSCB message or a Schedule Message.
- Schedule Period - The time span covered by the CB messages described in one Schedule Message.
- Message Description Type (MDT) - The field that identifies whether a slot is a first transmission, retransmission, or free-message slot.
- Link Protocol Discriminator (LPD) - The BlockType field that identifies the protocol used in the block.
Who uses SIST EN 300 943 V7.0.1:2003?
SIST EN 300 943 V7.0.1:2003 is used by GSM network operators, base station and core network vendors, and mobile station manufacturers. They use it to implement SMSCB delivery, schedule broadcast slots, and control how receivers decide what to read.
Test laboratories and quality teams use it for interoperability checks on CBCH framing, scheduling behavior, and idle-mode reception. It is also relevant to engineers working on battery-saving DRX behavior in GSM terminals.
What changed in SIST EN 300 943 V7.0.1:2003 from the previous edition?
SIST EN 300 943 V7.0.1:2003 is identified as the Release 1998 version of GSM 04.12. The scope says it is an upgrade from Phase 2+ to Release 1998, and the foreword states that version 7.x.y uses the middle digit for substantive changes and the last digit for editorial changes.
Which standards are used with SIST EN 300 943 V7.0.1:2003?
| Reference | What it contributes |
|---|---|
| GSM 01.04 | Abbreviations and acronyms used in the document |
| GSM 02.03 | Teleservices supported by a GSM PLMN, including Teleservice 23 |
| GSM 03.41 | Technical realization and message format of SMSCB |
| GSM 04.04 | Layer 1 general requirements and bit transmission order |
| GSM 04.06 | MS-BSS interface data link layer; relevant to LAPDm and LPD values |
| GSM 05.02 | Multiplexing, multiple access, CBCH allocation, and timing |
What does the SIST EN 300 943 V7.0.1:2003 document contain?
The document contains the block-format rules for SMSCB messages, the Schedule Message coding, and the bit-level fields used to signal message slots. It includes figures for the 23-octet block structure, the block-type field, the 48-bit message bitmap, and the four message-description encodings.
It also includes a table for sequence-number coding and reserved values, plus the rules for null messages and padding. Annex A gives a worked sample of SMSCB DRX operation, including no-DRX, first DRX mode, and second DRX mode, which helps implementers design receiver behavior and network scheduling logic.
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 943 V7.0.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "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)". This standard covers: Upgrade from Phase 2+ to Release 1998
Upgrade from Phase 2+ to Release 1998
SIST EN 300 943 V7.0.1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.070.50 - Global System for Mobile Communication (GSM). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 943 V7.0.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 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
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
...