Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:dpi:qoe:paramdescript:start [2024/01/26 13:36] – elena.krasnobryzh | en:dpi:qoe:paramdescript:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Description of QoE metrics | ||
- | {{indexmenu_n> | ||
- | =====Netflow===== | ||
- | |||
- | ^ Metric | ||
- | | Octet delta | Traffic difference (bytes) at the beginning and end of the specified period | ||
- | | Fragmented packets delta | Difference of IP packets divided into parts/ | ||
- | | Sorce AS | AS host number | ||
- | | Destination AS | Subscriber' | ||
- | | Post nat source IPv4-address | ||
- | | Post nat source port | A port converted by NAT from private to public for communicating with external devices and accessing the Internet | ||
- | | Vchannel/ | ||
- | | Service class | Traffic classes cs0 — cs7. For more details see Traffic class allocation for a tariff plan | 0 — cs0\\ 1 — cs1\\ …\\ 7 — cs7 | | ||
- | | Reciever IP-interface index and Sender IP-interface index | Traffic direction | ||
- | |||
- | ==== Retransmits ==== | ||
- | |||
- | - Total retransmit percentage | ||
- | - The percentage of retransmissions when the traffic goes FROM subscriber | ||
- | - The percentage of retransmissions when the traffic goes TO subscriber | ||
- | {{ : | ||
- | Retransmission types: | ||
- | * **TCP Retransmission** is a classic type of packet retransmission. The packet sender having not received acknowledgment from the addressee after the retransmission timer expires, resends the packet automatically, | ||
- | * **TCP Fast Retransmission** corresponds for the following case: the sender resends the data immediately after assuming that the sent packets are lost without waiting for the expiration of the transmission timer. Usually it can be triggered by receiving several consecutive (usually three) duplicate acknowledgments with the same serial number. For example, the sender transmitted a packet with sequence number 1 and received an acknowledgment equal to sequence number plus 1, i.e. 2. The sender understands that the next packet with number two is expected. Suppose that the next two packets are lost and the recipient receives data with serial number 4. The recipient resends the acknowledgment with the number 2. Upon the receiving the packet with the number 5, the sender still sends the acknowledgment with the number 2. The sender sees three duplicate acknowledgments, | ||
- | * **Spurious Retransmission** is the type of retransmission appeared in the version 1.12 of Wireshark sniffer and means that the sender resends packets to which the recipient has already sent acknowledgment. | ||
- | |||
- | =====Clickstream===== | ||
- | |||
- | < | ||
- | |||
- | ^ Metric | ||
- | | Path | The address to which the subscriber went | | | ||
- | | Referer | ||
- | | User agent | Allows you to understand from which device the request was made | ||
- | | 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 |