ETSI TR 122 982 V15.0.0 (2019-07)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Study of Customised Alerting Tone (CAT) requirements (3GPP TR 22.982 version 15.0.0 Release 15)

RTR/TSGS-0122982vf00

General Information

• Status: Published
• Publication Date: 22-Jul-2019
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 23-Jul-2019

Standards Content (Sample)

ETSI TR 122 982 V15.0.0 (2019-07)






TECHNICAL REPORT
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Study of Customised Alerting Tone (CAT) requirements
(3GPP TR 22.982 version 15.0.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 1 ETSI TR 122 982 V15.0.0 (2019-07)



Reference
RTR/TSGS-0122982vf00
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 - 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 2019.
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 TR 22.982 version 15.0.0 Release 15 2 ETSI TR 122 982 V15.0.0 (2019-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.
Legal Notice
This Technical Report (TR) 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 "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 TR 22.982 version 15.0.0 Release 15 3 ETSI TR 122 982 V15.0.0 (2019-07)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 4
1 Scope . 5
2 References . 5
3 Definitions, symbols and abbreviations . 5
3.1 Definitions . 5
3.2 Abbreviations . 6
4 Suggested CAT service requirements . 6
4.1 Basic functionality of the CAT service . 6
4.2 Normal procedures with successful outcome . 7
4.2.1 Provisioning and Withdrawal . 7
4.2.2 Activation and Deactivation and Update . 7
4.2.2.1 General . 7
4.2.2.2 Activation . 7
4.2.2.3 Deactivation . 7
4.2.3 Basic scenarios . 7
4.2.4 Interaction with Supplementary Services . 8
4.3 CAT service configuration . 9
4.4 Personal CAT Library . 10
4.5 CAT Expiry Notify . 10
4.6 The content of CAT . 10
4.7 Inter-working CAT . 10
4.8 CAT Charging . 10
4.8.1 General . 10
4.8.2 Advertising CATs . 11
4.9 CAT Security . 11
4.10 Interaction with User Profile . 11
4.10.1 CAT User Profile Provisioning . 11
4.10.2 Contents of User Profile relevant to CAT . 12
5 Architectural considerations on the CAT service . 13
5.1 CS Video telephony CAT . 13
5.2 IMS Multimedia CAT . 14
5.3 Interaction with IMS services and -entities . 14
5.3.1 Interaction with Multimedia Telephony Service . 14
5.3.2 Interaction with Multimedia Resource Function. 14
5.4 Considerations on applicability of CAT in IMS . 14
5.4.1 Consideration on QoS . 14
5.4.2 Consideration on VAD . 14
5.5 Considerations on requirement of Inter-working . 15
5.5.1 CS-CS Inter-working scenario . 15
5.5.2 CS-IMS interworking scenario . 15
5.5.2.1 General . 15
5.5.2.2 Scenario with IMS-based subscribers . 16
5.5.2.3 Scenario with Inter-working between CS and IMS subscribers . 16
Annex A (informative): Change history . 18
History . 19

ETSI

---------------------- Page: 4 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 4 ETSI TR 122 982 V15.0.0 (2019-07)
Foreword
rd
This Technical Report 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: 5 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 5 ETSI TR 122 982 V15.0.0 (2019-07)
1 Scope
The objective of this study item is to study requirements and potential new capabilities in 3GPP that need to be
standardized for the CAT service, especially additional features for roaming and interoperability support.
The present document specifies the requirements and technical implements for Customized Alerting Tone (CAT)
service in CS domain and the developments in PS domain.
Basically this TR is considering voice services, though interaction with MITe [2] services will be studied. Also Multi-
media CAT will be taken into consideration, so the CAT user may experience favourable songs, multi-media clips or
other customized alerting tones.
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 22.240: "Service requirements for 3GPP Generic User Profile (GUP); Stage 1".
3 Definitions, symbols 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.
Alerting Tone: An indication that is played to the calling subscriber during establishment of a call or during an
established call session indicating one of the following:
- that the called subscriber is being alerted.
- the progress of communication request (Call Forward, Call Wait etc.)
- any alerting event during a call session
Customized Alerting Tone: An Alerting Tone that is customized by the called subscriber or the calling subscriber.
A Customized Alerting Tone (CAT) may e.g. be a piece of recorded or composed music, greeting words , voice,
advertisement or video.
Customized Alerting Tone Service: A Customized Alerting Tone Service (CAT service) is an operator specific
service by which an operator enables the subscriber to customize his alerting tone.
CAT Inter-action: is the interaction of the CAT service with other services, e.g. Multiple Services Inter-
actioninteraction with Call Forwarding.
ETSI

---------------------- Page: 6 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 6 ETSI TR 122 982 V15.0.0 (2019-07)
CAT Inter-working : Multiple Domains Inter-workingis the interworking of a CAT service over different domains or
subsystems (CS or IMS) as well as between PLMNs.
CAT content provider: A service provider that provides a set of Alerting Tones for use as CAT for subscribers of
the CAT service. A 3GPP operator may be a CAT content provider.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 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
TR 21.905 [1].
CAT Customized Alerting Tone
4 Suggested CAT service requirements
4.1 Basic functionality of the CAT service
The Customized Alerting Tone Service (CAT service) is an operator specific service by which an operator enables the
subscriber to customize the alerting tone which is played to the calling party. CAT service should not negatively affect
the conversation between calling and called parties.
The CAT service should at least be able to fulfil the following requirements:
- The service user can easily subscribe the CAT service, activate the CAT service, and update the settings, e.g. to
change his active CAT.
- The calling party can experience the CAT set by the called party.
- The calling party can experience the CAT set by the calling party.
- The calling party’s operator should be able to configure which CAT should have priority, the one set by the
called or calling party. The calling party’s operator shall be able to take into account the calling party’s
preferences.
- The CAT shall override the default alerting tone towards the calling subscriber.
- Each CAT subscriber has a personal CAT library to store all his CATs. The CAT can be chosen from the CAT
library according to rules such as time, calling party’s location, called party’s location, the identity of the calling
and called party.
- It shall be possible to inform the user about changes in his CAT service, e.g. close expiry date for the CAT
service or a particular CAT content.
- The user whose CAT service is active will be charged according to a specified charging mode.
- When the called party answers the call, the call channel is set up and the CAT stops. Alternatively, as an operator
option the content of the CAT may continue to play during the conversation.
- When the called party is notified about an incoming call, the called party can send an indication to the CAT
service which CAT to play to the calling party.
- When the CAT is playing, the calling party can stop it for instance by pressing a specific button, then he shall
experience the default alerting tone.
- When the CAT is playing, the called party can stop it for instance by pressing a specific button, the calling party
shall experience another CAT.
- It shall be possible for a CAT subscriber to select a CAT, which content is provided by a CAT content provider,
which does not have to be the service provider.
ETSI

---------------------- Page: 7 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 7 ETSI TR 122 982 V15.0.0 (2019-07)
Note: the CAT implementation for PLMN based Networks may have a number of issues (CAT unidirectional
channel, charging for Early Media, negotiation of early H.324M during the alerting phase, etc.) that should be a
subject for Stage 2 standardization
4.2 Normal procedures with successful outcome
4.2.1 Provisioning and Withdrawal
The CAT Service can be provisioned and withdrawn by the operator per subscriber. Procedures for provisioning and
withdrawal are out of scope of standardisation
4.2.2 Activation and Deactivation and Update
4.2.2.1 General
The service subscriber can activate, de-activate his CAT service. For activation and de-activation, the service subscriber
may e.g. employ operator specific USSD commands, SMS, IVR or other means (e.g. customer self-administration via a
web-site).
4.2.2.2 Activation
When a subscriber activates his CAT Service he needs to specify, which CAT a calling user should experience.
After a subscriber has activated his CAT Service a calling user should experience the CAT, that was chosen by the
subscriber.
4.2.2.3 Deactivation
After a subscriber has deactivated his CAT Service a calling user should experience the default alerting tone.
4.2.3 Basic scenarios
In the following scenarios, contained in table 1, it is assumed that the called party (B) has activated his CAT Service.
Calling party (A) is calling B. The calling party has not subscribed and/or activated the CAT service.
The Customized Alerting Tone of B is CAT-B.

Table 1: Normal Operation Scenarios
Called party B
Forwarded-to-party Expected behaviour
(condition)
4 B, ringing A experiences CAT-B
5 B, busy A experiences busy indication.
First A experiences CAT-B and then the ‘no
6 B, no answer answer’ indication after B’s ‘no answer’ timer
has expired
7 B, not reachable A experiences ‘not reachable’ indication

In the following scenarios, contained in table 2, it is assumed that only the calling party (A) has activated his CAT
Service. Calling party (A) is calling B. The called party has not subscribed and/or activated the CAT service.
The Customized Alerting Tone of A is CAT-A,
ETSI

---------------------- Page: 8 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 8 ETSI TR 122 982 V15.0.0 (2019-07)

Table 2: Normal Operation Scenarios
Called party B
Forwarded-to-party Expected behaviour
(condition)
Depending on A settings, subscriber A will
4 B, ringing experience either CAT-A or the default
alerting tone.
Depending on A settings, subscriber A will
5 B, busy experience either CAT-A or the default busy
tone.
Depending on A settings, subscriber A will
experience either CAT-A or the default
6 B, no answer alerting tone and then the ‘no answer’
indication after B’s ‘no answer’ timer has
expired
7 B, not reachable A experiences ‘not reachable’ indication

In the following scenarios, contained in table 3, it is assumed that both the calling party (A) and called party (B) have
activated the CAT Service. Calling party (A) is calling B.
The Customized Alerting Tone of B is CAT-B, the Customized Alerting Tone for A is CAT-A.

Table 3: Normal Operation Scenarios
Called party B
Forwarded-to-party Expected behaviour
(condition)
Depending on A settings, A experiences
4 B, ringing
CAT-A, CAT-B or the default alerting tone.
Depending on A settings, subscriber A will
5 B, busy experience either CAT-A or the default busy
tone.
Depending on A settings, subscriber A will
experience either CAT-A, CAT-B or the
6 B, no answer default alerting tone and then the ‘no
answer’ indication after B’s ‘no answer’ timer
has expired
7 B, not reachable A experiences ‘not reachable’ indication

4.2.4 Interaction with Supplementary Services
Additionally, for call-forwarding scenarios, it is assumed that Forwarded-to-party (C) has activated his CAT Service.
The Customized Alerting Tone of C is called CAT-C. The Customized Alerting Tone of D is called CAT-D. The calling
party has not subscribed and/or activated the CAT service. If applicable, the CAT experienced by the calling user
should be the one customized for the user by the connected-to-party
In the following table, all the CATs that A experiences in the column "Expected behaviour" may be replaced by CAT-
B, if the operator wants to deploy so.
ETSI

---------------------- Page: 9 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 9 ETSI TR 122 982 V15.0.0 (2019-07)
Table 1: Supplementary Service Interaction Scenarios
Called party B Forwarded-to-party
Expected behaviour
(condition) (condition)
B has activated call
Depending on A settings, subscriber A will
waiting and B is
8
experience either CAT-B or the default call
engaged in an active or
waiting tone.
held call.
B has activated Call
Forwarding
9 Unconditional (CFU) to C, ringing A experiences CAT-C
C and A’s call is
forwarded to C
B has activated Call
Forwarding on Busy
10 (CFB) to C, B is busy C, ringing A experiences CAT-C
and A’s call is
forwarded to C
B has activated Call
Forwarding on No
A experiences CAT-B until B’s CFNRy timer
11 Reply (CFNRy) to C C, ringing
has expired. Then experiences CAT-C.
and A’s call is
forwarded to C
B has activated Call
Forwarding on Not
12 Reachable (CFNRc) to C, ringing A experiences CAT-C
C and A’s call is
forwarded to C
Tandem Forwarding:
B has activated a Call
Forwarding to C and C
C has activated a Call
13 has activated a Call A experiences CAT-D
Forwarding to D and
Forwarding to D so A’s
A’s call is forwarded to
call is forwarded to D
D

- As a configurable option it shall be possible to distinguish between different call states (from call status) and
provide the caller with different CAT
- It should be possible to configure each specific action (CAT) as a result of a sequence of specific rolls (Date,
Time, Call status etc.) for instance as an XML table
4.3 CAT service configuration
-  A service subscriber, that has activated his CAT service, shall be able to select and update his CAT settings - i.e.
select a different CAT than the current one. It should be possible to charge the subscriber for selection / update
of the CAT settings.
- The calling user should be able to ‘copy’ the last CAT that was experienced in the ongoing call, as his own CAT.
Note 1: DRM issues should be covered in order to make sure that copyrights are not infringed.
Note 2: One solution could for instance be to use DTMF signalling.
ETSI

---------------------- Page: 10 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 10 ETSI TR 122 982 V15.0.0 (2019-07)
4.4 Personal CAT Library
Each CAT subscriber has a personal CAT library to store his purchased CAT contents and/or his CAT settings. After a
CAT subscriber purchases a CAT content from else places, such as the system CAT library or other PLMN, the system
stores it in his personal CAT library automatically. Then the subscriber can set a CAT with the CAT contents in his
personal CAT library. The personal CAT library contains all the contents that the subscriber can use. The subscriber can
change the CAT contents in his personal CAT library. The system administrator may configure and query the maximum
number of CAT contents in a personal CAT library.
4.5 CAT Expiry Notify
Every CAT has its absolute expiry date (a specific date such as December 31, 2008), or relative expiry date (such as 30
days).
Considering that generally CAT content providers have strict requirements for the location and timeliness of CAT and
the copyright legality of CAT must be guaranteed, the copyright expiry date of an CAT must be provided in the CAT
management process. Upon expiry of this expiry date, the CAT will be invalid and the subscriber will be unable to
continue to use it. The CAT system (for example, the system-timing task) will periodically check the expiry dates of all
CAT. If an CAT is soon to reach its expiry date, the system will send a short message (or other ways) to the subscriber,
telling him that the CAT he is using will soon expire. When the expiry date is up, the system will change the status of
this CAT to the deleted or hidden status (depending on the system configuration).
4.6 The content of CAT
The content of CAT can be music, voice, text, or video.
The CAT may be composed of music, voice, text, video, which can be provided by the CAT content provider, operator
or by the user himself.
The content of the CAT service may be dynamically created, possibly taking into account information available in the
network, e.g. calling and/or called user’s location and/or presence information.
Charging information may be provided within a CAT in order to inform the caller about long distance call charging.
4.7 Inter-working CAT
It is important for a good user experience that CAT works as predicted independently if the called or the calling user is
roaming. A standardized CAT solution should therefore fulfil the following end user requirements:
- When calling a service subscriber of another network, the calling party can still experience the CAT set by the
called party.
- When the calling party is roaming to another network, the calling party can still experience the CAT set by the
called party.
- When the calling party is roaming to another network, the calling party should still be able to experience the
CAT set by the calling party.
- The calling party should experience the CAT set by the called party if the called party is roaming to another
network.
- When calling a service subscriber of another network, the calling party should be able to ‘copy’ the last CAT
that was experienced in the ongoing call, as his own CAT.
4.8 CAT Charging
4.8.1 General
Each CAT subscriber can be charged according to the different charging mode.
ETSI

---------------------- Page: 11 ----------------------
3GPP TR 22.982 version 15.0.0 Release 15 11 ETSI TR 122 982 V15.0.0 (2019-07)

Charging
Index Description
mode
Fixed (for example monthly) expense for the CAT service. In
Service monthly the first month the expense may be calculated according to
1
fee the number of days. This revenue is obtained by network
operators.
A subscriber is charged by the system when he purchases
Fee of CAT in any mode, inc
...