23.2043GPPRelease 16Stage 2Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) accessTS
6.3a.1 Initial delivery of SMS without MSISDN
Figure 6.3a.1 shows the initial SM delivery by IP-SM-GW during MO-SMS operation without MSISDN.
Figure 6.3a.1: Short Message origination procedure for MSISDN-less operation
1) The UE-A registers to S-CSCF according the IMS registration procedure. Note that I-CSCF and P-CSCF are not shown in this figure.
2) UE-A submits the encapsulated Short Message (SMS-SUBMIT, SC Address) to the S-CSCF using an appropriate SIP method. Since recipient does not have MSISDN, the UE-A fills the TP-DA field with value that indicates recipient UE is addressed without MSISDN, and indicates recipient’s SIP URI in SIP MESSAGE (e.g. UE-A sets the R-URI to PSI (SMSC address) and the To header with recipient’s SIP URI in the MESSAGE). Based on the existing procedure, P-CSCF fills the UE-A’s default URI to p-asserted-identity before sending the MESSAGE to S-CSCF.
NOTE: It is up to stage 3 to define how recipient’s SIP URI is to be indicated in the protocol level.
3) S-CSCF forwards the encapsulated Short Message (SMS-SUBMIT, SC Address) to IP-SM-GW (AS) based on stored iFC.
4) IP-SM-GW (AS) acknowledges the SIP message.
5) SIP message acknowledge is forwarded by S-CSCF to UE-A.
6) The IP-SM-GW performs service authorization based on the stored subscriber data as described in the clause 6.1. The IP SM GW shall check whether the subscriber is authorised to use the short message service (e.g. Operator Determined Barring settings), similar to the authorization performed by MSC/SGSN in case the Short Message is delivered via CS or PS domain. In addition, the IP-SM-GW shall also check whether the user is authorised to use the encapsulated Short Message delivery via IMS. If the result of service authorization is negative, the IP-SM-GW shall not forward the message, and shall return the appropriate error information to the UE in a failure report. Otherwise, the IP-SM-GW (AS) extracts the Short Message (SMS-SUBMIT) and constructs the SMS-DELIVER and sends it towards the terminating IMS network.
7) The terminating IMS network tries to deliver the SM toward the designated recipient (see clause 6.4a).
8) Terminating IMS network response with one of the following:
8a) Terminating IMS network refuses or does not allow SMS delivery with MSISDN-less operation by sending back a permanent error.
8b) Terminating IMS network is not able to deliver the SM to designated recipient and returns a MSISDN-less correlation ID to allow retries at a later time. IP-SM-GW then forwards the SM to SMSC for storage and forward operation (see clause 6.3a.2).
8c) Terminating IMS network is successfully deliver the SM toward the designated recipient.
9) Proper response as determined in step 8a, 8b, or 8c is returned back to UE-A. For 8a, the response indicates to the UE-A that SMS to this recipient is failed permanently. For 8b, the response is the Submit report received from the SMSC. For 8c, the response indicates a successful delivery of the SM to the recipient.
6.3a.2 Subsequent re-delivery of SMS without MSISDN
When the initial delivery attempt failed and retry is possible (see Figure 6.3a.1 step 8b), the IP-SM-GW forwards the SM to SMS-SC for storage and forwarding operation. Figure 6.3a.2 shows the subsequent re-delivery attempt of SM by SMS-SC.
Figure 6.3a.2: Redelivery attempt of SM without MSISDN
1) IP-SM-GW forwards the SM along with the MSISDN-less correlation ID received in step 8b of figure 6.3a.1 to SMS-SC/SMS-IWMSC.
2a) SMS-SC/SMS-GMSC receives a trigger to re-deliver the SMS from HSS (see clause 6.5b) and queries the HSS for serving node information using the recipient’s SIP URI and HLR-id from the MSISDN-less correlation ID.
2b) SMS-GMSC forwards the SM along with the MSISDN-less correlation ID to the IP-SM-GW using the address (i.e. IP-SM-GW of UE-B) received from HSS in step 2a.
3) IP-SM-GW (terminating) delivers SM to UE-B via the SIP MESSAGE.