architecture

This implementation uses O-RAN standards and consists of a Radio Unit(RU) deployed on cell towers and a Distributed Unit (DU) as well as a centralized unit (CU) which is deployed in an AWS local zone.

DISH Networks is pioneering the deployment of a greenfield 5G network. This implementation uses O-RAN standards and consists of a Radio Unit(RU) deployed on cell towers and a Distributed Unit (DU) as well as a centralized unit (CU) which is deployed in an AWS local zone. While these components combine to provide a full RAN solution that handles radio level control and subscriber data traffic, let us consider the key architecture lessons from this first blog.

Before we dive into the 5 main solution architecture patterns for 5G deployments, let us discuss the key considerations and domains involved in creating an architecture than can accommodate 

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.

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. 

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.

To break this out into numbers, a typical CSP will deploy hundreds of thousands of network services as virtual network functions (VNFs) or CNFs. VNFs will run in virtual machines that can optionally be run inside a Kubernetes distribution.