Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 29.311  Word version:  16.0.0

Top   Top   None   None   Next
1…   6…

 

1  ScopeWord‑p. 7

The present document specifies the protocol details of service level interworking between Instant Message (OMA-TS-SIMPLE_IM [4]) or Chat Session (OMA-TS-CPM_Conv_Fnct [17]) using the 3GPP IP Multimedia CN subsystem and the Short Message Service over both legacy CS/PS network as specified in the TS 23.040 and a generic IP Conectivity Access Network (IP-CAN) as specified in the TS 24.341. These include:
  • Procedures to implement service level interworking between IM and SM;
  • Procedures to implement service level interworking between CPM and SM;
  • Enhancement of the IP-SM-GW as an Application Server to support service selection, authorization and mapping between IM or CPM and SM protocols; and
  • Interaction between service level interworking and transport layer interworking.
Up

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)".
[3]
TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[4]
OMA OMA-TS-SIMPLE_IM-V1_0: "Instant Messaging using SIMPLE", http://www.openmobilealliance.org/.
[5]
TS 24.341: "Support of SMS over IP networks; Stage 3".
[6]
TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2".
[7]
TS 29.002: "Mobile Application Part (MAP) specification".
[8]
RFC 3428:  "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[9]
TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
[10]
RFC 3261:  "SIP: Session Initiation Protocol".
[11]
TS 23.002: "Network architecture".
[12]
TS 23.228: "IP multimedia subsystem; Stage 2".
[13]
RFC 3841:  "Caller Preferences for the Session Initiation Protocol (SIP)".
[14]
TS 23.042: "Compression algorithm for text messaging services".
[15]
TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".
[16]
TS 26.141: "IP Multimedia System (IMS) Messaging and Presence; Media formats and codecs".
[17]
OMA OMA-TS-CPM_Conv_Fnct-V1_0: "CPM Conversation Functions", http://www.openmobilealliance.org/.
[18]
RFC 4575:  "A Session Initiation Protocol (SIP) Event Package for Conference State".
[19]
RFC 4975:  "The Message Session Relay Protocol (MSRP)".
[20]
OMA OMA-TS-CPM_System_Description-V1_0: "Converged IP Messaging System Description", http://www.openmobilealliance.org/.
[21]
TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[22]
TS 51.011: "Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface".
[23]
RFC 822:  "Standard for the Format of ARPA Internet Text Messages".
[24]
TS 23.038: "Alphabets and language-specific information".
Up

3  Definitions and abbreviations |R10|Word‑p. 8

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
For the purposes of the present document, the following terms and definitions given in TS 23.204, subclause 3.1 apply:
SMSIP MESSAGE
Instant Message
For the purposes of the present document, the following terms and definitions given in RFC 3261 apply.
Header
Header field
Request
Response
Status-Code (see RFC 3261 subclause 7.2)
For the purposes of the present document, the following terms and definitions given in TS 23.002, subclause 4.1.1.1 and TS 23.002, subclause 4a.7 apply:
Home Subscriber Server (HSS)
For the purposes of the present document, the following terms and definitions given in TS 23.040 apply:
WVG Object
For the purposes of the present document, the following terms and definitions given in TS 23.228, subclause 4.3.3.1, TS 23.228, subclause 4.3.6 and TS 23.228, subclause 4.6 apply:
Serving-CSCF (S-CSCF)
For the purposes of the present document, the following terms and definitions given in OMA-TS-CPM_Conv_Fnct [17] apply:
Participant Information
For the purposes of the present document, the following term and definition applies:
Chat Session:
A session established between two or more participants that is used for exchanging messages.
Up

3.2  AbbreviationsWord‑p. 9

For the purposes of the present document, the abbreviations given in TR 21.905 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.
AS
Application Server
CPIM
Common Profile for Instant Messaging
CPM
Converged IP Messaging
IM
Instant Message
IMDN
Instant Message Disposition Notification
IP-SM-GW
IP-Short-Message-Gateway
MSRP
Message Session Relay Protocol
SM
Short Message
UDH
User Data Header
WVG
Wireless Vector Graphics
Up

4  Overview of service level interworking for messaging services

4.1  Introduction

The service level interworking for messaging services provides the interworking function between Instant Message or Chat Sessions and the Short Message to enable the communication between SM UE and Instant Message or CPM UE. The architecture for service level interworking is specified in TS 23.204.

4.2  Service level interworking between SM and IM

In order to provide the service level interworking between SM and IM, the following protocol mapping functionalities defined in TS 23.204 shall be supported:
  • Instant Message mapped to Short Message over CS/PS;
  • Instant Message mapped to Short Message over IP; and
  • Short Message mapped to Instant Message.

4.3  Interaction with transport layer interworking

Both transport layer interworking and service level interworking shall be provided by IP-SM-GW. The interaction between transport layer interworking and service level interworking depends on the user subscription and authorization, on the UE capabilities, and on operator policy.
If a user only subscribes to either transport layer interworking or to service level interworking, only procedures defined for the subscribed interworking shall be performed by the IP-SM-GW.
If a user subscribes to both transport layer interworking and service level interworking, but the user is only authorised for one of the interworking when the message is processed, only the authorised interworking shall be performed by the IP-SM-GW.
If a user subscribes to both transport layer interworking and service level interworking, and is authorised for both, the behaviour of the IP-SM-GW depends on the specific scenario, on the registered capabilities of the UE, and finally is defined by operator policy and user preferences.
Up

4.4  Service level interworking between SM and Chat Session |R10|Word‑p. 10

In order to provide the service level interworking between SM and Chat Session, the following protocol mapping functionalities defined in TS 23.204 shall be supported:
  • Chat Session invitation request mapped to Short Message;
  • Short Message mapped to Chat Session MSRP SEND request;
  • Chat Session MSRP SEND request mapped to Short Message;
  • Short Message mapped to Chat Session teardown request;
  • Chat Session teardown request mapped to Short Message; and
  • Event package for conference state information specified in RFC 4575 mapped to Short Message.
Up

5  Functional entities

5.1  Application Server (AS)

An AS may implement the role of an IP-SM-GW (see subclause 6.1).

Up   Top   ToC