Re: [6tsch] scheduling link

Qin Wang <> Thu, 19 September 2013 19:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5B31121F8475 for <>; Thu, 19 Sep 2013 12:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.428, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AKRMp4m1KLr5 for <>; Thu, 19 Sep 2013 12:56:54 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1EAD721F844D for <>; Thu, 19 Sep 2013 12:56:53 -0700 (PDT)
Received: by with SMTP id e14so16756325iej.10 for <>; Thu, 19 Sep 2013 12:56:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tQgjFGKcA8//pKRTxxMG2fPoEmYYKAg8Q7RE1b5S8FQ=; b=J6uBa4mzbdO5k0BHx8Kk4kuqudJYLROlibaR5ke/qruqwXYn1WCnHsDbtVKjgwpFQm KKP6+lhQHsweLjqnQVvw+fir1D3zO7gqUJR1459Sho1+kxS/rEvnJ7ihTwytxZhFKZ8f QC/5qmIGT5cgZiE2/lpWwE/vwjXHvG5h7Kbe4tisAbeVhmgKo5G39dNaxJwsYdty75DR E4lM5pyUAVxnbIVRmon4WRzdI55LbnZk9Nedq9jOXuyaHpmzXZYxuNJnRx+9HA/IeM6S NEXzJNaViwEq1wTqC7/zjdWPlBYIYXPTX7bDh5kXaf+SKADtt/e6k6L4gfDE77FaNdfr ToqA==
X-Gm-Message-State: ALoCoQmFhCzLhVxqYdBTdNZP9ScKmOPvHxbbRXv1MPGnEs6iGFuxMR4peljuyvkCxOxLjwsdMWH9
MIME-Version: 1.0
X-Received: by with SMTP id c6mr1960328icg.3.1379620611900; Thu, 19 Sep 2013 12:56:51 -0700 (PDT)
Received: by with HTTP; Thu, 19 Sep 2013 12:56:51 -0700 (PDT)
In-Reply-To: <>
References: <>
Date: Fri, 20 Sep 2013 03:56:51 +0800
Message-ID: <>
From: Qin Wang <>
To: mehdi sabzevari <>
Content-Type: multipart/alternative; boundary=20cf301cc4567f579e04e6c1f49e
Cc: "" <>, "" <>, "" <>, fabrice theoleyre <>
Subject: Re: [6tsch] scheduling link
X-Mailman-Version: 2.1.12
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" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 19 Sep 2013 19:57:02 -0000

Hi Mehdi,

(1) I think your question 1 is related with time source parent selection.
Please see thread " time parent selection based on EB priority" for more

(2) Regarding to your question 2, for dedicated cell reservation, the
reservation is associated not only Tx side, but also Rx side. For example,
node A and node B reserve slotOffest=5, channelOffset=12 to send data from
node A to node B. That means node A may send data to node B at the cell,
and node B should listen at the cell. If there is no data sent by node A at
the cell, node B will go to sleep, otherwise, node B receives the data sent
by node A. Regarding to how a pair of nodes reserve a cell for the
communication between them, roughly speaking, there are two approaches, one
is centralized approach, i.e. a center like PCE will set a cell to the pair
of nodes with LinkType as Tx and Rx respectively; another is distributed
approach, i.e. the pair of nodes negotiate with each other to select a cell
for their communication.

Make sense?


On Thu, Sep 19, 2013 at 11:43 AM, mehdi sabzevari <
> wrote:

> Dear All
> I have two question about the below state for scheduling of two simultaneous
> link and scheduling of Rx cell(link).
>                       A ----------> B <------------C
> 1- Inside B, with receiving of advertisement(EB) from peers A and C, Which
> peer is selected by B for scheduling of link? (I think here priority should
> exists)
> 2- I'm confused a little about scheduling links as Rx, In fact, the motes
> how find that a peer has data for it and it schedule a Rx link with it?
>     For example in A-->B link, how B find that it should schedule link? I
> think we have consider in OpenWSN that only senders can schedule a link. Is
> this correct?
> Regards
> Mehdi
> _______________________________________________
> 6tsch mailing list