B.6 Signalling flows demonstrating successful UE terminated SM deliver procedure over IP (including delivery report)

24.3413GPPRelease 18Stage 3Support of SMS over IP networksTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

Figure B.6-1: UE originated SM deliver procedure over IP signalling

It is assumed that "sip:user2_public2@home2.net" associated with MSISDN=11111111 is registered at ipsmgw.home2.net using an SMS capable UE.

Figure B.6-1 shows a successful UE terminated SM over IP delivery. The details of the signalling flows are as follows:

1. Receiving SM from SC

The IP-SM-GW receives a short message from SC (sc.home1.net) which includes SMS-DELIVER as type indicator and MSISDN=11111111 as destination UE.

2. MESSAGE request (IP-SM-GW to S-CSCF) – see example in table B.6-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.6-1: MESSAGE request (IP-SM-GW to S-CSCF)

MESSAGE sip:user2_public2@home2.net SIP/2.0

Via: SIP/2.0/UDP ipsmgw.home2.net; branch=z9hG4bK876ffa3

Max-Forwards: 70

Route: <sip:scscf1.home2.net;lr>

From: <sip:ipsmgw.home2.net>; tag=583558

To: <sip:user2_public2@home2.net>

Call-ID: fy365h43g3f36f3f6fth74g3

Cseq: 888 MESSAGE

P-Asserted-Identity: sip:ipsmgw.home2.net

Request-Disposition: no-fork

Accept-Contact: *;+g.3gpp.smsip;require;explicit

Content-Type: application/vnd.3gpp.sms

Content-Length: (…)

Request-URI: Public user identity receiving the delivery report.

The payload includes the RP-DATA message (see 3GPP TS 24.011 [8]). Its RP-User-Data information element includes a TPDU of type SMS-DELIVER.

3. MESSAGE request (S-CSCF to P-CSCF) – see example in table B.6-2

S-CSCF performs the caller preferences to callee capabilities matching and builds the Request-URI with the selected contact.

Table B.6-2: MESSAGE request (S-CSCF to P-CSCF)

MESSAGE sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK344a651, SIP/2.0/UDP ipsmgw.home2.net; branch=z9hG4bK876ffa3

Max-Forwards: 69

Route: <sip:pcscf2.visited2.net:7531;lr;comp=sigcomp>

From: <sip:ipsmgw.home2.net>; tag=583558

To: <sip:user2_public2@home2.net>

Call-ID: fy365h43g3f36f3f6fth74g3

Cseq: 888 MESSAGE

P-Asserted-Identity: sip:ipsmgw.home2.net

P-Called-Party-ID: <sip:user2_public2@home2.net>

Request-Disposition: no-fork

Accept-Contact: *;+g.3gpp.smsip;require;explicit

Content-Type: application/vnd.3gpp.sms

Content-Length: (…)

Request-URI: SMS capable contact of the public user identity.

4. MESSAGE request (P-CSCF to UE) – see example in table B.6-3

Table B.6-3: MESSAGE request (P-CSCF to UE)

MESSAGE sip:[5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp SIP/2.0

Via: SIP/2.0/UDP pcscf2.visited2.net;branch=z9hG4bK2524fd2, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK344a651, SIP/2.0/UDP ipsmgw.home2.net; branch=z9hG4bK876ffa3

Max-Forwards: 68

From: <sip:ipsmgw.home2.net>; tag=583558

To: <sip:user2_public2@home2.net>

Call-ID: fy365h43g3f36f3f6fth74g3

Cseq: 888 MESSAGE

P-Called-Party-ID: <sip:user2_public2@home2.net>

Request-Disposition: no-fork

Accept-Contact: *;+g.3gpp.smsip;require;explicit

Content-Type: application/vnd.3gpp.sms

Content-Length: (…)

5. 200 (OK) response (UE to P-CSCF) – see example in table B.6-4

Table B.6-4: 200 (OK) response (UE to P-S-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf2.visited2.net;branch=z9hG4bK2524fd2, SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK344a651, SIP/2.0/UDP ipsmgw.home2.net; branch=z9hG4bK876ffa3

From:

To:

Call-ID:

Cseq:

6. 200 (OK) response (P-CSCF to S-CSCF) – see example in table B.6-5

Table B.6-5: 200 (OK) response (P-CSCF to S-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK344a651, SIP/2.0/UDP ipsmgw.home2.net; branch=z9hG4bK876ffa3

From:

To:

Call-ID:

Cseq:

7. 200 (OK) response (S-CSCF to IP-SM-GW) – see example in table B.6-6

Table B.6-6: 200 (OK) response (S-CSCF to IP-SM-GW)

SIP/2.0 200 OK

Via: SIP/2.0/UDP ipsmgw.home2.net; branch=z9hG4bK876ffa3

From:

To:

Call-ID:

Cseq:

8. MESSAGE request (UE to P-CSCF) – see example in table B.6-7

This request includes a vnd.3gpp.sms payload that includes the SMS-DELIVER-REPORT and routing information for the IP-SM-GW to forward the delivery report.

Table B.6-7: MESSAGE request (UE to P-CSCF)

MESSAGE sip:ipsmgw.home2.net SIP/2.0

Via: SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7

Max-Forwards: 70

Route: <sip:pcscf2.visited2.net:7531;lr;comp=sigcomp>, <sip:orig@scscf2.home2.net;lr>

P-Preferred-Identity: "John Doe" <sip:user2_public2@home2.net>

From: <sip:user2_public2@home2.net>; tag=171828

To: <sip:ipsmgw.home2.net>

Call-ID: cb03a0s09a2sdfglkj490333

In-Reply-to: fy365h43g3f36f3f6fth74g3

Cseq: 999 MESSAGE

Content-Type: application/vnd.3gpp.sms

Content-Length: (…)

Request-URI: The IP-SM-GW that sent the SIP MESSAGE request including the delivered short message to the SM-over-IP receiver.

The payload includes an RP-ACK message (see 3GPP TS 24.011 [8]). Its RP-User-Data information element includes a TPDU of type SMS-DELIVER-REPORT.

9. MESSAGE request (P-CSCF to S-CSCF) – see example in table B.6-8

Table B.6-8: MESSAGE request (P-CSCF to S-CSCF)

MESSAGE sip:ipsmgw.home2.net SIP/2.0

Via: SIP/2.0/UDP pcscf2.visited2.net;branch=z9hG4bK240f341, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7

Max-Forwards: 69

Route: <sip:orig@scscf2.home2.net;lr>

P-Asserted-Identity: "John Doe" <sip:user2_public2@home1.net>

From: <sip:user2_public2@home2.net>; tag=171828

To: <sip:ipsmgw.home2.net>

Call-ID: cb03a0s09a2sdfglkj490333

In-Reply-to: fy365h43g3f36f3f6fth74g3

Cseq: 999 MESSAGE

Content-Type: application/vnd.3gpp.sms

Content-Length: (…)

10. Initial filter criteria

The S-CSCF analyses the incoming request against the initial filter criteria and decides to send the SIP MESSAGE request to the IP-SM-GW.

11. MESSAGE request (S-CSCF to IP-SM-GW) – see example in table B.6-9

Table B.6-9: MESSAGE request (S-CSCF to IP-SM-GW)

MESSAGE sip:ipsmgw.home2.net SIP/2.0

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK344a651, SIP/2.0/UDP pcscf2.visited2.net;branch=z9hG4bK240f341, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7

Max-Forwards: 68

Route: <sip:ipsmgw.home2.net;lr>, <sip:cb03a0s09a2sdfglkj490333@scscf2.home2.net;lr>

P-Asserted-Identity: "John Doe" <sip:user2_public2@home2.net>

P-Asserted-Identity: tel:+12125552222

From: <sip:user2_public2@home2.net>; tag=171828

To: <sip:ipsmgw.home2.net>

Call-ID: cb03a0s09a2sdfglkj490333

In-Reply-to: fy365h43g3f36f3f6fth74g3

Cseq: 666 MESSAGE

Content-Type: application/vnd.3gpp.sms

Content-Length: (…)

12. 202 (Accepted) response (IP-SM-GW to S-CSCF) – see example in table B.6-10

Table B.6-10: 202 (Accepted) response (IP-SM-GW to S-CSCF)

SIP/2.0 202 Accepted

Via: SIP/2.0/UDP scscf2.home2.net;branch=z9hG4bK344a651, SIP/2.0/UDP pcscf2.visited2.net;branch=z9hG4bK240f341, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7

From:

To:

Call-ID:

Cseq:

13. 202 (Accepted) response (S-CSCF to P-CSCF) – see example in table B.6-11

Table B.6-11: 202 (Accepted) response (S-CSCF to P-CSCF)

SIP/2.0 202 Accepted

Via: SIP/2.0/UDP pcscf2.visited2.net;branch=z9hG4bK240f341, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7

From:

To:

Call-ID:

Cseq:

14. 202 (Accepted) response (P-CSCF to UE) – see example in table B.6-12

Table B.6-12: 202 (Accepted) response (P-CSCF to UE)

SIP/2.0 202 Accepted

Via: SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7

From:

To:

Call-ID:

Cseq:

15. Extracting and forwarding the delivery report

The IP-SM-GW forwards the short message TPDU (SMS‑DELIVER-REPORT) to the SC.