Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.863  Word version:  12.0.0

Top   Top   None   None   Next
0…   4…

 

0  Introductionp. 6

Since Release 7, SMS delivery over IMS has been possible with TS 23.204. The fundamental principle used when developing that work is to reuse the legacy CS SMS infrastructure in order to preserve the possibility to deliver SMS to both CS/PS domain and IMS as the user may roam between both domains. In addition, the existing SMS infrastructure that an operator has in place e.g. SC, GMSC-SMS, IWMSC is able to be reused. This is achieved by mandating MSISDN as part of the SMS delivery addressing, even for SMS delivery toward IMS.
In Release 11, MTC allows the UE to have PS only subscription without MSISDN. Such UE may also be IMS UE. Allowing Messages delivery to these UEs in IMS without MSISDN is an important requirement for these devices.
Therefore, there is a need to improve the SMS submit/delivery mechanism within IMS to allow MSISDN-less delivery toward the IMS registered UEs.
Up

1  Scopep. 7

This Technical Report is to specify architecture enhancement toward SMS submit/delivery mechanism in IMS to allow IMS registered UE to:
  • Receive and send SMS without requiring an MSISDN associated as part of their IMS subscription record in HSS and
  • any possible enhancements towards the related storing and forwarding mechanism if the UE is out of reach.
There are three potential aspects for these IMS UEs without MSISDN that need to be investigated:
  1. Server - IMS UE communication via SMS (e.g. for M2M).
  2. IMS UE to IMS UE communication via SMS for person to person communications. Both UEs do not have MSISDN.
  3. SMS Interworking between IMS UE without MSISDN and traditional UE (e.g. CS) with MSISDN.
Normative specification work (if needed or feasible) for each of these areas can be started independently.
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.040: "Technical realization of the Short Message Service (SMS)".
[3]
TR 21 912: (V3.1.0) "Example 2, using fixed text".
→ to date, withdrawn by 3GPP
[4]
TS 23.204: "Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access".
[6]
TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
[7]
TS 29.311: "Service Level Interworking (SLI) for messaging services".
[8]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
Up

3  Definitions and abbreviationsp. 7

3.1  Definitionsp. 7

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.
Server:
A Short Message Entity (SME) in the network which sends or receives SMS to/from MSISDN-less IMS UE.
Traditional UE:
UE with MSISDN for as part of its subscription profile and using MSISDN for SMS service.
Up

3.2  Abbreviationsp. 8

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply.
MSISDN
Mobile Station International ISDN Number

Up   Top   ToC