1、 ETSI TR 122 940 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) messaging (3GPP TR 22.940 version 15.0.0 Release 15) TECHNICAL REPORT ETSI ETSI TR 122 940 V15.0.0 (2018-07)13GPP TR 2
2、2.940 version 15.0.0 Release 15Reference RTR/TSGS-0122940vf00 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 enregistre la Sous-Prfecture de Gr
3、asse (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 w
4、ithout 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 o
5、f 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 you
6、r 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 E
7、TSI. 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. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the
8、 benefit of its Members. 3GPPTM and LTETMare 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. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TR 122
9、 940 V15.0.0 (2018-07)23GPP TR 22.940 version 15.0.0 Release 15Intellectual 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 m
10、embers 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.e
11、tsi.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
12、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 tradem
13、ark 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 Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The p
14、resent 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
15、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). “mus
16、t“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 122 940 V15.0.0 (2018-07)33GPP TR 22.940 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 Refe
17、rences 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Messaging services . 7g34.1 Background 7g34.2 SMS 7g34.3 MMS 7g34.4 Instant Messaging . 8g34.5 Chat 8g34.6 Email 8g34.7 Messaging in the IMS . 9g35 Current messaging standardisation summary . 9g35.1 C
18、PIM and SIMPLE work in IETF 9g35.2 Wireless Village and OMA messaging work . 10g35.3 3GPP work on existing messaging standards . 10g36 IMS Messaging 11g36.1 Messaging types . 11g36.2 Use Cases . 11g36.2.1 Instant Messaging with immediate delivery . 11g36.2.2 Instant Messaging With “Delivery at a lat
19、er date“ 11g36.2.3 Sending a document during an instant message exchange. . 12g36.2.4 Delivery of documents at a later date 12g36.2.5 Message Filtering 12g36.2.6 Chat Room 12g36.2.7 Sending a document during a chat room session 13g36.2.8 Location and Presence Enhanced Messaging . 13g36.2.9 IMS Messa
20、ging Selects Appropriate Delivery Methods . 13g36.2.10 IMS Messaging Service Provides Added Value to Messages Through Network Based Services 14g36.2.11 IMS Messaging Support for Value Added Service Providers . 14g36.3 Interaction with other Features . 14g36.3.1 MMS. 14g36.3.2 IMS Group Management 14
21、g36.3.3 Presence 14g36.4 Messaging Interoperability . 15g37 Deferred delivery messaging requirements 16g38 Open Issues 16g39 Conclusions and Recommendation 16g3Annex A (informative): Architecture considerations 17g3A.1 Introduction 17g3A.2 SMS 17g3A.3 MMS. 17g3ETSI ETSI TR 122 940 V15.0.0 (2018-07)4
22、3GPP TR 22.940 version 15.0.0 Release 15A.4 Instant Messaging . 17g3A.5 Chat 18g3A.6 Email 18g3Annex B (informative): Change history . 19g3History 20g3ETSI ETSI TR 122 940 V15.0.0 (2018-07)53GPP TR 22.940 version 15.0.0 Release 15Foreword This Technical Report has been produced by the 3rdGeneration
23、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
24、 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 enhan
25、cements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction This Technical Report identifies the issues and needs surrounding messaging solutions related to the 3GPP IP Multimedia Subsystem (IMS). The report is
26、 designed to identify essential messaging requirements, taking into consideration use cases that illustrate the needs of both service providers and users. The report also highlights and contrasts the messaging capabilities of the 3GPP Multimedia Messaging Service and how these messaging capabilities
27、 might relate to or interact with the messaging services running in IMS. An evaluation of various messaging solutions and technologies is provided together with an analysis on how they relate to the identified requirements. Finally, conclusions are drawn on the possible actions 3GPP may wish to take
28、 in regards to potential future work. To encourage rapid end-user adoption and to protect existing operator investments, IMS Messaging is an evolution and enhancement of the current 3GPP multimedia messaging user experience. IMS messaging mechanisms should re-use industry wide specifications as far
29、as possible and propose extensions as necessary. It is a goal of IMS Messaging to leverage the popularity of existing messaging services by supporting end-user friendly interfaces and features, flexible service offerings and to adopt and support existing pre and post-paid billing models. ETSI ETSI T
30、R 122 940 V15.0.0 (2018-07)63GPP TR 22.940 version 15.0.0 Release 151 Scope The objective of this Technical Report is to: a) Describe use cases that illustrate the service requirements for IMS messaging. b) Derive the broad 3GPP requirements for IMS messaging services. c) Investigate the possible re
31、quirements for interworking with networks outside the 3GPP domain d) Develop an analysis of the possible interaction between IMS messaging services and existing 3GPP messaging services (SMS, EMS and MMS) as well as other relevant 3GPP services such as presence IMS group management and so on. e) Iden
32、tify possible routes to standardization by: 1) Adopting existing and emerging standards, e.g. OMA, IETF. 2) Modifying and enhancing existing and emerging standards. 3) Developing of new standards. 2 References The following documents contain provisions which, through reference in this text, constitu
33、te 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 ref
34、erence 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. (up to and includingyyyy-mm|Vonwards): “. 1 3GPP TS 22.141: 3rdGeneration Partnership Project; Technical Specification
35、Group Services and Systems Aspects; Presence Service, Stage 1 2 IETF RFC 2779: “Instant Messaging / Presence Protocol Requirements“ 3 IETF RFC 2778: “A Model for Presence and Instant Messaging“ 4 IETF RFC 3261: “SIP: Session Initiation Protocol“ 5 draft-ietf-sip-message-07.txt: “Session Initiation P
36、rotocol Extension for Instant Messaging“ September 2002. Editors note: The above document cannot be formally referenced until it is published as an RFC. 6 3GPP TS 22.140: 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Stage 1, Multimedia messaging servi
37、ce 7 3GPP TS 22.250: 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Stage 1, IMS Group Management ETSI ETSI TR 122 940 V15.0.0 (2018-07)73GPP TR 22.940 version 15.0.0 Release 153 Definitions, symbols and abbreviations 3.1 Definitions (void) 3.2 Abbrevia
38、tions CPIM IP Internet Protocol IMS IP Multimedia Subsystem MMS Multimedia Messaging Service OMA Open Mobile Allicance SIMPLE SIP for Instant Messaging and Presence Leveraged Extensions SIP Session Initiation Protocol SMS Short Message Service 4 Messaging services 4.1 Background In todays world ther
39、e are many different types of messaging services available both in the wired and wireless worlds. Some services are supported in both, others are only found in one. For example, SMS has been designed for a wireless environment, whereas Instant Messaging has been designed for a wired environment. The
40、 expectations of these services also differ in that some services are designed to be used in what is perceived as real time and others are designed as a mailbox service where the message is stored ready for collection or delivery at a later date. This section investigates current messaging services
41、and examines the expectations and differences between them. In summary this section highlights the important fact that services where the message is delivery in what is perceived as real time by the user, are currently only being offered within the wired world, whereas all standardized services with
42、in the wireless world can be classed as non-real time. Introducing what is perceived as real time services into the wireless world brings many challenges not currently experienced in the wired environment. For example bandwidth, limited footprint/memory in the terminal, charging and billing. It is t
43、herefore important to consider the issues and impacts that surround these types of services when deploying in a wireless world. The messaging services covered in this section are as follows: 4.2 SMS The SMS messaging service allows a message to be created on a mobile device irrespective of whether t
44、he device is connected to a network or not. Once connected to an appropriate network, the user can send the message to the originators home SMSC, where it is stored until it is possible for the SMSC to deliver the message to the recipient. (please note that it is technically possible to send the mes
45、sage to any SMSC). Because of the short delivery times sometimes experienced by users of the SMS service, it could be perceived as being a real time service. However, real time delivery cannot be guaranteed due to the fact that there is no communications association between the originator and the re
46、cipient, only the originator and the SMSC, and therefore the SMS service should not be considered as a real time service. 4.3 MMS SMS has been very successful messaging service within in the second-generation GSM system. In the third generation mobile system it is envisaged that the Multimedia Messa
47、ging Service, MMS, shall succeed this easy to use, non real-time text transmission service. The MMS will allow users to send and receive messages exploiting the whole array of ETSI ETSI TR 122 940 V15.0.0 (2018-07)83GPP TR 22.940 version 15.0.0 Release 15media types available today e.g. text, images
48、, audio, video, while also making it possible to support new content types as they become popular. As with SMS, the MMS message is created using the application on the device. Again, the device does not have to be connected to a network in order to create a message. Once connected to the network the
49、 message can be sent from the device to the originators MMS server, again similar to the SMS implementation. This can be classed as the originating process. However, the MMS delivery process differs to that of the SMS in that instead of sending the message directly to the recipient, the MMS server forwards the message to the recipients MMS mailbox. Depending on the architecture, the recipient may be notified that a new MMS message has arrived in their inbox from which the recipient can then connect to their mailbox to retrieve the
