Aviz Networks details extended session tracking
Aviz says its Service Node now extends user session identification for telecom networks by adding tunnel and quality-of-service fields to standard keys. The update is aimed at operators that need more accurate flow separation, subscriber correlation, and exported analytics without changing existing downstream systems.
Research Overview
The blog says shared mobile infrastructure can produce many flows that look similar when only the inner 5-tuple is used. In those cases, different subscribers or services can be grouped into the same session, which affects the accuracy of exported records.
Aviz presents the issue as a session-identification problem for operators that rely on Kafka and IPFIX outputs for analytics, monitoring, and reporting. The article says those outputs depend on correct session grouping to keep metadata and KPI records aligned with actual traffic.
Technical Breakdown
The standard session key used by ASN is the inner 5-tuple: inner source IP, inner destination IP, source port, destination port, and transport protocol. The blog says this can be insufficient when separate subscribers share the same inner values.
To address that, Enhanced User Session Identification can add outer source IP, outer destination IP, GTP TEID, outer DSCP, and inner DSCP to the session key. Aviz says operators can choose which of those fields to include, and existing deployments can continue with the conventional method if the feature is turned off.
Operational Impact
The blog says the expanded session key is used to create Kafka topic keys and IPFIX flow keys. Aviz says that allows downstream analytics systems to receive unique session identifiers while keeping the analytics architecture unchanged.
The company says the feature is intended to improve flow separation, IMSI correlation, metadata exports, and KPI calculations. It also says the approach supports more granular tracking of subscriber and service traffic across shared network infrastructure.
Leadership Perspective
For network operators, the article frames accurate session identification as a requirement for subscriber analytics and reporting. It says the feature is configurable to match deployment needs and remains backward compatible with existing environments.
This Blog Signals brief is a fact-based summary of the vendor blog.