A hardware device positioned between constrained edge devices and backend network infrastructure, aggregating device traffic and translating between the device-facing protocol — LoRaWAN, NB-IoT, Modbus, and similar — and the IP-based network the collected data is forwarded over.

Key Points

Bridges device-facing protocols (LoRaWAN, NB-IoT, Bluetooth, Zigbee, Modbus, and similar) to backend IP connectivity (Ethernet, cellular, Wi-Fi) the collected data is forwarded over
Frequently performs local edge processing — filtering, aggregation, basic analytics — before forwarding data onward, reducing backhaul bandwidth and cloud processing load
A single gateway typically serves many end devices simultaneously, making gateway placement and coverage planning a major factor in overall network economics
Often the natural point to enforce device authentication, encryption, and network segmentation for an otherwise resource-constrained edge device population
Distinct from an API gateway, which routes and manages application-layer traffic between backend services rather than aggregating physical-layer device traffic

Concept

End devices — sensors, meters, actuators — communicate with the gateway using whatever low-power protocol they're built around, often without any direct IP connectivity of their own. The gateway receives this traffic, performs whatever local processing or filtering is configured, and forwards the result onward over its own IP-based backhaul connection (Ethernet, cellular, satellite, or Wi-Fi) to a network or application server. This structure lets individually resource-constrained end devices participate in a broader IP network without each one needing its own IP stack, power budget, or backhaul connection.

Explainer

The gateway is the single point where an otherwise fragmented population of constrained, resource-limited end devices becomes economically manageable as a network — without it, every sensor would need its own independent backhaul connection, which is rarely viable given the power, cost, and complexity constraints those devices are specifically designed around. This concentration also makes the gateway the natural place to enforce security controls (authentication, encryption, network segmentation) that individual constrained devices often cannot implement themselves, but it correspondingly makes the gateway a single point of failure for every device it serves — a gateway outage takes an entire local device population offline simultaneously, unlike a single device failure. For CE verticals, gateway placement and redundancy planning is a first-order design decision: a mining or energy site deploying a wide-area sensor network needs to weigh gateway density (more gateways, smaller footprint each, better redundancy) against the capital and backhaul cost of each additional gateway, a tradeoff that shapes the entire network's economics and resilience profile far more than any individual end device's characteristics do.