Terminology puzzle: Understanding telecoms, cloud, and edge technologies

Terminology used by telecoms and cloud providers often overlaps, leading to confusion
A representational image. — Freepik
A representational image. — Freepik

The terminology used by telecoms and cloud providers often overlaps, leading to confusion, despite the clear distinctions between these technologies. In essence, we are dealing with three distinct technological concepts. To make an informed decision on their utilisation, it is important to break them down, examine their benefits, and grasp the current state of edge technology.

5G: The evolution beyond 4G

5G represents the natural progression from 4G, but with a differentiating factor — it is based on IP (Internet Protocol). This means there is no need for a dedicated mobile network infrastructure. Communication and data transmission occur seamlessly over IP, eliminating the need for complex telecom protocols.

The cloud is not directly related to communication protocols but refers to the space where data processing takes place. To better understand the abstract notion of the "cloud," it is helpful to envision it as "outsourced infrastructure services." Prominent providers like AWS, Microsoft, or Google have a global network of data centres, but smaller cloud or colocation providers can also offer proximity to outsourced infrastructure services based on geographical location.

Mobile Edge Compute

Mobile Edge Compute (MEC) takes the concept of the cloud and brings it closer to radio masts. Instead of having computing resources, memory, and storage solely in data centres, these resources can be located near or directly behind radio masts. With a 5G-connected device, you can perform processing tasks right at the edge, obtaining immediate responses without the need to transmit data to distant data centres, such as those located in Arizona where AWS has many of its facilities.

Apart from latency, there are additional considerations regarding the movement of large volumes of data. For instance, if a retailer wants to analyse a video stream for theft-related activities, it may not be cost-effective to transmit the entire stream to the cloud for processing. Instead, deploying processing capabilities in-store or at the edge could be more efficient, although it may require trade-offs in terms of power usage and security measures.

Cloud-native aspect

The cloud-native element involves transforming network functions and services from dedicated appliances into virtual appliances. These virtual appliances operate as microservices within containers. This shift enables mobile operators to leverage services like AWS EC2, aligning them with the practices of DevOps and NetDevOps communities. However, it also presents challenges in terms of skill requirements, as service providers may lack the necessary background and experience to build and manage these networks effectively.