畢業(yè)設(shè)計外文資料翻譯-擴(kuò)展的低功耗無線互聯(lián)網(wǎng)架構(gòu)的設(shè)計與實(shí)現(xiàn)

1、畢業(yè)設(shè)計外文資料翻譯學(xué) 院： 專業(yè)班級： 學(xué)生姓名： 學(xué) 號： 指導(dǎo)教師： 外文出處：(外文)G JonathanW.Hui美 An Extended Internet Architecture for Low-Power Wireless Networks-Design and Implementation,2008 附 件：1.外文資料翻譯譯文； 2.外文原文指導(dǎo)教師評語：該同學(xué)的英文專業(yè)資料術(shù)語翻譯基本準(zhǔn)確，體現(xiàn)了一定的專業(yè)英語水平。翻譯材料能夠與原文保持一致，能正確表達(dá)出原文意思。翻譯字、詞數(shù)滿足要求。翻譯材料的格式基本符合要求。該同學(xué)較好的完成了外文文獻(xiàn)翻譯工作。簽名： 2015年1

2、0月14日第第 頁，共9頁1外文資料翻譯 譯文擴(kuò)展的低功耗無線互聯(lián)網(wǎng)架構(gòu)的設(shè)計與實(shí)現(xiàn)10.結(jié)論10.1.體系結(jié)構(gòu)的回溯在過去的十年中，對無線傳感器網(wǎng)絡(luò)和互聯(lián)網(wǎng)架構(gòu)，尤其是IPv6的互聯(lián)網(wǎng)架構(gòu)的研究，都取得了極大的進(jìn)步。因此，重新審視這個在大量傳感器網(wǎng)絡(luò)研究基礎(chǔ)上形成的假設(shè)是有意義的。通過構(gòu)建以IPv6為基礎(chǔ)的高質(zhì)量傳感器網(wǎng)絡(luò)，我們發(fā)現(xiàn)發(fā)展的兩個領(lǐng)域?qū)嶋H上有很強(qiáng)的互補(bǔ)性。IPv6架構(gòu)基本滿足傳感器網(wǎng)絡(luò)s的獨(dú)特需求，在很多情況下比分別進(jìn)行的任何努力出不針對任何特定網(wǎng)絡(luò)制式的關(guān)注更好。然而，在一些情況下，而結(jié)構(gòu)是合適的，對特定網(wǎng)絡(luò)RFC和實(shí)現(xiàn)是沒有。擴(kuò)展不得不被創(chuàng)建為包括特別需要和這些擴(kuò)展自然由系統(tǒng)

3、使用的選項(xiàng)支持。傳感器網(wǎng)絡(luò)研究更側(cè)重于網(wǎng)絡(luò)協(xié)議的算法和機(jī)制，而比在更廣泛意義上的網(wǎng)絡(luò)。分層的IPv6形式，地址，標(biāo)題格式，CON網(wǎng)絡(luò)配給管理，路由和轉(zhuǎn)發(fā)提供缺少的結(jié)構(gòu)。并且，在許多情況下，在傳感器網(wǎng)絡(luò)空間開發(fā)到一些長期挑戰(zhàn)問題提供了優(yōu)雅的解決方案傳統(tǒng)的IETF的方法。我們不僅ND網(wǎng)絡(luò)連接的接近模擬了在傳感器網(wǎng)絡(luò)如此普遍的傳播和收集的結(jié)構(gòu)，但涓流機(jī)制提供達(dá)到一個優(yōu)雅的手段。共識，快速響應(yīng)變化，成為被動的穩(wěn)定狀態(tài)。需要特別指出的是，我們不必放棄分層，以滿足嚴(yán)厲的許多優(yōu)點(diǎn)傳感器網(wǎng)絡(luò)節(jié)點(diǎn)的資源限制。如果有什么事情，通過分層方法獲得的重點(diǎn)往往產(chǎn)生比當(dāng)許多自由度在一個特設(shè)的同時解決更好的解決方案方式。我們

4、能夠獲得極低的功耗，占地面積小，良好的吞吐量，低延遲，并具有層狀溶液高可靠性。然而，這些層之間的界面不能不經(jīng)意的限制和挑戰(zhàn)的性質(zhì)，為層，以提供足夠的表現(xiàn)力有效的合作。無人使用的節(jié)點(diǎn)，需要以方便CON組和管理的絕對數(shù)量以及是通過ICMPv6的提供的機(jī)制對齊。而在IPv4中發(fā)現(xiàn)和反對網(wǎng)絡(luò)連接的許多方面的外層像BOOTP和DHCP2服務(wù)依賴，這些都被系統(tǒng)地納入具有增強(qiáng)發(fā)現(xiàn)IPv6的架構(gòu)，是由較大的，較簡單的命名空間，并支持組播功能。我們發(fā)現(xiàn)該ICMPv6的功能遠(yuǎn)遠(yuǎn)超過已經(jīng)提出具體傳感器網(wǎng)絡(luò)。事實(shí)上，如果傳感器網(wǎng)絡(luò)不摻入的IP架構(gòu)，多的這種功能將需要被徹底改造這些網(wǎng)絡(luò)進(jìn)入生產(chǎn)。然而，大多數(shù)這些IPv6

5、的解決方案假設(shè)所有節(jié)點(diǎn)從一個指定的單插槽。它們需要被擴(kuò)展到服務(wù)于多插槽情況?；蛟S令人驚奇的結(jié)果是，通過將每個節(jié)點(diǎn)作為路由器，因此德音響寧重疊鏈路本地作用域的網(wǎng)絡(luò)體系結(jié)構(gòu)，該現(xiàn)有的IPv6協(xié)議可以用簡單的選項(xiàng)自然延伸。要在，它似乎是模仿經(jīng)過多跳比較常見的單播域會保留更多的現(xiàn)有的IPv6的機(jī)制。我們的經(jīng)驗(yàn)是，我們需要有2層的版本同樣的功能，支持模擬，所以這是更自然，保持第二層非常簡單，利用路由能力是通過內(nèi)置于第三層。而它是否局部算法和在網(wǎng)絡(luò)處理將變得仍不清楚普遍，而不是相對簡單的數(shù)據(jù)收集，記錄，警報和CON組配置中，使用的IPv6架構(gòu)的，因?yàn)槲覀円呀?jīng)制定它是與支持這種算法的愿望是完全一致的。通過構(gòu)

6、建架構(gòu)重疊的鏈路本地范圍提供全局路由，局部算法只是作為UDP數(shù)據(jù)報以各種組播地址或單播實(shí)現(xiàn)地址。它也仍不清楚命名是否會成為主要的數(shù)據(jù)中心，如果是這樣，這是否將需要網(wǎng)絡(luò)堆棧內(nèi)或應(yīng)用覆蓋解決。但不管，通過提供對于傳感器網(wǎng)絡(luò)干凈的IPv6架構(gòu)，這場辯論從本質(zhì)上變成一樣的以數(shù)據(jù)為中心的爭論在互聯(lián)網(wǎng)的其他部分。我們所做的網(wǎng)絡(luò)連接第二是大的，簡單的地址空間，使用組播集團(tuán)架構(gòu)的德網(wǎng)絡(luò)地址空間的角度定義，和規(guī)律性實(shí)際上使資源約束溶液比在IPv4的設(shè)置更加容易。壓縮和首標(biāo)信息省音在那里可以從第2層頭部中的共享上下文的一些簡單的假設(shè)存在下重建變得簡單。雖然傳感器網(wǎng)絡(luò)實(shí)際上更多的應(yīng)用程序特定網(wǎng)絡(luò)連接溫度比傳統(tǒng)網(wǎng)絡(luò)中

7、，我們網(wǎng)絡(luò)ND的聯(lián)網(wǎng)機(jī)制和結(jié)構(gòu)都沒有。什么是應(yīng)用特定網(wǎng)絡(luò)是如何使用這些的機(jī)制的優(yōu)化和網(wǎng)絡(luò)是如何的架構(gòu)框架內(nèi)舉辦。 是否這是通信或數(shù)據(jù)流的確定性調(diào)度，以減少開銷，簡單的機(jī)制這種支持多種應(yīng)用可以利用應(yīng)用特定網(wǎng)絡(luò)C語言結(jié)構(gòu)。然而，機(jī)制當(dāng)網(wǎng)絡(luò)的行為是不按特定網(wǎng)絡(luò)連接模式還提供了更廣泛的安全網(wǎng)。例如，它可以是在低功率與始終在線行為充分運(yùn)作而節(jié)點(diǎn)通信，以確定時間表。或者，它可以回退到樣監(jiān)聽時間表漂移的時候。這是典型的傳感器網(wǎng)絡(luò)的相對簡單的應(yīng)用程序特征可被利用來簡化協(xié)議及其實(shí)施，實(shí)現(xiàn)小的資源需求。這樣的解決方案可以是次優(yōu)任意任意到任意這對于傳統(tǒng)網(wǎng)絡(luò)的主要設(shè)計點(diǎn)傳輸。10.2.影響研究本文廣泛的架構(gòu)問題都與社

8、會協(xié)議的最佳解決。在本工作中，我們一直在積極參與標(biāo)準(zhǔn)組織，如IETF和IEEE。我們當(dāng)前與IEEE 802.15.4e工作組的工作，并提出了許多的想法，從第4章包含在IEEE 802.15.4標(biāo)準(zhǔn)。 IETF內(nèi)部6LoWPAN的工作組發(fā)布了建議標(biāo)準(zhǔn)IEEE 802.15.4幀中進(jìn)行通信的IPv6數(shù)據(jù)報。我們的工作初期工作導(dǎo)致頭格式特定網(wǎng)絡(luò)版在RFC 4944，它采用了適配層報頭格式第5章中提出然而，仍然存在內(nèi)6LoWPAN的顯著的工作完成基于IPv6的網(wǎng)絡(luò)架構(gòu)，我們計劃繼續(xù)這一進(jìn)程。我們的報頭壓縮機(jī)制在第5章介紹所服務(wù)作為報頭壓縮改進(jìn)的基礎(chǔ)上的。我們在第6章的工作是在發(fā)現(xiàn)的設(shè)計和特異性陽離子對

9、于6LoWPAN的網(wǎng)絡(luò)。盡管6LoWPAN的工作組還遠(yuǎn)遠(yuǎn)沒有完成，其成果已傳播IETF的外面。其他標(biāo)準(zhǔn)組織，如ISA84，都采用了6LoWPAN的頭用戶資格墊和工業(yè)自動化應(yīng)用基于IPv6的網(wǎng)絡(luò)架構(gòu)。學(xué)術(shù)努力已經(jīng)實(shí)現(xiàn)了基于RFC4944基于IPv6的網(wǎng)絡(luò)協(xié)議棧27，68。眾多的商業(yè)實(shí)體也做同樣的，包括日立76，Jennic公司88，Sensinode154和Sun Microsys-統(tǒng)160。我們在本文描述和評價執(zhí)行情況的變種作為核心技術(shù)拱石公司。我們的產(chǎn)品質(zhì)量實(shí)施一直在使用在實(shí)際客戶部署的一年。我們也使用同樣的技術(shù)在學(xué)術(shù)環(huán)境。 在加州大學(xué)伯克利分校，該技術(shù)被用來教標(biāo)題為本科班道：“每天物聯(lián)網(wǎng)“

10、26。通過支持熟悉的基于IP的通信機(jī)制，學(xué)生能夠?qū)Ｗ⒂诶脧V泛的現(xiàn)有的基于IP的工具，而不是構(gòu)建基于Web的應(yīng)用程序在非標(biāo)準(zhǔn)網(wǎng)絡(luò)堆棧并將其納入傳統(tǒng)網(wǎng)絡(luò)的復(fù)雜性。10.3.結(jié)束語支持IP提供與現(xiàn)有的IP設(shè)備的互操作性的寶貴，以及能夠連接傳感器網(wǎng)絡(luò)到其他IP網(wǎng)絡(luò)（即網(wǎng)絡(luò)重新連接時利用現(xiàn)有的IP工具的廣泛身體，代理，高速緩存等）。我們已經(jīng)表明，基于IPv6的網(wǎng)絡(luò)架構(gòu)可以實(shí)現(xiàn)更在傳感器網(wǎng)絡(luò)比已被證明迄今沒有遵守任何特定的標(biāo)準(zhǔn)。我們的實(shí)現(xiàn)是能夠達(dá)到的0.65的平均占空比，平均每62ms跳延遲，和99.98，比在現(xiàn)實(shí)世界的家庭監(jiān)控應(yīng)用一個為期4周的數(shù)據(jù)接收速率其中每個節(jié)點(diǎn)產(chǎn)生每分鐘一個應(yīng)用程序包?；趶V泛

11、的IPv6支持在同一個技術(shù)上下文之前更有限的存在，更奇特的解決方案意味著我們可以重新審視一個更為廣泛的研究問題。該在網(wǎng)絡(luò)處理，聚集，壓縮和查詢處理的問題沒有被約束底層網(wǎng)絡(luò)能力。這是相當(dāng)簡單的實(shí)現(xiàn)任何這些。其功效可以從問題的強(qiáng)烈分離是否應(yīng)該應(yīng)用水平疊加來實(shí)現(xiàn)或在某種程度上更深入地集成到網(wǎng)絡(luò)堆棧。同樣地，許多長期存在的傳感器網(wǎng)絡(luò)問題可以在一個更一般的設(shè)置進(jìn)行檢查，并且如果答案是“打開TCP連接”或“發(fā)送UDP數(shù)據(jù)報給需要的地方去”，這個問題的答案是可以接受的為好。在另一方面，一些新的問題出現(xiàn)關(guān)于互聯(lián)網(wǎng)架構(gòu)應(yīng)該如何更改或現(xiàn)在演變，它是支持一類新的應(yīng)用程序。這是難以忽視的普及UDP和TCP 它們必須被

12、實(shí)現(xiàn)為提供與現(xiàn)有的IP設(shè)備端至端的互操作性。然而，許多人認(rèn)為，無論是UDP或TCP傳輸是周期性的讀數(shù)，許多工業(yè)協(xié)議已經(jīng)在常規(guī)遇到這些緊張關(guān)系有線鏈路，但他們采取的低功耗無線設(shè)置一個新的。另一個例子是存在實(shí)施小組的，特別是當(dāng)致動涉及。樓宇自動化和家庭自動化的需要，例如，似乎是從音頻和視頻流，其中IP組播是常見大不相同。異質(zhì)性的部署變得更加自然的，因?yàn)镮P路由通過取消網(wǎng)絡(luò)支持跨越各種鏈接。在這些或各種其它的研究，所述的IPv6體系結(jié)構(gòu)提供了一個框架開發(fā)特定網(wǎng)絡(luò)機(jī)制，如此有效地做，即使嚴(yán)重的資源限制，沒有每個研究需要到尚未開發(fā)的另一個MAC，路由協(xié)議和傳輸。因此，它會似乎是發(fā)展兩行不只是技術(shù)上的互補(bǔ)

13、性，合并可能加速在這兩個進(jìn)步。2.外文原文An Extended Internet Architecture for Low-Power Wireless Networks - Design and ImplementationChapter 10Conclusions10.1 Architectural RetrospectiveIn the past decade, wireless sensor network research and Internet architecture, especially IPv6, have both progressed substantially.

14、Thus, it makes sense to revisit the assumptions that have formed the basis of so much 傳感器網(wǎng)絡(luò) research. By constructing a high quality 傳感器網(wǎng)絡(luò) using IPv6 as a foundation, we nd that the two areas of development are in fact highly complementary. Most of the unique requirements of 傳感器網(wǎng)絡(luò)s are well served b

15、y the IPv6 architecture, in many cases better than by any efforts that were carried out without concern for any particular network standard. However, in several instances while the architecture was appropriate, the specic RFCs and implementations were not. Extensions had to be created to encompass p

16、articular needs, and these extensions are naturally supported by the systematic use of options.傳感器網(wǎng)絡(luò) research has focused much more on network protocol algorithms and mechanisms, rather than on networking in the broader sense. The IPv6 forms of layering, addressing, header formats, conguration, mana

17、gement, routing, and forwarding provide the missing structure. And, in many cases the mechanisms developed in the 傳感器網(wǎng)絡(luò) space provide elegant solutions to problems that have long challenged conventional IETF approaches. Not only do we nd a close analog to the structures for dissemination and collect

18、ion that are so common in 傳感器網(wǎng)絡(luò)s, but Trickle mechanisms provide an elegant means of reachingconsensus, responding quickly to changes, and becoming passive in the steady state. In particular, we nd that we need not forsake the many virtues of layering to meet the severe resource constraints of 傳感器網(wǎng)絡(luò)

19、 nodes. If anything, the focus obtained by a layered approach tends to produce better solutions than when many degrees of freedom are addressed simultaneously in an ad-hoc manner. We were able to obtain extremely low power consumption, small footprint, good throughput, low latency, and high reliabil

20、ity with a layered solution. However, the interfaces between the layers cannot be oblivious to the nature of the constraints and challenges, to provide enough expressiveness for the layers to cooperate effectively.The sheer numbers of nodes, unattended use, and need for ease of conguration and manag

21、ement are well aligned with the mechanisms provided by ICMPv6. While many aspects of discovery and conguration in IPv4 relied on external layer 2 services like BOOTP and DHCP, these have been systematically incorporated into the IPv6 architecture with enhanced autoconf and discovery that are enabled

22、 by the larger,simpler namespace and multicast support. We nd that ICMPv6 capabilities far exceed anything that has been proposed specically for 傳感器網(wǎng)絡(luò)s. Indeed, if 傳感器網(wǎng)絡(luò)s are not to incorporate the IP architecture,much of this functionality will need to be reinvented for these networks to go into pr

23、oduction.However, most of these IPv6 solutions assume that all nodes are a single hop from a designated agent. They needed to be extended to service the multihop case. Perhaps the surprising result is that by treating each node as a router and hence dening a network architecture of overlapping link-

24、local scopes, the existing IPv6 protocols can be naturally extended with simple options. Going in, it seemed that emulating the more common single broadcast domain over multiple hops would preserve more of the existing IPv6 mechanisms. Our experience was that we needed to have layer 2 versions of th

25、is same functionality to support the emulation, so it was much more natural to keep layer 2 extremely simple and utilize the routing capability that is by denition built in to layer 3.While it remains unclear whether localized algorithms and in-network processing will become prevalent, rather than r

26、elatively straightforward data collection, logging, alarms, and conguration, the use of an IPv6 architecture as we have formulated it is entirely consistent with the desire to support such algorithms.By constructing the architecture as overlapping link-local scopes that provide global routing, local

27、ized algorithms are simply implemented as UDP datagrams to various well-dened multicast addresses or to unicast addresses. It also remains unclear whether naming will become primarily data-centric and if so whether this will need to be addressed within the network stack or by application overlays. B

28、ut regardless, by providing a clean IPv6 architecture for 傳感器網(wǎng)絡(luò)s, this debate becomes essentially the same as the data-centric debate in the rest of the Internet. What we did nd was that the large, simple address space, use of multicast groups dened in terms of that address space, and regularity of

29、the architecture actually made the resource constrained solution easier than in the IPv4 setting. Compression and elision of header information where it can be reconstructed from the layer 2 header in the presence of some simple assumptions of shared context becomes straightforward and efcient.While

30、 傳感器網(wǎng)絡(luò)s are indeed more application specic than traditional networks, we nd that the networking mechanisms and the architecture are not. What is application specic is how the use of those mechanisms is optimized and how the network is organized within that architectural framework. Whether it is dete

31、rministic scheduling of communication or streaming data to reduce overhead, simple mechanisms that support a wide variety of use can exploit the application specic structure. However, the mechanisms also provide a more general safety net when the networks behavior is not following the specic pattern

32、.For example, it can be fully operational at low power with always-on behavior while nodes communicate to determine that schedule. Or, it can fall back to sample listening when the schedule drifts.The relatively simple application characteristics that are typical of 傳感器網(wǎng)絡(luò)s can be exploited to simpli

33、fy protocols and their implementations to achieve small resource demand. Such solutions may be suboptimal for the arbitrary any-to-any transfers that are the primary design point for conventional networks.10.2 Research ImpactBroad architectural issues are best addressed in agreement with the communi

34、ty. Throughout this work, we have been actively involved in standards organizations such as the IETF and the IEEE. We are currently working with the IEEE 802.15.4e working group and have proposed many of the ideas from Chapter 4 for inclusion in the IEEE 802.15.4 standard. The 6LoWPAN working group

35、within the IETF published a proposed standard for communicating IPv6 datagrams within IEEE 802.15.4 frames. Our work initial work led to the header formats specied in RFC 4944, which incorporates the adaptation-layer header formats presented in Chapter 5. However, there still remains signicant work

36、within 6LoWPAN to complete an IPv6-based network architecture and we plan to continue the process. Our header compression mechanisms presented in Chapter 5 are serving as the basis for header compression improvements to RFC 4944. Furthermore, our work in Chapter 6 is signicantly inuencing the design

37、 and specication of Neighbor Discovery for 6LoWPAN networks.Even though the 6LoWPAN working group is far from complete, its results are already propagating outside the IETF. Other standards organizations, such as ISA 84, have adopted the 6LoWPAN header format and an IPv6-based network architecture f

38、or use in industrial automation applications. Academic efforts have already implemented an IPv6-based network stack based on RFC 4944 27, 68. Numerous commercial entities have also done the same, including Hitachi 76, Jennic 88, Sensinode 154, and Sun Microsystems 160.A variant of the implementation

39、 that we described and evaluated in this dissertation serves as the core technology for Arch Rock Corporation. Our production-quality implementation has been in use for over a year in real customer deployments. We have also used the same technology in academic settings. At the University of Californ

40、ia, Berkeley, the technology was used to teach an undergraduate class titled: “The Internet of Everyday Things” 26. By supporting familiar IP-based communication mechanisms, students were able focus on building web-based applications using a broad set of existing IP-based tools, rather than on the i

41、ntricacies of a non-standard network stack and their integration into traditional networks.10.3 Last WordsSupporting IP provides invaluable interoperability with existing IP devices as well as being able to utilize the broad body of existing IP tools when connecting 傳感器網(wǎng)絡(luò)s to other IP networks (i.e.

42、, rewalls,proxies, caches, etc.). We have shown that an IPv6-based network architecture can be implemented more efciently in 傳感器網(wǎng)絡(luò)s than what has been demonstrated to date without adherence to any particular standard.Our implementation was able to achieve an average duty-cycle of 0.65%, average per-

43、hop latency of 62ms,and a data reception rate of 99.98% over a period of 4 weeks in a real-world home-monitoring application where each node generates one application packet per minute.The presence of broad-based IPv6 support in the same technological context as prior more limited,more idiosyncratic

44、 solutions means that we can re-examine a much broader set of research questions. The question of in-network processing, aggregation, compression, and query processing are not constrained by the underlying networking capability. It is fairly straightforward to implement any of these. Their effectiveness can be strongly separated from questions of whether they should be implemented as application level overlays or somehow more deeply integrated into the network stack. Similarly, many of the long-standing 傳感器網(wǎng)絡(luò) questions can be examined in a much more general setting, and if th