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.17  — fig. 17b p. 129

Copy of original 3GPP image for 3GPP TS 23.040, Fig. 17b: Successful short message transfer attempt via the MSC, SGSN or MME, with short message retransmission by the SMS-GMSC upon MS originated signalling prior to the retransmission time requested by the MSC, SGSN or MME
Up
Operation 4a:
same as for Figure 17a.
Operation 4c:
same as for Figure 17a.
Operation 5b:
Upon MS originated signalling to the same MSC in Deployment Option 2 (see clause 8.2.4a.1 of TS 23.272), SGSN or MME, the MSC in Deployment Option 2 (see clause 8.2.4a.1 of TS 23.272), SGSN or MME sends an Alert Service Center to the SMS-GMSC to trigger the immediate retransmission of the Short Message.
Operation 6a:
the SMS-GMSC retransmits the Short Message immediately.
Up

10.1.18  — fig. 17c p. 130

Copy of original 3GPP image for 3GPP TS 23.040, Fig. 17c: Successful short message transfer attempt via the MSC, SGSN or MME, with short message retransmission by the SMS-GMSC upon MS mobility to a new serving node prior to the retransmission time requested by the MSC, SGSN or MME.
Up
Operation 4a:
same as for Figure 17a.
Operation 4c:
same as for Figure 17a.
Operation 5c:
Upon MS mobility to a new SGSN or MME prior to the retransmission time requested by the old SGSN or MME, the old SGSN or MME signals to the new SGSN or MME (in the Context Response during a RAU or TAU procedure or in the Forward Relocation Request during a Handover procedure), that there is a pending MT Short Message to be sent to the MS.
Operation 5d:
if so, the new SGSN or MME signals its MAP or Diameter address for MT SMS to the old SGSN or MME (in the Context Acknowledge during a RAU or TAU procedure or in the Forward Relocation Response during a Handover procedure). The new SGSN or MME also maintains the signalling connection with the MS for a longer time to enable the retransmission of the Short Message.
Operation 5e:
Based on Deployment Option 2 (see clause 8.2.4a.1 of TS 23.272), upon receipt of a Cancel Location Request the old MSC sends an Alert Service Center message to the SMS-GMSC with an indication that the MS has moved to another serving node, to trigger the immediate retransmission of the Short Message towards the new serving node. Upon mobility to a new MME without MSC change (for SMS over SGs), the MSC sends an Alert Service Center message to the SMS-GMSC with an indication that the MS is available for MT SMS to trigger the immediate retransmission of the Short Message to the MSC.
Upon receipt of a Cancel Location Request, Context Acknowledge or Forward Relocation Response, the old SGSN or MME sends an Alert Service Center message to the SMS-GMSC, with an indication that the MS has moved to another serving node, and with the new serving node's address if received at step 5d, to trigger the immediate retransmission of the Short Message towards the new serving node.
Operation 6a:
If the Alert Service Center message indicates that that the MS has moved to another serving node but the message does not contain the new serving node's address, the SMS-GMSC retrieves the new serving node's address from the HLR or HSS.
Operation 6c:
the SMS-GMSC retransmits the Short Message immediately towards the new serving node.
Up

Up   Top   ToC