ETSI TS 124 010 V19.1.0 (2026-03)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Mobile radio interface layer 3; Supplementary services specification; General aspects (3GPP TS 24.010 version 19.1.0 Release 19)

RTS/TSGC-0424010vj10

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 10-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Mobile radio interface layer 3;
Supplementary services specification;
General aspects
(3GPP TS 24.010 version 19.1.0 Release 19)

3GPP TS 24.010 version 19.1.0 Release 19 1 ETSI TS 124 010 V19.1.0 (2026-03)

Reference
RTS/TSGC-0424010vj10
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
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 on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2026.
All rights reserved.
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 2 ETSI TS 124 010 V19.1.0 (2026-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo 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.
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 at 3GPP to ETSI numbering cross-referencing.
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
3GPP TS 24.010 version 19.1.0 Release 19 3 ETSI TS 124 010 V19.1.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
1.1 References . 6
1.2 Abbreviations . 8
2 Generic procedures for the control of supplementary services . 9
2.1 Overview of the generic protocol and its scope . 9
2.2 Functional procedures for the control of supplementary services . 9
2.2.1 General . 9
2.2.2 Separate Messages Category. 10
2.2.3 Common Information Element Category . 10
2.2.4 Call related supplementary service procedures . 10
2.2.4.1 Supplementary service procedures at call establishment or call clearing . 10
2.2.4.1.1 Encoding of the Facility IEI for different supplementary services . 11
2.2.4.1.2 Supplementary service procedures at network initiated mobile originating call establishment . 11
2.2.4.2 Supplementary service procedures during the call . 12
2.2.4.3 Handling of protocol errors in call related SS procedures. 12
2.2.4.4 Handling of other errors in call related SS procedures . 12
2.2.5 Call independent supplementary service procedures . 13
2.2.5.1 Introduction . 13
2.2.5.2 Handling of protocol errors in call independent SS procedures . 13
2.2.5.3 Handling of other errors in call independent SS procedures . 13
2.2.6 Multiple supplementary service invocatio ns . 13
2.2.6.1 Call related supplementary service procedures . 13
2.2.6.2 Call independent supplementary service procedures . 14
2.2.7 Recovery procedures. 14
2.2.7.1 Call related supplementary service recovery procedures . 14
2.2.7.2 Call independent supplementary service recovery procedures . 14
2.2.8 Generic protocol error handling for the component part of supplementary services operations . 14
2.2.8.1 Call related component errors . 14
2.2.8.2 Call independent component errors . 14
2.2.8.2.1 Single component errors . 14
2.2.8.2.2 Multiple component errors . 15
3 Supplementary service support procedures . 15
3.1 General . 15
3.2 Supplementary service support establishment . 15
3.2.1 Supplementary service support establishment at the originating side . 15
3.2.2 Supplementary service support establishment at the terminating side . 15
3.3 Supplementary service support information transfer phase . 15
3.4 Supplementary service support release . 15
3.5 Recovery procedures . 16
3.6 Message flow (single operation example) . 16
3.6.1 Mobile station initiated supplementary service transaction . 16
3.6.2 Network initiated supplementary service transaction . 17
3.7 Handling of unknown, unforeseen, and erroneous protocol data . 17
3.7.1 General . 17
3.7.2 Message too short . 18
3.7.3 Unknown or unforeseen transaction identifier . 18
3.7.4 Unknown or unforeseen message type. 18
3.7.5 Non-semantical mandatory Information Element Error. 18
3.7.6 Unknown and Unforeseen IEs in the non-imperative part . 19
3.7.6.1 IEIs unknown in the message . 19
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 4 ETSI TS 124 010 V19.1.0 (2026-03)
3.7.6.2 Out of sequence IEs . 19
3.7.6.3 Repeated IEs . 19
3.7.7 Non-imperative message part errors . 19
3.7.7.1 Syntactically incorrect optional IEs (other than Facility) . 19
3.7.7.2 Conditional IE errors . 19
4 Password management . 20
4.1 Password check . 20
4.1.1 Successful procedure . 20
4.1.2 Error cases . 20
4.2 Password registration . 21
4.2.1 Successful procedure . 21
4.2.2 Error cases . 21
4.3 Cross phase compatibility . 22
5 Supplementary service cross phase compatibility . 23
5.1 Cross phase, or cross protocol version, interworking . 23
5.2 Objectives . 23
5.3 Supplementary service compatibility philosophy . 23
5.4 Compatibility mechanisms . 24
5.4.1 SS screening indicator . 24
5.4.2 SS version indicator . 24
5.4.3 Protocol extension mechanism . 24
5.5 SS compatibility procedures . 24
5.5.1 Screening indicator procedures . 24
5.5.1.1 MS procedure . 24
5.5.1.2 Network procedure . 25
5.5.2 SS version indicator procedures . 25
5.5.2.1 MS procedure . 25
5.5.2.1.1 MS procedure for version 3 or higher operations . 25
5.5.2.2 Network procedure . 26
5.5.2.2.1 Call independent SS activity . 26
5.5.2.2.2 Call related SS activity . 26
5.5.3 Extension mechanism procedures . 26
5.5.4 SS version indicator - MAP context interworking . 26
5.5.4.1 Call independent interworking . 26
5.5.4.2 Call related interworking . 27
5.6 Development of future protocol versions . 27
6 Forward Check SS Indication. 27
Annex A (normative): Notation used for stage 3 description of supplementary services . 28
A.1 General structure of the SS stage 3 diagrams . 28
A.1.1 Exceptional release procedures . 29
A.2 Messages used to transport operations . 29
A.3 Contents of messages . 29
Annex B (informative): Change history . 31
History . 32

ETSI
3GPP TS 24.010 version 19.1.0 Release 19 5 ETSI TS 124 010 V19.1.0 (2026-03)
Foreword
rd
This Technical Specification (TS) has been produced by the 3 Generation Partnership Project (3GPP).
The present document defines the general aspects of the specification of supplementary services at the layer 3 radio
interface within the 3GPP system.
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
3GPP TS 24.010 version 19.1.0 Release 19 6 ETSI TS 124 010 V19.1.0 (2026-03)
1 Scope
The present document gives the general aspects of the specification of supplementary services at the layer 3 radio
interface.
3GPP TS 24.08x and 24.09x-series specify the procedures used at the radio interface (reference point Um as defined in
3GPP 24.002) for normal operation, registration, erasure, activation, deactivation, invocation and interrogation of
supplementary services. Provision and withdrawal of supplementary services is an administrative matter between the
mobile subscriber and the service provider and cause no signalling on the radio interface.
3GPP TS 24.008 [48] and 3GPP TS 24.080 [27] specifies the formats and coding for the supplementary services.
Definitions and descriptions of supplementary services are given in 3GPP TS 22.004 and 3GPP TS 22.08x and
22.09x-series.
Technical realization of supplementary services is described in 3GPP TS 23.011 and GSM 23.08x and 23.09x-series.
The procedures for Call Control, Mobility Management and Radio Resource management at the layer 3 radio interface
are defined in 3GPP TS 24.007 [49] and 3GPP TS 24.008 [48].
1.1 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] 3GPP TS 21.905: "Abbreviations and acronyms".
[2] 3GPP TS 22.004: "General on supplementary services".
[3] 3GPP TS 22.081: "Line identification supplementary services - Stage 1".
[4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1".
[5] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 1".
[6] 3GPP TS 22.084: "MultiParty (MPTY) supplementary services - Stage 1".
[7] 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1".
[8] 3GPP TS 22.086: "Advice of charge (AoC) supplementary services - Stage 1".
[9] 3GPP TS 22.088: "Call Barring (CB) supplementary services - Stage 1".
[10] 3GPP TS 22.090: "Unstructured Supplementary Services Data (USSD) - Stage 1".
[11] 3GPP TS 22.091: "Explicit Call Transfer (ECT) supplementary service - Stage 1".
[12] 3GPP TS 23.011: "Technical realization of supplementary services".
[13] 3GPP TS 23.081: "Line identification supplementary services - Stage 2".
[14] 3GPP TS 23.082: "Call Forwarding (CF) supplementary services - Stage 2".
[15] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2".
[16] 3GPP TS 23.084: "MultiParty (MPTY) supplementary services - Stage 2".
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 7 ETSI TS 124 010 V19.1.0 (2026-03)
[17] 3GPP TS 23.085: "Closed User Group (CUG) supplementary services - Stage 2".
[18] 3GPP TS 23.086: "Advice of Charge (AoC) supplementary services - Stage 2".
[19] 3GPP TS 23.088: "Call Barring (CB) supplementary services - Stage 2".
[20] 3GPP TS 23.090: "Unstructured supplementary services operation - Stage 2".
[21] 3GPP TS 23.091: "Explicit Call Transfer (ECT) supplementary service - Stage 2".
[22] 3GPP TS 24.002: "GSM Public Land Mobile Network (PLMN) access reference configuration".
[23] 3GPP TS 24.003: "Mobile Station - Base Stations system (MS - BSS) interface; Channel structures
and access capabilities".
[24] 3GPP TS 24.004: "Layer 1; General requirements".
[25] 3GPP TS 44.005: "Data Link (DL) layer; General aspects".
[26] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL)
layer specification".
[27] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification; Formats
and coding".
[28] 3GPP TS 24.081: "Line identification supplementary services - Stage 3".
[29] 3GPP TS 24.082: "Call Forwarding (CF) supplementary services - Stage 3".
[30] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3".
[31] 3GPP TS 24.084: "MultiParty (MPTY) supplementary services - Stage 3".
[32] 3GPP TS 24.085: "Closed User Group (CUG) supplementary services - Stage 3".
[33] 3GPP TS 24.086: "Advice of Charge (AoC) supplementary services - Stage 3".
[34] 3GPP TS 24.088: "Call Barring (CB) supplementary services - Stage 3".
[35] 3GPP TS 24.090: "Unstructured supplementary services operation - Stage 3".
[36] 3GPP TS 24.091: "Explicit Call Transfer (ECT) supplementary service - Stage 3".
[37] 3GPP TS 45.001: "Physical layer on the radio path; General description".
[38] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".
[39] 3GPP TS 45.003: "Channel coding".
[40] 3GPP TS 45.004: "Modulation".
[41] 3GPP TS 45.005: "Radio transmission and reception".
[42] 3GPP TS 45.008: "Radio subsystem link control".
[43] 3GPP TS 45.010: "Radio subsystem synchronization".
[44] GSM 05.90: "Digital cellular telecommunications system; GSM Electro Magnetic Compatibility
(EMC) considerations".
[45] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[46] 3GPP TS 29.011: "Signalling interworking for supplementary services".
[47] CCITT Recommendation Q.774 (White Book): "Specifications of Signalling System No.7;
Transaction capabilities procedures".
[48] 3GPP TS 24.008: "Core network protocols; Stage 3".
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 8 ETSI TS 124 010 V19.1.0 (2026-03)
[49] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[50] 3GPP TS 24.571: "Control plane Location Services (LCS) procedures; Stage 3".
1.2 Abbreviations
Abbreviations used in the present document are listed in 3GPP TS 21.905.
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 9 ETSI TS 124 010 V19.1.0 (2026-03)
2 Generic procedures for the control of supplementary
services
2.1 Overview of the generic protocol and its scope
One generic protocol is defined for the control of supplementary services at the radio interface. This protocol operates at
layer 3 of the radio interface and assumes the use of layers 1 and 2 conform to 3GPP TS 45-series and 3GPP TS 44.004,
3GPP TS 44.005 and 3GPP TS 44.006. The generic protocol uses the acknowledged information transfer service
available at the layer 2 - layer 3 interface.
The Functional protocol is based on the use of the Facility information element and the FACILITY message as well as
other specific functional messages specified in 3GPP TS 24.080 [27].
Standardised services use a functional protocol. A transparent protocol is also provided. The functional protocol
requires the knowledge of the related supplementary service by the mobile equipment supporting it. This facilitates
mobile equipment operation without human intervention by defining semantics for the protocol elements which the
mobile equipment can process on its own.
2.2 Functional procedures for the control of supplementary
services
2.2.1 General
This clause specifies the functional signalling procedures for the control of supplementary services at the radio
interface.
The Functional protocol is based on the use of the (Extended) Facility information element and the FACILITY message
as well as other specific functional messages specified in 3GPP TS 24.080 [27]. For messages used in 5GS LCS
procedures, when the MS and network support the "ExtendedFacility IE for 5G LCS" (as specified in
3GPP TS 24.571 [50]) and the length of the component cannot be fitted into the Facility IE, the ExtendedFacility IE is
used to carry the component in such messages. In this case, the requirements in this specification applied to the Facility
IE are applied to the ExtendedFacility IE.
In UMTS only, integrity protected signalling (see TS 24.008 [48], subclause 'Integrity Protection of Signalling
Messages,' and in general, see 3GPP TS 33.102) is mandatory. In UMTS only, all protocols shall use integrity protected
signalling. Integrity protection of all SS signalling messages is the responsibility of lower layers. It is the network which
activates integrity protection. This is done using the security mode control procedure (TS 25.331).
The defined procedures specify the basic methodology for the control (e.g. registration, erasure, invocation, etc.) of
supplementary services.
The first category, called the Separate Message Category utilises separate message types to indicate a desired function.
The hold and retrieve families of messages are identified for this category.
The second category called the Common Information Element Category utilises the Facility information element to
transport the protocol defined in 3GPP TS 24.080 [27]. The use of the Facility information element is common to many
services, and its contents indicates what type of procedure is being requested. This category can be signalled both in the
mobile to network and the network to mobile directions.
The control of supplementary services includes the following cases:
a) the request of supplementary service procedures during the establishment of a call;
b) the request of supplementary service procedures during the clearing of a call;
c) the request of call related supplementary service procedures during the active state of a call;
d) the request of supplementary service procedures independent from an active call;
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 10 ETSI TS 124 010 V19.1.0 (2026-03)
e) the request of multiple, different supplementary service procedures within a single message;
f) the request of supplementary service procedures related to different calls.
The correlation of a call related supplementary service operation and the call which it modifies is provided by use of the
transaction identifier (cases a, b, c, e and f).
The correlation of supplementary service operations and their responses, is provided by the combination of the
transaction identifier of the messages containing the Facility information element and the Invoke identifier present
within the Facility information element itself (cases a, b, c, d, e and f).
The identification of different supplementary service operations within one single message is provided by the Invoke
identifier present within the Facility information element itself (case e).
The identification of supplementary service related operations to different calls is provided by using different messages
with the corresponding transaction identifier of the appropriate call (case f), i.e. different transaction identifier values
are used to identify each call individually.
2.2.2 Separate Messages Category
The messages defined in this clause are specified as separate functional messages for the request, acknowledgement and
rejection of specific procedures. These procedures can only be performed during the active phase of a call. The
functions of these messages are not to be duplicated or overlapped by the ones of the Common Information Element
Category.
The following separate messages are defined:
HOLD RETRIEVE
HOLD ACKNOWLEDGE RETRIEVE ACKNOWLEDGE
HOLD REJECT RETRIEVE REJECT.
For detailed description of the Hold and Retrieve functions see 3GPP TS 24.083.
2.2.3 Common Information Element Category
The Common Information Element Category uses operations defined in 3GPP TS 24.080 [27] for supplementary
services signalling. Procedures are initiated by sending an operation including an invoke component. The invoke
component may yield a Return Error, Return Result or Reject component (also included in an operation) depending on
the outcome of the procedure.
The operation state machines, and procedures for management of Invoke IDs specified in CCITT Recommendation
Q.774 White Book are used.
A REGISTER message, a FACILITY message or certain existing 3GPP TS 24.008 [48] Call Control message is used to
carry the Facility information element which includes these operations. These operations request, acknowledge or reject
the desired supplementary service procedure.
2.2.4 Call related supplementary service procedures
2.2.4.1 Supplementary service procedures at call establishment or call clearing
For call related supplementary service procedures initiated at call establishment or call clearing, the messages for call
control specified in 3GPP TS 24.008 [48] are utilised to transport Facility information elements. This enables, for
example the originating mobile user to send a supplementary service invoke component within a SETUP message and
to receive from the network a Return result, Return error, or Reject component type within the Facility information
element in an ALERTING message, CONNECT message, or any other appropriate message.
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 11 ETSI TS 124 010 V19.1.0 (2026-03)
When a supplementary service invoke component is included within a SETUP message, the originating mobile station
shall encode the Facility information element identifier according to one of the three possible ways (see 3GPP
TS 24.008 [48]):
a) simple recall alignment;
b) advanced recall alignment;
c) recall alignment not essential.
Encoding of the Facility IEI within the SETUP message for different supplementary services is described in the
subclause 2.2.4.1.1.
The three different ways of encoding are required to support the network initiated mobile originating call establishment
(see subclause 2.2.4.1.2 and 3GPP TS 24.008 [48]).
2.2.4.1.1 Encoding of the Facility IEI for different supplementary services
The table 2.1 shows the encoding of the Facility IEI within the SETUP message for different supplementary services.
Table 2.1: Encoding of the Facility IE within the SETUP message
Service Facility IE Encoding
CUG simple recall alignment
UUS Advanced recall alignment
2.2.4.1.2 Supplementary service procedures at network initiated mobile originating call
establishment
The Facility and SS Version IE received in the set-up container of the CC_ESTABLISHMENT message shall be
handled according to the following rules:
The mobile station shall examine the IEI of the Facility IE.
If the Facility IEI coding is "simple recall alignment", the mobile station shall copy the Facility IE and SS Version IE
from the set-up container to the SETUP message without verifying or modifying the contents of these information
elements.
If the Facility IEI is encoded as "advanced recall alignment", the mobile station shall examine the SS Version IE.
If the mobile station recognises the protocol defined by the SS Version IE, it shall attempt to decode the Facility IE. If
the decoding is successful, and the operation is supported by the mobile station, the mobile station shall copy this
Facility IE and SS Version IE to the SETUP message. The mobile station shall also store relevant supplementary
service information contained within the Facility IE so that any reply to this Facility IE sent by the network will be
properly understood and processed.
If the mobile station does not recognise the SS Version IE, or the decoding of the Facility IE is unsuccessful, then the
call is rejected as described in 3GPP TS 24.008 [48].
If the Facility IE is encoded as "recall alignment not essential", the mobile station shall examine the SS Version IE .
If the mobile station recognises the protocol defined by the SS Version IE, it shall attempt to decode the Facility IE.
If the decoding is successful, and the operation is supported by the mobile station, the mobile station shall copy this
Facility IE and SS Version IE into the SETUP message. The mobile station shall also store relevant supplementary
service information contained within the Facility IE so that any reply to this Facility IE sent by the network will be
properly understood and processed.
If the mobile station does not recognise the SS Version IE, or the decoding of the Facility IE is unsuccessful, then the
SS Version IE and Facility IE are discarded, and NOT copied into the SETUP message.
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 12 ETSI TS 124 010 V19.1.0 (2026-03)
NOTE: A mobile station may include a Facility IE without an associated SS Version IE. This would indicate that
the SS operation is encoded using Phase 1 protocols.
2.2.4.2 Supplementary service procedures during the call
For call related supplementary service procedures during the active state of a call, the FACILITY message is used for
the exchange of the Facility information elements.
Note that the FACILITY message can also be used for this purpose in all states after the SETUP message has been sent.
If the supplementary service procedure is related only to a single call, the FACILITY message will use the transaction
identifier and protocol discriminator of this call.
If the supplementary service procedure affects more then one call, the FACILITY message may use the transaction
identifier and protocol discriminator of one of these calls.
If a call related FACILITY message is sent using the transaction identifier of a call in progress, and this call is cleared
due to call related causes, then the transaction identifier may not be cleared simultaneously in all cases. Depending upon
the supplementary service invoked, one of the following will occur:
- the network or mobile user may retain both the connection and the transaction identifier association and may
send a response within a Facility information element in a FACILITY message prior to the initiation of the
normal call clearing procedures; or
- the network or mobile user may send a response with a Facility information element in the first clearing message
(i.e. DISCONNECT, RELEASE or RELEASE COMPLETE message).
2.2.4.3 Handling of protocol errors in call related SS procedures
Messages containing a Facility information element shall be checked for protocol errors before the contents of the
Facility IE is acted on. The checks shall be performed in the following order:
1) The message carrying the Facility IE shall be checked for protocol errors as specified in 3GPP TS 24.008 [48]. If
a protocol error is found then the procedures in 3GPP TS 24.008 [48] apply.
2) The contents of the Facility IE shall be checked for protocol errors as specified in subclause 2.2.8. If a protocol
error is found then the procedures in subclause 2.2.8 apply.
2.2.4.4 Handling of other errors in call related SS procedures
If the tests specified in subclause 2.2.4.3 have been passed without the detection of a protocol error, the receiver will
attempt to process the contents of the Facility Information Element. If errors occur during this processing (e.g. system
failure, or information in the Facility IE is incompatible with the requested operation) then the procedures specified in
the individual service specifications apply.
Examples of the behaviour that could occur in this case are:
- the network or MS clears the call and rejects the supplementary services request by means of a clearing message
which contains a Return Error component with the appropriate parameter in the Facility Information Element;
- the network and MS continue to process the call according to normal 3GPP TS 24.008 [48] call control
procedures. The supplementary services request is rejected by means of a FACILITY message or appropriate
call control message containing a Return Error component with the appropriate parameter in the Facility
Information Element;
- the network and MS continue to process the call according to the normal 3GPP TS 24.008 [48] call control
procedures. The supplementary services request is ignored.
ETSI
3GPP TS 24.010 version 19.1.0 Release 19 13 ETSI TS 124 010 V19.1.0 (2026-03)
2.2.5 Call independent supplementary service procedures
2.2.5.1 Introduction
For supplementary service procedures independent of any call, the initiating side must establish a MM-connection
between the network and the MS according to the rules given in 3GPP TS 24.007 [49] and 3GPP TS 24.008 [48]. The
call independent supplementary service procedures shall apply to both CS and PS domain for some specific services.
On PS domain, a PS-signalling connection shall be established between the network and the MS instead of a MM-
connection. Throughout this specification, the term MM-connection is used to denote a MM-connection for CS domain
or PS-signalling connection for PS domain, as appropriate. The MS or the network starts the transaction by transferring
a REGISTER message across the radio interface. This transaction is identified by the transaction identifier associated
with the REGISTER message, and the Invoke identifier present in the component part of the Facility information
element. Following the REGISTER message one or more FACILITY messages may be transmitted, all of them related
by the use of the same transaction identifier. If the transaction is no longer used, it shall be released by sending a
RELEASE COMPLETE message. This procedure is specified in detail in clause 3, and the text in clause 3 takes
precedence over this introduction.
To convey the supplementary service invocation, the Facility information element is used. The Facility information
element present either in the REGISTER message or a subsequent message identifies the supplementary service
involved and the type of component (i.e. Invoke, Return result, Return error or Reject component).
When the REGISTER or FACILITY message contains a Facility information element and the requested service is
available, a FACILITY message containing a Facility inf
...