Chapters

23 IoT Requirements: Five-Layer and Seven-Layer Models

applications
iot
requirements
Listen
Uses your device's voice. Tap ▶ beside any paragraph to hear just that one.
  • Podcast audio coming soon
  • Character narration audio coming soon
Lecture
Video lecture coming soon. The slides are the lecture for now.
Ask AI
Pick a prompt. We copy it for you and open an AI service; paste it there. Nothing is sent to IoTClass.

23.1 From a Reading to a Responsibility

A five-layer model is a useful first map of an IoT system. A seven-layer view splits the backend when data and business duties need clear owners. The distinction matters because a single cloud box can hide storage choices, schema choices, and ownership choices that a real design has to give to someone.

Follow the chapter’s smart thermostat: a temperature sensor captures a reading, local processing reduces the data, connectivity carries it onward, and cloud and application work turn it into user value. Every requirement has to land somewhere along that path. The problem is deciding where processing should happen and who owns the result; the two layer models give us different levels of detail for that decision.

Review IoT Requirements: Connectivity Costs and Trade-Offs for the preceding evidence. We will first compare the models, then use the device-selection example to connect architecture choices to quality, cost, and value.

23.2 Learning Objectives

  • Map the five-layer teaching view to the seven-layer IoT model.
  • Trace data through sensing, transport, processing, application, and business layers.

KEY CONCEPTS

  • Layer boundaries

    Physical, edge, connectivity, cloud, and application work transform readings into user value.

  • Three ingredients

    Thing plus computation plus internet reach is the minimum IoT filter.

  • Weighted priorities

    Quality goals are not equal requirements; prioritize the few that fit the domain.

  • Total cost of ownership

    Purchase price, battery visits, firmware updates, and integration shape the decision.

23.3 Visual Bridge: From 5 Layers to 7

The five-layer model is a teaching shortcut. Detailed reference architectures split the backend into more specific data and business layers when you need sharper design boundaries.

Which part of the compact model is doing too much work? Figure 1 puts the two models side by side so the answer is visible.

Mapping between the chapter's five-layer IoT model and a more detailed seven-layer reference architecture
The five-layer teaching model maps to a seven-layer reference architecture.

Start on the left of Figure 1 with the five-layer column. Physical, edge, and connectivity line up almost one to one with the seven-layer column beside them, so nothing is lost there. The difference sits at the top. The cloud block on the left fans out into data accumulation and data abstraction on the right. The separate application block maps to application work and the new business-collaboration layer above it. One word was hiding storage choices, schema choices, and ownership choices that a real design has to give to someone.

Use the five-layer version when you are learning the flow. Switch to the seven-layer reference view when you need to separate storage, abstraction, applications, and business processes explicitly.

23.4 Interactive Quiz: Match Concepts

Try it

Interactive Quiz: Match Concepts

Open activity

23.5 Interactive Quiz: Sequence the Steps

Try it

Interactive Quiz: Sequence the Steps

Open activity

23.6 Label the Diagram

Try it

Label the Diagram

Open activity

Check knowledge

Visual Bridge: From 5 Layers to 7

Check knowledge

23.7 Code Challenge

Try it

Code Challenge

Open activity

23.8 Requirements in Practice

The Three Ingredients Test asks whether a product has a thing, computation, and internet connectivity. A local wireless link such as Bluetooth alone makes a connected product; an end-to-end internet path makes it part of an IoT system. IoT Introduction develops these minimum requirements, while Device Evolution follows the Embedded → Connected → IoT progression.

Beyond that minimum, eleven characteristics describe quality goals: Ubiquitous, Smart, Agile, On Demand, Blend into Background, Secure, Low Maintenance, Fast, Upgradable, Growing, and Adaptable. No device excels at all eleven. Prioritize 3–4 for the use case: medical IoT emphasizes Secure and Fast; agriculture emphasizes Growing and Low Maintenance; consumer applications emphasize On Demand and Upgradable. IoT Perspectives explains why stakeholders weight these characteristics differently.

Requirements also drive technology selection. Wi-Fi suits local high-bandwidth devices; LoRa and LoRaWAN address long-range, battery-powered field and warehouse monitoring; Cellular IoT covers NB-IoT/LTE-M for mobile assets. Protocol comparison uses the same framework to choose Wi-Fi, LoRaWAN, cellular, or a gateway pattern. The Simulation Playground collects interactive IoT protocol experiments.

23.9 Knowledge Check

23.10 IoT Requirements Quiz

Check knowledge

IoT Requirements Quiz

Check knowledge

23.11 Eleven Characteristics Selection

Scenario: A hospital system must choose between three remote patient monitoring (RPM) wearable devices for 5,000 chronic heart failure patients. All three meet minimum IoT requirements (Thing + Computation + Internet). The comparison connects quality priorities to cost and modeled clinical value.

The Three Devices:

  • Device A: $89, 48-hour battery, 15-minute data interval, U.S. Food and Drug Administration (FDA) cleared, proprietary protocol, and no over-the-air (OTA) updates because devices must be returned.
  • Device B: $199, 7-day battery, 5-minute data interval, FDA cleared, standard BLE plus FHIR, and automatic OTA updates.
  • Device C: $145, 72-hour battery, 1-minute data interval, FDA cleared, standard protocols, and OTA updates with manual approval.

Quality priorities for healthcare RPM

For this medical wearable comparison with 5,000 deployed devices, the 11 characteristics receive different priorities.

  • Secure, critical 9/10: Patient health data needs strong protection; Health Insurance Portability and Accountability Act (HIPAA) compliance is required when the deployment is a covered entity or business associate.
  • Fast, high 7/10: Heart failure alerts need less than five-minute latency.
  • Low Maintenance, high 8/10: 5,000 devices with frequent battery visits would be unsustainable.
  • Upgradable, high 8/10: FDA-required firmware patches and clinical protocol changes must reach the fleet.
  • Growing, medium 6/10: The system may expand to 10,000 patients, but not 100,000.
  • Adaptable, medium 5/10: Epic EHR integration matters, but the scope is defined.
  • Smart, medium 6/10: Local anomaly detection helps, but is not the primary decision driver.
  • On Demand, low 4/10: Medical monitoring is periodic, not an instant-response consumer interaction.
  • Ubiquitous, low 3/10: The device works at home and clinic, not everywhere.
  • Agile, low 4/10: Clinical protocols change slowly.
  • Blend into Background, low 3/10: Patients expect visible medical devices.

Scores and their rationale

  • Secure, 20%: Device A scores 7/10 because the proprietary design is hard to audit; Devices B and C score 9/10 with standard protocols.
  • Fast, 15%: Device A scores 5/10 because 15-minute intervals are too slow; Device B scores 9/10 at five minutes; Device C scores 10/10 at one minute.
  • Low Maintenance, 20%: Device A scores 4/10 with a two-day battery; Device B scores 10/10 with a seven-day battery; Device C scores 6/10 with a three-day battery.
  • Upgradable, 20%: Device A scores 2/10 because updates require return; Device B scores 10/10 with automatic OTA; Device C scores 7/10 with manual OTA.
  • Growing, 10%: Device A scores 4/10 due to vendor lock-in; Devices B and C score 9/10 with open standards.
  • Adaptable, 10%: Device A scores 3/10 with proprietary integration; Device B scores 10/10 with FHIR; Device C scores 9/10 with standards but a narrower integration set.
  • Smart, 5%: Device A scores 6/10 with basic alerts; Device B scores 8/10 with edge anomaly detection; Device C scores 7/10 with cloud-only processing.

Weighted Scores:

  • Device A: (7×0.20) + (5×0.15) + (4×0.20) + (2×0.20) + (4×0.10) + (3×0.10) + (6×0.05) = 4.4/10
  • Device B: (9×0.20) + (9×0.15) + (10×0.20) + (10×0.20) + (9×0.10) + (10×0.10) + (8×0.05) = 9.5/10
  • Device C: (9×0.20) + (10×0.15) + (6×0.20) + (7×0.20) + (9×0.10) + (9×0.10) + (7×0.05) = 8.1/10

Five-layer and seven-layer models expose different boundaries for processing, service, and business decisions. The same requirement priorities inform those boundaries.

Five-year total cost of ownership (TCO)

  • Hardware for 5,000 devices: Device A costs $445,000; Device B costs $995,000; Device C costs $725,000.
  • Battery replacements at $25 per visit: Assume 4,500 annual visits for Device A, 250 for Device B, and 3,500 for Device C; these illustrative counts are not derived from the stated battery lives. Device A costs $112,500 per year, or $562,500 over five years; Device B costs $6,250 per year, or $31,250; Device C costs $87,500 per year, or $437,500.
  • Firmware updates: Device A costs $225,000 for return shipping across three updates; Device B costs $0 with OTA; Device C costs $75,000 for two manual updates.
  • Integration: Device A costs $150,000 because of proprietary integration; Device B costs $25,000; Device C costs $40,000.
  • Five-year TCO: Device A totals $1,382,500; Device B totals $1,051,250; Device C totals $1,277,500.

Modeled clinical value

The 72%, 94% and 96% early-alert rates are hypothetical evaluation inputs, not demonstrated clinical sensitivity.

  • Prevented hospitalizations per 5,000 patients per year: Device A prevents 360, Device B prevents 470, and Device C prevents 480.
  • Cost per hospitalization: All three use the same $12,500 avoided-cost assumption.

Annual modeled savings of $4.5M, $5.875M and $6M follow only if the assumed hospitalization counts and $12,500 avoided cost hold.

  • Five-year clinical value: Device A produces $22.5M, Device B produces $29.375M, and Device C produces $30.0M.

Decision:

Device B wins on quality score and five-year TCO; Device C has the highest modeled clinical value:

  1. Highest quality score: 9.5/10 vs. 8.1 (Device C) vs. 4.4 (Device A)
  2. Lowest TCO: $1.05M vs. $1.28M (Device C) vs. $1.38M (Device A)
  3. Clinical value: $29.4M (Device B) vs. $30M (Device C) vs. $22.5M (Device A)

Device B costs $110 more per unit than Device A, but saves $331K in 5-year TCO and delivers $6.9M more in clinical value.

Device C has slightly higher modeled clinical value ($600K over 5 years) but costs $226K more than Device B and scores lower on critical characteristics (Low Maintenance, Upgradable).

Key Lessons:

  1. Not all 11 characteristics matter equally: For medical RPM, 75% of the decision weight comes from just 4 characteristics (Secure, Fast, Low Maintenance, Upgradable). Domain determines priorities.

  2. TCO ≠ purchase price: Device A’s $89 price looks attractive, but 5-year TCO is 31% higher than Device B due to battery replacement visits and firmware update logistics.

  3. Characteristics predict TCO: Low Maintenance and Upgradable directly correlate with operational costs. In this comparison, the lower scores accompany higher long-term costs.

  4. Weighted scoring prevents bias: Without structured scoring, humans gravitate toward “favorite features.” Device C’s 1-minute data frequency is impressive but matters far less than Device B’s 7-day battery and auto-OTA for a 5,000-device deployment.

The decision framework begins with the 11 characteristics, identifies 3–4 non-negotiable priorities, and assigns weights summing to 100%. Each option then receives scores on the prioritized characteristics. The weighted total sits alongside TCO and domain-specific value, with a documented rationale for the decision. This makes the trade-offs visible before a favorite feature or purchase price dominates the comparison.

Practice

Eleven Characteristics Selection

Read the activity

23.12 Checkpoint: Weighted Decisions

Practice

Checkpoint: Weighted Decisions

Read the activity

The final data-flow section ties the chapter back to architecture: every requirement has to land somewhere in the physical, edge, connectivity, cloud, or application layer.

23.13 IoT Data Flow Layers

IoT systems move data through five architectural layers—Physical, Edge, Connectivity, Cloud, and Application—with each layer transforming raw sensor readings into actionable user value. The cycle is Sense → Connect → Process → Act, repeating continuously.

In the smart thermostat’s illustrative architecture, the sensor rate, payload, history, cloud service, and savings below are assumed values:

  1. Physical Layer (Data Capture): A DHT22 temperature sensor measures 18.3°C every 30 seconds. This generates 2,880 readings per day; at 2 bytes each, the raw data totals 5.76 kB/day.
  2. Edge Layer (Local Processing): The ESP32 microcontroller averages readings locally. Edge Computing explains how local processing supports Fast and Low Maintenance requirements.
  3. Connectivity Layer (Data Transmission): Wi-Fi sends the aggregated reading and trend flag.
  4. Cloud Layer (Intelligence and Storage): An Amazon Web Services (AWS) Lambda function compares the current pattern against historical data.
  5. Application Layer (User Value): A mobile app displays “Heating starts in 15 min.” The assumed benefit is 30% energy savings ($180/year) compared with always-on heating.

Understanding this data flow reveals where processing should happen. Sending every 30-second reading in a 50-byte payload would use 144 kB/day, while aggregating to one such payload every five minutes uses 14.4 kB/day, a 10× reduction in transmitted payload bytes. At a hypothetical fixed price per byte, a $2/month transfer charge would fall to $0.20/month. Actual Wi-Fi and cloud charges depend on the service and protocol overhead. Edge aggregation can therefore reduce traffic and sometimes cost.

23.14 Concept Relationships

The five-layer model expands into complete system design patterns in Reference Architectures. Use the seven-layer view when processing, service, and business decisions need separate boundaries and owners.

23.15 Summary

IoT needs a thing, computation, and internet reach. Its continuous Sense → Connect → Process → Act cycle crosses physical, edge, connectivity, cloud, and application duties. The seven-layer view makes backend storage, abstraction, applications, and business processes explicit.

The eleven characteristics are quality benchmarks, not equal checkboxes. Prioritize 3–4 for the use case and compare weighted quality, total cost of ownership, and domain-specific value. The medical wearable example shows why a low purchase price can conceal battery, update, and integration costs; the thermostat shows why local aggregation can reduce transmitted payload bytes.

23.16 Key Takeaways

Choose technology from requirements, then assign each requirement to a layer and an owner. A more detailed layer map is useful when it exposes responsibilities that one cloud box would hide.

23.17 See Also

Hi, I’m Ada. What do you need?

Find help

Let’s find what you need

Find a lesson or return to your module guide.

Give feedback

Help improve this chapter

Tell us what helped or what needs fixing.

Tips

Try a small next step

A few ways to get more from this chapter.

Ask AI

Continue the conversation

Take the conversation further with your preferred assistant.

AI help is available in supported modules when enabled in Settings.

No live person answers on independent study. Feedback does not promise a personal reply.

For welfare or safety concerns, follow your school’s procedures outside IoTClass.