Telecom Performance Management System: Overview
29 likes15,295 views
The document outlines the Telecom Performance Management System (TPMS), detailing its requirements and architecture for monitoring network and service performance. It highlights essential functionalities such as data collection, processing, KPI calculations, and reporting, along with system security and administration. The document emphasizes the need for scalability, customization, and support for various data sources while maintaining high availability and performance standards.
Telecom Performance Management System: Overview
- 1. TelecomPerformance ManagementSystem:System DescriptionPavelLechenkopavel.lechenko@hpcms.ruOctober 2010This document is licensed under CC BY.
- 2. Operators need PM system to:Predict, analyze and investigate network and service performance degradationsGenerate and present network and service performance reports to company managementForecast network and service performance in case of events (Exhibitions/Trade Shows, New Year, Olympic games) or new product launchesControl compliance with SLA on outsourced equipmentOctober 20102TPMS: System Description
- 3. General requirements for PM system - 1Near real-time systemSupport different data sources like performance counters, CDRs, probes, field/drive test results Scalable for any volumes of input data and retention periodsSystem availability 99,999%Flexible for customization and extensionHave open southbound and northbound interfacesSupport object-level and domain-level securityOctober 20103TPMS: System Description
- 4. General requirementsfor PM system - 2Support multi-vendor, vendor-dependent, multi-service and service-dependent models for data and hierarchy. Support a service-network relationKeep history of changes of network hierarchy, KPIs and reportsSupport standard telecom functions and methods like Busy Hour, DAV, Erlang etc. Flexible for extension with user-defined functions.Support data forecasting and profilingOctober 20104TPMS: System Description
- 5. High-levelSystem architectureAs most other systems PM system contains:RAW data collection and parsing layerData storage and managementlayerApplication layerPresentation layer (User interface)October 20105TPMS: System Description
- 6. RAW data collection and parsingCollect data using FTP, SNMP, CORBA, X.25, SQL, custom scriptsStore collected data in input filesUnpack files (if needed)Rename files to unified file name (if needed)Identify corrupted filesFeed files to parsersStore processed files (may be needed for future data re-load)October 20106TPMS: System Description
- 7. RAW data collection and parsingDump files to unified formatProcess variable file structure and contentsUn-peg dataValidate and filter data (formula-based)Normalize dataAggregate, accumulate and enrich dataCollect and report it’s own performance countersOctober 20107TPMS: System Description
- 8. Data storage and managementlayerData warehouse based on industrial standard DBMS (Oracle or Sybase IQ) optimized for VLDBDistributed data storage structure split by source (domain/technology/vendor/version) and location (region)Designed for parallel processingHistorical class-object-relation model for all system entitiesScalable for network growth and regional splits/mergesSecure data storageFlexible for customization and extensionEmbedded programming language for data access and modificationOctober 20108TPMS: System Description
- 9. Application layerMulti-threaded access to DB for parallel processingProvide open integration interface (Web-services, OSS/J, SNMP)Events generationData aggregation, correlation and profilingScheduled report generationStore and share generated KPIs and reportsThreshold actions (alarms, notifications, etc.)Extendable with optional modulesOptional clustered architecture and redundancyAutomatic health-check reportingOctober 20109TPMS: System Description
- 10. Presentation layer (User interface)Rich web-based user interfaceReport and KPI designer/browser for end-users without knowledge of SQLDashboards and real-time reportsAd-hoc reporting with interactivity and drill-up, drill-down and drill-same capabilitiesObject-based and domain-based securityExport report results to CSV, XML, PDF, etc.Provide an administrative UI for all system componentsOctober 201010TPMS: System Description
- 11. System architecture in detailsOctober 201011TPMS: System Description
- 12. Data Collection and ParsingCollect data using FTP, SNMP, CORBA, X.25, SQL, custom scriptsValidate dataDump, validate and filter dataNormalize, aggregate, accumulate and enrich dataOctober 201012TPMS: System Description
- 13. Data Loading & ValidationLoad parsed data into the DBValidate data gaps and data re-loadsTransform and normalize late dataInitiate data processing and KPI calculation mechanismsOctober 201013TPMS: System Description
- 14. Data storageKeep RAW and aggregated performance data and KPIs, network hierarchy, KPI and report templatesDistributed data storage structure split by source (domain/technology/vendor/version) and location (region)1 data context = 1 DB instance or schema or databaseOptimized for parallel processingDesigned for very large volumes of data with unstable structureOctober 201014TPMS: System Description
- 15. Data abstractionProvide access to data in different contexts for presentation layer components making the data location-independent.Automatically locates requested data, builds parallelized queries and retrieves collected results.Correctly retrieves data in case of context unavailabilityOctober 201015TPMS: System Description
- 16. KPI engineStore KPI/PI hierarchy for root-cause analysisCreate KPIs by templateCalculate KPIs as user-defined formulas or scripts (for complex KPIs)Aggregate KPIs by time and hierarchyKeep history of changes of KPI definitionsCreate personal and ad-hoc KPIsOctober 201016TPMS: System Description
- 17. Report engineStore reports hierarchyCreate reports by templateCreate batch reports or report chainsCreate master-detail reportsCreate personal and ad-hoc reportsCalculate reports by request, scheduler, eventSupport time zones in calculations. Report may be calculated for local or central time zoneSave pre-calculated report results for review and investigation without need of recalculationSave report results as XML, CSV, PDF, XLS, etc.Keep history of report definition changesOctober 201017TPMS: System Description
- 18. InventoryKeep hierarchy of network elements (NE)Manage a class-object modelSupport vendor-specific and vendor-neutral hierarchiesKeep history of changes of network hierarchyManage virtual and logical network elements and groups (like region or data-center)Automatically discover network elementsGroup NEs by properties (like number of ports)October 201018TPMS: System Description
- 19. Security engineManage users, roles and domainsAllow user access to the system functions or objects (NEs, KPIs, Reports)Provide a Single-Sign-On to the systemCan be integrated with LDAP, AD, RADIUS, etc. for user authentication and authorizationLog all user activitiesOctober 201019TPMS: System Description
- 20. Alarm engineAutomatically calculate KPI thresholds with minimal latencySend threshold alarms to Fault/Event Management SystemsAlarms with conditions (alarm is raised in case of 2 or more threshold crosses during 1 hour)Threshold zones for different alarm severitiesTime-dependent thresholdsAutomatically clear the alarm in FM system in case of return to normal operationOctober 201020TPMS: System Description
- 21. System administrationSystem is managed from a single user interface as well as from the command lineAllow system administrator to manage:ContextsSystem securityData in DBSystem componentsOctober 201021TPMS: System Description
- 22. High-level roadmapOctober 201022TPMS: System Description
- 23. First stepsAs a first step the Performance Monitoring core functions shall be done:Data Collection and Parsing,Data aggregation and normalization,KPI engine,Reporting (tables and charts)Components to be done first:DB,Report viewer,Report designer,KPI editor,Inventory, Scheduler, User GUIOctober 201023TPMS: System Description
- 24. Next stepsFollowing Performance Management functions and components shall be added later:GIS, Alarm engine, Northbound interface, Administration GUI,Collection and parsing visual designer,OLAP, Profiler, Decision Support System, Forecast (What-If),Root-cause analysisOctober 201024TPMS: System Description
- 25. Thank you.October 201025TPMS: System DescriptionPavelLechenkopavel.lechenko@hpcms.ruOctober 2010This document is licensed under CC BY.