Fair usage policy for operators and ISPs
Fair usage policy enforcement for telecom operators
Enforcing a fair usage policy starts with identifying the traffic the policy refers to and the subscriber groups it applies to, then showing what each rule did. The terms themselves, such as the allowance, the conditions and the action, are the operator's commercial decision, made within applicable regulation. Interkey Intelligent DPI classifies traffic by application in real time, including encrypted traffic, without decrypting it. It applies operator-defined policies per application, subscriber group or cell, and reports policy execution in Live View.
A Saudi product, built by Interkey
For policy, product and network teams at telecom operators and ISPs. Reviewed November 2026.
- The operator sets the terms:allowances, conditions and actions are a commercial decision within applicable regulation; the platform does not set them.
- The platform identifies the traffic:each flow is classified by application, including encrypted and tunnelled flows.
- Policies are scoped to groups:per application, subscriber group or cell, deployed and adjusted in real time.
- Every rule leaves evidence:triggered policies are recorded as metadata, and Live View shows policy execution feedback.
Who defines what in a fair usage policy
| Part of the rule | Defined by | Role of Interkey Intelligent DPI |
|---|---|---|
| Plan terms and allowances | The operator, within applicable regulation | None: the platform does not set commercial terms |
| The traffic a rule refers to | The operator's policy catalogue | Classifies each flow by application, including encrypted flows |
| Who a rule applies to | The operator's plans and subscriber groups | Applies policies per subscriber group, application or cell |
| The action when a rule triggers | The operator's policy, within applicable regulation | Executes the actions available in your deployment, as defined in scoping |
| Evidence that a rule worked | Policy, product and compliance teams | Records triggered policies as metadata; shows policy execution feedback in Live View |
Why fair-use rules depend on identifying traffic
A fair-use rule that refers to a type of traffic, or treats some application classes differently from others, can only be applied as accurately as that traffic is identified. Fair-use rules, tiered plans and quality-of-service commitments all depend on identifying the traffic they refer to.
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 (handshake structure, packet sizing and timing, and endpoint behaviour) rather than from port numbers or payload alone, and it classifies encrypted and tunnelled flows without decrypting them.
A misclassified flow means a rule acts on the wrong traffic, and subscribers notice. Measure detection and false-positive rates for every class a fair-use rule depends on, on your own traffic. See Measuring DPI classification accuracy on your traffic.
Identify and report usage by policy class
Before a rule acts on anything, the platform can show what it would act on. Out-of-band, it classifies traffic and reports without sitting in the forwarding path.
| Question | What the reports show |
|---|---|
| Which application classes account for the heaviest use? | Network- and application-level trends in Live View |
| How often does each fair-use rule trigger? | Triggered policies, recorded as metadata |
| Is each rule doing what it was approved to do? | Real-time policy execution feedback |
| What do we tell product, care and compliance teams? | A reporting layer for capacity and regulatory teams, with traffic described by application class |
These reports describe classes of traffic and subscriber groups. The platform is built for network governance and regulatory compliance, not for surveillance of individuals. Its output is metadata about applications, traffic volumes and triggered policies, and retention and access follow your data-governance rules and the contract.
Applying operator-defined policies
- Scope.Policies act per application, subscriber group or cell, so a rule can apply to one plan's subscriber group and leave others untouched.
- Timing.Policies are deployed and adjusted in real time.
- Placement.A policy acts on traffic only in an inline deployment, which operators usually add as a second phase after classification has been validated.
- Report-only first.A new rule can first run in report-only mode, showing what it would have done before it acts.
- Actions.Which enforcement actions your deployment uses, and how they connect to your policy and charging architecture, is defined with your team during scoping and documented in the integration plan.
Governance for subscriber-facing rules
Fair-use rules change what subscribers experience, so each one needs an owner and an audit trail:
1. Published terms.The rule matches the terms subscribers were given for their plan.
2. A policy catalogue.For each rule: the traffic classes, the subscriber group, the condition, the action, the commercial or regulatory basis, and an owner.
3. An approval route.Who signs off the move from report-only to enforcement, and on what evidence.
4. Evidence on file.Triggered-policy records and policy execution feedback, so product, care and compliance teams can answer questions about a rule.
5. Change control.Rule changes and model updates enter the live network through your change-control process.
Test a fair-use rule in 3 stages
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.
See also: How Interkey runs a DPI proof of concept
Questions about fair usage policy enforcement
Does the platform decide fair-use allowances or terms?
Can a rule apply to one plan only?
Can we see what a rule would do before it affects subscribers?
Does it work when most traffic is encrypted?
What data does the platform keep?
How is it priced?
Related pages
- Network traffic management for telecom operators
- DPI traffic analytics and reporting for operators
- Network traffic classification engine for telecom operators
- Interkey Intelligent DPI features
- Deep packet inspection for Saudi telecom networks
- Bandwidth management for ISPs
- Traffic shaping for telecom operators
- Tethering detection for mobile operators
- Zero rating for telecom operators
- DPI for mobile operators
- DPI RFP requirements
- Policy control and PCRF
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 fair-use policy on your network
Tell us which plans or subscriber groups your fair-use rules cover, which application classes they refer to, 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