You are on page 1of 6


Globitel offers the BTS Module over the ITS Product to protect ZANTEL subscribers from accidental roaming that occurs around the border areas where some neighboring networks (VodaCom) may have powerful signal strength and accordingly cause ZANTEL subscribers to roam accidentally and thus bear the unnecessary roaming tariffs.


1- Depends on the operator Cell IDs on which the subscriber is latched onto and the ones that need to be blocked in the border area.

2- The salient benefits of the BTS Module is that it is transparent to the

other networks and subscribers while offering a flexible steering criteria

definition to suit the different situations, all of which will lead to no subscriber leakage occurring at the border areas and thus boost the revenue.

3- Work Flow
In brief the below steps describe the system logic: 1- MSCs was configured to route all E214 traffic coming from Vodacom network to Globitel

2- After receiving the LU message the BTS send ATI (Any Time Interrogation) message to the HLR to get the last Cell ID that the subscriber was on. 3- The ATI result contains the Cell ID either (Vodacom (if he already accepted before) or

4- The old logic will be applied only for Zantel Cells, and recently the logic was extended to apply the blacklist rule on Vodacom Cells. 5- Three groups are defined in the system for cells:

a. Blacklisted: the system will reject the LU from that subscriber until it reach the
configured limit which is defined in the Border Max Rejections parameter. b. BannededList: The system will always block (reject) the LU requests. c. Others will be considered as white list which we always accept the


B T S Action with B o r d e r C e l l

B T S action with N o n B o r d e r C e l l

Additional steps to describe the system logic

we have customized the flow to adapt the age of location, where extra check will be on the ATI result to check the age of location where: Any Age of location less than or equal x minutes will be considered as up to

date, and the logic will continue the same.

Any Age of location greater than x minutes will considered out of date and the following logic will be applied: 1.Reject the first y requests assuming that the Handset will move to another choice of network. After each LU an ATI message will be generated (regardless the time between them).
Currently the following values are defined X= AgeOfLocation= 60 Minutes Y= AgeOfLocationMaxRejection = 6 times