What Makes OneVu™ Different?: S3 Metrics
What makes OneVu dramatically different from other solutions is what we call S3 metrics, meaning:
- Single source
- Synchronized time and location
- Simultaneous multi-layer processing
Single Source
From a single source, OneVu™ gives a complete end-to-end view of your customers, without having to post-process multiple disjointed metrics from scattered interfaces nor inject traffic that would add stress to your network, and distort Quality of Experience (QoE) measurements. In simple terms, OneVu™ gives a pure calculation of QoE because it utilises the subscriber’s own packets and granular metrics to determine QoE. This single source architecture, coupled with OneVu’s powerful network flow processor hardware enables superior scalability.
Legacy Approach - multiple sources
For years, USA and European mobile operators and probe vendors have pursued the legacy approach. They have attempted to correlate hundreds of disparate probes, generating non-homogenous data that must be stitched together. And to exacerbate problems, legacy solutions frequently rely on signaling data – and therefore do not reflect the customers’ actual experience found in the user plane.
Synchronized time and location across multiple layers
OneVu’s End-to-End Visibility Engine reads over 10Gbps of traffic coming from a single GGSN. As, it breaks open packets for inspection, it synchronizes and timestamps the Layer3&4 information with the Layer 7. With this tagging and time stamping, moble operators can be assured of consistency across Layer 3 and 7 metrics. Likewise, accurate Layer 2 information is extracted. Combining this Layer 2 information with operator reference data, OneVu can isolate metrics to the device, sector, cell, RNC, SGSN, GGSN, or APN. And like with time, this layer 2 location information is accurately assigned to both layers 3 through 7.
Legacy Approach – unreliable time and location
Competitors rely on different source probes for different metrics and encounter variations in timing and cell location. As a result, they cannot correctly correspond measurements for the accurate timings back to the correct cell location. Therefore, legacy KPIs represent a “best guess” result that is often highly inaccurate. Without accuracy, they cannot reliably determine root causes for problems and inform capacity planning.
Simultaneous multi-layer processing
Many DPI vendors say inspecting every user’s packets is impossible. At Velocent, we do the impossible. We have invested in cutting edge, hardware-based network processor technology. From our LexaVu End-to-End Visibility Engine, we simultaneously develop metrics for both layer 3&4 and layer 7. For every subscriber. For every PDP Context. For every Service Category. And because we avoid post processing, we can provide real-time metrics and analysis. Therefore, mobile operators can fix and manage situations as they occur.
Legacy Approach- post processing
The legacy approach involves pulling together many soures in a post processing effort that requires massive storage, complicated correlation, and is time-intensive. As data volumes increase exponentially, the post-processing solutions fall further and further behind. The result is a non-scalable, expensive-to-maintain architecture delivering unreliable metrics long after problems have come and gone.