embedded web services report
TRANSCRIPT
![Page 1: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/1.jpg)
EMBEDDED WEB SERVICES
IEEE Wireless CommunicationsVolume 17, Issue 6, December 2010, Article
number5675778, Pages 52-57
學生:邱柏誌
![Page 2: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/2.jpg)
This article first gives an overview of the web architecture, its core REST concepts, and the current state of the art in web services.
Two key activities required in order to achieve efficient embedded web services are introduced:◦ a fresh approach to a web application transfer protocol
and efficient payload encoding.◦ The article analyzes the most promising payload
encoding techniques and introduces the new IETF Constrained RESTful Environments (CoRE) standardization activity.
Abstract
![Page 3: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/3.jpg)
Introduction
![Page 4: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/4.jpg)
The IPv6 over low-power wireless area network are playing a key role in driving the Internet of Things.
Problems:◦ Web service technology today is a poor match for
the vast majority of constrained networks, machine-to-machine (M2M) applications
◦ constrained embedded devices are optimized for low cost and power consumption
Introduction
![Page 5: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/5.jpg)
Web Services
![Page 6: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/6.jpg)
Two general ways of realizing web services: ◦ applying REST for the manipulation of resources
using HTTP◦ via remote procedure call (RPC) style interactions
using, say, the Simple Object Access Protocol (SOAP).
What Is Web Service?
![Page 7: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/7.jpg)
What Is Web Service?
![Page 8: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/8.jpg)
What Is Web Service? The RESTful paradigm has many
advantages over RPC style interactions for constrained embedded device. These include less overhead, less parsing complexity, statelessness, and tighter integration with HTTP
![Page 9: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/9.jpg)
Web services today are usually not suitable for constrained networks and devices
Problems with these protocols include:
The Embedded Web
![Page 10: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/10.jpg)
Overhead: The ideal UDP payload over 6LoWPAN and IEEE 802.15.4 is just 60–80 bytes for reasonable performance
TCP binding: Web services today depend on TCP, which has performance problems over lossy links, sensitivity to mobility, no multicast support and high overhead for short-lived transactions.
The Embedded Web
![Page 11: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/11.jpg)
Pull model: In sensor networks wireless nodes are typically sleeping over 90 percent of the time, making the HTTP request/response pull model inappropriate.
Complexity: A large number of features and optional headers may be employed, increasing embedded device complexity.
The Embedded Web
![Page 12: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/12.jpg)
To address those problems, we need a fresh approach to both the transfer protocol used to convey REST semantics, and the payload formats exchanged between applications.
The Embedded Web
![Page 13: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/13.jpg)
PAYLOAD COMPRESSION AND ENCODING
![Page 14: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/14.jpg)
IETF started a new working group on Constrained RESTful Environments (CoRE) focusing on the goal of producing two items specifically for M2M:
IETF CONSTRAINED RESTFULENVIRONMENTS
![Page 15: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/15.jpg)
Constrained Application Protocol (CoAP):◦ The group has defined an application transfer
protocol that realizes a minimal subset of REST along with resource discovery, subscription notification, and the use of appropriate security measures
Security bootstrapping:◦ The group will also define a set of security
bootstrapping methods for use in constrained environments in order to associate devices and set up keying material for secure operation
IETF CONSTRAINED RESTFULENVIRONMENTS
![Page 16: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/16.jpg)
IETF CONSTRAINED RESTFULENVIRONMENTS
![Page 17: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/17.jpg)
In order to realize the web architecture while meeting the demanding requirements of M2M applications, CoAP has the following key features:◦ Compact header◦ Methods and URIs◦ Subscription◦ Content Types◦ Simple caching◦ Transport binding◦ Resource discovery
THE CONSTRAINED APPLICATION PROTOCOL
![Page 18: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/18.jpg)
THE CONSTRAINED APPLICATION PROTOCOL
![Page 19: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/19.jpg)
By applying the fundamental REST architecture to this domain, efficient web service interfaces between embedded machines can be achieved.
Conclusion
![Page 20: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/20.jpg)
Recent advancements in XML encoding with W3C EXI along with industry-specific formats have shown promising results in minimizing payload overhead and parsing complexity.
The new IETF Constrained RESTful Environments working group is developing a new application transfer protocol designed specifically for realizing embedded web services.
Conclusion
![Page 21: Embedded Web Services Report](https://reader036.vdocuments.us/reader036/viewer/2022062406/559050a11a28abb3548b461f/html5/thumbnails/21.jpg)
Routing scalability, naming and identification, security, privacy, and the manageability of such a network
Chanllenges