SIST ETS 300 949 E4:2003
(Main)Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (GSM 04.69 version 5.3.1 Release 1996)
- Abstract
SUBJECT GSM 04.69 Corrections. Get Status Procedure Set Status Procedure
- 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 ETS 300 949 E4:2003 is the Slovenian adoption of ETS 300 949 Edition 4, published by SIST and identical to the ETSI standard for the Broadcast Call Control (BCC) protocol in GSM Phase 2+. It specifies how the BCC protocol works on the radio interface for the Voice Broadcast Call Service (VBCS), including call setup, active-state handling, release, status exchange, and error handling. The document is written for implementers of the Mobile Station (MS) and network sides of GSM equipment, as well as for people who test or manage that signaling.
What does SIST ETS 300 949 E4:2003 specify?
SIST ETS 300 949 E4:2003 specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service (VBCS) on the radio interface. In practical terms, it defines how an MS and the network exchange BCC messages, move through BCC states, and handle setup, active operation, termination, and protocol errors.
The document is organized into clauses on scope, normative references, definitions and abbreviations, applicability, main concepts, elementary procedures, error handling, message functional definitions, and the contents of information elements. Annex A is informative and gives the change request history.
| Annex | What it covers |
|---|---|
| Annex A | Change Request History |
What are the key requirements of SIST ETS 300 949 E4:2003?
Support, scope of operation, and protocol roles
SIST ETS 300 949 E4:2003 says support for the broadcast call protocol is optional in both the MS and the network. The protocol is part of the Connection Management (CM) sublayer and is described as communication between two peer entities, one in the MS and one in the network.
That matters because implementers can choose whether a device supports BCC, but if it does, it must follow the protocol behavior defined here. The standard also makes clear that the BCC protocol is for radio-interface signaling, not for dispatcher protocol behavior outside its scope.
Call establishment procedures
SIST ETS 300 949 E4:2003 defines two MS-side ways to start a broadcast call: the set-up procedure and the immediate set-up procedure. The set-up procedure uses an explicit Mobility Management (MM) connection, while the immediate set-up procedure uses implicit MM connection establishment. The network can also initiate activation of a broadcast call in a list of cells.
In practice, this means equipment must build the correct message, start the correct timers, and move through the specified states. The network may accept or reject the establishment, and on acceptance it sends a CONNECT message that identifies the broadcast call reference and indicates whether the MS is the originator.
State machines and timers
SIST ETS 300 949 E4:2003 describes BCC as extended finite state machines on both sides of the interface. On the MS side, the important states include NULL, MM CONNECTION PENDING, BROADCAST CALL INITIATED, BROADCAST CALL ACTIVE, BROADCAST CALL PRESENT, BROADCAST CALL CONNECTION REQUESTED, TERMINATION REQUESTED, and RECEIVE MODE ACTIVE. The network side uses states such as NULL, BROADCAST CALL INITIATED, BROADCAST CALL ACTIVE, BROADCAST CALL ESTABLISHMENT PROCEEDING, and TERMINATION REQUESTED.
The state definitions matter because they control what each peer is allowed to do and what parameters must be set. The document also specifies timers used during establishment, connection request handling, termination, and no-channel conditions, so implementations need timer supervision to avoid staying in a stale call state.
Release, abortion, and termination
SIST ETS 300 949 E4:2003 defines termination, abort, and release behavior for both the originator and the network. The originator MS can request termination with a TERMINATION REQUEST, and the network can answer with TERMINATION or TERMINATION REJECT. Either side may also trigger abortion or release through lower-layer events such as radio link failure or resource release.
This matters in operations because the standard defines what the MS must inform higher layers, when it must clear the call context, and when it must return to NULL. A conforming implementation must handle these exits consistently so that calls do not remain half-open after a failure or a user request.
Status procedures and parameter control
SIST ETS 300 949 E4:2003 includes a GET STATUS procedure and a SET PARAMETER procedure. On GET STATUS, the MS responds with a STATUS message when communication is enabled, reporting the current call state and parameter values. On SET PARAMETER, the MS applies the requested values only when they are consistent with the current BCC state and sub-state.
For a buyer or engineer, this is the part that supports network supervision and troubleshooting. It lets the network query the MS state and push state-related parameters, while also forcing the MS to reject or ignore inconsistent changes in a defined way.
Error handling and compatibility behavior
SIST ETS 300 949 E4:2003 defines how the MS handles short messages, unknown transaction identifiers, unsupported message types, invalid mandatory information, out-of-sequence information elements, repeated information elements, and semantically incorrect contents. In many cases the MS ignores the message, and in other cases it returns a STATUS message with a specific cause.
This is important for interoperability and future extensions. The rules make sure that unsupported or malformed messages do not break the call state machine, while still giving diagnostics where the protocol requires them.
What terms does SIST ETS 300 949 E4:2003 define?
- Broadcast call channel - A downlink channel allocated in each cell for a particular broadcast call, so all listening MSs in that cell receive the same call.
- Calling user - The BCC entity in the MS that initiates, or has initiated, the broadcast call.
- ORIG - A behavior parameter indicating whether the MS assumes it is the originator of the call.
- COMM - A behavior parameter indicating whether communication with the peer entity is enabled in both directions.
- D-ATT - A configuration parameter that shows whether the user connection is attached in the downlink.
- U-ATT - A configuration parameter that shows whether the user connection is attached in the uplink.
- Broadcast call reference - The reference value used to identify a broadcast call, and in some messages also to carry priority information.
- Call state - An information element that identifies the BCC state, or a sub-state of the active state, at the MS side.
Who uses SIST ETS 300 949 E4:2003?
SIST ETS 300 949 E4:2003 is used by GSM equipment designers, protocol implementers, test laboratories, and network engineers who need to implement or verify BCC signaling. It is also relevant to quality managers and integrators who need to check message formats, state behavior, timer handling, and interoperability between an MS and the network.
In practice, it supports tasks such as building BCC software, validating radio-interface signaling, checking conformance tests, and troubleshooting call establishment or termination problems. It is also useful for anyone working with Voice Broadcast Call Service behavior in a GSM Phase 2+ environment.
What changed in SIST ETS 300 949 E4:2003 from the previous edition?
Annex A records the change request history behind this edition. The listed changes include GSM 04.69 Corrections, the Get Status Procedure, the Set Status Procedure, coding of the Call Reference IE, and an update to version 5.3.1 for publication.
The history page also shows that this is the fourth edition, following the earlier publication steps recorded in the document history.
Which standards are used with SIST ETS 300 949 E4:2003?
SIST ETS 300 949 E4:2003 cites these normative references and companion parts:
- GSM 01.04 - provides abbreviations and acronyms used throughout the protocol description.
- GSM 02.69 - gives the stage 1 description of the Voice Broadcast Call Service (VBCS).
- GSM 03.03 - provides numbering, addressing, and identification, including broadcast call reference concepts.
- GSM 03.67 - covers the enhanced Multi-Level Precedence and Pre-emption service (eMLPP), which is referenced for priority-related behavior.
- GSM 03.69 - gives the stage 2 description of the VBCS.
- GSM 04.06 - defines the Mobile Station - Base Station System (MS - BSS) interface data link layer used by BCC signaling.
- GSM 04.07 - gives the general layer 3 signaling rules and message structure used by BCC.
- GSM 04.08 - provides the mobile radio interface layer 3 and the MM and RR procedures that BCC depends on.
What does the SIST ETS 300 949 E4:2003 document contain?
SIST ETS 300 949 E4:2003 contains the BCC state model, procedure descriptions, message definitions, information element coding, and error-handling rules. Clause 6 gives the elementary procedures for establishment, active-state operation, release, and miscellaneous status handling, including the timer behavior used by the MS.
Clause 8 defines the messages such as CONNECT, GET STATUS, IMMEDIATE SETUP, SET PARAMETER, SETUP, STATUS, TERMINATION, TERMINATION REJECT, and TERMINATION REQUEST. Clause 9 then specifies the value parts of the information elements, including call reference, call state, cause, originator indication, spare half octet, and state attributes. Annex A provides the change request history that led to this edition.
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 ETS 300 949 E4: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 5.3.1 Release 1996)". This standard covers: SUBJECT GSM 04.69 Corrections. Get Status Procedure Set Status Procedure
SUBJECT GSM 04.69 Corrections. Get Status Procedure Set Status Procedure
SIST ETS 300 949 E4: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 ETS 300 949 E4: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 ETS 300 949 E4: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)
SLOVENSKI STANDARD
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ±3URWRNROUDGLRGLIX]QHJDNOLFD
%&& *60 UD]OLþLFDL]GDMD
Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control
(BCC) protocol (GSM 04.69 version 5.3.1 Release 1996)
Ta slovenski standard je istoveten z: ETS 300 949 Edition 4
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 949
TELECOMMUNICATION December 1999
STANDARD Fourth Edition
Source: SMG Reference: RE/SMG-030469QR3
ICS: 33.020
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
Digital cellular telecommunications system (Phase 2+);
Broadcast Call Control (BCC) protocol
(GSM 04.69 version 5.3.1 Release 1996)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.org
Tel.:+33492944200- Fax:+33493654716
Copyright Notification: No 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.
Page 2
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.
Page 3
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .8
4 Applicability.8
5 Main concepts .8
6 Elementary procedures for Broadcast Call Control.9
6.1 Overview .9
6.1.1 General.9
6.1.2 Broadcast call control states .9
6.1.2.1 Broadcast call control states at the MS side of the
interface.9
6.1.2.1.1 Attributes and Parameters of BCC in
the MS.9
6.1.2.1.2 NULL (U0).9
6.1.2.1.3 MM CONNECTION PENDING (U0.p) .10
6.1.2.1.4 BROADCAST CALL INITIATED (U1).10
6.1.2.1.5 BROADCAST CALL ACTIVE (U2) .10
6.1.2.1.6 BROADCAST CALL PRESENT (U3) .10
6.1.2.1.7 BROADCAST CALL CONNECTION
REQUESTED (U4).10
6.1.2.1.8 TERMINATION REQUESTED (U5).10
6.1.2.1.9 RECEIVE MODE ACTIVE (U6) .10
6.1.2.1.10 BCC TIMERS IN THE MS.10
6.1.2.1.11 CONSISTENCY OF PARAMETERS
AND STATES .11
6.1.2.2 BROADCAST CALL CONTROL STATES AT THE
NETWORK SIDE OF THE INTERFACE.11
6.1.2.2.1 NULL (State N0) .11
6.1.2.2.2 BROADCAST CALL INITIATED (N1).11
6.1.2.2.3 BROADCAST CALL ACTIVE (N2) .11
6.1.2.2.4 BROADCAST CALL
ESTABLISHMENT PROCEEDING
(N3).11
6.1.2.2.5 TERMINATION REQUESTED (N4).11
6.2 Procedures for establishment of a broadcast call.12
6.2.1 Activation of a broadcast call by the network .12
6.2.2 Mobile originated establishment.12
6.2.2.1 Termination during mobile originated establishment.13
6.2.2.2 Abnormal cases.13
6.2.3 Mobile terminating broadcast call establishment in the MS .13
6.3 Procedures during the active state and receive mode active state of a broadcast call .13
6.3.1 Mobile station procedures in the active state .13
6.3.2 Network procedures in the active state .13
6.3.3 Mobile station procedures in the RECEIVE MODE ACTIVE state .14
6.4 Procedures for release, abortion, and termination of a broadcast call .14
6.4.1 Termination procedure .14
Page 4
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
6.4.2 Abort and release procedures . 14
6.5 Miscellaneous procedures. 15
6.5.1 Status procedures. 15
6.5.1.1 Get status procedure. 15
6.5.1.2 Set parameter procedure . 15
7 Handling of unknown, unforeseen, and erroneous protocol data . 15
7.1 General. 15
7.2 Message too short. 15
7.3 Unknown or unforeseen transaction identifier. 16
7.4 Unknown or unforeseen message type. 16
7.5 Non-semantical mandatory information element errors . 16
7.6 Unknown and unforeseen information elements in the non-imperative message part . 16
7.6.1 Information elements unknown in the message . 16
7.6.2 Out of sequence information elements. 17
7.6.3 Repeated Information elements. 17
7.7 Non-imperative message part errors. 17
7.7.1 Syntactically incorrect optional Information elements. 17
7.8 Messages with semantically incorrect contents . 17
8 Message functional definitions and contents. 17
8.1 CONNECT. 18
8.2 GET STATUS.19
8.2.1 mobile identity. 19
8.3 IMMEDIATE SETUP . 19
8.3.1 Mobile identity . 20
8.4 SET PARAMETER. 20
8.5 SETUP . 20
8.6 STATUS . 21
8.6.1 Call state. 21
8.6.2 State attributes. 21
8.7 TERMINATION.21
8.8 TERMINATION REJECT . 22
8.9 TERMINATION REQUEST . 22
9 Contents of information elements value parts . 22
9.1 Protocol Discriminator . 22
9.2 Transaction identifier. 22
9.3 Message Type. 23
9.4 Other information elements. 23
9.4.1 Call Reference . 23
9.4.2 Call state. 24
9.4.3 Cause. 25
9.4.4 Originator indication. 26
9.4.5 Spare Half Octet . 27
9.4.6 State attributes. 27
Annex A (Informative): Change Request History. 28
History. 29
Page 5
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The
information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-
members, and can be found in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially
Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI
Secretariat. Latest updates are available on the ETSI 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 guarantee can 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.
Foreword
This European Telecommunication Standard (ETS) has been produced by the Special Mobile Group
(SMG) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS specifies the Broadcast Call Control (BCC) protocol within the digital cellular
telecommunications system (Phase 2+).
The contents of this ETS is subject to continuing work within TC-SMG and may change following formal
TC-SMG approval. Should TC-SMG modify the contents of this ETS, it will be resubmitted for OAP by
ETSI with an identifying change of release date and an increase in version number as follows:
Version 5.x.y
5 Indicates GSM Phase 2+ Release 1996;
x the second digit is incremented for all changes of substance, i.e. technical enhancements,
corrections, updates, etc.;
y the third digit is incremented when editorial only changes have been incorporated in the
specification.
Transposition dates
Date of adoption of this ETS: 10 December 1999
Date of latest announcement of this ETS (doa):
31 March 2000
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 September 2000
Date of withdrawal of any conflicting National Standard (dow): 30 September 2000
Page 6
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
Blank page
Page 7
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
1 Scope
This European Telecommunication Standard (ETS) specifies the Broadcast Call Control (BCC) protocol
used by the Voice Broadcast Call Service (VBCS) on the radio interface.
2 Normative references
This ETS incorporates by dated and undated references, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] GSM 01.04 (ETR 350) "Digital cellular telecommunications system (Phase 2+);
Abbreviations and acronyms".
[2] GSM 02.69 (ETS 300 925): "Digital cellular telecommunications system
(Phase 2+); Voice Broadcast Call Service (VBCS) stage 1".
[3] GSM 03.03 (ETS 300 927): "Digital cellular telecommunications system
(Phase 2+); Numbering, addressing and identification".
[4] GSM 03.67 (ETS 300 932): "Digital cellular telecommunications system
(Phase 2+); enhanced Multi-Level Precedence and Pre-emption service
(eMLPP) - Stage 2".
[5] GSM 03.69 (ETS 300 934): "Digital cellular telecommunications system
(Phase 2+); Voice Broadcast Call Service (VBCS) stage 2".
[6] GSM 04.06 (ETS 300 938): "Digital cellular telecommunications system; Mobile
Station - Base Station System (MS - BSS) interface Data Link (DL) layer
specification"
[7] GSM 04.07 (ETS 300 939): "Digital cellular telecommunications system
(Phase 2+); Mobile radio interface signalling layer 3 General aspects".
[8] GSM 04.08 (ETS 300 940): "Digital cellular telecommunications system
(Phase 2+); Mobile radio interface layer 3 specification".
3 Definitions and abbreviations
3.1 Definitions
Definitions used in this ETS are also defined in GSM 02.69.
For the purposes of this ETS, 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 broadcast call. 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 entity are stopped, all attributes in the relevant BCC entity are deleted.
Downlink: Network to MS direction.
Page 8
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
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.2 Abbreviations
Abbreviations used in this ETS are also listed in GSM 01.04.
For the purposes of this ETS, the following abbreviation applies:
BCC Broadcast Call Control
4 Applicability
Support of the broadcast call protocol is optional in the MS and in the network.
5 Main concepts
This ETS describes the broadcast call control (BCC) protocol, which is one of the protocols of the
Connection 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 MS with a BCC entity engaged in the same broadcast call, and there is one BCC entity in the
network engaged in that broadcast call.
Under which conditions a BCC message is passed from lower (sub-)layers to the BCC entity is defined in
the specifications of the sub-layers.
The MS shall ignore BCC messages that it receives which were sent in unacknowledged mode and which
explicitly specify 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 BCC transactions in parallel to other CM transactions.
The broadcast call may be initiated by a mobile user or by a dispatcher. Specification of a protocol for
dispatchers is out of the scope of this ETS. Hence, in the scope of this ETS, there are:
- one BCC entity in the network; and
- one or more than one BCC entities in different MSs.
engaged in a broadcast call, and one ore none of the MSs is the originator of the broadcast call (called the
originating MS in this ETS).
NOTE: Whereas for the Group Call Control (GCC) protocol (see GSM 04.68), in certain
situations, the GCC entity in a MS assumes to be the originator of a broadcast call
without being the originator, this is not the case for the BCC protocol.
The originator of the BCC transaction chooses the Transaction Identifier (TI). A MS not assuming to be
the originator of the transaction will chose the transaction identifier received from the network, setting the
TI flag to 1+x mod 2 where x is the received TI flag.
This ETS 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 which exchange 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 the originator of the broadcast call shall not send
messages to its peer entity. This description in only normative as far as the consequential externally
observable behaviour is concerned. For simplicity, instead of using the terms "BCC entity in the MS" and
"BCC entity in the network", this ETS often uses the terms "MS" and "network" if no confusion may arise.
Page 9
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
Certain sequences of actions of the two peer entities compose "elementary procedures" which are used
as a basis for the description in this ETS. 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, take appropriate means to resolve the problems. This, however, is out of the scope of this ETS.
6 Elementary procedures for Broadcast Call Control
6.1 Overview
6.1.1 General
The 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.2 Broadcast call control states
6.1.2.1 Broadcast call control states at the MS side of the interface
The BCC entity of the MS is described as an extended finite state machine. It performs transitions
between states. It has certain parameters and attributes, e.g. configuration parameters and behaviour
parameters, which it sets and changes based on interaction with higher and lower (sub-)layers and on
message exchange with its peer entity. If a configuration parameter is set to a certain value, the MS shall
also adapt the configuration accordingly. Behaviour parameters decide on (part of) the behaviour of the
BCC entity. When the BCC entity in the MS receives a message, it shall first analyse whether it shall
ignore the message, see clauses 5 and 7.
6.1.2.1.1 Attributes and Parameters of BCC in the MS
For the following behaviour parameters, the description is informative.
Parameter Description
ORIG Depending on the context, the MS assumes to be the originator of the call (ORIG=T) or not
to be the originator of the call (ORIG=F).
COMM Depending on the context, the MS assumes that communication with its peer entity is
enabled in both directions (COMM = T) or not (COMM = F).
For the following configuration parameters the MS shall adapt its configuration according to the parameter
value and parameter definition.
Parameter Definition
D-ATT D-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 the downlink.
U-ATT U-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 the uplink.
6.1.2.1.2 NULL (U0)
No broadcast call exists for the BCC entity. When entering the state, parameters shall be set to the
following values, and configuration shall be adapted to the new values of configuration parameters:
ORIG = F, COMM = F, D-ATT = F, U-ATT = F.
Page 10
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
6.1.2.1.3 MM CONNECTION PENDING (U0.p)
The BCC entity has requested the explicit establishment of an MM connection. When entering the state,
parameters shall be 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.4 BROADCAST 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 configuration parameters: ORIG = T, COMM = T, D-ATT = F, U-ATT = F.
6.1.2.1.5 BROADCAST CALL ACTIVE (U2)
The broadcast call is established at least in one cell. When entering the state, parameters shall be set to
the following values, and configuration shall be adapted to the new values of configuration parameters:
ORIG = T, COMM = T, D-ATT = T, U-ATT = T.
6.1.2.1.6 BROADCAST CALL PRESENT (U3)
The MS has received a notification about an ongoing broadcast call. Higher layers are requested to accept
or reject the call. When entering the state, parameters shall be set to the following values, and
configuration shall be adapted to the new values of configuration parameters: ORIG = F, COMM = F,
D-ATT = F, U-ATT = F.
6.1.2.1.7 BROADCAST CALL CONNECTION REQUESTED (U4)
The MS has received a notification about an ongoing broadcast call. Higher layers have decided to accept
the call. When entering the state, parameters shall be set to the following values, and configuration shall
be adapted to the new values of configuration parameters: ORIG = F, COMM = F, D-ATT = F, U-ATT = F.
6.1.2.1.8 TERMINATION REQUESTED (U5)
The MS which is the originator of the broadcast call has been in state U1 or U2 and has sent a
TERMINATION REQUEST message to the network. When entering the state, parameters shall be set to
the following values, and configuration shall be adapted to the new values of configuration parameters:
ORIG = T, COMM = T, D-ATT = T, U-ATT = T.
6.1.2.1.9 RECEIVE MODE ACTIVE (U6)
The BCC entity in the MS in state U4, BROADCAST CALL CONNECTION REQUESTED, has got an
indication from lower (sub-)layers that RR has entered group receive mode (see GSM 04.08). When
entering the state, parameters shall be 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.10 BCC TIMERS IN THE MS
Table 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).
Page 11
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
Table 6.1: Specification of timers used in BCC
timer set stopped running in action at value
state(s) expiry
T in state U6 on receipt of an when leaving U6 or when in U6, see 3s
no channel
indication from lower receivinginU6anindication depending subclause
(sub-)layers that no from lower (sub-)layers that on further 6.3.1
channel is currently a channel is available conditions
available
T when entering U0.p using when leaving U0.p or U1 U0.p, U1 see 5s
MM-est
the set-up procedure subclause
when entering U1 using 6.2.1
the immediate set-up
procedure
T when sending a when receiving a U5 abort 10 s
term
TERMINATION TERMINATION or broadcast
REQUEST TERMINATION REJECT call
T when entering state U4 when leaving state U4 U4 abort 10-30 s
conn req
broadcast
call
6.1.2.1.11 CONSISTENCY OF PARAMETERS AND STATES
The 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
inconsistent with a state.
6.1.2.2 BROADCAST CALL CONTROL STATES AT THE NETWORK SIDE OF THE
INTERFACE
6.1.2.2.1 NULL (State N0)
No broadcast call exists for the BCC entity.
6.1.2.2.2 BROADCAST CALL INITIATED (N1)
The BCC entity has received the indication that a peer entity in a MS wants to establish a broadcast call
for a certain broadcast identity.
6.1.2.2.3 BROADCAST CALL ACTIVE (N2)
The broadcast call is established in at least one cell; there may be a MS which has seized the uplink or
not; there may be talking dispatchers or not.
6.1.2.2.4 BROADCAST CALL ESTABLISHMENT PROCEEDING (N3)
The BCC entity wants to accept the broadcast call, has initiated establishment of corresponding broadcast
call channels, and, if there is a calling user. has sent a CONNECT message to the calling user.
6.1.2.2.5 TERMINATION REQUESTED (N4)
The BCC entity has asked lower sub-layers to terminate the broadcast call in all cells and waits for a
confirmation that the broadcast call has been terminated in all cells.
Page 12
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
6.2 Procedures for establishment of a broadcast call
6.2.1 Activation of a broadcast call by the network
The BCC entity in the network may initiate the activation of a broadcast call with a certain broadcast call
reference and priority in a list of cells by asking lower layers to establish the broadcast call with that
broadcast call reference and priority in those cells. It then waits until it is informed by lower (sub-)layers
that resource activation was sufficiently successful, and enters state N2, BC ACTIVE,
6.2.2 Mobile originated establishment
Higher layers in the MS may ask the BCC entity in state U0, NULL, to establish a broadcast call, either
using the immediate set-up procedure or using the set-up procedure. The request contains a group-id and
may contain a priority indication.
On request of higher layers to establish a broadcast call using the set-up procedure, the BCC entity of the
MS builds an appropriate SETUP message and asks lower (sub-)layers to establish an MM connection
explicitly (i.e. by use of a CM SERVICE REQUEST message) and to transmit the SETUP message. It
then enters state U0.p, MM CONNECTION PENDING. In state U0.p, when informed by lower sub-layers
that an MM connection has been established, the BCC entity in the MS shall stop timer T and enter
MM-est
state U1, BC INITIATED.
On request of higher layers to establish a broadcast call using the immediate set-up procedure, the BCC
entity of the MS builds an appropriate IMMEDIATE SETUP message and asks lower (sub-)layers to
establish an MM connection implicitly (see GSM 04.08) and to transmit the IMMEDIATE SETUP message.
It sets timer T and then enters state U1, BC INITIATED.
MM-est
The network BCC entity in state NULL may receive a set-up message from its peer entity in the originating
MS. This set-up message is either a SETUP message or an IMMEDIATE SETUP message. The network
enters state N1, BC INITIATED.
In state N1, the network decides whether
a) the establishment is accepted; or
b) the establishment rejected.
In case a), the BCC entity in the network considers the peer entity in the MS having sent the set-up
message to be the calling user and asks lower layers to activate the appropriate resources. It then
1) waits until it is informed by lower (sub-)layers that resource activation was sufficiently
successful, then sends a CONNECT message to the calling user, and enters state N2, BC
ACTIVE; or
2) sends a CONNECT message to the calling user and enters N3, BC ESTABLISHMENT
PROCEEDING. In state N3, the BCC entity is informed by lower layers whenever the status
of resources for the broadcast call is changed. When informed that activation of resources
was sufficiently successful, the BCC entity in the network enters state N2, ACTIVE.
The CONNECT message specifies the broadcast call reference of the broadcast call and indicates
that the MS is the originator of the broadcast call.
In case b), the further proceeding is as defined in subclause 6.2.2.1.
In state U0.p or U1, the BCC entity in the MS shall, on receipt of a CONNECT message, establish the
conditions defined for state U2, ACTIVE and the suitable sub-state (see subclause 6.1.2.1), stop timer
T (if running) and enter state U2, ACTIVE. If the immediate set-up procedure has been used, the
MM-est
BCC entity in the MS shall inform lower sub-layers that the MM connection has been implicitly established.
Page 13
ETS 300 949 (GSM 04.69 version 5.3.1 Release 1996): December 1999
6.2.2.1 Termination during mobile originated establishment
At any time during the mobile originated establishment of a broadcast call, the network may decide to
terminate the connection between the two peer entities in the network and MS. In this case the network
sends a TERMINATION message to the MS specifying the appropriate cause; it may ask lower
(sub-)layers to release associated resource
...