Internet of things

Internet of Things Access Technologies

Internet of Things Access Technologies

The Internet of Things (IoT) has evolved from a collection of connected devices into a distributed technology ecosystem spanning homes, enterprises, industrial environments, vehicles, healthcare, utilities, and smart infrastructure.

At the foundation of every IoT deployment is connectivity. Sensors and devices need a way to communicate with gateways, edge platforms, applications, and cloud services. The appropriate access technology depends on factors such as range, bandwidth, power consumption, mobility, reliability, device density, deployment environment, and security requirements.

There is therefore no single IoT connectivity technology that fits every deployment.

Understanding IoT Access Technologies

IoT access technologies provide the communications layer between devices and the systems that consume their data.

A simplified IoT architecture can involve several stages:

Device → Access Network → Gateway or Edge → IoT Platform → Application

In some architectures, a device may communicate directly with an IP network or cloud service. In others, a gateway aggregates data from hundreds or thousands of sensors before forwarding selected information upstream.

IoT connectivity can broadly be divided into wired, short-range wireless, low-power wide-area, cellular, and specialised industrial technologies.

Wired Connectivity

Wired connectivity remains important where predictable performance, physical security, power delivery, or high bandwidth are required.

Ethernet is widely used in industrial, enterprise, building automation, and infrastructure environments. It provides reliable IP connectivity and can support high data rates with relatively predictable performance.

Power over Ethernet (PoE) combines network connectivity and electrical power over Ethernet cabling. This can simplify deployments for devices such as cameras, access points, sensors, controllers, and other powered endpoints.

Wired technologies are particularly useful where devices are stationary and cabling is practical, but installation costs and physical deployment constraints can make wireless alternatives more attractive.

Short-Range Wireless Connectivity

Short-range wireless technologies are widely used for devices operating within homes, buildings, industrial sites, and personal environments.

Wi-Fi provides relatively high bandwidth and integrates easily with existing IP networks. It is useful for cameras, appliances, industrial devices, gateways, and applications that require greater throughput.

Bluetooth Low Energy (BLE) is designed for low-power short-range communication and is commonly used for sensors, wearables, beacons, medical devices, and device provisioning.

Zigbee and Thread are designed around low-power mesh networking and can support large numbers of constrained devices.

Thread is particularly important in modern smart-home environments because it is based on IPv6 and is designed for low-power mesh connectivity. Matter operates at the application layer and can use technologies such as Wi-Fi, Ethernet, and Thread as its underlying network connectivity.

The distinction is important: connectivity technology and application protocol are not necessarily the same thing.

Low-Power Wide-Area Networking

Many IoT devices do not require high bandwidth. A remote sensor may only need to transmit a small amount of information every few minutes or hours.

This is where Low-Power Wide-Area Networking (LPWAN) technologies become valuable.

LoRaWAN is designed for long-range, low-power communications and is particularly useful for distributed sensors such as environmental monitoring, agriculture, metering, and smart-city deployments.

Cellular IoT technologies such as NB-IoT and LTE-M provide another approach, using mobile network infrastructure to connect devices over wide geographic areas.

These technologies prioritise characteristics such as long battery life, wide coverage, device density, and relatively low data requirements rather than raw bandwidth.

Cellular IoT

Cellular connectivity is particularly useful when devices are geographically distributed, mobile, or located where local network infrastructure is unavailable.

Traditional generations of mobile technology have supported IoT connectivity, but modern deployments increasingly focus on technologies such as LTE-M, NB-IoT, and 5G.

5G also introduces capabilities relevant to more demanding IoT scenarios, including high bandwidth, lower latency, greater device density, and support for specialised industrial and private-network deployments.

However, 5G should not automatically be considered the answer for every IoT deployment. A low-power environmental sensor transmitting a few bytes of telemetry does not necessarily require the capabilities or cost structure of a high-performance 5G connection.

Edge Connectivity

Modern IoT architectures increasingly move processing closer to the devices.

An edge gateway can aggregate sensor traffic, translate between protocols, filter data, perform local analytics, enforce security policies, and continue operating when connectivity to the cloud is unavailable.

This is particularly valuable in industrial environments where latency, bandwidth, resilience, and local decision-making are important.

For example, an industrial sensor might send raw telemetry to a local edge platform. The edge system can detect an abnormal condition immediately while sending only the relevant event or aggregated telemetry to a central cloud platform.

This approach reduces unnecessary data transmission and can improve response times.

Security Must Begin at the Access Layer

Connectivity also introduces an attack surface.

IoT devices can be physically accessible, resource constrained, widely distributed, and difficult to update. Security therefore needs to be considered throughout the device and connectivity lifecycle.

Important controls include:

Device identity: each device should have a verifiable identity rather than relying on shared credentials.

Authentication: devices and services should authenticate before exchanging sensitive information.

Encryption: communications should be protected against interception and manipulation.

Secure onboarding: devices should be provisioned securely before they become trusted members of the environment.

Network segmentation: IoT devices should be isolated from systems that do not require direct access to them.

Secure updates: firmware and software need mechanisms for authenticated and controlled updates.

Lifecycle management: devices should be monitored, maintained, rotated, and securely decommissioned when they reach the end of their operational life.

This is increasingly aligned with a zero-trust approach, where network location alone does not establish trust.

Choosing the Right IoT Connectivity

Selecting an IoT access technology is therefore an engineering decision rather than simply a choice between wired and wireless.

Key questions include:

How far must the device communicate?

How much data does it need to transmit?

How frequently does it communicate?

Does the device need to operate for years on battery power?

Is the device stationary or mobile?

What level of latency and reliability is required?

Is local edge processing required?

What security and lifecycle controls are necessary?

What existing infrastructure can be reused?

The answers determine whether Ethernet, Wi-Fi, Thread, Bluetooth, LoRaWAN, cellular IoT, 5G, or another connectivity technology is appropriate.

IoT connectivity is therefore best understood as a layered architecture rather than a single access technology. The right combination of device connectivity, networking, edge computing, cloud services, and security allows IoT deployments to scale from a handful of sensors to millions of distributed devices.

As IoT continues to move toward edge computing, autonomous systems, industrial automation, and AI-driven operations, understanding the characteristics and trade-offs of these access technologies becomes increasingly important.

IoT Connectivity Explorer

Which Access Technology Fits the IoT Use Case?

IoT devices do not all have the same connectivity requirements. Choose a deployment scenario and explore which access technology best matches its range, power, bandwidth and mobility needs.

Learning Objective Understand why Wi-Fi, cellular, Bluetooth, Zigbee and LoRaWAN are suited to different IoT connectivity requirements.

1. Choose an IoT Scenario

Select the environment you are designing connectivity for.

Select a scenario
Recommended Access Technology
—
Choose an IoT scenario to see the recommended connectivity approach.
Range
Power
Bandwidth
Mobility
Technology insight
Select a scenario or technology to explore its role in IoT connectivity.
Engineering Takeaway There is no single best IoT access technology. Connectivity should be selected according to the application's range, power, bandwidth, mobility and deployment requirements.

Highlights: Internet of Things Access Technologies

A practitioner in the tech industry should be familiar with the term Internet of Things (IoT). IoT continues to grow due to industries’ increasing reliance on the internet. Even though we sometimes don’t realize it, it is everywhere.

The Internet of Things plays an important role in the development of smart cities through its various implementations, such as real-time sensor data retrieval and automated task execution. The Internet of Things’ profound impact on our urban landscape, which is increasingly evident, means that these systems, equipped with numerous sensors, take action when specific thresholds are reached.

The Internet of Things, coined by computer scientist Kevin Ashton in 1999, is a network of connected physical objects that send and receive data. Smart fridges and mobile phones are examples of everyday objects, as are smart agriculture and smart cities, which span entire towns and industries.

IoT has revolutionized how we live and interact with our environment in just a few years. Households can benefit from IoT in the following ways:

  • Convenience: Devices can be programmed and controlled remotely. Think about being able to adjust your home’s lighting or heating even when you’re miles away using your smartphone.
  • Efficiency: Smart thermostats and lighting systems can optimize operations based on your usage patterns, saving energy and lowering utility bills.
  • Security: In terms of security, IoT-enabled security systems and cameras can alert homeowners of potential breaches, and smart locks can recognize and grant access based on recognized users.
  • Monitoring health metrics: Smart wearables can track health metrics and provide real-time feedback, potentially alerting users or medical professionals to concerning changes.
  • Improved user experience: Devices can learn and adapt to users’ preferences, ensuring tailored and improved interactions over time.

IoT Access Technologies:

Wi-Fi:

One of the most widely used IoT access technologies is Wi-Fi. With high data transfer speeds and widespread availability, Wi-Fi enables devices to connect effortlessly to the internet. Wi-Fi allows for convenient and reliable connectivity, whether controlling your thermostat remotely or monitoring security cameras. However, its range limitations and power consumption can be challenging in specific IoT applications.

Cellular Networks:

Cellular networks, such as 3G, 4G, and now the emerging 5G technology, play a vital role in IoT connectivity. These networks offer broad coverage areas, making them ideal for IoT deployments in remote or rural areas. With the advent of 5G, IoT devices can now benefit from ultra-low latency and high bandwidth, paving the way for real-time applications like autonomous vehicles and remote robotic surgery.

Bluetooth:

Bluetooth technology has long been synonymous with wireless audio streaming, but it also plays a significant role in IoT connectivity. Bluetooth Low Energy (BLE) is designed for IoT devices, offering low power consumption and short-range communication. This makes it perfect for applications like wearable devices, healthcare monitoring, and intelligent home automation, where battery life and proximity are crucial.

Zigbee:

Zigbee is a low-power wireless communication standard designed for IoT devices. It operates on the IEEE 802.15.4 standard and offers low data rates and long battery life. Zigbee is commonly used for home automation systems, such as smart lighting, temperature control, and security systems. Its mesh networking capabilities allow devices to form a network and communicate with each other, extending the overall range and reliability.

LoRaWAN:

LoRaWAN (Long Range Wide Area Network) is a low-power, wide-area network technology for long-range communication. It enables IoT devices to transmit data over long distances, making it suitable for applications like smart agriculture, asset tracking, and environmental monitoring. LoRaWAN operates on unlicensed frequency bands, enabling cost-effective and scalable IoT deployments.

Example Product: Cisco IoT Operations Dashboard

### Streamlined Device Management

One of the standout features of the Cisco IoT Operations Dashboard is its capability to streamline device management. With a user-friendly interface, you can quickly onboard, monitor, and manage a wide array of IoT devices. The dashboard provides real-time visibility into device status, performance metrics, and potential issues, allowing for proactive maintenance and swift troubleshooting.

### Enhanced Security Measures

Security is a top priority when it comes to IoT devices, and the Cisco IoT Operations Dashboard excels in this area. It offers robust security protocols to protect your devices from vulnerabilities and cyber threats. Features such as encrypted communications, device authentication, and regular security updates ensure that your IoT ecosystem remains secure and resilient against attacks.

### Scalability for Growing IoT Networks

As your IoT network expands, managing an increasing number of devices can become challenging. The Cisco IoT Operations Dashboard is designed to scale effortlessly with your network. Whether you have a small deployment or a vast array of interconnected devices, the dashboard’s scalable architecture ensures that you can manage your IoT operations effectively, regardless of size.

### Integration and Interoperability

The Cisco IoT Operations Dashboard is built with integration and interoperability in mind. It seamlessly integrates with other Cisco products and third-party solutions, providing a cohesive and unified management experience. This interoperability allows for the aggregation of data from various sources, enabling comprehensive analytics and informed decision-making.

 

1. Define the Requirements
Move the sliders toward the requirement you want to prioritise.
Transmission Range Medium
Local Long range
Low Power Requirement Medium
Less important Critical
Bandwidth Requirement Medium
Low High
Mobility Requirement Medium
Stationary Highly mobile
Engineering Principle

IoT connectivity is a trade-off. The best technology depends on the workload and constraints rather than a single performance metric.

1 Define the workload
What data must be moved, and how often?
2 Identify the constraints
Consider range, power, bandwidth and mobility.
3 Select the technology
Choose the option that best fits the complete requirement.
2. Compare the Technologies
The ranking updates as the requirements change.
Current Engineering Recommendation

Wi-Fi

Balanced requirements currently favour a technology with strong local connectivity and useful bandwidth.

Engineering Insight: There is no universally "best" IoT access technology. The correct choice depends on the combination of range, energy constraints, bandwidth and mobility.

Internet of Things Access Technologies

The Internet of Things consists of a network of several devices, including a range of digital and mechanical objects, with separate access to transfer information over a network. The word “thing” can also represent an individual with a heart- monitor implant or even a pet with an IoT-based collar.

The term “thing” reflects the association of “internet” to devices previously disconnected with internet access. For example, the alarm clock was never meant to be internet-enabled, but now you can connect it to the Internet. With IoT, the options are endless.

Examples: IoT Access Technologies

Then, we have IoT access technologies. The three major network access technologies for IoT Connectivity are Standard Wireless Access – WiFi, 2G, 3G, and standard LTE. We also have Private Long Range – LoRA-based platforms, Zigbee and SigFox. Mobile IoT Technologies – LTE-M, NB-IoT, and EC-GSM-IoT

The origins of the Internet, which started in the 1960s, look entirely different from our current map. It is now no longer a luxury but more of a necessity. It started with areas such as basic messaging, which grew to hold the elasticity and dynamic nature of the cloud, to a significant technological shift into the world of the Internet of Things (IoT): Internet of Things theory.

It’s not about buying and selling computers and connecting them anymore; it’s all about data, analytics, and new solutions, such as event stream processing.

Internet of Things Access Technologies: A New World

A World with the Right Connections

IoT represents a new world where previously unconnected devices have new communication paths and reachability points. This marks IoT as the next evolutionary phase of the Internet, building better customer solutions.

The revolutionary phase is not just a technical phase; ethical challenges now face organizations, society, and governments. In the past, computers relied on input from humans. We entered keystrokes, and the machine would perform an action based on the input.

The computer had no sensors that could automatically detect the world around it and perform a specific action based on that. IoT ties these functions together. The function could be behavioral, making the object carry out a particular task or provide other information. IoT brings a human element to technology, connecting physically to logic.

 It’s all about data and analytics.

The Internet of Things is not just about connectivity. The power of IoT comes from how all these objects are connected and the analytics they provide. New analytics lead to new use cases that will lead to revolutionary ideas enhancing our lives. Sensors are not just put on machines and objects but also on living things. Have you heard of the connected cow? Maybe we should start calling this “cow computing” instead of “cloud computing.” For example, an agricultural firm called Chitale Group uses IoT technologies to keep tabs on herds to monitor their thirst.

These solutions will formulate a new type of culture, intertwining various connected objects and dramatically shifting how we interact with our surroundings. This new type of connectivity will undoubtedly formulate how we live and form the base of a new culture of connectivity and communication.

 IoT Access Technologies: Data management – Edge, fog, and cloud computing

In the traditional world of I.T. networks, data management is straightforward. It is based on I.P. with a client/server model, and the data is in a central location. IoT brings new data management concepts such as Edge, Cloud, and Fog computing. However, the sheer scale of IoT data management presents many challenges. Low bandwidth of the last mile leads to high latency, and new IoT architectural concepts such as Fog computing, where you analyze data close to where it’s connected, are needed. 

Like the cloud in Skype, Fog is on the ground and best suited for constrained networks that need contextual awareness and quick reaction. Edge computing is another term where the processing is carried out at the furthest point – the IoT device itself. Edge computing is often called Mist computing.

IoT Access Technologies
Diagram: IoT Access Technologies. Source Cisco.

Cloud computing is not everything.

IoT brings highlights the concept that “cloud computing is not everything.” IoT will require onsite data processing; some data must be analyzed in real-time. This form of edge computing is essential when you need near-time results and when there isn’t time to send visual, speed, and location information to the cloud for instructions on what to do next. For example, if a dog runs out in front of your car, the application does not have the time for several round trips to the cloud. 

Services like iCloud have had a rough few years. Businesses are worried about how secure their data will be when using one of the many cloud-based services available, especially after the iCloud data breach in 2014. However, with the rise of cloud security solutions, many businesses are starting to see the benefits of cloud technology, as they no longer have to worry about their data security.

The Internet is prone to latency, and we cannot fix it unless we shorten the links or change the speed of light. Connected cars require the capability to “think” and make decisions on the ground without additional hops to the cloud.

Fog Computing – Distributed Infrastructure 

Fog computing is a distributed computing infrastructure between a network’s edge and the cloud. It is a distributed computing architecture designed to address the challenges of latency and bandwidth constraints introduced by traditional cloud computing. Fog computing decentralizes the computing process rather than relying on a single, centralized data center to store and process data. It enables data to be processed closer to the network’s edge.

Fog computing performs better than cloud computing in meeting the demands of emerging paradigms. However, batch processing is still preferred for high-end jobs in the business world, so it can only partially replace cloud computing. In conclusion, fog computing and cloud computing complement one another while having their advantages and disadvantages. Edge computing is crucial in the Internet of Things (IoT).

Security, confidentiality, and system reliability are research topics in the fog computing platform. Cloud computing will meet the needs of business communities with its lower cost based on a utility pricing model. In contrast, fog computing is expected to serve the emerging network paradigms that require faster processing with less delay and delay jitter. Fog computing will grow by supporting the emerging network paradigms that require faster processing with less delay and delay jitter.

Internet of Things Access Technologies: Architectural Standpoint

A ) From an architectural point of view, one must determine the technologies used to allow these “things” to communicate with each other. And the technologies chosen are determined by how the object is classified. I.T. network architecture has matured over the last decade, but IoT architectures bring new paradigms and a fresh approach. For example, traditional security designs consist of physical devices with well-designed modules.

B ) Although new technologies such as VM NIC Firewalls and other distributed firewalls other than IoT have dissolved the perimeter, IoT brings dispersed sensors outside the protected network, completely dissolving the perimeter to a new level. 

C) When evaluating the type of network needed to connect IoT smart objects, one needs to address transmission range, frequency bands, power consumption, topology, and constrained devices and networks. The technologies used for these topologies include IEEE 802.15.4, IEEE 802.15.4g and IEEE 802.15.4e, IEEE 1901.2a, IEEE 802.11ah, LoRaWAN, and NB-IoT. The majority of them are wireless. Similar to I.T. networks, IoT networks follow Layer 1 (PHY), Layer 2 (MAC), Layer 3 (I.P.), etc. layers. And some of these layers require optimizations to support IoT intelligent objects.

IP/TCP/UDP in an IoT world

– The Internet Protocol (I.P.) is an integral part of IoT due to its versatility in dealing with the large array of changes in Layer 1 and Layer 2 to suit the last-mile IoT access technologies. I.P. is the Internet protocol that connects billions of networks with a well-understood knowledge base. Everyone understands I.P. and knows how to troubleshoot it.

– It has proven robust and scalable, providing a solid framework for bi-directional or unidirectional communication between IoT devices. Sometimes, the full I.P. stack may not be necessary as protocol overhead may exceed device data. 

– More importantly, IPv6. Using I.P. for the last mile of constrained networks requires introducing a new mechanism and routing protocols, such as RLP and adaptation layers, to handle the constrained environments. In addition, routing protocol optimizations must occur for constrained devices and networks. This is where we see the introduction of the IPv6 RPL protocol. IPv6 RPL protocol is a distance-vector routing protocol specifically designed for IoT intelligent objects.

– Optimizations are needed at various levels, and control plane traffic must be kept to a minimum, leading to new algorithms such as On-Demand Distance Vector. Standard routing algorithms learn the paths and store the information for future use. This works compared to AODV, which does not send a message until a route is needed.

Both TCP and UDP have their place in IoT:

TCP and UDP will play a significant role in the IoT transport layer. TCP for guaranteed delivery or UDP to leave the handling to a higher layer. The additional activities TCP brings to make it a reliable transport protocol come at the overhead cost per packet and session.

On the other hand, UDP is connectionless and often used for performance, which is more critical than packet retransmission. Therefore, a low-power and Lossy network (LLN) may be better suited than UDP and a more robust cellular network for TCP.

Session overhead may not be a problem on everyday I.T. infrastructures. Still, it can cause stress on IoT-constrained networks and devices, especially when a device needs only to send a few bytes per bytes of data per transaction. IoT Class 0 devices that only send a few bytes do not need to implement a full network protocol stack. For example, small payloads can be transported on top of the MAC layer without TCP or UDP.

**Ethical Challenges**

What are the ethical ramifications of IoT? In the Cold War, everyone was freaked out about nuclear war; now, it’s all about data science. We are creating billions of connected “things,” and we don’t know what’s to come. The responsibilities around the ethical framework for IoT and the data it generates fall broadly on individual governments and society.

These are not technical choices; they are socially driven. This might scare people and hold them back with IoT, but if you look at technology, it’s been a fantastic force for good. One should not resist IoT and the use cases it will offer our lives. However, I don’t think it will work out well for you if you do.

New technologies will always have risks and challenges. But if you reflect on and look at original technologies, such as the wheel, they created new jobs rather than destroyed old ones. IoT is the same. It’s about being on the right side of history and accepting it.

Example Product: Cisco Edge Device Manager

### What is Cisco Edge Device Manager?

Cisco Edge Device Manager is a cutting-edge platform designed to simplify the management of edge devices. It provides a unified interface for monitoring, configuring, and troubleshooting devices located at the edge of the network. By leveraging Cisco EDM, businesses can ensure optimal performance, reduce downtime, and enhance security across their edge infrastructure.

### Key Features and Benefits

#### Seamless Integration

One of the standout features of Cisco Edge Device Manager is its seamless integration with the Cisco IoT Operations Dashboard. This synergy allows for a centralized view of all IoT devices, enabling efficient management and streamlined operations.

#### Enhanced Security

Cisco EDM prioritizes security, offering advanced features such as automated firmware updates, real-time threat detection, and secure communication channels. These measures ensure that your edge devices are protected against potential cyber threats.

#### Scalability

Whether you have a handful of devices or thousands, Cisco Edge Device Manager scales effortlessly to meet your needs. Its flexible architecture supports the growth of your IoT infrastructure without compromising performance or reliability.

### Practical Applications

Cisco Edge Device Manager is not just a tool; it’s a game-changer for various industries. Here are a few practical applications:

– **Manufacturing**: Monitor and manage factory equipment in real-time to enhance productivity and reduce maintenance costs.

– **Retail**: Ensure seamless operation of point-of-sale systems and inventory tracking devices, improving customer experience.

– **Healthcare**: Maintain the performance and security of medical devices, ensuring patient safety and data integrity.

### Getting Started with Cisco Edge Device Manager

Setting up Cisco Edge Device Manager is straightforward. Begin by integrating it with your existing Cisco IoT Operations Dashboard. Next, configure your edge devices through the intuitive interface, and start monitoring their performance and security. Cisco provides detailed documentation and support to guide you through each step.

Cisco and IoT

One technology that has significantly advanced IoT is Cisco’s LoRaWAN. LoRaWAN, short for Long Range Wide Area Network, is a low-power, wide-area network protocol for long-range communication between IoT devices.

It operates in the sub-gigahertz frequency bands, providing an extended communication range while consuming minimal power. This makes it ideal for applications that require long-distance connectivity, such as smart cities, agriculture, asset tracking, and industrial automation.

Cisco’s Contribution: Cisco, a global leader in networking solutions, has embraced LoRaWAN technology and has been at the forefront of driving its adoption. The company has developed a comprehensive suite of LoRaWAN solutions, including gateways, sensors, and network infrastructure, enabling businesses to leverage the power of IoT.

Example Use Case: Cisco’s LoRaWAN-compliant solution.

With Cisco’s LoRaWAN-compliant solution, IoT sensors and endpoints can be connected cheaply across cities and rural areas. Low power consumption also extends battery life up to several years. The solution operates in the 800–900 MHz ISM band around the globe as part of Cisco’s LoRaWAN (long-range wide-area network) solution.

The Cisco Industrial Asset Vision solution includes it and a stand-alone component. Monitoring equipment, people, and facilities with LoRaWAN sensors improve business resilience, safety, and efficiency.

Cisco IoT Solution
Diagram: Cisco IoT Solution. Source Cisco.

Benefits of Cisco’s LoRaWAN:

1. Extended Range: With its long-range capabilities, Cisco’s LoRaWAN enables devices to communicate over several kilometers, surpassing the limitations of traditional wireless networks.

2. Low Power Consumption: LoRaWAN devices consume minimal power, allowing them to operate on batteries for an extended period. This makes them ideal for applications where the power supply is limited or impractical to install.

3. Scalability: Cisco’s LoRaWAN solutions are highly scalable, accommodating thousands of devices and ensuring seamless communication between them. This scalability makes it suitable for large-scale deployments, such as smart cities or industrial IoT applications.

4. Secure Connectivity: Security is a top priority in any IoT deployment. Cisco’s LoRaWAN solutions incorporate robust security measures, ensuring data integrity and protection against unauthorized access.

Cisco’s LoRaWAN Use Cases:

1. Smart Agriculture: LoRaWAN allows farmers to monitor soil moisture, temperature, and humidity, optimize irrigation, and reduce water consumption. Cisco’s LoRaWAN solutions provide reliable connectivity to enable efficient farming practices.

2. Asset Tracking: From logistics to supply chain management, tracking assets in real-time is crucial. Cisco’s LoRaWAN solutions enable accurate and cost-effective asset tracking, enhancing operational efficiency.

3. Smart Cities: LoRaWAN is vital in building smart cities. It allows municipalities to monitor and manage various aspects, such as parking, waste management, and street lighting. Cisco’s LoRaWAN solutions provide the necessary infrastructure to support these initiatives.

As the IoT ecosystem expands, the choice of access technologies becomes critical to ensure seamless connectivity and efficient data exchange. Wi-Fi, cellular networks, Bluetooth, Zigbee, and LoRaWAN are examples of today’s diverse IoT access technologies.

By understanding the strengths and limitations of each technology, businesses and individuals can make informed decisions about which access technology best suits their IoT applications. As we embrace the connected future, IoT access technologies will continue to evolve, enabling us to unlock the full potential of the Internet of Things.

IoT Access Technologies Closing Points

Wi-Fi is one of the most widely used access technologies in IoT. It offers high data rates, making it ideal for applications that require significant bandwidth, such as video streaming from security cameras or data transfers from smart appliances. However, Wi-Fi networks typically have limited range, which may necessitate additional infrastructure for widespread IoT deployments. Its widespread adoption in residential and commercial settings makes Wi-Fi a popular choice for many IoT applications

Cellular networks provide a robust solution for IoT devices that require mobility and extensive coverage. Technologies like 4G LTE and the emerging 5G networks offer high-speed data connections over large distances, making them perfect for applications such as connected vehicles and remote monitoring systems. The ability to maintain connectivity while moving and the potential for low-latency communication with 5G make cellular networks a pivotal component in the IoT landscape.

Low Power Wide Area Networks (LPWAN) are designed specifically for IoT applications that require long-range connectivity with minimal power consumption. Technologies such as LoRaWAN and Sigfox excel in scenarios where devices need to operate for extended periods without frequent battery replacements, such as in environmental monitoring or smart agriculture. These networks typically offer lower data rates, but their energy efficiency and extensive coverage make them ideal for specific IoT use cases.

For IoT applications that require short-range communication, Bluetooth and Zigbee are popular choices. Bluetooth is widely used in personal devices like wearables and health monitors due to its low power consumption and ease of integration. Zigbee, on the other hand, is often employed in smart home ecosystems, providing reliable mesh networking capabilities that enhance device-to-device communication within a limited area. Both technologies offer solutions for specific IoT scenarios where proximity and power efficiency are priorities.

Interactive IoT Deployment Challenge

Choose the Right Connectivity Architecture

Apply the engineering trade-offs from this article to a realistic deployment scenario.

1. Read the Scenario
Identify the dominant requirements before selecting a connectivity technology.
Scenario

A logistics company needs to deploy battery-powered sensors across a large agricultural site. The sensors transmit small amounts of telemetry several times per hour and must operate for years without frequent battery replacement.

Coverage Very high
Power budget Very low
Bandwidth Low
Mobility Moderate
Which connectivity technology is the strongest fit?
2. Engineering Assessment
Make your decision first. The assessment explains why the technology fits — or does not fit — the workload.
Select a technology and evaluate your choice.
Challenge Progress 0 / 1
Event Stream Processing

Event Stream Processing

Event Stream Processing

Modern applications generate a continuous flow of events: transactions, API requests, network telemetry, IoT measurements, security alerts, application logs, user interactions, and changes to business systems. Processing these events as they occur has become increasingly important because many operational decisions cannot wait for a batch job to run hours later. Event Stream Processing (ESP) provides a way to continuously analyse data in motion and respond to meaningful events as they arrive.

Unlike traditional batch processing, where data is collected and processed periodically, stream processing operates continuously against an incoming sequence of events. A stream-processing application can filter, transform, aggregate, correlate, enrich, and route events while they are moving through the system. The result may be an alert, database update, API call, automated workflow, dashboard update, or another event entering a downstream stream.

A modern ESP architecture typically separates event producers, event transport, stream processing, and downstream consumers. Applications, devices, databases, and infrastructure systems generate events. A streaming platform provides durable transport and partitioning, while stream-processing engines execute continuous computations over those events. Results can then be delivered to applications, data stores, observability platforms, security systems, or automated control processes.

Real-Time Processing: Stream processing enables organisations to evaluate information shortly after it is generated. This can support fraud detection, security monitoring, infrastructure observability, IoT analytics, application monitoring, and operational automation where delayed information reduces its value.

Stateful Stream Processing: Modern ESP is more than simply processing individual messages independently. Processing applications can maintain state across events, allowing them to calculate rolling statistics, track sessions, correlate related events, detect sequences, and identify changes in behaviour. Windowing techniques can limit calculations to periods such as the previous minute, hour, or day.

Event Time and Ordering: Real-world event streams are rarely perfectly ordered. Events may be delayed, duplicated, retried, or arrive out of sequence. Production stream-processing systems therefore need to consider event timestamps, processing time, watermarks, late-arriving events, partition ordering, and delivery semantics. These details can have a significant impact on the accuracy of real-time analytics.

Complex Event Detection: Stream processors can correlate events across multiple sources and detect patterns that would be difficult to identify from individual records. For example, a security platform could correlate authentication failures, unusual network connections, and privileged activity within a defined time window to generate a higher-confidence investigation signal.

Scalability and Resilience: Distributed stream-processing architectures can partition workloads across multiple processing instances, allowing systems to handle high event volumes while maintaining low processing latency. Production deployments also need to address checkpointing, state recovery, backpressure, partition rebalancing, fault tolerance, and scaling during traffic spikes.

Financial Services: Streaming analytics can support transaction monitoring, fraud detection, risk analysis, market-data processing, and real-time customer interactions. Decisions can be made while transactions are occurring rather than after large datasets have been accumulated.

IoT and Infrastructure: Sensors, network devices, applications, and cloud platforms can generate continuous telemetry. Stream processing can detect threshold breaches, identify anomalies, calculate rolling metrics, correlate events, and trigger automated responses without waiting for the telemetry to be stored and analysed later.

Supply Chain and Operations: Streaming data can combine inventory events, shipment updates, logistics information, customer demand, and external signals to provide continuously updated operational visibility. This can help organisations react to changes rather than relying exclusively on periodic reports.

ESP also introduces important engineering considerations. High event volumes require careful partitioning and capacity planning, while stateful processing requires appropriate storage and recovery mechanisms. Systems must also account for duplicate events, retries, schema evolution, data quality, security, access control, and observability. Exactly-once processing, where supported and correctly configured, can reduce some duplication and consistency problems, but it should not be treated as a universal guarantee across an entire distributed workflow.

The distinction between event streaming and event stream processing is also important. An event-streaming platform provides mechanisms for transporting and retaining events, while stream processing applies continuous computation to those events. A complete architecture may therefore combine streaming infrastructure, processing engines, databases, APIs, observability platforms, and automation systems.

The modern value of Event Stream Processing lies in turning continuously generated data into continuously updated decisions. Instead of asking only “What happened?” after data has been collected, organisations can increasingly ask “What is happening now, what does it mean, and what should happen next?”

When designed correctly, ESP becomes an important foundation for real-time analytics, observability, security operations, IoT systems, and automated business processes—bringing computation closer to the moment when the underlying event actually occurs.

Highlights: Event Stream Processing

Real-time Data Streams

Event Stream Processing, also known as ESP, is a computing paradigm that allows for analyzing and processing real-time data streams. Unlike traditional batch processing, where data is processed in chunks or batches, event stream processing deals with data as it arrives, enabling organizations to respond to events in real time. ESP empowers businesses to make timely decisions, detect patterns, and identify anomalies by continuously analyzing and acting upon incoming data.

Event Stream Processing is a method of analyzing and deriving insights from continuous streams of data in real-time. Unlike traditional batch processing, ESP enables organizations to process and respond to data as it arrives, enabling instant decision-making and proactive actions. By leveraging complex event processing algorithms, ESP empowers businesses to unlock actionable insights from high-velocity, high-volume data streams.

ESP Key Points: 

  • Real-time Insights: One critical advantage of event stream processing is gaining real-time insights. By processing data as it flows in, organizations can detect and respond to essential events immediately, enabling them to seize opportunities and mitigate risks promptly.
  • Scalability and Flexibility: Event stream processing systems are designed to handle massive amounts of real-time data. These systems can scale horizontally, allowing businesses to process and analyze data from multiple sources concurrently. Additionally, event stream processing offers flexibility regarding data sources, supporting various input streams such as IoT devices, social media feeds, and transactional data.
  • Fraud Detection: Event stream processing plays a crucial role in fraud detection by enabling organizations to monitor and analyze real-time transactions. By processing transactional data as it occurs, businesses can detect fraudulent activities and take immediate action to prevent financial losses.
  • Predictive Maintenance: With event stream processing, organizations can monitor and analyze sensor data from machinery and equipment in real time. By detecting patterns and anomalies, businesses can identify potential faults or failures before they occur, allowing for proactive maintenance and minimizing downtime.
  • Supply Chain Optimization: Event stream processing helps optimize supply chain operations by providing real-time visibility into inventory levels, demand patterns, and logistics data. By continuously analyzing these data streams, organizations can make data-driven decisions to improve efficiency, reduce costs, and enhance customer satisfaction.

Example: Apache Flink and Stateful Stream Processing

a) Apache Flink provides an intuitive and expressive API for implementing stateful stream processing applications. These applications can be run fault-tolerantly on a large scale. The Apache Software Foundation incubated Flink in April 2014, and it became a top-level project in January 2015. Since its inception, Flink’s community has been very active.

b) Thanks to the contributions of more than five hundred people, Flink has evolved into one of the most sophisticated open-source stream processing engines. Flink powers large-scale, business-critical applications across various industries and regions.

c) In addition to offering superior solutions for many established use cases, such as data analytics, ETL, and transactional applications, stream processing technology facilitates new applications, software architectures, and business opportunities for companies of all sizes.

d) Data and data processing have been ubiquitous in businesses for decades. Companies are designing and building infrastructures to manage data, which has increased over the years. Transactional and analytical data processing are standard in most businesses.

**Massive Amounts of Data**

It’s a common theme that the Internet of Things is all about data. IoT represents a massive increase in data rates from multiple sources that need to be processed and analyzed from various Internet of Things access technologies.

In addition, various heterogeneous sensors exhibit a continuous stream of information back and forth, requiring real-time processing and intelligent data visualization with event stream processing (ESP) and IoT stream processing.

This data flow and volume shift may easily represent thousands to millions of events per second. It is the most significant kind of “big data” and will exhibit considerably more data than we have seen on the Internet of humans. Processing large amounts of data from multiple sources in real time is crucial for most IoT solutions, making reliability in distributed systems a pivotal factor to consider in the design process.

**Data Transmission**

Data transmitted between things instructs how to act and react to certain conditions and thresholds. Analysis of this data turns data streams into meaningful events, offering unique situational awareness and insight into the thing transmitting the data. This analysis allows engineers and data science specialists to track formerly immeasurable processes. 

Before you proceed, you may find the following helpful:

  1. Docker Container Security
  2. Network Functions
  3. IP Forwarding
  4. OpenContrail
  5. Internet of Things Theory
  6. 6LoWPAN Range

Event Stream Processing

Stream processing technology is increasingly prevalent because it provides superior solutions for many established use cases, such as data analytics, ETL, and transactional applications. It also enables novel applications, software architectures, and business opportunities. With traditional data infrastructures, data and data processing have been omnipresent in businesses for many decades.

Over the years, data collection and usage have grown consistently, and companies have designed and built infrastructures to manage that data. However, the traditional architecture that most businesses implement distinguishes two types of data processing: transactional processing and analytical processing.

Analytics and Data Handling are Changing.

– All this type of new device information enables valuable insights into what is happening on our planet, offering the ability to make accurate and quick decisions. However, analytics and data handling are challenging. Everything is now distributed to the edge, and new ways of handling data are emerging.

– To combat this, IoT uses emerging technologies such as stream data processing with in-stream analytics, predictive analytics, and machine learning techniques. In addition, IoT devices generate vast amounts of data, putting pressure on the internet infrastructure. This is where the role of cloud computing comes in useful. Cloud computing assists in storing, processing, and transferring data in the cloud instead of connected devices.

– Organizations can utilize various technologies and tools to implement event stream processing (ESP). Some popular ESP frameworks include Apache Kafka, Apache Flink, and Apache Storm. These frameworks provide the infrastructure and processing capabilities to handle high-speed data streams and perform real-time analytics. 

IoT Stream Processing: Distributed to the Edge

1: IoT represents a distributed architecture. Analytics are distributed from the IoT platform, either cloud or on-premise, to network edges, making analytics more complicated. A lot of the filtering and analysis is carried out on the gateways and the actual things themselves. These types of edge devices process sensor event data locally.

2: Some can execute immediate local responses without contacting the gateway or remote IoT platform. A device with sufficient memory and processing power can run a lightweight version of an Event Stream Processing ( ESP ) platform.

3: For example, Raspberry PI supports complex-event processing ( CEP ). Gateways ingest event streams from sensors and usually carry out more sophisticated steam processing than the actual thing. Some can send an immediate response via a control signal to actuators, causing a state change.

Technicality is only one part of the puzzle; data ownership and governance are the other. 

Time Series Data – Data in Motion

In specific IoT solutions, such as traffic light monitoring in intelligent cities, reaction time must be immediate without delay. This requires a different type of big data solution that processes data while it’s in motion. In some IoT solutions, there is too much data to store, so the analysis of data streams must be done on the fly while being transferred.

It’s not just about capturing and storing as much data as possible anymore. The essence of IoT is the ability to use the data while it is still in motion. Applying analytical models to data streams before they are forwarded enables accurate pattern and anomaly detection while they are occurring. This analysis offers immediate insight into events, enabling quicker reaction times and business decisions. 

Traditional analytical models are applied to stored data, offering analytics for historical events only. IoT requires the examination of patterns before data is stored, not after. The traditional store and process model does not have the characteristics to meet the real-time analysis of IoT data streams.

In response to new data handling requirements, new analytical architectures are emerging. The volume and handling of IoT traffic require a new type of platform known as Event Stream Processing ( ESP ) and Distributed Computing Platforms ( DCSP )

Event Stream Processing
Diagram: Event Stream Processing.

Event Stream Processing ( ESP ) 

ESP is an in-memory, real-time process technique that enables the analysis of continuously flowing events in data streams. Assessing events in motion is known as “event streams.” This reveals what is happening now and can be used with historical data to predict future events accurately. Predictive models are embedded into the data streams to predict future events.

This type of processing represents a shift in data processing. Data is no longer stored and processed; it is analyzed while still being transferred, and models are applied.

ESP & Predictive Analytics Models

ESP applies sophisticated predictive analytics models to data streams and then takes action based on those scores or business rules. It is becoming popular in IoT solutions for predictive asset maintenance and real-time fault detection.

For example, you can create models that signal a future unplanned condition. This can then be applied to ESP, quickly detecting upcoming failures and interruptions. ESP is also commonly used in network optimization of the power grid and traffic control systems.

ESP – All Data in RAM

ESP is in-memory, meaning all data is loaded into RAM. It does not use hard drives or substitutes, resulting in fast processing, enhanced scale, and analytics. In-memory can analyze terabytes of data in just a few seconds and can ingest from millions of sources in milliseconds. All the processing happens at the system’s edge before data is passed to storage.

How you define real-time depends on the context. Your time horizon will depict whether you need the full power of ESP. Events with ESP should happen close together in time and frequency. However, if your time horizon is over a relatively long period and events are not close together, your requirements might be fulfilled with Batch processing. 

**Batch vs Real-Time Processing**

With Batch processing, files are gathered over time and sent together as a batch. It is commonly used when fast response times are not critical and for non-real-time processing. Batch jobs can be stored for an extended period and then executed; for example, an end-of-day report is suited for batch processing as it does not need to be done in real-time.

They can scale, but the batch orientation limits real-time decision-making and IoT stream requirements. Real-time processing involves a continual input, process, and output of data. Data is processed in a relatively short period. When your solution requires immediate action, real-time is the one for you. Examples of batch and real-time solutions include Hadoop for batch and Apache Spark, focusing on real-time computation.

**Hadoop vs. Apache Spark** 

Hadoop is a distributed data infrastructure that distributes data collections across nodes in a cluster. It includes a storage component called Hadoop Distributed File System ( HDFS ) and a processing component called MapReduce. However, with the new requirements for IoT, MapReduce is not the answer for everything.

MapReduce is fine if your data operation requirements are static and you can wait for batch processing. But if your solution requires analytics from sensor streaming data, then you are better off using Apache Spark. Spark was created in response to MapReduce’s limitations.

Apache Spark does not have a file system and may be integrated with HDFS or a cloud-based data platform such as Amazon S3 or OpenStack Swift. It is much faster than MapReduce and operates in memory and real-time. In addition, it has machine learning libraries to gain insights from the data and identify patterns. Machine learning can be as simple as a Python event and anomaly detection script.

Closing Points on Event Stream Processing 

Event Stream Processing is a computing paradigm focused on the real-time analysis of data streams. Unlike traditional batch processing, which involves collecting data and analyzing it periodically, ESP allows for immediate insights as data flows in. This capability is crucial for applications that demand instantaneous action, such as fraud detection in financial transactions or monitoring network security.

The architecture of an Event Stream Processing system typically comprises several key components:

1. **Event Sources**: These are the origins of the data streams, which could be sensors, user actions, or any system generating continuous data.

2. **Stream Processor**: The core of ESP, where the actual computation and analysis occur. It processes the data in real-time, applying various transformations and detecting patterns.

3. **Data Sink**: This is where the processed data is delivered, often to databases, dashboards, or triggering subsequent actions.

4. **Messaging System**: A crucial part of ESP, it ensures that data flows seamlessly from the source to the processor and finally to the sink.

The versatility of ESP makes it applicable across numerous industries:

– **Finance**: ESP is used in algorithmic trading, risk management, and fraud detection, providing real-time insights that drive decisions.

– **Healthcare**: In monitoring patient vitals and managing hospital operations, ESP enables timely interventions and improved resource allocation.

– **Telecommunications**: ESP helps in network monitoring, ensuring optimal performance and quick resolution of issues.

– **E-commerce**: Companies use ESP to personalize user experiences by analyzing browsing and purchasing behaviors in real-time.

Implementing ESP can be challenging due to the need for reliable and scalable infrastructure. Key considerations include:

– **Latency**: Minimizing the delay between data generation and analysis is crucial for effectiveness.

– **Scalability**: As data volumes increase, the system must efficiently handle larger streams without performance degradation.

– **Data Quality**: Ensuring data accuracy and consistency is essential for meaningful analysis.

Summary: Event Stream Processing

In today’s fast-paced digital world, the ability to process and analyze data in real time has become crucial for businesses across various industries. Event stream processing is one technology that has emerged as a game-changer in this realm. In this blog post, we will explore the concept of event stream processing, its benefits, and its applications in different domains.

Understanding Event Stream Processing

Event stream processing is a method of analyzing and acting upon data generated in real time. Unlike traditional batch processing, which deals with static datasets, event stream processing focuses on continuous data streams. It involves capturing, filtering, aggregating, and analyzing events as they occur, enabling businesses to gain immediate insights and take proactive actions.

Benefits of Event Stream Processing

Real-Time Insights: Event stream processing processes data in real time, allowing businesses to derive insights and make decisions instantly. This empowers them to respond swiftly to changing market conditions, customer demands, and emerging trends.

Enhanced Operational Efficiency: Event stream processing enables businesses to automate complex workflows, detect anomalies, and trigger real-time alerts. This leads to improved operational efficiency, reduced downtime, and optimized resource utilization.

Seamless Integration: Event stream processing platforms seamlessly integrate existing IT systems and data sources. This ensures that businesses can leverage their existing infrastructure and tools, making implementing and scaling event-driven architectures easier.

Applications of Event Stream Processing

Financial Services: Event stream processing is widely used in the financial sector for real-time fraud detection, algorithmic trading, and risk management. By analyzing vast amounts of transactional data in real time, financial institutions can identify suspicious activities, make informed trading decisions, and manage risks.

Internet of Things (IoT): With the proliferation of IoT devices, event stream processing has become crucial for managing and extracting value from the massive amounts of data generated by these devices. It enables real-time monitoring, predictive maintenance, and anomaly detection in IoT networks.

Retail and E-commerce: Event stream processing lets retailers personalize customer experiences, optimize inventory management, and detect fraudulent transactions in real time. By analyzing customer behavior data in real time, retailers can deliver targeted promotions, ensure product availability, and prevent fraudulent activities.

Conclusion: Event stream processing is revolutionizing how businesses harness real-time data’s power. Providing instant insights, enhanced operational efficiency, and seamless integration empowers organizations to stay agile, make data-driven decisions, and gain a competitive edge in today’s dynamic business landscape.