1.4 Evolution and the Current State of the Industry
1.4.1 The Embryonic Stage: RFID and Sensor Networks (1999-2008)
As a periodization in the engineering narrative, the technical starting point of the IoT can be traced along three parallel threads: early applications of RFID (Radio Frequency Identification) in supply chains, academic breakthroughs in wireless sensor networks (WSN), and the first industrial trials of M2M (Machine to Machine) communication in vertical industries. These three threads solved, respectively, the most fundamental capabilities of the IoT — identifying things, sensing the environment, and machine communication.
RFID: Giving Things a Digital Identity
The engineering origin of the term "IoT" is tied directly to item identification. In 1999, Kevin Ashton first coined the term "IoT"; he then co-founded the Auto-ID Center at the Massachusetts Institute of Technology and drove the concept toward reality. The core idea was to attach a unique electronic identifier to every item, and then use the Internet to achieve automated information sharing and management on a global scale.
An RFID system consists of three parts: tags, readers, and a backend system. The reader activates the tag chip with a radio-frequency signal; the tag returns the data stored on it (such as the Electronic Product Code, EPC); and after decoding, the reader sends the data over the network to the backend system for business processing. A simplified structure is shown in the diagram below.
The strongest early industrial push for RFID came from retail. Several large retailers required their core suppliers to attach RFID tags to cartons and pallets in order to improve inventory turnover and logistics visibility. The practice proved the point: giving items a digital identity substantially reduces manual scanning costs and data-entry errors, with no optical alignment required. The technical boundaries of the time were equally clear — the read range of passive tags is constrained by the operating frequency band and tag design; under ultra-high-frequency passive schemes the effective distance is typically within the near field or a few meters; and in environments with metal and liquids, electromagnetic coupling attenuates severely and missed reads are frequent. This meant that RFID was no universal answer in real deployment: it demanded engineering trade-offs according to item type, operating environment, and required read distance.
Wireless Sensor Networks: Organizing Sensing into a Mesh
Where RFID emphasized "identification", another technical thread pursued "sensing" — large numbers of distributed, self-organizing sensor nodes collecting physical-environment data (temperature, humidity, vibration, light) and converging it over a wireless multi-hop network to a central node. This is the wireless sensor network.
In 2003, the US magazine Technology Review ranked wireless sensor network technology first among the ten technologies that would most change people's lives in the future. Academic research around WSN followed in volume: low-power node design, self-organizing network protocols, and data fusion among nodes. Take the LEACH (Low Energy Adaptive Clustering Hierarchy) protocol as an example: it rotates cluster heads at random to balance node energy consumption and thereby extend the lifetime of the whole network. One engineering trade-off of that era deserves equal attention: this random strategy is not stable in heterogeneous networks. If a few high-power nodes get mixed into a region, random rotation may temporarily put a node with unreliable communication in the cluster-head role, causing local data aggregation to be lost. The same trade-off still appears today in discussions of self-organizing network schemes for edge nodes.
M2M: Device Conversations over Mobile Networks
Beyond RFID and WSN, the telecom industry was working on something else: letting machines talk to each other directly over cellular networks. M2M refers to automated data exchange between devices, and between devices and backend systems, carried over mobile communication networks (GPRS/2G in the early days) or dedicated wireless channels.
Typical scenarios included remote automatic meter reading for electric power, upload of security alarm signals, and GPS position tracking of freight vehicles. These applications had common features: small per-transmission payloads, low sending frequency, and hard requirements on network reliability and terminal battery life. The engineering practice of the time was blunt: temperature and humidity transmitters with embedded SIM cards reported data on a schedule over GPRS. Data formats were agreed separately by each vendor's system, and backend interface protocols were mutually incompatible. These rough realities later showed practitioners the gap between "being connected" and "being networked". Protocol fragmentation and interoperability difficulties are precisely the core challenges that the subsequent IoT platform layer needed to solve; Chapter 4 develops them.
Why It Is Called the "Embryonic Stage"
Seen through the engineering thread of the embryonic period: without RFID tags, items lacked a stable digital identity; without the accumulated research on WSN, low-cost, large-scale sensing lacked an engineering foundation; without M2M's industrial trials, the IoT's commercial viability lacked first-hand verification. The three threads had no unified architecture, but they separately conquered the three basic capabilities of identification, sensing, and communication. It was precisely this technological reserve from the embryonic period that gave the later strategic pushes by governments and industry solid ground to build on.
1.4.2 The Growth Stage: National Strategies and Industrial Applications (2009-2019)
Taking the policy window around 2009 as the dividing line, several major economies one after another wrote the capability to connect "things" into their digital-economy and industrial-upgrading agendas. Before that point, the engineering value of the IoT had been verified mainly by academia and a few vertical industries; afterward, policy groundwork and industrial deployment compounded each other, moving the IoT from experimental projects toward broader engineering deployment.
From Round Table to National Strategy
Seen as policy-industry interaction, IoT development in this period took several distinct paths. The United States emphasized enterprises proposing smart-infrastructure visions, pushed forward jointly by government investment and the industrial ecosystem — a strong market-pull coloring. China leaned more toward top-level design linked with local demonstration projects: "Sensing China", the strategic emerging industries program, and subsequent special plans together shaped its early industrial clusters. Japan's u-Japan vision paid more attention to ubiquitous networks and livelihood applications, and Korea laid out plans in a similar direction; the European Union attached more importance to unified architecture, interface specifications, and data-privacy governance. These paths have no absolute ranking, but together they show one thing: the IoT's move from laboratory to industry relied not just on sensors and networks — it also required the combined pull of policy, markets, standards, and application scenarios.
Table 1-4 compares the strategic layouts of the major economies across three dimensions: launch timing, core positioning, and dominant mode.
Table 1-4 Comparison of Major Economies' IoT Strategies
| Economy | Launch Milestone and Time | Core Positioning | Dominant Mode |
|---|---|---|---|
| Japan | 2004, u-Japan | Ubiquitous network society | Government planning + industry coordination |
| United States | 2008, Smarter Planet (attracted wide attention in 2009) | Intelligent infrastructure | Industry-led, policy-assisted |
| China | 2009, Sensing China | Strategic emerging industries | Top-level design, administrative push |
Industrial Deployment: Smart Homes and Connected Vehicles
The smart home was the consumer market's first tangible breakthrough. Early smart bulbs and smart plugs required users to download an app, configure Wi-Fi, and set timers; the chain of operations was too long, and no rigid demand formed. The real shift in market perception came from smart thermostats capable of learning: the device regulates temperature automatically according to the user's daily habits — the user sets no rules, and the device completes the behavioral adaptation itself. This intuitive interaction won consumers' first large-scale endorsement of the idea that "things can save you effort". Connected vehicles were another growth band. Expanding 3G/4G coverage and falling GPS module costs turned the automobile into a fast-moving networked node. Automakers successively built vehicle data platforms that collect position, speed, battery status, and other parameters in real time; once OTA updates entered service, in-vehicle software could be updated online like a phone's system. This set of capabilities later directly supported autonomous driving's accumulation of real-road data.
An Engineering Judgment: After the Policy Groundwork
Between 2009 and 2019, the IoT completed two transformations: strategic groundwork gave the industry initial resources and market confidence, while smart homes and connected vehicles won the first large-scale acceptance by capital and consumer markets of the business logic of "connecting everything". But the other side of this history deserves equal caution: policy-driven early projects carried substantial waste from duplicated construction and incompatible standards — a single city might build several streetlight control systems, each outsourced by a different department to a different vendor; and cross-brand interoperability in smart homes remained a pain point a decade later. These costs pushed practitioners toward a realization: what the IoT needed was not more demonstration projects, but a platform system that could be reused at scale. That judgment leads directly to the architecture discussion of Chapter 2.
Figure 1-13 charts this path of "policy groundwork → industrial deployment".
1.4.3 The Explosion Stage: Large-Scale Deployment and Platformization After 2020
In periodization terms, the scale deployment of the IoT visibly accelerated once the 2020s began. Three forces compounded: low-power wide-area network (LPWAN) standards gradually matured, platform ecosystems moved from concept to substance, and demand for remote operations and maintenance was amplified rapidly by the external environment. The industry often calls this stage the "explosion period", but its arrival was not the result of any single technical breakthrough — it was a systemic phenomenon produced when communications, platforms, and market demand converged.
LPWAN's rollout at scale was the first trigger point. After NB‑IoT and Cat‑M were standardized under the 3GPP framework and refined by industry over several years, they met the conditions for large-scale deployment by the early 2020s. NB‑IoT emphasizes deep coverage and extremely low power, suiting static terminals such as water meters and smoke detectors; Cat‑M supports higher data rates and mobility, fitting wearables and vehicle tracking. Carriers took the two technologies to market as foundational IoT capabilities, and communication module procurement costs fell markedly during this stage — moving massive connectivity from technical argument into budget planning, something rarely seen in the preceding accumulation period.
The second trigger point was platformization competition shifting from concept to substance. During this period, cloud vendors rolled out managed IoT services in concentration: device management, rule engines, time-series data storage, and security authentication were packaged as standard products. Open-source communities also contributed a rich set of choices. Edge computing gained wide acceptance in turn, and deployment models changed from "pure cloud" to three-layer "cloud-edge-device" collaboration: programmable nodes deployed close to devices carry out data preprocessing and local decisions, and only necessary data is uploaded to the cloud. The platform market turned from a technology-selection contest into ecosystem lock-in competition, with differentiated positioning becoming gradually clear along two dimensions: ecosystem completeness and the strength of carrier support.
The third trigger point came from the pandemic. During the global pandemic, remote monitoring, contactless maintenance, and automated inspection went from "future trends" to "immediate necessities". Factories needed unattended production, hospitals needed remote monitoring of vital signs, and buildings needed intelligent ventilation adjustment. Most of these scenarios had previously sat in technical validation or short-term trials; the pandemic pushed enterprises directly into bulk equipment procurement and project acceptance. Project cycles were compressed drastically, and the engineering maturity of sensors, communication modules, and cloud platforms was driven sharply upward in short pulses. This stage also exposed the security gaps of remote operations and maintenance — expanded on in Chapter 8's discussion of "IoT security technology".
To make the change in project deployment patterns before and during the pandemic concrete, here is a hypothetical comparison:
Table 1-5 Project deployment patterns before and during the pandemic
| Dimension | Before the Pandemic (Typical Pilot Phase) | During the Pandemic (Emergency Deployment Phase) |
|---|---|---|
| Demand source | Forward-looking corporate pilots | Driven by emergency needs |
| Project cycle | Planning 3–6 months, implementation 3–6 months | Planning 1–2 months, implementation 1–2 months |
| Equipment selection | Emphasis on long-term stability; long selection cycles | Availability first; rapid procurement of mature solutions |
| Deployment scale | Hundreds to thousands of terminals | Thousands to tens of thousands of terminals, or more |
| System integration | Mostly custom development; poor interface compatibility | Mature platform-based solutions; ready out of the box |
| Acceptance criteria | Complete functionality, expansion interfaces reserved | Core functions running first, iteration to follow |
The comparison reveals an engineering fact: the so-called "explosion period" on a technology maturity curve usually needs the "trigger point" of an external, non-technical event. The pandemic happened to play exactly that role.
Looking back at this stage as a distinct period yields a more measured judgment: the acceleration of IoT deployment was in essence the result of three currents converging — mature technology, complete ecosystems, and changed demand. Cloud platforms and edge computing went from "optional extras" to standard infrastructure, and device connectivity was upgraded from pilots to large-scale deployment. What this stage accumulated prepared two key prerequisites for the later fusion of AI and the IoT: more usable data fuel, and a stable, layered computing foundation.
1.4.4 The State of the Industry and Key Data
Judging the scale of the IoT industry cannot rest on a single report. The market definitions used by different organizations vary widely: the broad definition covers sensors, modules, terminals, connectivity services, cloud platforms, application software, system integration, and industry solutions; the narrow version counts only connection subscription revenue. Still another kind of report folds into its statistics any digitalization spending that touches "things" at all. The three versions of the "market" are in essence three different things, and comparing them side by side produces nothing but confusion.
The pragmatic approach is to let go of the attachment to absolute figures and turn to a few structural questions: which industries are paying? Does growth come from rising connection counts or from rising data value? Toward which layer is the center of value migrating?
Industry Distribution: Different Scenarios, Different Logic
In industry practice, manufacturing, transportation and logistics, and energy/utilities occupy the top three positions in total spending year after year. This is no coincidence — what the three share are large physical-asset bases and long operating chains, so returns on digitalization investment are comparatively easy to quantify.
Manufacturing's core needs are equipment condition monitoring and predictive maintenance. The loss caused by one hour of unplanned downtime on a critical machine can cover a full year of sensor and platform costs. Transportation and logistics emphasize fleet management and cold-chain tracking: logistics firms use real-time location and temperature data to cut cargo-loss rates and thereby obtain lower insurance rates. In energy/utilities, smart meters, substation inspection, and oil and gas pipeline monitoring have been deployed in many places for years; constrained by infrastructure renewal cycles, this field grows at a relatively measured pace, but single-project amounts far exceed consumer-grade applications — an IoT retrofit of a provincial power grid may cost more than all of a comparable city's smart streetlight projects combined.
Healthcare and retail have smaller bases but comparatively prominent growth. Healthcare is driven mainly by compliance requirements, such as end-to-end traceability of pharmaceutical cold chains; retail focuses on operational refinement, such as restocking optimization for unmanned retail cabinets. The table below summarizes the driving logic and growth characteristics of the major vertical industries.
Table 1-6 IoT Investment Characteristics of Major Vertical Industries
| Industry | Core Drivers | Typical Scenarios | Growth Pace | Single-Project Scale |
|---|---|---|---|---|
| Manufacturing | Reduce downtime losses, improve yield | Predictive maintenance, equipment monitoring | Steady growth | Medium to large |
| Transportation & logistics | Operational visibility, lower cargo loss | Fleet management, cold-chain tracking | Rapid growth | Medium |
| Energy/utilities | Asset monitoring, automated inspection | Smart meters, pipeline monitoring | Mature stage, gentle growth | Large |
| Healthcare | Compliance traceability, supply-chain transparency | Pharmaceutical cold chain, equipment asset management | High growth on a small base | Small to medium |
| Retail | Operational refinement, better customer experience | Unmanned cabinets, intelligent inventory management | High growth on a small base | Small |
The Center of Value Migrating Upward
Mapping the IoT industry value chain reveals a clear migration trajectory. The bottommost connectivity layer — communication modules, SIM cards, connection-management platforms — has the lowest entry barrier, matured earliest, and was also the first to descend into a price war. At volume procurement, NB-IoT module prices fell to levels that support mass rollout, and connectivity itself is becoming a standardized commodity. The service of "getting your devices online" is, by itself, genuinely hard to build a long-term barrier on.
The platform layer above it — device management, data access, rule engines — has become the main battlefield of the cloud-computing giants, who dominate this layer on the strength of infrastructure advantages and AI ecosystems. Independent IoT PaaS companies face considerable pressure: customer-acquisition costs are high and differentiation is hard to establish; most have either been acquired or have exited the market.
The real growth in value is migrating toward the intelligence layer: data analysis, AI prediction, and automated decision-making driven by large models. Per-device output value in industrial-grade IoT far exceeds the consumer grade — the predictive-maintenance value of one CNC machine tool may be hundreds of times that of a smart speaker. This is why industry investment keeps tilting toward industrial fields rather than stopping at smart speakers and wristbands. The Agentic Center of IoT DC3 is a typical example — it wires large language models into operational workflows, letting the model not only "read the data" but also "act on devices", and moving from conversational operations toward autonomous decision-making (see Chapter 7).
The figure below outlines the core path of this value migration:
Judging an Industry's Stage: Three Quick Questions
Faced with an IoT project in some vertical industry, you can quickly judge which stage it is in with the following three questions:
- Has connectivity already been standardized into a purchasable commodity? If so, the industry has passed the "should we connect" stage and entered the "what to do after connecting" stage. In manufacturing, for example, wireless sensors can now be procured directly as standard modules, whereas agricultural IoT still often requires customized integration.
- Is platform-layer competition dominated by a few giants, or wide open with many players? If the latter, the industry has not yet completed the foundational work of data standardization. The smart-building field holds large numbers of fragmented platforms, and interoperability between devices remains a pain point; industrial sectors, by contrast, have gradually settled on services from a few mainstream cloud platforms.
- Does the share of the project budget going to AI and analytical decision-making exceed the spending on connectivity and hardware? If it does, the industry has entered the value zone driven by the intelligence layer. This shift is underway in transportation and logistics — the cost center of fleet-management platforms has moved from GPS trackers to route-optimization and driver-behavior-analysis modules.
Connectivity is the foundation, but not the destination. The next section discusses the natural-language interaction, knowledge retrieval, and candidate-decision capabilities that large models add to IoT, while also making one boundary explicit: a probabilistic model cannot replace protocols, permissions, or deterministic control.