Traffic management for operators and ISPs
Network traffic management for telecom operators
Network traffic management at operator scale is a loop: identify what the traffic is, decide what should happen to it, apply the decision and check the result. Flow counts tell you how much traffic moved; deep packet inspection (DPI) tells you what it was. Interkey Intelligent DPI classifies traffic in real time at carrier scale, applies policies per application, subscriber group or cell, and shows the outcome in Live View with latency measured in seconds. This page answers how the whole traffic management loop is organised across teams; for one action or one question, see the pages on traffic shaping and bandwidth management.
A Saudi product, built by Interkey
For capacity planning, policy and network operations teams at telecom operators and ISPs. Reviewed November 2026.
- Classification comes first:without knowing what the traffic is, congestion is diagnosed by guesswork and policies cannot be verified.
- Policy scope:per application, subscriber group or cell.
- Policy actions:real-time deployment and adjustment, service-chain control, and blocking where your policy and applicable regulation require it.
- Visibility:Live View from the network-wide view down to application and flow level, with policy execution feedback.
Why traffic management starts with classification
Most operators already know how much traffic crosses each link. What volume counters cannot say is which applications make up that traffic, so a congested cell or link gets the same answer as every other: more capacity, everywhere. With classification, capacity goes where a specific class of traffic is saturating a specific part of the network.
The same applies to commercial and regulatory rules. Fair-use rules, tiered plans and quality-of-service commitments all depend on identifying the traffic they refer to. Regulatory reporting assumes the operator can describe its own traffic.
Classification is also harder than it was. Encryption removes the payload signal, and many applications share the same common ports. Interkey Intelligent DPI classifies from flow behaviour (handshake structure, packet sizing and timing, and endpoint behaviour) rather than from port numbers or payload alone, including encrypted and tunnelled flows, without decrypting them.
The traffic management loop
| Step | The question it answers | In Interkey Intelligent DPI |
|---|---|---|
| 1. Ingest | Can the platform take in our traffic? | Designed for carrier-scale traffic across fixed and mobile networks, where volumes run from Tbps up to dozens of Tbps; throughput is sized for each deployment |
| 2. Classify | What is this traffic? | An AI traffic model built into the engine core identifies the application of each flow, including encrypted and tunnelled flows |
| 3. Act | What should happen to it? | Policies deployed and adjusted in real time, per application, subscriber group or cell; service-chain control; blocking where your policy and applicable regulation require it |
| 4. Observe | Is the policy doing what it was approved to do? | Live View: network-wide view with drill-down, trend analysis and real-time policy execution feedback |
| 5. Refine | What should change? | Live View results feed back to refine models and policies |
A refinement to a live policy is a change to a live network, so it should pass through the same approval as the original rule.
What classification supports, team by team
| Job | What classification provides | Team |
|---|---|---|
| Capacity planning | Which applications drive load, where and when, from network- and application-level trends | Capacity planning |
| Congestion | Which class of traffic is saturating which part of the network | Network operations |
| Fair use and tiered plans | Identification of the traffic a rule refers to, with policies applied per subscriber group | Policy and product |
| Quality-of-service commitments | Identification of the traffic a commitment refers to | Policy |
| Regulatory reporting | A reporting layer for regulatory teams | Regulatory affairs and compliance |
| New services | Service chaining and flexible deployment of user-plane nodes | Service and network planning |
Which enforcement actions your deployment uses, and how they connect to your policy and charging architecture and your 5G core, is defined with your team during scoping and documented in the integration plan.
Out-of-band first, enforcement second
| Out-of-band | Inline |
|---|---|
| Receives a copy of traffic; classifies and reports without sitting in the forwarding path | Sits in the forwarding path and can act on traffic |
| Gives capacity and reporting teams classification straight away | Needed for policy enforcement |
| Where most operators start | Usually a second phase, after classification has been validated |
Both run on your own infrastructure, and the platform can operate entirely in the Kingdom. The architecture is cloud-based, with full-mesh interconnection between the control and user planes and multi-level disaster recovery.
Governance controls before go-live
Traffic management changes what subscribers experience, so the rules need an owner and an audit trail. These controls sit with the operator, not the platform:
1. A policy catalogue.For each rule: the application class, the scope (application, subscriber group or cell), the action, the commercial or regulatory basis, and an owner.
2. Report-only first.Every new rule runs in report-only mode, so you see what it would have done before it acts.
3. An approval route.Who signs off the move from report-only to enforcement, and on what evidence.
4. Data rules.The platform produces metadata about applications, traffic volumes and triggered policies; retention and access follow your data-governance rules and the contract.
5. Change control.Model and policy updates enter the live network through your change-control process.
Test it on your network in 3 stages
1. Written acceptance criteria.Agree what is tested, on which traffic, how it is measured and what counts as a pass.
2. Out-of-band classification against verified traffic.Measure false positives as carefully as detection: a false positive means a rule acts on the wrong traffic.
3. Report-only policy, then the inline decision.Enforcement follows only after classification has proven itself.
See also: How Interkey runs a DPI proof of concept
Who owns which step of the loop
The traffic management loop has a different owner at each step, and most disagreements come from two teams believing the same step is theirs. Classification is owned by the network team, which answers for detection and false-positive rates on its own traffic. Policy is owned by the policy or product team, which writes each rule with its traffic classes, scope, action and basis. Approval belongs to whoever signs off the move from report-only to enforcement, and should not be the author of the rule. Operation belongs to the team that runs the inline deployment and its failover. Review belongs to the capacity and compliance teams, who read policy execution feedback against what each rule was approved to do. Write the five owners in the policy catalogue before the first rule is enforced. When a question comes up later, such as why a class was treated in a certain way, the catalogue answers who decided and on what evidence.
If you are looking for one action or one question, read Traffic shaping for telecom operators or Bandwidth management for ISPs.
Questions traffic management teams ask
Is DPI the right tool for every network?
Can a policy be tested without affecting traffic?
Do we need an inline deployment to get traffic reports?
Does it work when most traffic is encrypted?
How does it connect to our policy and charging system and 5G core?
How is it priced?
Related pages
- Encrypted traffic classification without decryption
- ISP content filtering for national requirements
- Interkey Intelligent DPI features
- Deep packet inspection for Saudi telecom networks
- Technology for telecom operators in Saudi Arabia
- Policy control PCRF: DPI alongside your PCRF and PCF
- Traffic shaping for telecom operators
- DPI for ISPs
- DPI RFP requirements
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 a DPI proof of concept
Tell us which traffic management job comes first (capacity, congestion, plans and fair use, or regulatory reporting), whether your network is fixed, mobile or both, 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