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  VAS-SMS signalling procedurep. 10

7.0  General Signalling Procedurep. 10

7.0.1  Originating Signalling flowsp. 10

Copy of original 3GPP image for 3GPP TS 23.142, Fig. 7.0.1-1: General Short Message submittal procedures without active originating VAS
Up
Step 1.
MS successfully sends the short message to the SMS Node A via the originating user's serving node (e.g. MSC, SGSN, MME, SMSF, AMF). See TS 23.040 for details.
Step 2.
After checking that the originating user has subscribed VAS, the SMS Node A interacts with the VAS AS to interrogate whether the VAS of the originating user is active by sending an inquiring message including the message content received in step 1. In that case the SMS Node shall save the original short message.
Step 3.
The VAS AS indicates to the SMS Node A that there is no active originating VAS for the originating user.
Step 4.
The SMS Node A transfers the original short message to the termination side.
Step 5.
The termination side responds the delivery report to SMS Node A to notify that the short message has been delivered successfully. In this case the SMS Node A deletes the original short message which was saved in step 2.
Step 6.
The SMS Node A send the status report to the MS, which is optional depending on user's request.
Copy of original 3GPP image for 3GPP TS 23.142, Fig. 7.0.1-2: General Short Message submittal procedures with active originating VAS
Up
Step 1.
MS successfully sends the short message to the SMS Node A via the originating user's serving node (e.g. MSC, SGSN, MME, AMF, SMF). See TS 23.040 for details.
Step 2.
After checking that the originating user has subscribed VAS, the SMS Node A interacts with the VAS AS to interrogate whether originating VAS is active by sending an inquiring message including the message content received in step 1. In that case the SMS Node A shall save the original short message.
Step 3.
The VAS AS indicates to the SMS Node A that originating VAS is active.
Step 4.
The VAS AS performs originating VAS for the original user and generates a new short message by modifying the message content if necessary and submits the new short message to SMS Node A for transferring.
Step 5.
The SMS Node A sends a Submit short message response message to the Originating VAS AS.
Step 6.
The SMS Node A shall not check for VAS services for messages that are submitted by a VAS AS. The SMS Node A successfully transfer the new short message to the termination side.
Step 7.
The termination side sends the delivery status notification to SMS Node A to notify the new short message has been delivered successfully.
Step 8.
The SMS Node A transfers the delivery status notification as the VAS delivery report to the originating VAS AS.
Step 9.
The originating VAS AS generates a general delivery report based on the report which received in step 8 and sends it to the SMS Node A. The SMS Node removes the original short message which was saved in step 2 when it receives the VAS submittal report from the VAS AS.
Step 10.
The SMS Node A delivers the status report to originating MS, which is optional depending on originating user's request.
Up

7.0.2  Terminating signalling flowsp. 12

Copy of original 3GPP image for 3GPP TS 23.142, Fig. 7.0.2-1: General Short Message delivery procedures without active terminating VAS
Up
Step 1-2.
SMS Node B receives the relayed short message from the originating side and responds by sending an acknowledge message. See TS 23.040 for details.
Step 3.
After checking that the terminating user has subscribed VAS, the SMS Node B interacts with the VAS AS B to interrogate whether terminating VAS is active by sending an inquiring message including the short message content received in step 1. In that case the SMS Node B shall save the short message.
Step 4.
The VAS AS B indicates to the SMS Node B that there is no active terminating VAS for the terminating user.
Step 5-6.
The SMS Node B successfully transfers the short message to the terminating MS B and receives the Delivery Report message (see TS 23.040 for details). In this case the SMS Node B removes the short message which was saved in step 3.
Step 7.
The SMS Node B notifies the originating side of the delivery status.
Copy of original 3GPP image for 3GPP TS 23.142, Fig. 7.0.2-2: General Short Message delivery procedures with active terminating VAS
Up
Step 1-2.
SMS Node B receives the relayed short message from the originating side and responds by sending an acknowledge message. See TS 23.040 for details.
Step 3.
After checking that the terminating user has subscribed VAS, the SMS Node B interacts with the VAS AS B to interrogate whether terminating VAS is active by sending an inquiring message including the short message content received in step 1. In that case the SMS Node B shall save the short message.
Step 4.
The VAS AS B indicates to the SMS Node B that there is active terminating VAS for the terminating user.
Step 5.
The VAS AS B performs terminating VAS and generates a new short message by modifying the received short message content if necessary and submits the new short message to SMS Node B for transferring.
Step 6.
The SMS Node B sends a response message to the VAS AS B.
Step 7-8.
The SMS Node B shall not check for VAS services for messages that are submitted by a VAS AS B. The SMS Node B delivers the short message to the MS and receives the ACK messages (see TS 23.040 for details).
Step 9.
The SMS Node B transfers the delivery report to the VAS AS B.
Step 10.
The VAS AS B generates a delivery report of the short message for the originating user based on the report received in step 9 and sends to SMS Node B.
Step 11.
The SMS Node B notifies the originating side of the delivery status. In that case the SMS Node B removes the short message which was saved in step 3.
Up

Up   Top   ToC