B.7 Signalling flow demonstrating successful procedures for SM over IP in case terminating side is addressed with SIP URI
24.3413GPPRelease 18Stage 3Support of SMS over IP networksTS
Figure B.7-1: SM over IP procedures when terminating UE is addressed with SIP URI
It is assumed that "sip:user1_public1@home1.net" is registered at ipsmgw.home1.net using an SMS capable UE and addresses UE 2 with sip:user2_public2@home2.net. "sip:user2_public2@home2.net" is registered at ipsmgw.home2.net using an SMS capable UE.
1. Receiving SM from UE
The IP-SM-GW receives a SIP MESSAGE request containing a short message from UE-1 which includes SMS-SUBMIT as type indicator and TP-DA field set to the dummy MSISDN.
The destination address of the short message is include in a XML body include in the received SIP MESSAGE request. The IP-SM-GW will include this URI in the Request-URI of the outgoing SIP MESSAGE request
– The IP-SM-GW analysis of the destination address and local policy indicates that the terminating side can be addressed with SIP URI for delivery of SM.
– The IP-SM-GW constructs a RP DATA with SMS-DELIVER as type indicator. The TP-OA field is set to the dummy MSISDN value as defined in 3GPP TS 23.003 [22]
– The IP-SM-GW will include the SIP URI of user1 received in the P-Asserted-Identity header field in the short-message-info XML body that is included in the outgoing SIP MESSAGE request.
2. MESSAGE request (IP-SM-GW to S-CSCF) – see example in table B.7-1
This request includes a vnd.3gpp.sms payload that includes the short message and routing information for the S-CSCF to forward the short message.
Table B.7-1: MESSAGE request (IP-SM-GW to S-CSCF)
MESSAGE sip:user2_public2@home2.net SIP/2.0
Via: SIP/2.0/UDP ipsmgw.home1.net; branch=z9hG4bK876ffa3
Feature-Caps: *;+g.3gpp.smsip-msisdn-less
Max-Forwards: 70
Route: <sip:scscf1.home1.net;lr>
From: <sip:ipsmgw.home1.net>; tag=583558
To: <sip:user2_public2@home2.net>
Call-ID: cb03a0s09a2sdfglkj490333
Cseq: 888 MESSAGE
P-Asserted-Identity: sip:ipsmgw.home1.net
Request-Disposition: no-fork
Content-Type: multipart/mixed; boundary=outer
Content-Length: (…)
–outer
Content-Type: application/vnd.3gpp.sms
–outer
Content-Type: application/vnd.3gpp.sms+xml
<?xml version="1.0" encoding="UTF-8"?>
<short-message-info>
<From>sip:user1_public1@home1.net</From>
</short-messsage-info>
–outer—
Request-URI: Public user identity of the receiving UE.
P-Asserted-ID: value of the originating side IP-SM-GW.
Feature-Caps: g. 3gpp.smsip-msisdn-less indicator indicating that an IP-SM-GW supporting MISDSN less operation is in the signalling chain for the SIP MESSAGE.
3. MESSAGE request (S-CSCF to terminating side)
– The S-CSCF serving ipsmgw.home1.net forwards the SIP MESSAGE request based on the R-URI.
4. MESSAGE request (I-CSCF to S-CSCF)
– The I-CSCF forwards the SIP MESSAGE request to the S-CSCF that hosts the subscriber that is indicated in the R-URI as per normal IMS procedures.
5. MESSAGE request (S-CSCF to IP-SM-GW)
– The S-CSCF serving ipsmgw.home1.net forwards the SIP MESSAGE request based on iFC to the IP-SM-GW hosting the service for the subscriber.
6. 202 (Accepted) response (IP-SM-GW to S-CSCF)
7. 202 (Accepted) response (S-CSCF to I-CSCF)
8. 202 (Accepted) response (I-CSCF to S-CSCF)
9. 202 (Accepted) response (S-CSCF to IP-SM-GW)
10. Delivery of Short Message via SIP MESSAGE
– The IP-SM-GW delivers the SIP MESSAGE to the user that is indicted in the R-URI of the incoming SIP MESSAGE.
11. Short Message Deliver Report
– The IP-SM-GW receives a SIP MESSAGE request containing a DELIVER REPORT to a previously sent short message.
12. MESSAGE request (IP-SM-GW to S-CSCF) – see example in table B.7-2
The SIP MESSAGE request includes a vnd.3gpp.sms payload that includes the DELIVER REPORT and routing information for the S-CSCF to forward the short message.
– The destination address for the delivery report is included in a XML body include in the received SIP MESSAGE request. The IP-SM-GW will include this URI in the Request-URI of the outgoing SIP MESSAGE request
– The IP-SM-GW will include the SIP URI of user2 received in the P-Asserted-Identity header field in the short-message-info XML body that is included in the outgoing SIP MESSAGE request.
Table B.7-2: MESSAGE request (IP-SM-GW to S-CSCF)
MESSAGE sip:user1_public1@home1.net SIP/2.0
Via: SIP/2.0/UDP ipsmgw.home1.net; branch=z9hG4bK876ffa3
Feature-Caps: *;+g.3gpp.smsip-msisdn-less
Max-Forwards: 70
Route: <sip:scscf2.home2.net;lr>
From: <sip:ipsmgw.home2.net >; tag=583558
To: <sip:user1_public1@home1.net>
Call-ID: fy365h43g3f36f3f6fth74g3
Cseq: 888 MESSAGE
P-Asserted-Identity: sip:ipsmgw.home2.net
In-Reply-to: cb03a0s09a2sdfglkj490333
Content-Type: multipart/mixed; boundary=outer
Content-Length: (…)
–outer
Content-Type: application/vnd.3gpp.sms
–outer
Content-Type: application/vnd.3gpp.sms+xml
<?xml version="1.0" encoding="UTF-8"?>
<short-message-info>
<From>sip:user2_public1@home2.net</From>
</short-messsage-info>
–outer—
Request-URI: Public user identity of the receiving UE.
P-Asserted-ID: value of the terminating side IP-SM-GW.
Feature-Caps: g. 3gpp.smsip-msisdn-less indicator indicating that an IP-SM-GW supporting MISDSN less operation is in the signalling chain for the SIP MESSAGE.
13. MESSAGE request (S-CSCF to terminating side)
– The S-CSCF serving ipsmgw.home1.net.net forwards the SIP MESSAGE request based on the R-URI.
14. MESSAGE request (I-CSCF to S-CSCF)
– The I-CSCF forwards the SIP MESSAGE request to the S-CSCF that hosts the subscriber that is indicated in the R-URI as per normal IMS procedures.
15. MESSAGE request (S-CSCF to IP-SM-GW)
– The S-CSCF serving user1_public1@home1.net forwards the SIP MESSAGE request based on iFC to the IP-SM-GW hosting the service for the subscriber.
16. 202 (Accepted) response (IP-SM-GW to S-CSCF)
17. 202 (Accepted) response (S-CSCF to I-CSCF)
18. 202 (Accepted) response (I-CSCF to S-CSCF)
19. 202 (Accepted) response (S-CSCF to IP-SM-GW)
12. Short Message Deliver Report
– The IP-SM-GW sends a SIP MESSAGE containing the DELIVER REPORT to the user indicated in the Request-URI received in message 15.
Annex C (normative):
XML schemas