5G

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.

This post and the next one discuss the next generation of tools for telco service update, we first cover IaC (Infrastructure as code) tools to deploy end-to-end networks

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. 

We will make extensive use of Outposts deployments when we discuss 5G network architectures in follow-up blogs in 2022.

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.

We will cover a reference architecture for network slicing in this blogpost. 

3GPP as the foremost standards body driving network slicing defines the overall framework for Operators to provide customized network slice instances (NSI) that support various requirements/features. These include a Network Slicing management framework which this blog post will discuss. 

3GPP is the principal standards body driving 5G architecture and standards. It has defined various network slicing specifications in its various working groups.

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.