REPORTING DB STRUCTURE

Current Reporting Sources

Database name

Database Version Schema DW Source

Information Size Hardware OS

IPKO DW (old DW)

Oracle Database 10g RAC Enterprise Edition Release 10.2.0.3.0

DWRATING schema of old billing platform

1 TB

IBM POWER5 8X2GHzRed Hat Enterprise Linux AS release 4 (Nahant Update 5)

OLDBILLING (Temp DWH)

Oracle Database 10g Enterprise Edition Release 10.2.0.1.0

DW 1 TB

Intel(R) Xeon(R) CPU E5440 @ 2.83GHz X 4

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

VCCE

Oracle Database 11g RAC Enterprise Edition Release 11.1.0.6.0

VCCE 600 GB

Intel(R) Xeon(R) CPU E5440 @ 2.83GHz X 8

Red Hat Enterprise Linux Server release 5.2 (Tikanga)

CDR MS SQL SERVER 2005 CDR Network

Element CDR's 2 TB Dual-Core AMD Opteron @ 2.2GHz X 8

MS Windows Server 2003 Enterprise x64 Edition

Data stored in DatabasesDATABASE NAME DATA TYPE

IPKO DW (old DW)

Outgoing & Incomming Traffi c; MVNO Outgoing and Incomming Traffi c in agreggated format. After Migration to New Bill ing Platform charges are not coming against events (coming with amount=0) and Outbound roamers is not coming at all! Here we have only GSM Traffi c

OLDBILLING(Temp DWH)

Traffi c for prepaid and postaid from new bil l ing platform. There are only chargable events that are coming to new platform. These are not in formated standard CDR's. Data is structured on session based, for one call you can have more than one rows instead of having one and consolidated. No incoming events are available. Tables serve for GSM, FIX and Internet Traffi c

VCCE

Customer and Subscription Information. VCCE is for customer information, contact details, service activated/deactivated on GSM, DTV, Internet & Fix.

TDB (Applicon-x)

Recharge DB. Has all type of prepaid refill information based on Service (GSM, FIX, INTERNET & DTV). Here you have all types of refills: Voucher, e-refills and ATM refills

CDR

DB is fed by mediation. Has Outgoing and Incoming events. After Migration we do not have charging information and Outbound Roamers. Here we have only GSM Traffi c

Inbound roamer info we have

Inbound roamer info we have

outbound roamer info we have

NEW System StructurePRODUCTION DB

HD RATING HD BILLING HD PREPAID

ETL

VCCE CRM

DWH_SUBSCRIPTION & DWH_SUBSCRIPTION_ACCOUNT table

TDB (Recharge DB)

TEMP DWH

TEMP DWH

DWH_SUBSCRIPTION & DWH_SUBSCRIPTION_ACCOU

NT table

PREPAID TRANSACTION table

(traffic)

POSTPAID TRANSACTIONS tables

(traffic)

Network Elements & Ericsson Multi-Mediation

SGSN

Technical db – MSSQL -

Billing db – old platform -Feed to DWH

EMM

Highdeal

GGSNSMSCMSCCCN

...AIR

SDP...

MMS

NCX IPKOFix

HP OCSAC

Volubill

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

High level overview of mediation flows

Highdeal transactions

Old System Structure

NETWORK ELEMENTS

Multi Mediation (Collection and Distribution)

FTP File CDR file copy FTP File CDR file copy

ORACLE

IPKO OLD DW

DWH - ETL

Old BILLING

MSSQL

SSIS

MSSQL CDR DB

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