2. Agenda
What is SFERIA?
Why SFERIA needed IN?
DHZ – concept
DHZ – implementation
DHZ in operation
Other SurePay functionalities developed for
SFERIA
Overview of IN architecture in SFERIA
3. What is SFERIA
Start-up operator in Poland
CDMA 2000 radio network
Voice (1x) and Data services (EVDO)
Postpaid subscribers
License to provide Fixed Service
4. Why SFERIA needed IN
Difficult to attract new subscribers with
traditional „fixed” terminals
Need to introduce handsets enabling VAS like
SMS, WAP and MMS
Introduce Green Zone service
Limit subscriber mobility to fulfill license
obligations
5. Why SFERIA needed IN
Solution: Nomadic Service - subscriber should
not be allowed to move during call
6. DHZ - concept
Alcatel-Lucent proposed to develop Dynamic
Home Zone:
Only limited mobility is allowed while calls are
in progress and mobility is limited to a specific
maximum number of neighbouring cells or
sectors.
Implemented using SurePay and MiHomeZone
applications
8. DHZ - concept
All calls and events are triggered to SurePay
Example of handling of a Nomadic, Green Zone
and Postpaid subscriber:
MSC triggers SurePay (including translated number
& prefix for tariff)
SurePay exercises MHZ: Green Zone and DHZ
service and arm a timer
Assuming authorized zone, SurePay checks
balance, selects tariff plan and authorizes the call
Periodically during call, SurePay/MHZ check the
position of the subscriber
SurePay/MHZ terminates call when subscriber
moves out of his DHZ
9. Mid-Call Disconnection by DHZ
Origination MSC Serving MSC SurePay MHZ
CgRAA ANLYZD
LocationAuthorize(MDN, MSID, MSCID, BILLID, SCELLID)
Green Zone Screening
DMZ initialization
Response(Allow)
anlyzd RR
OANSWER
HLR
POSREQ(Current=Yes)
HLR pages for current location
posreq(SCELLID)
DMZ logic determines
if subscriber has moved
out of allowed cells/sectors.
ODISCONNECT
odisconnect RR
CCDIR(MSCID, MDN, BILLID)
ccdir RR
LocationUpdate(MDN, SCELLID)
Response
MHZ releases corresponding
Resources
10. DHZ – implementation
DHZ works only for 1x voice calls
For SMS and MMS or EVDO Data calls – only
GZ is checked
Service is triggered independently for
Originating and Terminating party
Service can be configured to work in two ways:
When DHZ is breached, call is terminated
When DHZ is breached, call is allowed to continue,
but SurePay applies different tariff for part of call
realized outside DHZ
11. DHZ – implementation
MHZ knows whether any two cells or sectors
are next to each other
MHZ dynamically maintains subscriber’s
location through POSREQ
Maintains active cell/sectors list for each call
Determines if a subscriber’s current cell/sector
is allowed - according to SFERIA’s business
rule
Total number of cell/sector moves detected by
MHZ during call is written in the CDR at the end
of call
Count is incremented on each move, regardless
of whether the new cell/sector has been visited
before
12. DHZ – implementation
User perspective:
When subscriber leaves his DHZ, first he hears
warning tone and service allows him to go back
to his DHZ
If subscriber does not return to his DHZ in ‘n’
(configurable) seconds, then his call is
terminated (or re-rated)
Upon call termination due to DHZ violation,
system generates particular EDRs and alarms
13. DHZ – implementation
Provisioning:
Subscriber: Nomadic or not ; type of DHZ
Neighbouring sectors table:
List of all the neighbour sectors of the
Sector ‘n’
Neighbouring cells table:
List of all the neighbour cells of the Cell ‘n’
These tables are re-provisioned after
introduction of new BS or network optimization.
Interval parameter for sending Location request
(set globally or per subscriber)
14. DHZ – implementation
Values used currently in SFERIA’s network:
DHZ based on sectors
Max number of sectors in DHZ: 3
Interval for POSREQ: 30 s
Time to allow return to DHZ: 35 s
15. DHZ in operation
SFERIA experience:
In first period after service was launched we’ve seen that 1,5 % of all calls were
terminated due to DHZ and 4 % - GZ violations.
In order to meet our customers satisfaction requirements, we optimized
neighbouring table and move_out_of_home_zone timers.
In result there was a decrease in number of calls which were terminated by DHZ
and GZ service - as you can see on fallowing graph:
0
1
2
3
4
5
22 24 26 28 30 32 34 36 38 40 42
Weeks 2007
ALLCALLS[%]
Call terminated by GZ
Call terminated by DHZ
16. Other SurePay functionalities
Family VPN:
Up to 5 groups of max 10 F&F numbers
Each group can use different tariff
Subscriber can change numbers in each group via
IVR
Subscriber can change tariff for each group via IVR
Conditional OG Screening
Extension of standard screening functionality
Upon reaching his credit limit, subscriber is barred
from making calls except from calls to max 10
numbers from his OG Screening list
17. IN architecture in SFERIA
SMSC
MAS1
MAS2’
eMRS
PDSN,
AAA
Navis
Radius
MSC
HLR
BSC
MAS2
LMG
OSS
eSM
18. MAS – hardware
Current configuration
able to serve 300.000
subscribers
MAS Active/Active x2. -
4 SUN Netra440 servers
FC disk array StorEdge™
3510 for each pair of
MAS servers
Disk Array
0
1
2
3
0
1
0
1
2
3
0
1
N440
EnetSW 0/1
AU
MPDU
TermSvrs
N440
10
25
4Disk Array
0
1
2
3
0
1
0
1
2
3
0
1
N440
EnetSW 0/1
AU
MPDU
TermSvrs
N440
10
25
4 10
25
4
19. Summary
First deployment of DHZ service in the world
Project finished successfully and on time
Commercial launch in SFERIA: 15/05/07
System is stable
Plans to implement DHZ also for Data Calls
