3.1 Sensing Layer Overview
3.1.1 The Role and Core Capabilities of the Sensing Layer
When an IoT project moves from blueprint to deployment, the first thing that stalls it is usually not the choice of cloud platform or database, but the most bottom-layer question of all: how does the machine "touch" the physical world? Whether a fan is running smoothly or shaking, whether a container is at the port or on the highway, whether a motor is overloaded or normal — if the system cannot acquire this information, everything downstream — monitoring and alarms, predictive maintenance, closed-loop control — is empty talk. The technology layer responsible for this first step is the sensing layer.
The sensing layer sits at the very bottom of the IoT reference architecture, facing the physical world directly. In the classic four-layer reference model (sensing layer, network layer, platform layer, application layer), the sensing layer plays the part of an organism's "nerve endings" — it does not carry data over long distances and rarely performs complex computation. But its role is sharply defined: to transform the analog, non-electrical information of the physical world into electrical signals and numerical values that digital systems can process.
Around this core role, the sensing layer must deliver four foundational capabilities (the summary below distills the author's years of engineering practice):
- Data acquisition: using sensors to convert physical quantities (temperature, pressure, vibration, gas concentration, and so on) into processable electrical signals. This is the most fundamental function; without it, no downstream analysis is possible. Sensor selection directly determines data quality — whether the measurement range covers the target span, whether the accuracy meets threshold-alarm requirements, whether the response time can keep up with dynamic changes. Getting any one of these dimensions wrong can lead upper-layer applications to make wrong decisions based on wrong data.
- Identity recognition: using technologies such as RFID (Radio Frequency Identification), QR codes, and NFC (Near Field Communication) to answer "what is this thing" or "which individual is it". Early IoT explorers regarded radio-frequency identification as the bridge connecting the physical world to the information world, which marked identity recognition as an official core direction of IoT. In engineering practice, metal surfaces call for anti-metal tags, and near liquids the antenna's polarization direction or operating frequency must be adjusted — these interference factors directly affect recognition success rates.
- Position sensing: providing the spatial coordinates of monitored objects by means of GNSS (Global Navigation Satellite System, e.g. GPS and BeiDou), base-station positioning, UWB (Ultra-Wideband), and BLE (Bluetooth Low Energy) beacons. The accuracy differences among these technologies call for judgment by the engineer according to the scenario: precise docking of an AGV inside a warehouse needs high-precision positioning, while coarse route monitoring of transport vehicles tolerates tens of meters of error.
- Preliminary processing: performing signal conditioning (amplification, filtering), analog-to-digital conversion (ADC, Analog-to-Digital Converter), data formatting, and even simple logic decisions (such as threshold alarms) at the signal source. This is the sensing layer's first step from "passive acquisition" toward "active processing". For example, an industrial temperature sensor can carry built-in logic: when the temperature exceeds its upper limit, it actively sends an alarm instead of waiting for the platform to poll on schedule. This edge preprocessing markedly reduces network-bandwidth and cloud-computing pressure.
Each of the four capabilities looks straightforward on its own; combined, they give the IoT system a capability that traditional information systems lack: machines can obtain raw data from the physical world directly and automatically, with no manual entry or hand-copied meter readings. ISO/IEC 30141 is a multi-domain IoT reference-architecture standard; it does not prescribe a specific layered model, but the sensing-related entities within it are defined as a subsystem responsible for data acquisition, identification, and control; its core output is a digital mapping of the physical world.
The logical boundary of the sensing layer must be drawn strictly. The sensing layer's responsibility ends once it hands data to the network layer for long-distance transmission. Take the wireless sensor network (WSN) as an example: the short-range communication among sensing nodes, routing nodes, and sink nodes (over ZigBee or BLE, for instance) belongs entirely to the sensing layer. But the functional module in the sink node that uploads over long distances via 4G/5G or Ethernet already falls within the scope of the network layer. In practice, physical devices often "cross the boundary" — a smart gateway may play a dual role, sensing layer (connecting sensors) and network layer (cellular uplink), at the same time. During architecture design the layers must be kept logically distinct, or responsibility boundaries blur in later operations and maintenance. For example, the sensor interface circuitry on a gateway belongs to the sensing layer, while the 4G module inside the gateway and its protocol stack belong to the network layer; adjusting a sensor should not disturb the network communication configuration, and vice versa.
In terms of architectural interfaces, the sensing layer produces "streams of point values with semantics" — the vibration amplitude of a fan, the RFID tag ID of a vehicle, the UWB coordinates of an AGV in a warehouse. The network layer carries these value streams to the platform layer reliably and with low latency. The application layer, on receiving the information, performs rule evaluation, statistical analysis, or model inference, and may generate control commands fed back into the physical world, forming a complete closed loop from acquisition through analysis and decision to execution. Within this chain, the sensing layer supplies raw data that is as accurate, timely, and semantically complete as possible. This, together with the time-series data processing of Chapter 5, "The Platform Layer and Data Processing," and the AI model inference of Chapter 7, "AIoT and Agent Applications," forms a complete data loop, while the architecture model of Chapter 2 (the classic four layers plus an intelligence layer embedded within the application layer) carries this logical layering and mode of collaboration forward.
New demands in the move from connected things to intelligent things: a traditional sensor has done its duty as long as it outputs stable values, but concrete scenarios impose stronger demands. For example, a vibration sensor on industrial rotating equipment that uploads only amplitude on a schedule cannot capture sudden shocks; a cold-chain transport temperature sensor that alarms only when the reading drifts past a threshold cannot trace degradation trends. Such scenarios require sensors with self-diagnosis capability (actively reporting accuracy drift), adaptive sampling of frequency (raising the sampling rate only on anomalies), and even preliminary on-site anomaly judgment. In real projects, engineers must assess: which data must be processed at the edge to relieve network pressure? Which latency-tolerant data can be sent to the cloud for more complex model inference? This trade-off directly affects the selection and cost of sensing-layer components. And to unify vastly heterogeneous physical devices onto one platform, the thing model introduced in later sections is the key abstraction layer; we return to it in detail in Section 3.7.
Engineering tip: performance parameters such as accuracy and resolution quoted in sensor datasheets are usually measured under standard laboratory conditions. On an industrial site, the combined effects of supply ripple, common-mode interference, temperature and humidity variation, and mechanical stress can markedly affect actual accuracy. When selecting parts, refer to the "typical operating conditions" section of the datasheet and budget margin for the worst case.
3.1.2 Sensing Layer Evolution: From Simple Acquisition to Intelligent Sensing
When engineers troubleshoot abnormal vibration on a cold-storage fan, they often run into this trap: the sensor reports acceleration at a fixed cadence of once per minute, and by the time the amplitude finally crosses the preset threshold and the alarm light comes on, the bearing balls are already worn with pits visible to the naked eye. An even more passive scenario: the sensor keeps acquiring and keeps reporting, the battery drains within less than one maintenance cycle, and the node has long been offline by the time the maintenance crew arrives.
The root of such problems is not that the sensor itself lacks precision, but the fixed-sampling pattern that has been in use for decades — acquire the physical quantity at a fixed interval and forward it unchanged over an I²C or SPI interface to the microcontroller, with no data understanding, no priority judgment, and still less any decision-making ability. This architecture still works where data volumes are small and the environment is stable, but in industrial vibration monitoring, large-scale environmental sensing, and asset tracking, the flaws surface immediately: a fixed sampling rate either misses transient shocks or wastes power in steady state; a fixed threshold cannot distinguish a real fault from normal operating fluctuation; and the uplink is crowded with large volumes of redundant "all is well" packets.
What pushes the sensing layer from "simple acquisition" toward "intelligent sensing" is a pair of compute-downward forces pressing from the architectural level. The first is edge computing: deploy edge nodes near the sensor clusters — industrial PCs on the shop floor, smart gateways in buildings, collection boxes in agricultural greenhouses — so that filtering and denoising, initial anomaly screening, and data aggregation are completed at the data source, easing the pressure on uplink bandwidth and end-to-end latency. The second is on-device AI and adaptive sampling: give milliwatt-level sensor nodes a preliminary judgment capability of their own and let them adjust the rhythm of acquisition and reporting dynamically according to the state of the data, taking aim at the balance between node power consumption and the risk of missed reports. The two forces point in the same direction — moving "judgment" forward to the place closest to the physical world; but the hardware selection, model deployment, and engineering boundaries involved on each side are far from trivial, and the mechanisms are detailed in Section 3.5 and Section 3.6.