Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.341  Word version:  17.1.0

Top   Top   None   None   Next
1…   5…   A…

 

1  Scopep. 7

The present document provides the protocol details for SMS over IP within the IP Multimedia (IM) Core Network (CN) subsystem based on the Session Initiation Protocol (SIP) and SIP Events as defined in TS 24.229.
The present document provides the protocol details for SMS over IP within the IP Multimedia (IM) Core Network (CN) subsystem based on the SMS layer as defined in TS 24.011.
Where possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of SIP and SIP Events, either directly, or as modified by TS 24.229.
The present document is applicable to Application Servers (ASs) and User Equipment (UE) providing SMS over IP functionality.
Up

2  Referencesp. 7

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.002: "Network Architecture".
[3]
TS 23.040: "Technical realization of the Short Message Service (SMS)".
[4]
TS 23.140: "Multimedia Messaging Service (MMS); Functional description; Stage 2".
[5]
TS 23.204: "Support of SMS over generic 3GPP IP access; Stage 2".
[6]
TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".
[7]
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[8]
TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
[8A]
TS 24.167: "3GPP IMS Management Object (MO)".
[9]
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".
[10]
TS 24.229: "Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[11]
TS 29.002: "Mobile Application Part (MAP) specification".
[12]
RFC 3261  (June 2002): "SIP: Session Initiation Protocol".
[13]
RFC 3325  (November 2002): "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks".
[14]
RFC 3428  (December 2002): "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[15]
RFC 3680  (March 2004): "A Session Initiation Protocol (SIP) Event Package for Registrations".
[16]
RFC 3840  (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[17]
RFC 3841  (August 2004): "Caller Preferences for the Session Initiation Protocol (SIP)".
[18]
TS 31.103: "Characteristics of the IP Multimedia Services Identity Module (ISIM) Application".
[19]
TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) Application".
[20]
TS 51.011: Release 4: "Specification of the Subscriber Identity Module, Mobile Equipment (SIM - ME) interface".
[21]
TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit (USAT)".
[22]
TS 23.003: "Numbering, addressing and identification".
[23]
TS 29.311: "Service Level Interworking (SLI) for messaging services".
[24]
RFC 6809  (November 2012): "Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)".
[25]
RFC 5621  (September 2009): "Message Body Handling in the Session Initiation Protocol (SIP)".
[26]
RFC 4288  (December 2005): "Media Type Specifications and Registration Procedures".
[27]
RFC 6665  (July 2012): "SIP-Specific Event Notification".
[28]
TS 22.011: "Service accessibility".
[29]
TS 23.221: "Architectural requirements".
[30]
TS 24.216: "Communication Continuity Management Object (MO)".
[31]
TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".
Up

3  Definitions and abbreviationsp. 8

3.1  Definitionsp. 8

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.
MSISDN less operation:
Operation of SMS over IP for subscriber without MSISDN in the subscription profile as defined in TS 23.204, clause 6.0a.
SM-over-IP sender:
the A party that sends an SM using a SIP MESSAGE request including a vnd.3gpp.sms payload (introduced in TS 23.140).
SM-over-IP receiver:
the B party that receives an SM encapsulated in the vnd.3gpp.sms payload of a SIP MESSAGE request.
For the purposes of the present document, the following terms and definitions given in RFC 3261 apply.
Header
Header field
Method
Request
Response
(SIP) transaction
Status-code (see Section 7.2 of RFC 3261)
Tag (see Section 19.3 of RFC 3261)
For the purposes of the present document, the following terms and definitions given in TS 23.002, clause 4.1.1.1 and TS 23.002, clause 4a.7 apply:
Call Session Control Function (CSCF)
Home Subscriber Server (HSS)
For the purposes of the present document, the following terms and definitions given in TS 23.218, clause 3.1 apply:
Filter criteria
Initial filter criteria
For the purposes of the present document, the following terms and definitions given in TS 23.228, clause 4.3.3.1, TS 23.228, clause 4.3.6 and TS 23.228, clause 4.6 apply:
Interrogating-CSCF (I-CSCF)
Public Service Identity (PSI)
Proxy-CSCF (P-CSCF)
Serving-CSCF (S-CSCF)
For the purposes of the present document, the following terms and definitions given in TS 22.011 apply:
3GPP PS data off
3GPP PS data off exempt service
For the purposes of the present document, the following terms and definitions given in TS 24.229 apply:
3GPP PS data off status
For the purposes of the present document, the following terms and definitions given in TS 23.122 apply:
Equivalent Home PLMN (EHPLMN)
Home PLMN (HPLMN)
Visited PLMN (VPLMN)
Up

3.2  Abbreviationsp. 9

For the purposes of the present document, the abbreviations given in TR 21.905, TS 23.040 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
IP-SM-GW
IP-Short-Message-Gateway
PS
Packet Switched

4  Overview of SMS over IP functionalityp. 9

4.1  Introductionp. 9

SMS over IP functionality provides the UE with the capability of sending traditional short messages over IMS network. The architecture for SMS is specified in TS 23.040 and for SMS over IP functionality in TS 23.204.

4.2  SMS over IPp. 9

In order to guarantee SMS interoperability the SM-over-IP sender, the SM-over-IP receiver and the IP-SM-GW shall support encapsulation of RPDUs defined in TS 24.011, clause 7.3. The SM-over-IP sender, the SM-over-IP receiver and the IP-SM-GW shall use the MIME type "application/vnd.3gpp.sms" for this purpose.

4.3  Application utilisation of SMS over IPp. 10

SMS over generic IP access can be used to support all applications and services that use SMS.

4.4  SMS over IP and subscription without MSISDN |R11|p. 10

When SMS over IP is to be delivered to a subscriber where the subscription profile does not contain an MSISDN, then there is a need for the IP-SM-GW to become aware of the IMSI during IMS registration for later correlation of short messages. In order to do so the IP-SM-GW derives the IMSI from the private user identity of the user that the UE includes in the REGISTER request at registration or if the private user identity is not available, derives the IMSI from the public user identity.
3GPP TS 23.003 defines the relationship between the private user identity and the IMSI and the relationship between the public user identity and the IMSI.
Up

Up   Top   ToC