Subscriber-Aware Metadata (BETA)

Required License: Subscriber-Aware Metadata, Subscriber Metadata Aggregation Function

This section provides the following information about the Subscriber-Aware Metadata feature (BETA):

Overview

The Subscriber-Aware Metadata (SAM) feature produces datasets on subscriber-level network activity that is useful for analytics. This data is created across a set of high-value dimensions in terms of:

  • Subscriber session
  • Over-the-Top (OTT) application
  • Handset type
  • Location (cell)
  • Service QCI/QoS

Note:  Early Access is a pre-GA feature status indicating it is not recommended for production networks. The functionality has been tested. Little to no system testing has been performed, however, and performance/scale data is not yet available. Preliminary documentation is available.

How SAM Works

The metadata of subscriber activities is extracted using GTP or 5G correlation and Application Metadata Intelligence (AMI) modules of the Gigamon’s Network Visibility nodes. After extraction, the following information is correlated and merged by Sub-Metadata Aggregator Function (SMAF) server and exported to the Data Collection Center in JSON or AVRO format:

  • Extracted metadata information
  • Transaction event records
  • Application Metadata Intelligence flow records

The exporter sends the final SAM records to the destination using file transfer or KAFKA bus. The file records are stored in a system for a period that is configured to store the data. In case of filer transfer failures, the file transfer attempts occur for the number of times the attempts are configured . The following table provides the information about the exporter type and the supported format for SFTP and KAFKA:

 
File Format
JSON AVRO

Unarchived

(JSON File)

 Archived

(ZIP)

 File Split

Unarchived

(OCF File)

 Archived

(ZIP)

 File Split
Local
Yes Yes Yes Yes Yes Yes
SFTP
Yes Yes No Yes Yes No

 

Message Format
 

KAFKA

JSON

AVRO
Yes* Yes

* Reduces Server performance

GigaVUE-FM is the centralized configuration manager for SAM, which is deployed across multiple nodes in a network. SAM is supported in:

In each case, SAM is supported in both no-engine and engine-grouping models.

Control and User Plane Separation (CUPS) solution

In CUPS solution, SAM feature is supported in:

  • No engine grouping model
  • Engine grouping model

Non-CUPS solution

In Non-CUPS solution, SAM feature is supported in:

  • No engine grouping model
  • Engine grouping model

Licensing

■   SMT-HC2-SAM —The SMT-HC2-SAM card has GigaSMART, GigaVUE-HC2, Subscriber-Aware Metadata license for the AMI engine component. It also includes entitlement to unlimited use of Subscriber Metadata Aggregation Function (SMAF), but does not include SMAF hardware. Also, does not include GTP and/or 5G Correlation license.
■   SMT-HC3-SAM—The SMT-HC3-SAM card has GigaSMART, GigaVUE-HC3 Subscriber-Aware Metadata license for the AMI engine component. It also includes entitlement to unlimited use of Subscriber Metadata Aggregation Function (SMAF), but does not include SMAF hardware. Also, does not include GTP and/or 5G Correlation license.

Configuration of SAM

To configure Subscriber-Aware Metadata (SAM) , refer to Configuration of Subscriber-Aware Metadata using Ansible.