Re: [6tisch] [6TISCH] Specify the number of cells to be added or deleted in SF0

Tengfei Chang <tengfei.chang@gmail.com> Wed, 02 November 2016 15:00 UTC

Return-Path: <tengfei.chang@gmail.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6A0512965C for <6tisch@ietfa.amsl.com>; Wed, 2 Nov 2016 08:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBNq-f84lwOS for <6tisch@ietfa.amsl.com>; Wed, 2 Nov 2016 08:00:03 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1C9D129426 for <6tisch@ietf.org>; Wed, 2 Nov 2016 08:00:02 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id t79so42818092wmt.0 for <6tisch@ietf.org>; Wed, 02 Nov 2016 08:00:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=e4sUtkZ27Y+fOevMhdVpBIyCNldBVMtEeXC+uLa89Qs=; b=nm0VBIaaL3RuRItpxkSIK4Zb+yChLtFLq37lF5R9lqIl+zScO5wKGa0Jr12PxuqlhV zemunjUmZBZYnEazO5isTTs7BPhDZDg2gCGnj/MTD9WyM6+hOIOpY2Y7wPfLuXS7no6m TTtCKBekZdMuIGUvhtVvUralSfgyvhWAhALUlJlIDOpzjmw2roAwRPrADnqxekzkIN5w DH+4EFwP6l3tj0dmkBVrhcHebJwUpa+IriSLfVhe/mi8m17fkKl+01GCzlHvUvD6RRX8 zW82jWZ/qLe2zpchnr2DRzqR3Dj7I2wmFWuMAxxEzSC54DuXOq8JcUmFaLR+5aezrMDx k9AA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=e4sUtkZ27Y+fOevMhdVpBIyCNldBVMtEeXC+uLa89Qs=; b=Pj7TPFgGAFNYyIfLZajb/NlugbA4p4DON9edoZBIFiAEywS37VvFhEA33pNqGuG4td 9EvXEYJSDqJ469wGNUNmYcX9QUF5VVmiWWPO1aG+F4pyyFvQVOzWAPpshs43Qq9NlA50 EPpeTQxWC80w0tTE0FmaXYWM8buD/LzMg/9cGpe+tTgVK/Wf4u0ZA3tkI174b/C/GLPt W8A1Vnh+28JZYomUoV8Nh9DCC5N2kyotzjYKIoSe45cMpaUXgOKjvZsUjniLky+mu9cz Q15nAF2ltjqxN9CawNa3seEqt1oTughErTtsLPunlzDKoXHqXwlaOgJdW446B6WiUhQk QSpw==
X-Gm-Message-State: ABUngvdK6mkP4QrAUYlJERcy53a3NP+mqAJl7gOL/mLmkcNmDZhajN//45UieuR1bDmTzPTrzfeIQ6rWrocvWw==
X-Received: by 10.194.87.170 with SMTP id az10mr3880033wjb.189.1478098801109; Wed, 02 Nov 2016 08:00:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.64.131 with HTTP; Wed, 2 Nov 2016 08:00:00 -0700 (PDT)
In-Reply-To: <CAH7SZV9J9Ds=SEB3j0oMuybjzao6k0ZaWgHWbfU=Gu_GNCq=tQ@mail.gmail.com>
References: <CAAdgstQnts2ZNqjKOzG76MDZEKcVRunxU92OvWw19sHNnZtzuw@mail.gmail.com> <CAAYrgaApm=2vNQ2etMKmMA4+2dYSxr19eraNM-AAgTQnOXN5dg@mail.gmail.com> <CAH7SZV9J9Ds=SEB3j0oMuybjzao6k0ZaWgHWbfU=Gu_GNCq=tQ@mail.gmail.com>
From: Tengfei Chang <tengfei.chang@gmail.com>
Date: Wed, 02 Nov 2016 16:00:00 +0100
Message-ID: <CAAdgstROKbVhkdzi+sXdvhUV-FgXwQxkAL4-w2eUM7rMSY_f_g@mail.gmail.com>
To: "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl>
Content-Type: multipart/alternative; boundary="089e010d867cfbafea054052b1d0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/6tisch/e5mks2DnQXOMoABdhRF8ujLWP2U>
Cc: Nicola Accettura <nick.accettura@gmail.com>, "6tisch@ietf.org" <6tisch@ietf.org>
Subject: Re: [6tisch] [6TISCH] Specify the number of cells to be added or deleted in SF0
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Nov 2016 15:00:05 -0000

Hi Nicola, Diego,

I see. Thanks for all your explanation!

It would be very helpful if we can see some recommended number of cell or
advice how to choose the number of cell in the draft.
As Sixtop left lots of details in SF, my thought is SF should give more
specific information or clues for developer/implementer to implement.
Of course, those information will come out from real experiments.

Thanks for all you replying!

Tengfei


On Wed, Nov 2, 2016 at 3:42 PM, Prof. Diego Dujovne <
diego.dujovne@mail.udp.cl> wrote:

> Nicola,
>            I agree with your comment, but the cell estimation
> algorithm changed: we now estimate the number of required
> cells from the number of requested cells (to add or delete)
> and the number of effectively used cells. What is still not clear
> to me is if the simulation results from the OTF paper is still valid
> given this change. To enable the cell estimation algorithm without
> packet loss, we need to guarantee always a small amount of
> overprovisioning.
>           Let me bring the lost text (from OTF) back to SF0.
>           Regards,
>
>                                          Diego
>
> 2016-11-02 11:36 GMT-03:00 Nicola Accettura <nick.accettura@gmail.com>:
>
>> Hi Tengei,
>>
>> the problem you are rising is that you would like to see a number of
>> cells to add/delete when comparing required and deleted cells.
>>
>> The ancestor of SF0, namely OTF, used to specify the following sentence:
>>
>> The number of soft cells to be scheduled/deleted for bundle resizing
>>    is out of the scope of this document and implementation-dependant.
>>
>> In fact, we wanted to let that choice being implementation specific.
>>
>> What you are proposing (the exact number of cells to add or delete) was
>> already implemented in the 6tisch simulator, and it is in fact something
>> that has already been used and tested in the following papers:
>>
>> Palattella et al., On-the-Fly Bandwidth Reservation for 6TiSCH Wireless
>> Industrial Networks, IEEE Sensors Journal, 2015
>>
>> Muraoka et al., Simple Distributed Scheduling with Collision Detection in
>> TSCH Networks, IEEE Sensors Journal, 2016
>>
>> But, as already said, this is just a way you can allocate cells. I guess
>> we don't want to restrict that setting to a particular algorithm choice.
>>
>> Hope this helps.
>>
>> Nicola
>>
>> 2016-11-02 14:59 GMT+01:00 Tengfei Chang <tengfei.chang@gmail.com>:
>>
>>> Hi All,
>>>
>>> I am reading the SF0-02 version which is just released few days ago.
>>>
>>> In the SF0 Allocation Policy section, the policy said
>>>
>>>    1.  If REQUIREDCELLS<(SCHEDULEDCELLS-SF0THRESH), delete one or more
>>>        cells.
>>>    2.  If (SCHEDULEDCELLS-SF0THRESH)<=REQUIREDCELLS<=SCHEDULEDCELLS, do
>>>        nothing.
>>>    3.  If SCHEDULEDCELLS<=REQUIREDCELLS, add one or more cells.
>>>
>>>
>>>
>>> Personally thinking, add/delete one cells may call the sixtop many times
>>> which is not efficiency, add/delete more cells is not clear to the
>>> implementer.
>>> I guess there is a decision to say when to add one cell and when to add
>>> more cells. But I didn't find it in SF0 draft.
>>> Is there any reason why we doesn't say specific number of cells?
>>>
>>> If no, I think we can add/remove the number of cells to make sure the
>>> scheduled cells equals to the required cells plus half of SF0THRESH, which
>>> will help stabilize a little bit of the SF0, in case the sixtop is calling
>>> too often.
>>>
>>> Which means: if SCHEDULEDCELLS<=REQUIREDCELLS:
>>>
>>> 1. when there is no cell in the schedule add one cell
>>> 2. when there is at least one cell in schedule, add
>>> REQUIREDCELLS-SCHEDULEDCELLS+(SF0THRESH+1)/2 number of cells
>>>
>>> if REQUIREDCELLS<(SCHEDULEDCELLS-SF0THRESH))
>>>
>>> 1. When required cells equals 0, remove all cells but keep one in
>>> schedule
>>> 2. when required cells is greater than 0, remove  SCHEDULEDCELLS-
>>> REQUIREDCELLS-(SF0THRESH+1)/2
>>>
>>> Does this make sense?
>>>
>>> Tengfei
>>>
>>> --
>>> Chang Tengfei,
>>> Pre-Postdoctoral Research Engineer, Inria
>>>
>>> _______________________________________________
>>> 6tisch mailing list
>>> 6tisch@ietf.org
>>> https://www.ietf.org/mailman/listinfo/6tisch
>>>
>>>
>>
>> _______________________________________________
>> 6tisch mailing list
>> 6tisch@ietf.org
>> https://www.ietf.org/mailman/listinfo/6tisch
>>
>>
>
>
> --
> DIEGO DUJOVNE
> Profesor Asociado
> Escuela de Informática y Telecomunicaciones
> Facultad de Ingeniería - Universidad Diego Portales - Chile
> www.ingenieria.udp.cl
> (56 2) 676 8125
>



-- 
Chang Tengfei,
Pre-Postdoctoral Research Engineer, Inria