Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en:dpi:qoe_analytics:qoe_gui:reports:paramdescript [2025/10/30 13:40] – created elena.krasnobryzh | en:dpi:qoe_analytics:qoe_gui:reports:paramdescript [2025/12/09 13:23] (current) – elena.krasnobryzh | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== QoE metric descriptions | + | ====== |
| {{indexmenu_n> | {{indexmenu_n> | ||
| - | < | + | =====Netflow===== |
| - | Example: suppose you need to find a report that contains the RTT metric.\\ | + | |
| - | To do this, locate the RTT metric in the upper filter table, type " | + | |
| - | As a result, the main table below will be filtered, showing only the reports containing the RTT metric:\\ \\ | + | |
| - | {{gallery>: | + | |
| - | Each report includes a note specifying where to find it (scroll to the beginning of the document to see the note). | + | |
| - | </ | + | |
| - | ===== NetFlow ===== | + | ^ Metric |
| - | ^ Metric | + | | Octet delta |
| - | | Delta of octets | + | | Fragmented |
| - | | Delta of fragmented | + | | [[en:dpi:qoe:use_cases:full_netflow_analytics# |
| - | | [[en:dpi:qoe_analytics:qoe_gui:dashboard# | + | | Source AS | AS host number |
| - | | Source AS | AS number of the source | + | | Destination AS |
| - | | Destination AS | + | | Post nat source |
| - | | IPv4 source address | + | | Post nat source |
| - | | Source | + | | Vchannel/ |
| - | | Channel/ | + | | Service class | Traffic classes cs0 — cs7. For more details see [[en: |
| - | | Service class | Traffic classes cs0 — cs7. [[en: | + | | Receiver |
| - | | Receiver and sender | + | |
| - | ===== ClickStream ===== | ||
| - | < | ||
| - | ^ Metric | + | =====Clickstream===== |
| - | | Path | The URL path the subscriber visited | + | |
| - | | Source request URL | The resource from which the request originated.\\ Used during redirection: | + | |
| - | | User agent | User agent string. Identifies the device used for the request | + | |
| - | | Method | + | |
| - | | Result code | HTTP response code returned by the server | + | |
| - | | Content size | Amount of data (in bytes) returned by the server in response to the request | + | |
| - | | Content type | HTTP Content-Type, | + | |
| - | | Blocked | + | |
| - | | Host type | Type of host | 1 — HTTP\\ 2 — CNAME\\ 3 — SNI\\ 4 — QUIC | | + | |
| - | ===== DNS flow ===== | + | < |
| - | ^ Metric | + | |
| - | | Host | Domain name of the DNS host from the DNS response | + | |
| - | | Host category | + | |
| - | | Total | Number of raw log entries grouped into a single record in the aggregated log | | + | |
| - | | Sessions | + | |
| - | | Hosts | Number of hosts in the aggregated log | | + | |
| - | | Host categories | + | |
| - | | DNS host IPs | Number of unique IP addresses of DNS hosts | | + | |
| - | | Logins | + | |
| - | | Subscribers | + | |
| - | | Channels | + | |
| - | | Time | Session start time | | + | |
| - | | Session ID | Session identifier | + | |
| - | | Login | Subscriber login | | + | |
| - | | IPv4 source address | + | |
| - | | IPv6 source address | + | |
| - | | Source port | ::: | | + | |
| - | | IPv4 destination addr | Destination address of the request — can be either subscriber or host | | + | |
| - | | IPv6 destination addr | ::: | | + | |
| - | | Destination port | ::: | | + | |
| - | | DNS transport | + | |
| - | | DNS host IP | IP address of the DNS host | | + | |
| - | | DNS host port | Port used by the DNS host | | + | |
| - | | Subscriber | + | |
| - | | Subscriber port | Port used by the subscriber | + | |
| - | | Rrclass | + | |
| - | | DNS type | Type of DNS record (defines the function):\\ \\ 1 — A\\ 5 — CNAME | | + | |
| - | | TTL | Time-to-live | + | |
| - | | DNS data | RDATA content, base64 encoded — can be used to identify IPs belonging to a host | | + | |
| - | | VLAN ID | Unique VLAN identifier | + | |
| - | | Post VLAN ID | VLAN ID after route modification | + | |
| - | | DPI ID | DPI number (found in GUI: Administrator → Equipment) | + | |
| - | | Channel/Bridge | + | |
| - | | MPLS labels | + | |
| - | ===== GTP flow ===== | + | ^ Metric |
| - | GTP (GPRS Tunneling Protocol) is an IP-based group of connection protocols used in GSM, UMTS, and LTE networks. | + | | Path | The address to which the subscriber went | | |
| - | Mobile operators use GTP as a tunneling protocol | + | | Referer |
| - | * **GTP-C** | + | | User agent | Allows you to understand from which device the request was made |
| - | * **GTP-U** (User Plane) — user data, such as voice or application data | + | | Method |
| + | | Result code | The HTTP code that the server returned | ||
| + | | Content length | ||
| + | | Content type | Content-Type in HTTP, used to define the MIME type of a resource | ||
| + | | Locked | ||
| + | | Host type | ||
| + | |||
| + | =====DNS Flow===== | ||
| + | |||
| + | |||
| + | |||
| + | ^ Metric | ||
| + | | Host | DNS host domain name from the DNS response | ||
| + | | Host category | ||
| + | | Total | Number of records from the raw log, grouped into a single entry in the aggregated log | | ||
| + | | Sessions | ||
| + | | Hosts | Number of hosts in the aggregated log | | ||
| + | | Host categories | ||
| + | | DNS hosts IPs | Number of unique IP addresses of DNS hosts | | ||
| + | | Logins | ||
| + | | Subscribers | ||
| + | | Channels | ||
| + | | Time | Time of session start | | ||
| + | | Session ID | Session ID | | ||
| + | | Login | Subscriber login | | ||
| + | | Source IPv4-address | ||
| + | | Source IPv6-address | ||
| + | | Source port | ::: | | ||
| + | | Destination IPv4-address| Information about the recipient of the request. The recipient can be either | ||
| + | | Destination IPv6-address| ::: | | ||
| + | | Destination port | ::: | | ||
| + | | DNS transport | ||
| + | | DNS host IP | IP address | ||
| + | | DNS host port | Port used by the DNS host | | ||
| + | | Subscriber | ||
| + | | Subscriber port | Port used by the subscriber | ||
| + | | Rrclass | ||
| + | | DNS type | Indicates the function of the server in processing and storing DNS requests in the domain name system:\\ \\ 1 - A\\ 5 - CNAME | | ||
| + | | TTL | The acceptable time for storing this resource record in the cache of a non-responsive DNS server | ||
| + | | DNS data | RDATA encoded in base64. For example, it is possible to find out which IPs belong to the host | | ||
| + | | VLAN ID | Unique identifier of the virtual local area network | ||
| + | | Post VLAN ID | VLAN ID after route change | ||
| + | | DPI ID | Number of DPI, taken from GUI: Administrator → Equipment | ||
| + | | Vchannel/ | ||
| + | | MPLS labels | ||
| - | DPI decodes **GTP-C**, and this information is exported via **IPFIX** | + | =====GTP Flow===== |
| + | GTP (GPRS Tunneling Protocol) is a group of IP-based connection protocols used in GSM, UMTS, and LTE networks. | ||
| + | The GTP protocol is used by mobile operators as a tunnel for data transmission. It consists of two layers: | ||
| + | * **GTP-C** (Control Plane) — service information, | ||
| + | * **GTP-U** (User Plane) — user data, such as voice information. | ||
| + | DPI decodes **GTP-C**, and this information is sent to **IPFIX** | ||
| - | GTP logs are used for: | + | GTP logs are used for the following tasks: |
| - | * **Base station load analysis** | + | * **Base station load analysis**: distribution of subscribers |
| - | * **Anomaly monitoring** | + | * **Anomaly monitoring**: tracking changes |
| - | * **Subscriber tracking** | + | * **Subscriber tracking** on the map and movement |
| - | Some operators also use GTP logs to link IP addresses with IMSI (subscriber identifier), combining data from different | + | Some operators also use GTP logs to link IP and IMSI (subscriber identifier) |
| - | Reports are based on **GTP-C V1** and **GTP-C V2** versions.\\ | + | |
| - | Access to GTP logs is available only to users with a QoE Standard license. [[en: | + | |
| - | ^ Metric | + | The report is based on versions **GTP-C V1** and **GTP-C V2**. |
| - | | Date | Date and time of subscriber registration on the base station. In the aggregated log, it depends on the aggregation period | + | Access |
| - | | Time | ::: | | + | |
| - | | SIM card number | + | |
| - | | Phone number | + | |
| - | | IMEI | Unique device identifier that includes manufacturer, | + | |
| - | | IPv4 subscriber address | + | |
| - | | IPv6 subscriber address | + | |
| - | | Subscriber timestamp | + | |
| - | | Country code | Country where the base station is located\\ \\ 0 — undefined\\ 250 — Russia | + | |
| - | | Country name | ::: | | + | |
| - | | Network (operator) code | Operator code for the base station\\ \\ 0 — undefined\\ 1 — MTS\\ 2 — Megafon\\ 20 — Tele2\\ 99 — Beeline | + | |
| - | | Network (operator) name | ::: | | + | |
| - | | Coverage area code | Cell identifier within the coverage area (may correspond | + | |
| - | | Base station code | Code of the base station to which the subscriber | + | |
| - | | DPI ID | DPI number (found in GUI: Administrator → Equipment) | + | |
| - | | Total | Number of raw log entries collapsed into one aggregated record | + | |
| - | | Sessions | + | |
| - | | Latitude | + | |
| - | | Longitude | + | |
| - | | Element ID | Geographic element identifier — composed of country code, network code, base station code, and coverage area code | | + | |
| - | | Element name | Geographic name — composed of country code, network code, base station code, and coverage area code | | + | |
| - | | Element description | + | |
| - | | Session ID | Subscriber Internet session ID | | + | |
| - | | GTP version | + | |
| - | | Request ID | Internet session data | | + | |
| - | | Response ID | ::: | | + | |
| - | | Result code | Result code of the operation | + | |
| - | | Success | + | |
| - | | SGW control plane IP | Fields describing parameters and identifiers of SGW/PGW connections for control and data separation, including IP addresses and TEIDs | | + | |
| - | | SGW control plane TEID | ::: | | + | |
| - | | SGW user plane IP | ::: | | + | |
| - | | SGW user plane TEID | ::: | | + | |
| - | | PGW control plane IP | ::: | | + | |
| - | | PGW control plane TEID | ::: | | + | |
| - | | PGW user plane IP | ::: | | + | |
| - | | PGW user plane TEID | ::: | | + | |
| - | | Access point name | Traffic type; may be a custom value | | + | |
| - | | Rat | Radio access technology — defines whether the subscriber uses Bluetooth, Wi-Fi, GSM, UMTS, LTE, or 5G. | | + | |
| + | ^ Metric | ||
| + | | Date | Date and time of subscriber registration at the tower. In the aggregated log, this time depends on the aggregation time | | ||
| + | | Time | ::: | | ||
| + | | SIM card number | ||
| + | | Phone number | ||
| + | | IMEI | Unique phone identification number, contains information about the manufacturer, | ||
| + | | Subscriber ipv4 address | ||
| + | | Subscriber ipv6 address | ||
| + | | Time of ULI | Time at which the subscriber' | ||
| + | | Mobile country code | Information about the country where the tower is located\\ \\ 0 - not defined (?)\\ 250 – Russia | ||
| + | | Country name | ::: | | ||
| + | | Mobile network (operator) code | Information about the operator who owns the tower\\ \\ 0 - not defined (?)\\ 1 - MTS\\ 2 - Megafon\\ 20 – Tele2\\ 99 - Beeline | ||
| + | | Network (operator) name | ::: | | ||
| + | | Service/ | ||
| + | | Base station code | The base station to which the subscriber has connected. There may be several of them in the coverage area | | ||
| + | | DPI ID | DPI number, taken from GUI: Administrator → Equipment | ||
| + | | Total | The number of records from the raw log, collapsed into one record of the aggregated log | | ||
| + | | Sessions | ||
| + | | Latitude | ||
| + | | Longitude | ||
| + | | Cell ID | Identifier of the area in which the subscriber is located. Consists of several values: \\ - Country code\\ - Network (operator) code\\ - Base station code\\ - Coverage area code | | ||
| + | | Cell name | The name of the location in which the subscriber is located. Consists of several values: \\ - Country code\\ - Network (operator) code\\ - Base station code\\ - Coverage area code | | ||
| + | | Cell description | ||
| + | | Session ID | Subscriber Internet session ID | | ||
| + | | GTP version | ||
| + | | Request message ID | Internet session data | | ||
| + | | Response message ID | ::: | | ||
| + | | Result code | Code indicating the result of the operation | ||
| + | | Success | ||
| + | | SGW control plane IP | Fields describing connection parameters and identification at the network gateway level (SGW and PGW) for data transfer and control. Includes IP addresses and tunnel identifiers (TEIDs) to differentiate between management traffic and user data. | | ||
| + | | SGW control plane TEID | ::: | | ||
| + | | SGW data plane IP | ::: | | ||
| + | | SGW data plane TEID | ::: | | ||
| + | | PGW control plane IP | ::: | | ||
| + | | PGW control plane TEID | ::: | | ||
| + | | PGW data plane IP | ::: | | ||
| + | | PGW data plane TEID | ::: | | ||
| + | | Access Point Name | Traffic type. The name can be custom | ||
| + | | Rat | Radio access technology (radio access technology). Indicates what technology the subscriber uses - Bluetooth, Wi-Fi, GSM, UMTS, LTE or 5G. | | ||