5.1 結論
本研究以整合物聯網異質性為目標，並已成功整合部分物聯網異質，其中包括(1)通訊 協定異質：於物聯網中，IEEE 802.15.4 Zigbee 協定扮演了環境感測重要角色，但 Zigbee 協定與網際網路是異質的(Ethernet IEEE 802.3 與 WiFi IEEE 802.11)，無法直接溝通，
容易形成通訊孤島，因此，本研究於 Gateway 中安裝不同的網路介面，包括 Zigbee、
Ethernet、WiFi，使 Zigbee 節點感測資料能夠透過其它介面轉送至網際網路。(2)連網技 術異質：由於傳統 Zigbee 無法使用 IP，因此，本研究於 Zigbee Node 實作 6LoWPAN，
讓 Zigbee Node 能夠使用 IPv6 相關功能。另外，於 Gateway 上實作 6LoWPAN Border
Router 的功能，使 Zigbee 節點所送出的 6LoWPAN 封包能夠成功轉為完整的 IPv6 並送 上 Internet。最後，由於物聯網中有許多設備，使用的連網技術並不盡相同，如 IPv6、
IPv4，由於 6LoWPAN 制定為 IPv6 Only，因此，本研究於 Gateway 上實作 Tunnel 6to4 的功能，使 6LoWPAN 不僅能用於 IPv6，也能使用於 IPv4。(3)設備異質：因為每個設 備可提供的能力並不盡相同，本研究以 CoAP 為基礎記錄 Sensor Profile 並設計一 M2M 平台，以不需人為介入的中央控管機制來管理與取得 Sensor Profile 與 Sensor data，並 記錄於資料中心，給予使用者方便後續使用。(4)實現感測節點與遠端設備之 End-to-End
Communication：本研究不只將 6LoWPAN 節點所產生之感測資料能夠使用 UDP 封包成 功傳送至遠端 Server。也於 6LoWPAN 節點中實作 CoAP，並證明遠端設備能夠成功直 接訪問節點並取得節點所提供的資料，因此，Global 的雙向 End-to-End Communication
已成功部屬與應用於本系統中。(5)以 M2M 平台為基礎設計使用者應用範例：設計者只 需利用本 M2M 平台所產生的資料，無須了解其中的細節，過程中繁複的處理流程，均 交由平台中 M2M 模組處理完成。
5.2 未來展望
本系統的 Gateway 目前已處理 IEEE 802.15.4 與 IEEE 802.3、IEEE802.11 間的異質，未 來希望能夠加入新的通訊技術用於處理物聯網異質性，使本系統 Gateway 處理異質功 能更加完善。另外，可以於更多的物聯網設備上實作 CoAP 以運用於本系統。
參考文獻
[1] Gartner Identifies the Top 10 Strategic Technology Trends for 2014, Available At:
http://www.gartner.com/newsroom/id/2603623
[2] L. Atzori, A. Iera, and G. Morabito, “The Internet of Things: A survey,” ACM Computer Networks , vol. 54, no. 15, pp. 2787 – 2805, Oct. 2010.
[3] D. Miorandi, S. Sicari, F. D. Pellegrini, and I. Chlamtac, “Internet of Things: Vision, applications and research challenges,” ACM Ad Hoc Networks, vol. 10, no.7, pp.1497-1516, Sep. 2012.
[4] oneM2M, Available At: http://www.onem2m.org/
[5] K. C. Chen, and S. Y. Lien. “Machine-to-Machine communications: Technologies and Challenges,”
ACM Ad Hoc Networks, vol.18, no. 3, pp. 3-23, Jul. 2014.
[6] Transmission of IPv6 Packets over IEEE 802.15.4 Networks, IETF RFC Standard 4944, Sep. 2007.
[7] Connection of IPv6 Domains via IPv4 Clouds, IETF RFC Standard 3056, Feb. 2001.
[8] Constrained Application Protocol (CoAP), IETF RFC Standard 7252, Jun. 2014.
[9] Gartner Says the Internet of Things Installed Base Will Grow to 26 Billion Units By 2020, Available
At: http://www.gartner.com/newsroom/id/2636073
[10] G. M. Lee, J. Park, N. Kong, N. Crespi, “The Internet of Things – Concept and Problem Statement,”
IETF, draft–lee–iot–problem–statement–00, Apr. 2011.
[11] Machine–to–Machine Communications; M2M service requirements, ETSI Standard TS.102
689v2.1.1, Jul. 2013.
[12] Machine–to–Machine Communications; Functional Architecture, ETSI Standard TS. 102 690
v1.2.1, Jun. 2013.
[13] Architecture Analysis – Part 1: Analysis of architectures proposed for consideration, oneM2M
Standard TR.0002, Nov. 2013.
[14] Architecture Analysis – Part 2: Study for the merging of architectures proposed for consideration
by oneM2M, oneM2Mstandard TR. 0002, Jul. 2013.
[15] P. Barontib, P. Pillaia, V. W. C. Chooka, S. Chessab, et al, “Wireless sensor networks: A survey on the state of the art and the 802.15.4 and ZigBee standards,” ACM Computer Communications, vol. 30, no. 7, pp.1655-1695, May. 2007.
[16] J. Nieminen, T. Savolainen, M. Isomaki, B. Patil, Z. Shelby, andC. Gomez, “Transmission of IPv6 Packets over BLUETOOTH Low Energy,” IETF, draft–ietf–6lowpan–btle–12, work–in–progress, Feb. 2013.
[17] Z. Shelby, and C. Bormann, 6LoWPAN: The wireless embedded Internet, 2011.
[18] J. Hui, and P. Thubert, “Compression Format for IPv6 Datagrams in Low Power and Lossy Networks,” IETF, draft–ietf–6lowpan–hc–15, Aug. 2011.
[19] Compression Format for IPv6 Datagrams over IEEE 802.15.4–Based Networks, IETF RFC
Standard 6282, Sep. 2011.
[20] A NONSTANDARD FOR TRANSMISSION OF IP DATAGRAMS OVER SERIAL LINES:
SLIP, IETF RFC Standard 1055, Jun. 2011.
[21] B. C. Villaverde, R. D. P. Alberola, A. J. Jara, S. Fedor, S. K. Das, and D. Pesch, “Service Discovery Protocols for Constrained Machine-to-Machine Communications,” IEEE
Communication Surveys & Tutorials, vol. 16, no. 1, pp. 41-57, Feb. 2014.
[22] Sensinode Ltd, Available At: http://www.sensinode.com
[23] K. Kim, W. A. Baig, S. Yoo, “Simple Service Location Protocol (SSLP) for 6LoWPAN,” IETF, draft-daniel-6lowpan-sslp-02, Oct. 2009.
[24] DNS-Based Service Discovery, IETF RFC Standard 6763, Feb. 2013.
[25] Google IPv6 Statistics, Available At: http://www.google.com/intl/en/ipv6/statistics.html
[26] G. Lencse, S. Répás, “Performance Analysis and Comparison of 6to4 Relay Implementations,”
International Journal of Advanced Computer Science and Applications, vol. 4, no. 9, pp. 13-21,
2013
[27] Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers,
IETF RFC standard 6146, Apr. 2011.
[28] DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers,
IETF RFC standard 6147, Apr. 2011.
[29] IPv6 Stateless Address Autoconfiguration, IETF RFC standard 4862, Aug. 2007.
[30] Y. Chen, K. M. Hou, H. Zhou , H. L. Shi , X. Liu , X. Diao, H. Ding , J. J. Li ,and d. Vaulx,
“6LoWPAN stacks: a survey,” Proceeding of IEEE 2011 7th International Conference on Wireless Communications Networking and Mobile Computing, Wuhan, pp. 1-4, 2011.
[31] TinyOS Home Page, Available At: http://www.tinyos.net/
[32] Contiki: The Open Source OS for the Internet of Things, Available At: http://www.contiki–
os.org/index.html
[33] Zigduino, Available At: http://www.logos-electro.com/store/zigduino-r2
[34] Contiki on Zigduino, Available At: https://github.com/maniacbug/contiki-avr-zigduino/wiki
[35] Raspberry PI, Available At: http://www.raspberrypi.org/
[36] Nooliberry, Available At: https://github.com/Noolitic/Nooliberry/wiki
[37] Coap Sharp, Available At: http://www.coapsharp.com/
[38] Copper, Available At: https://addons.mozilla.org/en-US/firefox/addon/copper-270430/
[39] T. Savolainen, J. Soininen, and B.Silverajan, “IPv6 Addressing Strategies for IoT,” IEEE Sensors Journal, vol. 13, no. 10, pp. 3511-3519, Oct. 2013.