REPORTING DB STRUCTURE

Current Reporting Sources

Database name Database Version Schema DW Source Information Size Hardware OS Oracle Database 10g IPKO DW (old RAC Enterprise DW DW) Edition Release 10.2.0.3.0 Oracle Database 10g OLDBILLING Enterprise DW (Temp DWH) Edition Release 10.2.0.1.0 Oracle Database 11g RAC Enterprise VCCE Edition Release 11.1.0.6.0 MS SQL SERVER CDR 2005

RATING schema of old billing 1 TB platform IBM POWER5 8X2GHz

Red Hat Enterprise Linux AS release 4 (Nahant Update 5)

1 TB Intel(R) Xeon(R) CPU E5440 @ 2.83GHz X 4 600 GB Intel(R) Xeon(R) CPU E5440 @ 2.83GHz X 8 Network Element 2 TB Dual-Core AMD Opteron @ CDR's 2.2GHz X 8 Red Hat Enterprise Linux Server release 5.2 (Tikanga) MS Windows Server 2003 Enterprise x64 Edition Red Hat Enterprise Linux AS release 4 (Nahant Update 6)

VCCE

CDR

Data stored in Databases

DATABASE NAME DATA TYPE Outgoi ng & Incommi ng Traffi c; MVNO Outgoi ng and Incommi ng Traffi c i n agreggated format. After Mi grati on to New Bi l l i ng Pl atform charges are not comi ng agai nst events (comi ng wi th amount=0) and Outbound roamers i s not comi ng at al l ! Here we have onl y GSM Traffi c

Inbound roamer info we have

IPKO DW (ol d DW)

Traffi c for prepai d and postai d from new bi l l i ng pl atform. There are onl y chargabl e events that are comi ng to new pl atform. These are not i n OLDBILLING(Temp DWH) formated standard CDR's. Data i s structured on outbound roamer info we have sessi on based, for one cal l you can have more than one rows i nstead of havi ng one and consol i dated. No i ncomi ng events are avai l abl e. Tabl es serve for GSM, FIX and Internet Traffi c Customer and Subscri pti on Informati on. VCCE i s for customer i nformati on, contact detai l s, VCCE servi ce acti vated/deacti vated on GSM, DTV, Internet & Fi x. Recharge DB. Has al l type of prepai d refi l l i nformati on based on Servi ce (GSM, FIX, TDB (Appl i con-x) INTERNET & DTV). Here you have al l types of refi l l s: Voucher, e-refi l l s and ATM refi l l s DB i s fed by medi ati on. Has Outgoi ng and Incomi ng events. After Mi grati on we do not have CDR chargi ng i nformati on and Outbound Roamers. Inbound roamer info we have Here we have onl y GSM Traffi c

NEW System Structure

PRODUCTION DB HD RATING HD BILLING HD PREPAID TDB (Recharge DB)

ETL

VCCE CRM

DWH_SUBSCRIPTION & DWH_SUBSCRIPTION_ACCOUNT table

TEMP DWH

DWH_SUBSCRIPTION & DWH_SUBSCRIPTION_ACCOU NT table

POSTPAID TRANSACTIONS tables (traffic)

PREPAID TRANSACTION table (traffic)

TEMP DWH

Network Elements & Ericsson Multi-Mediation

High level overview of mediation flows MMS SDP ... AIR CCN ... MSC SMSC GGSN SGSN

NCX IPKOFix Technical db MSSQL HP OCSAC

Volubill

EMM

Billing db old platform Feed to DWH

Offli ne

ch a

rg e s

Highdeal transactions

Highdeal
Technical db stores all network events, interconnect data. CDRs are used for technical troubleshooting. Billing db (old platform) - Stores IPKO GSM old platform customer provisioning data - Stores CDRs (IPKO & D3) from all network elements, their primary purpose is data feed for old DWH and invoice producing for D3 Mobile. - Previously it was used for troubleshooting customer complaints through IPKO Mobile Mercury and IPKO GSM billing operations. - Stores aggregated data from CDR's for reporting purposes

Old System Structure

NETWORK ELEMENTS

Multi Mediation (Collection and Distribution)

FTP File CDR file copy

FTP File CDR file copy

ORACLE

MSSQL

Old BILLING

SSIS

DWH - ETL

MSSQL CDR DB IPKO OLD DW

Issues & Critical Problems

Data need for reporting are not in one structured Data Warehouse

(have different sources for incoming and outgoing traffic) Traffic tables copied from production are not structured. Not standardized CDR format for mobile traffic Shared storage with production databases Do not have dedicated storage for reporting, and it probably will be an

issue depending on load and retention policy that is going to be applied.

We have dedicated servers for reporting databases.

which reports we are making etc

c

Thank You