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  TS 23.040  Word version:  18.0.0

Top   Top   Up   Prev   Next
0…   3…   3.3…   4…   8…   9…   9.2…   9.2.2.2…   9.2.2.3…   9.2.3…   9.2.3.12…   9.2.3.24   9.2.3.24.1…   9.2.3.24.10…   9.2.3.24.10.1.12…   9.2.3.24.10.2…   9.2.3.24.11…   9.2.3.25…   9.3…   10…   10.1.1…   10.1.3…   10.1.5…   10.1.7…   10.1.9…   10.1.11…   10.1.13…   10.1.15…   10.1.17…   10.2   10.2.1…   10.2.3…   10.2.5…   10.2.7…   10.3   11…   A…   C   C.1…   C.3…   C.5…   C.7…   C.9…   C.11…   C.13…   C.15…   D…   E…   F…   G…   G.2…   G.6   G.7   H…   I…   J…   K… 
10 Fundamental procedures within SMS  10.1 Short message mobile terminated 
...

 

10  Fundamental procedures within SMS  p. 111

The procedures for providing SMS over a generic IP CAN is described in TS 23.204 (see clause 6).
The SMS comprises 3 fundamental procedures:
  1. Short message mobile terminated. This procedure consists of all necessary operations to:
    1. transfer a short message or status report from the SC to the MS;
    2. return a report to the SC, containing the result of the message transfer attempt.
  2. Short message mobile originated. This procedure consists of all necessary operations to:
    1. transfer a short message from the MS to the SC;
    2. return a report to the MS, containing the result of the message transfer attempt.
  3. Transfer of an Alert. This procedure consists of all necessary operations for an HLR or a VLR to initiate a transfer of an Alert to a specific SC, informing the SC that the MS has recovered operation.
3GPP TS 29.002 defines operations necessary for the provision of the Short Message Service. The operations defined in clause 10 describe the requirement that the Short Message Service puts upon the network functionality. If discrepancies exist in nomenclature, it is the TS 29.002 that shall be the reference.
Annex C indicates the flow of primitives and parameters during the short message transfer between the SC and the MS. Both the Mobile terminated and the Mobile originated cases are covered.
Up

10.1  Short message mobile terminated  p. 112

The entities involved in this procedure are depicted in Figure 14.
Copy of original 3GPP image for 3GPP TS 23.040, Fig. 14: Interfaces involved in the Short message mobile terminated procedure. GSM TS 43.002 [5]. X is the interface between an MSC and an SC as defined in clause 5
Figure 14: Interfaces involved in the Short message mobile terminated procedure. GSM TS 43.002 [5]. X is the interface between an MSC and an SC as defined in clause 5
(⇒ copy of original 3GPP image)
Up
In Figure 15*, sequence diagrams are shown for the following basic situations of short message mobile terminated transfer attempt:
  • Successful short message transfer via the MSC or the SGSN;
  • Successful short message transfer via the SMS Router, and the MSC or SGSN;
  • Short message transfer attempt failing due to error at the SMS-GMSC;
  • Short message transfer attempt failing due to negative outcome of HLR information retrieval;
  • Short message transfer attempt via the SMS Router failing due to negative outcome of HLR information retrieval;
  • Short message transfer attempt failing due to error at the MSC or SGSN;
  • Short message transfer attempt failing due to negative outcome of VLR information retrieval;
  • Short message transfer attempt failing due to erroneous message transfer on the radio path;
  • Short message transfer attempt failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC);
  • Short message transfer attempt via the SMS Router failing over the first path (e.g. SGSN) and succeeding over the second path (e.g. MSC);
  • Short message transfer attempt failing over the first path (e.g. SGSN) and over the second path (e.g. MSC).
References to the relevant specifications of the different operations are given in clause 4.
Up

Up   Top   ToC