Vamsi Chemitiganti

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.

s telcos and other CSPs begin moving to 5G RAN and 5G Core deployments, these are overwhelmingly based on Cloud-native microservice architectures, REST APIs, Kubernetes-based containers, and NoSQL databases for stateless architecture are commonly implemented in telecom networks. With this blog, we begin discussing life cycle management of 5G networks.

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.

We briefly discussed the benefits of slicing from a 5G operator POV. Let us consider the top benefits of this technology from an Operator Standpoint.

Network slicing should be thought of as true business-level virtualization for 5G networks. Operators will be able to share the same 5G physical infrastructure among many multiple tenants – 5G service operators, enterprises and consumers.

The goal of 5G deployments is to provide consumers and business users with highly engaging experiences that leverage the high reliability and high performance provided by the underlying network.

As we discuss in this blog, Karpenter observes events within the Kubernetes cluster, and then sends provisioning commands to resources in the underlying cloud provider.

Join us for Container Day x KubeCon, a fully live, virtual day of sessions all about Amazon EKS and Kubernetes at AWS, hosted by Containers from the Couch.