deploying a 5G System Core on an aws ra.pdf

The typical model of 5G network infrastructure is composed of a 4G/5G radio site, a fronthaul/midhaul/backhaul network, a core network site, and a telecom/IT data center. CSPs can use AWS Services to create a scalable, flexible 5G network infrastructure while reducing upfront investment cost. AWS can be used to implement the virtual Network Operation Center (NOC) in the Region that hosts the Operations Support System/Business Support System (OSS/BSS) and the majority of control plane core network functions.

AWS can also be leveraged. to implement the local central office (CO) or distributed data center with a fleet of AWS Outposts instances that host mostly user-plane functions such as UPF (user-plane function), RAN central unit (CU), and Multi-Access Edge Computing (MEC). A more detailed explanation of the reference architecture and the benefits of 5G network implementation on AWS is explained in the 5G Network Evolution on AWS

whitepaper.

When it’s time to implement the 5G network on AWS, AWS CI/CD tools, which are introduced in the following sections of this whitepaper, can facilitate the full automation of deployment, upgrade, and lifecycle management of 5G network functions.

The design construct of the infrastructure is stored in the form of code using declarative language. This enables the CSP to have a repeatable reproduction of the infrastructure with the same expected behavior as needed. The code is maintained in the code repository, and a pipeline is set up to orchestrate updates to the deployed stacks (for example, AWS CDK and AWS CloudFormation). AWS can help build Infrastructure as Code (IaC) for agile onboarding of Independent Software Vendor (ISV) functions.

Changes in cloud-native network function configurations through Helm charts are considered to be triggers for an automatic CI/CD pipeline execution for network functions.

AWS CodeCommit can be used to maintain configuration files, and Amazon ECR can be used to preserve container images.

As shown in the Code pipeline flow figure, when the ISV pushes new code changes into the code repository (Helm chart, config files, or a properties file), the code pipeline is triggered. The code pipeline pulls the image from ECR and use the Helm chart to deploy the application. The new application testing can be integrated with the third-party test automation framework. Based on the result, CSPs can approve for production deployment.

The CodePipeline source stage looks for changes in configuration files. The valid providers for source stage are CodeCommit, Amazon S3, GitHub, or AWS CloudFormation. Alternative source systems can be integrated by using Lambda functions to implement Webhooks, which enables event-driven integration between Gitlab and AWS CodePipeline. See the following links for a detailed implementation guide.

1. © 2020, Amazon Web Services, Inc. or its affiliates. All rights reserved.AWS Reference Architecture
Private subnet
Orchestration, operational, and business
support systems can run on AWS Regions
with direct connectivity to on-premises data
centers.
9
AWS Transit Gateway is used to provide
connectivity to other VPCs that performs 5G
management and control services.
8
The service end-point provides direct access
to AWS regional services such as Amazon
Simple Storage Service (Amazon S3)
without traversing via internet.
7
AWS Direct Connect can be used to provide
high throughput connection to VPC on an
AWS Region (via public virtual interface).
6
Service Link traffic in outpost get separated
from local traffic via virtual LANS (VLANS),
providing connectivity both locally and to
AWS Regions.
5
Internet access to mobile subscribers is
achieved via local gateway as a default route
in the subnet route tables.
4
Outpostshas two subnets (for ingress and
egress) with routing tables that contains paths
to service end points and Transit Gateway to
other virtual private clouds (VPCs).
3
UPF instances are containers running on
Amazon Elastic Kubernetes Service
(Amazon EKS)with access to multiple
network interfaces via AWS Multi-homing
support and Multus.
2
Subscriber’s traffic from radio access network
(RAN) ingress/egress AWS Outposts running
5G User Plane Function (UPF) via Outposts
Local Gateway (LGW) .
1
Deploying 5G Core on AWS
Distribute your 5G Core to on-premisesdata centers
This reference architecture explains how 5G Core can be distributed between on-premises data centers and AWS
Regions.
Customer
Gateway
Local
Router (LR) Radio
Sites
Region
Internet/
Backbone
Local Internet
Gateway
AWS Outposts
5GC DP
Amazon
EKS
ENA
Amazon EC2
ASG
UPFUPF…
UPFUPF…
UPFUPF…
EC2 Worker nodeEC2 Worker nodeEC2 Worker node
Outpost
Subnet 1
Outpost
Subnet 210.1.0.0/16Local
DestinationTarget
0.0.0.0/0LGW
S3.prefix.listVPCE
Other routesTGW
Extension to Region VPC 10.1.0.0/16
Service Link
Amazon EKSAmazon EC2Amazon
ElasstiCache
Amazon
Aurora
Amazon
DoucumentDB
Amazon
EBS
Amazon
EFS
AWS
App Mesh
ELBAWS
Lambda
Amazon
CloudWatch
AWS
CloudFormation
AWS
CloudTrail
AWS X-RayAWS
CodeCommit
AWS
CodeBuild
Amazon
S3
Amazon
SageMakerer
AWS
CodeDeploy
Amazon
ECR
Amazon
QuickSight
Amazon
ElasticSearch
Service
Amazon
S3
AZ-aAZ-bAZ-c
UDM
µService
AUSF
µService
NSSF
µService
AMF
µService
SMF
µService
PCF
µService
…
µService
…
µService
NRF
µService
5G Core
OSS
µService
BSS
µService
OSS/BSS
AWS
Transit
Gateway
Local Network
VPC CIDR 10.1.0.0/16
1
2
3
4
5
7
8
9
VPC CIDR 10.2.0.0/16
10.1.4.0/24
10.1.5.0/24
IGW
VPCE
Corporate Data Centers (Core)
VPC Extension
5GC CP
LGW
AZ-aAZ-bAZ-c
Private subnet
Public subnet
AWS App MeshAWS X-RayPrometheusGrafanaMultusfluentd