7 MS functionality
23.0403GPPRelease 17Technical realization of the Short Message Service (SMS)TS
In the present document, only the MS functionality related to the short message service between the SC and the MS is specified.
7.1 MS capabilities
The MS, when equipped for SMS, should be capable of:
‑ submitting a short message TPDU to an SC, retaining the responsibility of the message until:
1) the report arrives from the network; or
2) a timer expires.
‑ receiving a short message TPDU from an SC;
‑ returning a delivery report to the network for a previously received short message;
‑ receiving a report from the network;
‑ notifying the network when it has memory capacity available to receive one or more short messages when it has previously rejected a short message because its memory capacity was exceeded;
‑ notifying the SC when a short message is intended to replace a short message the MS has previously submitted to the same destination address.
It is recommended that an MS supporting both replying and automatic SC selection (as specified in clause D.2 of annex D) follows procedures specified in annex D when replying to MT short messages with MO short messages.
It is recommended that an MS supporting a capability for requesting a reply path follows procedures specified in annex D.
7.2 MS configuration
The reference configuration is assumed as in figure 6, i.e. only the case where the terminal is integrated in the MS is considered.
Figure 6: Reference configuration of the MS which apply to the SMS
NOTE: It is foreseen that a terminal interface may be offered, e.g. for higher layer protocols, memory capacity reasons or to be able to type in mobile originated messages. This terminal interface is regarded as an implementation option, although, where offered, it must be based upon an R‑ or S‑reference point. 3GPP TS 27.005 [14] provides an example based on the R reference point.