The document discusses several key aspects of Internet of Things (IoT) systems including: 1. IoT devices and networks have heterogeneous requirements for data representation, visualization, and interaction both locally and remotely. 2. IoT systems interface the physical world through physical entities, sensors, and actuators, and require consideration of the deployment context. 3. Design of IoT devices and networks requires addressing functional requirements like sensing, actuation, and communication as well as non-functional requirements including energy, cost, regulations, and ease of use.

2. • Each iot application has an optimal visual
representation of
• The data and
• The system.
• Data that is generated from heterogeneous systems
has heterogeneous visualization requirements.
• There are currently no satisfactory standard data
representation and storage methods that satisfy all of the
potential iot applications.
• Data-derivative products will have further ad hoc
visualization requirements.

3. • A derivative in these terms exists once a function has
been performed on an initial data set (may or may not
be raw data).
• These can be further integrated at various levels of
abstraction, depending on the logic of the integrator.
• New information sources, such as those derived from
integrated data streams from various logically correlated
IoT applications, will present interesting representation
and visualization challenges.

5. • To exploit remote interaction and control over IoT
applications, connectivity that spans the traditional
Internet. (from anywhere)
• the application manager,
• authorized entity,
• to the end-point (embedded device), continues to be a
challenging problem

6. Particularly for devices deployed inaccessible locations
requires:
• Elements of device management,
• Specifically reprogramming and
• Reconfiguration of deeply embedded devices

7. • End-to-end latency,
• Security,
• Reliability,
• Availability,
• Times between failure and repair,
• Responsibility, etc.,

10. • The Deployment and Operational View depends on the
specific actual use case and requirements.
• The two sensor nodes are connected to the payment
station through wireless or wired communication.
• The payment station acts both as a
• (user interface) for the driver to pay and get a
payment receipt as well as a communication gateway
that connects the two sensor nodes
• (the payment interface) physical devices with the
Internet through Wide Area Network (WAN) technology.
• The two main applications connected to this
management system are human user mobile phone
applications and parking operation center
applications.

12. • An iot system is typically part of a larger system. Starting
from the sensor devices,
• sensor node #1 hosts resource #11#18, representing
the sensors for the parking spots #01#08,
• sensor node #2 hosts resource #21#28,
• The two sensor nodes are connected to the gateway
device that also hosts the payment service with the
accompanying sensors and actuators,
• The management system for the specific parking lot, as
well as others, is deployed on a virtual machine on a
data centre.

13. • The virtual machine hosts communication capabilities,
Virtual Entity services
• a payment business process that involves the payment
station and input from the occupancy sensor services
• the parking lot management service that provides
exposure and access control
• The services offered on these parking spots are to read
the current state of the parking spot to see whether it is
“free” or “occupied.”
• The physical sensors,
• actuators,
• tags,
• processors, and
• memory, which are parts of a Device, are deployed close to the
Physical Entities, (the ones whose properties are monitored or
controlled).

15. • Advanced Device of type #1 that allows the basic
device to perform protocol adaptation
• Advanced Devices (type #2) can host the Sensor IoT
Service communicating to the Sensor Resource
• The cloud infrastructure contains:
Virtual Entity services,
Service Organization components (Composition,
Orchestration, Choreography),
IoT Process Management components,
Historical Data Services (collection, processing),
Data Analytics and Knowledge Management.

16. • Apart from these functional views, there are a few more
that are very important for a system that interfaces the
physical world.
• The two most important are
• the Physical Entity View and
• the Context View.
• The Physical Entity View describes the Physical Entities
from the IoT Domain Model in terms of physical
properties (e.g. dimensions for spaces/ objects).
• The description of the Physical Entities may also include
the relationship between Physical Entities

17. • The context of a system, “describes
• The relationships,
• Dependencies, and
• Interactions between the system and its environment
Therefore, the context view should capture external
entities interacting with the system

19. • The IoT will see additional circuitry built into a number of
existing products and machines.
• Giving these things an identity, and the ability to
represent themselves online and communicate with
applications and other things, represents a significant,
widely recognized opportunity.
• For manufacturers of products that typically contain
electronic components, process will be relatively
straightforward

20. • The device -Hardware,
• representation -Data and visualization
• interaction -Local or remote control
Devices and networks
• Devices that form networks in the M2M area network
domain must be selected, or designed, with certain
functionality
• At a minimum, they must have
• An energy source (e.g. Batteries, increasingly EH),
• Computational capability (e.g. An MCU),
• Appropriate communications interface (e.g. A radio frequency
integrated circuit (RFIC) and front end RF circuitry),
• Memory (program and data), and
• Sensing (and/or actuation) capability.

21. • Specific sensing and actuating capabilities are basic
functional requirements.
• the device must be capable of sensing or perceiving
something interesting from the environment.
• The sensor may directly measure the phenomenon
(e.g. temperature), or may be used to derive data or
information about the phenomenon, based on additional
knowledge (e.g. a level of comfort).
• Sensors may sense a phenomenon that is local (i.e. a
meter detecting total electricity consumption of a space)
or distributed (e.g. the weather).

22. • The sensing field is of importance when considering
both the phenomenon to be sensed (local or distributed)
and the distance between sensing points.
• Devices must be placed in close enough proximity to
communicate.
• Where the distance is too great, routing devices may be
necessary.
• Devices may become intermittently disconnected due to
the time varying, stochastic nature.

23. • Devices in the IoT are fundamentally heterogeneous.
• There are, various computational architectures, including
MCUs (8-, 16-, 32-bit, ARM, 8051, RISC, Intel, etc.),
signal conditioning (e.g. ADC), and
memory (ROM, (S/F/D)RAM, etc.),
In addition to communications media,
peripheral components (sensors, actuators,
buttons, screens, LEDs), etc.
• Operating systems are typically used to make
programming simpler and modular for embedded
systems designers

24. • Power is essential for any embedded or IoT device.
Depending on the application, power may be provided
by the mains, batteries, or conversion from energy
scavengers.
• The power source has a significant implication on the
design of the entire system.
Gateway
• Is typically more straightforward to design if it usually acts
as a proxy.
• It is also thought that the gateway device can be
exploited for performing some level of analytics on data
transitioning to and from capillary networks.

25. • There are a number of non-functional requirements that
need to be satisfied for every application.
• These are technical and non-technical
• Regulations(varies by region and frequency band)
• Ease of use, installation, maintenance,
accessibility(Simplification of installation )
• Physical constraints(physical size limitations )
Financial cost
1. Component Selection- Developing devices in small
quantities is expensive.
2. Integrated Device Design- the energy, sensors,
actuators, computation, memory, power,
connectivity, physical, and other functional and non
functional requirements are considered