Bill Shock is a common concept in Postpaid Data roaming & very contentious for both the operator & subscriber. Whose problem is it anyway? I will try to break it down here:
GPRS can be blocked from:
1. HLR (GPRS Roaming Flag can be set to ON/OFF at Subscriber level)
2. PCRF ( PLMN's can be allowed/blocked).
When a Postpaid subscriber roams to another PLMN with GPRS Roaming Flag Allowed in HLR & PCRF has allowed the PLMN , This subscriber can easily use data for the entire duration they roam, and on return, the bill accrued can be huge as roaming is generally expensive, Some customers say, i was not aware that i was using the Service!. We'll, Who then takes the burden?
To avoid all this:
1.) Collect all your roaming Partner inter-PLMN IP addresses or SGSN MCC/MNC & Configure them as on "OR" condition in the PCRF. (Meaning if any is matched, a given set of procedures can be executed).
2.) Create a small quota in PCRF say 10MB with some usage levels to be used for notification say at Start (Welcome subscriber into roaming environment and alert them that roaming is on and expensive), 50% (Alert them on steps on how to continue using the Data Service after 100% Usage when PCRF has automatically blocked them) & 100% Usage (Telling subscriber that Data Service has been disconnected but share steps to follow in case subscriber consciously wants to use the Data Service). Ensure the GGSN monitors this volume and reports to PCRF with correct Monitoring Key & Rating Group Where applicable.
3.) Configure related Rule & Policy with event triggers like SGSN Change, PDP Context Activation, Usage Report, PLMN Change depending on your scenario.
4.) Configure a Service onto which all the related quota, policy, rules, conditions, actions & notifications are bound.
4.) Configure a dynamic subscriber group which all postpaid roaming subscribers can Match once they Turn on Data Service in the Roaming Environment. & Auto subscribe them to this 10MB service and as they use it, Send Notifications as mentioned above. Once this 10MB is exhausted, do not allow PDP to be activated until subscriber dials a USSD code to be subscribed to Unlimited Usage as the case originally in the environment which had alot of complaints & bill shocks.
With this Logic. We have only 10MB which any postpaid subscriber would be willing to pay if it was unintentional and no other subscriber can be shocked about a bill after dialing a USSD code to OPT in.
The Operator doesnot have many bad debts & Subscriber doesnot have many bill shocks.. A definite Win/Win and worth giving a try if you have such a problem!
#PerfectionIsANorm
GPRS can be blocked from:
1. HLR (GPRS Roaming Flag can be set to ON/OFF at Subscriber level)
2. PCRF ( PLMN's can be allowed/blocked).
When a Postpaid subscriber roams to another PLMN with GPRS Roaming Flag Allowed in HLR & PCRF has allowed the PLMN , This subscriber can easily use data for the entire duration they roam, and on return, the bill accrued can be huge as roaming is generally expensive, Some customers say, i was not aware that i was using the Service!. We'll, Who then takes the burden?
To avoid all this:
1.) Collect all your roaming Partner inter-PLMN IP addresses or SGSN MCC/MNC & Configure them as on "OR" condition in the PCRF. (Meaning if any is matched, a given set of procedures can be executed).
2.) Create a small quota in PCRF say 10MB with some usage levels to be used for notification say at Start (Welcome subscriber into roaming environment and alert them that roaming is on and expensive), 50% (Alert them on steps on how to continue using the Data Service after 100% Usage when PCRF has automatically blocked them) & 100% Usage (Telling subscriber that Data Service has been disconnected but share steps to follow in case subscriber consciously wants to use the Data Service). Ensure the GGSN monitors this volume and reports to PCRF with correct Monitoring Key & Rating Group Where applicable.
3.) Configure related Rule & Policy with event triggers like SGSN Change, PDP Context Activation, Usage Report, PLMN Change depending on your scenario.
4.) Configure a Service onto which all the related quota, policy, rules, conditions, actions & notifications are bound.
4.) Configure a dynamic subscriber group which all postpaid roaming subscribers can Match once they Turn on Data Service in the Roaming Environment. & Auto subscribe them to this 10MB service and as they use it, Send Notifications as mentioned above. Once this 10MB is exhausted, do not allow PDP to be activated until subscriber dials a USSD code to be subscribed to Unlimited Usage as the case originally in the environment which had alot of complaints & bill shocks.
With this Logic. We have only 10MB which any postpaid subscriber would be willing to pay if it was unintentional and no other subscriber can be shocked about a bill after dialing a USSD code to OPT in.
The Operator doesnot have many bad debts & Subscriber doesnot have many bill shocks.. A definite Win/Win and worth giving a try if you have such a problem!
#PerfectionIsANorm
Good stuff
ReplyDeleteAwesome stuff man, keep them coming.
ReplyDeleteYou can also redirect them to a free page where they can sign up for roaming services. once you detect that a customer is latched on foreign SGSN, you can create an http redirect rule to a zero rated page that informs them of their roaming status and where they want to continue and use data roaming services.
Joshua Nomwesigwa, by just thinking about it, most operators may not be ok with redirection in roaming. A customer without money or interest to actually use roaming as a service may keep online with this redirect page, because Uplink & Downlink Flux is passing through the SGSN of roaming partner, you may be charged for sessions where customer was doing nothing, i think if customer has no money, it is always ame to keep PDP off.
Delete