Re: [xrblock] Calculation of delay metrics defined in the Delay Block

Qin Wu <bill.wu@huawei.com> Fri, 28 October 2011 10:13 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 8492221F84AD for <xrblock@ietfa.amsl.com>; Fri, 28 Oct 2011 03:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.329
X-Spam-Level:
X-Spam-Status: No, score=-5.329 tagged_above=-999 required=5 tests=[AWL=0.385, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H7Sjl034im47 for <xrblock@ietfa.amsl.com>; Fri, 28 Oct 2011 03:13:32 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 6B2C721F8494 for <xrblock@ietf.org>; Fri, 28 Oct 2011 03:13:32 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTR006ZJTMORC@szxga04-in.huawei.com> for xrblock@ietf.org; Fri, 28 Oct 2011 18:11:13 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LTR000Q0TME5F@szxga04-in.huawei.com> for xrblock@ietf.org; Fri, 28 Oct 2011 18:11:12 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AEM73509; Fri, 28 Oct 2011 18:11:12 +0800
Received: from SZXEML411-HUB.china.huawei.com (10.82.67.138) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 28 Oct 2011 18:11:03 +0800
Received: from w53375q (10.138.41.130) by szxeml411-hub.china.huawei.com (10.82.67.138) with Microsoft SMTP Server (TLS) id 14.1.270.1; Fri, 28 Oct 2011 18:10:52 +0800
Date: Fri, 28 Oct 2011 18:10:49 +0800
From: Qin Wu <bill.wu@huawei.com>
X-Originating-IP: [10.138.41.130]
To: zhaojing@sttri.com.cn, xrblock <xrblock@ietf.org>
Message-id: <800EEFA4D9B8409F8DFE21EA2A7CFBCA@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
Content-type: multipart/alternative; boundary="Boundary_(ID_Z3GAdJw6LIkd0/iO7vhXtg)"
X-Priority: 3
X-MSMail-priority: Normal
X-CFilter-Loop: Reflected
References: <29087808.18541319790323615.JavaMail.root@ent8>
Subject: Re: [xrblock] Calculation of delay metrics defined in the Delay Block
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: Fri, 28 Oct 2011 10:13:33 -0000

End System Delay is part of  Network Round trip delay(Transmission Delay is another part of Network Round Trip Delay).
The End System Delay is calculate based on sending side internal Delay and receiving side internal Delay.
Sending side internal Delay = Accumulation and Encoding Delay
Reciving Side Internal Delay = Jitter Buffer Delay + Decoding and Playout Buffer Delay.
In my understanding, the End System Delay can be measured using DLSR or DLRR. We can choose mean value of DLSR and DLRR to stand
for the average End System Delay.

Regards!
-Qin
  ----- Original Message ----- 
  From: zhaojing@sttri.com.cn 
  To: xrblock 
  Sent: Friday, October 28, 2011 4:25 PM
  Subject: Re: [xrblock] Calculation of delay metrics defined in the Delay Block


  Hi, Qin:

  Would you like to explain to me how End System Delay is calculated?

  Is it based on DLSR or something else? It looks like a internal calculation.

  Regards!

  -JingZhao



    a.. From: Qin Wu <bill.wu at huawei.com> 
    b.. To: zhaojing at sttri.com.cn, xrblock <xrblock at ietf.org> 
    c.. Date: Thu, 20 Oct 2011 18:34:53 +0800 
    d.. References: <22819783.8901319076443866.JavaMail.root at ent11> 
    e.. List-id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org> 

------------------------------------------------------------------------------


        Hi,jing: 
        Please refere to RFC3550. 
        The round trip time computation method is defined as a example in the figure 2 of RFC3550. 
         
        Regards! 
        -Qin 
          ----- Original Message ----- 
          From: zhaojing at sttri.com.cn 
          To: xrblock 
          Sent: Thursday, October 20, 2011 10:07 AM 
          Subject: [xrblock] Calculation of delay metrics defined in the Delay Block 


          Hi, 
          I have read Delay draft avaiable at: 
          http://tools.ietf.org/html/draft-ietf-avt-rtcp-xr-delay-02 
          It is not clear to me how each metric is calculated, For example, 
          it is said Mean Network Round Trip Delay metric is ypically determined 
          using RTCP SR/RR? 
          I am not sure I understand the rationale? Who would like to explain a little to me? 
          Regards! 
          jing Zhao   
          ShangHai Research Institute of China Telecom Corporation Limited.  



------------------------------------------------------------------------------


  _______________________________________________
  xrblock mailing list
  xrblock@ietf.org
  https://www.ietf.org/mailman/listinfo/xrblock