tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TS 23.204 (SA2)
Support of SMS over Generic 3GPP IP Access – Stage 2

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    61 p.
(P) V13.1.0    2016/06    61 p.
(P) V12.5.0    2016/06    61 p.
(P) V11.5.0    2013/09    57 p.
(P) V10.2.0    2010/09    55 p.
(P) V9.1.0    2010/03    39 p.
(P) V8.5.0    2010/03    39 p.
(P) V7.6.0    2009/03    22 p.


Rapporteur:  Mr. Zhang, Wenlin
Antecedent:  TR 23.804    
See also:  SMS-related TS/TR    


The Short Message Service (SMS) has have enjoyed great success in cellular networks. At the same time, specifications have been and are being developed for extending 3GPP services to non-cellular IP Connectivity Access Networks (IPCANs). In this same spirit, this specification describes the capabilities needed to support SMS for generic IP-CANs.

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

This TS specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228). These include (but are not limited) to:
  • Enhancements to the HSS;
  • Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
  • Authentication of service usage and registration;
  • Transfer of UE Terminated SMS, UE Originated SMS, and Delivery reports;
  • Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
  • Mechanisms to handle MT-SMS without MSISDN.
The document also specifies the capabilities and enhancements needed to support the service level interworking for the Short Message service as defined in the TS 23.040 and in this specification and the Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.

Note:  The page-mode immediate message as defined in TS 24.247 is considered as a subset of OMA-TS-SIMPLE-IM-V1_0.

The document also specifies the capabilities and enhancements needed to support service level interworking for the Short Message service, as defined in the TS 23.040 and in this specification and the OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0. The features supported from the CPM specification are the exchange of short or large immediate messages in pager mode, as well as session-based messaging.

The service requirements are described in TS 22.340.


 

Here          Top          None          None          Next
part:    1     2

 

1 Scope    2 References    3 Definitions and abbreviations    3.1 Definitions    3.2 Abbreviations    4 Void    4a Architecture Requirements    4a.1 General    4a.2 Transport-level interworking    4a.3 Service-level interworking    4a.4 SMS without MSISDN    4a.5 SMS without MSISDN interworking with Non-supporting MSISDN-less SMS UE    5 Architecture model and reference points    5.1 Reference architecture    5.2 Reference points    5.3 Functional entities    6 Procedures    6.0 General    6.0a SMS without MSISDN in IMS    6.1 Registration procedure    6.2 De-registration procedure    6.3 Transport-level interworking: Successful encapsulated Short Message origination procedure with MSISDN    6.3a Transport-level interworking: Short Message origination procedure without MSISDN    6.4 Transport-level interworking: Successful encapsulated Short Message termination procedure from SMS-GMSC    6.4a Transport-level interworking: Short Message termination procedure without MSISDN from IMS network    6.5 Transport-level interworking: Delivery Report procedure    6.5a Unsuccessful SM termination procedure    6.5b Alert Service Centre procedure when UE is available    6.6 Transport-level interworking: Alert service centre procedure when memory capacity is available    6.7 Service-level Interworking: IM or CPM capable UE sends an Instant Message to an SMS user    6.8 Interaction between transport-level and service-level Interworking    6.9 Service-level Interworking: Concatenated Short Messages delivered as a large Instant Message   
...

 

1   Scope [R7]   PDF-p. 6
2   References [R7]
3   Definitions and abbreviations [R7]   PDF-p. 7
4   Void
4a   Architecture Requirements [R7]
5   Architecture model and reference points [R7]   PDF-p. 11
6   Procedures [R7]   PDF-p. 15
6.0   General [R8]
6.0a   SMS without MSISDN in IMS [R11]
6.1   Registration procedure   PDF-p. 16      Up
6.2   De-registration procedure   PDF-p. 17
6.3   Transport-level interworking: Successful encapsulated Short Message origination procedure with MSISDN   PDF-p. 18
6.3a   Transport-level interworking: Short Message origination procedure without MSISDN [R12]   PDF-p. 19
6.4   Transport-level interworking: Successful encapsulated Short Message termination procedure from SMS-GMSC   PDF-p. 21
6.4a   Transport-level interworking: Short Message termination procedure without MSISDN from IMS network [R12]   PDF-p. 23
6.5   Transport-level interworking: Delivery Report procedure   PDF-p. 24      Up
6.5a   Unsuccessful SM termination procedure
6.5b   Alert Service Centre procedure when UE is available   PDF-p. 26
6.6   Transport-level interworking: Alert service centre procedure when memory capacity is available   PDF-p. 28
6.7   Service-level Interworking: IM or CPM capable UE sends an Instant Message to an SMS user [R8]   PDF-p. 29
6.8   Interaction between transport-level and service-level Interworking [R8]   PDF-p. 30
6.9   Service-level Interworking: Concatenated Short Messages delivered as a large Instant Message [R8]

Up          Top          ToC