ETSI TS 124 606 V11.2.0 (2019-10)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Message Waiting Indication (MWI) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification (3GPP TS 24.606 version 11.2.0 Release 11)

RTS/TSGC-0124606vb20

General Information

• Status: Published
• Publication Date: 30-Sep-2019
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 12 - Completion
• Completion Date: 01-Oct-2019

Standards Content (Sample)

ETSI TS 124 606 V11.2.0 (2019-10)






TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Message Waiting Indication (MWI) using IP Multimedia (IM)
Core Network (CN) subsystem;
Protocol specification
(3GPP TS 24.606 version 11.2.0 Release 11)

---------------------- Page: 1 ----------------------
3GPP TS 24.606 version 11.2.0 Release 11 1 ETSI TS 124 606 V11.2.0 (2019-10)



Reference
RTS/TSGC-0124606vb20
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 TS 24.606 version 11.2.0 Release 11 2 ETSI TS 124 606 V11.2.0 (2019-10)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 24.606 version 11.2.0 Release 11 3 ETSI TS 124 606 V11.2.0 (2019-10)
Contents
Intellectual Property Rights . 2
Legal Notice . 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 Message Waiting Indication (MWI) . 8
4.1 Introduction . 8
4.2 Description . 8
4.2.1 General description . 8
4.3 Functional entities . 8
4.3.1 User Equipment (UE) . 8
4.3.2 Application Server (AS) . 8
4.4 Roles . 8
4.4.1 MWI Subscriber User Agent (MSUA) . 8
4.4.2 MWI Notifier User Agent (MNUA) . 8
4.4.3 Message Account (MA) . 9
4.4.3.0 General . 9
4.4.3.1 Identification of the message account for the message deposit . 9
4.4.3.2 Identification of the message account for the MWI subscription . 9
4.5 Operational requirements . 9
4.5.1 Provision/withdrawal . 9
4.5.2 Requirements on the originating network side. 9
4.5.3 Requirements in the network . 9
4.5.4 Requirements on the terminating network side . 9
4.6 Coding requirements . 9
4.7 Signalling requirements . 10
4.7.1 Activation/deactivation . 10
4.7.1A Registration/erasure . 10
4.7.1B Interrogation . 10
4.7.2 Invocation and operation . 10
4.7.2.1 Actions at the MSUA . 10
4.7.2.2 Void. 11
4.7.2.3 Void. 11
4.7.2.4 Void. 11
4.7.2.5 Actions at the MNUA . 11
4.7.2.6 Void. 11
4.7.2.7 Void. 11
4.7.2.8 Void. 11
4.7.2.9 Void. 11
4.8 Interaction with other IMS capabilities . 11
4.8.1 Void . 11
4.8.2 Void . 11
4.9 Interaction with other services . 11
4.9.1 Communication Hold (HOLD) . 11
4.9.2 Terminating Identification Presentation (TIP) . 11
4.9.3 Terminating Identification Restriction (TIR) . 11
4.9.4 Originating Identification Presentation (OIP) . 12
4.9.5 Originating Identification Restriction (OIR) . 12
4.9.6 CONFerence calling (CONF) . 12
4.9.7 Communication DIVersion services (CDIV) . 12
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 24.606 version 11.2.0 Release 11 4 ETSI TS 124 606 V11.2.0 (2019-10)
4.9.7.0 General . 12
4.9.7.1 Communication Forwarding Unconditional (CFU) . 12
4.9.7.2 Communication Forwarding Busy (CFB) . 12
4.9.7.3 Communication Forwarding No Reply (CFNR) . 12
4.9.7.4 Communication Forwarding on Not Logged-in (CFNL) . 12
4.9.7.5 Communication Deflection (CD) . 12
4.9.8 Malicious Call IDentification (MCID) . 12
4.9.9 Explicit Communication Transfer (ECT) . 13
4.10 Interactions with other networks . 13
4.10.1 Void . 13
4.10.2 Void . 13
4.10.3 Void . 13
4.11 Parameter values (timers) . 13
Annex A (informative): Example signalling flows of Message Waiting Indication (MWI)
service operation . 14
A.1 Scope of signalling flows . 14
A.1.1 Introduction . 14
A.1.1.1 General . 14
A.1.1.2 Key required to interpret signalling flows . 14
A.1.2 Signalling flows demonstrating how UE subscribes to message waiting indication event notification . 14
A.1.2.1 Introduction. 14
A.1.2.2 MWI Subscriber subscribing to the status of his message account, MWI AS is in the subscriber's
network . 15
A.1.2.3 Void . 20
A.1.3 Void . 20
A.1.4 Signalling flows demonstrating how a message is deposited into the subscribers message account . 20
A.1.4.1 Introduction. 20
A.1.4.2 Depositing a message into the subscriber's message account . 20
A.1.4.2.1 Successful message deposit into the subscriber's message account . 20
Annex B (informative): Example of a filter criteria . 25
Annex C (informative): Void . 26
Annex D (informative): Change history . 27
History . 28

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 24.606 version 11.2.0 Release 11 5 ETSI TS 124 606 V11.2.0 (2019-10)
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.606 version 11.2.0 Release 11 6 ETSI TS 124 606 V11.2.0 (2019-10)
1 Scope
The present document specifies the stage three Protocol Description of the Message Waiting Indication (MWI) service,
based on stage one and two of the ISDN MWI supplementary services. It provides the protocol details in the IP
Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and the Session
Description Protocol (SDP).
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to
support the MWI 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 TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service
and supplementary services; Stage 1".
[2] 3GPP TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[3] IETF RFC 3842: "A Message Summary and Message Waiting Indication Event Package for the
Session Initiation Protocol (SIP)".
[4] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification".
[5] IETF RFC 3458: "Message Context for Internet Mail".
[6] IETF RFC 3938: "Video-Message Message-Context".
[7] IETF RFC 2822: "Internet Message Format".
[8] IETF RFC 2156: "MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and
RFC 822/MIME".
[9] IETF RFC 3263: "Session Initiation Protocol (SIP): Locating SIP Servers".
[10] 3GPP TS 22.101: "Service aspects; Service principles".
[11] IETF RFC 3261: "SIP: Session Initiation Protocol".
[12] 3GPP TS 24.228 Release 5: "Signalling flows for the IP multimedia call control based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[13] 3GPP TS 23.003: "Numbering, addressing and identification".
[14] Void
[15] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network
subsystem (IMS); Stage 1".
[16] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging".
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 24.606 version 11.2.0 Release 11 7 ETSI TS 124 606 V11.2.0 (2019-10)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 22.173 [1], 3GPP TS 22.101
[10], 3GPP TS 22.228 [15], 3GPP TS 23.003 [13] and the following apply:
correspondent: person or entity that deposits messages in the subscriber's message account
NOTE: Correspondent and subscriber can be the same person or entity.
Message Account (MA): resource that retains multimedia messages (voice, video, fax, etc.) deposited by
correspondents for the subscriber
subscriber: person or entity that receives status information about deposited messages
supplementary service: modifies or supplements a basic Telecommunication service
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AS Application Server
CD Communication Deflection
CDIV Communication DIVersion
CFB Communication Forwarding Busy
CFNL Communication Forwarding on Not Logged-in
CFNR Communication Forwarding No Reply
CFU Communication Forwarding Unconditional
CONF CONFerence calling
CSCF Call Session Control Function
ECT Explicit Communication Transfer
HOLD Communication Hold
I-CSCF Interrogating - CSCF
IMS IP Multimedia Subsystem
IP Internet Protocol
ISDN Integrated Service Data Network
MA Message Account
MCID Malicious Call IDentification
MIME Multipurpose Internet Mail Extensions
MNUA MWI Notifier User Agent
MSUA MWI Subscriber User Agent
MWI Message Waiting Indication
OIP Originating Identification Presentation
OIR Originating Identification Restriction
P-CSCF Proxy - CSCF
PSI Public Service Identity
PSTN Public Switch Telephone Network
S-CSCF Serving - CSCF
SDP Session Description Protocol
SIP Session Initiation Protocol
TIP Terminating Identification Presentation
TIR Terminating Identification Restriction
UA User Agent
UE User Equipment
URI Universal Resource Identifier
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 24.606 version 11.2.0 Release 11 8 ETSI TS 124 606 V11.2.0 (2019-10)
4 Message Waiting Indication (MWI)
4.1 Introduction
The Message Waiting Indication (MWI) service enables the network, upon the request of a controlling user to indicate
to the receiving user, that there is at least one message waiting.
4.2 Description
4.2.1 General description
The MWI service enables the AS to indicate to the subscriber, that there is at least one message waiting.
The indication is delivered to the subscriber's UE after successful subscription to the Message Waiting Indication
service as described in the present document.
Other modes of MWI service invocation are not applicable.
NOTE: Having received this indication, the subscriber user can subsequently access the message account, to have
the deposited message delivered. The means by which the subscriber accesses and manages the message
account are outside the scope of the present document.
4.3 Functional entities
4.3.1 User Equipment (UE)
The UE shall implement the MWI Subscriber User Agent role as described in subclause 4.4.1.
4.3.2 Application Server (AS)
An AS shall implement the role of a MWI Notifier User Agent as described in subclause 4.4.2.
An AS implementing the role of MWI Notifier User Agent shall implement the role of the AS acting as terminating UA
as described in 3GPP TS 24.229 [2], subclause 5.7.2.
Additionally an AS may implement other roles for the receipt and storage of the messages for example Web Server,
Mail Transfer and Delivery Agent, Short Message Service centre, etc.
The definition of additional roles for an MWI AS is out of the scope for the current specification.
4.4 Roles
4.4.1 MWI Subscriber User Agent (MSUA)
A MSUA is an entity that is subscribed or requests information about status change of message account from an MWI
AS.
Actions performed by a MSUA as a part of the UE are described in subclause 4.7.2.1.
4.4.2 MWI Notifier User Agent (MNUA)
The MNUA is an entity that provides information about changes in message account status to the MSUA.
Actions performed by a MWI Notifier User Agent as a part of the AS are described in subclause 4.7.2.5.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 24.606 version 11.2.0 Release 11 9 ETSI TS 124 606 V11.2.0 (2019-10)
4.4.3 Message Account (MA)
4.4.3.0 General
The definition of the message account from the RFC 3842 [3] applies with following additions:
Message account retains multimedia messages (e.g. voice, video and fax) intended to a particular subscriber.
4.4.3.1 Identification of the message account for the message deposit
Since messages may be intended to the different public user identities that belong to the same subscriber, the message
account may be configured to retain messages for any of the subscriber's public user identities.
Configuration of a message account to retain messages for each public user identity, for a group of public user identities
or for all of public user identities that belong to the same subscriber is subject to the operator's policy.
4.4.3.2 Identification of the message account for the MWI subscription
For the identification of the message account by subscriptions to the MWI service any of a subscriber's public user
identities can be used (see examples in subclause A.1.1.2).
4.5 Operational requirements
4.5.1 Provision/withdrawal
The MWI service is provided after prior arrangement with the service provider. The MWI service shall be withdrawn at
the subscriber's request or for administrative reasons.
Any of the subscriber's public user identities can be used to access the MWI service, see annex B.
4.5.2 Requirements on the originating network side
No specific requirements are needed on the originating network side.
NOTE: Annex B includes an example of an iFC that can be used to invoke the MWI supplementary service.
4.5.3 Requirements in the network
No specific requirements are needed in the network.
4.5.4 Requirements on the terminating network side
No specific requirements are needed in the network.
4.6 Coding requirements
The application/simple-message-summary MIME type used to provide Message Summary and Message Waiting
Indication Information is defined in subclause 5 of RFC 3842 [3].
The coding of the message types in the message-context-class values is defined in the specifications listed in the
"reference" column of table 1.
ETSI

---------------------- Page: 10 ----------------------
3GPP TS 24.606 version 11.2.0 Release 11 10 ETSI TS 124 606 V11.2.0 (2019-10)
Table 1: Coding requirements
Value Reference
voice-message RFC 3458 [5]
video-message RFC 3938 [6]
fax-message RFC 3458 [5]
pager-message RFC 3458 [5]
multimedia-message RFC 3458 [5]
text-message RFC 3458 [5]
none RFC 3458 [5]

The coding of the additional information about deposited messages in the application/simple-message-summary MIME
body is defined in subclause 25 of RFC 3261 [11] for SIP extension-header (subclause 3.5 of RFC 3842 [3]) and follow
the rules defined in the specifications listed in the "reference" column of table 2.
Table 2: Additional information
Header Description Reference
To: Indicates the subscriber's public user identity used by correspondent subclause 3.6.3 of RFC 2822
to deposit a message. [7]
From: Indicates the correspondent's public user
...