Interkey Intelligent DPI

Zero rating for mobile operators and ISPs

Zero rating for telecom operators: identify exactly the traffic an offer covers

Zero rating means that traffic from chosen applications does not count against a subscriber's data allowance. It only works if the network can tell, flow by flow, which traffic belongs to the offer, and which does not. Interkey Intelligent DPI classifies traffic by application in real time, including encrypted traffic, without decrypting it, and supports zero-rating offers by identifying the qualifying traffic for your policy and charging architecture. The offer, its terms and the charging decision stay with the operator. This page answers who needs to be involved in launching a zero-rated offer, from the application list to charging.

A Saudi product, built by Interkey

For product, policy and charging teams at mobile operators and ISPs. Reviewed November 2026.

  • What it is:identification of the application traffic a zero-rated offer covers, done by DPI classification.
  • What it does:classifies each flow by application and supports zero-rating offers together with your policy and charging architecture.
  • Who it is for:product, policy and charging teams at mobile operators and ISPs.
  • Where it works:mobile and fixed networks, on your own infrastructure; it can operate entirely in the Kingdom.

Zero rating: who does what

Parts of a zero-rated offer and the role of Interkey Intelligent DPI
Part of the offerDefined byRole of Interkey Intelligent DPI
The offer and its termsThe operator, within applicable regulationNone: the platform does not set commercial terms.
Which traffic qualifiesThe operator's policy catalogueClassifies each flow by application, including encrypted flows.
Which subscribers it applies toThe operator's plans and subscriber groupsApplies policy per application, subscriber group or cell.
How the traffic is chargedYour policy and charging architectureWorks with it; the connection is defined in scoping and documented in the integration plan.
Evidence that it worksProduct, policy and compliance teamsPolicy execution feedback and triggered policies recorded as metadata.

Why zero rating depends on accurate identification

A zero-rated offer promises subscribers that a particular application is free of charge against their allowance. If classification misses part of that application's traffic, subscribers are charged for what they were told was free. If it catches traffic from another application, the operator gives away more than the offer intended. Both errors reach customer care quickly.

Identification is harder than it was: encryption removes the payload signal, and many applications share the same common ports or the same content delivery networks. 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, and its AI traffic model is retrained automatically as applications change.

Measure detection and false-positive rates for each application an offer covers, on your own traffic, before the offer launches. See Measuring DPI classification accuracy on your traffic.

Working with your policy and charging architecture

  • Division of roles.The platform identifies the qualifying traffic. Your policy and charging architecture decides how it is charged. Interkey does not replace it.
  • Scope.Policies act per application, subscriber group or cell, so an offer can apply to one plan's subscribers and leave others untouched.
  • Placement.Out-of-band, the platform classifies and reports without sitting in the forwarding path, which is the right place to check what an offer would cover. Policy acts on traffic only in an inline deployment.
  • Report-only first.A rule shows what it would have covered before it acts on traffic.
  • Integration.How the qualifying traffic is signalled to charging is defined with your team during scoping and documented in the integration plan. Bring your enforcement points to the first meeting.

For the wider picture of policy and charging, see Policy control and PCRF: how DPI works alongside your PCRF and PCF.

Governance for zero-rated offers

  1. 1. Published terms.The offer's terms match what subscribers were told, and applicable regulation.

  2. 2. A policy catalogue.For each offer: the qualifying application classes, the subscriber group, the basis and an owner.

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

  4. 4. Change control.Application lists and model updates enter the live network through your change-control process.

A zero-rated offer from idea to launch: who is involved

A zero-rated offer crosses four teams, and it stalls when one of them is missing. Product defines the offer and its terms. Policy turns the application list into rules, with the classes that qualify and the subscriber groups they apply to. The network team checks, on its own traffic, that each qualifying application is identified correctly, because a missed flow is charged to a subscriber who was told it was free. The charging team decides how the qualifying traffic is signalled to your policy and charging architecture, and that connection is defined with Interkey in scoping and written in the integration plan. Customer care joins at the end, with an answer for the subscriber who asks why an application was or was not counted. Run the offer in report-only mode first, read what it would have covered, and launch only when the network and charging teams agree on the same list.

If you are looking for fair-use allowances and rules tied to plans, read Fair usage policy enforcement for telecom operators.

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 zero rating

Does Interkey Intelligent DPI support zero rating?

Yes. It identifies the application traffic an offer covers and works with your policy and charging architecture. How the qualifying traffic is signalled to charging is defined with your team during scoping.

Who sets the offer and its terms?

The operator, within applicable regulation. The platform does not set commercial terms. It identifies traffic and applies the policies you define.

Can an offer apply to one plan only?

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

Can we check what an offer would cover before it launches?

Yes. Out-of-band, the platform classifies and reports on your own traffic, and report-only mode shows what a rule would have covered.

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 zero rating on your network

Tell us which applications and plans an offer would cover, which charging systems you run, 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.