7.6 Short Message to multiple destinations

23.1423GPPInterface and signalling flowRelease 17TSValue-added Services for SMS (VAS4SMS)

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.

Figure 7.6-1 Short Message to multiple destinations service procedure

1.-3. These steps are identical to step 1 to 3 of the general message flow described in clause 7.0. SMS Group ID shall be included in the short message and identified by recipient address.

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.

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.

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.