ETSI TS 144 069 V16.0.0 (2020-08)

Digital cellular telecommunications system (Phase 2+) (GSM); Broadcast Call Control (BCC) protocol (3GPP TS 44.069 version 16.0.0 Release 16)

RTS/TSGC-0144069vg00

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 12 - Completion
• Completion Date: 06-Aug-2020

Standards Content (Sample)

ETSI TS 144 069 V16.0.0 (2020-08)






TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Broadcast Call Control (BCC) protocol
(3GPP TS 44.069 version 16.0.0 Release 16)

R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS

---------------------- Page: 1 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 1 ETSI TS 144 069 V16.0.0 (2020-08)



Reference
RTS/TSGC-0144069vg00
Keywords
GSM
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 2 ETSI TS 144 069 V16.0.0 (2020-08)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 ETSI 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 (https://ipr.etsi.org/).
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 ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 3 ETSI TS 144 069 V16.0.0 (2020-08)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
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) . 10
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) . 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 . 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 . 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 . 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 . 15
7.1 General . 15
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 4 ETSI TS 144 069 V16.0.0 (2020-08)
7.2 Message too short . 15
7.3 Unknown or unforeseen transaction identifier . 15
7.4 Unknown or unforeseen message type . 15
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. 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 . 17
8 Message functional definitions and contents . 17
8.1 CONNECT . 18
8.2 GET STATUS . 18
8.2.1 mobile identity . 18
8.3 IMMEDIATE SETUP . 19
8.3.1 Mobile identity . 19
8.3a IMMEDIATE SETUP 2 . 19
8.3a.1 TMSI . 20
8.3a.2 Compressed otdi . 20
8.4 SET PARAMETER . 20
8.5 SETUP . 20
8.5.1 Originator-to-dispatcher information . 21
8.6 STATUS . 21
8.6.1 Call state . 21
8.6.2 State attributes . 22
8.7 TERMINATION . 22
8.8 TERMINATION REJECT . 22
8.9 TERMINATION REQUEST . 23
9 Contents of information elements value parts . 23
9.1 Protocol Discriminator . 23
9.2 Transaction identifier . 23
9.3 Message Type . 23
9.4 Other information elements . 24
9.4.1 Call Reference . 24
9.4.2 Call state . 25
9.4.3 Cause . 26
9.4.4 Originator indication . 27
9.4.5 Spare Half Octet . 28
9.4.6 State attributes . 28
9.4.7 Compressed otdi . 28
Annex A (informative):  Example of the coding of the user-user information after
decompression of the originator-to-dispatcher information . 29
Annex B (informative): Change History . 30
History . 31

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 5 ETSI TS 144 069 V16.0.0 (2020-08)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.

ETSI

---------------------- Page: 6 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 6 ETSI TS 144 069 V16.0.0 (2020-08)
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. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] Void.
[1a] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 42.069: "Voice Broadcast Service (VBS); Stage 1".
[3] 3GPP TS 23.003: "Numbering, addressing and identification".
[4] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2".
[5] 3GPP TS 43.069: "Voice Broadcast Call Service (VBCS); Stage 2".
[6] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL)
layer specification".
[7] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[8] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols;
Stage 3".
[9] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[10] 3GPP TS 44.068: "Group Call Control (GCC) protocol".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions defined in 3GPP TS 42.069 and the following
apply:
Attachment of the user connection: See 3GPP TS 24.008, 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.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 7 ETSI TS 144 069 V16.0.0 (2020-08)
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 3GPP TS 44.018.
Originating mobile station: MS initiating or having initiated the broadcast call.
Uplink: Mobile station to network direction.
3.2 Abbreviations
For the purposes of the present document, the abbreviation defined in 3GPP TR 21.905 [1a] and the following 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 3GPP TS 24.007).
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 3GPP TS 44.068), 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.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 8 ETSI TS 144 069 V16.0.0 (2020-08)
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 3GPP TS 24.008 and 3GPP TS 44.018. 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

---------------------- Page: 9 ----------------------
3GPP TS 44.069 version 16.0.0 Release 16 9 ETSI TS 144 069 V16.0.0 (2020-08)
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, pa
...