Interkey Intelligent DPI

For procurement and engineering teams writing a DPI tender

DPI RFP requirements: a checklist for telecom operators

DPI RFP requirements should state what the platform must classify, where and how it will be deployed, which policy actions and reports it must deliver, how subscriber data is governed, and how bidders will prove their claims on your own traffic before award. This checklist groups the requirements into those areas, lists the evidence to ask bidders for, and ends with an acceptance clause built on a three-stage proof of concept.

A Saudi product, built by Interkey

For procurement, network engineering and regulatory-affairs teams at telecom operators and ISPs. Reviewed November 2026.

  • Describe the network first:governance jobs, network points, busy-hour volumes and deployment mode per phase.
  • Ask for evidence, not adjectives:per-class results on your traffic, load tests at your peak, and written integration plans.
  • Separate out-of-band and inline requirements:classification and reporting do not need the platform in the forwarding path; enforcement does.
  • Write the proof of concept into the RFP:acceptance criteria first, then out-of-band classification, then report-only policy before the inline decision.

Part 1: describe your network and the job

Bidders can only size and price a DPI platform against a clear description of where it will run and what it is for. State:

  • Governance jobs in scope:capacity planning, policy enforcement, regulatory reporting, content governance for ISPs, security visibility.
  • Network points to cover:RAN, core, peering or internet gateways, on fixed networks, mobile networks or both.
  • Volumes:busy-hour traffic at each point, and expected growth over the contract term.
  • Deployment mode per phase:out-of-band, inline, or out-of-band first.
  • Your architecture:the policy and charging architecture and enforcement points, and the reporting and security systems that results must reach.
  • Data rules:where data must stay, how long results may be kept, and who may query them.

These are also the factors a DPI quote is built on, so the more precisely they are stated, the more comparable the bids will be.

Part 2: the DPI RFP requirements checklist

Classification

Classification
RequirementEvidence to ask bidders for
Classify traffic by application and protocol at every network point in scopeDetection and false-positive rates for each class, measured on your traffic during the proof of concept
Classify encrypted and tunnelled flows, and state whether any decryption is usedA description of the method, and per-class results for the encrypted classes that matter to you
Keep classification current as applications changeHow models or signatures are updated, and how updates enter your change control
Report the share of traffic left unclassifiedThe unclassified share in proof-of-concept results

Deployment, scale and resilience

Deployment, scale and resilience
RequirementEvidence to ask bidders for
Support out-of-band and inline deployment, and state what each mode providesArchitecture for each mode at your network points
Handle busy-hour throughput at each pointA load-test plan at your busy-hour peak
Defined behaviour if an inline component failsA failure-mode description and a failover test plan
An availability and disaster-recovery design for your topologyThe availability design document

Policy

Policy
RequirementEvidence to ask bidders for
Policies per application, subscriber group or cell, deployed and adjusted in real timeA demonstration during the proof of concept
A report-only mode before any rule acts on trafficA demonstration in report-only mode
Support for each policy action on your required listA written statement, action by action
Integration with your policy and charging architecture and 5G coreAn integration plan stating what each side provides

Reporting

Reporting
RequirementEvidence to ask bidders for
A network-wide view with drill-down to application and flowSample reports and a live demonstration
Trends at network and application level, and policy execution feedbackSample reports
Reports in the form your regulatory obligations requireA mapping of each required report to platform output
Export to your reporting and security systemsThe integration plan

Data governance, delivery and commercial terms

Data governance, delivery and commercial terms
RequirementEvidence to ask bidders for
Runs on your infrastructure, with data kept in the KingdomDeployment architecture showing where traffic and results stay
Output limited to what the governance job needs, with retention and access set by youA data-flow description listing every data element produced
Local delivery: localisation to your traffic mix, integration and supportThe support model, team location and working languages
A transparent pricing basisA price breakdown by deployment, capacity, throughput, placement and scope

Get the RFP checklist as an editable file

The same checklist as this page, ready to paste into your RFP.

Send me the file

Leave your work email below and we send it to you.

Part 3: write the proof of concept into the RFP

Make award or final acceptance depend on results measured on your network, in three stages:

  1. 1. Written acceptance criteria.Before anything is installed, agree per-class detection and false-positive thresholds, the reports to be produced, and the expected failure behaviour.

  2. 2. Out-of-band classification against verified traffic.The platform classifies your traffic out-of-band, and results are checked against traffic you have verified independently. False positives are measured as carefully as detection.

  3. 3. Report-only policy, then the inline decision.Rules run in report-only mode so you see what they would have done. Inline enforcement is decided only after classification has proven itself.

How to set up stage 2 in detail: Measuring DPI classification accuracy on your traffic.

Common gaps in DPI RFPs

  • One accuracy figure with no definition.Ask for detection and false-positive rates per class, on your traffic.
  • Inline from day one.It puts an unproven platform in the forwarding path. Phase it: out-of-band first, inline when enforcement is needed.
  • No false-positive requirement.A false positive means a policy acts on the wrong traffic.
  • Reporting obligations left unnamed.List the reports you must produce, so bidders can map them.
  • No data-governance clause.State where data stays, what is produced, who may query it and for how long.
  • Requirements with no governance purpose.Trace every requirement to a capacity, policy, reporting or compliance need. It keeps the scope, the data produced and the evaluation focused.

How Interkey Intelligent DPI answers these requirements

Interkey Intelligent DPI against the requirement areas
Requirement areaInterkey Intelligent DPI
ClassificationAn AI traffic model built into the engine core classifies from flow behaviour; encrypted and tunnelled flows are classified without decryption
Keeping currentAutomated feature extraction from live traffic, automated model training, and a closed loop from Live View back to models and policies
DeploymentInline or out-of-band on your infrastructure; most operators start out-of-band
Scale and resilienceDesigned for terabit-per-second traffic intake; full-mesh control and user planes; multi-level disaster recovery; throughput scoped per deployment
PolicyPer application, subscriber group or cell; real-time deployment and adjustment; service-chain control; blocking where your policy and applicable regulation require it
ReportingLive View drill-down to application and flow, trend insights, policy execution feedback, latency measured in seconds; a reporting layer for capacity and regulatory teams
IntegrationPolicy and charging and 5G core integration scoped in the deployment design; Interkey integrates with your policy, billing, security and reporting systems
DataCan operate entirely in the Kingdom; output is metadata; retention and access follow your rules and the contract
DeliveryLocalisation, integration and support from Interkey's team in Riyadh, in Arabic and English
CommercialQuote-based on deployment, capacity, throughput, placement and scope; no published price list

Questions about DPI RFPs

What should a DPI RFP include?

A description of your network and the governance jobs in scope, requirements for classification, deployment, policy, reporting and data governance, the evidence each bidder must provide, and a proof-of-concept clause that ties acceptance to results on your traffic.

How is an RFP different from a vendor evaluation?

The RFP states what you require in writing. The evaluation is how you compare the responses and the proof-of-concept results. See How to evaluate DPI vendors.

Should the RFP require inline deployment?

Only for the phase where policy must act on traffic. Classification and reporting work out-of-band. See Inline vs out-of-band DPI.

How should accuracy be specified?

As detection and false-positive thresholds for each application class that matters to you, measured on traffic you have verified, and agreed in writing before the test.

Can we discuss requirements with Interkey before issuing the RFP?

Yes. Use the form below to tell us the scope and your timeline.

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 your DPI requirements

Tell us the governance jobs in scope, the network points to cover, whether the RFP is in drafting or already issued, 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.