Interkey Intelligent DPI

Tethering detection for mobile operators and ISPs

Tethering detection for mobile operators in Saudi Arabia

Tethering detection means telling traffic that comes from a subscriber's own device apart from traffic that is shared onward to other devices through a hotspot. Interkey Intelligent DPI supports tethering detection as part of its application and traffic classification, and operators use the result in reports and in policies they define themselves, per subscriber group or cell. The platform is built for network governance and regulatory compliance, not for monitoring individuals. This page answers how to settle plan terms about connection sharing before a rule refers to tethered traffic.

A Saudi product, built by Interkey

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

  • What it is:identification of tethered traffic, as part of DPI traffic classification.
  • What it does:shows how much traffic is tethered and lets operator policy refer to it, per subscriber group or cell.
  • Who it is for:product, policy and network teams at mobile operators and ISPs.
  • Where it works:mobile and fixed networks, on your own infrastructure; it can operate entirely in the Kingdom.

What tethering detection does, and what it does not

Scope of tethering detection in Interkey Intelligent DPI
QuestionAnswer
What does it identify?Traffic that is shared onward from a subscriber's device to other devices, shown as a class of traffic in reports.
Does it read content?No. Traffic is not decrypted at any stage, and the output is metadata about applications, traffic volumes and triggered policies.
Does it act on its own?No. Any action is set by your policy, your plan terms and applicable regulation, and a policy acts on traffic only in an inline deployment.
Is it for monitoring individuals?No. Reports describe classes of traffic and subscriber groups, and the platform is built for network governance and regulatory compliance.

Why operators look for tethered traffic

Plans differ in how they treat shared connections, and operators need to know how much traffic that sharing creates. Without detection, reports describe the subscriber's device and miss the devices behind it, so capacity planning and plan design work from an incomplete picture.

Detection is also a matter of fairness to subscribers. A subscriber who shares a connection within the terms of their plan should not be treated as if they had broken them, so a rule that refers to tethered traffic needs to be accurate and needs a stated basis.

Using the result: reports, then policy

  • Reports.Live View shows network-level and application-level trends, and traffic can be reported by subscriber group, so product and capacity teams see how much traffic is tethered.
  • Policy scope.Policies act per application, subscriber group or cell, so a rule can apply to one plan's subscribers and leave others untouched.
  • Placement.Reporting works out-of-band. A policy acts on traffic only in an inline deployment, which operators usually add as a second phase.
  • Report-only first.A rule shows what it would have done before it acts on traffic.
  • Actions.Which actions your deployment uses is defined with your team during scoping and documented in the integration plan, together with the connection to your policy and charging architecture.

Measure it on your own traffic

Detection results depend on your subscriber mix, device mix and application mix. The mistake that matters most is the false positive: a subscriber with several of their own devices must not be counted as tethering. Measure detection and false-positive rates on your own traffic before any rule refers to tethered traffic, and check again after significant updates. The method is in Measuring DPI classification accuracy on your traffic.

Build the test from devices you control: a known device on its own, and the same device sharing its connection with others. Interkey's team in Riyadh supports the test in Arabic and English.

Governance for rules that refer to tethering

  1. 1. Published terms.The rule matches what subscribers were told about sharing their connection on their plan.

  2. 2. A policy catalogue.For each rule: the traffic classes, the subscriber group, 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. Data rules.Retention and access for the metadata follow your data-governance rules and the contract.

Plan terms to settle before a tethering rule

A rule about tethered traffic is only as clear as the plan terms behind it. Before any rule is written, product and policy teams should settle five points. First, which plans allow sharing a connection, and which do not. Second, whether sharing is allowed in full, or within an allowance, because that decides whether the rule refers to the existence of tethering or to its volume. Third, what subscribers were told, in the plan terms and at sale, because the rule has to match it. Fourth, what customer care will say to a subscriber who asks why a rule applies to them. Fifth, who approves the rule and on what evidence. Then use report-only mode to see how much traffic the rule would have covered, by subscriber group, and compare it with your expectation. A large gap usually points to an unsettled plan term, not to a detection problem.

If you are looking for fair-use allowances and rules tied to plans in general, 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 tethering detection

Does Interkey Intelligent DPI detect tethering?

Yes. Tethering detection is part of its traffic classification, and the result is available to reports and to operator-defined policies. The detection method and its accuracy on your network are confirmed with your team during scoping and measured in a proof of concept.

Can we report on it without changing our network?

Yes. Out-of-band, the platform receives a copy of traffic, classifies it and reports without sitting in the forwarding path.

Does it monitor individual subscribers?

No. It is built and offered for network governance and regulatory compliance, and its reports describe classes of traffic and subscriber groups.

Can a rule apply to one plan 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 tethering detection on your network

Tell us which plans and subscriber groups matter, what you want to report or control, 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.