Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.142  Word version:  16.0.0

Top   Top   Up   Prev   None
1…   7…

 

7  VAS-SMS signalling procedureWord‑p. 10

7.0  General Signalling Procedure

7.0.1  Originating Signalling flows

(not reproduced yet)
Figure 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.
(not reproduced yet)
Figure 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 flowsWord‑p. 12

(not reproduced yet)
Figure 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.
(not reproduced yet)
Figure 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

7.1  Short Message forwardingWord‑p. 14

The short message forwarding shall be a service feature only active for terminating user. The signaling procedure in originating side network shall not be affected for whether the message forwarding is active or not.
The figures in this section describe the following possible scenarios when short message forwarding is active:
  • a short message is forwarded to an address which is specified by terminating user other than called number.
  • a short message is not forwarded subject to terminating user's configuration
(not reproduced yet)
Figure 7.1-1: Terminating signaling flow - Short Message is forwarded
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 forwarding 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 the message needs to be forwarded to MS C. 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 forwarding service and do not go to following steps.
Step 6-10.
The VAS AS B delivers the original short message to the MS C after including a loop prevention indication.
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.
(not reproduced yet)
Figure 7.1-2: Terminating signaling flow - Short Message is not forwarded
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 forwarding 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 the message needs not to be forwarded.
Step 6-10.
The VAS AS B delivers the original short message to the terminating user. See general flow described in the previous clause 7.0.
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

7.2  Short Message forwarding multiple subscriptionsWord‑p. 15

Short Message Forwarding Multiple Subscriptions is applicable for the terminating user. In this case, the VAS AS checks that the terminating user has activated the Short Message Forwarding Multiple Subscriptions service and shall send the original short message to multiple receivers based on the subscription information. The procedure of Short Message Forwarding Multiple Subscriptions described in the following Figure 7.2-1.
(not reproduced yet)
Figure 7.2-1: Short Message forwarding to multiple subscriptions procedure
Up
Step 1.-3.
The short message is transferred from the originating user to terminating sides' SMS Node B. After checking out that the terminating user has subscribed VAS, the SMS Node B interacts with the VAS AS to interrogate whether the VAS of the terminating 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 4.
The VAS AS performs the short message forwarding to multiple subscriptions service and generates new short messages based on the original short message for each subscription.
Step 5-6.
The SMS Node B receives a short message to MS-1 and sends the Submit short message response to the VAS AS B.
Step 7-8.
The SMS Node B receives a short message to MS-n and sends the Submit short message response to the VAS AS B.
Step 9-10.
The SMS node B delivers the short message to MS-1 and relay the delivery report received from MS-1 to the VAS AS. These steps can happen at any time after step 6.
Step 11-12.
The SMS node B delivers the short message to MS-n and relay the delivery report received from MS-n to the VAS AS. These steps can happen at any time after step 6. There is no sequence requirement of sending short message for SMS Node, i.e. the SMS Node can send the short message in parallel.
Step 13.
The VAS AS generates a general delivery report based on all the delivery reports it receives and sends it to SMS Node B.
Step 14.
The SMS Node B notifies the originating side of the delivery status.
Up

7.3  Short Message filteringWord‑p. 17

The short message filtering shall be a service feature only active for terminating user. The signaling procedure in originating side network shall not be affected for whether the message filtering is active or not.
The figures in this section describe the following possible scenarios when short message filtering is active:
  • a short message is filtered subject to terminating user's configuration, such as a terminating user would not like to receive the message coming from a certain user.
  • a short message is not filtered subject to terminating user's configuration.
(not reproduced yet)
Figure 7.3-1: Terminating signaling flow - Short Message is filtered
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 filtering 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 the message needs to be filtered.
Step 6.
The VAS AS B generates a report of the short message and sends it to SMS Node B. The delivery result in report is based on the configuration of user B or operator.
Step 7.
The SMS Node B notifies the originating side of the delivery status.
(not reproduced yet)
Figure 7.3-2: Terminating signaling flow - Short Message is not filtered
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 filtering 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 the message needs not to be filtered.
Step 6-10.
The VAS AS B delivers the original short message to the terminating user. See general flow described in the previous clause 7.0.
Step 12.
The VAS AS B generates a report of the short message and sends it to SMS Node B.
Step 13.
The SMS Node B notifies the originating side of the delivery status.
Up

7.4  Short Message receiptWord‑p. 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 sub-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.
(not reproduced yet)
Figure 7.4-1: Short Message receipt procedure
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 storageWord‑p. 20

The short message storage can be active to both originating and terminating user.
(not reproduced yet)
Figure 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.
(not reproduced yet)
Figure 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

7.6  Short Message to multiple destinationsWord‑p. 22

In order to support short message to multiple destinations service it is needed for one user to establish a SMS group which is identified by a unique identifier in the VAS AS firstly. The SMS Group ID shall be allocated by VAS AS uniquely and be known by all the members of the SMS group. A SMS group also can be deleted by creator. There may be many ways to manage a SMS group, i.e. create or delete or query a SMS group which is out of the scope of this specification.
When the SMS group is established, every group member can send the short message to all other members in this group by setting the destination to the unique identifier of the SMS group. The procedure of sending message to multiple destinations is described in the following Figure 7.6-1.
(not reproduced yet)
Figure 7.6-1: Short Message to multiple destinations service procedure
Up
Step 1.-3.
These steps are identical to step 1 to 3 of the general message flow described in subclause 7.0. SMS Group ID shall be included in the short message and identified by recipient address.
Step 4.
The VAS AS performs a short message to multiple destinations service and generates new short messages with the same content as the original short message.
Step 5.-14.
The VAS AS separately submits the short message to the SMS Node A with different destination address. These destinations should be all other recipients within the SMS group. There is no sequence requirement of sending short message for VAS AS, i.e. the VAS AS can send the short message in parallel. The SMS Node A receives a delivery report from each receiving MS and relays it to the VAS AS. The VAS AS generates a general delivery report based on the results of the delivery reports from each recipient.
Step 15.-16.
The general delivery report is sent from VAS AS to SMS Node A and transferred to the sending MS by SMS Node if possible.
Up

7.7  Short Message Virtual Private Network (VPN)Word‑p. 23

The originating user and the terminating user are in the same VPN and support sending messages to local numbers in the VPN. The local number may be a short number which is bound to mobile number. The mapping table with local number to mobile number shall be stored in the VAS AS. The VAS AS receiving a checking message from SMS Node checks that the originating user activating VPN service, then replace local number by terminating user's mobile number.
(not reproduced yet)
Figure 7.7-1: Short Message Virtual Private Network procedure
Up
Step 1.
The SMS Node A receives a short message to local number from MS and need ask the VAS AS to check whether the originating user has activated VAS.
Step 2.-3.
The VAS AS checks that the originating user has activated VPN service and the destination is a local number. The VAS AS indicates the SMS Node there is active originating VAS for originating user.
Step 4.
The VAS AS replaces the local number by its mobile number and continues according to the general procedure described in sub-clause 7.0 step 4 and following.
Up

7.8  Short Message auto reply

Short Message Auto Reply is a terminating VAS. The procedure of the short message auto reply refers to the general flow for VAS SMS described in the previous subclause 7.0. The VAS AS checks that the terminating user has activated the Short Message Auto Reply service and generates an auto reply short message which contents have been defined in advance, then deliver it to the originating user.
(not reproduced yet)
Figure 7.8-1: Short Message auto reply procedure
Up
Step 1.-4.
See general flow described in the previous clause 7.0. The VAS AS checks that a terminating user has activated short message auto reply service and indicates to the SMS Node B there is terminating VAS active.
Step 5.
The VAS-AS B checks a loop prevention indication within the message. If the loop prevention indication is not set, then the VAS AS B generates an auto reply short message and set the loop prevention indication within the auto reply short message to indicate a spawned message. Otherwise an auto reply short message shall not be generated. The VAS AS B stores the original short message for next delivery.
Step 6.-7.
The VAS AS B delivers a short message which is indicated as an auto reply message to the SMS Node B.
Step 8.-9.
The auto reply short message is delivered to the originating user. See TS 23.040 for details.
Step 10.
The VAS AS B receives a delivery report for auto reply message delivery.
Step 11.-17.
The VAS AS B continues to deliver the original short message to the terminating user. See general flow described in the previous clause 7.0.
Up

7.9  Short Message personal signatureWord‑p. 25

Short Message Personal Signature service is applicable for the originating user. In this case, the VAS AS checks that the originating user has activated the Short Message Personal Signature service and shall append the user's personal signature to the short message. The Short Message Personal Signature procedure refers to the general procedure for VAS SMS which described in the previous clause 7.0.
Short message personal signature should be appended in the last concatenated message for a large message need to be separated into concatenated messages.
Up

7.10  Short Message deferred delivery

Short Message Deferred Delivery service allows the user to set the short message delivery time. In this case the VAS AS checks that the originating user has activated the short message deferred delivery service. The VAS AS shall store the short message and set the timer to deferred delivery time. The short message should be sent when the timer times out. The deferred delivery time should be determined by the originating user. The service procedure refers to the general flow for VAS SMS which described in the previous clause 7.0.
Up

8  Interaction with other features

8.1  Interaction with barring services

Barring services described in TS 23.040 are prior to VAS-SMS services. Any related VAS-SMS service to Operator Determined Barring (see TS 22.041) is not applicable when Operator Determined Barring applies to the Short Message Service. For example, if an originating service for SMS is barred by ODB and a terminating service for SMS is not barred, all the related originating services for VAS-SMS service are also barred, but terminating services (e.g. SMS forwarding) for VAS-SMS are not impacted.
Up

8.2  Interaction with multiple Short Message transfer

There is no direct conflict between the VAS-SMS service and the multiple short message transfer service described in TS 23.040. VAS-SMS services shall not impact the implementation of the multiple short message transfer service when the SMS-SC indicates to the SMS-GMSC that there are more messages to send for each message waiting in the service centre.

8.3  Interaction with SMS COMPRESSION

VAS-SMS services should be applicable for the SMS COMPRESSION described in TS 23.040. If the VAS-SMS service does not support SMS COMPRESSION (for example for VAS-SMS services that modify the content of a SM), then it shall guarantee the compressed SMS message delivery as normal.

8.4  Interaction with Enhanced Messaging Service

For the enhanced messaging service described in TS 23.040, VAS-SMS services should be applicable. If the VAS-SMS service does not support the enhanced messaging service (for example for VAS-SMS services that modify the content of a SM), then it shall guarantee enhanced message delivery as normal.

8.5  Interaction with SM delivery reportWord‑p. 26

If a Short Message Receipt service is applied the SMS Node shall not send SM delivery report message to the user.

8.6  Interaction with charging

VAS-SMS services are required to produce billing of extra fee (e.g. monthly based function fee).

8.7  Interaction between VAS-SMS services

VAS-SMS services should be classified by priority and triggered according to priority order based on operator's policy.

9  Interworking with other networks

The network architecture defined for VAS SMS is based on cellular networks. TS 23.204 specifies how to deliver SMS over generic 3GPP IP access. The theory of interworking with IP based network for VAS SMS is the same as normal SMS; refers to TS 23.204.
Up

$  Change historyWord‑p. 27


Up   Top