ZigBee和6LoWPAN在物联网中应用对比

ZigBee和6LoWPAN在物联网中应用对比

ZigBee是现今最流行的低成本,低能耗无线Mesh网络标准。ZigBee被应用在家庭自动化(home automation),智能能源(Smart Energy),商业楼宇自动化(commercial building automation)以及其它低速率无线网络中。ZigBee是架构在802.15.4标准上的技术。ZigBee被设计用来实现物联网(sensor networks)通信标准。

6Lowpan是IPv6 over Low-power wireless Personal Area Networks的首字母缩写。这个名字起源于IETF的6LoWPAN工作组。6Lowpan的物理层和MAC层采用802.15.4标准。 与以太网、802.11等传统链路层不同,标准的IPv6协议不能直接构建在IEEE802.15.4MAC层之上。为此,需要在IPv6网络层和IEEE802.15.4MAC层之间加入一个中间层,即适配层,适配层主要功能是压缩、分片与重组、 Mesh路由。网络层采用IPV6协议,传输层采用TCP或者UDP,应用层Socket接口。

6Lowpan和ZigBee都可以用于802.15.4技术标准, 下边我们从几个方面比较一下这两个技术。

1.互操作性 Interoperability

互操作性是我们在选择无线协议时首先要考虑的。从技术术语上看,互操作意味着应用无需了解传输数据包的物理链路。ZigBee定义通行在802.15.4的节点节点进行,对应IP技术是二层。然后定义上层应用通信技术。这意味着ZigBee设备可以和其它ZigBee设备互通,假设这些设备应用同样的profile.

应用一个简单的Bridge 设备,6Lowpan支持与其它802.15.4设备的互通,同时也支持和其它IP网络的互通,如以太网和WIFI。ZigBee网络和非ZigBee网络之间的桥接需要非常复杂的应用层网关。

 2.堆栈大小/封包负载Stack size/packet overhead

比较ZigBee和6LoWPAN,必须熟悉数据包结构和开销,因为这直接关系到网络伸缩和数据负载空间。

 

Figure 1 (Archrock supplied diagram)

Fctrl: Frame control bit fields

D ep: Destination endpoint

Clst: Cluster identifier

Prof: Profile identifier

S ep: Source endpoint

APS: APT counter (sequence to prevent duplicates)

经过6LoWPAN链路的路由选址不需要额外的6LoWPAN头信息,这削减了头信息,允许了更多的负载数据空间。而且,ZigBee典型的full-feature栈是90KB,而6LoWPAN仅需要30KB。

3.安全Security

ZigBee和6LoWPAN都采用AES128技术加密,AES128是802.15.4技术标准的一部分。

4.厂商支持及成本Availability and cost

半导体行业的大多数设备商都对两个标准都支持。如Texas Instruments, Freescale and

Atmel, 提升并供应802.15.4芯片,同时支持ZigBee or 6LoWPAN.这些公司甚至提供免费的ZigBee堆栈

5.结论Conclusions

6lowpan是非常吸引人的。因为6lowpan基于IP技术-互联网的标准技术。同时,采用6lowpan可是实现与其它网络的链接,实现low-power,low-enger产品可以与网络采用。

ZigBee目前是更为流行的物联网技术,因为ZigBee联盟的支持,所以ZigBee更多的被主流厂商支持。

INTRODUCTION lwIP is a small independent implementation of the TCP/IP protocol suite. The focus of the lwIP TCP/IP implementation is to reduce the RAM usage while still having a full scale TCP. This making lwIP suitable for use in embedded systems with tens of kilobytes of free RAM and room for around 40 kilobytes of code ROM. lwIP was originally developed by Adam Dunkels at the Computer and Networks Architectures (CNA) lab at the Swedish Institute of Computer Science (SICS) and is now developed and maintained by a worldwide network of developers. FEATURES * IP (Internet Protocol, IPv4 and IPv6) including packet forwarding over multiple network interfaces * ICMP (Internet Control Message Protocol) for network maintenance and debugging * IGMP (Internet Group Management Protocol) for multicast traffic management * MLD (Multicast listener discovery for IPv6). Aims to be compliant with RFC 2710. No support for MLDv2 * ND (Neighbor discovery and stateless address autoconfiguration for IPv6). Aims to be compliant with RFC 4861 (Neighbor discovery) and RFC 4862 (Address autoconfiguration) * DHCP, AutoIP/APIPA (Zeroconf), ACD (Address Conflict Detection) and (stateless) DHCPv6 * UDP (User Datagram Protocol) including experimental UDP-lite extensions * TCP (Transmission Control Protocol) with congestion control, RTT estimation fast recovery/fast retransmit and sending SACKs * raw/native API for enhanced performance * Optional Berkeley-like socket API * TLS: optional layered TCP ("altcp") for nearly transparent TLS for any TCP-based protocol (ported to mbedTLS) (see changelog for more info) * PPPoS and PPPoE (Point-to-point protocol over Serial/Ethernet) * DNS (Domain name resolver incl. mDNS) * 6LoWPAN (via IEEE 802.15.4, BLE or ZEP) APPLICATIONS * HTTP server with SSI and CGI (HTTPS via altcp) * SNMPv2c agent with MIB compiler (Simple Network Management Protocol), v3 via altcp * SNTP (Simple network time protocol) * NetBIOS name service responder * MDNS (Multicast DNS) responder * iPerf server implementation * MQTT client (TLS support via altcp) LICENSE lwIP is freely available under a BSD license. DEVELOPMENT lwIP has grown into an excellent TCP/IP stack for embedded devices, and developers using the stack often submit bug fixes, improvements, and additions to the stack to further increase its usefulness. Development of lwIP is hosted on Savannah, a central point for software development, maintenance and distribution. Everyone can help improve lwIP by use of Savannah's interface, Git and the mailing list. A core team of developers will commit changes to the Git source tree. The lwIP TCP/IP stack is maintained in the 'lwip' Git module and contributions (such as platform ports) are in the 'contrib' Git module. See doc/savannah.txt for details on Git server access for users and developers. The current Git trees are web-browsable: http://git.savannah.gnu.org/cgit/lwip.git http://git.savannah.gnu.org/cgit/lwip/lwip-contrib.git Submit patches and bugs via the lwIP project page: http://savannah.nongnu.org/projects/lwip/ Continuous integration builds (GCC, clang): https://travis-ci.org/lwip-tcpip/lwip DOCUMENTATION Self documentation of the source code is regularly extracted from the current Git sources and is available from this web page: http://www.nongnu.org/lwip/ Also, there are mailing lists you can subscribe at http://savannah.nongnu.org/mail/?group=lwip plus searchable archives: http://lists.nongnu.org/archive/html/lwip-users/ http://lists.nongnu.org/archive/html/lwip-devel/ There is a wiki about lwIP at http://lwip.wikia.com/wiki/LwIP_Wiki You might get questions answered there, but unfortunately, it is not as well maintained as it should be. lwIP was originally written by Adam Dunkels: http://dunkels.com/adam/ Reading Adam's papers, the files in docs/, browsing the source code documentation and browsing the mailing list archives is a good way to become familiar with the design of lwIP. Adam Dunkels Leon Woestenberg
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值