24.4513GPPRelease 8Stage 3 [Endorsement of 3GPP TS 24.341 Release 7]Support of SMS and MMS over NGN IMS subsystemTISPANTS

NOTE: When making modifications to the endorsed document’s original text, strikethrough text means deleted text and underlined text means inserted text. If there has been underlined text in the endorsed document’s original text, the underlining has been removed for the sake of clarity.

2 References

The references should be replaced as shown below.

Table 1: List of references to be replaced

5.3.2.5 Sending a notification about SM-over-IP receiver having memory available

When an SM-over-IP receiver wants to send a notification about UE having memory available, the SM-over-IP receiver shall send a SIP MESSAGE request with the following information:

a) the Request-URI, which shall contain the IP-SM-GW address, if available. and shall contain PSI of the SC, otherwise;

NOTE 1: The address of the IP-SM-GW is received in the P-Asserted-Identity in the SIP MESSAGE request that included the short message the UE could not store.

b) the From header, which shall contain a public user identity of the SM-over-IP receiver;

c) the To header, which shall contain the IP-SM-GW address, if available, and shall contain PSI of the SC, otherwise;

d) the Content-Type header shall contain "application/vnd.3gpp.sms"; and

e) the body of the request shall contain an RP-SMMA message, see 3GPP TS 24.011 [8], including the SMS headers and the SMS user information encoded as specified in 3GPP TS 23.040 [3].

NOTE 2: The SM-over-IP receiver will use content transfer encoding of type "binary" for the encoding of the SMS in the body of the SIP MESSAGE request.

NOTE 3: According to 3GPP TS 23.204 [5], the IP-SM-GW routes SIP MESSAGE requests containing a notification of UE having memory available (containing RP-SMMA as the body) towards the HSS and routes other SIP MESSAGE requests (containing RP-DATA, RP-ACK or RP-ERROR as the body) towards SMS-IWMSC.

Annex ZA (informative):
Change history