Interkey Intelligent DPI

Telecom subscriber analytics for operators and ISPs

Telecom subscriber analytics: what DPI shows about usage by group and application

Telecom subscriber analytics from DPI answers a practical question: which applications do which groups of subscribers use, where and when? Interkey Intelligent DPI classifies traffic by application in real time, including encrypted traffic, without decrypting it, and Live View reports the result by application, subscriber group and cell. Product, capacity and policy teams use it to design plans and to check that rules do what they were approved to do. What is reported, to whom and for how long follows your data-governance rules.

A Saudi product, built by Interkey

For product, capacity, policy and regulatory-reporting teams at operators and ISPs. Reviewed November 2026.

  • What it is:usage analytics built on DPI classification, by application, subscriber group and cell.
  • What it does:shows trends in Live View and records triggered policies as metadata, for the teams that design plans and rules.
  • Who it is for:product, capacity, policy and regulatory-reporting teams at operators and ISPs.
  • Where it works:fixed and mobile networks, on your own infrastructure; it can operate entirely in the Kingdom.

What the analytics show, and who uses them

Questions asked of subscriber analytics and what the platform provides
TeamTypical questionWhat the platform provides
ProductWhich applications do the subscribers of each plan use?Application-level traffic trends, reported by subscriber group.
Capacity planningWhere and when do applications drive load?Network-level and application-level trends, with drill-down by cell.
Policy ownersIs a rule doing what it was approved to do?Policy execution feedback, and triggered policies recorded as metadata.
Regulatory reportingCan we describe traffic in the form our obligations require?A reporting layer for regulatory teams; specify the reports your obligations need during scoping.

How the analytics are produced

Everything starts with classification. Interkey Intelligent DPI identifies the application behind each flow from flow behaviour, such as handshake structure, packet sizing and timing, and endpoint behaviour, so encrypted and tunnelled traffic is counted under its application and not lost. An AI traffic model built into the engine core is retrained automatically as applications change.

Live View then provides a full-network view with drill-down to application level, trend analysis, and latency measured in seconds. See DPI traffic analytics and reporting for telecom operators for how teams use these views.

Privacy and data governance

Subscriber analytics touches subscriber data by its nature, so it is a governance decision before it is a feature. Interkey Intelligent DPI is built and offered for network governance and regulatory compliance, not for surveillance of individuals. Its output is metadata about applications, traffic volumes and triggered policies.

  • Level of detail.Each team sees data at the level it needs, starting from application classes and subscriber groups. Which views your deployment includes is defined with your team during scoping.
  • Retention and access.How long records are kept and who can query them are set by your data-governance rules and recorded in the deployment design and the contract.
  • Residency.The platform runs on your infrastructure and can operate entirely in the Kingdom. See DPI data residency.
  • Applicable law.Which laws and regulator requirements apply to your organisation is for your compliance, privacy and legal teams to determine.

Decisions the analytics support

  • Plan design.Which application classes a plan's subscribers actually use, so allowances and plan definitions follow real demand.
  • Capacity.Which applications fill your links at peak, and in which cells.
  • Policy review.Whether each rule is doing what it was approved to do, before it moves from report-only to enforcement.
  • Regulatory reporting.Describing traffic by application class in the form your obligations require.

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 telecom subscriber analytics

What can the analytics show?

Network-level and application-level traffic trends in Live View, reported by subscriber group and cell, plus policy execution feedback and triggered policies recorded as metadata.

Is it a tool for monitoring individual subscribers?

No. It is built and offered for network governance and regulatory compliance. Reports describe classes of traffic and subscriber groups, and which views your deployment includes is set with your team under your data-governance rules.

Who can see the data, and for how long is it kept?

That is set by your data-governance rules and recorded in the deployment design and the contract. The platform runs on your infrastructure and can operate entirely in the Kingdom.

Can we get reports in the form our regulator requires?

The platform includes a reporting layer for regulatory teams. Specify the reports your obligations need during scoping, so they are written into the integration plan.

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 subscriber analytics on your network

Tell us which teams need the analytics, which questions they ask, and your data-governance rules. 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.