Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 23.804 Word version: 7.1.0

0… 4…

4 Overall Requirements p. 6

5 Architectural requirements and considerations p. 6

5.1 Architecture for support of SMS p. 6

5.1.1 IP Short Message Gateway (IP-MESSAGE-GW) p. 7

5.1.2 HLR/HSS p. 7

5.1.2.1 Indication that the terminal is registered with an IP Short Message gateway p. 8

5.1.2.2 The address of the IP-MESSAGE-GW p. 8

5.1.3 Reference points p. 8

5.1.3.1 R1 reference point p. 8

5.1.3.2 R2 reference point p. 8

5.1.3.3 R3 reference point p. 8

5.1.3.4 R4 reference point p. 8

5.1.3.5 R5 reference point p. 9

5.1.3.6 R6 reference point p. 9

6 Security aspects p. 9

7 Charging aspects p. 9

7.1 SMS Charging p. 9

8 Procedures p. 9

8.1 Common registration procedure p. 10

8.2 De-registration procedure p. 10

8.2.1 UE initiated p. 10

8.2.2 IP-Message-GW initiated p. 11

8.3 Successful SMS MO delivery procedure p. 11

8.4 Successful SMS MT deliver procedure p. 12

8.5 Unsuccessful MT deliver procedure p. 13

8.6 SMS Alerting procedure p. 14

8.6.1 SMS Alerting procedure when UE has memory available to receive one or more short messages p. 14

8.7 Registration procedure using SIP/IMS p. 15

8.8 De-registration procedure using SIP/IMS p. 16

8.8.1 UE initiated p. 16

8.9 Successful SMS MO delivery procedure using SIP/IMS p. 17

8.10 Successful SMS MT deliver procedure using SIP/IMS p. 18

8.11 MMS procedures p. 19

8.11.1 MMS Origination procedure p. 19

8.11.2 MMS Terminating Procedure p. 21

8.11.3 MMS with SIP based Push p. 22

8.11.3.1 General p. 22

8.11.3.2 MMS Origination procedure p. 22

8.11.3.3 MMS Terminating Procedure p. 23

9 Conclusion and recommendations p. 24

$ Change history p. 25