> For the complete documentation index, see [llms.txt](https://whitepaper.qualoo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.qualoo.io/introduction/internet-landscape/quality-of-service-qos-and-quality-of-experience-qoe.md).

# Quality of Service (QoS) and Quality of experience (QoE)

The International Telecommunication Union (ITU) characterizes Quality of Service (QoS) as "the collective attributes of a telecommunication service that influence its capacity to satisfy the user's expressed and implicit needs" ([source](https://www.itu.int/rec/T-REC-E.800-200809-I/en)). QoS is primarily assessed through objective metrics such as bandwidth, packet loss ratio, latency, etc. However, QoS measurement may vary depending on the location within the network where it is evaluated.

The ITU defines Quality of Experience (QoE) as "the user's level of satisfaction or frustration with an application or service" ([source](https://www.itu.int/rec/T-REC-P.10-201711-I/en)). While QoE is linked to QoS, it also relies on subjective factors like the user's mood, the device used, and time of day. There is an ongoing discussion within the telecommunications industry about the best way to quantify QoE. Several models exist, but the connection between QoE and QoS can be simplified as follows:

$$QoE=QoS+subjective factors$$

Considering that users prioritize QoE, which influences their decisions to lodge complaints with their service provider or switch providers, it's critical to establish a method for measuring this in a system that monitors internet performance. We propose several principles that must be fulfilled to ensure QoS data measurements align as closely as possible with QoE:

* **Extensive Data Coverage**: The user experience should be assessed over a wide geographical area and with enough independent data points to support statistical analysis.
* **Customer-Level Measurement**: Testing should occur at network points where the user interacts with the internet, such as the user's home, office, coffee shop, etc.
* **Independent Unbiased Data**: Test results should be impartial, and analysis should be conducted independently of industry stakeholders to mitigate conflict of interest concerns.
* **Data Sharing**: The collected data should be shared more openly than is currently standard in the industry, to prevent duplicate efforts and establish a single source of truth.
* **Actionable Insights**: Data should be analysed to identify major events and ongoing service-impacting issues. The collected data and insights should be available to relevant stakeholders for necessary actions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper.qualoo.io/introduction/internet-landscape/quality-of-service-qos-and-quality-of-experience-qoe.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.