Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.142  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   7…   7.1…   7.4…   7.6…   8…

 

7.4  Short Message receiptp. 18

Short Message Receipt is a terminating VAS. The procedure of the short message receipt refers to the general flow for VAS SMS described in the clause 7.0.2. The VAS AS checks that the terminating user has activated the Short Message Receipt service and generates a new short message as the receipt of original message.
Copy of original 3GPP image for 3GPP TS 23.142, Fig. 7.4-1: Short Message receipt procedure
Figure 7.4-1: Short Message receipt procedure
(⇒ copy of original 3GPP image)
Up
Step 1-4.
See general flow described in the previous clause 7.0. The VAS AS B checks that a terminating user has activated short message receipt service and indicates to the SMS Node B there is terminating VAS active.
Step 5.
According to user B's preferences, the VAS AS B decides a message receipt is needed and shall be sent to user A. The VAS AS B takes a loop check for original SM. If there is a loop prevention indication set in the SM, the VAS AS B shall not apply short message receipt service and do not go to following steps.
Step 6-9.
The VAS AS B delivers the original short message to the terminating user. See general flow described in the previous clause 7.0.
Step 10.
The VAS AS B generates a receipt short message, based on the report received in step 9 and terminating user's preferences. The receipt message shall include a loop prevention indication that indicating it is a message generated for message receipt service of user B.
Step 11-14.
The VAS AS B delivers the message receipt to the originating user. See general flow described in the previous clause 7.0.
Step 15.
The VAS AS B generates a report of the short message and sends it to SMS Node B.
Step 16.
The SMS Node B notifies the originating side of the delivery status.
Up

7.5  Short Message network storagep. 20

The short message storage can be active to both originating and terminating user.
Copy of original 3GPP image for 3GPP TS 23.142, Fig. 7.5-1: Originating signaling flow - Short Message storage
Up
Step 1-3.
See general flow described in the previous clause 7.0. The VAS AS A checks that a originating user has activated short message network storage service and indicates to the SMS Node A there is originating VAS active.
Step 4.
The VAS AS A decides that the original SMS shall be stored based on originating user's preferences.
Step 5-9.
The VAS AS A delivers the original short message to the terminating user. See general flow described in the previous clause 7.0.
Step 10.
VAS AS A stores the original SMS and relevant information for originating user.
Step 11.
The VAS AS A generates a delivery report for the original short message based on the report which received in step 9 and sends to SMS Node A.
Step 12.
The SMS Node A sends the status report to UE, which is optional depending on user's request.
Copy of original 3GPP image for 3GPP TS 23.142, Fig. 7.5-2: Terminating signaling flow - Short Message storage
Up
Step 1-4.
See general flow described in the previous clause 7.0. The VAS AS B checks that a terminating user has activated short message network storage service and indicates to the SMS Node B that the terminating VAS is active.
Step 5.
The VAS AS B decides that the original SMS shall be stored based on terminating user's preferences.
Step 6-9.
The VAS AS B delivers the original short message to the terminating user. See general flow described in the previous clause 7.0.
Step 10.
The VAS AS B stores the SMS and relevant information for terminating user.
Step 11.
The VAS AS B generates a report of the short message and sends it to SMS Node B.
Step 12.
The SMS Node B notifies the originating side of the delivery status.
Up

Up   Top   ToC