Interkey Intelligent DPI

5G networks at operator scale

5G traffic management with application classification

5G traffic management means knowing what traffic fills the new network, deciding what should happen to it and checking the result, at much larger volumes than before. More capacity per cell does not tell you which applications use it. Interkey Intelligent DPI is designed for fixed and mobile networks at carrier scale. It classifies traffic by application in real time, including encrypted traffic, without decrypting it, and applies policies per application, subscriber group or cell. Integration with your 5G core is part of the deployment design, scoped with you.

A Saudi product, built by Interkey

For 5G core, capacity planning and policy teams at telecom operators. Reviewed November 2026.

  • Same loop, larger scale:identify the traffic, decide, act, observe. 5G raises the volumes, not the need to know what the traffic is.
  • Classification:encrypted and tunnelled flows are classified without decryption, by an AI traffic model built into the engine core.
  • Policy:deployed and adjusted in real time, per application, subscriber group or cell.
  • Integration:the connection to your 5G core and your policy and charging architecture is defined during scoping and documented in the integration plan.

What changes for traffic management on 5G

  • Volumes.5G adds capacity, and traffic grows to fill it. A traffic management platform has to take in carrier volumes without becoming the bottleneck. Interkey Intelligent DPI is designed for carrier-grade traffic intake at Tbps scale across fixed and mobile networks, with throughput sized per deployment.
  • The question stays the same.A busier cell on 5G is still a cell whose load you need to explain. Volume counters say how much; classification says what.
  • Encryption.Classification by port number or payload alone cannot tell encrypted applications apart, so it has to rely on characteristics that stay observable.
  • New plans and services.New plans and services may be defined around application classes or subscriber groups. Policies need to act at that level and be adjustable quickly.
  • The core.How traffic management connects to the 5G core and to policy and charging is a design decision for each operator, not a fixed recipe.

The traffic management loop on a 5G network

5G traffic management with Interkey Intelligent DPI
StepThe question it answersIn Interkey Intelligent DPI
1. IngestCan the platform take in our 5G traffic?Carrier-grade traffic intake at Tbps scale across fixed and mobile networks; throughput sized per deployment
2. ClassifyWhat is this traffic?AI traffic model built into the engine core; encrypted and tunnelled flows classified without decryption
3. ActWhat should happen to it?Policies deployed and adjusted in real time, per application, subscriber group or cell; service-chain control; blocking where your policy and applicable regulation require it
4. ObserveIs it working?Live View: network-wide view with drill-down to application and flow, trends and real-time policy execution feedback
5. RefineWhat should change?Live View results feed back to refine models and policies

For the capacity side in detail, see Mobile network congestion: diagnose it by application.

What to bring to 5G scoping

Integration with the 5G core and your policy and charging architecture is part of the deployment design. You bring your policy architecture and enforcement points to scoping, and the integration plan documents what each side provides. Come prepared with answers to these questions:

  1. 1. Observation points.Where in the network the platform should see traffic, for which services, and at what busy-hour peak.

  2. 2. Placement.Which points start out-of-band (classify and report) and which may later need inline (act on traffic).

  3. 3. Policy and charging.Which of your systems define plans and subscriber groups, and where enforcement points sit.

  4. 4. Report consumers.Which teams use the reports: capacity planning, network operations, policy and product, regulatory affairs.

  5. 5. Data rules.Retention and access for the metadata the platform produces, and whether everything stays in the Kingdom.

  6. 6. Acceptance.What the proof of concept must show before anything moves inline.

Deployment: out-of-band first, then inline

Out-of-band, the platform receives a copy of traffic and classifies and reports without sitting in the forwarding path. This is where most operators start, and it gives capacity and reporting teams classification straight away. An inline deployment, needed for policy enforcement, usually follows as a second phase after classification has been validated. See Inline vs out-of-band DPI: choosing the deployment.

The architecture is cloud-based, with full-mesh interconnection between the control and user planes, multi-level disaster recovery, a cloud-native operations and maintenance platform and flexible deployment of user-plane nodes. It runs on your own infrastructure and can operate entirely in the Kingdom. Throughput for your network is scoped per deployment and should be confirmed with a load test at your busiest-hour peak.

Test it on your 5G traffic in 3 stages

  1. 1. Written acceptance criteria.Agree what is tested, on which 5G traffic, how it is measured and what counts as a pass.

  2. 2. Out-of-band classification against verified traffic.Measure false positives as carefully as detection, per application class.

  3. 3. Report-only policy, then the inline decision.Policies show what they would have done before they act; enforcement follows only after classification has proven itself.

See also: How Interkey runs a DPI proof of concept

Questions about 5G traffic management

Does Interkey Intelligent DPI work on 5G networks?

It is designed for fixed and mobile networks at carrier scale. Integration with your 5G core and your policy and charging architecture is part of the deployment design, scoped with you.

Which 5G core interfaces does it connect to?

That is defined during scoping and documented in the integration plan, based on the policy architecture and enforcement points you bring.

Does it classify encrypted 5G traffic?

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.

Can it handle 5G traffic volumes?

It is designed for carrier-grade traffic intake at Tbps scale. Throughput for your network is scoped per deployment and should be confirmed with a load test at your busiest-hour peak.

Does subscriber traffic leave Saudi Arabia?

No. The platform runs on your infrastructure and can operate entirely in the Kingdom. Its output is metadata about applications, traffic volumes and triggered policies.

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 DPI for your 5G network

Tell us where you want to see 5G traffic, which teams need the results (capacity, policy, operations, regulatory), whether you plan out-of-band first, 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.