For mobile network operators
DPI for mobile operators
For a mobile operator, deep packet inspection (DPI) answers the question that network counters cannot: which applications make up the traffic in each cell, at each hour, including encrypted traffic. Capacity plans, data plans and fair-use terms, policy decisions and regulatory reports all rest on that answer. Interkey Intelligent DPI classifies traffic in real time at carrier scale across fixed and mobile networks, applies policies per application, subscriber group or cell, and runs on the operator's own infrastructure.
A Saudi product, built by Interkey
For packet core, capacity planning, policy and regulatory teams at mobile operators. Reviewed November 2026.
- What it adds:application-level classification of mobile traffic, including encrypted and tunnelled flows, without decrypting them.
- Policy scope:per application, subscriber group or cell, so a rule applies where the congestion or the requirement actually is.
- Scale:designed for carrier traffic intake, from Tbps up to dozens of Tbps, across fixed and mobile networks.
- How to start:out-of-band first, then a proof of concept in 3 stages before anything acts on traffic.
Why mobile networks need application-level visibility
Mobile operators already measure a great deal. Radio, transport and core counters show which cells, links and nodes are loaded, and when. What they do not show is what the traffic is, and three things make that harder on a mobile network than elsewhere:
- Capacity is shared per cell.Everyone in a cell shares its capacity, so one class of traffic at the busy hour affects every subscriber in that cell.
- Most traffic is encrypted.Payload patterns are hidden, and many applications share the same common ports, so neither says much about which application a flow belongs to.
- Applications keep changing.Updates change how applications behave on the network, and some applications disguise their traffic as other services.
Interkey Intelligent DPI classifies from flow behaviour (handshake structure, packet sizing and timing, and endpoint behaviour) rather than from port numbers or payload alone. Its AI traffic model is built into the engine core: it extracts features from live traffic automatically and is retrained automatically, so classification keeps up as applications change.
DPI for mobile operators: what it does on the network
| Need | What DPI provides | Team |
|---|---|---|
| Congestion diagnosis | Which application classes fill the busy hour in a congested cell, backhaul link or core node | Network operations |
| Capacity planning | Network- and application-level traffic trends, so capacity goes where a class of traffic is growing | Capacity planning |
| Data plans and fair use | Identification of the traffic a plan or fair-use rule refers to, with policies applied per subscriber group | Policy and product |
| Cell-level policy | Policies deployed and adjusted in real time, per application, subscriber group or cell | Policy |
| Regulatory requirements | Content filtering to meet national regulatory requirements, blocking where your policy and applicable regulation require it, and a reporting layer for regulatory teams | Regulatory affairs and compliance |
| New services | Service-chain control and flexible deployment of user-plane nodes | Service and network planning |
For the congestion workflow, see Mobile network congestion: diagnose it by application. For the full policy loop, see Network traffic management for telecom operators.
Fitting DPI into the mobile core: what to settle in the design
Integration with your policy and charging architecture and your 5G core is part of the deployment design, scoped with your team. You bring your policy architecture and enforcement points to scoping, and the integration plan documents what each side provides. These are the points to settle:
| Design question | Why it matters |
|---|---|
| Which traffic the platform sees | Classification, policy and reporting cover only the traffic that reaches the platform |
| Out-of-band or inline | Out-of-band classifies and reports outside the forwarding path; inline is needed for a policy to act on traffic |
| Policy and charging integration | Decides how classification feeds your plans, fair-use rules and enforcement |
| 5G core | Scoped with your team as part of the same policy architecture |
| Enforcement actions | Which actions your deployment uses is defined during scoping and set by your policy and applicable regulation |
| Reporting | Which reports capacity and regulatory teams need, and how often |
| Data | Retention and access follow your data-governance rules and the contract |
| Throughput | Scoped per deployment, and confirmed with a load test at your busiest hour |
The architecture is cloud-based, with full-mesh interconnection between the control plane and the user plane, multi-level disaster recovery and cloud-native operations and maintenance.
Operators with fixed and mobile networks
Interkey Intelligent DPI is designed for traffic intake across fixed and mobile networks. If you run both, the deployment design sets which parts of each network the platform covers, where it sits in each, and which reports each team receives. On a fixed network, the cell is not a useful policy scope, so rules are usually written per application or subscriber group.
Subscriber data and governance
The platform's output is metadata about applications, traffic volumes and triggered policies. Policies act per application, subscriber group or cell. Retention and access are set in the deployment design and the contract, following your data-governance rules, not a vendor default. The platform runs on your own infrastructure and can operate entirely in the Kingdom, so subscriber traffic does not have to leave Saudi Arabia. More on this: DPI data residency.
Interkey's team in Riyadh handles localisation to your traffic mix, application set and reporting obligations, integration with your policy, billing, security and reporting systems, and support in Arabic and English.
Start out-of-band, then test in 3 stages
Most operators start with an out-of-band deployment, which gives capacity and reporting teams classification without placing the platform in the forwarding path. Inline deployment, which policy enforcement needs, usually follows as a second phase. See Inline vs out-of-band DPI.
1. Written acceptance criteria.What is tested, on which traffic, how it is measured and what counts as a pass, agreed before deployment.
2. Out-of-band classification against verified traffic.False positives are measured as carefully as detection. Method: Measuring DPI classification accuracy.
3. Report-only policy, then the inline decision.Rules run in report-only mode first; enforcement follows only after classification has proven itself.
See also: How Interkey runs a DPI proof of concept
Questions mobile operators ask about DPI
Does it work on 5G networks?
Can a policy apply to a single cell?
Does it decrypt subscriber traffic?
How does it connect to our policy and charging system?
Do we need an inline deployment to start?
How is it priced?
Related pages
- Mobile network congestion: diagnose it by application
- Network traffic management for telecom operators
- Network traffic classification engine
- DPI data residency
- Deep packet inspection for Saudi telecom networks
- DPI in Saudi Arabia
- Tethering detection for mobile operators
- 5G traffic management
- Fair usage policy enforcement
- Policy control and PCRF
- Video optimization
- Zero rating
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 DPI for your mobile network
Tell us whether you run a mobile network only or fixed and mobile, which job comes first (congestion, plans and fair use, cell-level policy or regulatory reporting), 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