1. A Dynamic Telecommunications SOA platform
A WSO2 and 2degrees Mobile Ltd Co-creation
by
Neeraj Satija
Software Development Manager
2degrees Mobile Limited, NZ

2. 2degrees – WSO2 Alliance: A Brief History
• Wireless Telco Landscape in NZ in 2007-2008
• Duopoly – Exorbitant prices and stale products
• No motivation for innovation
• High barrier to entry
• 2degrees Mobile Limited
• Set-up in 2007
• IT Team set-up in 2008
• Launch in 18 months
• Team of 5 people in IT, 2 focussed on SOA

3. 2degrees – WSO2 Alliance: A Brief History
DESIRED APPS/PRODUCTS/SERVICES RANGE

4. 2degrees – WSO2 Alliance: A Brief History
• 2degrees IT Requirements
• Disruptive Innovation - Differentiators
• Complex workflows, Simple Interface
• Leverage web-service technology
• Flexible, configurable integration with Network
Elements
• Rapid response to competition
• Robust, scalable, reliable technology
• Decision to adopt SOA and light, flexible, scalable
technology stack –Web services, ESB, N.E.

5. Supplier Selection Approach
Review &
select
Get
proposals
Create
shortlist
Technical
Q&A
Create
shortlist Oracle
Mule
Demos by WSO2
suppliers
Demo briefs IBM
Oracle
With scenarios Mule
sent to all suppliers WSO2
Apache
Sonic
Open

6. 2degrees – WSO2 Alliance: A Brief History
CAPABILITY MATRIX

7. 2degrees – WSO2 Alliance: A Brief History
CAPABILITY MATRIX

8. 2degrees – WSO2 Alliance: A Brief History
CAPABILITY MATRIX

9. DEVELOPING DIFFERENTIATORS – TOP UP

10. DEVELOPING DIFFERENTIATORS – TOP UP

11. AUTO TOP UP
1. Set up
Customer sets up Auto Top Up
in “Your 2Degrees”. Customer
registers their card, and the 2. Balance trigger
amount they want to top up When customer’s balance drops
with each time. below $2.50, customer receives a
text message asking whether they
Systems/backend: want top up from their credit card. A
“Y” reply will trigger the payment
> IN – enables balance notification for MSISDN
> @billity – stores amount and top up.
> Flo2Cash – validates & stores credit card
Systems/backend:
3. Payment / top up > IN – triggers the text message when balance goes
below $2.50
Customer replies “Y” to > Recharge gateway - sends the text message to
authorise/confirm payment customer and awaits reply
Systems/backend:
> Recharge gateway - “looks up” customer’s amount from @billity
> Recharge gateway – requests Flo2Cash to process $X payment
against e-token
> Recharge gateway (on confirmation from Flo2Cash of successful
payment) – processes top up and sends standard top up confirmation
messages
1

12. DEVELOPING DIFFERENTIATORS - ATU

13. ME2U
STEP-1 STEP-2 STEP-3 STEP-4

14. DEVELOPING DIFFERENTIATORS – Me2U

15. DEVELOPING DIFFERENTIATORS – FB TOP UP

16. DEVELOPING DIFFERENTIATORS – ONLINE
POSTPAY CONVERSION

17. ARCHITECTURAL SUMMARY
CURRENT NEW
ESB and DSS Applications Full SOA Application Stack
Architecture build as needed – home- Architecture build as per Best Practices
grown
Removing complexity from Apps and
Limited transaction monitoring building it into BPS
(debug logs)
Full Transaction monitoring
Linux LVS used for clustering and
load balancing Content Switch used for clustering and
load balancing
Development and Deployments
manual Development and Deployments
streamlined (Carbon Studio)
Complex composite services deliver
Business processes via ESB proxies Complex processes delivered via BPS and
and sequences. simple via ESB

18. WSO2 BPS INTEGRATION OVERVIEW
18

19. WSO2 BPS INTEGRATION – A SAMPLE FLOW

20. NEW PRODUCTION ENVIRONMENT

21. VISION & FUTURE INITIATIVES
• Continued Focus on Innovation & Differentiators
• Offer comprehensive customer lifecycle through
Online channels
• Create Web Service wrappers for all key Telco
Systems/Network Elements to enable flexibility in
design using the SOA paradigm
• Utilize smart technology to give rapid response to
competition
• Increased portfolio of services offered through Social
Networking tools
• Facilitate innovative models like SDP and external
partner collaboration and shape the 2degrees SOA
stack accordingly

22. Q&A
FEEDBACK/QUESTIONS/COMMENTS
THANK YOU!