|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
IP Multimedia Subsystem (IMS)
Customized Alerting Tones (CAT);
Protocol specification
(3GPP TS 24.182 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 24.182 version 15.0.0 Release 15 1 ETSI TS 124 182 V15.0.0 (2018-07)
Reference
RTS/TSGC-0124182vf00
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.182 version 15.0.0 Release 15 2 ETSI TS 124 182 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.182 version 15.0.0 Release 15 3 ETSI TS 124 182 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 . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Customized Alerting Tones (CAT) . 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.1.1 CAT provision/withdrawal . 7
4.3.1.2 Requirements on the originating network side . 8
4.3.1.3 Requirements on the terminating network side . 8
4.4 Syntax requirements . 8
4.5 Signalling procedures . 8
4.5.1 General . 8
4.5.2 Activation/deactivation . 8
4.5.3 Registration/erasure . 8
4.5.4 Interrogation . 8
4.5.5 Invocation and operation . 9
4.5.5.1 Actions at the originating UE . 9
4.5.5.1.1 General . 9
4.5.5.1.2 UE Actions for CAT copy . 9
4.5.5.1.3 UE Actions for CAT stop . 9
4.5.5.1.4 UE support of DTMF . 9
4.5.5.2 Actions at the AS serving the originating UE . 9
4.5.5.2.1 General . 9
4.5.5.2.2 AS Actions for forking model . 9
4.5.5.2.3 AS Actions for early session model . 11
4.5.5.2.3A AS Actions for CAT Reject . 12
4.5.5.2.4 AS Actions for CAT stop . 13
4.5.5.2.5 AS support of DTMF . 13
4.5.5.2.6 AS Actions for Gateway model . 13
4.5.5.3 Actions at the AS serving the terminating UE . 15
4.5.5.3.1 General . 15
4.5.5.3.2 AS actions for forking model . 15
4.5.5.3.3 AS Actions for early session model . 17
4.5.5.3.4 AS Actions for CAT copy . 18
4.5.5.3.5 AS Actions for CAT stop . 18
4.5.5.3.6 AS support of DTMF . 18
4.5.5.3.7 AS Actions for Gateway model . 19
4.6 Interaction with other services . 20
4.6.1 Communication session Hold (HOLD). 20
4.6.2 Termination Identification Presentation (TIP) . 21
4.6.3 Termination Identification Restriction (TIR) . 21
4.6.4 Originating Identification Presentation (OIP) . 21
4.6.5 Originating Identification Restriction (OIR) . 21
4.6.6 Conference (CONF) . 21
4.6.7 Communication DIVersion services (CDIV) . 21
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 24.182 version 15.0.0 Release 15 4 ETSI TS 124 182 V15.0.0 (2018-07)
4.6.7.1 General . 21
4.6.7.2 CFNR . 22
4.6.8 Message Waiting Indication (MWI) . 22
4.6.9 Communication Barring (CB). 22
4.6.10 Explicit Call Transfer (ECT) . 22
4.6.11 Communication Wait . 23
4.6.12 Completion of Communications to Busy Subscriber . 23
4.6.13 Customized Ringing Signal (CRS) . 23
4.7 Parameter values (timers) . 23
4.8 Service configuration . 23
Annex A (informative): Signalling flows . 24
A.1 Scope of signalling flows . 24
A.2 Void . 24
A.3 CAT forking model signalling flows . 24
A.3.1 Introduction . 24
A.3.2 CAT when UE#1 and UE#2 have resources available . 24
A.3.3 CAT when UE#1 does not have required resources available while UE#2 has resources available . 29
A.3.4 CAT when UE#1 has resources available while UE#2 does not have required resources available . 35
A.4 CAT early session model signalling flows . 40
A.4.1 Introduction . 40
A.4.2 CAT when UE#1 and UE#2 have resources available . 40
A.4.3 CAT when UE#1 does not have required resources available while UE#2 has resources available . 45
A.4.4 CAT when UE#1 has resources available while UE#2 does not have required resources available . 55
A.5 CAT Gateway model signalling flows . 61
A.5.1 Introduction . 61
A.5.2 CAT when UE#1 and UE#2 have resources available . 62
A.5.2A CAT using reINVITE request when UE#1 and UE#2 have resources available . 67
A.5.3 CAT when UE#1 does not have required resources available while UE#2 has resources available . 72
A.5.3A CAT using reINVITE request when UE#1 does not have required resources available while UE#2 has
resources available . 81
A.5.4 CAT when UE#1 has resources available while UE#2 does not have required resources available . 91
A.5.4A CAT using reINVITE request when UE#1 has resources available while UE#2 does not have required
resources available . 96
A.5.5 CAT diverting for CFNR using reINVITE request when UE#1, UE#2 and UE#3 have resources
available . 102
A.5.6 CAT diverting for CFU . 113
A.5.6.1 General . 113
A.5.6.2 Gateway model CAT diverting for CFU when UE#1, UE#2 and UE#3 have resources available . 114
A.5.7 CAT when both UE#1 and UE#2 do not have required resources available . 121
A.5.8 CAT with different media types during one SIP session when both UE#1 and UE#2 do not have
required resources available . 130
A.6 Interworking with CS domain . 139
A.6.1 Introduction . 139
A.6.2 CAT provided by the terminating CS domain . 139
A.6.3 CAT provided to the originating CS domain with the CAT forking model . 142
A.6.4 CAT provided to the originating CS domain with the CAT early session model. 146
Annex B (normative): SDP a=content attribute "g.3gpp.cat" value . 152
B.1 Introduction . 152
B.2 New value . 152
Annex C (informative): Change history . 153
History . 157
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 24.182 version 15.0.0 Release 15 5 ETSI TS 124 182 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.182 version 15.0.0 Release 15 6 ETSI TS 124 182 V15.0.0 (2018-07)
1 Scope
The present document provides the protocol details for the Customized Alerting Tones (CAT) service in the IP
Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.182 [2].
The CAT service is an operator specific service by which an operator enables the subscriber to customize the media
which is played to the calling party during alerting of the called party.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the CAT 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.182: "Customized Alerting Tones (CAT) Requirements; Stage 1".
[3] 3GPP TS 24.238: "Session Initiation Protocol (SIP) based user configuration; Stage 3".
[4] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[5] RFC 3262: "Reliability of Provisional Responses in the Session Initiation Protocol (SIP)".
[6] 3GPP TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
over the Ut interface for Manipulating Supplementary Services".
[7] RFC 3959: "The Early Session Disposition Type for the Session Initiation Protocol (SIP)".
[8] RFC 3960: "Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)".
[9] RFC 5009 (September 2007): "Private Header (P-Header) Extension to the Session Initiation
Protocol (SIP) for Authorization of Early Media".
[10] 3GPP TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification
Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol
specification".
[11] RFC 6086 (January 2011): "Session Initiation Protocol (SIP) INFO Method and Package
Framework".
[12] RFC 4796 (February 2007): "The Session Description Protocol (SDP) Content Attribute".
[13] RFC 3311: "The Session Initiation Protocol (SIP) UPDATE Method".
[14] 3GPP TS 24.628: "Common Basic Communication procedures; Protocol specification".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 24.182 version 15.0.0 Release 15 7 ETSI TS 124 182 V15.0.0 (2018-07)
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].
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].
B2BUA Back-to-Back User Agent
CAT Customized Alerting Tones
DTMF Dual Tone Multi Frequency
MRF Media Resource Function
4 Customized Alerting Tones (CAT)
4.1 Introduction
The CAT service is an operator specific service by which an operator enables the subscriber to customize the media
which is played to the calling party during alerting of the called party. The media can consist of favourable songs,
multi-media clips or other customized alerting tones. CAT service should not negatively affect the conversation
between calling and called parties.
4.2 Description
4.2.1 General description
The service user is able to subscribe to the CAT service, activate (or de-activate) the service, and update the settings,
e.g., to change by configuration the active CAT media. The media can consist of favourable songs, multimedia clips or
other customized alerting tones. The CAT subscriber is able to refine the CAT media selection behaviour with
configured rules, e.g. time, calling party's location, called party's location, the identity of the calling and called party.
The CAT service is able to select the appropriate CAT media according to the rules.
CAT is a terminating network service, but can also have an originating network functional component. That is, CAT
media can be selected on behalf of the called subscriber for playback to the calling party, but the calling (IMS)
subscriber can also subscribe to and activate the CAT service. In such a case, the CAT media selected by the calling
party takes precedence for playback purposes over that selected by the called party. Whether or not the calling party’s
CAT media has precedence over the called party's selected CAT media is a matter of configuration in the calling party’s
(originating) network.
The start of playback of the selected CAT media toward the calling party occurs some time following the initiation of a
session, but prior to session answer. When the called party answers, playback of the CAT media either stops or
continues to play during the conversation, depending on operator or user preferences. When the CAT media is playing,
the calling party is able to stop (e.g. mute) it.
4.3 Operational requirements
4.3.1 Provision/withdrawal
4.3.1.1 CAT provision/withdrawal
The CAT service may be provided after prior arrangement with the service provider.
The CAT service may be withdrawn at the subscriber’s request or for administrative reasons.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 24.182 version 15.0.0 Release 15 8 ETSI TS 124 182 V15.0.0 (2018-07)
4.3.1.2 Requirements on the originating network side
The originating network side may support the "early-session" extension as described in RFC 3959 [7].
NOTE 1: the CAT service implementing the early-session model needs the early-session extension to be supported
by intermediate entities and the originating UE, else CAT media can not be provided to the caller.
The CAT service implementing the forking model and gateway model add no additional requirements on the originating
network side.
For the early session model, if the CAT service is provided by the originating network, the CAT AS shall control an
MRF as described in 3GPP TS 24.229 [4] that is acting on behalf of a calling subscriber who has activated CAT.
NOTE 2: The interworking between different models for CAT service is out of scope of this specification.
4.3.1.3 Requirements on the terminating network side
For the early session model, if the CAT service is provided by the terminating network, the CAT AS shall control an
MRF as described in 3GPP TS 24.229 [4] that is acting on behalf of a called subscriber who has activated CAT.
NOTE: The interworking between different models for CAT service is out of scope of this specification.
4.4 Syntax requirements
There are no special SIP syntax requirements for the CAT service.
4.5 Signalling procedures
4.5.1 General
Configuration of supplementary services by the user should:
- take place over the Ut interface using XCAP as enabling protocol as described in 3GPP TS 24.623 [6]; or
- use 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 deta
...