A Dynamic Telecommunications SOA platformA WSO2 and 2degrees Mobile Ltd Co-creation

by

Neeraj SatijaSoftware Development Manager

2degrees Mobile Limited, NZ

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

2degrees – WSO2 Alliance: A Brief History

DESIRED APPS/PRODUCTS/SERVICES RANGE

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.

Supplier Selection Approach

Demo briefsWith scenarios

sent to all suppliers

Demos by suppliers

Create shortlist

Technical Q&A

Createshortlist

Get proposals

Review & select

IBMOracleMuleWSO2ApacheSonicOpen

OracleMuleWSO2

2degrees – WSO2 Alliance: A Brief History

CAPABILITY MATRIX

2degrees – WSO2 Alliance: A Brief History

CAPABILITY MATRIX

2degrees – WSO2 Alliance: A Brief History

CAPABILITY MATRIX

DEVELOPING DIFFERENTIATORS – TOP UP

DEVELOPING DIFFERENTIATORS – TOP UP

11

1. Set upCustomer sets up Auto Top Up in “Your 2Degrees”. Customer registers their card, and the amount they want to top up with each time.

Systems/backend:

> IN – enables balance notification for MSISDN> @billity – stores amount> Flo2Cash – validates & stores credit card

2. Balance triggerWhen customer’s balance drops below $2.50, customer receives a text message asking whether they want top up from their credit card. A “Y” reply will trigger the payment and top up.

Systems/backend:

> IN – triggers the text message when balance goes below $2.50> Recharge gateway - sends the text message to customer and awaits reply

3. Payment / top upCustomer replies “Y” to authorise/confirm payment

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

AUTO TOP UP

DEVELOPING DIFFERENTIATORS - ATU

ME2USTEP-1 STEP-2 STEP-3 STEP-4

DEVELOPING DIFFERENTIATORS – Me2U

ARCHITECTURAL SUMMARY

CURRENTNEW Full SOA Application Stack

Architecture build as per Best Practices

Removing complexity from Apps and building it into BPS

Full Transaction monitoring

Content Switch used for clustering and load balancing

Development and Deployments streamlined (Carbon Studio)

Complex processes delivered via BPS and simple via ESB

ESB and DSS Applications

Architecture build as needed – home-grown

Limited transaction monitoring (debug logs)

Linux LVS used for clustering and load balancing

Development and Deployments manual

Complex composite services deliver Business processes via ESB proxies and sequences.

16

WSO2 BPS Integration

WSO2 BPS INTEGRATION

NEW PRODUCTION ENVIRONMENT

VISION & FUTURE INITIATIVES• Continued Focus on Innovation &

Differentiators

• Leverage full WSO2 SOA stack

• 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

• Include Social Networking, SDP and other innovative models into 2degrees SOA stack

Q & A

FEEDBACK/QUESTIONS/COMMENTS

THANK YOU!