cloud

This post discusses the first 5G architecture pattern – where both the 5G Core and the Radio Access Network (RAN) are deployed on the cloud.

This post describes a model for the same, albeit one for AWS. It is to be noted that a 5G deployment will need the support of NEP (Network Equipment Provider) ISVs such as Nokia, Ericsson, Samsung et al. Fortunately all of these leading vendors provide functions that support some variant of the below model.

While Network Slicing is undoubtedly key in enabling operators to monetize 5G, the principles of DevOps as applied to network slicing and NF updates are key in helping achieve a competitive edge. 

I would like to round-out 2021 with a final post on a reference architecture that I have been driving towards all year. This post brings together several themes we have covered since 2019 – on the suitability of Kubernetes as a foundation for Telco 5G workloads. 

Network Slicing is a key feature of 3GPP proposed 5G specifications. As previous posts have discussed, network slicing enables the 5G network to offer business applications that offer various levels of services to customers.

Prior to the advent of K8s and Cloud-Native functions, network functions (NFs) were primarily deployed by CSPs as a combination of physical appliances and some VMs.

Amazon EKS Anywhere, is a new deployment option for Amazon EKS that enables customers and operators to run open-source Kubernetes clusters on-premises.

Proton provides platform teams with the tools to manage and enforce consistency across environments while helping developers as well.

Whatever the actual approach to cloud, it is clear that due to changing customer preferences, post-pandemic realities, and evolving business models, the banking institution will change dramatically every few years going forward.