SOLUTIONS MANUAL FOR FUNDAMENTALS OF
IOT AND WEARABLE TECHNOLOGY DESIGN – 1ST
EDITION BY HAIDER RAAD
Table of Contents
Chapter Title Questions
1 Introduction and Historical Background 30
2 Applications 30
3 Architectures 30
4 Hardware 30
5 Communication Protocols and Technologies 30
6 Product Development and Design Considerations 30
7 Cloud and Edge: Architectures, Topologies, and Platforms 30
8 Security 30
9 Concerns, Risks, and Regulations 20
Total 260
,Chapter 1: Introduction and Historical Background
Q1.1. What are the main differences between IoT and Wearable Technology?
Answer: Communication is IP-based in IoT, while it is not necessary in wearables. Most
wearables rely on a gateway device, such as a smartphone, for configuration and
connectivity, and in most cases to enable features and process data. This is not always
true in IoT devices. IoT devices are mainly stationary; wearables, on the other hand, are
mobile since they are worn or integrated within the user's body or clothing.
Rationale: These distinctions arise from the fundamental design philosophies: IoT
devices are designed for persistent network connectivity and remote operation, while
wearables prioritize user mobility and often depend on a companion device for full
functionality.
Q1.2. What is meant by "things" in Internet of Things?
Answer: The core functionality of IoT and wearable devices starts with data acquired or
an action performed by a device. These devices are called endpoints, and they are the
"Things" in Internet of Things. The value of IoT and wearable devices is in the data
collected by these endpoints.
Rationale: The term "things" refers to physical objects embedded with sensors,
software, and network connectivity that enable them to collect and exchange data. They
are the fundamental building blocks of any IoT system.
Q1.3. What are the main differences between IoT and M2M?
Answer: Communication is IP-based in IoT, while it is usually not in M2M. M2M is
mainly point-to-point while this is not true when it comes to IoT. M2M devices are
stationary; IoT could be stationary, or portable/mobile.
,Rationale: M2M (Machine-to-Machine) communication predates IoT and typically
involves direct, isolated connections between devices. IoT extends this by leveraging IP-
based networks, enabling broader integration and cloud connectivity.
Q1.4. Can you think of other potential challenges found in IoT and wearable technology
other than the ones mentioned in this chapter?
Answer: There are several other challenges besides the ones mentioned in the chapter,
which include design-based challenges, safety, longevity, compatibility, etc.
Rationale: While the chapter covers security, privacy, standards, energy, and
connectivity, real-world deployment reveals additional concerns such as device
interoperability, long-term reliability, and physical safety in medical applications.
Q1.5. Give examples of wearable devices/applications that do not require internet
connectivity.
Answer: Ultraviolet exposure wearable device, a simple pedometer, smart socks, GPS-
enabled hiking helmets, etc.
Rationale: Many wearables operate as standalone devices, processing data locally
without needing cloud connectivity. This reduces power consumption, improves privacy,
and enables operation in remote areas.
Q1.6. List five real-world examples of smart clothing.
Answer: (A) Smart fashion applications (e.g., Tommy Jeans Xplore) which utilize an
integrated chip that can track how often the product is used and also where it was worn.
(B) Smart yoga pants (e.g., Nadi X) which can sense when yoga poses need adjustment
by using haptic feedback to create small vibrations on the body part. (C) Athlete
recovery applications (e.g., Under Armour's apparel) that absorb heat from the user's
body and reflect it back in the form of far infrared light, which is supposed to promote
muscle recovery. (D) Smart Fitness Socks (e.g., Sensoria) which use advanced textile
, sensors to provide precise data on how your foot lands while walking or running. (E) A
swimming suit equipped with a UV sensor (e.g., Neviano's swimsuits).
Rationale: Smart clothing integrates sensors and electronics into fabrics, enabling
applications from fitness tracking to recovery monitoring. The examples illustrate the
diversity of form factors and use cases in wearable technology.
Q1.7. List five real-world examples of the headwear form in wearable technology.
Answer: Virtual reality headsets (e.g., Oculus), Smart motorcycle helmets (e.g., Sena),
Smart ski goggles (e.g., RideOn), Smart hats (e.g., LifeBeam), Smart sleep headbands
(e.g., Philips).
Rationale: Headwear represents a growing category of wearables, leveraging the
proximity to the head for applications in augmented/virtual reality, safety, and health
monitoring.
Q1.8. List four components common between IoT and wearable devices (an application
of your choice).
Answer: Microcontroller, sensor, battery/power management system, LCD screen.
Rationale: Despite differences in form factor and connectivity, IoT and wearable devices
share a common core architecture: sensing, processing, power, and user interface. This
commonality enables shared design methodologies.
Q1.9. Are wearable devices a form of M2M? Why?
Answer: Typically, wearables are non-IP based, and this feature is common with M2M.
Although some IoT devices do not directly utilize IP, the data traffic of the networks
involved are typically based on IP.
Rationale: Wearables often communicate with a smartphone via Bluetooth (non-IP),
which then relays data to the cloud via IP. This hybrid architecture blurs the line between
M2M and IoT.
IOT AND WEARABLE TECHNOLOGY DESIGN – 1ST
EDITION BY HAIDER RAAD
Table of Contents
Chapter Title Questions
1 Introduction and Historical Background 30
2 Applications 30
3 Architectures 30
4 Hardware 30
5 Communication Protocols and Technologies 30
6 Product Development and Design Considerations 30
7 Cloud and Edge: Architectures, Topologies, and Platforms 30
8 Security 30
9 Concerns, Risks, and Regulations 20
Total 260
,Chapter 1: Introduction and Historical Background
Q1.1. What are the main differences between IoT and Wearable Technology?
Answer: Communication is IP-based in IoT, while it is not necessary in wearables. Most
wearables rely on a gateway device, such as a smartphone, for configuration and
connectivity, and in most cases to enable features and process data. This is not always
true in IoT devices. IoT devices are mainly stationary; wearables, on the other hand, are
mobile since they are worn or integrated within the user's body or clothing.
Rationale: These distinctions arise from the fundamental design philosophies: IoT
devices are designed for persistent network connectivity and remote operation, while
wearables prioritize user mobility and often depend on a companion device for full
functionality.
Q1.2. What is meant by "things" in Internet of Things?
Answer: The core functionality of IoT and wearable devices starts with data acquired or
an action performed by a device. These devices are called endpoints, and they are the
"Things" in Internet of Things. The value of IoT and wearable devices is in the data
collected by these endpoints.
Rationale: The term "things" refers to physical objects embedded with sensors,
software, and network connectivity that enable them to collect and exchange data. They
are the fundamental building blocks of any IoT system.
Q1.3. What are the main differences between IoT and M2M?
Answer: Communication is IP-based in IoT, while it is usually not in M2M. M2M is
mainly point-to-point while this is not true when it comes to IoT. M2M devices are
stationary; IoT could be stationary, or portable/mobile.
,Rationale: M2M (Machine-to-Machine) communication predates IoT and typically
involves direct, isolated connections between devices. IoT extends this by leveraging IP-
based networks, enabling broader integration and cloud connectivity.
Q1.4. Can you think of other potential challenges found in IoT and wearable technology
other than the ones mentioned in this chapter?
Answer: There are several other challenges besides the ones mentioned in the chapter,
which include design-based challenges, safety, longevity, compatibility, etc.
Rationale: While the chapter covers security, privacy, standards, energy, and
connectivity, real-world deployment reveals additional concerns such as device
interoperability, long-term reliability, and physical safety in medical applications.
Q1.5. Give examples of wearable devices/applications that do not require internet
connectivity.
Answer: Ultraviolet exposure wearable device, a simple pedometer, smart socks, GPS-
enabled hiking helmets, etc.
Rationale: Many wearables operate as standalone devices, processing data locally
without needing cloud connectivity. This reduces power consumption, improves privacy,
and enables operation in remote areas.
Q1.6. List five real-world examples of smart clothing.
Answer: (A) Smart fashion applications (e.g., Tommy Jeans Xplore) which utilize an
integrated chip that can track how often the product is used and also where it was worn.
(B) Smart yoga pants (e.g., Nadi X) which can sense when yoga poses need adjustment
by using haptic feedback to create small vibrations on the body part. (C) Athlete
recovery applications (e.g., Under Armour's apparel) that absorb heat from the user's
body and reflect it back in the form of far infrared light, which is supposed to promote
muscle recovery. (D) Smart Fitness Socks (e.g., Sensoria) which use advanced textile
, sensors to provide precise data on how your foot lands while walking or running. (E) A
swimming suit equipped with a UV sensor (e.g., Neviano's swimsuits).
Rationale: Smart clothing integrates sensors and electronics into fabrics, enabling
applications from fitness tracking to recovery monitoring. The examples illustrate the
diversity of form factors and use cases in wearable technology.
Q1.7. List five real-world examples of the headwear form in wearable technology.
Answer: Virtual reality headsets (e.g., Oculus), Smart motorcycle helmets (e.g., Sena),
Smart ski goggles (e.g., RideOn), Smart hats (e.g., LifeBeam), Smart sleep headbands
(e.g., Philips).
Rationale: Headwear represents a growing category of wearables, leveraging the
proximity to the head for applications in augmented/virtual reality, safety, and health
monitoring.
Q1.8. List four components common between IoT and wearable devices (an application
of your choice).
Answer: Microcontroller, sensor, battery/power management system, LCD screen.
Rationale: Despite differences in form factor and connectivity, IoT and wearable devices
share a common core architecture: sensing, processing, power, and user interface. This
commonality enables shared design methodologies.
Q1.9. Are wearable devices a form of M2M? Why?
Answer: Typically, wearables are non-IP based, and this feature is common with M2M.
Although some IoT devices do not directly utilize IP, the data traffic of the networks
involved are typically based on IP.
Rationale: Wearables often communicate with a smartphone via Bluetooth (non-IP),
which then relays data to the cloud via IP. This hybrid architecture blurs the line between
M2M and IoT.
