QoE monitoring for mobile operators and ISPs
Quality of experience monitoring: see how applications perform for each group and cell
Quality of experience monitoring looks at the network the way subscribers do: not as links and nodes, but as the applications they use. Interkey Intelligent DPI classifies traffic by application in real time, including encrypted traffic, without decrypting it, and supports quality of experience monitoring per application, subscriber group and cell, shown in Live View. Network, care and product teams use it to find where an application is not performing and to check that a fix worked.
A Saudi product, built by Interkey
For network operations, customer-care and product teams at mobile operators and ISPs. Reviewed November 2026.
- What it is:monitoring of how applications perform for subscribers, built on DPI classification.
- What it does:reports experience per application, subscriber group and cell in Live View, with latency of reporting measured in seconds.
- Who it is for:network operations, care and product teams at mobile operators and ISPs.
- Where it works:mobile and fixed networks, on your own infrastructure; it can operate entirely in the Kingdom.
What quality of experience monitoring shows
| Team | Typical question | What the platform provides |
|---|---|---|
| Network operations | Which application is affected, and in which cell? | A full-network view in Live View with drill-down to application level, scoped by cell. |
| Customer care | Is the problem a subscriber's, or the network's? | Experience reported per application and subscriber group, so a pattern shows as a pattern. |
| Capacity planning | Does experience drop when load rises? | Network-level and application-level trends over time, next to traffic volumes. |
| Policy owners | Did the change we approved help? | Policy execution feedback, and a before-and-after view at application level. |
Which experience indicators your deployment reports for each application class is defined with your team during scoping and documented in the integration plan.
Why experience is measured per application
A link can look healthy while one application on it performs badly, and the reverse. Subscribers do not complain about links. They complain about video that stalls, calls that break up or pages that do not load, so monitoring has to be per application to be useful.
That requires knowing which application each flow belongs to. Encryption removes the payload signal and many applications share the same common ports, so Interkey Intelligent DPI classifies from flow behaviour, such as handshake structure, packet sizing and timing, and endpoint behaviour. An AI traffic model built into the engine core is retrained automatically as applications change. Measure detection and false-positive rates for the applications you will monitor, on your own traffic. See Measuring DPI classification accuracy on your traffic.
From monitoring to action
- Find.Live View shows where an application's experience is poor, by application, subscriber group and cell.
- Decide.Capacity, network and policy teams agree the response. For congestion by application, see Mobile network congestion by application.
- Act.Policies act per application, subscriber group or cell, deployed and adjusted in real time. A policy acts on traffic only in an inline deployment.
- Check.Policy execution feedback and Live View trends show whether the change helped, and the results feed back into the models and policies.
Monitoring works out-of-band, without sitting in the forwarding path, so it can start before any inline decision is made. The reports describe classes of traffic and subscriber groups. The platform is built for network governance and regulatory compliance, not for monitoring individuals.
Governance for experience data
- Who sees what.Each team sees data at the level it needs, starting from application classes and subscriber groups.
- Retention and access.How long records are kept and who can query them follow your data-governance rules and the contract.
- Residency.The platform runs on your infrastructure and can operate entirely in the Kingdom.
- Change control.Rule changes and model updates enter the live network through your change-control process.
What to bring to a first scoping meeting
- Your network points.Which parts of the network are covered in the first phase: fixed, mobile or both.
- Your architecture.The policy and charging architecture, the enforcement points, and the reporting and security systems that results must reach.
- Your data rules.Retention, access, and whether everything must stay in the Kingdom.
- Your timeline.Whether you start out-of-band, and when an inline decision is due.
Test it on your network in 3 stages
1. Written acceptance criteria.Agree which classes and rules are tested, on which traffic and subscriber groups, how results are measured and what counts as a pass.
2. Out-of-band classification against verified traffic.Measure false positives as carefully as detection, for every class the rules depend on.
3. Report-only policy, then the inline decision.Each rule shows what it would have done; enforcement follows only after classification has proven itself.
Questions about quality of experience monitoring
Does Interkey Intelligent DPI support quality of experience monitoring?
Can we start without changing our network?
Is it a tool for monitoring individual subscribers?
How quickly do the reports update?
Does it work when most traffic is encrypted?
How is it priced?
Proof of concept in three phases
Written acceptance criteria.Agree which rules are tested, on which traffic and subscriber groups, how results are measured and what counts as a pass.
Out-of-band classification against verified traffic.Measure false positives as carefully as detection for every class the rules depend on.
Report-only policy, then the inline decision.Each rule shows what it would have done; enforcement follows only after classification has proven itself.
Discuss QoE monitoring on your network
Tell us which applications and cells matter most, which teams will use the reports, and your timeline. Our team in Riyadh replies in Arabic or English.
- Our engineers read your request
- We agree the scope of a technical session
- You see the product on a use case you choose