The Building Blocks of Edge Computing
The IoT has rapidly gained a profile in our everyday lives as its phenomenal growth has enabled the connection of a wide range of devices in our homes and in our working environments. The sophistication of these connected devices is continually increasing, allowing more computing to be done at the edge, instead of in the cloud. Computing at the edge of a network may be a well-established concept, but, for successful operation, edge devices must possess a broad set of capabilities to ensure optimal security, energy efficiency, connectivity, and of course, computing power.
In this article, we take a look at the building blocks which are enabling this new generation of connected devices to support IoT edge computing.
What happens at the edge?
The generic diagram of an embedded IoT device, depicted in Figure 1, illustrates the basic functions performed at the edge. The edge device monitors a range of inputs, via sensors, and alters a set of outputs, via actuators, based upon the status of the inputs. A microcontroller unit (MCU) at the heart of the device converts the data (analog to digital or vice versa) and performs various operations on it, depending on the specifics of the application. The MCU will also be equipped with resources such as memory, connectivity (to enable communication with the cloud and with other sensors), security, and real-time capabilities – such as interrupt scheduling and real-time processing.
Figure 1: generic IoT device functionality
The MCU is therefore the engine of the IoT device, and its computing power is dictated by the specifics of the application. Engine control units in a connected automobile, for example, may need to react to an input change in real-time, requiring sophisticated decision-making capability. To achieve near real-time responsiveness, the computing algorithm must be located locally – meaning that the MCU must have the resources to host it. Applications such as remote sensor monitoring in agriculture will generate less data and will usually have more relaxed response time requirements, meaning that decision-making can take place in the cloud, reducing the requirements on the MCU.
The MCU is therefore a critical component of the IoT device and the above description hints at some of the trade-offs facing the designer when choosing the optimum device.
The MCU dictates the performance of the IoT device
The MCU, described above, is actually a “system-on-chip” (SoC), literally a chip containing all of the functionality of a computer system, Figure 2.
Figure 2: The MCU is a system-on-chip
The brain of this SoC is the microprocessing unit, (MPU), a general-purpose digital computer central processing unit, whose main objective is to read data, perform extensive calculations on it, and either store or display the results. Modern MPUs, such as those based on Arm technology, can contain multiple cores, each capable of executing instructions independently and therefore handling different tasks. One core, for example, could be dedicated to handling real-time operations with another taking care of background system operations. Multiple cores can also be treated as a single unit, or cluster, where processing demand is higher. The power consumption of multi-core systems can be significantly lower than that of single processor cores, since they can execute instructions faster, enabling cores to be powered down for periods where they are idle. Throughput can also be higher with multiple cores, enabling the device to operate at lower frequencies, and individual cores can be shut down when not in use, saving power consumption.
Continue reading: https://www.eetimes.eu/the-building-blocks-of-edge-computing/