Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:dpi:qoe:paramdescript [2024/11/01 19:47] – elena.krasnobryzh | en:dpi:qoe:paramdescript [2024/11/05 08:40] (current) – [GTP Flow] elena.krasnobryzh | ||
|---|---|---|---|
| Line 33: | Line 33: | ||
| =====DNS Flow===== | =====DNS Flow===== | ||
| + | |||
| + | |||
| + | |||
| ^ Metric | ^ Metric | ||
| | Host | DNS host domain name from the DNS response | | Host | DNS host domain name from the DNS response | ||
| Line 54: | Line 57: | ||
| | Destination port | ::: | | | Destination port | ::: | | ||
| | DNS transport | | DNS transport | ||
| - | | DNS host IP | DNS host domain name from the DNS response | + | | DNS host IP | IP address of the DNS host | |
| - | | DNS host port | IP address of the DNS host | | + | | DNS host port | Port used by the DNS host | |
| - | | Subscriber | + | | Subscriber |
| - | | Subscriber | + | | Subscriber port |
| - | | Rrclass | + | | Rrclass |
| - | | DNS type | Resource class (RR Class) in the DNS request | + | | DNS type | Indicates the function of the server in processing and storing DNS requests in the domain name system:\\ \\ 1 - A\\ 5 - CNAME | |
| - | | TTL | + | | TTL |
| - | | DNS data | 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 | + | | VLAN ID | Unique identifier of the virtual local area network |
| - | | Post VLAN ID | + | | Post VLAN ID |
| - | | DPI ID | + | | DPI ID | Number of DPI, taken from GUI: Administrator → Equipment |
| - | | Vchannel/ | + | | Vchannel/ |
| - | | MPLS labels | + | | MPLS labels |
| - | | | Labels for routing packets in MPLS networks | + | |
| + | =====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** in the “GTP flow” and “Raw GTP flow” reports in the GUI. | ||
| + | |||
| + | GTP logs are used for the following tasks: | ||
| + | * **Base station load analysis**: distribution of subscribers across base stations and traffic monitoring, which is useful for LBS (Location-Based Services). | ||
| + | * **Anomaly monitoring**: | ||
| + | * **Subscriber tracking** on the map and movement analysis: visualization on the map is possible, as well as route analysis and current location. | ||
| + | Some operators also use GTP logs to link IP and IMSI (subscriber identifier) to consolidate user information from various information systems (DPI, billing, etc.). | ||
| + | |||
| + | The report is based on versions **GTP-C V1** and **GTP-C V2**. | ||
| + | Access to GTP Log is available only to users with a QoE Standard license. [[en: | ||
| + | |||
| + | ^ 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. | ||