Policy control and Live View reporting
Policy control and reporting: from traffic classification to governed action
Without classification, a traffic policy is an intention rather than a control. In Interkey Intelligent DPI, policies act per application, subscriber group or cell; Live View shows what is happening with latency measured in seconds; and the results feed back into the models and policies. Rules can run in report-only mode first, so you see what they would do before they act on traffic.
A Saudi product, built by Interkey
For policy, network operations, capacity planning and regulatory reporting teams at operators and ISPs. Reviewed November 2026.
- Policy scope:per application, subscriber group or cell.
- Policy actions:real-time deployment and adjustment, service-chain control, and blocking where your policy and applicable regulation require it.
- Report-only first:see what a rule would have done before it acts.
- Live View:a network-wide view with drill-down to application and flow level, trends, and policy execution feedback, with latency measured in seconds.
What a policy acts on, and how
| Policy element | In Interkey Intelligent DPI | Governance note |
|---|---|---|
| Scope | Per application, subscriber group or cell | Define the scope in your policy catalogue before rules are configured |
| Actions | Real-time policy deployment and adjustment; service-chain control; blocking | Which actions are permitted is set by your policy and applicable regulation |
| Testing | Report-only mode shows what a rule would have done | Keep report-only results as evidence for the approval decision |
| Where it acts | Policy acts on traffic only in an inline deployment; out-of-band deployments classify and report | Move a rule to enforcement only after classification has proven itself |
| Integration | Integration with your policy and charging architecture and 5G core is scoped in the deployment design | Bring your enforcement points to scoping |
Live View: what the reports show
- Global traffic visualisation:a network-wide view, with drill-down to application and flow level.
- Traffic trend insights:trend analysis at network and application level.
- Policy execution feedback:a real-time view of how each policy is being executed.
- Second-level latency:Live View latency is measured in seconds, not minutes.
Interkey Intelligent DPI includes a reporting layer for capacity and regulatory teams. Interkey handles integration with your reporting and security systems as part of integrating the platform into the live network.
| Team | Typical question | Where the answer comes from |
|---|---|---|
| Capacity planning | Which applications drive load, where and when? | Traffic trend insights at network and application level |
| Policy owners | Is a rule doing what it was approved to do? | Policy execution feedback |
| Regulatory reporting | Can we describe traffic in the form our obligations require? | The reporting layer; specify the reports your obligations need during scoping |
| Network operations | What is happening on the network now? | Global traffic visualisation, with latency measured in seconds |
The closed loop: classify, act, observe, refine
1. Classify.The AI traffic model identifies the application class of each flow.
2. Act.Approved policies apply to the classes, subscriber groups or cells they cover.
3. Observe.Live View shows traffic and policy execution as it happens.
4. Refine.Live View results feed back to refine models and policies.
A refinement to a live policy is a change to a live network. It should pass through the same approval as the original rule.
Governance controls to set up before go-live
These controls sit with the operator, not the platform. Setting them up before the first rule is enforced makes every later decision easier to explain and to audit.
1. A policy catalogue.For each rule: the application class, the scope, the action, the policy or regulatory basis, and an owner.
2. An approval route.Who signs off a rule before it moves from report-only to enforcement, and what report-only evidence they need to see.
3. Data rules.Which reports are kept, for how long, and who can query them. The platform produces metadata; retention and access are set in the deployment design and the contract, following your data-governance rules.
4. A review rhythm.Compare policy execution feedback with what each rule was approved to do.
5. Change control for updates.Model and policy updates enter the live network through your change-control process.
Questions policy and reporting teams ask
Can a policy be tested without affecting traffic?
Do we need an inline deployment to get reports?
What data do the reports contain?
Can reports feed our existing systems?
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 your policy and reporting requirements
Tell us which governance job comes first (capacity, policy, regulatory reporting or security visibility), which reports your teams need, 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