EAI Architecture – Vodafone India

Agenda

Application Stack

IT Network Architecture

Business Interaction Matrix

EAI Interface

EAI Technology

EAI
Advantages

Vodafone!
 • Hutchison Whampoa and MAX group establish Hutchison Max
1992

• Acquisition of Delhi operations and entry into Calcutta (now Kolkata) and Gujarat markets through Essar
Vodafone India Evolution
2000 acquisition

• Won auction for licences to operate GSM services in Karnataka, Andhra Pradesh and Chennai
2001

• Acquired AirCel Digilink (ADIL — ESSAR Subsidiary) which operated in Rajastan, Uttar Pradesh East and
2003 Haryana telecom circles and rebranded it 'Hutch'

• Launched in three additional telecom circles of India namely Punjab, Uttar Pradesh (West) and West Bengal.'
2004

• Acquired BPL Mobile operations in 3 circles. This left BPL with operations only in Mumbai, where it still
2005 operates under the brand 'Loop Mobile

• Vodafone acquires a 67% stake in Hutchison Essar for $10.7 billion. The company is renamed Vodafone Essar.
2007 'Hutch' is rebranded to 'Vodafone'.

• Vodafone acquires the licences in remaining 7 circles and has starts its pending operations in Madhya
2008 Pradesh circle, as well as in Orissa, Assam, North East and Bihar.

• Vodafone Group buys out its partner Essar from its Indian mobile phone business. It paid $5.46 billion to take
2011 Essar out of its 33% stake in the Indian subsidiary. It left Vodafone owning 74% of the Indian business.
Vodafone IT Application flow & Architecture

MIS/DWH SAP

EBPP

BSCS
cPOS • Cust admin
• Tariff config. CNCS
• Rating
CRM • Billing
• Roaming FMS
• Account Rec.
CSS IVR/ACD

Mediation

Network
 Vodafone IT Network Stack

Subscriber
IOC interface to
NPAC

SMS IVR Email

Marketing CSR Agencies WEB
GW GW GW

CTI
E CRM (Sales / OE / Service / Mkt) SELF CARE
Interactive Dialer

IPOS / EPOS / cPOS

Enterprise Application Integration

BI
(WebSphere Business Integration / MQ / Adapters)

Bill
BILLING
Formatter
FMS

INTC SERVICE
MANAGEMENT
RA (Fulfillment & Net. Resource Mgmt)
EIS MEDIATION

Reports Provisioning

Mobile Network Backbone Network

 Vodafone Business Interaction Matrix

Interface From / To Interface Type Supported Use Case Description

I-00 BSCS->SIMFile File Based Creation of SIM file to be sent to SIM Vendor
I-01 SIM FilecPOS File Upload SIM File Load
I-05 BSCS  cPOS Batch load Number Range Upload
I-10 cPOS  BSCS CMS API (Online) Customer/Contract Creation
I-20 BSCS  Comptel Prov (HLR) Online (EDIFACT) HLR Provisioning Flow
I-25 Comptel Prov (HLR)  HLR Online - Telnet based HLR Provisioning Flow
I-40 BSCS  BSCS ODS DB Replication (CDC) BSCS Replication
I-50 BSCS ODS  GDSP File based upload to GDSP via SFTP Customer/Contract Load into GDSP
I-60 GDSP  EAI Web Service based Interface with Request SIM State Change
asynchronous call back
Request Tariff Change
I-70 CRM  EAI Queue Based Async Interface Contract Termination
I-75 EAI  BSCS Queue Based Async Interface Write BSCS Operations
I-80 BSCS  CRM DB Replication (CDC) BSCS Replication to CRM
I-90 Network Elements  Mediation File Based Raw Usage (CDR) feed
I-95 Mediation  BSCS File Based Mediated Usage (CDR) feed
I-100 BSCS  EBPP File Based (TIMM Format) Bill Data
i-110 CNCS->EAI Queue Based Async Interface SR Creation for triggering Suspension/Re-Activation

6
 Vodafone EAI Interface Architecture

GDSP CRM cPOS

(Single Instance) (6 Instances) 4 Instances

I60 I70
I01
EAI
ESS
(Single Instance)
SIM File
I50

I00
i110
I75
I80

CNCS I10
RA
BSCS-ODS BSCS
I40 I05
(6 Instances) ( 23 Instances)
I95
FMS
EBPP I20
I100
(7 Instances)
Comptel Comptel
DWH/ Legal
Provisioning Mediation(Usage)
MIS
I25
I90
HLR
( 23 Instances) Network
Elements
New Interfaces

* With Amdocs Architecture would largely remain the same –

Existing Interfaces
with BSCS 23 Instances being replaced by a single Amdocs instance

7
 Vodafone EAI Technology - ESB
Enterprise Service Bus - The Next Step in EAI
• The bus architecture sought to lessen the burden of functionality placed on a single
component by distributing some of the integration tasks to other parts of the network
• The components could then be grouped in various configurations via configuration files
to handle any integration scenario in the most efficient way possible, and could be
hosted anywhere within the infrastructure, or duplicated for scalability across large
geographic regions.
• The ultimate result - lightweight, tailor-made integration solutions with guaranteed
reliability, that are fully abstracted from the application layer, follow a consistent pattern,
and can be designed and configured with minimal additional code with no modification
to the systems that need to be integrated

Core Features Advantages

Location Transparency Lightweight

Transformation Easy to expand
Protocol Conversion Scalable and Distributable
Routing SOA-Friendly
Enhancement Incremental Adoption
Monitoring / Administration
Security
 EAI Advantages
 Lower development costs
 Integration is simpler because systems are more loosely coupled

 Lower opportunity costs

 Integration is done more quickly corresponding cost savings reachieved sooner

 Lower maintenance effort

 significant advantage from the software engineering point of view

 Real time information access among systems

 Streamlines business processes and helps raise organizational efficiency

 Maintains information integrity across multiple systems

 Incorporate re-usability into your design

 XML deals effectively with platform and coding difference and reduces integration
complexity with partners
 Vodafone - Overall Result??

Increased Cost Savings

Increased Operating Profits

Integrate and Streamline

Business Processes Reduced Maintenance Efforts

Reduced Time to Markets

Real time access to Business
Intelligence
 Thank You

Happy to Answer all Queries!! 