Knowledge Hub:
IoT Definitions
Connectivity & Networks
Definition: Second-generation mobile network for voice/SMS and limited data.
Why this matters: Still available in some countries/areas as a fallback, but being phased out.
When relevant: For legacy devices or as a last resort in difficult coverage situations.
Definition: Third-generation mobile network with higher data speeds than 2G.
Why this matters: Already switched off or nearly switched off in many countries — planning around it creates risk.
When relevant: Only for existing installations; migration is preferable.
Definition: Mobile network with stable data connections and broad coverage.
Why this matters: Often the default for IoT when you need reliability and throughput.
When relevant: Cameras, routers, gateways, tracking with frequent updates.
Definition: New-generation mobile network with higher capacity and lower latency, depending on rollout.
Why this matters: Not always necessary for IoT — mainly valuable for high-data use cases or many connected devices.
When relevant: Video or edge use cases, busy environments, future-ready routers.
Definition: 4G variant for IoT with lower power consumption and better indoor penetration.
Why this matters: Balances coverage, battery life and true mobility.
When relevant: Battery-powered devices that move, such as trackers, and sensors with regular updates.
Definition: Narrowband IoT network for deep indoor coverage and extremely low power consumption.
Why this matters: Ideal for small messages and long battery life — less suitable for mobile use cases.
When relevant: Smart metering, fixed sensors, very low message frequency.
Definition: Availability of a network in a given area.
Why this matters: Coverage maps are indicative; behaviour inside buildings or containers determines real-world success.
When relevant: Always — especially indoors, in rural areas, basements or metal enclosures.
Definition: Network reach inside buildings.
Why this matters: IoT often fails indoors, not outdoors.
When relevant: Retail, industrial halls, basements, technical rooms.
Definition: Connection to a foreign network through agreements between operators.
Why this matters: Can be more expensive and may come with limitations such as latency, policies or stability.
When relevant: Cross-border assets, international rollout, temporary deployments.
Definition: Data exits to the internet locally in the country or region, instead of through a central core elsewhere.
Why this matters: Can improve latency and make compliance easier.
When relevant: Real-time applications, region-specific compliance requirements.
Definition: Delay between sending and receiving data.
Why this matters: Shapes the user experience and the reliability of near-real-time processes.
When relevant: Remote control, alarms, interactive use.
Definition: The amount of data that can pass over a connection per second.
Why this matters: Prevents bottlenecks for gateways, video or bulk updates.
When relevant: Routers and gateways, cameras, large firmware updates.
Definition: Loss of data packets during transport.
Why this matters: Can cause time-outs, retries and higher data usage.
When relevant: Poor coverage, congested cells, moving assets.
Definition: Prioritisation and quality settings for network traffic.
Why this matters: Not every IoT message is equally critical; QoS improves predictability.
When relevant: Critical monitoring, alarms, SLA-driven environments.
Definition: Alternative route or network when the primary connection fails.
Why this matters: Makes uptime more predictable in real-life conditions.
When relevant: Mission-critical applications and remote sites.
Definition: Multiple operators available for one device or SIM profile.
Why this matters: Increases the chance of connection and reduces dependency on a single network.
When relevant: International rollout, moving assets, indoor challenges.
SIM, eUICC & Provisioning
Definition: Physical card with the operator identity that grants access to mobile networks.
Why this matters: Foundation of connectivity; influences coverage, policies and cost.
When relevant: All cellular IoT devices with a SIM slot.
Definition: Consumer term for ‘SIM without swapping’, often confused with eUICC.
Why this matters: In IoT, it is better to be precise: usually what you mean is eUICC plus provisioning.
When relevant: Communication with non-technical stakeholders.
Definition: SIM technology that allows you to download or switch operator profiles remotely.
Why this matters: Enables scale and flexibility without a truck roll.
When relevant: Long lifecycles, multi-country deployments, supply-chain simplification.
Definition: Operator identity and settings stored on the eUICC.
Why this matters: Profile choice affects coverage, roaming, compliance and cost.
When relevant: International rollout or carrier-switch scenarios.
Definition: Process for managing profiles remotely on an eUICC.
Why this matters: Without RSP, eUICC is only hardware without real flexibility.
When relevant: Fleet management, large-scale deployments.
Definition: Activating and configuring the device, SIM and network access.
Why this matters: A strong provisioning process prevents later ‘unexplained’ issues.
When relevant: Pilot to production, mass rollout.
Definition: Unique serial number of the SIM.
Why this matters: Useful for administration, inventory and troubleshooting.
When relevant: Integrations, portal management, RMA processes.
Definition: Unique network identity of the SIM at operator level.
Why this matters: Determines which operator or core you use; relevant in roaming and profiling.
When relevant: Deeper network diagnostics, multi-operator setups.
Definition: The ‘phone number’ that may be linked to a SIM.
Why this matters: Not every IoT scenario uses it, but it can be necessary for SMS or legacy flows.
When relevant: SMS-based setup, legacy telemetry.
Definition: The phases of stock, activation, use, suspension and termination.
Why this matters: Lifecycle management prevents cost leakage and security risks.
When relevant: Growing fleets and contract management.
Definition: Unique identifier of the modem or telecom part of the device.
Why this matters: Helps with device mapping, fraud control and support.
When relevant: Hardware management, SIM-to-device pairing.
Definition: Unique ID of an eUICC chip.
Why this matters: Needed for eUICC provisioning processes and inventory management.
When relevant: eUICC fleets, manufacturing and supply chain.
Definition: Starter profile that brings a device online so it can then download the ‘real’ profile.
Why this matters: Enables global manufacturing without a local SIM per country.
When relevant: Global production, first-time connection in the field.
Network Configuration & Routing
Definition: Access point that determines how a device sends data into the network.
Why this matters: Wrong APN means no connection or insecure traffic.
When relevant: Always with cellular data; during setup and troubleshooting.
Definition: APN that routes traffic into a protected, private environment.
Why this matters: Increases security and control over data flows.
When relevant: Critical systems, compliance, separated networks.
Definition: Fixed IP address for a device or connection.
Why this matters: Simplifies inbound connections, whitelisting and management.
When relevant: Remote access, fixed endpoints, integrations with restrictions.
Definition: IP address that can be directly reachable from the internet.
Why this matters: Can be useful, but increases exposure; security must be strong.
When relevant: Only when inbound access is truly required and properly protected.
Definition: Multiple devices share one external IP address through translation.
Why this matters: Much IoT traffic is outbound only; in that case NAT is fine and safer.
When relevant: Sensors and trackers that only send data out.
Definition: Encrypted tunnel between the device or network and your environment.
Why this matters: Adds privacy, integration simplicity and an extra security layer.
When relevant: Remote sites, industrial networks, sensitive data.
Definition: VPN technology at IP level, often used in enterprise networks.
Why this matters: Robust and widely supported in firewalls and routers.
When relevant: Corporate integrations, site-to-site connections.
Definition: System that translates domain names into IP addresses.
Why this matters: Incorrect DNS settings can create ‘unexplained’ offline behaviour.
When relevant: Every cloud connection, failover architectures.
Definition: Rules that determine which traffic is allowed.
Why this matters: Minimises the attack surface and helps prevent data leaks.
When relevant: Always with private APNs, VPNs and platform integrations.
Management, Portals & Operations
Definition: Portal for SIM management, data usage, policies and troubleshooting.
Why this matters: Without a CMP, scaling becomes expensive and error-prone.
When relevant: From around 50 to 100 devices onward, or earlier for critical use cases.
Definition: Overall environment for management of SIMs, devices, alerts and users.
Why this matters: Brings control and predictability across your whole fleet.
When relevant: With growth, multi-country rollout, multiple teams or roles.
Definition: Management of device status, configuration, updates and lifecycle.
Why this matters: Device issues are usually operational, not one-off incidents.
When relevant: Always at scale — especially with OTA updates.
Definition: Management of a large group of devices as one whole through policies and segments.
Why this matters: You want to steer groups, not individual exceptions.
When relevant: Tracking fleets, sensor networks, international rollout.
Definition: Continuous measurement of status, performance and availability.
Why this matters: You can only improve what you can see.
When relevant: As soon as uptime matters, which is usually immediately.
Definition: Automatic notifications when something deviates, such as offline status, data spikes or roaming changes.
Why this matters: Shortens downtime and prevents costly surprises.
When relevant: Production rollout, SLAs, remote sites.
Definition: Rules for usage, such as data caps, roaming, access or time windows.
Why this matters: Policies help keep cost and risk under control.
When relevant: Large fleets, cost control, security.
Definition: Maximum amount of data per SIM or device per period.
Why this matters: Protects against runaway usage and unexpected costs.
When relevant: Gateways, debug phases, devices with variable payloads.
Definition: Temporarily blocking a SIM without permanently terminating it.
Why this matters: Useful for theft, test devices or seasonal use.
When relevant: During incidents or temporary stops.
Definition: Service Level Agreement: commitments on availability and support.
Why this matters: Makes expectations concrete and measurable.
When relevant: Mission-critical deployments and enterprise customers.
Definition: Process for registering, resolving and preventing disruptions.
Why this matters: Without a process, you repeat the same issues.
When relevant: With growth or when multiple teams provide support.
Security (device, network & platform)
Definition: Minimum set of security measures for IoT chains.
Why this matters: Prevents security from becoming ad hoc and leaving gaps.
When relevant: Always — especially during scale-up and compliance.
Definition: Unique, cryptographically verifiable identity of a device.
Why this matters: You need to know exactly which device is sending data.
When relevant: Every secure IoT architecture.
Definition: Public Key Infrastructure for certificates and keys.
Why this matters: Scalable basis for device identity and encryption.
When relevant: mTLS, certificate management, enterprise security.
Definition: Digital proof that a key belongs to an identity.
Why this matters: Supports secure authentication without shared passwords.
When relevant: mTLS, secure API access.
Definition: TLS where both server and client authenticate with certificates.
Why this matters: Strong protection against spoofing and man-in-the-middle attacks.
When relevant: Critical data, industrial environments, Zero Trust.
Definition: Encryption of data while it is being transmitted.
Why this matters: Prevents eavesdropping and manipulation.
When relevant: Always; at minimum TLS.
Definition: Encryption of data stored on the device or server.
Why this matters: Limits the impact of theft or server incidents.
When relevant: Sensitive data, devices in the field.
Definition: Device starts only firmware that has been cryptographically approved.
Why this matters: Blocks malware at firmware level.
When relevant: Long-life devices, high-risk environments.
Definition: Firmware is signed so you can verify its origin and integrity.
Why this matters: Prevents malicious actors from injecting updates.
When relevant: OTA updates, supply-chain security.
Definition: Over-the-air remote firmware or software update.
Why this matters: Essential for patching vulnerabilities and rolling out features.
When relevant: Anything that remains live for more than a few months.
Definition: Trust nothing by default; continuously verify identity and access.
Why this matters: Fits IoT well: many devices, many risks, little physical control.
When relevant: Enterprise integrations, critical systems.
Definition: Grant only the minimum rights required.
Why this matters: Limits damage if something is compromised.
When relevant: API keys, portal users, device permissions.
Definition: Periodic replacement of keys or credentials.
Why this matters: Reduces the impact of leaked keys.
When relevant: Long-running deployments, compliance.
Radio, Signal & Performance
Definition: Indication of received signal strength.
Why this matters: Gives a rough signal picture; useful but not the full story.
When relevant: First diagnosis of coverage issues.
Definition: Reference signal strength for LTE.
Why this matters: Better measurement than RSSI for LTE quality.
When relevant: LTE/4G performance and planning.
Definition: Signal quality indicator that reflects quality versus interference.
Why this matters: Low RSRQ often means congestion or interference.
When relevant: Unstable connections despite a ‘strong signal’.
Definition: Ratio between signal and noise or interference.
Why this matters: Strong predictor of actual data speed and reliability.
When relevant: Gateways, data-intensive use cases.
Definition: Degree to which an antenna strengthens signal in a given direction.
Why this matters: Can dramatically improve indoor or outdoor performance.
When relevant: Installations in metal enclosures, containers, remote sites.
Definition: Combining frequency bands to increase throughput in LTE or 5G.
Why this matters: Useful for routers and gateways with high data demands.
When relevant: 4G/5G routers, busy environments.
Definition: Energy budget of a device over its desired lifetime.
Why this matters: Wrong assumptions lead to dead batteries and service visits.
When relevant: Battery-powered devices and cold environments.
Definition: Power Saving Mode where the modem sleeps deeply and uses extremely little power.
Why this matters: Extends battery life, but affects reachability.
When relevant: NB-IoT or LTE-M sensors with infrequent messages.
Definition: Extended Discontinuous Reception where the device listens to the network less often.
Why this matters: Saves energy with limited impact on reachability.
When relevant: Battery-powered devices that still need occasional reachability.
Definition: Protection rating against dust and water.
Why this matters: Physical reliability is just as important as connectivity.
When relevant: Outdoor, industrial and humid environments.
Hardware & Edge
Definition: Modem component that enables 4G, 5G, LTE-M or NB-IoT.
Why this matters: Module choice determines supported bands, certifications, power consumption and stability.
When relevant: Device design, hardware selection.
Definition: Intermediate device that connects local devices or sensors to the internet or cellular network.
Why this matters: Reduces cost and complexity when many local endpoints are involved.
When relevant: Industrial sites, buildings, locations with many sensors.
Definition: Network device that uses cellular to connect a LAN, Wi-Fi or Ethernet environment.
Why this matters: Backbone for remote sites and reliable connectivity.
When relevant: Retail, construction sites, temporary locations, failover.
Definition: Processing data close to the source instead of sending everything to the cloud.
Why this matters: Less latency, less data usage and more continuity during network issues.
When relevant: Real-time decisions, bandwidth costs, privacy.
Definition: Device that measures a physical value, such as temperature or vibration.
Why this matters: A sensor only creates value with the right sampling, power design and data model.
When relevant: Monitoring, condition-based maintenance.
Definition: Device that measures and reports location and movement.
Why this matters: Location is operational; you want reliability, not just pretty maps.
When relevant: Logistics, assets, reverse flows.
Data, Protocols & Integrations
Definition: Lightweight publish/subscribe protocol for IoT messaging.
Why this matters: Efficient for many devices and unstable networks.
When relevant: Sensor fleets, event-driven data, low overhead.
Definition: Web protocol, with HTTPS being encrypted, for request/response communication.
Why this matters: Easy to integrate, but heavier than MQTT.
When relevant: API calls, configuration, simple telemetry.
Definition: Lightweight protocol similar to HTTP, aimed at constrained devices.
Why this matters: Efficient, but less mainstream in enterprise integrations.
When relevant: Highly constrained devices and specific IoT stacks.
Definition: Mechanism where one system automatically sends events to your endpoint.
Why this matters: Enables real-time integration without polling.
When relevant: Alerts, status updates, automations.
Definition: Standardised way to connect systems through HTTP endpoints.
Why this matters: Makes integration with portals, data platforms and applications straightforward.
When relevant: Dashboards, provisioning, reporting.
Definition: Architecture in which events or changes are central.
Why this matters: Scalable and flexible for large numbers of devices.
When relevant: Growing fleets, multiple consumers of the same data.
Definition: Data with timestamps, meaning measurements over time.
Why this matters: Basis for trends, alerts and predictive maintenance.
When relevant: Sensors, energy, industry, quality monitoring.
Definition: The content of a message — the actual data.
Why this matters: Payload influences data cost, power consumption and latency.
When relevant: Optimisation and cost control.
Definition: How often you measure.
Why this matters: High sampling can drain battery and data without adding value.
When relevant: Condition monitoring, vibration, temperature.
Standards, Regulation & Governance
Definition: Industry organisation that publishes standards, including around eUICC and provisioning.
Why this matters: Supports interoperability between ecosystems.
When relevant: eUICC and RSP projects, multi-vendor environments.
Definition: European marking showing that a product complies with EU requirements.
Why this matters: Necessary for selling or deploying hardware in the EU.
When relevant: Hardware delivered in Europe.
Definition: EU directive for radio equipment, such as cellular modules or routers.
Why this matters: Protects safety and spectrum use; requires conformity.
When relevant: All radio hardware in the EU.
Definition: Standard for information security management systems.
Why this matters: Provides demonstrable structure around security processes.
When relevant: Enterprise sales, compliance, security maturity.
Definition: EU directive for cybersecurity in essential and important sectors, implemented per country.
Why this matters: Raises requirements around risk, incidents and supply chain.
When relevant: Customers in regulated sectors or supply chains.
Definition: Where data is physically stored and processed.
Why this matters: Can be legally and contractually decisive.
When relevant: Government, healthcare, regulated industries.
Definition: Log of who did what and when, including management actions and changes.
Why this matters: Crucial for compliance and incident investigation.
When relevant: Portals, provisioning, security.
Operational & Troubleshooting Terms
Definition: Limited test rollout to validate assumptions in practice.
Why this matters: IoT fails on details; a good pilot prevents scaling risk.
When relevant: Always before production — but design it like a mini-production environment.
Definition: Phased deployment into production at larger scale.
Why this matters: Success depends on process: provisioning, monitoring and support.
When relevant: Once the pilot works and you want to scale.
Definition: Metric that defines success, such as uptime, latency or battery life.
Why this matters: Without KPIs, you are steering on intuition.
When relevant: Pilot evaluations, SLAs, operations.
Definition: Percentage of time that a service or device is available.
Why this matters: This is what end users experience as reliability.
When relevant: Anything that affects business processes.
Definition: Return Merchandise Authorization process for defective hardware.
Why this matters: Hardware can fail; you want the process to be tight and measurable.
When relevant: Physical devices in the field.
Definition: Physical service visit on site.
Why this matters: Expensive and slow; you want to minimise it through remote management.
When relevant: Hardware swaps, installations, no-connect cases.
Definition: Method for finding the true cause of an incident.
Why this matters: Otherwise you only solve symptoms and the issue keeps returning.
When relevant: Recurring disruptions, scaling problems.