Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑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.1.15  — fig. 16d p. 127

Copy of original 3GPP image for 3GPP TS 23.040, Fig. 16d: "Send information for MT SMS" procedure; incorrect authentication
Up

10.1.16  — fig. 17a p. 128

Copy of original 3GPP image for 3GPP TS 23.040, Fig. 17a: Successful short message transfer attempt via the MSC, SGSN or MME, with short message retransmission by the SMS-GMSC at the time requested by the MSC, SGSN or MME
Up
Operation 4a:
the SMS-GMSC indicates in the ForwardShortMsg that it is capable to retransmit the Short Message until a maximum retransmission time.
Operation 4c:
If the MS is using extended idle mode DRX, and if the ForwardShortMsg includes a maximum retransmission time, the MSC in Deployment Option 2 (see clause 8.2.4a.1 of TS 23.272), SGSN or MME may return a Delivery Report with a cause indicating that the user is temporarily unreachable and with an indication requesting the SMS-GMSC to retransmit the Short Message at a later requested retransmission time prior to the maximum retransmission time. In that case, the MSC in Deployment Option 2 (see clause 8.2.4a.1 of TS 23.272), SGSN or MME shall not set the MNRF, MNRG or MNRF flag respectively. The SMS-GMSC shall not send an SM-Delivery Report Status to the HLR or HSS.
Operation 5a:
the SMS-GMSC retransmits the Short Message at the requested retransmission time.
Up

Up   Top   ToC