The Core Ideas Behind Connecting Everyday Physical Objects to the Internet

UPI Study › Courses › Ethics in Technology › Free lessons › Lesson 14.4 Free with a free account

The Core Ideas Behind Connecting Everyday Physical Objects to the Internet

Ethics in Technology · Chapter 14: Tomorrow's Technology: AI, Biotech, IoT, and the Connected FutureSection 14.4 · lesson 92 of 11615 min · free with a free account

← Where Biology Meets Technology — The Science of Modifying Living Systems for Human BenefitNext lesson: Sensors, Wearables, and Smart Devices — The Hardware That Powers the Connected World →

Earn 3 college credits for Ethics in TechnologyRecommended for credit by NCCRS · Computer Science 195 · self-paced · one payment, lifetime access

In this lesson

How sensing, networks, applications, and security make an IoT system work.

  • Identify the ingredients of an Internet of Things device.
  • Explain perception, network, and application layers.
  • Distinguish wireless connectivity from MQTT messaging.
  • Evaluate edge computing and the lessons of Mirai.

Free study notes

Get this lesson's notes by email

The key points and 4 practice questions with answers, in your inbox. One email, free.

One email. Unsubscribe in one click.

Transcript

Everything said in the video, section by section (1,870 words). Read along, or search it.

Tomorrow's Technology: AI, Biotech, IoT, and the Connected Future

Connecting Everyday Objects

The Internet of Things connects everyday physical objects with systems that collect and use their data. Examples include thermostats, doorbells, medical equipment, factory machinery, and vehicles carrying connected sensors. Useful operation combines physical sensing or action with processing and an automatic communication capability. We will follow a simplified architecture, from the physical event through networking to the application. Then, distinguish wireless communication technologies from MQTT, which organizes messages through a central broker. Edge computing changes where processing occurs. Some decisions happen near the source of the data. That choice can reduce delay and bandwidth demands, while introducing limits on local resources. Connected devices also create security dependencies, even when each individual object appears small or inexpensive. Mirai demonstrated how neglected devices could be recruited together and used to disrupt major internet services. By the end, explain both the operation of an IoT system and its security responsibilities.

Physical Things, Digital Data

Sensing, Processing, and Connectivity Work Together

An IoT device combines a physical capability with processing and a network connection for automatic exchange. The physical capability can sense something, such as temperature or movement. It can also perform an action. A motor that locks a door is an actuator, even though its purpose differs from measurement. Processing prepares readings, interprets local information, or runs the control logic required by the device. Communication lets that information travel without a person manually entering each individual reading into another system. A phone or gateway may supply the route toward the broader network, rather than direct internet access. An ordinary thermometer read only by a person does not supply that automatic connected behavior. A thermometer logging readings to a connected phone app illustrates what the communication capability adds. Worldwide counts reach billions, but estimates vary with definitions and the methods used to count devices. The useful question here is what functions the object performs, rather than one supposedly exact global total.

Three-Layer Model

From Physical Events to Useful Information and Action

The three-layer model separates physical interaction, communication, and the use of information within the system. The perception layer contains sensors and actuators, where digital systems meet events in the physical world. Examples include temperature sensors, cameras, motion detectors, RFID tags, and motors opening valves or locks. The network layer carries information to its destination, using communication links and connecting equipment. Wi-Fi, Bluetooth Low Energy, Zigbee, cellular systems, gateways, and routers can contribute to that function. The application layer interprets or displays information, producing useful alerts, decisions, dashboards, or mobile experiences. A temperature reading generally travels upward through those functions, from sensing toward a useful application. An instruction can also travel back toward an actuator, enabling a physical response to the information. The layers describe roles within the overall design. A real device can perform more than one role. For a smart lock, the motor belongs to perception because it takes action in the physical world.

Wireless Links

Choose Radio Connectivity for the Intended Workload

Wireless choices should match the amount of data, power supply, coverage requirements, and intended workload. Wi-Fi commonly suits powered devices such as smart speakers and cameras that transfer substantial information. The illustrative indoor range here is roughly thirty to one hundred meters, depending heavily on conditions. Bluetooth Low Energy is designed for low power, supporting devices such as wearables near a phone. Its illustrative range is ten to one hundred meters; different implementations can achieve very different distances. Zigbee supports low-power communication and mesh networking, often serving lights, door sensors, and similar devices. Ten to one hundred meters per hop illustrates ordinary coverage, with relaying extending the network’s reach. Not every device necessarily relays traffic; the mesh depends on suitable intermediate devices and their connections. Walls, interference, and antenna design affect actual performance. Settings and workload also influence performance and energy consumption. Treat these ranges as examples, rather than fixed limits guaranteed by the name of a protocol.

Two Different Roles

MQTT Organizes Messages over an Existing Connection

Wireless connectivity and messaging perform different jobs, even when they operate within the same connected system. Wi-Fi, Bluetooth Low Energy, and Zigbee provide capabilities for transmitting information through wireless links. A device can reach a broader network through a phone or gateway, rather than directly by itself. Wired and cellular connections supply other options. The choice depends on the deployment and its physical requirements. MQTT is a lightweight messaging protocol, operating over a suitable existing connection, commonly using TCP/IP. It organizes communication through named topics and a server commonly called the message broker. Clients publish messages or subscribe to receive messages relevant to the topics that interest them. A small protocol overhead helps systems with constrained processing capacity or limited network bandwidth. However, MQTT does not replace the radio technology that provides a device’s underlying wireless communication. Nor does every IoT system require exactly one radio and MQTT; designers can choose other approaches.

Publish and Subscribe

The Broker Connects Publishers with Interested Subscribers

The diagram shows a thermostat publishing a temperature message to a broker, rather than addressing every receiver. Its named topic describes the information, allowing interested clients to arrange subscriptions that match. In this example, the topic identifies the temperature for the home’s living room. A phone app subscribes so it can show the current reading to the person using it. Automation rules also subscribe, allowing the same information to contribute to an appropriate control decision. The broker receives the publication and routes the message toward clients with matching subscriptions. For this message path, clients communicate through the broker rather than sending directly to each other. Adding a new subscriber need not require the thermostat to learn that subscriber’s network address. This separation simplifies changes. Reliable operation still depends on the broker, network, and application settings. Lightweight messaging therefore helps organize communication without eliminating the system’s availability or security responsibilities.

Compute near the Source

Edge Computing Reduces Dependence on a Distant Round Trip

Edge computing places processing on or near the device that generates the information being examined. Some decisions can occur locally, instead of requiring every reading to reach a distant cloud first. Reducing the round trip can lower delay, which matters when a response cannot wait. Sending summaries or selected events can also reduce bandwidth use and the cost of transmitting raw data. Local functions may continue during an internet outage, provided they do not require unavailable remote services. Privacy can improve when sensitive raw video or audio remains on-site within an appropriate design. However, local devices often have less processing power, storage, or available energy than large cloud resources. A complex analysis may still belong remotely, while a well-defined urgent response stays near the sensor. Edge and cloud processing can complement each other. They are not mutually exclusive choices. Check the actual dependencies before assuming that every edge system works offline or keeps every reading private.

Factory Example

A Local Decision Can Protect a Time-Sensitive Process

Consider a factory sensor detecting a dangerous vibration pattern in an operating piece of machinery. A cloud-only approach sends readings outward, waits for processing, and depends on a response returning. That delay could be unacceptable when a machine must stop promptly to avoid additional damage. An edge controller can evaluate the relevant pattern nearby and issue a local stop instruction. A summary of the event can then travel to the cloud. Remote processing supports later investigation or broader analysis. The urgent decision and the longer analysis can use different processing locations within the same system. Limited local resources can be acceptable when the required task is specific and carefully designed. The system must still meet its response-time requirement, including the behavior of sensors, controllers, and actuators. Local processing does not by itself guarantee that the judgment is correct or the physical response safe. The example explains why location matters, while keeping the complete system’s performance and safety requirements visible.

Mirai’s Security Lesson

Neglected Devices Can Become a Coordinated Attack Network

A botnet is a collection of compromised devices that an operator can command to act together. A distributed denial-of-service attack uses coordinated traffic. It exhausts a target’s ability to serve legitimate users. Mirai, identified in twenty sixteen, recruited connected devices such as routers, cameras, and digital video recorders. A central weakness was exposed remote administration combined with common factory credentials that remained unchanged. Unauthorized access allowed vulnerable devices to be infected and recruited, often without their owners understanding the compromise. Commands could then coordinate many small devices, combining their traffic into a much larger disruptive force. This describes the historical mechanism conceptually; the practical lesson concerns preventing exposure and unauthorized control. Weak update support and large populations of neglected identical devices can magnify the consequences of basic oversights. The original botnet reached hundreds of thousands of compromised devices, according to the Justice Department’s account. One device’s low price or apparent insignificance does not remove its responsibilities within a connected environment.

Historical Timeline

Mirai Linked Household Devices with Wider Service Disruption

Mirai emerged during the late summer and early fall of twenty sixteen, recruiting vulnerable connected equipment. On September twentieth, the KrebsOnSecurity website experienced an attack. Its report estimated traffic near six hundred twenty gigabits per second. That figure describes a historical estimate, rather than the capacity of every later Mirai-based attack. On September thirtieth, source code was published under the alias Anna-senpai, enabling other operators and variants. On October twenty-first, attacks against DNS provider Dyn disrupted access to many major online services. Affected sites included Twitter, Netflix, Reddit, and Spotify, illustrating the consequences of a shared infrastructure dependency. Reports of a one point two terabit-per-second peak were not confirmed in Dyn’s initial analysis. In December twenty seventeen, Paras Jha, Josiah White, and Dalton Norman pleaded guilty to the Mirai conspiracy. Related later click-fraud activity formed a separate case involving Jha and Norman; it was not identical to every Mirai attack. The timeline connects device weaknesses with wider disruption, while separating confirmed events from uncertain measurements.

Defensive Practices

Reduce Exposure before a Device Joins the Network

Begin defense before exposing a device, replacing factory credentials with strong and unique account credentials. Change default account names where supported. Recognize that product capabilities differ between devices. Keep firmware updated, and consider whether the manufacturer provides credible support and a workable update mechanism. A device that cannot receive needed security maintenance can remain vulnerable long after installation. Disable remote administrative access that serves no necessary purpose, reducing opportunities for unauthorized entry. Separate IoT equipment from sensitive systems through network segmentation with appropriate restrictions between segments. That can limit what an already compromised camera reaches, reducing the possible consequences within the local network. Segmentation alone does not prevent every infection or stop a compromised device from generating outbound attack traffic. Configuration, updates, access controls, and monitoring therefore complement one another across the device’s lifecycle. The connected system requires maintained security, rather than assuming that an isolated configuration choice solves every risk.

Review and Apply

Follow the Data, Then Evaluate the Dependencies

For the first review question, identify sensing or actuation, processing, and automatic network exchange. For the second, place the smart lock’s motor in perception because it performs a physical action. For the third, separate MQTT’s messaging and broker routing from the radio technology carrying wireless communication. The publisher sends a topic message, and the broker directs it toward matching subscribed clients. For the fourth, use the factory vibration example to explain why an urgent response may belong locally. That choice trades large remote resources for a shorter decision path. The requirements still need verification. For the fifth, explain how exposed access and unchanged credentials enabled recruitment into the Mirai botnet. Many small compromised devices could then act together, overwhelming services that legitimate users depended on. Trace the complete path from perception through communication and application, including any return to physical action. A responsible design considers performance, availability, privacy, and the maintenance duties of owners and providers together.

About Ethics in Technology at UPI Study

Ethics in Technology (Computer Science 195) is a self-paced online course of 116 video lessons in 15 chapters, from cybersecurity basics, privacy and surveillance to big data, hacking, malware, network defense, intellectual property, cybercrime, encryption, emerging technology and digital citizenship. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Compare: Cybersecurity vs Ethics in Technology · Which ethics course?

Why take it here

Why students take Ethics in Technology with UPI Study

The right and wrong of the digital worldEthics in Technology looks at the choices technology forces on people and organizations: security and privacy, surveillance and the law, big data, hacking and cyber warfare, malware and breaches, intellectual property, cybercrime, encryption, artificial intelligence and responsible digital citizenship. It suits computer science, information technology and business degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Ethics in Technology carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About The Core Ideas Behind Connecting Everyday Physical Objects to the Internet

What are the three layers of IoT architecture?
The basic IoT architecture has a perception layer, a network layer, and an application layer. The perception layer holds sensors and actuators, such as temperature sensors, cameras, RFID tags, and the motor in a smart lock. The network layer moves data using Wi-Fi, Bluetooth Low Energy, Zigbee, cellular links, gateways, and routers. The application layer turns data into alerts, dashboards, and decisions, and can send commands back to actuators.
What is MQTT, and how does it work?
MQTT is a lightweight publish-subscribe messaging protocol for IoT, usually running over TCP/IP. Devices publish messages to named topics on a central server called a broker, and clients subscribe to the topics they want. A thermostat might publish a living-room temperature that both a phone app and an automation rule receive, without knowing either one's address. MQTT organizes messages; it does not replace radio technologies like Wi-Fi or Zigbee.
What is edge computing in IoT?
Edge computing processes data on or near the device that produces it instead of sending everything to a distant cloud. That cuts delay and bandwidth, can keep some functions running during an internet outage, and can keep sensitive video or audio on-site. For example, a factory controller can stop a machine immediately when it detects dangerous vibration, then send a summary to the cloud for analysis. Edge devices have limited resources, so edge and cloud often work together.
How did the Mirai botnet take down major websites in 2016?
Mirai infected routers, cameras, and digital video recorders that exposed remote access and still used factory default passwords, recruiting hundreds of thousands of devices. On September 20, 2016, it hit KrebsOnSecurity with roughly 620 Gbps of traffic. After its source code was posted on September 30, an October 21 attack on DNS provider Dyn disrupted Twitter, Netflix, Reddit, and Spotify. Three men pleaded guilty in December 2017. Changing default credentials and updating firmware are the basic defenses.

About the Ethics in Technology course

How many college credits is Ethics in Technology?
Ethics in Technology (Computer Science 195) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Ethics in Technology cost and what is included?
$250, paid once, with lifetime access: all 116 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. It is sold on its own and is not part of UPI Study PRO.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Ethics in Technology take?
It is self-paced with no deadlines. The 116 lessons total about 28 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Ethics in Technology.

116 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Ethics in Technology
3 credits · NCCRS
Enroll →