Contact

QUALITY OF OUTCOME · QoO

Network metrics matter. The outcome matters more.

Quality of Outcome focuses on whether network conditions allow a service to deliver the outcome the user actually expects.

Go beyond isolated QoS metrics and interpret network conditions in the context of the service.

Explore QoO with DegustExplore Degust
Visualization of your quality of outcome

METRIC VS. OUTCOME

The same network metric can lead to very different service outcomes.

NETWORK METRIC

LatencyMeasured
Packet lossMeasured
ThroughputMeasured
JitterMeasured

SERVICE OUTCOME

WebDoes the page respond as expected?
VideoCan playback continue without unacceptable impairment?
GamingCan interaction remain responsive?
VoiceCan the conversation remain usable?

QoO connects measured network conditions with the outcome a service is expected to deliver.

The applicable performance requirements depend on the service; there is no single universal formula for every application.

QoS · QoE · QoO

Related perspectives — but not the same question.

The IETF IPPM draft positions QoO as an objective, application-specific network-quality perspective that can complement established quality concepts.

Quality of Service (QoS)Characteristics of a telecommunications service that affect its ability to satisfy stated and implied user needs.
Quality of Experience (QoE)The user’s degree of delight or annoyance with an application or service.
Quality of Outcome (QoO)A framework and metric that evaluates measured network conditions against application-specific, quality-focused performance requirements.
DegustDegust uses measured network conditions and service-specific context to qualify whether defined KPIs would lead to a proper service delivery per service. ISPs can define there weighting on any of the parameters, as despito of the standardisation, the outcome will be rated differently per operator, county or even end customer base.

Related insights

SERVICE FAMILIES

Different services need different outcomes.

Web

Responsiveness matters because users wait for interactions and content to complete.

Explore Broadband

Video

Sustained delivery and responsiveness influence whether playback can continue as expected.

Explore Broadband

Gaming

Interactive responsiveness and stability matter more than raw bandwidth alone.

Explore Broadband

FROM METRIC TO OUTCOME

Qualify network conditions in the context of the service.

01

MEASURE

Collect the relevant technical conditions.

02

CONTEXTUALIZE

Consider access technology, location, tariff and service context.

03

QUALIFY

Determine whether the conditions support the expected outcome.

04

COMPARE

Compare results across time, locations and relevant groups.

QUALITY OF OUTCOME QUESTIONS

Questions operators ask about QoO.

The answers distinguish objective network-quality assessment from actual user experience.

What is Quality of Outcome (QoO)?

The IETF IPPM draft defines QoO as a network-quality framework and metric that evaluates how closely measured network conditions meet application-specific, quality-focused performance requirements. In practice, it connects objective conditions such as latency, packet loss and throughput with the outcome a defined service is expected to support.

What is the difference between QoS, QoE and QoO?

QoS describes characteristics that affect a service’s ability to meet stated needs. QoE concerns the user’s delight or annoyance. QoO evaluates measured network conditions against application-specific performance requirements; it may relate to QoE, but it is not the same as actual user experience.

Why is bandwidth alone not enough to predict service outcome?

Applications also depend on latency and packet loss, and different application classes tolerate these conditions differently. Sufficient throughput therefore does not by itself show whether web interaction, video playback, gaming or voice can deliver the expected outcome.

How can Quality of Outcome help an ISP evaluate web, video or gaming services?

An operator can compare measured network conditions with requirements chosen for the relevant service family. The result indicates whether the network conditions support the expected outcome without assuming that one threshold or formula applies universally to every service.

Does the same latency mean the same thing for every service?

No. Downloads, interactive web use, gaming, voice and real-time video can respond differently to latency distributions and high-percentile delays. The service context is therefore required to interpret the measurement.

Why does access technology matter when qualifying a result?

Access technology influences the conditions and expectations under which a result was measured. Technology, location, tariff and other context help operators compare like with like and avoid applying one undifferentiated expectation to every connection.

How can Degust use QoO in continuous service validation?

Degust can combine measured network conditions with service-specific and deployment context to qualify whether defined outcomes can be supported. This is an Acctopus application of the QoO perspective; Acctopus does not claim to have invented QoO.

Can QoO complement existing network monitoring?

Yes. Infrastructure and service monitoring remain important. QoO adds an application-specific interpretation of measured network conditions and can help translate technical evidence into the outcome a service is expected to deliver.

Is Quality of Outcome a replacement for QoE?

No. The IETF draft explicitly describes QoO as a QoS indicator that may be related to, but is not the same as, actual end-user QoE. The perspectives can complement one another.

Measure the network. Validate the outcome.

See how Degust can use service context to turn technical measurements into meaningful validation results.
See Degust in actionExplore Broadband