B.5 Signalling flows demonstrating successful UE originated SM submit procedure over IP

24.3413GPPRelease 18Stage 3Support of SMS over IP networksTS

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

Figure B.5-1: UE originated SM submit procedure over IP signalling

Figure B.5-1 shows a successful UE originated SM over IP submission. For simplicity it is assumed that IP-SM-GW has direct access to SC. The details of the signalling flows are as follows:

1. MESSAGE request (UE to P-CSCF) – see example in table B.5-1

This request includes a vnd.3gpp.sms payload that includes the short message and routing information for the IP-SM-GW to forward the short message.

Table B.5-1: MESSAGE request (UE to P-CSCF)

MESSAGE sip:sc.home1.net SIP/2.0

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

Max-Forwards: 70

Route: <sip:pcscf1.visited1.net:7531;lr;comp=sigcomp>, <sip:orig@scscf1.home1.net;lr>

P-Preferred-Identity: "John Doe" <sip:user1_public1@home1.net>

From: <sip:user1_public1@home1.net>; tag=171828

To: <sip:sc.home1.net.net>

Call-ID: cb03a0s09a2sdfglkj490333

Cseq: 666 MESSAGE

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

Content-Length: (…)

Request-URI: PSI of the SC of user1_public1@home1.net.

The payload includes an RP-DATA message (see 3GPP TS 24.011 [8]). It includes:

– Address of the originating UE: this field includes the length indicator only;

– Address of the destination SC, which is configured in the UE; and

– RP-User-Data (see 3GPP TS 24.011 [8]), which includes SMS-SUBMIT (see 3GPP TS 23.040 [3]) as type indicator.

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

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

MESSAGE sip:sc.home1.net SIP/2.0

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

Max-Forwards: 69

Route: <sip:orig@scscf1.home1.net;lr>

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

From: <sip:user1_public1@home1.net>; tag=171828

To: <sip:sc.home1.net>

Call-ID: cb03a0s09a2sdfglkj490333

Cseq: 666 MESSAGE

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

Content-Length: (…)

3. 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.

4. MESSAGE request (S-CSCF to IP-SM-GW) – see example in table B.5-3

Table B.5-3: MESSAGE request (S-CSCF to IP-SM-GW)

MESSAGE sip:sc.home1.net SIP/2.0

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK344a651, SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f341, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7

Max-Forwards: 68

Route: <sip:ipsmgw.home1.net;lr>, <sip:cb03a0s09a2sdfglkj490333@scscf1.home1.net;lr>

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

P-Asserted-Identity: tel:+12125551111

From: <sip:user1_public1@home1.net>; tag=171828

To: <sip:sc.home1.net>

Call-ID: cb03a0s09a2sdfglkj490333

Cseq: 666 MESSAGE

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

Content-Length: (…)

5. 202 (Accepted) response (IP-SM-GW to S-CSCF) – see example in table B.5-4

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

SIP/2.0 202 Accepted

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK344a651, SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK240f341, SIP/2.0/UDP [5555::aaa:bbb:ccc:ddd]:1357;comp=sigcomp; branch=z9hG4bKnashds7

From:

To:

Call-ID:

Cseq:

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

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

SIP/2.0 202 Accepted

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

From:

To:

Call-ID:

Cseq:

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

Table B.5-6: 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:

8. Extracting and forwarding the short message, waiting and processing report

The IP-SM-GW forwards the short message TPDU (SMS‑SUBMIT) to the SC. The SC returns a submit report which includes SMS-SUBMIT-REPORT as type indicator.

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

This request includes a vnd.3gpp.sms payload that includes the short message submission report and routing information for the IP-SM-GW to forward the submission report.

Table B.5-7: 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

Max-Forwards: 70

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

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

To: <sip:user1_public1@home1.net>

Call-ID: fy365h43g3f36f3f6fth74g3

Cseq: 888 MESSAGE

P-Asserted-Identity: <sip:ipsmgw.home1.net>

In-Reply-to: cb03a0s09a2sdfglkj490333

Request-Disposition:fork,parallel

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

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

Content-Length: (…)

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

The payload includes an RP-ACK message (see 3GPP TS 24.011 [8]). It includes RP-User-Data (see 3GPP TS 24.011 [8]), which includes SMS-SUBMIT-REPORT (see 3GPP TS 23.040 [3]) as type indicator.

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

Table B.5-8: 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 scscf1.home1.net;branch=z9hG4bK344a651, SIP/2.0/UDP ipsmgw.home1.net; branch=z9hG4bK876ffa3

Max-Forwards: 69

Route: <sip:pcscf1.visited1.net:7531;lr;comp=sigcomp>

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

To: <sip:user1_public1@home1.net>

Call-ID: fy365h43g3f36f3f6fth74g3

Cseq: 888 MESSAGE

P-Asserted-Identity: <sip:ipsmgw.home1.net>

P-Called-Party-ID: <sip:user1_public1@home1.net>

In-Reply-to: cb03a0s09a2sdfglkj490333

Request-Disposition:fork,parallel

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

Content-Length: (…)

11. MESSAGE request (P-CSCF to UE) – see example in table B.5-9

Table B.5-9: MESSAGE request (P-CSCF to UE)

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

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK2524fd2, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK344a651, SIP/2.0/UDP ipsmgw.home1.net; branch=z9hG4bK876ffa3

Max-Forwards: 68

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

To: <sip:user1_public1@home1.net>

Call-ID: fy365h43g3f36f3f6fth74g3

Cseq: 888 MESSAGE

P-Called-Party-ID: <sip:user1_public1@home1.net>

In-Reply-to: cb03a0s09a2sdfglkj490333

Request-Disposition:fork,parallel

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

Content-Length: (…)

12. 200 (OK) response (UEto P-CSCF) – see example in table B.5-10

Table B.5-10: 200 (OK) response (UE to P-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP pcscf1.visited1.net;branch=z9hG4bK2524fd2, SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK344a651, SIP/2.0/UDP ipsmgw.home1.net; branch=z9hG4bK876ffa3

From:

To:

Call-ID:

Cseq:

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

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

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK344a651, SIP/2.0/UDP ipsmgw.home1.net; branch=z9hG4bK876ffa3

From:

To:

Call-ID:

Cseq:

14. 200 (OK) response (S-CSCF to IP-SM-GW) – see example in table B.5-12

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

SIP/2.0 200 OK

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

From:

To:

Call-ID:

Cseq: