26.03.2015 Views

19SafQB

19SafQB

19SafQB

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

9.1 Introduction 319<br />

• Shrinkage of hardware and software. Some already established<br />

devices which, in one way or another, are constrained to low power<br />

consuming or narrow bandwidth necessities, as motes in ubiquitous<br />

networking, are sure to be smaller than domestic computers, so<br />

services need to be provided at their minimum possible capabilities<br />

of transmission, energy storage, etc. This dramatic shrinking in<br />

hardware (and consequently, in software) will take its toll when<br />

creating new services and experiences, but without it ubiquitous<br />

computing would lose a part of its meaning.<br />

• Human intervention is reduced to its minimal expression. As<br />

new paradigms in computing (Internet of Things, Service Oriented<br />

Computing) are developed under the ideas of Mark D. Weiser,<br />

it becomes crystal clear that if an everyday augmented element<br />

is to become part of a service provided by networked embedded<br />

systems like Wireless Sensor Networks, that supposedly is as quiet<br />

and discrete as it can be, intrusion and attention from a human being<br />

must be kept at their lowest rates (unless the end user is willing<br />

to be told about any datum related to the service) in order to have<br />

the devices participating in the Internet of Things turning into —<br />

or remain as — a silent, non-attention demanding electronic piece<br />

naturally integrated within its environment — or embedded in an<br />

object that is already like that —, which will not add extra duties<br />

or discomfort to its human beneficiaries.<br />

• Content and parameters under constant change. Should OSI or<br />

TCP/IP architectures be considered as the components architecture<br />

of a service found in an Internet of Things scenario, with a physical<br />

layer at the bottom and an application layer at the top, any device<br />

is likely to find a huge number of its kind scattered through those<br />

layers: personal computers’, wireless nodes’ or smart phones’ electronics<br />

as hardware and almost any imaginable idea as applications.<br />

Not only must an efficient middleware layer abstract the general<br />

working conditions and offer a usable interface to higher levels,<br />

but also has to deal with the changing status of applications: if a<br />

device is working in combination with, for example, a piece of<br />

clothes, services will change as the user walks or drives. In this<br />

way, some services will be lost, rendering the application built to

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!