Interkey Intelligent DPI

Service chaining and traffic steering for operators

Service chaining and traffic steering for telecom operators

Service chaining sends selected traffic through an ordered set of network functions, a chain, instead of passing every flow through every function. Traffic steering is the decision about which flows enter which chain, and that decision needs a criterion. For most operator use cases, the criterion is what the traffic is. Interkey Intelligent DPI classifies traffic in real time, including encrypted flows, without decrypting them, and service-chain control is one of its policy execution actions.

A Saudi product, built by Interkey

For core network, service and network planning engineers at telecom operators and ISPs. Reviewed November 2026.

  • Service chaining:traffic passes only through the network functions it needs, in a defined order.
  • What DPI adds:the classification that decides which traffic enters which chain, per application, subscriber group or cell.
  • In Interkey Intelligent DPI:service-chain control as a policy execution action, plus service chaining and flexible deployment of user-plane nodes for launching new services.
  • Scope of this page:steering inside the operator's service path. Steering in the radio access network or for roaming is a different subject.

What service chaining and traffic steering mean

Terms used on this page
TermMeaning
Service functionA network function that traffic can pass through, such as a function for policy, reporting or a value-added service
Service chainAn ordered set of service functions applied to a defined type of traffic
Traffic steeringThe decision that sends a flow into a particular chain, or past it
Steering criterionWhat the decision is based on: the application, the subscriber group, the cell, or a combination

Without steering, an operator has two poor options. Either every flow passes through every function, which spends capacity and adds processing to traffic that does not need it, or functions are fixed to particular links, which makes new services slow to introduce. Steering by classification lets each function see only the traffic it exists for.

Why steering starts with classification

A steering decision is only as good as its criterion. If the criterion is the application, the platform has to know which application each flow belongs to, and that is harder than it used to be: 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. This includes encrypted and tunnelled flows, which it classifies without decrypting them. An AI traffic model built into the engine core does the classification, and features are extracted automatically from live traffic to train it.

A misclassified flow takes the wrong chain. That is why classification accuracy has to be measured per class, on your own traffic, before steering acts on anything. See Measuring DPI classification accuracy on your traffic.

What Interkey Intelligent DPI provides

Service chaining in Interkey Intelligent DPI
CapabilityIn Interkey Intelligent DPI
ClassificationAI traffic model built into the engine core; encrypted and tunnelled flows classified without decryption
Policy executionReal-time policy deployment and adjustment; service-chain control; blocking where your policy and applicable regulation require it
Policy scopePer application, subscriber group or cell
New servicesService chaining and flexible deployment of user-plane nodes, on a cloud-native operations and maintenance platform
FeedbackLive View policy execution feedback; results feed back to refine models and policies
ScaleCarrier-grade traffic intake at Tbps scale across fixed and mobile networks; throughput sized per deployment

Which chains your network uses, the functions in each and the policies that select them are defined with your team during scoping. They are documented in the integration plan, together with the connection to your policy and charging architecture and your 5G core.

Design questions to settle before steering live traffic

  1. 1. A chain catalogue.For each chain: the traffic it is for, the functions in order, the steering criterion, and an owner.

  2. 2. The steering point.Steering acts on traffic, so it needs an inline deployment. Decide where in the network that sits.

  3. 3. Behaviour when a function is unavailable.Decide what happens to steered traffic if a function in its chain cannot take it. This is part of the deployment design and must be tested before go-live.

  4. 4. Accuracy per class.Check detection and false-positive rates for every class that selects a chain.

  5. 5. Report-only first.Run each steering rule in report-only mode, so you see which traffic it would have steered before it changes anything.

  6. 6. Change control.New chains, rule changes and model updates enter the live network through your change-control process.

Validate out-of-band, steer inline

Out-of-band, the platform receives a copy of traffic, classifies it and reports without sitting in the forwarding path. That is the right place to validate classification and to see which flows each candidate chain would receive. Steering itself acts on traffic, so it needs an inline deployment, which operators usually add as a second phase after classification has been validated. See Inline vs out-of-band DPI: choosing the deployment.

Both run on your own infrastructure, and the platform can operate entirely in the Kingdom. The architecture is cloud-based, with full-mesh interconnection between the control and user planes and multi-level disaster recovery.

Test it on your network in 3 stages

  1. 1. Written acceptance criteria.Agree which chains are in scope, which traffic each should receive, how that is measured and what counts as a pass.

  2. 2. Out-of-band classification against verified traffic.Measure false positives as carefully as detection: a false positive here means a flow enters a chain it was not meant for.

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

See also: How Interkey runs a DPI proof of concept

Questions about service chaining

Is service chaining the same as traffic steering?

They work together. A service chain is the ordered set of functions; traffic steering is the decision that sends a flow into a chain. Steering needs a criterion, and classification provides it.

Does this cover traffic steering in the radio access network or for roaming?

No. This page is about steering traffic through service functions inside the operator's network, based on what the traffic is.

Do we need an inline deployment?

To steer traffic, yes. To validate classification and see which traffic each chain would receive, out-of-band is enough.

Can steering use encrypted traffic as a criterion?

Yes, through classification: encrypted and tunnelled flows are classified from observable characteristics without decrypting them. Measure accuracy for those classes on your own traffic.

How does it connect to our policy and charging system and 5G core?

Integration 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.

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 service chaining on your network

Tell us which services or functions you want to steer traffic to, which criteria matter (application, subscriber group or cell), whether your network is fixed, mobile or both, 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.