“Smart” objects are ubiquitous. Not only our phones, but our cars, refrigerators
ID: 3722776 • Letter: #
Question
“Smart” objects are ubiquitous. Not only our phones, but our cars, refrigerators, washers/dryers, even vital biomedical equipment that is implanted in us. These smart objects are on a network, which means they talk to each other. Who administrates the IoT network? Research the Internet of Things (IoT) and write a 2 - 3-page essay comparing and contrasting the benefits of this vs. the privacy and security concerns. You must use three (3) sources. Please write the sources in the comment section below.
PLease make copy paste available
Explanation / Answer
A smart object is an object that enhances the interaction with not only people but also with other smart objects. It can not only refer to interaction with physical world objects but also to interaction with virtual (computing environment) objects. A smart physical object may be created either as an artifact or manufactured product or by embedding electronic tags such as RFID tags or sensors into non-smart physical objects. Smart virtual objects are created as software objects that are intrinsic when creating and operating a virtual or cyber world simulation or game. The concept of a smart object has several origins and uses, see History. There are also several overlapping terms, see also smart device, tangible object or tangible user interface and Thing as in the Internet of things.
A true Internet of Things will require IP in the tiniest devices that monitor or control real world objects, and that services and data from these devices are somehow available more openly for applications to make use of. The use of standard IP and Web technologies will ensure that device costs are driven down and that application development and use will be significantly simplified.
Key Technologies of IoT
Technologies for realizing IoT devices have already been around for years, and have been standardized by the IETF, starting from the lower layers of the stack and moving up. Today, we have IPv6 as a foundation running over links such as those found in mobile networks (2G, 3G and LTE) as well as low power local area sensor networks such as IEEE 802.15.4/6LoWPAN.
The current focus is on getting the application layer capabilities in place. We firmly believe that the REST paradigm is the way forward for integrating Smart Objects on the Web and the Internet. To this end, we are contributing to the work in IETF on defining a new protocol for REST in Smart Objects called CoAP – Constrained Application Protocol. In its simplest explanation, CoAP is a binary HTTP with simplified transport capabilities. The Working Group in IETF performing this CoRE – Constrained RESTful Environments – is also working on other necessary capabilities, such as proxying between CoAP and HTTP, web resources that are self-describing, resource discovery, capabilities for off-line and sleepy devices, as well as security.
Interoperability of Smart Objects
One key feature for IoT is to ensure interoperability of various Smart Objects including their seamless integration with applications and services.
Last week, the IPSO Alliance, which is an alliance of companies and organizations promoting and spearheading the development of IP in Smart Objects, held a successful interop event at its member meeting in Paris, France. The focus of the interop was on application layer capabilities. Past events included interoperability tests of IPv6 devices over different physical layers.
On test were services based on CoAP, such as reading sensors, doing actuation, and resource publication and discovery. To this end, the alliance had, in addition to the various relevant IETF drafts, also defined a dedicated interoperability-oriented application layer profile. The purpose of this profile was simply to be able to test interoperability between real and proper sensors and actuators. The profile made it possible to provide basic sensor and actuator service descriptions and naming.
Eight different member companies and organizations participated in the event with a number of implementations for various sensors and actuators, including smart plugs, light bulbs, temperature, luminosity sensors and others. Many of the devices ran the open source ContikiOS coming out of SICS.
Even though IPv6 makes it possible to run IP end-to-end, we believe there are many reasons for having gateways. One obvious reason is to be able to connect IPv6 devices to the IPv4 internet. There are also benefits in application layer gateways depending on the deployment scenario. Protecting Smart Objects from DoS attacks that may drain batteries, being able to provide localized services in Smart Buildings, interworking with legacy devices, or local sensor data event filtering and aggregation are all typical examples.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.