Telecom Performance Management System: Overview


Published on

This is an overview of the concept of Telecom Performance Management System for Tier-1 and Tier-2 operators.
The main features of this concept are:
- full coverage of all TMN model layers
- the ability for extension to full FCAPS model
- integration with any third-party systems
- distributed and fault-tolerant database model optimized for very large data volumes

Published in: Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Telecom Performance Management System: Overview

  1. 1. TelecomPerformance ManagementSystem:System Description<br />PavelLechenko<br /><br />October 2010<br />This document is licensed under CC BY.<br />
  2. 2. Operators need PM system to:<br />Predict, analyze and investigate network and service performance degradations<br />Generate and present network and service performance reports to company management<br />Forecast network and service performance in case of events (Exhibitions/Trade Shows, New Year, Olympic games) or new product launches<br />Control compliance with SLA on outsourced equipment<br />October 2010<br />2<br />TPMS: System Description<br />
  3. 3. General requirements for PM system - 1<br />Near real-time system<br />Support different data sources like performance counters, CDRs, probes, field/drive test results <br />Scalable for any volumes of input data and retention periods<br />System availability 99,999%<br />Flexible for customization and extension<br />Have open southbound and northbound interfaces<br />Support object-level and domain-level security<br />October 2010<br />3<br />TPMS: System Description<br />
  4. 4. General requirementsfor PM system - 2<br />Support multi-vendor, vendor-dependent, multi-service and service-dependent models for data and hierarchy. Support a service-network relation<br />Keep history of changes of network hierarchy, KPIs and reports<br />Support standard telecom functions and methods like Busy Hour, DAV, Erlang etc. Flexible for extension with user-defined functions.<br />Support data forecasting and profiling<br />October 2010<br />4<br />TPMS: System Description<br />
  5. 5. High-levelSystem architecture<br />As most other systems PM system contains:<br />RAW data collection and parsing layer<br />Data storage and managementlayer<br />Application layer<br />Presentation layer (User interface)<br />October 2010<br />5<br />TPMS: System Description<br />
  6. 6. RAW data collection and parsing<br />Collect data using FTP, SNMP, CORBA, X.25, SQL, custom scripts<br />Store collected data in input files<br />Unpack files (if needed)<br />Rename files to unified file name (if needed)<br />Identify corrupted files<br />Feed files to parsers<br />Store processed files (may be needed for future data re-load)<br />October 2010<br />6<br />TPMS: System Description<br />
  7. 7. RAW data collection and parsing<br />Dump files to unified format<br />Process variable file structure and contents<br />Un-peg data<br />Validate and filter data (formula-based)<br />Normalize data<br />Aggregate, accumulate and enrich data<br />Collect and report it’s own performance counters<br />October 2010<br />7<br />TPMS: System Description<br />
  8. 8. Data storage and managementlayer<br />Data warehouse based on industrial standard DBMS (Oracle or Sybase IQ) optimized for VLDB<br />Distributed data storage structure split by source (domain/technology/vendor/version) and location (region)<br />Designed for parallel processing<br />Historical class-object-relation model for all system entities<br />Scalable for network growth and regional splits/merges<br />Secure data storage<br />Flexible for customization and extension<br />Embedded programming language for data access and modification<br />October 2010<br />8<br />TPMS: System Description<br />
  9. 9. Application layer<br />Multi-threaded access to DB for parallel processing<br />Provide open integration interface (Web-services, OSS/J, SNMP)<br />Events generation<br />Data aggregation, correlation and profiling<br />Scheduled report generation<br />Store and share generated KPIs and reports<br />Threshold actions (alarms, notifications, etc.)<br />Extendable with optional modules<br />Optional clustered architecture and redundancy<br />Automatic health-check reporting<br />October 2010<br />9<br />TPMS: System Description<br />
  10. 10. Presentation layer (User interface)<br />Rich web-based user interface<br />Report and KPI designer/browser for end-users without knowledge of SQL<br />Dashboards and real-time reports<br />Ad-hoc reporting with interactivity and drill-up, drill-down and drill-same capabilities<br />Object-based and domain-based security<br />Export report results to CSV, XML, PDF, etc.<br />Provide an administrative UI for all system components<br />October 2010<br />10<br />TPMS: System Description<br />
  11. 11. System architecture in details<br />October 2010<br />11<br />TPMS: System Description<br />
  12. 12. Data Collection and Parsing<br />Collect data using FTP, SNMP, CORBA, X.25, SQL, custom scripts<br />Validate data<br />Dump, validate and filter data<br />Normalize, aggregate, accumulate and enrich data<br />October 2010<br />12<br />TPMS: System Description<br />
  13. 13. Data Loading & Validation<br />Load parsed data into the DB<br />Validate data gaps and data re-loads<br />Transform and normalize late data<br />Initiate data processing and KPI calculation mechanisms<br />October 2010<br />13<br />TPMS: System Description<br />
  14. 14. Data storage<br />Keep RAW and aggregated performance data and KPIs, network hierarchy, KPI and report templates<br />Distributed data storage structure split by source (domain/technology/vendor/version) and location (region)<br />1 data context = 1 DB instance or schema or database<br />Optimized for parallel processing<br />Designed for very large volumes of data with unstable structure<br />October 2010<br />14<br />TPMS: System Description<br />
  15. 15. Data abstraction<br />Provide access to data in different contexts for presentation layer components making the data location-independent.<br />Automatically locates requested data, builds parallelized queries and retrieves collected results.<br />Correctly retrieves data in case of context unavailability<br />October 2010<br />15<br />TPMS: System Description<br />
  16. 16. KPI engine<br />Store KPI/PI hierarchy for root-cause analysis<br />Create KPIs by template<br />Calculate KPIs as user-defined formulas or scripts (for complex KPIs)<br />Aggregate KPIs by time and hierarchy<br />Keep history of changes of KPI definitions<br />Create personal and ad-hoc KPIs<br />October 2010<br />16<br />TPMS: System Description<br />
  17. 17. Report engine<br />Store reports hierarchy<br />Create reports by template<br />Create batch reports or report chains<br />Create master-detail reports<br />Create personal and ad-hoc reports<br />Calculate reports by request, scheduler, event<br />Support time zones in calculations. Report may be calculated for local or central time zone<br />Save pre-calculated report results for review and investigation without need of recalculation<br />Save report results as XML, CSV, PDF, XLS, etc.<br />Keep history of report definition changes<br />October 2010<br />17<br />TPMS: System Description<br />
  18. 18. Inventory<br />Keep hierarchy of network elements (NE)<br />Manage a class-object model<br />Support vendor-specific and vendor-neutral hierarchies<br />Keep history of changes of network hierarchy<br />Manage virtual and logical network elements and groups (like region or data-center)<br />Automatically discover network elements<br />Group NEs by properties (like number of ports)<br />October 2010<br />18<br />TPMS: System Description<br />
  19. 19. Security engine<br />Manage users, roles and domains<br />Allow user access to the system functions or objects (NEs, KPIs, Reports)<br />Provide a Single-Sign-On to the system<br />Can be integrated with LDAP, AD, RADIUS, etc. for user authentication and authorization<br />Log all user activities<br />October 2010<br />19<br />TPMS: System Description<br />
  20. 20. Alarm engine<br />Automatically calculate KPI thresholds with minimal latency<br />Send threshold alarms to Fault/Event Management Systems<br />Alarms with conditions (alarm is raised in case of 2 or more threshold crosses during 1 hour)<br />Threshold zones for different alarm severities<br />Time-dependent thresholds<br />Automatically clear the alarm in FM system in case of return to normal operation<br />October 2010<br />20<br />TPMS: System Description<br />
  21. 21. System administration<br />System is managed from a single user interface as well as from the command line<br />Allow system administrator to manage:<br />Contexts<br />System security<br />Data in DB<br />System components<br />October 2010<br />21<br />TPMS: System Description<br />
  22. 22. High-level roadmap<br />October 2010<br />22<br />TPMS: System Description<br />
  23. 23. First steps<br />As a first step the Performance Monitoring core functions shall be done:<br />Data Collection and Parsing,<br />Data aggregation and normalization,<br />KPI engine,<br />Reporting (tables and charts)<br />Components to be done first:<br />DB,<br />Report viewer,<br />Report designer,<br />KPI editor,<br />Inventory, <br />Scheduler, <br />User GUI<br />October 2010<br />23<br />TPMS: System Description<br />
  24. 24. Next steps<br />Following Performance Management functions and components shall be added later:<br />GIS, <br />Alarm engine, <br />Northbound interface, <br />Administration GUI,<br />Collection and parsing visual designer,<br />OLAP, <br />Profiler, <br />Decision Support System, <br />Forecast (What-If),<br />Root-cause analysis<br />October 2010<br />24<br />TPMS: System Description<br />
  25. 25. Thank you.<br />October 2010<br />25<br />TPMS: System Description<br />PavelLechenko<br /><br />October 2010<br />This document is licensed under CC BY.<br />