ETSI TS 124 247 V8.3.0 (2009-06)

Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.247 version 8.3.0 Release 8)

RTS/TSGC-0124247v830

General Information

• Status: Published
• Publication Date: 16-Jun-2009
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 12 - Completion
• Due Date: 22-Jun-2009
• Completion Date: 17-Jun-2009

Standards Content (Sample)

ETSI TS 124 247 V8.3.0 (2009-06)
Technical Specification

Digital cellular telecommunications system (Phase 2+);
Universal Mobile Telecommunications System (UMTS);
LTE;
Messaging service using the IP Multimedia (IM)
Core Network (CN) subsystem;
Stage 3
(3GPP TS 24.247 version 8.3.0 Release 8)

---------------------- Page: 1 ----------------------
3GPP TS 24.247 version 8.3.0 Release 8 1 ETSI TS 124 247 V8.3.0 (2009-06)



Reference
RTS/TSGC-0124247v830
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
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the 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
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2009.
All rights reserved.

TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 24.247 version 8.3.0 Release 8 2 ETSI TS 124 247 V8.3.0 (2009-06)
Intellectual Property Rights
IPRs essential or potentially essential to the present document 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 (http://webapp.etsi.org/IPR/home.asp).
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.
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
http://webapp.etsi.org/key/queryform.asp.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 24.247 version 8.3.0 Release 8 3 ETSI TS 124 247 V8.3.0 (2009-06)
Contents
Intellectual Property Rights.2
Foreword.2
Foreword.5
1 Scope.6
2 References.6
3 Definitions, symbols and abbreviations .7
3.1 Definitions.7
3.2 Abbreviations.7
4 Messaging overview.8
5 Protocol using SIP for page-mode messaging.8
5.1 Introduction.8
5.1.1 Sending immediate message to multiple recipients .8
5.2 Functional entities .9
5.2.1 User Equipment (UE) .9
5.2.2 Application Server (AS).9
5.2.3 Media Resource Function Controller (MRFC) .9
5.3 Role.9
5.3.1 Participant.9
5.3.1.1 General.9
5.3.1.2 Sending of an immediate message .9
5.3.1.3 Receiving an immediate message .9
5.3.1.4 Consent to list server distribution.10
5.3.2 Application Server (AS).10
5.3.2.1 Receiving an immediate message for unregistered Public User Identity .10
5.3.3 List Server.10
5.3.3.1 List server originating case .10
5.3.3.2 List server terminating case.10
5.3.3.3 List Server processing the MESSAGE URI-list.11
5.3.3.4 List server support of MESSAGE URI-lists .11
6 Protocol using SIP for session-mode messaging.11
6.1 Introduction.11
6.2 Functional entities .11
6.2.1 User Equipment (UE) .11
6.3 Role.12
6.3.1 Participant.12
6.3.1.1 General.12
6.3.1.2 Session initiation - mobile originating case .12
6.3.1.3 Session initiation - mobile terminating case.12
6.3.2 Intermediate Node.12
6.3.2.1 General.12
6.3.2.2 Generic procedures for all methods at the intermediate node .12
6.3.2.2.1 Intermediate node – originating case.12
6.3.2.2.2 Intermediate node – terminating case .12
6.3.2.3 Session Initiation.13
6.3.2.3.1 Session initiation – originating case .13
6.3.2.3.2 Session initiation – terminating case .13
7 Protocol using SIP for session-mode messaging conferences.13
7.1 Introduction.13
7.2 Functional entities .13
7.2.1 User Equipment (UE) .13
7.2.2 Media Resource Function Controller (MRFC) .13
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 24.247 version 8.3.0 Release 8 4 ETSI TS 124 247 V8.3.0 (2009-06)
7.2.3 Conferencing Application Server (AS).13
8 Protocol using SDP for session-mode messaging and session-mode messaging conferences.14
8.1 Introduction.14
8.2 Functional entities .14
8.2.1 User Equipment (UE) .14
8.2.2 Media Resource Function Controller (MRFC) .14
8.2.3 Application Server (AS).14
8.3 Role.14
8.3.1 SDP offerer.14
8.3.2 SDP answerer.15
8.3.3 Intermediate node.16
8.3.3.1 Intermediate node Originating case.16
8.3.3.1.1 Sending of a SDP offer.16
8.3.3.2 Intermediate node Terminating case .16
8.3.3.2.1 Sending of a SDP answer .16
9 Protocol using MSRP for session-mode messaging and session-mode messaging conferences.17
9.1 Introduction.17
9.2 Functional entities .17
9.2.1 User Equipment (UE) .17
9.2.1.1 General.17
9.2.2 Application Server (AS).17
9.2.3 Media Resource Function Processor (MRFP) .17
9.3 Role.18
9.3.1 MSRP sender.18
9.3.1.1 MSRP sender sends a message.18
9.3.2 MSRP receiver.18
9.3.3 Intermediate node.18
9.3.3.1 Intermediate node terminating case.18
9.3.3.2 Intermediate node originating case.19
10 Void.19
Annex A (informative): Example signalling flows of messaging service operation .20
A.1 Scope of signalling flows .20
A.2 Introduction.20
A.2.1 General.20
A.2.2 Key required to interpret signalling flows.20
A.3 Signalling flows demonstrating immediate messaging .20
A.4 Signalling flows demonstrating session-based messaging .20
A.4.1 Introduction.20
A.4.2 Establishing a session for session-based messaging without preconditions.21
A.4.3 Establishing a session for session-based messaging with Intermediate Nodes .35
A.4.4 Establishing a session for session-based messaging with preconditions .58
A.5 Flows demonstrating session-based messaging conferences .59
A.5.1 User connecting into a messaging conference.59
A.5.2 MRFC/AS invites a user to a messaging conference.68
Annex B (informative): Change history .78
History .81

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 24.247 version 8.3.0 Release 8 5 ETSI TS 124 247 V8.3.0 (2009-06)
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.247 version 8.3.0 Release 8 6 ETSI TS 124 247 V8.3.0 (2009-06)
1 Scope
The present document provides the protocol details for the messaging service within the IP Multimedia CN Subsystem
(IMS) based on the Session Initiation Protocol (SIP), the Session Description Protocol (SDP) and, the Message Session
Relay Protocol (MSRP) . The document covers immediate messaging, session based messaging and session-based
messaging conferences, as described in 3GPP TS 22.340.
Where possible the present document specifies the requirements for this protocol by reference to specifications
produced by the IETF within the scope of SIP, SDP and, MSRP, either directly, or as modified by 3GPP TS 24.229.
The present document is applicable to Application Servers (ASs) , Media Resource Function Controllers (MRFCs),
Media Resource Function Processors (MRFPs) and to User Equipment (UE) providing messaging capabilities.
This document does not cover the signalling between a MRFC and a MRFP.
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: "3G Vocabulary".
[2] 3GPP TS 22.228: " Service requirements for the Internet Protocol (IP) multimedia core network
subsystem; Stage 1".
[3] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IP Multimedia (IM) call model;
Stage 2".
[4] 3GPP TS 24.228 Release 5: "Signalling flows for the IP multimedia call control based on SIP and
SDP; Stage 3".
[5] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP; Stage 3".
[6] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[7] IETF RFC 3261 (March 2002): "SIP: Session Initiation Protocol".
[8] IETF RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for Instant
Messaging".
[9] IETF RFC 4975 (September 2007): "The Message Session Relay Protocol (MSRP)".
[10] 3GPP TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem;
Stage 3".
[11] 3GPP TS 22.340: "IP Multimedia System (IMS) messaging; Stage 1".
[12] IETF RFC 5365 (October 2008): "Multiple-Recipient MESSAGE Requests in the Session
Initiation Protocol (SIP)".
[13] IETF RFC 3994 (January 2005): "Indication of Message Composition for Instant Messaging".
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 24.247 version 8.3.0 Release 8 7 ETSI TS 124 247 V8.3.0 (2009-06)
[14] 3GPP TS 26.141 "IP Multimedia System (IMS) Messaging and Presence; Media formats and
codecs".
[15] draft-ietf-mmusic-file-transfer-mech-00.txt (December 2006):"A Session Description Protocol
(SDP) Offer/Answer Mechanism to Enable File Transfer".
Editor's note: The above document cannot be formally referenced until it is published as an RFC.
[16] IETF RFC 5360 (October 2008): " A Framework for Consent-Based Communications in the
Session Initiation Protocol (SIP)".
[17] 3GPP2 C.S0050-B: "3GPP2 File Formats for Multimedia Services".
[18] draft-ietf-simple-msrp-acm-00.txt (January 2009): "An Alternative Connection Model for the
Message Session Relay Protocol (MSRP)".
Editor's note: The above document cannot be formally referenced until it is published as an RFC.

3 Definitions, symbols and abbreviations
3.1 Definitions
IsComposing information This is a term used to indicate that an indication is sent to the communicating user when
a user in entering a new message.
For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.340 [11] apply:
Immediate messaging
Session based messaging
Session based messaging conferences
For the purposes of the present document, the [following] terms and definitions given in RFC 4975 [9] apply:
Host
Page-mode messaging
Session inactivity timer
Session-mode messaging
Session-mode messaging conferences
Visitor
For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.147 [10] apply:
Conferencing Application Server
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AS Application Server
CN Core Network
DM Data manipulator
DMS Data manipulation server
IM IP Multimedia
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 24.247 version 8.3.0 Release 8 8 ETSI TS 124 247 V8.3.0 (2009-06)
IMS IP Multimedia CN subsystem
IP Internet Protocol
MRFC Media Resource Function Controllers
MRFP Media Resource Function Processors
MSRP Message Session Relay Protocol
SBLP Service Based Local Policy
SDP Session Description Protocol
SIP Session Initiation Protocol
UE User Equipment
URL Uniform Resource Locator
4 Messaging overview
The basic services for the IP Multimedia core network Subsystem (IMS), as defined in 3GPP TS 24.229 [5], allow a
user to initiate, modify and terminate media sessions using the Session Initiation Protocol, as defined in RFC 3261 [7].
Although these basic mechanisms already allow the exchange of instant messaging information using SIP, this
functionality can be extended to provide a richer service within the IMS.
The messaging service within the IM CN subsystem provides the means for a user to send or receive single messages
immediately to / from another user and to create and participate in a messaging conference with one ore more other
users. Participants to such message based communication may be internal or external to the home network.
When to use an immediate message and when to use a session-based messaging session will depend on the application.
NOTE: Some participants may always use session-based messaging, while others may use immediate messaging
or a combination of session-based messaging and immediate messaging dependant of the characteristics
of the messaging session. The criteria are implementation and application specific.
For immediate messaging the procedures for page-mode messaging, as defined in RFC 3428 [8] or for session-mode
messaging, as defined in RFC 4975 [9] and draft-ietf-simple-msrp-acm [18] are utilized. When to use an page-mode
messaging and when to use session-mode messaging session for the purpose of immediate messaging will depend on
the application.
For session-based messaging and session-based messaging conferences, the Message Session Relay Protocol (MSRP) is
utilized to transport messages.
The architecture for the 3GPP messaging is specified in 3GPP TS 23.228 [6] and 3GPP TS 23.218 [3]. The 3GPP
recommended media formats and codecs are specified in 3GPP TS 26.141 [14]. The 3GPP2 recommended media
formats and codecs are specified in 3GPP2 C.S0050-B [17].
The functional split for session-mode messaging between an AS, MRFC and MRFP is that same as that described in
clause 4 in 3GPP TS 24.147 [10] for SIP based conferences. The functional split between the AS, MRFC and MRFP for
page-model messaging is out of scope of the present document.
5 Protocol using SIP for page-mode messaging
5.1 Introduction
5.1.1 Sending immediate message to multiple recipients
The UE may be able to send a single immediate message to multiple recipients by including in the MESSAGE request
the list of URIs (i.e., URI-list) that identify the intended recipients.
The UE shall create a MESSAGE request in accordance with 3GPP TS 24.229 [5], and it shall also include a multipart
body in the MESSAGE request. The Request-URI shall be set to the SIP URI of the Application Server that implements
the role of the List Server. The multipart body shall contain the body carrying the URI-list (in the XML format) whose
Content-Disposition type is 'recipient-list', and the body that contains the immediate message payload as specified in the
RFC 5365 [12].
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 24.247 version 8.3.0 Release 8 9 ETSI TS 124 247 V8.3.0 (2009-06)
The handling of the received response shall be in accordance with 3GPP TS 24.229 [5].
5.2 Functional entities
5.2.1 User Equipment (UE)
For the purpose of page-mode messaging, the UE shall implement the role of a Participant as described in
subclause 5.3.1.
5.2.2 Application Server (AS)
As the functional split for the purposes of page mode messaging between the AS and the MRFC is out of scope of the
present document, the procedures are described for a combined AS and MRFC. The AS and MRFC may either be
collocated, or interoperate using a proprietary protocol and a proprietary functional split.
For the purpose of page-mode messaging, an Application Server may implement the role of a List Server as described
in subclause 5.3.3. An Application Server may implement the role of a Participant as described in subclause 5.3.1
5.2.3 Media Resource Function Controller (MRFC)
As the function split for the purposes of page mode messaging between the MRFC and the AS is out of scope of the
present document, the procedures for the MRFC are described together with those for the AS in subclause 5.2.2.
5.3 Role
5.3.1 Participant
5.3.1.1 General
For the purpose of page-mode messaging a participant will send a page-mode message using a SIP MESSAGE request
as defined in RFC 3428 [8] to another participant.
5.3.1.2 Sending of an immediate message
When sending an page-mode message to another participant or to a list server, the participant shall construct and send a
MESSAGE request in accordance with RFC 342
...