HCIP-IoT flashcards
HCIP-IoT · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- IoT four-layer architecture
- Perception/device layer collects data via sensors and actuators; network layer transports it; platform layer manages devices and data; application layer delivers vertical services to end users.
- MQTT QoS levels
- QoS 0 delivers at most once with no acknowledgment; QoS 1 delivers at least once and may duplicate; QoS 2 uses a four-way handshake for exactly-once delivery.
- CoAP protocol basis
- CoAP is a REST-style request/response protocol over UDP defined in RFC 7252, using GET, POST, PUT and DELETE methods, with an observe option for server push to clients.
- LwM2M object model
- LwM2M layers device management over CoAP. Object 3 is Device, Object 4 is Connectivity Monitoring, Object 5 is Firmware Update, and Object 1 is the Server object.
- CAP theorem for IoT
- A distributed platform cannot guarantee consistency, availability and partition tolerance together. Most IoT data planes favor availability with eventual consistency across regions.
- Gateway protocol translation
- A gateway converts southbound device protocols such as ZigBee, Modbus or BLE into northbound MQTT, HTTPS or CoAP toward the cloud platform, abstracting device heterogeneity.
- Transparent transmission mode
- In transparent mode the gateway forwards raw device payloads and the platform parses them; in non-transparent mode the gateway parses and normalizes data before uplink.
- Gateway offline caching
- When the uplink fails, the gateway buffers telemetry locally and replays it after reconnection, preserving message order and de-duplicating by message identifier.
- ZigBee device roles
- A ZigBee network has one coordinator that forms the PAN, routers that extend and relay the mesh, and end devices that communicate only through their parent node.
- BLE GATT hierarchy
- BLE attribute data is organized as services containing characteristics, each with a value and optional descriptors; clients discover and read or write these attributes.
- RFID UHF passive tags
- UHF passive RFID operates around 860 to 960 MHz, harvesting energy from the reader's field and achieving read ranges of several meters without a battery.
- Wi-Fi 802.11n capability
- 802.11n operates at 2.4 and 5 GHz with up to four spatial streams and 40 MHz channels, reaching a theoretical 600 Mbps, far above ZigBee or BLE rates.
- NB-IoT bandwidth
- NB-IoT occupies a single 180 kHz resource block and can be deployed stand-alone, in-band within LTE, or in the LTE guard band, using 15 kHz or 3.75 kHz uplink spacing.
- NB-IoT power saving
- Power Saving Mode lets a device sleep deeply while remaining registered; extended DRX lengthens paging cycles, together enabling multi-year battery life for stationary meters.
- eMTC versus NB-IoT
- eMTC uses 1.4 MHz, supports handover, connected-mode mobility and VoLTE, while NB-IoT offers narrower bandwidth, deeper coverage and no handover support.
- LoRa spreading factor
- LoRa chirp spread spectrum uses spreading factors SF7 to SF12; higher factors increase airtime and receiver sensitivity, extending range at the cost of data rate.
- LoRaWAN device classes
- Class A devices open receive windows only after uplink, Class B adds beacon-scheduled slots, and Class C listens continuously; Class A consumes the least power.
- Product model definition
- On OceanConnect or IoTDA a product model declares service identifiers, properties with access modes, and commands with parameters, enabling platform parsing of device payloads.
- Device shadow state
- The device shadow stores reported state from the device and desired state from applications, letting apps read or set values without waiting for a sleeping device.
- FOTA versus SOTA
- Firmware Over the Air updates the device's low-level firmware image, while Software Over the Air updates application software; both use campaign management and integrity checks.
- Platform rule engine
- A rule engine subscribes to device data changes, online and offline events, and command responses, then forwards or transforms data to storage, message queues or functions.
- LiteOS kernel features
- Huawei LiteOS is a lightweight real-time kernel offering preemptive priority scheduling, static and dynamic memory pools, inter-process communication, and a kilobyte-scale configurable footprint.
- Edge computing placement rule
- Latency-critical control, bandwidth filtering and local inference run at the edge; cross-site analytics, model training and long-term storage run in the cloud.
- Edge store-and-forward
- Edge nodes persist data locally during connectivity loss and synchronize with the cloud on reconnection, requiring conflict resolution rules for divergent updates.
- DTLS for constrained devices
- DTLS provides TLS-equivalent confidentiality and integrity over UDP, making it the transport security layer for CoAP and LwM2M traffic on constrained IoT devices.
- Hardware root of trust
- A secure element or TPM stores the device private key in tamper-resistant hardware, so credentials cannot be extracted even if the application firmware is compromised.
- IoT replay attack
- An attacker captures a valid authenticated message and retransmits it later; defenses include nonces, timestamps and monotonically increasing sequence numbers.
- Secure boot chain
- Each boot stage verifies the cryptographic signature of the next stage before executing it, preventing unauthorized or tampered firmware from running on the device.
- Smart metering connectivity
- Electricity and water meters typically use NB-IoT or PLC uplinks with low message rates, high device density and a ten-year battery target, favoring coverage over throughput.
- Industrial IoT latency design
- Deterministic control loops run at the edge with Modbus or OPC-UA southbound and MQTT northbound, prioritizing reliability, time synchronization and bounded latency.
- Solution volume sizing
- Daily data volume equals device count multiplied by messages per day multiplied by payload bytes; this figure sizes broker throughput, storage and platform quotas.
- Smart home hybrid topology
- Wi-Fi carries high-bandwidth devices such as cameras, while ZigBee or BLE handles battery sensors; a local hub keeps automation running when the WAN link fails.