Re: [lp-wan] Comments to the [lpwan] Overview re: Wi-SUN characteristics

"Liubing (Remy)" <remy.liubing@huawei.com> Thu, 20 July 2017 02:08 UTC

Return-Path: <remy.liubing@huawei.com>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AAC612EACC for <lp-wan@ietfa.amsl.com>; Wed, 19 Jul 2017 19:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1LGlsa7pGfd9 for <lp-wan@ietfa.amsl.com>; Wed, 19 Jul 2017 19:08:32 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2F7B126C2F for <lp-wan@ietf.org>; Wed, 19 Jul 2017 19:08:31 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DKW61983; Thu, 20 Jul 2017 02:08:29 +0000 (GMT)
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 20 Jul 2017 03:08:28 +0100
Received: from DGGEMM506-MBS.china.huawei.com ([169.254.4.222]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0301.000; Thu, 20 Jul 2017 10:08:15 +0800
From: "Liubing (Remy)" <remy.liubing@huawei.com>
To: "Patrick Wetterwald (pwetterw)" <pwetterw@cisco.com>, Charlie Perkins <charles.perkins@earthlink.net>, lp-wan <lp-wan@ietf.org>
CC: Bob Heile <bheile@ieee.org>, Jonathan Muñoz <jonathan.munoz@inria.fr>
Thread-Topic: [lp-wan] Comments to the [lpwan] Overview re: Wi-SUN characteristics
Thread-Index: AQHTAESas+RCO3nO0kChksG2lNL9laJa/oCAgADzvGA=
Date: Thu, 20 Jul 2017 02:08:15 +0000
Message-ID: <BB09947B5326FE42BA3918FA28765C2ED2D79B@DGGEMM506-MBS.china.huawei.com>
References: <6f22c5a9-60f6-3995-f8e5-79f0443ff748@earthlink.net> <d124d204-cf9f-cd83-b731-c2820b993913@earthlink.net> <C5A2C5EF-A65B-4F12-B29D-2015BC94A696@kinneyconsultingllc.com>
In-Reply-To: <C5A2C5EF-A65B-4F12-B29D-2015BC94A696@kinneyconsultingllc.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.180.83]
Content-Type: multipart/alternative; boundary="_000_BB09947B5326FE42BA3918FA28765C2ED2D79BDGGEMM506MBSchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090203.5970109E.002C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.4.222, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 3d2d7fe40d39b51769ec050abb75a490
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/wZ6LjGuoht8ZNc8vmOck2jSGLtw>
Subject: Re: [lp-wan] Comments to the [lpwan] Overview re: Wi-SUN characteristics
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 02:08:35 -0000

Hello folks,
I agree with Charlie and Patrick Wetterwald that Wi-SUN FAN uses some different terminologies and should be illustrated as a column in Figure.8 of the LPWAN overview draft.

As mentioned by Patrick Kinney, the packet size of Wi-SUN can also be included.

Best regards,
Remy
From: Pat.kinney@kinneyconsultingllc.com [mailto:pat.kinney@kinneyconsultingllc.com]
Sent: Thursday, July 20, 2017 3:10 AM
To: Charlie Perkins
Cc: lp-wan; Bob Heile; Zhangmingui (Martin); Jonathan Muñoz; Liubing (Remy)
Subject: Re: [lp-wan] Comments to the [lpwan] Overview re: Wi-SUN characteristics

You raised some very good points about Wi-SUN, Charlie.
Perhaps another point could be the ability to change the PHY characteristics such as modulations, packet size, or FEC; or change out the whole PHY for a different band.

Patrick Kinney
Kinney Consulting
+1.847.960.3715
pat.kinney@kinneyconsultingllc.com<mailto:pat.kinney@kinneyconsultingllc.com>

On Jul 18, 2017, at 23:07, Charlie Perkins <charles.perkins@earthlink.net<mailto:charles.perkins@earthlink.net>> wrote:

Hello folks,

I'd like to suggest some additional text to be included in the Wi-SUN overview section of the document.  I think it is important to emphasize the following characteristics.  These comments can be viewed as more or less the distillation of information described at longer length in our individual Internet Draft contribution submitted earlier about Wi-SUN.  We have received many comments about that draft, and it needs to be significantly revised and resubmitted as soon as possible.  But the [lpwan] Overview document is in Last Call, and we don't have time to revise our individual draft before the end of Last Call.

Given a little more time after this busy week, I would also like to include a fuller description about the Wi-SUN mesh protocol choices.  If that is acceptable, I will provide text next week.

Regards,
Charlie P.
-----------------------------------------------------------------------------------------------------------

-Coverage

The range of Wi-SUN FAN is typically 2~3 km in line of sight, matching the needs of neighborhood area networks, campus area networks, or corporate area networks. The range can also be extended via multi-hop networking.



- High bandwidth, low latency

Wi-SUN's relatively high bandwidth, i.e. up to 300 kbps [FANTPS], enables remote update and upgrade of devices so that they can handle new applications, extending their working life. Some IoT applications may require on-demand control, e.g. on-demand metering in AMI, device control in distribution automation. Wi-SUN supports these requirements by providing high bandwidth, low latency (0.02s) and bi-directional communication.



- Low power consumption

FAN devices draw less than 2 uA when resting and only 8 mA when listening [COM]. Such devices can maintain a long lifetime even if they are frequently listening. For instance, suppose the device transmits data for 10 ms once every 10 s; theoretically, a battery of 1000 mAh can last more than 10 years.



- Mesh topology

Wi-SUN FAN mesh networks offer self-forming and self-healing capabilities. When a new device is powered up, it can automatically discover communication peers. If the link is interrupted by obstacles, a device can switch to alternative redundant paths. The reliability of Wi-SUN has been proven for years in harsh and remote environments.



- Scalability

10s of millions Wi-SUN FAN devices have been deployed all over the world, including several deployments with more than 1 million devices [COM]. This demonstrates the scalability of Wi-SUN FAN in urban, suburban and rural environments.





The following references could be added in the LPWAN overview draft:

[COM] Wi-SUN Alliance, “Comparing IoT Networks at a Glance”, May 2017.

[FANTPS] Wi-SUN Alliance, "Technical Profile Specification Field Area Network", May 2016.



Figure.8 needs a column for Wi-SUN:

<image001.png>



Another paragraph could be added regarding the Wi-SUN security solution, something along the following lines.


Wi-SUN has made it a design goal to rely on industry standard security solutions instead of special-purpose or proprietary methods.  In this way, users and equipment vendors can have a high degree of confidence that their system will truly be secure.  Moreover it will be easier to provide secure interfaces to other system modules and components, which are more likely to support standard security protocols without special purpose coding.


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

Regards,
Charlie P.

<Figure 8 terminology.EFX>
_______________________________________________
lp-wan mailing list
lp-wan@ietf.org<mailto:lp-wan@ietf.org>
https://www.ietf.org/mailman/listinfo/lp-wan