|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Flexible Alerting (FA) using IP Multimedia (IM)
Core Network (CN) subsystem;
Protocol specification
(3GPP TS 24.239 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 24.239 version 15.0.0 Release 15 1 ETSI TS 124 239 V15.0.0 (2018-07)
Reference
RTS/TSGC-0124239vf00
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
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:
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 only prevailing document is the
print of the Portable Document Format (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
If you find errors in the present document, please send your comment to one of the following services:
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 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 24.239 version 15.0.0 Release 15 2 ETSI TS 124 239 V15.0.0 (2018-07)
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.
Foreword
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, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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 24.239 version 15.0.0 Release 15 3 ETSI TS 124 239 V15.0.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 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 Flexible Alerting (FA) . 7
4.1 Introduction . 7
4.2 Description . 7
4.2.1 General description . 7
4.3 Operational requirements . 7
4.3.1 Provision/withdrawal . 7
4.3.2 Requirements on the originating network side. 8
4.3.3 Requirements on the terminating network side . 8
4.4 Syntax requirements . 8
4.5 Signalling procedures . 9
4.5.1 General . 9
4.5.2 Activation/deactivation . 9
4.5.2.1 General . 9
4.5.2.2 Demand member activation of a subscriber's default FA group(s) . 9
4.5.2.3 Demand member activation of a specified FA group . 9
4.5.2.4 Demand member deactivation of a subscriber's default FA group(s). 9
4.5.2.5 Demand member deactivation of a specified FA group . 9
4.5.3 Registration/erasure . 10
4.5.4 Interrogation . 10
4.5.4.1 General . 10
4.5.4.2 Interrogation using Ut interface . 10
4.5.4.3 Interrogation using the SIP-based user configuration . 10
4.5.5 Invocation and operation . 10
4.5.5.1 Actions at the AS serving the originating UE . 10
4.5.5.2 Actions at the AS serving the pilot identity . 10
4.6 Interaction with other services . 11
4.6.1 Communication session Hold (HOLD). 11
4.6.2 Terminating Identification Presentation (TIP) . 11
4.6.3 Terminating Identification Restriction (TIR) . 11
4.6.4 Originating Identification Presentation (OIP) . 11
4.6.5 Originating Identification Restriction (OIR) . 11
4.6.6 Conference (CONF) . 11
4.6.7 Communication DIVersion services (CDIV) . 11
4.6.7.1 Communication Forwarding Unconditional (CFU) . 11
4.6.7.2 Communication Forwarding Busy (CFB) . 11
4.6.7.3 Communication Forwarding No Reply (CFNR) . 12
4.6.7.4 Communication Forwarding Not Reachable (CFNRc) . 12
4.6.7.5 Communication Deflection (CD) . 12
4.6.7.6 Communication Forwarding on Not Logged-In (CFNL) . 12
4.6.8 Message Waiting Indication (MWI) . 12
4.6.9 Communication Barring (CB). 13
4.6.10 Explicit Communication Transfer (ECT) . 13
4.6.11 Enhanced Calling Name (eCNAM) . 13
4.7 Parameter values (timers) . 13
4.8 Service configuration . 13
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 24.239 version 15.0.0 Release 15 4 ETSI TS 124 239 V15.0.0 (2018-07)
4.8.1 General . 13
4.8.2 Data semantics . 13
4.8.3 XML schema . 14
Annex A (informative): Signalling flows . 15
A.1 Scope of signalling flows . 15
A.2 Introduction . 15
A.3 FA model signalling flow . 15
A.3.1 Introduction . 15
A.3.2 FA when UE#1 and UE#2 have resources available and UE#3 does not have required resources
available . 15
Annex B (informative): Example of filter criteria . 22
Annex C (informative): Change history . 23
History . 24
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 24.239 version 15.0.0 Release 15 5 ETSI TS 124 239 V15.0.0 (2018-07)
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 24.239 version 15.0.0 Release 15 6 ETSI TS 124 239 V15.0.0 (2018-07)
1 Scope
The present document provides the protocol details for the Flexible Alerting supplementary service in the IP
Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.173 [2].
Flexible Alerting (FA) causes a call to a pilot identity to branch the call into several legs to alert several termination
addresses (group members) simultaneously. The first leg to be answered is connected to the calling party. The other call
legs are abandoned.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the FA supplementary service.
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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service
and supplementary services; Stage 1".
[3] 3GPP TS 23.002: "Network architecture".
[4] 3GPP TS 24.238: "Session Initiation Protocol (SIP) based user configuration; Stage 3".
[5] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[6] 3GPP TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
over the Ut interface for Manipulating Simulation Services".
[7] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and
message contents".
[8] 3GPP TS 24.196: "Technical Specification Group Core Network and Terminals; Enhanced Calling
Name".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following
apply. A term defined in the present document takes precedence over the definition of the same term, if any, in
3GPP TR 21.905 [1].
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 24.239 version 15.0.0 Release 15 7 ETSI TS 124 239 V15.0.0 (2018-07)
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
AS Application Server
CS Circuit Switched
CN Core Network
FA Flexible Alerting
IP Internet Protocol
IM IP Multimedia
MMTEL Multimedia Telephony
4 Flexible Alerting (FA)
4.1 Introduction
Flexible Alerting (FA) causes a call to a Pilot Identity to branch the call into several legs to alert several termination
addresses (group members) simultaneously. Additional calls may be delivered to the FA Pilot Identity at any time. The
first leg to be answered is connected to the calling party. The other call legs are abandoned.
The members of an FA group are described by a list of termination addresses.
4.2 Description
4.2.1 General description
FA may be used for either a single user or multiple users. The difference between the two is in determining when the
FA group is busy. In the single user case, the group is considered to be busy when one of the members is considered to
be busy. In the multiple user case, the group is considered to be busy when all of the accessible members are considered
to be busy. A member is considered to be busy when it cannot accept the presentation of another call.
The FA pilot identity may have features to manage incoming calls (e.g., Incoming Communications Barring). These
features should take precedence over the corresponding features of individual members as described in subclause 4.6.
If an FA pilot identity is an FA member Identity, the FA member loses his or her individual incoming call features. In
this case, the FA member's incoming call features are superseded by the incoming call features of the FA pilot identity.
If an FA pilot identity is not an FA member Identity, the features of the FA pilot identity may be changed only through
user or service provider configuration.
FA does not affect the ability of an FA member to originate calls. FA may affect the ability of an FA member to receive
calls.
If an FA member has only a single identity that is the same as the FA pilot identity, the FA member may not receive
calls except through the FA pilot identity.
If an FA member has an identity different than the FA pilot identity, the FA member may receive calls as an individual
as well as calls through the FA pilot identity. Such an FA member may use revertive calling (i.e., a call to itself) for
other purposes, such as retrieval of voice mail.
4.3 Operational requirements
4.3.1 Provision/withdrawal
The FA service may be provided after prior arrangement with the service provider. The establishment of the initial
constituency (membership) of the FA group, along with additions to or subtractions from the set of group members, is
performed by the service provider.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 24.239 version 15.0.0 Release 15 8 ETSI TS 124 239 V15.0.0 (2018-07)
The FA service may be withdrawn at the subscriber's request or for administrative reasons. Withdrawal of the FA
service means dissolution of the FA group and results in calls to the Pilot Identity being treated as calls to a vacant
identity. Withdrawal of the FA service is performed by the service provider.
As determined by service provider provisioning, the FA group may have the following subscription options, as
summarized in table 4.3.1-1.
Table 4.3.1-1: FA group subscription options
Subscription option values Values
Type - Single User. The FA group is considered to be busy
when any member of the group is considered to be
busy.
- Multiple Users. The FA group is considered to be
busy when all accessible members of the group are
considered to be busy.
As determined by service provider provisioning, the FA member may have the following subscription options, as
summarized in table 4.3.1-2.
Table 4.3.1-2: FA member subscription options
Subscription option values Values
Membership - Demand. An FA member is authorized to activate or
deactivate his or her membership in the FA group(s).
- Permanent. An FA member is always a member of
his or her registered FA group(s).
If an FA group is of type 'demand activation', any configured FA member is able to, by means of user configuration,
change their status in the FA group from 'active' to 'inactive' or from 'inactive' to 'active'. The FA member status options
are summarized in table 4.3.1-3.
Table 4.3.1-3: FA member status options
Subscription option values Values
Status - Active. An FA member is eligible to be alerted when
a call is placed to the Pilot Identity.
- Inactive. An FA member is not eligible to be alerted
when a call is placed to the Pilot Identity.
Available user configuration actions for FA are described in subclause 4.5.2.
For user configuration of FA, the SIP-based user configuration capability as described in 3GPP TS 24.238 [4] or the Ut
interface as described in 3GPP TS 24.623 [6] could be used. More detail is described in subclause 4.8.
Other possibilities for provisioning could be used too, like web based provisioning or pre-provisioning by the operator.
4.3.2 Requirements on the originating network side
There are no requirements on the originating network side for FA. FA is a terminating network side service.
4.3.3 Requirements on the terminating network side
The public user identity that represents the pilot identity of the FA group has an always-registered presence on the IM
CN subsystem. The pilot identity is associated with a typical IM CN subsystem user service profile.
4.4 Syntax requirements
There are no special SIP syntax requirements for the FA service. The FA service is invoked when an IM CN subsystem
session is terminated to the pilot identity of an FA group.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 24.239 version 15.0.0 Release 15 9 ETSI TS 124 239 V15.0.0 (2018-07)
4.5 Signalling procedures
4.5.1 General
For user configuration of the FA service by a member of the FA group, either the Ut interface or the SIP-based user
configuration capability (as specified by 3GPP TS 24.238 [4]) should be used.
The enhancements to the XML schema for use over the Ut interface are described in subclause 4.8.
NOTE: Other possibilities for user configuration, such as web-based provisioning, are outside the scope of the
present document.
4.5.2 Activation/deactivation
4.5.2.1 General
The FA service is activated at provisioning and deactivated at withdrawal.
For an FA group that is of type 'demand activation', activation or deactivation of membership is accomplished by means
of user configuration and may be achieved by using either:
- the Ut interface using XCAP as enabling protocol as described in 3GPP TS 24.623 [6]; or
- SIP based user configuration as described in 3GPP TS 24.238 [3];
NOTE: Other possibilities for user configuration, such as web-based provisioning or pre-provisioning by the
operator are outside the scope of the present document, but are not precluded.
The enhancements to the XML schema for use over the Ut interface are described in subclause 4.9.
4.5.2.2 Demand member activation of a subscriber's default FA group(s)
For an FA group that is of type 'demand activation', an FA member may activate his or her membership in the
subscriber's default FA group(s) by specifying the FA membership activation feature code:
An example of the code is: *FC
If the activation is accepted, the system shall indicate success with feature confirmation treatment.
4.5.2.3 Demand member activation of a specified FA group
For an FA group that is of type 'demand activation', an FA member may activate his or her membership in a particular
FA group by specifying the FA membership activation feature code and a specific FA pilot identity:
An example of the code is: *FC + FA pilot identity
If the activation is accepted, the system shall indicate success with feature confirmation treatment.
4.5.2.4 Demand member deactivation of a subscriber's default FA group(s)
For an FA group that is of type 'demand activation', an FA member may deactivate his or her membership in the
subscriber's default FA group(s) by specifying the FA membership deactivation feature code:
An example of the code is: *FC0
If the deactivation is accepted, the system shall indicate success with feature confirmation treatment.
4.5.2.5 Demand member deactivation of a specified FA group
For an FA group that is of type 'demand activation', an FA member may deactivate his or her membership in a particular
FA group by specifying the FA membership deactivation feature code and a specific FA pilot identity:
An example of the code is: *FC0 + FA pilot identity
If the deactivation is accepted, the system shall indicate success with feature confirmation treatment.
ETSI
---------------------- Page: 10 ----------------------
3GPP TS 24.239 version 15.0.0 Release 15 10 ETSI TS 124 239 V15.0.0 (2018-07)
4.5.3 Registration/erasure
Individual members of the FA group may be added or deleted at any time by the service provider.
4.5.4 Interrogation
4.5.4.1 General
For interrogation, the mechanisms described in subclause 4.5.1 should be used.
4.5.4.2 Interrogation using Ut interface
The enhancements to the XML schema for use over the Ut interface are described in subclause 4.9.
4.5.4.3 Interrogation using the SIP-based user configuration
For an FA group that is of type 'demand activation', an FA member may interrogate his or her membership status in the
subscriber's default FA group(s) by specifying the FA membership interrogation feature code:
An example of the code is: *FC1
For an FA group that is of type 'demand activation', an FA member may interrogate his or her membership status in a
particular FA group by specifying the FA membership interrogation feature code and a specific FA pilot identity:
An example of the code is: *FC1 + FA pilot identity
NOTE 1: The response to such interrogation is not specified for the FA service. AS interactions with the MRF over
the CR reference point or a solution based on IVR can be used as a possible interrogation response.
4.5.5 Invocation and operation
4.5.5.1 Actions at the AS serving the originating UE
There are no procedures at the originating AS relevant to the FA service.
4.5.5.2 Actions at the AS serving the pilot identity
Procedures specified in 3GPP TS 24.229 [5] for an AS acting as a routing B2BUA shall apply, with the additions
described in this subclause.
The AS shall support procedures of notification about registration status defined in subclause 5.
...