All efforts have been made to incorporate all relevant up to date information
available, any discrepancies or need for addition or deletion is felt necessary, may
please be intimated to this office for further improvement, on E-mail Id
singhai_sc2@rediffmail.com.
1. Scope
This engineering instruction describes in brief about the prepaid service through IN platform in
GSM.
2. General
The Pre Paid Service (PPS) in GSM offers a quick and easy solution to cashless calling and
ensures the service provider and the network operator the guaranteed payment for the calls because a
service subscriber pays in advance for his calls. For a prepaid service the subscriber pays a certain amount
in advance to his prepaid account. He is subsequently able to make calls for this amount without having to
pay a (monthly) basic fee. The charging of prepaid type services is performed on-line at the SCP of the IN
platform. The calculation of the applicable tariff is based on a tariff model, which incorporates certain
parameters such as date and time, originating/terminating network operator, origination and destination (A-
party, B-party) of the call or the dialed number.
The prepaid account is simply updated each time a call is made. Prepaid accounts are of interest to
network operators and service providers for several reasons. Advance payment ensures a steady cash flow
and paper-free processing reduces administration costs to a minimum. In addition, Prepaid Service is highly
attractive to a wide target group - for example, parents looking to put an upper ceiling on the family phone
bill and travelers domiciled for a short period in a foreign country. Subscribers are offered new and safe on-
line charging methods. Vouchers can be purchased and easily used in order to recharge the account. Since
the Prepaid Service is planned to be used with low initial values, fraud and administration procedures are
kept to a minimum. Thus PPS is a lucrative business and ideally suited as a mass service.
3. ARCHITECTURE
Prepaid service in GSM is implemented by means of Intelligent Network (IN) platform. The
CAMEL (Customized Applications for Mobile Enhanced Logic) is the standard defined by ETSI to migrate
proprietary IN towards standardized GSM network solutions. The CAMEL functions are introduced in
several phases. These phases are steps towards integrating IN into a GSM PLMN/GPRS PLMN. With the
help of CAMEL, national and international roaming for IN services in a multi vendor environment has
become a reality. CAMEL standardizes communications between a Mobile SSP/VLR and the subscriber's
HLR across national borders where the HLR and M-SSP/VLR are from different vendors. The SCP, a
mandatory component of IN platform, is called CSE (CAMEL Service Environment) in GSM. The working
MSC (Mobile Switching Center) of the GSM-PLMN, or the SGSN (Serving GPRS support node) of the
GPRS-PLMN will be the M-SSP (Mobile Service Switching Point) and all other mandatory/optional
components of IN are implemented separately. However, the IP is accommodated in the M-SSP and
connected to it. Voucher management system (VOMS) maintaining database of recharge coupons is
implemented separately and is in LAN with SCP/CSE.
In this IN/CAMEL Network architecture, the following components are available for handling
IN/CAMEL services.
Fig-1
The dialed number is interpreted relative to the VPLMN, i.e. a subscriber can dial the foreign
(network) number without country code when roaming in a foreign network. The platform will add the
Country Code (CC) to the dialed number (NDC + dialed destination) as prefix depending on location
information. The location information within a tariff model or a rating module is used for individual
charging of roaming subscribers.
5.1.4.Dialed Access:
The PPS can dial from any Mobile (Post paid)/Telephone a common access number to get access
to his Prepaid account and make use of it. Call charges will be debited from his PPS account and not from
the originating Mobile/Telephone. This access is very much useful to recharge the PPS account from any
Mobile/Telephone.
For Dialed access, the subscriber has to dial the common access number. The system will prompt
to dial his account no. (The account no. is nothing but the MSISDN of the PPS). Now the Announcement
will be to enter the PIN. After entering the PIN. The PPS will be suggested to dial any destination, he
wants. For this call, the charges will be debited from the PPS account. When the system is prompting to
dial the destination, one can dial 123(DTMF MENU) and select option 2 (recharge option). Then by
entering the 14 digits secret code of the voucher purchased, the PPS account is recharged. The Personal
Identification Number (PIN) can be used for authentication and the subscriber is able to administrate his
PIN via the DTMF menu.
The system checks whether the CdPA is in international format. If so, nothing is done. If the
CdPA is in national format, the national escape code is substituted by the international escape code and the
country code.
Some of the services numbers, which need not be standardized, e.g. emergency numbers (100),
DTMF access numbers (123). These numbers are stored in a separate list. The following table gives an
overview of the different formats:
Format Numbers
National format 0 9443 124365
International format 91 9443 124365
Unknown format 0091 9443 124365 (Longest unknown format, a
complete phone number up to 20 digits)
5.2.2.Additional Announcements:
The CSE is having the facility to optionally play additional announcements to PPS during call
setup.
The first announcement needs to be defined at Provider level. Hence this announcement will be
played to all the subscribers every time during call setup. New year greetings/ marketing announcements
may be assigned.
The second announcement needs to be defined at the individual PPS level. This announcement
will be played only once on a specified day. Birthday greetings to the PPS may be played, if we maintain
PPS personal profile d/b.
5.2.3.Emergency Numbers:
The network operator can define up to 10 numbers in a list of emergency numbers. An emergency
call treatment is executed at each call setup before a subscriber is determined by the service. If the called
party is found in the list of emergency numbers, the connection is established immediately and without any
further checks. Emergency calls are always free of charge. The PPS credit balance & date criteria are not
taken into account for putting through the emergency call.
5.2.5.Call Forwarding:
This feature allows the PPS forwarding of incoming calls to another destination. Callers can be
forwarded, for example, to a mailbox or any other number. This forwarded number should be within the
HPLMN may be of Mobile/landline. Even when the PPS is on roaming the C/F can be effected to his
HPLMN numbers. The C/F is of unconditional and conditional.
I.C/F unconditional:
Case1: B party (a PPS in HPLMN) forwarded to Voicemail. No charge for B party.
Case 2: B party (a PPS in HPLMN) forwarded to Number. Facility charge + MOC leg for B party.
Case 3: B party (a PPS in VPLMN) forwarded to Voicemail. No charge for B party.
Case 4: B party (a PPS in VPLMN) forwarded to Number. Facility charge + MOC leg for B party.
I.C/F conditional: (CF BUSY, CF NR, CF Unreachable)
Case1: B party (a PPS in HPLMN) forwarded to Voicemail. No charge for B party.
Case 2: B party (a PPS in HPLMN) forwarded to Number. Facility charge + MOC leg for B party.
Case 3: B party (a PPS in VPLMN) forwarded to Voicemail. No charge for B party.
Case 4: B party (a PPS in VPLMN) forwarded to Number. Facility charge + MOC leg for B party + MTC
leg for B party.
In all the above cases, the A party only has to pay for the intended connection.
In case of a forwarded call the forwarding subscriber’s MSISDN (RedPA-the B party) is used as CgPA to
find the subscriber’s data, whereas the PPS subscriber is charged for the forwarding leg.
The B-subscriber of the CF (A->B->C) will not be charged for the MTC leg as long as he is in his
HPLMN where MTC is free. When he is in VPLMN and C/F conditional is activated, then he has to pay
for MTC leg, if any, in addition to facility charge + MOC leg.
subscriber is locked, an announcement is played and the call is released. Additionally, a fraud ticket is
written. If a subscriber is not locked call processing is continued.
5.2.9.Charge-free Numbers:
The service provider can define a list of numbers that are free of charge. When a call is set up, the
CdPA is compared with the list of charge-free numbers. If the CdPA is found in the list, the call is
connected and charging within the IN is suppressed. If the CdPA is not found in the list, call processing is
continued. Charge-free numbers cannot be selected as friends and family numbers.
5.2.14.Recharging Reminder:
This feature compares the actual account balance of a service subscriber with a threshold value. If
the actual account balance is equal or below the threshold, the service subscriber is requested to recharge
his account by an announcement. If the actual account balance is above the threshold, call processing is
continued. The account balance is updated after each call depending on the call charges.
5.2.16.Follow-on Calls:
This service feature allows the service subscriber in case of dialed access to place a follow-on call
to another destination without redialing the service access code and going through the authentication
process. The subscriber can place follow-on calls in case of B-party busy/no answer/disconnect and
network error. Follow-on calls are possible after connection to service center too, regardless of whether the
connection is established from DTMF menu or during service access. The SCP/CSE monitors the events B-
party busy/no answer, network error and disconnect B party. If one of these events occurs, an
announcement is played and the service subscriber can place a follow-on call. The number of follow-on
calls within one call execution is limited. The SCP/CSE checks this limit. If the limit is reached the call is
released after playing an announcement.
The Charge/Calculated balance (C) for that call will be computed by the following formula:
C = e4 + xe1
The SCP/CSE tariff matrix is very exhaustive for the SCP/CSE is the Charge determining point
for different A-locations. A-location being his HPLMN, for different destination numbers dialed by the
PPS subscribers the tariff needs to be defined in the SCP/CSE. Since national/international roaming can be
availed by these PPS, the M-SSP in the VPLMN contacts the parent SCP/CSE for charging purpose.
Hence, each VPLMN should be treated as A-location and with respect to that A location tariff needs to be
defined in the SCP/CSE for all the destination numbers dialed by the PPS subscribers. That is why the PPS
tariff definition in SCP/CSE is becoming huge than that of the Billing system catering for postpaid
subscribers.
tariff model is bypassed, it is only used with SINAP5m+ (proprietary). In CAP 2 implementation the
second IDP with 9D for PSTN is avoided. When the Call ticket is generated on completion of the call, we
could find a field called “PSTN component” in the CDR. While post processing the CDRs all such PSTN
component can be sorted and can be used for IUC settlement purpose.
At present, when the M-SSP at the VPLMN and the SCP/CSE at the HPLMN are from the same
vendor, then proprietary INAP is used for MTC trigger. When the M-SSP at the VPLMN and the SCP/CSE
at the HPLMN are from different vendor, then CAP-2 (Camel application part 2) is used for MTC trigger.
However care is to be taken for the balance amount in the account should not be utilized in the grace
period. That is the chargeable MTC (on roaming) is not permitted in the grace period, whereas charge free
MTC (in home area) is allowed.
5.4.3.Account Recharge:
The subscriber has to enter the SAC followed by the 14 digit secret code of the recharge coupon
with discriminators in between and a end string at the last, then press “send” button. The SCP/CSE contacts
the Voucher management (VOMS) where the d/b of the recharge vouchers is maintained, checks the
validity, updates the account balance, then a successful recharge message with updated balance is displayed
to the subscriber. The SAC is * 111 * 14 digits secret code #.
All these three USSD functions are possible whether the subscriber is in home area or on roaming.
If this number is reached, the call is released. If the subscriber selected a valid option, he is
branched to the appropriate menu option.
The PPS subscribers have to dial “123” for DTMF menu. The following figure gives an overview
of all DTMF menu options, which will be played on dialing 123.
Access to main
menu (123)
(Options)
1 2 3 4 5 6 8
Credit & exp Voucher Modify Feature Last call Call Help
date enquiry recharg account menu enquiry center
When option 1(123 – 1) is selected, the account balance and the expiry date will be fetched from
SCP/CSE and it will be played as announcement to the PPS subscriber.
When option 2 (123 – 2) is selected, the user is prompted to enter the 14 digit secret code of the
recharge coupon. It will be validated then the PPS account will be updated accordingly. The updated
balance amount after successful recharge and the new expiry date will be played as announcement to the
PPS subscriber.
When option 3 (123 – 3) is selected, the system will play the sub menus of “Modify account”.
123
Option 3
(Sub menus)
1 2 3
The sub menus of “Feature menu” will be useful when the SCP/CSE is released with additional
features like Friends & Family (FnF), Favorite area (FA), Mobile local call (MLC), and Home zone (HZI).
If such features are available & provisioned to the PPS subscribers, then it can be administrated by this
option.
When option 5(123 – 5) is selected, the Last call amount will be fetched from SCP/CSE and it will
be played as announcement to the PPS subscriber.
When option 6(123 – 6) is selected, SCP/CSE will route the call to a predefined Call Center
number.
When option 8(123 – 8) is selected, SCP/CSE will advise IP to play the entire options available
with DTMF menu in detail to the PPS subscriber.
7.0 CONCLUSION:
The PPS is attractive and the subscriber base is more than that of Postpaid. The secret lies in its
“on line charging” features, which privilege the user to monitor his usage. Though “on line charging” is
achieved for MOC/ MTC. For SMS/GPRS it is not so. Either we should go for “ off line charging” or
“messaging gateway”. We adopt “off line charging” with the help of one “Off line server”.
The Off line server will collect CDR from SMSC then send a file to the SCP/CSE to deduct the
amount from the PPS account. The pooling of CDR from SMSC and sending files to SCP/CSE will not
happen instantaneously and hence this process is called off line charging.
As for as SMS charging is concern, on line charging is achieved by CAP1 (Camel application part
1) implementation within the Zones of BSNL, where equipments are from a single vendor. Even then we
cannot dispense with the ‘off line server’. Since the PPS subscribers are with National roaming, for an
SMS, the M-SSP of another vendor cannot speck with the home SCP/CSE in any of the existing protocol.
So we seek the help of ‘off line server’ for SMS charging, for SMS made on roaming in other zones. To
conclude, SMS/GPRS on line charging will happen, when all the M-SSP & SCP/CSE in GSM of BSNL are
implemented with CAP3 (Camel application part 3) where messages similar to IDP for MOC/MTC, namely
IDP_SMS and IDP_GPRS are standardized.
THE END