ActixOne Call Trace Management Detail 25th March 2009 DRAFT
ActixOne Call Trace Management Detail 25th March 2009 DRAFT
ActixOne Call Trace Management Detail 25th March 2009 DRAFT
Solution Overview
INTRODUCTION
Always on data source Dive down into detailed project based optimization
Leverage GEO Located Call Trace / Probe data to improve network intelligence and reduce the reliance on Drive Survey data
Copyright Actix 2008. Commercial in confidence.
Engineering Management
2. Expert Engineers use individually traces and then discard results when finished. No GEO Location No data or expertise sharing.
1. Manual loading and analysis of Call Trace Data Lack of GEO Location Network configuration data needs to be found
Engineering Management
3. Web based interface provides end to end whole network view. With drill down into problem areas.
2. Engineers get shared access to traces Reuse of historical traces synchronized with network configuration Ability to integrate with other sources: Planning, Performance, Alarms, Prediction to enrich analysis. 1. Automated loading and server side processing of trace data. Automatic loading of configuration data.
Call Trace Management Built in Reports provide engineers with information on overshooting cells, missing Enabling ActixOne Features cells with poor RF neighbours,
and call analysis. Web based Smart Client technology provides zero install department wide access to Call Trace Data GEO Location module automatically geographically locates Call Trace data [2.1] Call Trace Management module provides out of the box analysis providing engineers with information on overshooting cells, missing neighbours, cells with poor RF and call analysis. ActixOne Repository enables Call Trace data to be brought together and archived in a single location. Actix One Platform automatically loads, stores and analyzes Call Trace data. Actix 2008. Commercial in confidence. Copyright
RF Analysis
Tasks
Viewpoint: Problem Investigation
Maps
Spotlight: Call Analysis Call Trace / Probe Management
Reports
Dashboard s
GEO Location
Drive
OSS
Trouble Ticket
Custome r/ Busines s
Solution Overview
KEY FEATURES
ActixOne 2.0
Early Q2-2009
ActixOne 2.1
Q3-2009 GEO Location
Beyond
Problem Investigation
Processing Node Loads into ActixOne Repository
Binned Analysis
Automated loading and analysis of GPEH files. Scripted retrieval of GPEH files from OMC
Copyright Actix 2008. Commercial in confidence.
Visualized OSS Performance, fault, configuration and trouble ticketing information alongside Call Trace statistics
Geographic location analysis of: Missing neighbours RF Issues Call Events Visualization of Sector footprint Integrated layer 3 message
Key Features
Automated Processing and Analysis Call Trace & Probe Data Automated GEO Location
GEO Location Algorithm
Centralized Data Repository Focused Call Trace Module Web Based Smart Client Interface Modular Architecture Standards Based, Open and Scalable Direct links to AXP
ActixOne Platform
DRAFT
Minimal Information
Blah
DRAFT
Accuracy
Layer 3
Radio Resource
MMR
Downlink
No
DRAFT
As Iub. (per user)
Call Control
Radio Frequen cy
As Iub (all users) As Iub (all users) As Iub (all users) As Iub (all users)
Integrated
Modular Architecture
The ActixOne platform has a modular architecture that delivers capabilities such as Drive Survey Management, support for OSS data sources and Reporting
OSS Visualization
Benchmarking
Network Acceptance
GEO Location Tech Rules Tech Rules Tech Rules Call Trace / Probe Management
Drive Survey Management
ActixOne Platform
Drive
Call Trace / Probe
OSS
Planning
Trouble Ticket
Customer / Business
APAC Customer
Drive Survey Management 100,000 Sectors with National Internal Benchmark Drives End to end network visibility in single ActixOne GUI
AXP Integration
ActixOne Web Client
ActixOne Platform
Web Services
Modules..
Web Services
DRAFT
Planning
AXP
Solution Overview
GPEH Overview
General Performance Event Handling (GPEH) function handles the management and collection of predefined events in the WCDMA RAN. There are two types of events:
Node-internal events - are events produced within the RNC, due to a specific condition, for example the detection of missing neighbours, Compressed Mode activation. Inter-node events (protocol events, layer 3 messages) - are protocol messages sent or received from UE, RBS, RNC. These being a subset of RRC, NBAP, RANAP, RNSAP protocols
Depending on what events are collected a single switch (250 sites) can generate between 6MBytes and 150MBytes every 15 minutes
HSPA Analysis HS Cell change analysis Average and Maximum HS user analysis Not defined Cell change Neighbour analysis Connection Analysis Connection replay Connection signalling visualisation RRC connection Metrics Connection Metrics Support for RRC, RAB message, if logged in the file Network Trending Periodic KPI collection of network elements using GPEH
Solution Overview
COMPETITIVE
Yes