SIST EN 300 949 V6.0.1:2003

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 6.0.1 Release 1997)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 6.0.1SIST EN 300 949 V6.0.1:2003en01-december-2003SIST EN 300 949 V6.0.1:2003SLOVENSKI
STANDARD



SIST EN 300 949 V6.0.1:2003



EN 300 949 V6.0.1 (1999-09)European Standard (Telecommunications series)Digital cellular telecommunications system (Phase 2+);Broadcast Call Control (BCC) protocol(GSM 04.69 version 6.0.1 Release 1997)GLOBAL SYSTEM
FOR MOBILE COMMUNICATIONSRSIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)2(GSM 04.69 version 6.0.1 Release 1997)ReferenceDEN/SMG-030469Q6 (8sc0300o.PDF)KeywordsDigital cellular telecommunications system,Global System for Mobile communications (GSM)ETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgIf you find errors in the present document, send yourcomment to: editor@etsi.frCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1999.All rights reserved.SIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)3(GSM 04.69 version 6.0.1 Release 1997)ContentsIntellectual Property Rights.5Foreword.51Scope.62References.63Definitions and abbreviations.73.1Definitions.73.2Abbreviations.74Applicability.75Main concepts.76Elementary procedures for Broadcast Call Control.86.1Overview.86.1.1General.86.1.2Broadcast call control states.86.1.2.1Broadcast call control states at the MS side of the interface.86.1.2.1.1Attributes and Parameters of BCC in the MS.96.1.2.1.2NULL (U0).96.1.2.1.3MM CONNECTION PENDING (U0.p).96.1.2.1.4BROADCAST CALL INITIATED (U1).96.1.2.1.5BROADCAST CALL ACTIVE (U2).96.1.2.1.6BROADCAST CALL PRESENT (U3).96.1.2.1.7BROADCAST CALL CONNECTION REQUESTED (U4).96.1.2.1.8TERMINATION REQUESTED (U5).106.1.2.1.9RECEIVE MODE ACTIVE (U6).106.1.2.1.10BCC TIMERS IN THE MS.106.1.2.1.11CONSISTENCY OF PARAMETERS AND STATES.106.1.2.2BROADCAST CALL CONTROL STATES AT THE NETWORK SIDE OF THE INTERFACE.116.1.2.2.1NULL (State N0).116.1.2.2.2BROADCAST CALL INITIATED (N1).116.1.2.2.3BROADCAST CALL ACTIVE (N2).116.1.2.2.4BROADCAST CALL ESTABLISHMENT PROCEEDING (N3).116.1.2.2.5TERMINATION REQUESTED (N4).116.2Procedures for establishment of a broadcast call.116.2.1Activation of a broadcast call by the network.116.2.2Mobile originated establishment.116.2.2.1Termination during mobile originated establishment.126.2.2.2Abnormal cases.126.2.3Mobile terminating broadcast call establishment in the MS.126.3Procedures during the active state and receive mode active state of a broadcast call.136.3.1Mobile station procedures in the active state.136.3.2Network procedures in the active state.136.3.3Mobile station procedures in the RECEIVE MODE ACTIVE state.136.4Procedures for release, abortion, and termination of a broadcast call.136.4.1Termination procedure.136.4.2Abort and release procedures.146.5Miscellaneous procedures.146.5.1Status procedures.146.5.1.1Get status procedure.146.5.1.2Set parameter procedure.147Handling of unknown, unforeseen, and erroneous protocol data.157.1General.157.2Message too short.157.3Unknown or unforeseen transaction identifier.15SIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)4(GSM 04.69 version 6.0.1 Release 1997)7.4Unknown or unforeseen message type.157.5Non-semantical mandatory information element errors.167.6Unknown and unforeseen information elements in the non-imperative message part.167.6.1Information elements unknown in the message.167.6.2Out of sequence information elements.167.6.3Repeated Information elements.167.7Non-imperative message part errors.167.7.1Syntactically incorrect optional Information elements.167.8Messages with semantically incorrect contents.178Message functional definitions and contents.178.1CONNECT.188.2GET STATUS.188.2.1mobile identity.188.3IMMEDIATE SETUP.198.3.1Mobile identity.198.4SET PARAMETER.198.5SETUP.208.6STATUS.208.6.1Call state.208.6.2State attributes.218.7TERMINATION.218.8TERMINATION REJECT.218.9TERMINATION REQUEST.229Contents of information elements value parts.229.1Protocol Discriminator.229.2Transaction identifier.229.3Message Type.229.4Other information elements.239.4.1Call Reference.239.4.2Call state.239.4.3Cause.249.4.4Originator indication.259.4.5Spare Half Octet.269.4.6State attributes.26Annex A (informative):Change Request History.27History.28SIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)5(GSM 04.69 version 6.0.1 Release 1997)Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by the Special Mobile Group (SMG).The present document specifies the Broadcast Call Control (BCC) protocol within the digital cellulartelecommunications system (Phase 2+).The contents of the present document is subject to continuing work within SMG and may change following formal SMGapproval. Should SMG modify the contents of the present document it will be re-released with an identifying change ofrelease date and an increase in version number as follows:Version 6.x.ywhere:6indicates Release 1997 of GSM Phase 2+xthe second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,etc.ythe third digit is incremented when editorial only changes have been incorporated in the specification.Proposed national transposition datesDate of adoption of this EN:3 September 1999Date of latest announcement of this EN (doa):31 December 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 June 2000Date of withdrawal of any conflicting National Standard (dow):30 June 2000SIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)6(GSM 04.69 version 6.0.1 Release 1997)1ScopeThe present document specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service(VBCS) on the radio interface.2ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, the latest version applies.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.· For this Release 1997 document, references to GSM documents are for Release 1997 versions (version 6.x.y).[1]GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations andacronyms".[2]GSM 02.69): "Digital cellular telecommunications system (Phase 2+); Voice Broadcast CallService (VBCS) stage 1".[3]GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing andidentification".[4]GSM 03.67: "Digital cellular telecommunications system (Phase 2+); enhanced Multi-LevelPrecedence and Pre-emption service (eMLPP) - Stage 2".[5]GSM 03.69: "Digital cellular telecommunications system (Phase 2+); Voice Broadcast CallService (VBCS) stage 2".[6]GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - BaseStation System (MS - BSS) interface
Data Link (DL) layer specification".[7]GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interfacesignalling layer 3
General aspects".[8]GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interfacelayer 3 specification".SIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)7(GSM 04.69 version 6.0.1 Release 1997)3Definitions and abbreviations3.1DefinitionsDefinitions used in the present document are also defined in GSM 02.69.For the purposes of the present document, the following terms and definitions apply.Attachment of the user connection: See GSM 04.08, subclause 5.2.Broadcast call channel: Downlink channel to be allocated in each cell of the group call area for a particular broadcastcall. All MSs of the listening service subscribers in one cell shall listen to the common downlink.Broadcast call: Is used in the same sense as "voice broadcast call".Calling user: BCC entity in the Mobile Station (MS) initiating or having initiated a broadcast call.Clearing the context related to the broadcast call establishment: all running BCC timers in the relevant BCC entityare stopped, all attributes in the relevant BCC entity are deleted.Downlink: Network to MS direction.Group receive mode: See GSM 04.08.Originating mobile station: MS initiating or having initiated the broadcast call.Uplink: Mobile station to network direction.3.2AbbreviationsAbbreviations used in the present document are also listed in GSM 01.04.For the purposes of the present document, the following abbreviation applies:BCCBroadcast Call Control.4ApplicabilitySupport of the broadcast call protocol is optional in the MS and in the network.5Main conceptsThe present document describes the broadcast call control (BCC) protocol, which is one of the protocols of theConnection Management (CM) sublayer (see GSM 04.07).There is in general more than one MS engaged in a broadcast call. Consequently, there is in general more than one MSwith a BCC entity engaged in the same broadcast call, and there is one BCC entity in the network engaged in thatbroadcast call.Under which conditions a BCC message is passed from lower (sub-)layers to the BCC entity is defined in thespecifications of the sub-layers.The MS shall ignore BCC messages that it receives which were sent in unacknowledged mode and which explicitlyspecify as destination a mobile identity which is not a mobile identity of the MS.Higher layers and the MM sub-layer decide when to accept parallel BCC transactions and when/whether to accept BCCtransactions in parallel to other CM transactions.SIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)8(GSM 04.69 version 6.0.1 Release 1997)The broadcast call may be initiated by a mobile user or by a dispatcher. Specification of a protocol for dispatchers is outof the scope of the present document. Hence, in the scope of the present document, there are-one BCC entity in the network; and-one or more than one BCC entities in different MSsengaged in a broadcast call, and one ore none of the MSs is the originator of the broadcast call (called the originatingMS in the present document).NOTE: Whereas for the Group Call Control (GCC) protocol (see GSM 04.68), in certain situations, the GCCentity in a MS assumes to be the originator of a broadcast call without being the originator, this is not thecase for the BCC protocol.The originator of the BCC transaction chooses the Transaction Identifier (TI). A MS not assuming to be the originatorof the transaction will chose the transaction identifier received from the network, setting the TI flag to 1+x mod 2 wherex is the received TI flag.The present document describes the broadcast call control protocol only with regard to two peer entities, one in a MS,the other one in the network. The call control entities are described as communicating finite state machines whichexchange messages across the radio interface and communicate internally with other protocol (sub)layers. In particular,the BCC protocol uses the MM and RR sublayer specified in GSM 04.08. The BCC entity in a MS that is not theoriginator of the broadcast call shall not send messages to its peer entity. This description in only normative as far as theconsequential externally observable behaviour is concerned. For simplicity, instead of using the terms "BCC entity inthe MS" and "BCC entity in the network", the present document often uses the terms "MS" and "network" if noconfusion may arise.Certain sequences of actions of the two peer entities compose "elementary procedures" which are used as a basis for thedescription in the present document. These elementary procedures are defined in clause 6.The network should apply supervisory functions to verify that the BCC procedures are progressing and if not, takeappropriate means to resolve the problems. This, however, is out of the scope of the present document.6Elementary procedures for Broadcast Call Control6.1Overview6.1.1GeneralThe elementary procedures may be broadcasted into the following classes:-broadcast call establishment procedures;-broadcast call termination procedures;-broadcast call information phase procedures;-miscellaneous procedures.6.1.2Broadcast call control states6.1.2.1Broadcast call control states at the MS side of the interfaceThe BCC entity of the MS is described as an extended finite state machine. It performs transitions between states. It hascertain parameters and attributes, e.g. configuration parameters and behaviour parameters, which it sets and changesbased on interaction with higher and lower (sub-)layers and on message exchange with its peer entity. If a configurationparameter is set to a certain value, the MS shall also adapt the configuration accordingly. Behaviour parameters decideon (part of) the behaviour of the BCC entity. When the BCC entity in the MS receives a message, it shall first analysewhether it shall ignore the message, see clauses 5 and 7.SIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)9(GSM 04.69 version 6.0.1 Release 1997)6.1.2.1.1Attributes and Parameters of BCC in the MSFor the following behaviour parameters, the description is informative.ParameterDescriptionORIGDepending on the context, the MS assumes to be the originator of the call (ORIG=T) or not to be theoriginator of the call (ORIG=F).COMMDepending on the context, the MS assumes that communication with its peer entity is enabled inboth directions (COMM = T) or not (COMM = F).For the following configuration parameters the MS shall adapt its configuration according to the parameter value andparameter definition.ParameterDefinitionD-ATTD-ATT = T means that the MS attaches the user connection for the broadcast call in the downlink.D-ATT = F means that the MS does not attach the user connection for the broadcast call in thedownlink.U-ATTU-ATT = T means that the MS attaches the user connection for the broadcast call in the uplink.U-ATT = F means that the MS does not attach the user connection for the broadcast call in theuplink.6.1.2.1.2NULL (U0)No broadcast call exists for the BCC entity. When entering the state, parameters shall be set to the following values, andconfiguration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = F,U-ATT = F.6.1.2.1.3MM CONNECTION PENDING (U0.p)The BCC entity has requested the explicit establishment of an MM connection. When entering the state, parameters shallbe set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG =T, COMM = F, D-ATT = F, U-ATT = F.6.1.2.1.4BROADCAST CALL INITIATED (U1)The BCC entity has requested the peer entity in the network to establish a broadcast call. When entering the state,parameters shall be set to the following values, and configuration shall be adapted to the new values of configurationparameters: ORIG = T, COMM = T, D-ATT = F, U-ATT = F.6.1.2.1.5BROADCAST CALL ACTIVE (U2)The broadcast call is established at least in one cell. When entering the state, parameters shall be set to the followingvalues, and configuration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = F,D-ATT = T, U-ATT = T.6.1.2.1.6BROADCAST CALL PRESENT (U3)The MS has received a notification about an ongoing broadcast call. Higher layers are requested to accept or reject thecall. When entering the state, parameters shall be set to the following values, and configuration shall be adapted to thenew values of configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F.6.1.2.1.7BROADCAST CALL CONNECTION REQUESTED (U4)The MS has received a notification about an ongoing broadcast call. Higher layers have decided to accept the call. Whenentering the state, parameters shall be set to the following values, and configuration shall be adapted to the new valuesof configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F.SIST EN 300 949 V6.0.1:2003



ETSIEN 300 949 V6.0.1 (1999-09)10(GSM 04.69 version 6.0.1 Release 1997)6.1.2.1.8TERMINATION REQUESTED (U5)The MS which is the originator of the broadcast call has been in state U1 or U2 and has sent a TERMINATIONREQUEST message to the network. When entering the state, parameters shall be set to the following values, andconfiguration shall be adapted to the new values of configuration parameters: ORIG = T, COMM = T, D-ATT = T,U-ATT = T.6.1.2.1.9RECEIVE MODE ACTIVE (U6)The BCC entity in the MS in state U4, BROADCAST CALL CONNECTION REQUESTED, has got an indication fromlower (sub-)layers that RR has entered group receive mode (see GSM 04.08). When entering the state, parameters shallbe set to the following values, and configuration shall be adapted to the new values of configuration parameters: ORIG =F, COMM = F, D-ATT = T, U-ATT = F.6.1.2.1.10BCC TIMERS IN THE MSTable 6.1 specifies the timers used in BCC. The denotation of columns is defined as follows:timer ::=name of the timer;set ::=under which conditions the timer is set (i.e., started);stopped ::=under which conditions the timer is stopped;running in state(s) ::=in which state(s) the timer may be running;action at expiry ::=which actions the BCC entity shall perform at expiry;value ::=the duration between setting the timer and expiry of the timer ("s" denotes"second(s)" "xx - yy" means that any value between xx and yy is permitted).Table 6.1: Specification of timers used in BCCtimersetstoppedrunning instate(s)action atexpiryvalueTno channelin state U6 on receipt of anindication from lower(sub-)layers that no channelis currently availablewhen leaving U6 or whenreceiving in U6 an indicationfrom lower (sub-)layers that achannel is availablein U6,depending onfurtherconditionsseesubclause6.3.13 sTMM-estwhen entering U0.p using theset-up procedurewhen entering U1 using theimmediate set-up procedurewhen leaving U0.p or U1U0.p, U1seesubclause6.2.15 sTtermwhen sending aTERMINATION REQUESTwhen receiving aTERMINATION orTERMINATION REJECTU5abortbroadcastcall10 sTconn reqwhen entering state U4when leaving state U4U4abortbroadcastcall10-30 s6.1.2.1.11CONSISTENCY OF PARAMETERS AND STATESThe MS shall consider the following parameter values as inconsistent with the state or sub-state:ORIG = T is inconsistent with states U3, U4, and U6.COMM = T is inconsistent with states U0, U3, U4, and U6.All other values of parameters ORIG, COMM, D-ATT, and U-ATT shall not be considered by the MS as inconsistentwith a state.SIST EN 300 949
...