[xrblock] MoS reference support in QoE draft
Qin Wu <bill.wu@huawei.com> Thu, 18 October 2012 02:37 UTC
Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF4B521F853E for <xrblock@ietfa.amsl.com>; Wed, 17 Oct 2012 19:37:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.626
X-Spam-Level:
X-Spam-Status: No, score=-3.626 tagged_above=-999 required=5 tests=[AWL=-1.181, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_23=0.6, J_CHICKENPOX_54=0.6, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HiPtmj+vt0AI for <xrblock@ietfa.amsl.com>; Wed, 17 Oct 2012 19:37:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 925BE21F853D for <xrblock@ietf.org>; Wed, 17 Oct 2012 19:37:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ALS77665; Thu, 18 Oct 2012 02:37:23 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 18 Oct 2012 03:35:42 +0100
Received: from SZXEML446-HUB.china.huawei.com (10.82.67.184) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 18 Oct 2012 10:36:32 +0800
Received: from w53375 (10.138.41.149) by szxeml446-hub.china.huawei.com (10.82.67.184) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 18 Oct 2012 10:36:25 +0800
Message-ID: <CCD13E4BD5D44ABCB425F337CCB3AF1C@china.huawei.com>
From: Qin Wu <bill.wu@huawei.com>
To: xrblock@ietf.org
Date: Thu, 18 Oct 2012 10:36:24 +0800
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0350_01CDAD1C.6BE59530"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Originating-IP: [10.138.41.149]
X-CFilter-Loop: Reflected
Subject: [xrblock] MoS reference support in QoE draft
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 02:37:30 -0000
Hi, MoS reference are referred to one QoE related parameter or option that is used to distinguish narrowband speech from wideband speech or low resolution video from high resolution for video For audio, MOS values for narrowband, wideband occupy the same range. For video application,MoS values for SD resolution, HD resolution video also occupy the same ranges,therefore it is important for the QoE block to indicate what the MOS reference is. In the current published media stream quality assessment documents, i.e., P.NAMS, P.NBAMS, they are splitted to support lower resolution application and higher resolution application respectively, this also tell us it is necessary for QoE block to indicate what the MoS reference is. In order to support MoS reference, with Alan's input, we like to propose the following changes to QoE draft. 1.Section 3.1, last sentence OLD TEXT: " The encoding of QoE metrics block payload consists of a series of 32 bit units called segments that describe MOS Type, MoS algorithm and MoS value. Editor's note: MOS values for narrowband, wideband, super wideband and fullband codecs; these MOS values occupy the same range. For video application,MoS values for SD resolution, HD resolution video also occupy the same ranges and hence the QoE block needs to indicate what the MOS reference is. Editor's Note: If we add MoS reference concept, 32 bit segment is not sufficient. Therefore it was suggested to expand 32 bit segment into 48 bit segment to support MoS reference feature. The QoE Metrics Block has the following format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=QMB | I | Reserved | Block Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment 1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ .................. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment n | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ " NEW TEXT: " The encoding of QoE metrics block payload consists of a series of 48-bit units called segments that describe MOS Type, MoS Reference, MoS algorithm and MoS value. The QoE Metrics Block has the following format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BT=QMB | I | Reserved | Block Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SSRC of source | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment 1 (bit0-31) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment 1 (bit32-47) | Segment 2 (bit0-15) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment 2 (bit16-47) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ .................. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment n | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |.................. +-+-+-+-+-+-+-+-+-+-+-+-+-+ " 2. Section 3.2.1 OLD TEXT: " 3.2.1. Single Stream per SSRC Segment +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |S| MT |CAlg | PT |Rsv. | MOS Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +----------------------------+--------------------------------------+ | Editor's Note: If we add | Editor's Note: Shall we need to | | MoS reference concept, we | support MoS Scaling concept in the | | should give a definition | future draft? One point on the list | | of MoS reference which | is MoS Scaling concept is implicitly | | covers both audio | used within the industry when | | application and video | quoting MOS scores for codecs and | | application. | measurements. | +----------------------------+--------------------------------------+ Segment Type (S): 1 bit This field is used to identify the segment type used in this report block. A zero identifies this as a single stream segment. Single stream means there is only one media stream carried in one RTP stream. The single stream segment can be used to report the MoS value associated with this media stream identified by SSRC. If there are multiple media streams and they want to use the single stream per SSRC segment to report the MOS value, they should be carried in the separate RTP streams with different SSRC. In this case, multiple QoE Metrics Blocks are required to report the MOS value corresponding to each media stream using single stream segment. Calculation Algorithm (CALg):3 bits 000 - ITU-T P.564 Compliant Algorithm [P.564] (Voice) 001 - G.107 [G.107] (Voice) 010 - ETSI TS 101 329-5 Annex E [ ETSI] (Voice) 011 - TTC JJ201.01 [TTC] (Voice) 100 - ITU-T P.1201 [P.1201] (Multimedia) 101 - ITU-T P.1202 [P.1202] (Video) 110~111 - Reserved for future extension. MOS Value: 14 bits The estimated mean opinion score for multimedia application quality is defined as including the effects of delay,loss, discard,jitter and other effects that would affect multimedia quality . It is expressed in numeric format 6:8 with the value in the range 0.0 to 63.996. The valid the measured value ranges from 0.0 to 50.0, corresponding to MoS x 10 as for MoS. If the measured value is over ranged, the value 0xFFFE SHOULD be reported to indicate an over-range measurement. If the measurement is unavailable, the value 0xFFFF SHOULD be reported. Values other than 0xFFFE,0xFFFF and the valid range defined above MUST NOT be sent and MUST be ignored by the receiving system. " NEW TEXT: " 3.2.1. Single Stream per SSRC Segment +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 0 | MT | MR | CAlg | PT | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MoS Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Segment Type (S): 2 bits This field is used to identify the segment type used in this report block. A zero identifies this as a single stream segment. The values 2-3 are reserved for future use.Single stream means there is only one media stream carried in one RTP stream. The single stream segment can be used to report the MoS value associated with this media stream identified by SSRC. If there are multiple media streams and they want to use the single stream per SSRC segment to report the MOS value, they should be carried in the separate RTP streams with different SSRC. In this case, multiple QoE Metrics Blocks are required to report the MOS value corresponding to each media stream using single stream segment. MoS Reference (MR):4 bits This field is used to indicate the MOS reference to be reported. The MoS reference is defined as follows: 0000 - Narrowband (3.4kHz) Speech 0001 - Wideband (7kHz) Speech 0010 - Standard Definition (SD) Resolution Video 0011 - High Definition (HD) Resolution Video 0100~1111 - Reserved for future definitions. Note that the frequency described above for Speech refers to the audio bandwidth and not the sample rate (e.g. an 8kHz sample rate is used on traditional telecom networks and audio bandwidth is filtered to 3.4kz).SD Resolution Video refers to lower resolution media (e.g.,Mobile TV) while HD Resolution Video refers to higher resolution media (e.g.,IPTV). Calculation Algorithm (CALg):6 bits 000000 - ITU-T P.564 Compliant Algorithm [P.564] (Voice) 000001 - G.107 [G.107] (Voice) 000010 - ETSI TS 101 329-5 Annex E [ ETSI] (Voice) 000011 - TTC JJ201.01 [TTC] (Voice) 000100 - ITU-T P.1201 [P.1201] (Multimedia) 000101 - ITU-T P.1202 [P.1202] (Video) 000110~111111 - Reserved for future extension. MOS Value: 16 bits The estimated mean opinion score for multimedia application quality is defined as including the effects of delay, loss, discard,jitter and other effects that would affect multimedia quality . It is expressed in numeric format 8:8 with the value in the range 0.0 to 255.996. The valid the measured value ranges from 10.0 to 50.0, corresponding to MoS x 10 as for MoS. If the measured value is over ranged, the value 0xFFFE SHOULD be reported to indicate an over-range measurement. If the measurement is unavailable, the value 0xFFFF SHOULD be reported. Values other than 0xFFFE,0xFFFF and the valid range defined above MUST NOT be sent and MUST be ignored by the receiving system. " 3. Section 3.2.2 OLD TEXT" " 3.2.2. Multi-Channel audio per SSRC Segment +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |S| MT |CAlg | PT |CHID | MOS Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Segement Type (S): 1 bit This field is used to identify the segment type used in this report block. A one identifies this as a multi-channel audio segment. Calculation Algorithm (CALg):3 bits 000 - ITU-T P.564 Compliant Algorithm [P.564] (Voice) 001 - G.107 [G.107] (Voice) 010 - ETSI TS 101 329-5 Annex E, [ ETSI] (Voice) 011 - TTC JJ201.01 [TTC] (Voice) 100~111 - Reserved for future extension. " NEW TEXT: " 3.2.2. Multi-Channel audio per SSRC Segment +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1 | MT | MR | CAlg | PT | CHID |Reserve| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MoS Value | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Segment Type (S): 2 bits This field is used to identify the segment type used in this report block. A one identifies this as a multi-channel audio segment. The values 2-3 are reserved for future use. MoS Reference (MR): 4 bits This field is used to indicate the MOS reference to be reported. The MoS reference is defined as follows: 0000 - Narrowband (3.4kHz) Speech 0001 - Wideband (7kHz) Speech 0010~1111 - Reserved for future definitions. Note that the frequency described above for Speech refers to the audio bandwidth and not the sample rate (e.g. an 8kHz sample rate is used on traditional telecom networks and audio bandwidth is filtered to 3.4kz). Calculation Algorithm (CALg):6 bits 000000 - ITU-T P.564 Compliant Algorithm [P.564] (Voice) 000001 - G.107 [G.107] (Voice) 000010 - ETSI TS 101 329-5 Annex E, [ ETSI] (Voice) 000011 - TTC JJ201.01 [TTC] (Voice) 000100~111111 - Reserved for future extension. " Regards! -Qin