Short message routing based on subscriber type

If you have Feature 1598: SMS Routing Based on Subscriber Type in use, it is possible to reduce the load of the Intelligent Network (IN) platform node, by routing Short Messages (SMs) either to the Short Message Service Center (SMSC) or to the IN platform based on the subscriber type.

The following figure shows a solution for routing SMs based on the type of the subscriber:

Figure 33. Short message routing based on prepaid and post-paid subscribers SMSC address: Logical SMSC address MS Prepaid MS Post-paid SMSC address: Logical SMSC address VMSC SMSC1 SMSC2 IN platform Logical SMSC address remains GT analysis for Logical SMSC address DPC=IN platform

SMSC address is changed to virtual SMSC address as this is the input of the load sharing algorithm. Application level or SCCP level load sharing is executed between SMSC1 and SMSC2.

By splitting the SM traffic of prepaid and post-paid subscribers, it is possible to route Mobile-Originated Short Messages (MO-SMs) from the Home Public Land Mobile Network (HPLMN) to the IN platform in case of a prepaid subscriber, or directly to the SMSC in case of a post-paid subscriber.

To route SMs depending on subscriber type, it is necessary that only one logical SMSC address is used in the network, and that each subscriber is marked with the ICK (IN category key) parameter if they are prepaid or post-paid subscribers. The type of the subscriber is determined by checking the value of ICK parameter. If you use this feature, this value is shown in the Mobile-Originated Short Message Service Charging Records (SMMO CDR).

1.16

Sending SMS without SMSC

If you haveFeature 1633: Direct SM Delivery in use, it is possible to provide solution for direct SM delivery without the involvement of the Short Message Service Centre (SMSC ).

This solution provides a considerable decrease in the load of the SMSC and also the MAP or SMRSE interface between the Mobile Services Switching Centre (MSC ) and the SMSC. In case of SMRSE SMSC, the load of the Interworking MSC (IWMSC) and the Gateway MSC (GMSC ) is also reduced.

This feature is implemented in the Mobile-Originated Visited Mobile Services Switching Centre (MO-VMSC).

If subscriber B is available and subscriber A is not roaming, the MO-VMSC can directly deliver the MO-SM by converting it to an MT-SM, and forwarding it to the proper Mobile-Terminated Visited Mobile Services Switching Centre (MT- VMSC) after the Home Location Register (HLR) enquiry.

In case of any error, the MO-VMSC forwards the MO-SM to the SMSC, and SM delivery is carried out in the traditional way.

This solution also enables you to distinguish the direct SMs from normal SMs in the SMS measurement and in the Charging Data Records (CDRs).

The decision on 'Non-store and forward' SM delivery without the SMSC is made as follows:

1. The MO-VMSC receives a normal MO-SM from the subscriber. 2. The SMS application executes the IN interaction (if needed), and the

barring checking. It also checks if there is routing analysis for the B- number of the MO-SM.

Depending on whether there is routing analysis for the B-number, the SM can be handled in the following ways:

. _{If there is analysis for the application terminated SM, the MO-SM is} forwarded to the SMSC in the traditional way.

. _{If there is no analysis for the B-number of the MO-SM, the MSC} delivers the SM directly.

It is possible to check the Service Application Name (SAN) to decide if direct SM delivery should be performed, if SMS routing analysis is used in the network also for MO-MT SMs (not just for MO-AT SMs).

For more information about possible parameter setting, see the feature description ofFeature 1633: Direct SM Delivery

Direct SM delivery

When direct SM delivery is performed, the SMS application sends positive acknowledgement to the MS, which receives a 'Message sent' response. The SMS application also converts the MO-SM to an MT-SM, and starts the GMSC functionality. This means that the MSC makes the HLR enquiry and sends the Forward-SM MAP operation to the correct MT-VMSC. The MT-VMSC delivers the MT-SM in a normal way.

If the MT-SM delivery is not successful, the MT-VMSC sends back a negative acknowledgement to the MT-GMSC/MO-VMSC. The MO-VMSC then forwards the SM to the SMSC. If DIRECT_SM_FAILURE_IND parameter is activated, the MO-VMSC sets the reserved value of Transport Protocol-Message Type Indication (TP-MTI) field in the SUBMIT-MO-SM. If the SMSC supports this functionality, it can handle the SM based on this reserved value as delayed delivery, and the next delivery attempt will be based on the SMSC retry table. If DIRECT_SM_STA_CHA_INFO parameter is activated, the SMSC address of the MO-SM is changed to the operator-predefined SMSC address, which allows that the SM delivered by the MSC can be differentiated from the normal SM in the statistics reports and charging data records. When the MT-SM arrives in the MT-VMSC, the SMS application checks the SMSC address. If the SMSC address of the MT-SM is the same as stored in the HRNFIL, the MT-SM is a

The following figures illustrate the SMSC with MAP interface including the Interworking Mobile Services Switching Centre (IWMSC ) functionality. If the SMSC has SMRSE interface, the IWMSC is a separate network element, and it is not affected by this feature.

1. SUBMIT-MO-SM

2. Checking SMS routing analysis (Application-terminated SM), and converting MO-SM to MT-SM (GMSC functionality invoked) 3. SMS-SUBMIT-REPORT 4. SRI-FOR-SM 5. SRI-FOR-SM-ACK 6. MT-FORWARD-SM 7. SMS-DELIVER 8. SMS-DELIVER-REPORT

9. SMMT CDR, STATISTICS REPORT UPDATE