Strategies for Deploying and Managing 5G Networks

Introduction:?

Client recognized the importance of building a strong wireless network to deliver high-quality services and meet the evolving needs of its customer base. To achieve this, the company adopted an innovative MSP approach, effectively collaborating with various service providers across three critical teams: RAN, E2E, and IMS Core. This case study delves into the strategies and outcomes of Network's MSP implementation.?

Overview of Scope:?

This case study explores Network's innovative Multi-Service Provider (MSP) approach in building and operating their wireless network. Network, a major telecommunications company, embarked on a transformative journey to establish a robust and reliable wireless infrastructure. By leveraging multiple service providers and focusing on Radio Access Network (RAN), End-to-End (E2E) integration, and IMS Core teams, Network successfully deployed a state-of-the-art network that offers exceptional connectivity and services to its customers.

AWS Proserve is requesting teams of resources, working in PODs model, to build, deploy, and support network functions running on the AWS platform within a telecom provider environment. Resources will provide 24 X 7 coverage adhering to SLA provided. Resources will work jointly with the existing AWS Build and AMS team. AWS Proserve is seeking the most optimal rates for resources based on the capacity requested.

Resources will meet the experience level, skill, and role requirements as provided. Role description, scope, and deliverables are provided for each role. The team would implement identified User Stories and defined backlog in the Customer’s pre-production environment.

Subscribe the Newsletter

which may include :

• Configuration of the Account Vending Machine (AVM) on AWS Landing Zone?

• Creation of testing environments and test slices?

• Based on a jointly developed design, configuring virtual private cloud (VPC), network access control lists (NACLs), security groups, and AWS Transit Gateway to operationalize Customer’s 5G Network on AWS?

• Configure AWS Organizations?

• Identifying a minimum-security baseline (MSB), to include configuring AWS Services intended to help Customers with preventive and detective control?

• Configure AWS Identity and Access Management (AWS IAM), and implement AWS Federated Authentication with Active Directory Federation Services (AD FS)?

• Configuring Customer’s AWS Service Catalog and developing AWS CloudFormation templates designed to help Customer automate products in Customer’s AWS master account?

• Configuring Customer’s AWS Outposts for 5G?

• Creation of VPCs/underlay networking via automation – at the Region, AZ, and LZ levels?

• Prepare JSON files and create subnets via automation (private, public, and for vRouters)?

• Provision egress access for EKS cluster deployment?

• FOR CNFs Deployed to LZs - Setup of network connectivity between Region and Local Zone, including egress?

• TGW Configuration of TGW and attachments for underlay?

• vRouter provisioning on EC2?

• Deployment of DNS (R53)?

• EKS Cluster creation via infra pipeline?

• NodeGroup creation via infra pipeline?

• Create, or update, application pipeline for CNF?

• Deploy CNF via application pipeline?

• Validate deployment?

• Troubleshoot any issues (e.g., connectivity, etc.)?

• End to End-to-end integration Support of Cloud Network Functions?

• Triage/work on JIRA tickets?

• Build End-to-end integrations?

• Handle tickets raised by other sources as well as their own?

• Adhere to agreed SLAs for operations and maintenance??

System Design Guiding Principles:?

To achieve the client’s ambitious 5G rollout target, the company’s architecture team partnered with AWS to design a scalable, automated platform to run its 5G functions. As an industry first and a groundbreaking deployment, the following guidelines were used in architecting the new platform:?

• Maximize the use of cloud infrastructure and services.?

• Enable the use of 5G components for services in multiple target environments (Dev/Test/Production/Enterprise) with full automation.?

• Maximize the use of native automation constructs provided by AWS instead of building overlay automation.?

• Maintain the flexibility to use a mix of cloud-native APIs as well as existing telecom protocols.?

Deployment in AWS Cloud:?

The architecture of the 5G network leverages the distributed nature of 5G cloud-native network functions and AWS Cloud flexibility, which optimizes the placement of 5G network functions for optimal performance based on latency, throughput, and processing requirements. Through this design, the aim is to provide nationwide 5G coverage.

The proposed network design utilizes a logical hierarchical architecture consisting of National Data Centers (NDCs), Regional Data Centers (RDCs), and Breakout Edge Data Centers (BEDCs) (Fig 1) to accommodate the distributed nature of 5G functions and the varying requirements for service layer integration. BEDCs are deployed in AWS Local Zones hosting 5G network functions (NFs) that have strict latency budgets. They relate to the network’s Passthrough Edge Data Centers (PEDC), which serve as an aggregation point for all Local Data Centers (LDCs) and cell sites in a particular market. BEDCs also provide internet peering for general 5G data service and enterprise customer-specific private network service.

The client is pioneering the deployment of a 5G network using O-RAN standards in the United States. An O-RAN network consists of an RU (Radio Unit), which is deployed on towers, and a DU (Distributed Unit), which controls the RU. These units interface with the Centralized Unit (CU), which is hosted in the BEDC at the Local Zone. These combined pieces provide a full RAN solution that handles all radio level control and subscriber data traffic.

Colocated in the BEDC is the User Plane Function (Data Network Name (DNN) = Internet), which anchors user data sessions and routes to the internet. The BEDCs leverage local internet access available in AWS Local Zones, which allows for a better user experience while optimizing network traffic utilization. This type of edge capability also enables different enterprise customers and end-users (gamers, streaming media, and other applications) to take full advantage of 5G speeds with minimal latency. The client has access to 16 Local Zones across the U.S. and is continuing to expand. For the latest information about Local Zones, visit the AWS Local Zone Page.

RDCs are hosted in the AWS Region across multiple availability zones. They host 5G subscribers’ signaling processes such as authentication and session management as well as voice for 5G subscribers. These workloads can operate with relatively high latencies, allowing for a centralized deployment throughout a region, resulting in cost efficiency and resiliency. For high availability, three RDCs are deployed in a region, each in a separate Availability Zone (AZ) to ensure application resiliency and high availability. An AZ is one or more discrete data centers with redundant power, networking, and connectivity in an AWS Region. All AZs in an AWS Region are interconnected with high-bandwidth and low-latency networking over a fully redundant, dedicated metro fiber, which provides high-throughput, low-latency networking between AZs. CNFs deployed in the RDC utilize an AWS high-speed backbone to failover between AZs for application resiliency. CNFs like AMF and SMF, which are deployed in RDC, continue to be accessible from the BEDC in the Local Zone in case of an AZ failure. They serve as the backup CNF in the neighboring AZ and would take over and service the requests from the BEDC.

The NDCs host nationwide global services such as subscriber database, IMS (IP multimedia subsystem: voice call), OSS (Operating Support System), and BSS (Billing Support System). An NDC is hosted in the AWS Region and spans multiple AZs for high availability. To meet geographical diversity requirements, NDCs are mapped to AWS Regions where three NDCs are built in three U.S. Regions (us-west-2, us-east-1, and us-east-2). AWS Regions us-east-1 and us-east-2 are within 15 ms while us-east-1 to us-west-2 is within 75 ms delay budget. An NDC is built to span across three AZs for high availability.

Radio Access Network (RAN):?

The RAN team at Client’s side played a critical role in the deployment of the wireless network infrastructure. By partnering with multiple RAN service providers,Network aimed to ensure extensive coverage and optimal network performance. The selection process involved evaluating the providers' expertise, network capabilities, and geographical reach. By leveraging the strengths of each service provider, Network achieved a comprehensive RAN deployment, enabling seamless connectivity and high-speed data transmission across a wide range of devices.?

During the implementation, we faced challenges related to coordination among multiple service providers, ensuring interoperability, and maintaining consistent network quality. However, by establishing effective communication channels and clear service level agreements (SLAs) with each provider, the proposed solution was able to address these challenges and achieve successful RAN integration.?

The benefits of solution ‘sMSP approach in the RAN domain were significant. The collaboration with multiple service providers allowed for rapid deployment, optimized resource allocation, and the ability to adapt quickly to changing market conditions. Furthermore, the diverse expertise brought by each service provider led to a more resilient and future-proof wireless network infrastructure.?

End-to-End (E2E) Integration:?

E2E integration is crucial for seamless connectivity and service delivery. Provided network engaged with specialized E2E service providers to integrate various network components, such as the RAN, backhaul, core network, and OSS/BSS systems. The case study explores the significance of E2E integration in provided network's MSP model, highlighting the advantages gained from leveraging external expertise.?

By partnering with specialized E2E service providers, client ’s Network gained access to expertise in network architecture design, system integration, and end-to-end testing. The collaboration with these providers facilitated the seamless integration of disparate network elements, optimizing network performance and enhancing the overall user experience.?

However, achieving E2E integration posed challenges such as ensuring compatibility among different vendor solutions, managing complex network configurations, and maintaining strict security protocols. The solution’s MSP approach enabled the company to leverage the expertise of the E2E service providers, overcoming these challenges and achieving a highly integrated network infrastructure.?

IMS (IP Multimedia Subsystem) Core:?

The IMS (IP Multimedia Subsystem) Core team focuses on the core network elements that enable the delivery of voice, video, and data services over IP-based networks. Client partnered with IMS Core service providers to design and deploy a robust and scalable core network architecture. This section of the case study discusses the collaboration process, the integration of IMS Core components, and the resulting impact on network performance.?

The partnership with IMS Core service providers allowed prospect to benefit from their specialized knowledge in designing and optimizing IMS Core networks. The providers assisted in implementing advanced features such as session management, multimedia services, and interconnection with external networks. The collaboration ensured that the prospect’s core network met the highest standards of performance, reliability, and scalability.?

Challenges faced during the IMS Core implementation included interoperability with existing network components, ensuring seamless handover between different network technologies, and accommodating future network expansion. Through effective coordination with the service providers, the solution was able to address these challenges and successfully deploy a resilient IMS Core network.?

DevOps and Infrastructure Deployment:?

Overview?

The Network Service E2E Integration teams are accountable for the over-all deployment of the network service. Responsibilities include:?

1. Manage network requirements, and adhering to committed quarterly plan?
2. Maintain over-all E2E network design?
3. Work with prospect and ISVs for E2E integration of network services?
4. Work with test automation ISVs for over-all integration and performance tests?
5. Maintaining documentation?
6. Supporting Operational Transition?

Deliverables:?

1. E2E network design?
2. Integration Runbooks?
3. Open and Close defects?

Metrics:?

1. Implementation of markets in committed time?
2. Variance from committed design?
3. Integration Test success?
4. Successful transition to operations?
5. Defect Management SLA?

Defect Management:?

1. Manage Sev1, Sev.2, Sev. 3 Jira Tickets?
2. All resources are proficient in Jira and has experience working in Agile?
3. Defect Management SLA?

Explore Further