Tech-invite3GPPspaceIETF RFCsSIP

Content for  TR 22.940  Word version:  16.0.0

Top   Top   None   None   Next
1…   4…


0  IntroductionWord‑p. 5

This Technical Report identifies the issues and needs surrounding messaging solutions related to the 3GPP IP Multimedia Subsystem (IMS).
The report is 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 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 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 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.

1  ScopeWord‑p. 6

The objective of this Technical Report is to:
  1. Describe use cases that illustrate the service requirements for IMS messaging.
  2. Derive the broad 3GPP requirements for IMS messaging services.
  3. Investigate the possible requirements for interworking with networks outside the 3GPP domain
  4. 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.
  5. Identify 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, 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.
TS 22.141: 3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Presence Service, Stage 1
RFC 2779:  "Instant Messaging / Presence Protocol Requirements"
RFC 2778:  "A Model for Presence and Instant Messaging"
RFC 3261:  "SIP: Session Initiation Protocol"
draft-ietf-sip-message-07.txt:  "Session Initiation Protocol Extension for Instant Messaging" September 2002.
TS 22.140: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Stage 1, Multimedia messaging service
TS 22.250: 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Stage 1, IMS Group Management

3  Definitions, symbols and abbreviationsWord‑p. 7

3.1  Definitions


3.2  Abbreviations

Internet Protocol
IP Multimedia Subsystem
Multimedia Messaging Service
Open Mobile Allicance
SIP for Instant Messaging and Presence Leveraged Extensions
Session Initiation Protocol
Short Message Service

Up   Top   ToC