[16NG] IEEE 802.16 QoS parameters

"Denio Mariz" <deniomariz@gmail.com> Tue, 05 June 2007 19:04 UTC

Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HveKC-0003l9-PL; Tue, 05 Jun 2007 15:04:12 -0400
Received: from 16ng by megatron.ietf.org with local (Exim 4.43) id 1HveKB-0003l4-Lc for 16ng-confirm+ok@megatron.ietf.org; Tue, 05 Jun 2007 15:04:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HveKB-0003kw-C4 for 16ng@ietf.org; Tue, 05 Jun 2007 15:04:11 -0400
Received: from an-out-0708.google.com ([209.85.132.248]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HveKA-0006NN-5i for 16ng@ietf.org; Tue, 05 Jun 2007 15:04:11 -0400
Received: by an-out-0708.google.com with SMTP id c17so442072anc for <16ng@ietf.org>; Tue, 05 Jun 2007 12:04:09 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HabhD391ht7dyqheAFekBBWXasqu/s0O5nW7PT283txfnetIFL4dDbj7p8xom7SNhtDEevPtJ7HAohgmLrBaCe9AOs2U2QEET15Y9w1RHbHYWV14Nt8W3X8FXTELr7rh8sJV0VftO3egQH7Wo3GrXVzumm2FyVYXstDwpUoXL4A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=I5rLZHj7KWgScHqGewnOEFfliCRwxULURNAHw+qBQb36FUrzfOZNrTe2+K0B1BDqy7qDSfMEzGj1V9HZM9hMWb/vYwiO+CuOIwx8Juy5Xxc065PXGApldALK7+Lg+iGEDwTlkKGB5B2JyIgcJyCYkQHEHlPsC0HWFxl1ute39nc=
Received: by 10.100.32.1 with SMTP id f1mr3543856anf.1181070217930; Tue, 05 Jun 2007 12:03:37 -0700 (PDT)
Received: by 10.100.111.15 with HTTP; Tue, 5 Jun 2007 12:03:37 -0700 (PDT)
Message-ID: <dde9f3ed0706051203i2d907654v3fbbbeca3cd00de7@mail.gmail.com>
Date: Tue, 5 Jun 2007 15:03:37 -0400
From: "Denio Mariz" <deniomariz@gmail.com>
To: 16ng@ietf.org
In-Reply-To: <dde9f3ed0706051201i21879de2ic8ee3d2ea9a00e98@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <dde9f3ed0706051201i21879de2ic8ee3d2ea9a00e98@mail.gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: [16NG] IEEE 802.16 QoS parameters
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: denio@gprt.ufpe.br
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org

Hi,

IEEE 802.16-2004 document defines some QoS parameters for admitted
connections, which includes maximum latency and maximum jitter. They
are defined as:

=======
Maximum latency - The value of this parameter specifies the maximum
latency between the reception of a packet by the BS or SS on its
network interface and the forwarding of the packet to its RF
Interface.

Maximum Jitter - This parameter defines the maximum delay variation
(jitter) for the connection.
======

Assuming D1 and D2 as the delay measured for two consecutive packets,
it is common for end-to-end systems to compute the jitter J as
J=|D1-D2|.

I am studying a scheduling algorithms for the download, which must run
inside the BS. This means that D1 and D2 are not available (or must be
avoided, since it would depend on measuring them at the mobile
terminal). So I am assuming that the algorithm must only consider
information from inside the BS (more specifically from queue
statistics).

So, I am wondering if it is possible to compute correctly the jitter
for packets assuming you can not watch the receiving end of the stream
and only consider info from the sender side.

TIA,

Denio Mariz


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www1.ietf.org/mailman/listinfo/16ng