SIST EN 300 949 V7.1.1:2003
(Main)Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (GSM 04.69 version 7.1.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
- Mandate
- UIC
SIST EN 300 949 V7.1.1:2003 is the Slovenian adoption of ETSI EN 300 949 V7.1.1 for GSM Release 1998. It specifies the Broadcast Call Control (BCC) protocol for the Voice Broadcast Call Service (VBCS) on the GSM radio interface, defining how the mobile station and the network establish, control, monitor, and end a broadcast call.
What does SIST EN 300 949 V7.1.1:2003 specify?
SIST EN 300 949 V7.1.1:2003 specifies the BCC protocol used by VBCS on the radio interface. It covers the protocol between one BCC entity in the network and one or more BCC entities in mobile stations, with optional support in both MS and network.
The document is organized into:
- scope and references
- definitions and abbreviations
- applicability and main concepts
- elementary procedures
- handling of unknown, unforeseen, and erroneous protocol data
- message functional definitions and contents
- coding of information element value parts
- informative Annex A with change request history
This structure matters in practice because implementers need both the call-control procedures and the exact message coding to interoperate correctly.
What are the key requirements of SIST EN 300 949 V7.1.1:2003?
SIST EN 300 949 V7.1.1:2003 defines BCC as a stateful signalling protocol. The key practical point is that the right message depends on the current state, the originator role, and whether the MS has attached the user connection in the downlink or uplink.
State control and protocol roles
Clause 6 describes the BCC entity in the MS as an extended finite state machine, with states such as NULL, BROADCASTCALLINITIATED, BROADCASTCALLACTIVE, BROADCASTCALLPRESENT, BROADCASTCALLCONNECTIONREQUESTED, TERMINATIONREQUESTED, and RECEIVEMODEACTIVE. The network side has its own state set. This matters because implementers must keep MS and network behaviour aligned to the current call phase.
Establishment procedures
Clause 6.2 covers network activation and mobile-originated and mobile-terminating establishment. The MS can start a broadcast call with SETUP after an MM connection is established, or with IMMEDIATESETUP without prior explicit MM connection setup. In practice, this tells equipment whether to build the call through explicit or implicit MM connection handling.
Call identity and originator handling
The originator chooses the Transaction Identifier (TI), and a non-originating MS uses the network TI value with the specified flag handling. The CONNECT message confirms establishment and includes the broadcast call reference and originator indication. This is important for correct transaction tracking and for knowing which MS started the call.
Release, abort, and termination
Clause 6.4 defines TERMINATIONREQUEST, TERMINATION, and TERMINATIONREJECT. The originating MS can request termination, the network can accept or reject it, and either side can trigger abort or release through lower layers. This tells operators and equipment vendors how a broadcast call is closed and how context is cleared.
Status and parameter procedures
Clause 6.5 defines GETSTATUS and SETPARAMETER. GETSTATUS elicits a STATUS response when communication is enabled, and STATUS carries the current call state, parameter values, and a cause. SETPARAMETER is only acted on when the requested values are consistent with the current state. This supports supervision and controlled reconfiguration during a live call.
Error handling
Clause 7 gives the rules for short messages, unknown transaction identifiers, unknown message types, mandatory IE errors, and semantically incorrect contents. The COMM parameter decides whether the MS ignores the message or replies with STATUS and a cause. This is the main compatibility mechanism for future extensions and for robust receiver behaviour.
What terms does SIST EN 300 949 V7.1.1:2003 define?
- BCC (Broadcast Call Control) - The protocol that controls broadcast calls between the network and MS entities.
- VBCS (Voice Broadcast Call Service) - The GSM service that uses BCC to support voice broadcast calling.
- Broadcast call channel - The downlink channel allocated in each cell for a specific broadcast call.
- ORIG - A behaviour parameter showing whether the MS acts as the call originator.
- COMM - A behaviour parameter showing whether communication with the peer entity is enabled in both directions.
- D-ATT - A configuration parameter that shows whether the MS attaches the broadcast call user connection in the downlink.
- U-ATT - A configuration parameter that shows whether the MS attaches the broadcast call user connection in the uplink.
- TMSI / IMSI - Identifiers used in Mobileidentity, with TMSI preferred if available and IMSI used otherwise.
Who uses SIST EN 300 949 V7.1.1:2003?
SIST EN 300 949 V7.1.1:2003 is used by GSM system designers, radio interface protocol engineers, and mobile equipment vendors implementing broadcast call support. It is also relevant to network operators, integration teams, and test labs that need to verify BCC message exchange, state handling, and error responses. Buyers and quality managers use it to check whether a product supports VBCS broadcast call signalling at the protocol level.
What changed in SIST EN 300 949 V7.1.1:2003 from the previous edition?
Annex A records the change request history leading to version 7.1.1. It shows updates to the GetStatus and SetStatus procedures, broadcast call control states and state attributes, coding of CallReference IE, the reject cause in TERMINATIONREJECT, a message name correction, and the version update for publication.
Which standards are used with SIST EN 300 949 V7.1.1:2003?
- GSM01.04 - Supplies abbreviations and acronyms used by the document.
- GSM02.69 - Defines VBCS stage 1.
- GSM03.03 - Defines numbering, addressing, and identification, used for broadcast call reference and related identity coding.
- GSM03.67 - Covers enhanced Multi-Level Precedence and Pre-emption service (eMLPP) stage 2.
- GSM03.69 - Defines VBCS stage 2.
- GSM04.06 - Defines the MS-BSS data link layer.
- GSM04.07 - Defines layer 3 general aspects, message structure, and error handling rules.
- GSM04.08 - Defines the mobile radio interface layer 3 specification, including MM and RR behaviour and several referenced information elements.
What does the SIST EN 300 949 V7.1.1:2003 document contain?
The document contains text-based state machines for MS and network behaviour, a timer table, and step-by-step procedures for call establishment, active-call operation, release, abort, and termination. It also includes the full message definitions for CONNECT, GETSTATUS, IMMEDIATESETUP, SETPARAMETER, SETUP, STATUS, TERMINATION, TERMINATIONREJECT, and TERMINATIONREQUEST.
Clause 9 gives the coding rules for the value parts of information elements, including ProtocolDiscriminator, Transactionidentifier, MessageType, CallReference, Callstate, Cause, Originatorindication, SpareHalfOctet, and Stateattributes. Annex A provides the change request history that explains the evolution of the specification.
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 949 V7.1.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (GSM 04.69 version 7.1.1 Release 1998)". This standard covers: Upgrade from Phase 2+ to Release 1998
Upgrade from Phase 2+ to Release 1998
SIST EN 300 949 V7.1.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 949 V7.1.1:2003 is associated with the following European legislation: Standardization Mandates: UIC. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST EN 300 949 V7.1.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.NUPLOMHQMDDigital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (GSM 04.69 version 7.1.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 949 Version 7.1.1SIST EN 300 949 V7.1.1:2003en01-december-2003SIST EN 300 949 V7.1.1:2003SLOVENSKI
STANDARD
ETSIEN300949V7.1.1(2000-04)EuropeanStandard(Telecommunicationsseries)Digitalcellulartelecommunicationssystem(Phase2+);BroadcastCallControl(BCC)protocol(GSM04.69version7.1.1Release1998)GLOBALSYSTEMFORMOBILECOMMUNICATIONSRSIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)2(GSM04.69version7.1.1Release1998)ReferenceREN/SMG-030469Q7R1KeywordsDigitalcellulartelecommunicationssystem,GlobalSystemforMobilecommunications(GSM)ETSI650RoutedesLuciolesF-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.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)3(GSM04.69version7.1.1Release1998)ContentsIntellectualPropertyRights.5Foreword.51Scope.62References.63Definitionsandabbreviations.63.1Definitions.63.2Abbreviations.74Applicability.75Mainconcepts.76ElementaryproceduresforBroadcastCallControl.86.1Overview.86.1.1General.86.1.2Broadcastcallcontrolstates.86.1.2.1BroadcastcallcontrolstatesattheMSsideoftheinterface.86.1.2.1.1AttributesandParametersofBCCintheMS.86.1.2.1.2NULL(U0).96.1.2.1.3MMCONNECTIONPENDING(U0.p).96.1.2.1.4BROADCASTCALLINITIATED(U1).96.1.2.1.5BROADCASTCALLACTIVE(U2).96.1.2.1.6BROADCASTCALLPRESENT(U3).96.1.2.1.7BROADCASTCALLCONNECTIONREQUESTED(U4).96.1.2.1.8TERMINATIONREQUESTED(U5).96.1.2.1.9RECEIVEMODEACTIVE(U6).96.1.2.1.10BCCTIMERSINTHEMS.106.1.2.1.11CONSISTENCYOFPARAMETERSANDSTATES.106.1.2.2BROADCASTCALLCONTROLSTATESATTHENETWORKSIDEOFTHEINTERFACE.106.1.2.2.1NULL(StateN0).106.1.2.2.2BROADCASTCALLINITIATED(N1).106.1.2.2.3BROADCASTCALLACTIVE(N2).116.1.2.2.4BROADCASTCALLESTABLISHMENTPROCEEDING(N3).116.1.2.2.5TERMINATIONREQUESTED(N4).116.2Proceduresforestablishmentofabroadcastcall.116.2.1Activationofabroadcastcallbythenetwork.116.2.2Mobileoriginatedestablishment.116.2.2.1Terminationduringmobileoriginatedestablishment.126.2.2.2Abnormalcases.126.2.3MobileterminatingbroadcastcallestablishmentintheMS.126.3Proceduresduringtheactivestateandreceivemodeactivestateofabroadcastcall.126.3.1Mobilestationproceduresintheactivestate.126.3.2Networkproceduresintheactivestate.136.3.3MobilestationproceduresintheRECEIVEMODEACTIVEstate.136.4Proceduresforrelease,abortion,andterminationofabroadcastcall.136.4.1Terminationprocedure.136.4.2Abortandreleaseprocedures.146.5Miscellaneousprocedures.146.5.1Statusprocedures.146.5.1.1Getstatusprocedure.146.5.1.2Setparameterprocedure.147Handlingofunknown,unforeseen,anderroneousprotocoldata.147.1General.147.2Messagetooshort.157.3Unknownorunforeseentransactionidentifier.15SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)4(GSM04.69version7.1.1Release1998)7.4Unknownorunforeseenmessagetype.157.5Non-semanticalmandatoryinformationelementerrors.157.6Unknownandunforeseeninformationelementsinthenon-imperativemessagepart.167.6.1Informationelementsunknowninthemessage.167.6.2Outofsequenceinformationelements.167.6.3RepeatedInformationelements.167.7Non-imperativemessageparterrors.167.7.1SyntacticallyincorrectoptionalInformationelements.167.8Messageswithsemanticallyincorrectcontents.168Messagefunctionaldefinitionsandcontents.168.1CONNECT.178.2GETSTATUS.188.2.1mobileidentity.188.3IMMEDIATESETUP.188.3.1Mobileidentity.198.4SETPARAMETER.198.5SETUP.198.6STATUS.208.6.1Callstate.208.6.2Stateattributes.208.7TERMINATION.218.8TERMINATIONREJECT.218.9TERMINATIONREQUEST.219Contentsofinformationelementsvalueparts.229.1ProtocolDiscriminator.229.2Transactionidentifier.229.3MessageType.229.4Otherinformationelements.229.4.1CallReference.239.4.2Callstate.239.4.3Cause.249.4.4Originatorindication.259.4.5SpareHalfOctet.269.4.6Stateattributes.26AnnexA(Informative):ChangeRequestHistory.27History.28SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)5(GSM04.69version7.1.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).ThepresentdocumentspecifiestheBroadcastCallControl(BCC)protocolwithinthedigitalcellulartelecommunicationssystem(Phase2+).ThecontentsofthepresentdocumentissubjecttocontinuingworkwithinSMGandmaychangefollowingformalSMGapproval.ShouldSMGmodifythecontentsofthepresentdocumentitwillbere-releasedwithanidentifyingchangeofreleasedateandanincreaseinversionnumberasfollows:Version7.x.ywhere:7indicatesRelease1998ofGSMPhase2+.xtheseconddigitisincrementedforallchangesofsubstance,i.e.technicalenhancements,corrections,updates,etc.ythethirddigitisincrementedwheneditorialonlychangeshavebeenincorporatedinthespecification.NationaltranspositiondatesDateofadoptionofthisEN:31March2000DateoflatestannouncementofthisEN(doa):30June2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31December2000DateofwithdrawalofanyconflictingNationalStandard(dow):31December2000SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)6(GSM04.69version7.1.1Release1998)1ScopeThepresentdocumentspecifiestheBroadcastCallControl(BCC)protocolusedbytheVoiceBroadcastCallService(VBCS)ontheradiointerface.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.• ForthisRelease1998document,referencestoGSMdocumentsareforRelease1998versions(version7.x.y).[1]GSM01.04:"Digitalcellulartelecommunicationssystem(Phase2+);Abbreviationsandacronyms".[2]GSM02.69):"Digitalcellulartelecommunicationssystem(Phase2+);VoiceBroadcastCallService(VBCS)stage1".[3]GSM03.03:"Digitalcellulartelecommunicationssystem(Phase2+);Numbering,addressingandidentification".[4]GSM03.67:"Digitalcellulartelecommunicationssystem(Phase2+);enhancedMulti-LevelPrecedenceandPre-emptionservice(eMLPP)-Stage2".[5]GSM03.69:"Digitalcellulartelecommunicationssystem(Phase2+);VoiceBroadcastCallService(VBCS)stage2".[6]GSM04.06:"Digitalcellulartelecommunicationssystem(Phase2+);MobileStation-BaseStationSystem(MS-BSS)interfaceDataLink(DL)layerspecification".[7]GSM04.07:"Digitalcellulartelecommunicationssystem(Phase2+);Mobileradiointerfacesignallinglayer3Generalaspects".[8]GSM04.08:"Digitalcellulartelecommunicationssystem(Phase2+);Mobileradiointerfacelayer3specification".3Definitionsandabbreviations3.1DefinitionsDefinitionsusedinthepresentdocumentarealsodefinedinGSM02.69.Forthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply.Attachmentoftheuserconnection:SeeGSM04.08,subclause5.2.Broadcastcallchannel:Downlinkchanneltobeallocatedineachcellofthegroupcallareaforaparticularbroadcastcall.AllMSsofthelisteningservicesubscribersinonecellshalllistentothecommondownlink.SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)7(GSM04.69version7.1.1Release1998)Broadcastcall:Isusedinthesamesenseas"voicebroadcastcall".Callinguser:BCCentityintheMobileStation(MS)initiatingorhavinginitiatedabroadcastcall.Clearingthecontextrelatedtothebroadcastcallestablishment:allrunningBCCtimersintherelevantBCCentityarestopped,allattributesintherelevantBCCentityaredeleted.Downlink:NetworktoMSdirection.Groupreceivemode:SeeGSM04.08.Originatingmobilestation:MSinitiatingorhavinginitiatedthebroadcastcall.Uplink:Mobilestationtonetworkdirection.3.2AbbreviationsAbbreviationsusedinthepresentdocumentarealsolistedinGSM01.04.Forthepurposesofthepresentdocument,thefollowingabbreviationapplies:BCCBroadcastCallControl.4ApplicabilitySupportofthebroadcastcallprotocolisoptionalintheMSandinthenetwork.5MainconceptsThepresentdocumentdescribesthebroadcastcallcontrol(BCC)protocol,whichisoneoftheprotocolsoftheConnectionManagement(CM)sublayer(seeGSM04.07).ThereisingeneralmorethanoneMSengagedinabroadcastcall.Consequently,thereisingeneralmorethanoneMSwithaBCCentityengagedinthesamebroadcastcall,andthereisoneBCCentityinthenetworkengagedinthatbroadcastcall.UnderwhichconditionsaBCCmessageispassedfromlower(sub-)layerstotheBCCentityisdefinedinthespecificationsofthesub-layers.TheMSshallignoreBCCmessagesthatitreceiveswhichweresentinunacknowledgedmodeandwhichexplicitlyspecifyasdestinationamobileidentitywhichisnotamobileidentityoftheMS.HigherlayersandtheMMsub-layerdecidewhentoacceptparallelBCCtransactionsandwhen/whethertoacceptBCCtransactionsinparalleltootherCMtransactions.Thebroadcastcallmaybeinitiatedbyamobileuserorbyadispatcher.Specificationofaprotocolfordispatchersisoutofthescopeofthepresentdocument.Hence,inthescopeofthepresentdocument,thereare-oneBCCentityinthenetwork;and-oneormorethanoneBCCentitiesindifferentMSsengagedinabroadcastcall,andoneorenoneoftheMSsistheoriginatorofthebroadcastcall(calledtheoriginatingMSinthisETS).NOTE:WhereasfortheGroupCallControl(GCC)protocol(seeGSM04.68),incertainsituations,theGCCentityinaMSassumestobetheoriginatorofabroadcastcallwithoutbeingtheoriginator,thisisnotthecasefortheBCCprotocol.SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)8(GSM04.69version7.1.1Release1998)TheoriginatoroftheBCCtransactionchoosestheTransactionIdentifier(TI).AMSnotassumingtobetheoriginatorofthetransactionwillchosethetransactionidentifierreceivedfromthenetwork,settingtheTIflagto1+xmod2wherexisthereceivedTIflag.ThisETSdescribesthebroadcastcallcontrolprotocolonlywithregardtotwopeerentities,oneinaMS,theotheroneinthenetwork.Thecallcontrolentitiesaredescribedascommunicatingfinitestatemachineswhichexchangemessagesacrosstheradiointerfaceandcommunicateinternallywithotherprotocol(sub)layers.Inparticular,theBCCprotocolusestheMMandRRsublayerspecifiedinGSM04.08.TheBCCentityinaMSthatisnottheoriginatorofthebroadcastcallshallnotsendmessagestoitspeerentity.Thisdescriptioninonlynormativeasfarastheconsequentialexternallyobservablebehaviourisconcerned.Forsimplicity,insteadofusingtheterms"BCCentityintheMS"and"BCCentityinthenetwork",thepresentdocumentoftenusestheterms"MS"and"network"ifnoconfusionmayarise.Certainsequencesofactionsofthetwopeerentitiescompose"elementaryprocedures"whichareusedasabasisforthedescriptioninthepresentdocument.Theseelementaryproceduresaredefinedinclause6.ThenetworkshouldapplysupervisoryfunctionstoverifythattheBCCproceduresareprogressingandifnot,takeappropriatemeanstoresolvetheproblems.This,however,isoutofthescopeofthepresentdocument.6ElementaryproceduresforBroadcastCallControl6.1Overview6.1.1GeneralTheelementaryproceduresmaybebroadcastedintothefollowingclasses:-broadcastcallestablishmentprocedures;-broadcastcallterminationprocedures;-broadcastcallinformationphaseprocedures;-miscellaneousprocedures.6.1.2Broadcastcallcontrolstates6.1.2.1BroadcastcallcontrolstatesattheMSsideoftheinterfaceTheBCCentityoftheMSisdescribedasanextendedfinitestatemachine.Itperformstransitionsbetweenstates.Ithascertainparametersandattributes,e.g.configurationparametersandbehaviourparameters,whichitsetsandchangesbasedoninteractionwithhigherandlower(sub-)layersandonmessageexchangewithitspeerentity.Ifaconfigurationparameterissettoacertainvalue,theMSshallalsoadapttheconfigurationaccordingly.Behaviourparametersdecideon(partof)thebehaviouroftheBCCentity.WhentheBCCentityintheMSreceivesamessage,itshallfirstanalysewhetheritshallignorethemessage,seeclauses5and7.6.1.2.1.1AttributesandParametersofBCCintheMSForthefollowingbehaviourparameters,thedescriptionisinformative.ParameterDescriptionORIGDependingonthecontext,theMSassumestobetheoriginatorofthecall(ORIG=T)ornottobetheoriginatorofthecall(ORIG=F).COMMDependingonthecontext,theMSassumesthatcommunicationwithitspeerentityisenabledinbothdirections(COMM=T)ornot(COMM=F).ForthefollowingconfigurationparameterstheMSshalladaptitsconfigurationaccordingtotheparametervalueandparameterdefinition.SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)9(GSM04.69version7.1.1Release1998)ParameterDefinitionD-ATTD-ATT=TmeansthattheMSattachestheuserconnectionforthebroadcastcallinthedownlink.D-ATT=FmeansthattheMSdoesnotattachtheuserconnectionforthebroadcastcallinthedownlink.U-ATTU-ATT=TmeansthattheMSattachestheuserconnectionforthebroadcastcallintheuplink.U-ATT=FmeansthattheMSdoesnotattachtheuserconnectionforthebroadcastcallintheuplink.6.1.2.1.2NULL(U0)NobroadcastcallexistsfortheBCCentity.Whenenteringthestate,parametersshallbesettothefollowingvalues,andconfigurationshallbeadaptedtothenewvaluesofconfigurationparameters:ORIG=F,COMM=F,D-ATT=F,U-ATT=F.6.1.2.1.3MMCONNECTIONPENDING(U0.p)TheBCCentityhasrequestedtheexplicitestablishmentofanMMconnection.Whenenteringthestate,parametersshallbesettothefollowingvalues,andconfigurationshallbeadaptedtothenewvaluesofconfigurationparameters:ORIG=T,COMM=F,D-ATT=F,U-ATT=F.6.1.2.1.4BROADCASTCALLINITIATED(U1)TheBCCentityhasrequestedthepeerentityinthenetworktoestablishabroadcastcall.Whenenteringthestate,parametersshallbesettothefollowingvalues,andconfigurationshallbeadaptedtothenewvaluesofconfigurationparameters:ORIG=T,COMM=T,D-ATT=F,U-ATT=F.6.1.2.1.5BROADCASTCALLACTIVE(U2)Thebroadcastcallisestablishedatleastinonecell.Whenenteringthestate,parametersshallbesettothefollowingvalues,andconfigurationshallbeadaptedtothenewvaluesofconfigurationparameters:ORIG=T,COMM=T,D-ATT=T,U-ATT=T.6.1.2.1.6BROADCASTCALLPRESENT(U3)TheMShasreceivedanotificationaboutanongoingbroadcastcall.Higherlayersarerequestedtoacceptorrejectthecall.Whenenteringthestate,parametersshallbesettothefollowingvalues,andconfigurationshallbeadaptedtothenewvaluesofconfigurationparameters:ORIG=F,COMM=F,D-ATT=F,U-ATT=F.6.1.2.1.7BROADCASTCALLCONNECTIONREQUESTED(U4)TheMShasreceivedanotificationaboutanongoingbroadcastcall.Higherlayershavedecidedtoacceptthecall.Whenenteringthestate,parametersshallbesettothefollowingvalues,andconfigurationshallbeadaptedtothenewvaluesofconfigurationparameters:ORIG=F,COMM=F,D-ATT=F,U-ATT=F.6.1.2.1.8TERMINATIONREQUESTED(U5)TheMSwhichistheoriginatorofthebroadcastcallhasbeeninstateU1orU2andhassentaTERMINATIONREQUESTmessagetothenetwork.Whenenteringthestate,parametersshallbesettothefollowingvalues,andconfigurationshallbeadaptedtothenewvaluesofconfigurationparameters:ORIG=T,COMM=T,D-ATT=T,U-ATT=T.6.1.2.1.9RECEIVEMODEACTIVE(U6)TheBCCentityintheMSinstateU4,BROADCASTCALLCONNECTIONREQUESTED,hasgotanindicationfromlower(sub-)layersthatRRhasenteredgroupreceivemode(seeGSM04.08).Whenenteringthestate,parametersshallbesettothefollowingvalues,andconfigurationshallbeadaptedtothenewvaluesofconfigurationparameters:ORIG=F,COMM=F,D-ATT=T,U-ATT=F.SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)10(GSM04.69version7.1.1Release1998)6.1.2.1.10BCCTIMERSINTHEMSTable6.1specifiesthetimersusedinBCC.Thedenotationofcolumnsisdefinedasfollows:timer::=nameofthetimer;set::=underwhichconditionsthetimerisset(i.e.,started);stopped::=underwhichconditionsthetimerisstopped;runninginstate(s)::=inwhichstate(s)thetimermayberunning;actionatexpiry::=whichactionstheBCCentityshallperformatexpiry;value::=thedurationbetweensettingthetimerandexpiryofthetimer("s"denotes"second(s)""xx-yy"meansthatanyvaluebetweenxxandyyispermitted).Table6.1:SpecificationoftimersusedinBCCtimersetstoppedrunninginstate(s)actionatexpiryvalueTnochannelinstateU6onreceiptofanindicationfromlower(sub-)layersthatnochanneliscurrentlyavailablewhenleavingU6orwhenreceivinginU6anindicationfromlower(sub-)layersthatachannelisavailableinU6,dependingonfurtherconditionsseesubclause6.3.13sTMM-estwhenenteringU0.pusingtheset-upprocedurewhenenteringU1usingtheimmediateset-upprocedurewhenleavingU0.porU1U0.p,U1seesubclause6.2.15sTtermwhensendingaTERMINATIONREQUESTwhenreceivingaTERMINATIONorTERMINATIONREJECTU5abortbroadcastcall10sTconnreqwhenenteringstateU4whenleavingstateU4U4abortbroadcastcall10-30s6.1.2.1.11CONSISTENCYOFPARAMETERSANDSTATESTheMSshallconsiderthefollowingparametervaluesasinconsistentwiththestateorsub-state:ORIG=TisinconsistentwithstatesU3,U4,andU6.COMM=TisinconsistentwithstatesU0,U3,U4,andU6.AllothervaluesofparametersORIG,COMM,D-ATT,andU-ATTshallnotbeconsideredbytheMSasinconsistentwithastate.6.1.2.2BROADCASTCALLCONTROLSTATESATTHENETWORKSIDEOFTHEINTERFACE6.1.2.2.1NULL(StateN0)NobroadcastcallexistsfortheBCCentity.6.1.2.2.2BROADCASTCALLINITIATED(N1)TheBCCentityhasreceivedtheindicationthatapeerentityinaMSwantstoestablishabroadcastcallforacertainbroadcastidentity.SIST EN 300 949 V7.1.1:2003
ETSIETSIEN300949V7.1.1(2000-04)11(GSM04.69version7.1.1Release1998)6.1.2.2.3BROADCASTCALLACTIVE(N2)Thebroadcastcallisestablishedinatleastonecell;theremaybeaMSwhichhasseizedtheuplinkornot;theremaybetalkingdispatchersornot.6.1.2.2.4BROADCASTCALLESTABLISHMENTPROCEEDING(N3)TheBCCentitywantstoacceptthebroadcastcall,hasinitiatedestablishmentofcorrespondingbroadcastcallchannels,and,ifthereisacallinguser.hassentaCONNECTmessagetothecallinguser.6.1.2.2.5TERMINATIONREQUESTED(N4)TheBCCentityhasaskedlowersub-layerstoterminatethebroadcastcallinallcellsandwaitsforaconfirmationthatthebroadcastcallhasbeenterminatedinallcells.6.2Proceduresforestablishmentofabroadcastcall6.2.1ActivationofabroadcastcallbythenetworkTheBCCentityinthenetworkmayinitiatetheactivationofabroadcastcallwithacertainbroadcastcallreferenceandpriorityinalistofcellsbyaskinglowerlayerstoestablishthebroadcastcallwiththatbroadcastcallreferenceandpriorityinthosecells.Itthenwaitsuntilitisinformedbylower(sub-)layersthatresourceactivationwassufficientlysuccessful,andentersstateN2,BCACTIVE,6.2.2MobileoriginatedestablishmentHigherlayersintheMSmayasktheBCCentityinstateU0,NULL,toestablishabroadcastcall,eitherusingtheimmediateset-upprocedureorusingtheset-upprocedure.Therequestcontainsagroup-idandmaycontainapriorityindication.Onrequestofhigherlayerstoestablishabroadcastcallusingtheset-upprocedure,theBCCentityoftheMSbuildsanappropriateSETUPmessageandaskslower(sub-)layerstoestablishanMMconnectionexplicitly(
...