MT-SMS routing to the primary member

There are two alternative methods to route SMS to the primary member: 1. an internal method which is not visible to MAP level

2. SMS forwarding mechanism ofFeature 626: GSM Supplementary Services Phase 2 Extensions

The SMS Forwarding mechanism requires thatFeature 626: GSM Supplementary Services Phase 2 Extensions is in use. If that feature is not in use, then the internal method is the only possibility. In the internal method, the Message Waiting Data (MWD ) is stored into the group subscriber data. A new flag: Mobile Not Reachable Multi (MNRM) is stored into the primary member data to indicate that there is MWD in the group subscriber data. In the SMS Forwarding mechanism, the group subscriber in MultiSIM service uses the MSISDN of the primary member in the same way as c-number of SMS Call Forwarding Unconditional (CFU). The functionality of the primary member is exactly the same as the functionality of C-subscriber in case of SMS CFU. MWD is stored into both the group subscriber and primary member data.

1.20

Short message charging

It is possible to collect charging data for both the MT-SMS and MO-SMS in the VMSC , the SMS-GMSC , and the SMS-IWMSC . Traffic administration can collect SMS data in the VMSC, SMS-GMSC and SMS-IWMSC.

IfFeature 619: Short Message Service Enhancements is in use in your exchange, you can create different charging cases for different short message services. These include charging of roaming subscribers, charging based on subscriber's IMSI, charging of SMs created by applications, charging of command SMs and status reports between MS and SMSC, as well as charging of SMs to service

applications such as fax and e-mail. The different charging cases are explained below.

If charging is concentrated in the SMS-IWMSC/SMS-GMSC, the amount of CDRs generated in the VMSC can be limited.

You can use the commands of Detailed Charging Handling GT command group to control SMS-related charging. For operating instructions and descriptions refer to Charging Handling .

Charging records (CDRs)

The SMS-related CDRs are the following:

. _{SMMO CDRs (for mobile-originating SMS)} . _{SMMT CDRs (for mobile-terminating SMS)} . _{SMMF CDRs (for forwarded SMS)}

. _{IN CDRs (for IN SMS)}

Operators usually charge the subscribers for short messages on the basis of the MO-SM CDRs. However, the majority of the billing information can also be obtained from the MT-SM CDR. The most important exception to this is when MO-SMs are being sent to a service application. In this case, the MO-SM CDRs are the only place to charge, since these SMs do not contain an MT-SM part, and thus no MT-SM CDR is generated. For further information, see Charging of SMs

to service applications .

In addition, the CDRs contain information such as:

. _{tariff class} . _{calling IMSI} . _{called IMSI} . _{calling VMSC number} . _{called number} . _{SMS length}

Note

If the subscriber B number is wrong, the called number field in the SMS-IWMSC is empty, while the dialled number field is filled.

. _{SMS type} . _{picture message} . _{routing category}

SM status request indication can also be included in the MO-SM CDRs, that is, you can apply different charging for mobile-originating short messages without having separate MT-SM CDRs for status reports if the subscribers wishes to receive a status report about whether their SMs were delivered to subscriber B or not.

The SMS type field contains information about whether the SM is:

. _MO-SM

. _{mobile-originating command short message}

. _MT-SM

. _{mobile-terminating status report}

. mobile-originating message status report requested . _{forwarded short message}

. _{special SM (Welcome SM, Direct SM, Trigger SM)}

The CDRs also include information on concatenated short messages and picture messages. In case of concatenated short messages, it is possible to generate CDRs only for the first SM by setting the 031:0028 PRFILE parameter on. Generating CDRs only for the first SM in a concatenated short message substantially decreases the load of both the network and the billing centre.

The routing category can be defined separately for each subscriber, and this information in the CDR can be used, for example, to distinguish between prepaid and postpaid subscribers.

The charging data record for MO-SMs has a new field dialled_digits_TON to indicate the dialled alphanumeric number type. If the dialled number is not of alphanumeric type, the value of this field is unknown. For related information, see Alphanumeric addressing of SMS-related applications .

The following fields can have alphanumeric value in the SMMO CDR:

. _{dialled_digits} . _{called_number}

The SMSC application can send MT-SM when the originating address (A number) is of alphanumeric type. The MSC/VLR supports this function and generates SMMT and SMMF CDRs.

Note

In the SMMO CDR there is a VMSC address field indicating through which VMSC the SM is sent. However, if SM rerouting takes place, note that in the SMMO CDR created in the second SMS-IWMSC this field contains the previous SMS-IWMSC address instead of the VMSC address.

For more information on CDRs in general, see CDR Field Description, Interface Specification and MSC/HLR-BC, Interface Specification. For more information on CDR improvements see the feature descriptions of Feature 619: Short Message Service Enhancements , and Feature 1043: Short Message Services GSM Phase 2+ .

Selective CDR generation in the Transit MSC (TSC)

Nowadays, the TSC (which means here the SMS-IWMSC and SMS-GMSC) generates CDRs for all the MO-/ MT-SMs. In case of SMs originating and terminating in the same PLMN, the same CDRs are generated in the visited MSC and TSC (for subscriber A and subscriber B ). You can reduce the CDR generation by using an option in the TSC (SMS-IWMSC and SMS-GMSC) by allowing CDR generation only when they are really needed, that is, for subscriber charging and/or inter-operator accounting. It means that if the optional FIFILE parameter 031:0026 TRANS_SEL_CDR_GEN is turned on, the TSC (SMS- IWMSC and SMS-GMSC) does not generate CDRs for the MO-/MT-SMs which come from or go to the same PLMN. This way you can decrease the load of both the network and the billing centre.

Note

You can control the MO-SM and MT-SM CDR generation separately with the direction parameter. This means, that by defining the SMSC address, it is possible to suppress either the MO-SM CDR generation, or the MT-SM CDR generation only, or both at the same time. This results in a decrease of load in the MSC/billing centre.

Selective CDR generation based on SMSC address

Charging Records (CDRs) can be suppressed depending on the SMSC ISDN address. You can control the MO-SM and MT-SM CDR generation with MML commands. The following table shows from which network elements the CDRs can be controlled:

Table 9. Types of CDR and network elements Type of CDR Network element from where it can be controlled

MO-SM CDR VMSC, SMS-IWMSC

MT-SM CDR VMSC, SMS-GMSC

MF-SM CDR VMSC

In connection with this functionality, a new SMSC address analysis is needed in the MSC to decide whether the MO-SM or the MT-SM CDR is barred or not. For related information, see Activating selective CDR generation in SMS .