Introduction
Mean Opinion Score (MOS) has become a very popular indicator of perceived media quality. While there is a clear benefit to such a “reference quality indicator” and its widespread acceptance, MOS is often applied without sufficient consideration of its scope or limitations. Basically, eMOS (estimated MOS) is just a different parameter that evaluates MOS with a different approach.
An important point to highlight is that these quality indicators cannot be interchanged one to one. As follow we will describe the eMOS evaluation.[
Call Quality is highly dependent from Network parameters and there are several ways in which the score can be predicted…
Reality: Measuring Call Quality is not the way to score big network’s MOS..
How eMOS can be estimated?
An estimation of the human based MOS score (estimated MOS – eMOS), can be pursuit with algorithms that focus on modem response time, codec speed and other tests that predict how the voice quality would be perceived by the human ear. This approach, compared with the standard one (MOS), is more practical and scalable. In fact, based on this scalability and simplicity, most VoIP measuring applications use MOS scoring based on the e-Model (defined in ITU-T G.107).
The e-model is an algorithm which is designed to evaluate factors of a transmission which lead to a deterioration of the quality of that data traffic, specifically in a cumulative or composite measure, and produce a result – called “Rating Factor” (R-factor) – in the overall quality of a conversation.
The E-model is based on a reference connection that, as shown below, is split into a send side and a receive side. The model estimates the conversational quality from mouth to ear as perceived by the user at the receive side, both as listener and talker. The resulting rating factor R, which combines all transmission parameters relevant for the considered connection, is obtained as following:
- “R0” is the basic signal-to-noise ratio (SNR), including noise sources such as circuit noise and room noise
- Factor “Is” is a combination of all impairments which occur with the voice signal
- Factor “Id” represents the impairments caused by delay
- The effective equipment impairment factor “Ie-eff” represents impairments caused by low bit-rate codecs. It also includes impairment due to randomly distributed packet losses
- The advantage factor “A” allows for compensation of impairment factors when the user benefits from other types of access to the user
The default values for all input parameters used in the algorithm of the E-model, are listed in the ITU-T G.107 reference. If all parameters are set to the default values, the calculation results in a very high quality with a rating factor of R = 93.2. For a more detailed description of these parameters refer to the ITU-T G.107.
From eModel to eMOS
After obtaining the R value, a relatively standard formula to convert that to a MOS score is often applied:
1. Start out with an R-value of 93.2, and deduct from there, based on network conditions. Take the average latency, add jitter, but double the impact to latency, then add 10 for protocol latencies:
2. Implement a basic curve – deduct 4 for the R value at 160ms of latency (round trip);
3. Now, deduct 2.5 R values per percentage of packet loss:
4. Finally, convert the R-Factor into a MOS value according to the following formulas:
VoIP calls often are in the 3.5 to 4.2 MOS range. The following chart can be used as a guide for VoIP MOS testing and a good comparison for voice quality.
Maximum for G.711 codec | 4.4 |
Very satisfied | 4.3-5.0 |
Satisfied | 4.0-4.3 |
Some users satisfied | 3.6-4.0 |
Many users dissatisfied | 3.1-3.6 |
Nearly all users dissatisfied | 2.6-3.1 |
Not recommended | 1.0-2.6 |
2 Responses
The 2nd formula for 0 < R < 100 seems to make no sense. For no latency, no loss, no jitter, it gives R_initial = 93.2 , it gives MOS = 1+0.035 + 0 == 1.035. It should be near 4.5
Dear Peter,
thanks for notifying this; you are right, the reported formula doesn’t make any sense, but this is only due to a typing error; in the formula the second addend 0.035 should be multiplied by R then the correct formula is:
MOSCQE = 1 + 0.035*R +R*(R-60)*(100-R)*7*10-6
If you implement this formula (I also modified the above one) in an excel sheet the resulting graph is as in the following (as reported also in ITU-T G.107, Annex B):