Patenting IoT and Connected Device Inventions

The Internet of Things — devices that sense, communicate, and act — creates patent opportunities at every layer of the stack: the sensor hardware, the communication protocol, the edge processing, the cloud analytics, and the actuator response. But IoT patents also face unique challenges: standards-essential patents (SEPs) on communication protocols, multi-actor infringement across device-cloud architectures, and the dense prior art landscape in wireless connectivity.

What Is Patentable

Device Hardware

Novel sensor designs, antenna configurations, power management circuits, energy harvesting mechanisms, ruggedised housings for industrial IoT, and miniaturised form factors. Hardware claims are the most straightforward IoT patents — standard apparatus claim strategy applies.

Communication and Protocol Innovation

Novel communication methods between devices, specific data packet structures, synchronisation mechanisms, mesh networking algorithms, and low-power communication techniques. These may intersect with standards (Bluetooth, Zigbee, LoRa, 5G, Matter) — triggering SEP/FRAND considerations if the technology becomes essential to a standard.

Edge and Cloud Processing

Data fusion from multiple sensors, anomaly detection algorithms, predictive analytics, device management systems, and over-the-air update mechanisms. These are software claims and must be drafted with the hardware-software integration approach described in the software patent guide.

System-Level Integration

The specific combination of sensors, connectivity, processing, and actuation that solves a defined problem. System claims are often the most commercially valuable IoT patents because they capture the complete commercial product.

The Multi-Actor Infringement Problem

IoT systems are inherently distributed — a sensor on a factory floor, a gateway in the server room, a cloud platform in a data centre, and a dashboard on a manager's phone. A method claim requiring steps performed by each of these components may face divided infringement: no single entity performs all the steps.

Drafting solution: Lead with system claims that define all components as part of a single system operated by one entity. "A system comprising: a sensor device configured to [measure]; a gateway configured to [transmit]; a server configured to [process]; and a client interface configured to [display]." The IoT platform provider operates the entire system and is the single direct infringer.

File separate apparatus claims for individual components (the sensor alone, the gateway alone) — these allow enforcement against component manufacturers who sell individual devices.

SEPs in IoT

IoT devices that implement wireless standards (Wi-Fi, Bluetooth, Zigbee, LoRa, 5G, Matter) use technology covered by standards-essential patents. If your device uses these protocols, you need licences from SEP holders — typically obtained through patent pools (Avanci for cellular IoT, Via Licensing for Wi-Fi/Bluetooth) or through chipset suppliers who include downstream patent coverage.

If your innovation becomes part of a standard, you gain mandatory adoption but accept FRAND licensing obligations.

Jurisdiction Comparison

The EU Cyber Resilience Act (CRA) introduces mandatory cybersecurity requirements for connected devices sold in the EU — including security update obligations, vulnerability disclosure, and conformity assessment. IoT inventors targeting the EU must design for CRA compliance from the start. Patent claims covering security features that satisfy CRA requirements have additional commercial value.

Sources

1. USPTO — Patent Examination Resources — US examination guidance for IoT and connected device patents
2. EPO — Internet of Things Patent Trends — European patent landscape for IoT technologies
3. WIPO — IP and the Internet of Things — Global policy and IP considerations for IoT
4. 35 U.S.C. § 271 — Infringement of Patent — US statute relevant to multi-actor and divided infringement in IoT systems
5. EPO Guidelines for Examination — Technical effect requirements for software/hardware integration claims