{"id":16568,"date":"2022-02-25T11:26:11","date_gmt":"2022-02-25T11:26:11","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/25\/the-status-of-5g-edge-computing-as-we-see-challenges-remain\/"},"modified":"2022-02-25T11:26:11","modified_gmt":"2022-02-25T11:26:11","slug":"the-status-of-5g-edge-computing-as-we-see-challenges-remain","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/02\/25\/the-status-of-5g-edge-computing-as-we-see-challenges-remain\/","title":{"rendered":"The status of 5G edge computing as we see challenges remain"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

The big picture:<\/strong> With less than a week to go until the Mobile World Congress kicks off in Barcelona, a great deal of attention is being focused on the latest developments in 5G and related technologies. Now that 5G networks<\/a> are becoming increasingly common around the world, the focus is shifting away from simply faster download speeds to the new capabilities that 5G networks were supposed to enable. Chief among these are edge computing applications. <\/p>\n

5G-based edge computing was supposed to deliver all kinds of futuristic applications. It was the promise of these new applications that arguably triggered some of the initial excitement and hype around the latest generation mobile network standard. But now that the time has come to turn these concepts into reality, there\u2019s a great deal of uncertainty as to how that\u2019s going to be achieved.<\/p>\n

Don\u2019t get me wrong, I expect to see a huge amount of discussion and even product announcements around 5G edge computing coming from MWC. When you start to scratch below the surface of this news, however, the picture isn\u2019t so clear.<\/p>\n

A big part of the problem boils down to definitions\u2014or rather, the lack of them. The \u201cedge\u201d has always been a fuzzy topic, and now we\u2019ve seen several variations on it\u2014like \u201cnear edge\u201d and \u201cfar edge\u201d\u2014that, while certainly well intentioned, only serve to confuse matters more. It\u2019s hard to have a clear conversation about a concrete topic when the subject matter at the heart of the discussion is so amorphous.<\/p>\n

Another confusing issue that\u2019s starting to become more apparent is uncertainty around who, where, and how these 5G edge applications, along with the necessary computing resources, will live, and who will offer them. Some of this stems from the lack of clarity around business models of various players\u2014carriers, cloud computing providers, network infrastructure vendors, application providers, businesses, etc.\u2014and how they will need to interact.<\/p>\n

To put things more bluntly, early conversations around 5G edge often seemed to suggest we were headed towards a day when computing resources (i.e., small, power-friendly servers) would be housed in nearly every cell tower and those servers would run specialized \u201cedge\u201d applications that could benefit from their proximity (e.g., low latency, high speed) to other devices. However, the reality of today\u2019s Mobile Edge Computing (MEC) offerings\u2014the phrase that many telcos and other tech players are using to describe 5G edge computing\u2014looks to be significantly different.<\/p>\n

Much of the \u201cedge computing\u201d is really just public cloud computing that happens to be connected via cellular networks…<\/p>\n

For one, it\u2019s clear now that the cost, complexity, and logistical hassle of adding computing resources to every cell tower, or even a modest percentage, will keep that from happening for a very long time. In fact, in my conversations with major US carriers, it sounds like we\u2019re several stages away from anything like that happening soon. Instead, standard practice seems to be based around using a few geographically-spaced data centers to run edge-based applications. Interestingly, most of them aren\u2019t housed in carrier facilities. Instead, carriers are essentially leasing space from the major cloud computing providers.<\/p>\n

In other words, much of the \u201cedge computing\u201d is really just public cloud computing that happens to be connected via cellular networks. Now, there\u2019s certainly nothing wrong with this approach. In fact, it makes sense. Nevertheless, it does seem to be much different than what many people perceive to be \u201cthe edge.\u201d<\/p>\n

\"\"<\/picture><\/p>\n

Another important clarification is that the carriers certainly do have large data centers of their own, and many of them play critical roles in 5G networks. However, much of that work is for running the network itself, using software-based technology to drive virtual RAN (radio access networks) and some early experiments in Open RAN. Part of the confusion around this topic is that many of the newest 5G compute-based offerings are really tied to this shift from a traditional network-infrastructure hardware model to a software-based virtualized one. That\u2019s clearly a very important step forward for telcos in general and a great opportunity for tech vendors to get their products and technologies embedded into 5G networks. However, it\u2019s architecturally still one step below actually running edge-based applications on top of this software-defined network.<\/p>\n

Seemingly, the next logical step in making edge computing more real for carrier networks would be to extend to a wider range of cloud computing sites, to expand into their own regional data centers, or likely, some combination thereof. After that, we could see telcos expanding their computing capabilities to traditional COs (central offices) that US carriers have dispersed around the country or in other co-location sites such as those offered by companies like Equinix. There are multiple challenges to each of these scenarios, however, not the least of which is the time, money, and effort it would require to drive these expanded computing efforts. An even more fundamental problem is determining who actually offers the value in a situation with these shared resources. In other words, does an enterprise or consumer-focused business go to a carrier or a cloud computing provider to get an edge computing project done?<\/p>\n

Yet another challenge in understanding the real status of 5G edge computing comes when you start to consider the public 5G networks and the hot new world of private 5G networks. Running edge applications on public networks is significantly more challenging on an architectural, logistical, and practical front, because, right now, it\u2019s extremely difficult to know what applications would need to run on which portions of the public network.<\/p>\n

Ideally, of course, combining a vast amount of computing resources with the flexibility and \u201cmobility\u201d of containerized, cloud-native applications would let essentially any edge computing app run anywhere, but practically speaking, that\u2019s just not possible now (nor will it likely be for some time). On top of that, while there have been a few interesting applications touted for public 5G edge computing, the truth is, the delay for many applications is due in part to the fact that companies are still trying to figure out what exactly they want to do.<\/p>\n

As mentioned earlier, given the fact that the computing resources for these public 5G edge applications aren\u2019t really that close to the edge, it does beg the question of how or why it\u2019s different from established cloud computing practices. And let\u2019s be honest, how many public network-driven applications will ever really need single millisecond latency? The long-promised network slicing technology could offer some promise here as a dedicated path for 5G-based applications. However, given that network slicing requires 5G standalone (SA) and that we\u2019re still years away from SA being the standard in the US, network slicing won\u2019t be coming anytime soon either. Only T-Mobile offers a 5G SA network, and they don\u2019t currently offer network slicing.<\/p>\n

Through private 5G networks, on the other hand, the benefits of edge computing become much more obvious, and it\u2019s here where I think the real opportunity lies\u2014at least for the next several years. In a private network, the geographical proximity to computing resources is a non-issue, the access to applications needed to run is inherently limited because it\u2019s only for employees of that organization, and the arguments about the theoretical benefits that we\u2019ve long been promised for 5G edge computing all start to make sense. That\u2019s why things like the announcement of AT&T\u2019s new Private 5G Edge offering\u2014done in conjunction with and leveraging Microsoft\u2019s Azure cloud computing resources\u2014is the kind of news that I expect to see more of over the coming year. Even here, though, the company acknowledges that it\u2019s early days for 5G edge computing on private networks, because organizations are still trying to figure out how to best take advantage of it.<\/p>\n

Despite all the concerns I\u2019ve raised, I do believe embedding computing capabilities into the network and enabling 5G edge computing is a critical differentiator for the latest generation mobile networks. Exactly when those capabilities are going to be widely available, who\u2019s going to offer them, who\u2019s going to make money from them, and what they\u2019re going to do, however, remain largely unanswered questions. Stronger definitions of what the various flavors of edge computing actually are would certainly help, but it\u2019s also going to take a lot of technical experimentation, business model adjustments, and creative thinking to help fulfill the vision of what 5G edge computing can really be.<\/p>\n

Bob O\u2019Donnell is the founder and chief analyst of TECHnalysis Research, LLC<\/a> a technology consulting firm that provides strategic consulting and market research services to the technology industry and professional financial community. You can follow him on Twitter @bobodtech<\/a>.<\/p>\n

Masthead credit: upklyak<\/a><\/p>\n<\/p><\/div>\n