Vamsi Chemitiganti

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.

Outposts is a family of fully managed solutions delivering AWS infrastructure and services to virtually any on-premises or edge location for a truly consistent hybrid experience.

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.