Re: [xrblock] Transport of I.D-xrblock-rtcp-xr-qoe style quality datain IPFIX

Michael Krüger <> Tue, 24 July 2012 07:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B06BA11E8125 for <>; Tue, 24 Jul 2012 00:08:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3fkWaKl5MLlF for <>; Tue, 24 Jul 2012 00:08:36 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D383A11E8119 for <>; Tue, 24 Jul 2012 00:08:35 -0700 (PDT)
X-Footer: dm9pcGZ1dHVyZS5jb20=
Received: from ([]) (authenticated user by (Kerio Connect 7.4.2) (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)); Tue, 24 Jul 2012 08:54:57 +0200
Message-ID: <>
Date: Tue, 24 Jul 2012 09:08:19 +0200
From: Michael Krüger <>
Organization: VOIPFUTURE
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Qin Wu <>
References: <><> <> <> <> <>
In-Reply-To: <>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [xrblock] Transport of I.D-xrblock-rtcp-xr-qoe style quality datain IPFIX
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Jul 2012 07:08:36 -0000

Hi, Qin,

Am 24.07.12 05:20, schrieb Qin Wu:
> Hi,Michael:
> Thank for your clarification.
> One thing I am not clear to your idea  is how to calculate MoS value or Rating value based on stream data from multiple sources?
> Currently in QoE XR draft, we support MoS calculation per SSRC or MoS calculation per audio channel?
> It seems you claim you can calculate MoS values based on audio data from multi-channels? 
> Is that MoS value is the weighted mean of MoS value of each channel? If in that case, what the weight for each 
> channel MoS calculation?
> Maybe this is just implemenation specific issue, however I am interested to listen to that.
Thank you for your interest.
Of course we have not reinvented MOS. Our approach is related to ITU-T
P.564. The audio test samples used in that standard have a minimum
length of 8-seconds. We therefore assume that one must evaluate at least
this period of time, to determine a reliable MOS value. What we try to
achieve with monitoring live traffic, is to determine for every
individual flow of a VoIP call MOS values for every 10-second segment.
This provides us with many MOS values over the duration of an individual
call. Most network impairments are of transient nature, so for every
call the result will be a distribution of MOS scores falling into one of
the 5 classes. Depending on the number of seconds in each of the
classes, it is possible to assess how many seconds of a call have been
with which quality on the MOS scale 1-5. If this data is available for a
single flow, call, etc. the seconds of the 5 classes can be aggregated
over all flows/calls performed between VoIP operators, operators and
customers, or simply SIP-trunks. This will e.g. allow to come up with
new SLA agreements where the agreement could possibly be that 99% of all
VoIP minutes must be in the highest MOS class. The accuracy of this is
pretty high, since one determines MOS values for only a few seconds of a
call, bringing every impairment to attention via a lower MOS value for
the segment in which the impairment occurred. No averaging over a call
is done, so the distribution of MOS values like this, truly reflects the
monitored quality.

Does this make sense to you as well?


> Regards!
> -Qin