SIST EN 300 949 V6.2.1:2003
(Main)Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (GSM 04.69 version 6.2.1 Release 1997)
- Abstract
Upgrade from Phase 2+ to Release 1997
- 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 949 V6.2.1:2003 is the Slovenian standard that adopts ETSI EN 300 949 Version 6.2.1. It specifies the Broadcast Call Control (BCC) protocol for the GSM Voice Broadcast Call Service (VBCS) on the radio interface, for use by the mobile station (MS) and the network. The document covers call setup, active operation, termination, error handling, and the coding of the BCC messages and information elements.
What does SIST EN 300 949 V6.2.1:2003 specify?
SIST EN 300 949 V6.2.1:2003 specifies how BCC works within the digital cellular telecommunications system (Phase 2+) for VBCS. It is a protocol specification for signalling between one network BCC entity and one or more MS BCC entities engaged in a broadcast call.
Clause 1 states the scope, clause 4 says support of the broadcast call protocol is optional in both the MS and the network, and clauses 5 to 9 define the protocol behavior and message coding. Annex A is informative and records change request history.
The main structure is:
- Clause 1 - Scope
- Clause 2 - References
- Clause 3 - Definitions and abbreviations
- Clause 4 - Applicability
- Clause 5 - Main concepts
- Clause 6 - Elementary procedures for Broadcast Call Control
- Clause 7 - Handling of unknown, unforeseen, and erroneous protocol data
- Clause 8 - Message functional definitions and contents
- Clause 9 - Contents of information elements value parts
- Annex A - Change Request History
What are the key requirements of SIST EN 300 949 V6.2.1:2003?
Call setup, entities, and state control
Clause 5 makes BCC a Connection Management (CM) sublayer protocol that uses the MM and RR sublayers from GSM 04.08. The protocol is described as a dialogue between peer entities in the MS and the network, with more than one MS potentially participating in the same broadcast call.
A practical point is that the originator of the BCC transaction chooses the Transaction Identifier (TI), while a non-originating MS reuses the received TI with the adjusted flag value. That matters when several broadcast call transactions exist at once, because the receiver has to match the message to the correct call leg.
Clause 6.1.2 defines the MS state machine, including 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 has its own states N0 to N4. Implementers need explicit state handling because the allowed actions, timers, and parameter values depend on the current state.
Parameters, timers, and establishment procedures
Clause 6.1.2.1.1 defines the key MS parameters ORIG, COMM, D-ATT, and U-ATT. ORIG and COMM describe the MS behavior context, while D-ATT and U-ATT control whether the user connection is attached in the downlink and uplink. In practice, a BCC implementation has to keep these values aligned with the active state, not only parse messages.
Table 6.1 defines timers used by BCC, including timers for setup, receive mode, termination, and connection-request waiting. These timers drive recovery when setup stalls, when no channel is available, or when termination is pending. In practice, the timers determine when the MS clears context, aborts resources, or informs higher layers.
Clause 6.2 distinguishes network-initiated activation, mobile-originated establishment, and mobile-terminating establishment. The MS may start a call with SETUP after an MM connection or with IMMEDIATE SETUP without a prior MM connection. That means an implementation must support both signalling paths.
Active behavior, receive mode, and ending a call
Clause 6.3 covers the active state and the RECEIVE MODE ACTIVE state. In the active state, the network performs supervisory and resource modification functions, and it may send SET PARAMETER to change MS parameters and trigger consequential actions. In RECEIVE MODE ACTIVE, the MS monitors channel availability and uses timer handling to decide whether to stay available or abort resources.
Clause 6.4 defines release, abortion, and termination. The originator uses TERMINATION REQUEST, the network may answer with TERMINATION or TERMINATION REJECT, and either side may request abort or release through the lower sublayers. In practice, implementers need to clear the broadcast-call context and return to NULL when termination or release completes.
Error handling and message coding
Clause 7 defines how the MS handles short messages, unknown transaction identifiers, unknown message types, mandatory IE errors, repeated or out-of-sequence information elements, and semantically incorrect contents. The default behavior is to ignore invalid input unless COMM = T, in which case the MS returns a STATUS message with the appropriate cause and, where possible, diagnostics. This is important for interoperability and for future protocol extensions.
Clause 8 and clause 9 define the message set and the coding of their value parts. The document fixes the permitted information elements and their order in each BCC message, so senders cannot add arbitrary elements or reorder them. This is the part implementers use for encoding and decoding BCC messages on the radio interface.
What terms does SIST EN 300 949 V6.2.1:2003 define?
- Broadcast Call Control (BCC) - The protocol that controls broadcast call setup, operation, and release in GSM Phase 2+.
- Mobile Station (MS) - The mobile terminal side of the protocol, which can initiate, receive, and terminate broadcast calls.
- Broadcast call channel - The common downlink channel allocated in each cell for a particular broadcast call.
- Calling user - The BCC entity in the MS that initiates, or has initiated, a broadcast call.
- D-ATT - A configuration parameter that says whether the user connection for the broadcast call is attached in the downlink.
- U-ATT - A configuration parameter that says whether the user connection for the broadcast call is attached in the uplink.
- ORIG / COMM - Behaviour parameters that indicate whether the MS is the originator of the call and whether communication with the peer entity is enabled in both directions.
Who uses SIST EN 300 949 V6.2.1:2003?
SIST EN 300 949 V6.2.1:2003 is used by GSM radio interface and core network engineers who implement voice broadcast call signalling. It is also used by MS vendors, network equipment suppliers, and protocol software developers who need to encode, decode, and state-machine test BCC.
Quality teams and conformance labs use it to verify message formats, state transitions, timer behavior, and error handling. Buyers and technical evaluators use it to check whether a product supports broadcast call control in the GSM Phase 2+ / Release 1997 environment.
What changed in SIST EN 300 949 V6.2.1:2003 from the previous edition?
SIST EN 300 949 V6.2.1:2003 updates ETSI EN 300 949 Version 6.2.0 to Version 6.2.1 for publication. Annex A lists the change history, including the correction of the reject cause in termination, a message name correction, and earlier Release 1997 updates to the broadcast call control states, state attributes, the call state IE, and the coding of the Call Reference IE.
Which standards are used with SIST EN 300 949 V6.2.1:2003?
| Standard | What it contributes |
|---|---|
| GSM 01.04 | Abbreviations and acronyms used across GSM documents. |
| GSM 02.69 | Voice Broadcast Call Service (VBCS) stage 1 service definition. |
| GSM 03.03 | Numbering, addressing, and identification, including broadcast call reference coding context. |
| GSM 03.67 | enhanced Multi-Level Precedence and Pre-emption service (eMLPP) stage 2, used for priority-related context. |
| GSM 03.69 | VBCS stage 2, including the service behavior that BCC supports. |
| GSM 04.06 | MS-BSS interface Data Link (DL) layer specification. |
| GSM 04.07 | General layer 3 aspects, message structure, and protocol formatting rules. |
| GSM 04.08 | Layer 3 signalling behavior, MM and RR interaction, and related procedures. |
What does the SIST EN 300 949 V6.2.1:2003 document contain?
Clause 6 contains the BCC state machines, elementary procedures, and timer behavior for setup, active operation, receive mode, termination, abort, and release. Clause 7 contains the error-handling rules for malformed or unexpected protocol data.
Clause 8 contains the message definitions for CONNECT, GET STATUS, IMMEDIATE SETUP, SET PARAMETER, SETUP, STATUS, TERMINATION, TERMINATION REJECT, and TERMINATION REQUEST. Clause 9 contains the coding rules for protocol discriminator, transaction identifier, message type, call reference, call state, cause, originator indication, spare half octet, and state attributes.
Annex A is an informative change request history that shows how the specification evolved through the Release 1997 updates and the final publication version.
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 V6.2.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 6.2.1 Release 1997)". This standard covers: Upgrade from Phase 2+ to Release 1997
Upgrade from Phase 2+ to Release 1997
SIST EN 300 949 V6.2.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 V6.2.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)
SLOVENSKI STANDARD
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ±3URWRNRONUPLOMHQMD
UDGLRGLIX]LMVNHJDNOLFD %&& *60 UD]OLþLFDL]GDMD
Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control
(BCC) protocol (GSM 04.69 version 6.2.1 Release 1997)
Ta slovenski standard je istoveten z: EN 300 949 Version 6.2.1
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.
ETSI EN 300 949 V6.2.1 (2000-04)
European Standard (Telecommunications series)
Digital cellular telecommunications system (Phase 2+);
Broadcast Call Control (BCC) protocol
(GSM 04.69 version 6.2.1 Release 1997)
R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
(GSM 04.69 version 6.2.1 Release 1997) 2 ETSI EN 300 949 V6.2.1 (2000-04)
Reference
REN/SMG-030469Q6R2
Keywords
Digital cellular telecommunications system,
Global System for Mobile communications (GSM)
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.:+33492944200 Fax:+33493654716
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network
drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://www.etsi.org/tb/status/
If you find errors in the present document, send your comment to:
editor@etsi.fr
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 2000.
All rights reserved.
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 3 ETSI EN 300 949 V6.2.1 (2000-04)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.6
3 Definitions and abbreviations .6
3.1 Definitions.6
3.2 Abbreviations .7
4 Applicability.7
5 Main concepts .7
6 Elementary procedures for Broadcast Call Control .8
6.1 Overview .8
6.1.1 General.8
6.1.2 Broadcast call control states .8
6.1.2.1 Broadcast call control states at the MS side of the interface .8
6.1.2.1.1 Attributes and Parameters of BCC in the MS.8
6.1.2.1.2 NULL (U0).9
6.1.2.1.3 MM CONNECTION PENDING (U0.p) .9
6.1.2.1.4 BROADCAST CALL INITIATED (U1) .9
6.1.2.1.5 BROADCAST CALL ACTIVE (U2).9
6.1.2.1.6 BROADCAST CALL PRESENT (U3).9
6.1.2.1.7 BROADCAST CALL CONNECTION REQUESTED (U4) .9
6.1.2.1.8 TERMINATION REQUESTED (U5).9
6.1.2.1.9 RECEIVE MODE ACTIVE (U6) .9
6.1.2.1.10 BCC TIMERS IN THE MS.10
6.1.2.1.11 CONSISTENCY OF PARAMETERS AND STATES .10
6.1.2.2 BROADCAST CALL CONTROL STATES AT THE NETWORK SIDE OF THE INTERFACE.10
6.1.2.2.1 NULL (State N0).10
6.1.2.2.2 BROADCAST CALL INITIATED (N1) .10
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.11
6.2.1 Activation of a broadcast call by the network.11
6.2.2 Mobile originated establishment.11
6.2.2.1 Termination during mobile originated establishment.12
6.2.2.2 Abnormal cases .12
6.2.3 Mobile terminating broadcast call establishment in the MS .12
6.3 Procedures during the active state and receive mode active state of a broadcast call.12
6.3.1 Mobile station procedures in the active state .12
6.3.2 Network procedures in the active state .13
6.3.3 Mobile station procedures in the RECEIVE MODE ACTIVE state.13
6.4 Procedures for release, abortion, and termination of a broadcast call .13
6.4.1 Termination procedure.13
6.4.2 Abort and release procedures.14
6.5 Miscellaneous procedures .14
6.5.1 Status procedures.14
6.5.1.1 Get status procedure.14
6.5.1.2 Set parameter procedure.14
7 Handling of unknown, unforeseen, and erroneous protocol data .14
7.1 General .14
7.2 Message too short.15
7.3 Unknown or unforeseen transaction identifier.15
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 4 ETSI EN 300 949 V6.2.1 (2000-04)
7.4 Unknown or unforeseen message type.15
7.5 Non-semantical mandatory information element errors.15
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.16
7.6.3 Repeated Information elements.16
7.7 Non-imperative message part errors.16
7.7.1 Syntactically incorrect optional Information elements.16
7.8 Messages with semantically incorrect contents .16
8 Message functional definitions and contents .16
8.1 CONNECT.17
8.2 GET STATUS.18
8.2.1 mobile identity .18
8.3 IMMEDIATE SETUP.18
8.3.1 Mobile identity.19
8.4 SET PARAMETER.19
8.5 SETUP .19
8.6 STATUS.20
8.6.1 Call state .20
8.6.2 State attributes .20
8.7 TERMINATION .21
8.8 TERMINATION REJECT.21
8.9 TERMINATION REQUEST .21
9 Contents of information elements value parts.22
9.1 Protocol Discriminator .22
9.2 Transaction identifier .22
9.3 Message Type.22
9.4 Other information elements .22
9.4.1 Call Reference .23
9.4.2 Call state .23
9.4.3 Cause .24
9.4.4 Originator indication.25
9.4.5 Spare Half Octet .26
9.4.6 State attributes .26
Annex A (informative): Change Request History .27
History.28
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 5 ETSI EN 300 949 V6.2.1 (2000-04)
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 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 cellular
telecommunications system (Phase 2+).
The contents of the present document is subject to continuing work within SMG and may change following formal SMG
approval. Should SMG modify the contents of the present document it will be re-released with an identifying change of
release date and an increase in version number as follows:
Version 6.x.y
where:
6 indicates Release 1997 of GSM Phase 2+.
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.
National transposition dates
Date of adoption of this EN: 31 March 2000
Date of latest announcement of this EN (doa): 30 June 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 December 2000
Date of withdrawal of any conflicting National Standard (dow): 31 December 2000
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 6 ETSI EN 300 949 V6.2.1 (2000-04)
1 Scope
The present document specifies the Broadcast Call Control (BCC) protocol used by the Voice Broadcast Call Service
(VBCS) on the radio interface.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-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 same
number.
• 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 and
acronyms".
[2] GSM 02.69): "Digital cellular telecommunications system (Phase 2+); Voice Broadcast Call
Service (VBCS) stage 1".
[3] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing and
identification".
[4] GSM 03.67: "Digital cellular telecommunications system (Phase 2+); enhanced Multi-Level
Precedence and Pre-emption service (eMLPP) - Stage 2".
[5] GSM 03.69: "Digital cellular telecommunications system (Phase 2+); Voice Broadcast Call
Service (VBCS) stage 2".
[6] GSM 04.06: "Digital cellular telecommunications system (Phase 2+); Mobile Station - Base
Station System (MS - BSS) interface Data Link (DL) layer specification".
[7] GSM 04.07: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface
signalling layer 3 General aspects".
[8] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface
layer 3 specification".
3 Definitions and abbreviations
3.1 Definitions
Definitions 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 broadcast
call. All MSs of the listening service subscribers in one cell shall listen to the common downlink.
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 7 ETSI EN 300 949 V6.2.1 (2000-04)
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.
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 the present document are also listed in GSM 01.04.
For the purposes of the present document, 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
The present document 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 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 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 the present document).
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.
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 8 ETSI EN 300 949 V6.2.1 (2000-04)
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.
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 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", the present document often uses the terms "MS" and "network" if no
confusion may arise.
Certain sequences of actions of the two peer entities compose "elementary procedures" which are used as a basis for the
description 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, take
appropriate means to resolve the problems. This, however, is out of the scope of the present document.
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).
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 9 ETSI EN 300 949 V6.2.1 (2000-04)
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.
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
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 10 ETSI EN 300 949 V6.2.1 (2000-04)
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).
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 on subclause
(sub-)layers that no channel from lower (sub-)layers that a further 6.3.1
is currently available channel is available conditions
T when entering U0.p using the when leaving U0.p or U1 U0.p, U1 see 5s
MM-est
set-up procedure subclause
when entering U1 using the 6.2.1
immediate set-up procedure
T when sending a when receiving a U5 abort 10 s
term
TERMINATION REQUEST TERMINATION or broadcast
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.
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 11 ETSI EN 300 949 V6.2.1 (2000-04)
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.
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 state U1, BC INITIATED.
MM-est
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
MM-est
state U1, BC INITIATED.
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
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 12 ETSI EN 300 949 V6.2.1 (2000-04)
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
MM-est
enter state U2, ACTIVE. If the immediate set-up procedure has been used, the BCC entity in the MS shall inform lower
sub-layers that the MM connection has been implicitly established.
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 resources. The
further actions are specified in subclause 6.4.
During mobile originated establishment of a broadcast call, the MS may abort the broadcast call, see subclause 6.4.
6.2.2.2 Abnormal cases
At expiry of T , or radio link failure (see GSM 04.08), the BCC entity in the MS requests lower sub-layers to abort
MM-est
the MM connection establishment and returns to state U0, NULL(this includes clearing of the context related to the
broadcast call establishment).
On receipt of an indication of lower sub-layers that the MM connection establishment was unsuccessful, the BCC entity
in the MS returns to state U0, NULL (this includes clearing of the context related to the broadcast call establishment).
6.2.3 Mobile terminating broadcast call establishment in the MS
The BCC entity in the MS, being in state U0, NULL, may receive an indication of lower layers that a broadcast call
exists. This indication specifies the broadcast-id and a priority. It shall then inform higher layers and enter state U3, BC
present. This state may be supervised by a timer at expiry of which the BCC entity clears the context and returns to state
U0, NULL.
In state U3, on request of higher layers to join the broadcast call, the BCC entity in the MS stops any running timer, asks
lower sub-layers to join the broadcast call, starts timer T , and enters state U4, BC CONNECTION
conn req
REQUESTED.
In state U4, on indication of lower sub-layers that the broadcast call has been joint (this indication specifies the mode of
the RR connection), the BCC entity in the MS stops any running timer, enters state U6, RECEIVE MODE ACTIVE,
establishes the appropriate configurations (see subclause 6.1) and informs higher layers (this includes information about
the sub-state).
6.3 Procedures during the active state and receive mode active
state of a broadcast call
6.3.1 Mobile station procedures in the active state
In the active state, the BCC entity in the MS performs, on receipt of messages from its peer entity, on request of higher
layers, and on indication of lower sub-layers, actions as defined below.
On request of higher layers, the MS initiates abort or termination of the broadcast call, see subclause 6.4.
If the network initiates broadcast call abortion or termination, the MS reacts as specified in subclause 6.4.
On radio link failure, the MS aborts the broadcast call, see subclause 6.4.
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 13 ETSI EN 300 949 V6.2.1 (2000-04)
6.3.2 Network procedures in the active state
In the active state the BCC entity in the network performs supervisory functions, maintenance functions and resource
modifications which are not further specified. (This includes through-connection of the application data stream(s), which
is defined in GSM 03.69.)
The network may initiate abort or termination of the broadcast call, see subclause 6.4.
If the MS initiates broadcast call abortion or termination, the network reacts as specified in subclause 6.4.
The network may send a SET PARAMETER message to the MS in order to ask the MS to set parameters to certain
values and to take consequential actions.
6.3.3 Mobile station procedures in the RECEIVE MODE ACTIVE state
In state U6, RECEIVE MODE ACTIVE, the BCC entity in the MS performs, on receipt of messages from its peer
entity, on request of higher layers, and on indication of lower sub-layers, actions as defined below.
On request of higher layers, the MS initiates abort of the broadcast call, see subclause 6.4.
If the network initiates broadcast call abortion or termination, the MS reacts as specified in subclause 6.4.
Upon indication from lower layers that no channel is available, the BCC entity in the MS informs higher layers and
starts timer T . Then:
no channel
if T expires, the BCC entity in the MS informs higher layers, asks lower sub-layers to abort resources and
no channel
enters the idle state
upon indication from lower layers that a channel is available, the BCC entity in the MS informs higher layers and stops
timer T .
no channel
6.4 Procedures for release, abortion, and termination of a
broadcast call
6.4.1 Termination procedure
The MS being the originator of the broadcast call (ORIG = T) shall, on request of higher layers,
initiate the termination procedure by sending a TERMINATION REQUEST message to its peer entity in the network
and setting timer T .
term
The network either accepts the termination by sending a TERMINATION or rejects termination by sending a
TERMINATION REJECT. These messages indicate an appropriate cause.
In state U5, on receipt of a TERMINATION REJECT message, the BCC entity in the MS informs higher layers and
stops T .
term
In state U5, on T expiry, the BCC entity in the MS informs higher layers, asks lower sub-layers to abort the
term
broadcast call, clears the context related to the broadcast call, and returns to state U0, NULL.
In any state, on receipt of a TERMINATION message, the BCC entity in the MS informs higher layers, asks lower
sub-layers to release the broadcast call, clears the context related to the broadcast call, and returns to state U0, NULL.
At any time during 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 resources. The further actions are specified above in this
subclause 6.4.
ETSI
(GSM 04.69 version 6.2.1 Release 1997) 14 ETSI EN 300 949 V6.2.1 (2000-04)
6.4.2 Abort and release procedures
The network may ask lower sub-layers to abort or release the broadcast call. The MS will detect abort of the broadcast
call by detecting the abort of RR resources, and a broadcast call release by detecting the release of RR resources. The
BCC entity in the MS shall then inform higher layers, ask lower sub-layers to abort the broadcast call, clear the context
related to the broadcast call, and return to state U0, NULL.
The MS shall, on request of higher layers, initiate the release procedure by asking lower sub-layers to release the
broadcast call, clearing the context related to the broadcast call, and returning to state U0, NULL.
The BCC entity in the MS shall when required by the BCC protocol, abort the broadcast call by requesting lower layers
to abort the broadcast call, informing higher layers, clearing the context related to the broadcast call, and returning to
state U0, NULL.
6.5 Miscellaneous procedures
6.5.1 Status procedures
6.5.1.1 Get status procedure
Upon receipt of a GET STATUS message, the MS shall:
- if COMM = T, respond with a STATUS message, reporting the current call state, the current values of
configuration and behaviour parameters and cause value # 30 "Response to GET STATUS";
- if COMM = F, ignore the message.
6.5.1.2 Set parameter procedure
Upon receipt of a SET PARAMETER message the MS shall set the parameters to the indicated values and the
configuration shall be adapted to the new values of configuration parameters, if they are consistent with the current BCC
state and sub-state (see subclause 6.1.2). If they are not:
- if COMM , before the message was received, is equal to T, it shall send a STATUS message specifying error
cause "message incompatible with protocol state", the state and, if applicable, sub-state, and the state attributes
IE;
- if COMM , before the message was received, is equal to F, it shall ignore the message.
7 Handling of unknown, unforeseen, and erroneous
protocol data
7.1 General
This clause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving
BCC protocol entity in the MS. These procedures are called "error handling procedures", but in addit
...