5 IoT Glossary: A-F
Essential IoT Terms from ACL to Frame
Putting Numbers to It
Reference usability can be estimated by lookup coverage:
\[ U = \frac{N_{\text{resolved-lookups}}}{N_{\text{total-lookups}}} \]
Worked example: If learners perform 220 glossary lookups and 198 are resolved without leaving the section, usability is \(198/220=90\%\). Improving cross-references and examples should push this ratio higher.
Navigation
This is Part 1 of the IoT Glossary, covering terms A-F. See also:
- IoT Glossary Index - Overview and quick navigation
- Glossary G-P - Gateway through Publisher
- Glossary Q-Z - QoS through 6LoWPAN
5.1 Learning Objectives
After reviewing this section, you should be able to:
5.3 For Beginners: IoT Glossary: A-F
A glossary is like a dictionary specifically for IoT terms – it helps you understand technical vocabulary when you encounter unfamiliar words. Think of it as your IoT translation guide. When you’re reading about IoT systems and come across terms like “MQTT” or “edge computing,” you can look them up here to get clear definitions, simple explanations, and see how they relate to other concepts. The “Common confusions” sections help you avoid the mistakes that most people make when learning these terms.
- Define key IoT terms from A to F with technical precision
- Differentiate commonly confused concepts (e.g., ACL vs. RBAC, edge vs. fog computing)
- Apply appropriate terminology when discussing IoT protocols, architectures, and security
- Trace related concepts and navigate cross-references to build systems-level understanding
5.4 A
5.4.1 ACL (Access Control List)
Definition: A security mechanism that specifies which users, devices, or systems are granted or denied access to particular resources, and what operations they can perform.
In simple terms: A list that says who can do what - like a VIP list for a club that specifies which guests can enter which rooms.
Common confusions:
- ACL vs. RBAC (Role-Based Access Control) - ACLs are resource-centric while RBAC is role-centric
- ACLs define permissions per resource, not per user globally
Related terms: Authentication, Authorization, OAuth
Synonyms: access list, permission list
5.4.2 Acknowledgment (ACK)
Definition: A signal or message sent by a receiving device to confirm successful receipt of data, enabling the sender to know transmission was successful.
In simple terms: A “message received” confirmation - like texting “got it” when someone sends you important information.
Common confusions:
- ACK vs. response - ACK confirms receipt, response contains actual reply data
- Different protocols implement ACKs differently (TCP vs. UDP)
Related terms: QoS, At-least-once, Retry
Synonyms: ACK, confirmation
5.4.3 Actuator
Definition: A device that converts electrical signals or energy into physical action, enabling IoT systems to affect the physical world through motion, heat, light, or other outputs.
In simple terms: The “muscles” of an IoT system - while sensors are the eyes and ears, actuators are the hands that actually do things like turn on lights or open valves.
Common confusions:
- Actuator vs. sensor - sensors read data, actuators perform actions
- Not all output devices are actuators (displays show data but don’t perform physical actions)
Related terms: Sensor, GPIO, DAC
Synonyms: effector, output device
5.4.4 ADC (Analog-to-Digital Converter)
Definition: An electronic circuit that converts continuous analog signals (like voltage from a sensor) into discrete digital values that can be processed by a microcontroller.
In simple terms: A translator that converts real-world measurements (like temperature as voltage) into numbers a computer can understand.
Common confusions:
- ADC resolution (bits) determines precision, not accuracy
- Sampling rate and resolution are independent specifications
Related terms: DAC, Sensor, GPIO, Sampling
Synonyms: A/D converter, analog-digital converter
5.4.5 Aggregation
Definition: The process of combining multiple data points into summary statistics (sum, average, min, max, count) to reduce data volume while preserving meaningful information.
In simple terms: Summarizing lots of small measurements into useful totals - like calculating your average daily steps from thousands of individual step counts.
Common confusions:
- Aggregation loses individual data points (cannot recover original values)
- Different aggregation functions suit different use cases (average vs. sum vs. max)
Related terms: Time Series, Sampling, Telemetry
Synonyms: summarization, rollup
5.4.6 AMQP (Advanced Message Queuing Protocol)
Definition: An open standard application layer protocol for message-oriented middleware, providing reliable queuing, topic-based publish-subscribe, flexible routing, and transactions.
In simple terms: A sophisticated postal system for software - it ensures messages get delivered reliably with options for different delivery patterns and confirmations.
Common confusions:
- AMQP vs. MQTT - AMQP is more feature-rich but heavier; MQTT is simpler and lighter
- AMQP 0.9.1 (RabbitMQ) vs. AMQP 1.0 are quite different protocols
Related terms: MQTT, Broker, Publisher, Subscriber
Synonyms: none common
5.4.7 API (Application Programming Interface)
Definition: A set of defined rules, protocols, and tools that specify how software components should interact, enabling different applications to communicate and share data.
In simple terms: A menu at a restaurant - it tells you what you can order (available functions) and how to order it (required format), without needing to know how the kitchen works.
Common confusions:
- API vs. SDK - API defines the interface, SDK provides tools to use it
- REST API vs. API - REST is one style of API, not all APIs are RESTful
Related terms: REST, HTTP, Microservices
Synonyms: interface, service endpoint
5.4.8 At-least-once
Definition: A message delivery guarantee where messages are delivered one or more times, ensuring no message loss but potentially causing duplicates that receivers must handle.
In simple terms: “Better safe than sorry” delivery - the system keeps trying until it’s sure you got the message, even if that means sending it twice.
Common confusions:
- At-least-once requires idempotent receivers to handle duplicates properly
- More reliable than at-most-once but less than exactly-once
Related terms: QoS, At-most-once, Exactly-once, Idempotency
Synonyms: QoS 1 (in MQTT)
5.4.9 At-most-once
Definition: A message delivery guarantee where messages are delivered zero or one time, providing best-effort delivery without retries, which may result in message loss.
In simple terms: “Fire and forget” delivery - send the message once and hope it arrives, like shouting across a noisy room.
Common confusions:
- At-most-once is not unreliable by design - it’s appropriate for frequent, non-critical data
- Often used for high-frequency sensor data where occasional loss is acceptable
Related terms: QoS, At-least-once, Exactly-once
Synonyms: QoS 0 (in MQTT), best-effort delivery
5.4.10 Authentication
Definition: The process of verifying the identity of a user, device, or system, typically through credentials like passwords, certificates, tokens, or biometrics.
In simple terms: Proving who you are - like showing your ID at a security checkpoint before being allowed in.
Common confusions:
- Authentication vs. authorization - authentication proves identity, authorization grants permissions
- Strong authentication often requires multiple factors (MFA)
Related terms: Authorization, Certificate, Token, OAuth
Synonyms: identity verification, login
5.5 B
5.5.1 Backoff
Definition: A strategy for handling failed operations by waiting increasingly longer periods before retrying, typically using exponential growth to reduce system load during failures.
In simple terms: Being patient when something fails - instead of repeatedly hammering a locked door, wait longer between each attempt to give the system time to recover.
Common confusions:
- Exponential backoff vs. linear backoff - exponential grows faster (1s, 2s, 4s, 8s)
- Jitter (randomization) is often added to prevent thundering herd problems
Related terms: Retry, Circuit Breaker
Synonyms: exponential backoff, retry delay
5.5.2 Bandwidth
Definition: The maximum rate of data transfer across a network path, measured in bits per second (bps), kilobits (kbps), megabits (Mbps), or gigabits (Gbps).
In simple terms: The width of a pipe - a wider pipe (more bandwidth) lets more water (data) flow through at once.
Common confusions:
- Bandwidth vs. throughput - bandwidth is capacity, throughput is actual achieved rate
- Bandwidth vs. latency - bandwidth is how much, latency is how fast
Related terms: Latency, Throughput, Jitter
Synonyms: data rate, capacity, speed
5.5.3 BLE (Bluetooth Low Energy)
Definition: A wireless personal area network technology designed for short-range communication with minimal power consumption, operating in the 2.4 GHz ISM band with range up to 100m.
In simple terms: Energy-efficient Bluetooth - designed so small devices like fitness trackers can communicate wirelessly while running on tiny batteries for months or years.
Common confusions:
- BLE vs. Bluetooth Classic - BLE is optimized for low power, Classic for continuous streaming
- BLE is not backward compatible with Bluetooth Classic
Related terms: Zigbee, Thread, Mesh
Synonyms: Bluetooth Smart, Bluetooth 4.0+
5.5.4 Broker
Definition: A middleware server that receives messages from publishers and routes them to appropriate subscribers based on topics or other criteria in publish-subscribe messaging systems.
In simple terms: A post office for IoT messages - it receives mail (messages) from senders and delivers it to everyone who signed up to receive that type of mail (subscribers).
Common confusions:
- Broker vs. queue - broker routes messages, queues store them
- Brokers can cluster for high availability and scalability
Related terms: MQTT, Publisher, Subscriber, Topic
Synonyms: message broker, MQTT broker
5.6 C
5.6.1 CBOR (Concise Binary Object Representation)
Definition: A binary data serialization format designed to be extremely compact and efficient, based on JSON’s data model but optimized for constrained environments and IoT devices.
In simple terms: Compressed JSON - takes the same information as JSON but packs it into a smaller, faster-to-process binary format perfect for devices with limited resources.
Common confusions:
- CBOR vs. JSON - CBOR is binary (smaller, faster), JSON is text (human-readable)
- CBOR is used with CoAP, while JSON is typically used with HTTP
Related terms: JSON, Protobuf, Serialization, CoAP
Synonyms: none common
5.6.2 Certificate
Definition: A digital document that uses cryptographic signatures to bind a public key to an identity, enabling secure authentication and encrypted communication in TLS/SSL.
In simple terms: A digital ID card - like a passport that proves your identity, issued by a trusted authority (Certificate Authority) that vouches for who you are.
Common confusions:
- Certificate vs. private key - certificate is public, private key must stay secret
- Self-signed vs. CA-signed certificates - self-signed aren’t trusted by default
Related terms: TLS, Authentication, Encryption
Synonyms: X.509 certificate, digital certificate, SSL certificate
5.6.3 Channel
Definition: A logical or physical pathway for communication between devices, which may refer to radio frequency channels, communication ports, or logical message streams.
In simple terms: A TV channel for data - different channels carry different information, and devices tune to specific channels to send or receive data.
Common confusions:
- Physical channel (radio frequency) vs. logical channel (message stream)
- Channel overlap in Wi-Fi can cause interference
Related terms: Topic, Bandwidth, Frequency
Synonyms: communication channel, frequency band
5.6.4 Circuit Breaker
Definition: A design pattern that prevents cascading failures by monitoring for failures and temporarily stopping requests to failing services, allowing them time to recover.
In simple terms: A safety switch for software - like an electrical breaker that trips when there’s too much load, it stops sending requests to overwhelmed services to prevent total system collapse.
Common confusions:
- Circuit breaker vs. retry - circuit breaker prevents retries during known failures
- States: closed (normal), open (failing), half-open (testing recovery)
Related terms: Retry, Backoff, Dead Letter Queue
Synonyms: failure circuit, stability pattern
5.6.5 Cloud
Definition: Remote computing infrastructure accessed over the internet that provides on-demand computing resources, storage, and services without direct management by the user.
In simple terms: Someone else’s computer that you rent - instead of buying servers, you use shared computing resources over the internet and pay for what you use.
Common confusions:
- Cloud vs. edge - cloud is remote/centralized, edge is local/distributed
- Public cloud vs. private cloud vs. hybrid cloud architectures
Related terms: Edge Computing, Fog Computing, Platform
Synonyms: cloud computing, cloud services
5.6.6 CoAP (Constrained Application Protocol)
Definition: A specialized web transfer protocol designed for constrained devices and networks, using UDP for lightweight request/response communication with built-in discovery and multicast support.
In simple terms: HTTP’s smaller sibling - does similar things (GET, PUT, POST) but is designed to work on tiny devices with limited memory and battery over unreliable networks.
Common confusions:
- CoAP uses UDP (not TCP like HTTP), making it lighter but requiring application-level reliability
- CoAP is request/response while MQTT is publish/subscribe
Related terms: HTTP, MQTT, 6LoWPAN, DTLS
Synonyms: none common
5.6.7 Compression
Definition: The process of encoding data to reduce its size for storage or transmission, using algorithms that eliminate redundancy while allowing recovery of original data.
In simple terms: Packing a suitcase efficiently - arranging data to take up less space, like vacuum-sealing clothes so you can fit more in your luggage.
Common confusions:
- Lossless vs. lossy compression - lossless recovers exact data, lossy discards some
- Compression adds CPU overhead - trade-off between bandwidth and processing
Related terms: Payload, CBOR, Serialization
Synonyms: data compression, encoding
5.7 D
5.7.1 DAC (Digital-to-Analog Converter)
Definition: An electronic circuit that converts digital values from a microcontroller into continuous analog signals, enabling digital systems to control analog devices.
In simple terms: The reverse of ADC - converts computer numbers back into real-world signals, like turning a volume number into actual sound levels.
Common confusions:
- DAC vs. PWM - DAC produces true analog, PWM simulates analog through fast switching
- DAC resolution affects output precision
Related terms: ADC, Actuator, GPIO
Synonyms: D/A converter, digital-analog converter
5.7.2 Data Lake
Definition: A centralized repository that stores vast amounts of raw data in native format until needed, supporting diverse data types and enabling flexible analysis without predefined schemas.
In simple terms: A massive storage pool - dump all your data in its original form, figure out how to use it later, like keeping everything in a warehouse rather than organizing it into specific shelves.
Common confusions:
- Data lake vs. data warehouse - lakes store raw data, warehouses store processed/structured data
- Data lakes can become “data swamps” without proper governance
Related terms: ETL, TSDB, Telemetry
Synonyms: raw data repository
5.7.3 DDS (Data Distribution Service)
Definition: A middleware protocol and API standard for real-time publish-subscribe communication, providing fine-grained QoS policies and designed for mission-critical systems.
In simple terms: Industrial-strength messaging - designed for systems where milliseconds matter and failures aren’t an option, like autonomous vehicles or medical devices.
Common confusions:
- DDS vs. MQTT - DDS offers more QoS options and is broker-optional
- DDS is peer-to-peer capable, MQTT requires a broker
Related terms: MQTT, AMQP, QoS, Publisher
Synonyms: OMG DDS
5.7.4 Dead Letter Queue
Definition: A service queue that stores messages that cannot be delivered or processed successfully, allowing later analysis, reprocessing, or manual intervention for failed messages.
In simple terms: A “lost and found” for messages - when a message can’t be delivered, it goes here instead of disappearing, so you can investigate what went wrong.
Common confusions:
- DLQ vs. retry queue - DLQ holds permanently failed messages, retry queue holds temporary failures
- Messages in DLQ need manual intervention or automated remediation
Related terms: Retry, Circuit Breaker, Broker
Synonyms: DLQ, poison queue, error queue
5.7.5 Digital Twin
Definition: A virtual representation of a physical device, system, or process that mirrors real-world behavior through synchronized sensor data, enabling simulation, analysis, and optimization.
In simple terms: A virtual clone - a digital copy of a real thing that updates in real-time, letting you test changes or predict problems without touching the actual device.
Common confusions:
- Digital twin vs. simulation - twins sync with real data, simulations use models
- Digital twins require continuous data connection to their physical counterpart
Related terms: Telemetry, Platform, Edge Computing
Synonyms: virtual twin, device shadow (AWS)
5.7.6 DTLS (Datagram Transport Layer Security)
Definition: A security protocol providing TLS-equivalent encryption and authentication for datagram protocols like UDP, designed to protect CoAP and other UDP-based IoT communications.
In simple terms: Security for UDP - since TLS only works with TCP, DTLS was created to provide the same protection for connectionless protocols used by many IoT devices.
Common confusions:
- DTLS vs. TLS - DTLS works with UDP, TLS requires TCP
- DTLS handles packet loss and reordering that UDP doesn’t prevent
Related terms: TLS, CoAP, Encryption, Certificate
Synonyms: none common
5.8 E
5.8.1 Edge Computing
Definition: A distributed computing paradigm that processes data near the source of generation rather than in a centralized data center, reducing latency and bandwidth requirements.
In simple terms: Computing at the source - instead of sending all data to a distant cloud, process it locally where it’s created, like having a smart assistant in each room rather than one in a faraway call center.
Common confusions:
- Edge vs. fog - edge is at devices, fog is between edge and cloud
- Edge doesn’t eliminate cloud, it complements it
Related terms: Fog Computing, Cloud, Gateway, Latency
Synonyms: edge processing, local computing
5.8.2 Encryption
Definition: The process of encoding data using cryptographic algorithms so that only authorized parties with the correct decryption key can access the original information.
In simple terms: A secret code - scrambles your message so only someone with the right key can read it, like a lockbox that only opens with your key.
Common confusions:
- Encryption at rest vs. in transit - different protection for stored vs. moving data
- Symmetric vs. asymmetric encryption serve different purposes
Related terms: TLS, DTLS, Certificate, Authentication
Synonyms: encoding, ciphering
5.8.3 ETL (Extract, Transform, Load)
Definition: A data integration process that extracts data from sources, transforms it to fit operational needs (cleaning, formatting, aggregating), and loads it into a destination database.
In simple terms: Data processing pipeline - grab raw data, clean it up and reshape it, then store it where it’s needed, like sorting mail, organizing it by category, and delivering to the right mailboxes.
Common confusions:
- ETL vs. ELT - ETL transforms before loading, ELT loads raw then transforms
- ETL is batch-oriented, streaming alternatives exist for real-time needs
Related terms: Data Lake, TSDB, Aggregation
Synonyms: data pipeline, data integration
5.8.4 Exactly-once
Definition: A message delivery guarantee ensuring each message is processed exactly one time - never lost and never duplicated - requiring sophisticated coordination between systems.
In simple terms: Perfect delivery - the message arrives once and only once, like registered mail with confirmation that prevents both loss and duplicate delivery.
Common confusions:
- True exactly-once is extremely difficult and often impossible across distributed systems
- Most “exactly-once” implementations are actually at-least-once with deduplication
Related terms: QoS, At-least-once, At-most-once, Idempotency
Synonyms: QoS 2 (in MQTT), exactly-once semantics
5.9 F
5.9.1 Filter
Definition: A mechanism that selectively passes or blocks messages based on specified criteria such as topic patterns, content attributes, or metadata properties.
In simple terms: A message sieve - only lets through messages you care about, like email filters that sort important messages from spam.
Common confusions:
- Topic filters vs. content filters - topic filters match message routing, content filters inspect payload
- Filter syntax varies by protocol (MQTT wildcards vs. AMQP routing keys)
Related terms: Topic, Subscription, Wildcard
Synonyms: message filter, selector
5.9.2 Firewall
Definition: A network security system that monitors and controls incoming and outgoing network traffic based on predetermined security rules, creating a barrier between trusted and untrusted networks.
In simple terms: A security guard for your network - checks everyone trying to enter or leave and only allows those who meet the rules to pass through.
Common confusions:
- Firewall vs. NAT - firewall filters traffic, NAT translates addresses (though often combined)
- Hardware vs. software firewalls serve different deployment needs
Related terms: ACL, Encryption, TLS
Synonyms: network firewall, packet filter
5.9.3 Fog Computing
Definition: A decentralized computing infrastructure extending cloud capabilities to the network edge, providing intermediate processing, storage, and networking between IoT devices and centralized cloud.
In simple terms: A middle layer between devices and cloud - like regional distribution centers between factories and central warehouses, processing some things locally without going all the way to headquarters.
Common confusions:
- Fog vs. edge - fog is in network infrastructure (routers, gateways), edge is at end devices
- Fog computing was coined by Cisco, edge computing is more general
Related terms: Edge Computing, Cloud, Gateway
Synonyms: fog networking, edge-cloud continuum
5.9.4 Frame
Definition: A data unit at the data link layer (Layer 2) containing header information, payload data, and error-checking trailer used for transmitting packets across physical network segments.
In simple terms: An envelope for network data - wraps the actual message (packet) with addressing and error-checking information needed for local network delivery.
Common confusions:
- Frame vs. packet - frames are Layer 2 (local network), packets are Layer 3 (routed network)
- Frame size limits (MTU) affect how packets are fragmented
Related terms: Packet, Payload, MTU
Synonyms: data frame, Layer 2 PDU
Worked Example: Glossary-Driven Troubleshooting of “At-least-once” Duplicate Messages
Scenario: Your MQTT sensor publishes temperature readings, but cloud dashboard shows occasional duplicates (same reading, same timestamp, received twice).
Glossary lookup (At-least-once): > “A message delivery guarantee where messages are delivered one or more times… potentially causing duplicates that receivers must handle.”
Aha moment: MQTT QoS 1 (at-least-once) is working correctly - duplicates are expected, not a bug!
Follow cross-reference → Idempotency: > “A property of operations where performing them multiple times produces the same result… enabling safe retries without unintended side effects.”
Solution: Add idempotency key to messages:
{
"device_id": "sensor-001",
"timestamp": "2026-02-15T10:30:00Z",
"temperature": 23.5,
"message_id": "a3b2c1" // <-- Deduplication key
}Dashboard code checks message_id - if already received, skip duplicate.
Key Insight: The glossary’s cross-references led from “at-least-once” → “idempotency” → solution. Understanding related concepts revealed the fix.
Decision Framework: Using Glossary Cross-References to Deepen Understanding
When you look up a term, follow this strategy:
| Your Goal | Strategy | Example |
|---|---|---|
| Quick definition | Read definition, move on | “What does ADC mean?” → Read, done |
| Design decision | Read definition + “Related terms” + “Common confusions” | “ADC vs. DAC for my actuator?” → Follow links |
| Troubleshooting | Read definition + “Common confusions” + cross-references | “Why QoS not working?” → Explore related concepts |
| Learning | Read definition + all cross-references + “Related terms” chapters | “I want to understand MQTT deeply” → Follow every link |
Effective glossary usage pattern:
- Look up primary term (e.g., “MQTT”)
- Read “Common confusions” (reveals frequent mistakes)
- Follow “Related terms” links (Broker, Publisher, Subscriber, QoS)
- Check synonyms (helps with literature searches)
- Jump to detailed chapter for implementation guidance
Key Insight: Glossary is a network of connected concepts, not isolated definitions. Following cross-references builds systems-level understanding.
Common Mistake: Skipping “Common Confusions” Section
The Mistake: Reading just the definition, skipping “Common confusions,” then making exactly that mistake in your project.
Example:
Term looked up: At-least-once - ✅ Read definition: “Messages delivered one or more times” - ❌ Skipped “Common confusions”: “At-least-once requires idempotent receivers” - ❌ Result: Built system assuming no duplicates, system breaks when duplicates occur
Another example:
Term looked up: ADC - ✅ Read definition: “Converts analog to digital” - ❌ Skipped “Common confusions”: “ADC resolution (bits) determines precision, not accuracy” - ❌ Result: Bought 16-bit ADC expecting 0.001°C accuracy, got 0.5°C due to sensor noise
The Fix: ALWAYS read “Common confusions” - it contains the mistakes that 80% of developers make. Learning from others’ mistakes is cheaper than repeating them.
Key Insight: The “Common confusions” section is the most valuable part of each glossary entry - it’s collected wisdom from thousands of IoT projects.
Concept Relationships
Glossary terms cluster into functional groups:
- Security chain: ACL → Authentication → Authorization → Certificate → Encryption
- Messaging reliability: ACK → At-least-once/At-most-once/Exactly-once → QoS
- Hardware interfaces: ADC ← Sensor data, DAC → Actuator control, GPIO for both
- Architecture continuum: Cloud ← Fog ← Edge (processing moves closer to source)
Terms reference across chapters: Understanding “Broker” (here) requires context from MQTT chapter. “Edge Computing” glossary entry points to detailed Edge Computing chapter.
Common confusions prevent mistakes: Each entry’s “Common confusions” section prevents the mistakes 80% of developers make (e.g., “ADC resolution ≠ accuracy”).
See Also
Glossary navigation:
- Glossary G-P - Gateway through Publisher
- Glossary Q-Z - QoS through 6LoWPAN
Referenced chapters (examples from terms covered): - MQTT Protocol - Detailed broker, QoS, pub/sub - Security Fundamentals - Authentication, authorization, encryption - Edge Computing - Edge vs. fog vs. cloud
External resources:
- RFC Index - Official protocol specifications
- IEEE Xplore - Standards documentation
- IoT Glossaries Compared - Industry terminology
Common Pitfalls
1. Looking up terms without reading the ‘Common confusions’ sections
Many IoT terms are easily confused (edge vs fog, authentication vs authorization, QoS 0 vs QoS 1). The ‘Common confusions’ subsections within each glossary entry specifically address these distinctions. Skipping them leads to persistent misunderstandings that propagate into design decisions – for example, confusing QoS levels leads to over-engineering reliability in systems that don’t require it.
2. Memorizing definitions without understanding application context
Knowing that BLE stands for Bluetooth Low Energy is less useful than knowing when to use BLE versus Zigbee versus LoRaWAN. Each glossary entry includes a ‘When to use’ or ‘IoT application’ note. Focus on the usage context, not the textbook definition – IoT engineering is about choosing the right tool for each constraint, not reciting acronym expansions.
3. Treating glossary as a substitute for chapter content
Glossary definitions are intentionally brief to serve as quick references. A 2-sentence glossary entry on MQTT cannot substitute for the MQTT chapter’s coverage of QoS levels, retained messages, last will and testament, and broker architecture. Use glossary for term lookup; use chapters for conceptual understanding.
5.10 Summary
This section covered 32 essential IoT terms from A through F:
| Category | Terms | Examples |
|---|---|---|
| Security | 8 | ACL, Authentication, Authorization, Certificate, Encryption, Firewall |
| Protocols | 6 | AMQP, CoAP, BLE, DDS, DTLS |
| Architecture | 5 | Broker, Cloud, Edge Computing, Fog Computing, Digital Twin |
| Data | 5 | Aggregation, CBOR, Compression, Data Lake, ETL |
| Reliability | 5 | ACK, At-least-once, At-most-once, Exactly-once, Backoff, Circuit Breaker |
| Hardware | 3 | Actuator, ADC, DAC |
| Networking | 4 | Bandwidth, Channel, Filter, Frame |
5.12 What’s Next
| If you want to… | Read this |
|---|---|
| Look up IoT terms from G through P | Glossary G-P |
| Look up IoT terms from Q through Z | Glossary Q-Z |
| Review the complete unified glossary | Full IoT Glossary |
| Apply these terms in capstone project work | Capstone Projects |
| Study mathematical foundations for IoT calculations | Mathematical Foundations |