Interkey Intelligent DPI

Traffic shaping for operators and ISPs

Traffic shaping for telecom operators: classify first, then shape by policy

Traffic shaping is the controlled treatment of traffic so that scarce capacity is shared the way the operator intends. It works only as well as the identification behind it: a shaping rule that cannot tell video from software updates or tunnelled traffic shapes the wrong flows. Interkey Intelligent DPI classifies traffic by application in real time, including encrypted traffic, without decrypting it, and supports traffic shaping as an operator-defined policy action per application, subscriber group or cell. This page answers which policy action fits which job: shaping, blocking or steering.

A Saudi product, built by Interkey

For network, capacity and policy teams at telecom operators and ISPs. Reviewed November 2026.

  • What it is:a DPI platform that classifies traffic by application and supports traffic shaping as a policy action.
  • What it does:classifies traffic in real time, applies shaping policy per application, subscriber group or cell, and reports the effect in Live View.
  • Who it is for:network, capacity and policy teams at operators and ISPs in Saudi Arabia.
  • Where it works:fixed and mobile networks, inline where policy acts on traffic, on your own infrastructure; it can operate entirely in the Kingdom.

What traffic shaping needs from a DPI platform

Shaping is the last step of a chain, and each step has a different owner. The table shows who does what.

The steps of a shaping policy and who owns each
StepWhat happensWho decides
Identify the trafficEach flow is classified by application, including encrypted and tunnelled flows.The platform classifies; you verify the result on your traffic.
Choose the ruleWhich classes, which subscriber groups or cells, and when.The operator's policy, within applicable regulation.
Apply the shapingThe policy acts on traffic in an inline deployment, deployed and adjusted in real time.The platform executes the action defined with your team in scoping.
Check the effectLive View shows trends and policy execution feedback; triggered policies are recorded as metadata.Network, policy and compliance teams.

Why classification quality decides shaping quality

A shaping rule refers to a class of traffic. If the class is wrong, the rule acts on the wrong flows, and subscribers notice it first. Identification is harder than it was: encryption removes the payload signal, and many applications share the same common ports.

Interkey Intelligent DPI classifies from flow behaviour, such as handshake structure, packet sizing and timing, and endpoint behaviour, rather than from port numbers or payload alone. An AI traffic model built into the engine core does the classification and is retrained automatically as applications change.

Before a rule shapes anything, measure detection and false-positive rates for each class it refers to, on your own traffic. See Measuring DPI classification accuracy on your traffic.

Scoping a shaping policy

  • Scope.Policies act per application, subscriber group or cell, so a rule applies where the pressure or the requirement is and leaves other traffic untouched.
  • Timing.Policies are deployed and adjusted in real time.
  • Placement.Shaping acts on traffic, so it needs an inline deployment. Out-of-band, the platform classifies and reports without sitting in the forwarding path, which is the right place to validate the classes first.
  • Report-only first.A new rule can run in report-only mode, showing which traffic it would have shaped before it changes anything.
  • Parameters.The parameters of each shaping action, and how it connects to your policy and charging architecture, are defined with your team during scoping and documented in the integration plan.

Governance for shaping rules

Shaping changes what subscribers experience, so each rule needs an owner and an audit trail.

  1. 1. Published terms.The rule matches the terms subscribers were given for their plan.

  2. 2. A policy catalogue.For each rule: the traffic classes, the scope, the action, the commercial or regulatory basis and an owner.

  3. 3. An approval route.Who signs off the move from report-only to enforcement, and on what evidence.

  4. 4. Evidence on file.Triggered-policy records and policy execution feedback, so product, care and compliance teams can answer questions about a rule.

  5. 5. Change control.Rule changes and model updates enter the live network through your change-control process.

Shaping, blocking or steering: choosing the action

A policy rule refers to a class of traffic and then does something to it. Interkey Intelligent DPI supports three actions among others: traffic shaping, blocking where your policy and applicable regulation require it, and service-chain control. They answer different jobs. Blocking removes a class of traffic that policy says should not pass. Shaping changes how a class is treated so that capacity is shared the way you intend, and the class keeps working. Service-chain control sends selected flows through the functions that act on them, in a defined order. Choose by the job, not by the tool: if the aim is to protect capacity at peak without cutting a service off, the question is about shaping; if the aim is to apply a requirement, it is about blocking; if the aim is to give a flow a function it needs, it is about steering. Each action acts on traffic only in an inline deployment, and each can first run in report-only mode.

If you are looking for how to see which applications use your links before choosing an action, read Bandwidth management for ISPs.

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. 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. 2. Out-of-band classification against verified traffic.Measure false positives as carefully as detection, for every class the rules depend on.

  3. 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 traffic shaping

Does Interkey Intelligent DPI support traffic shaping?

Yes. Traffic shaping is supported as a policy action, applied per application, subscriber group or cell. The parameters and the way it connects to your architecture are defined with your team during scoping.

Do we need an inline deployment?

For shaping, yes, because shaping acts on traffic. Out-of-band deployment gives you classification and reporting, and is the usual first phase for validating the classes a rule will refer to.

Who decides what is shaped?

You do. Rules are operator-defined, made within applicable regulation. The platform applies them and shows what each one did, and report-only mode shows the effect before a rule acts.

Can a rule apply to one plan or one cell only?

Yes. Policies act per application, subscriber group or cell.

Does it work when most traffic is encrypted?

It classifies encrypted and tunnelled flows from observable characteristics without decrypting them. Results depend on your subscriber mix, application mix and encryption share, so measure them on your own traffic.

How is it priced?

On a quote basis, depending on deployment, capacity, throughput, network placement and the capabilities in scope. There is no published price list.

Proof of concept in three phases

  1. Written acceptance criteria.Agree which 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.

Discuss a proof of concept on your network

Discuss traffic shaping on your network

Tell us which traffic classes and plans you have in mind, where policy would act, and your timeline. Our team in Riyadh replies in Arabic or English.

  1. Our engineers read your request
  2. We agree the scope of a technical session
  3. You see the product on a use case you choose

Tell us your network type (mobile, fixed, ISP), approximate traffic volume and the use case you are evaluating.

By sending this form, you agree to our Privacy Notice.