It’s on everyone’s mind, whether they’ve adopted 5G yet or not. With over 1 billion global subscribers of 5G Non-Standalone (NSA) already, 24 full commercial operator launches of 5G Standalone (SA), and, it’s the proverbial elephant in the room.
But where’s the promise of 5G revenue?
Mobile network operators (MNOs) are projecting a range of opportunities, including Cloud Gaming (), Manufacturing ( ) along with Energy and Utilities ( ) to name a few. Spirent surveyed approximately 70 MNOs on what they saw the drivers for deploying 5G Core:
Realizing the prospect of offering new robust services to customers
Attainment of greater agility
Achieving lower costs
These services include network slices, private networks, edge services, Voice over New Radio (VoNR), autonomous networks, and more.
But how do we get there?
That’s where it gets complicated. As 5G fully embraces the cloud, complexity increases dramatically. This cloudification includes: Cloud applications like virtual network functions (VNFs) and cloud-native functions (CNFs); Private cloud platforms (supported by OpenStack and Kubernetes – including RedHat, DELL, IBM and Nokia – and Public cloud platforms like AWS, Google, Microsoft Azure, IBM Cloud, and more); and the cloud infrastructure involving hardware and software supporting virtualization and containerization.
Contrasting the traditional core, a quantum leap of vendors is now involved to make all this possible. This means faster and frequent multi-vendor releases.
That means testing complexity increases between 10-50X. Then there are the complexities of moving from the lab to the live production network.
How can this be addressed in a comprehensive way, and keep pace with the accelerating pace of technology evolution?
New testing models required for success in 5G Core adoptions
Early movers have many lessons learned on the road to 5G SA. One critical takeaway is that the cloud breaks 5G testing as we know it. Validating the telecom cloud is a big change. Why? 5G CNFs failures are significantly different from physical network function (PNFs) or even VNFs. Traditional manual validation testing simply can't keep up with the constant stream of releases of cloud-native functions and compute and connectivity infrastructure across an expanded set of 5G vendors.
The cloud breaks 5G testing as we know it.
MNOs have a host of questions that need to be answered to have confidence their 5G Core is working as planned. A few include:
Will the cloud reliably deliver performant 5G services?
Is the mobile core ready for customers?
How do faults in cloud impact 5G services?
Does each CNF deliver to spec?
Does the cloud provide consistent performance to CNFs?
To answer these questions, and others, a new class of cloud tests is required that address CNF resilience, benchmarking and upgrade/change management.
To achieve this, ecosystem of collaboration requires a unified, automated platform that delivers a continuous testing framework. This should account for more vendors, more layers and more complex validation tests. We need an automated approach for all ecosystem players to use and requires an open framework of inter-connected functions forming an integrated continuous integration, deployment and test (CI/CD/CT) pipeline, with consistency across lab, staging, and production.
A team of experts convened in a: Heavy Reading Principal Analyst, Ruth Brown, Spirent Head of Strategy, Steve Douglas, and Spirent VP of Global Business Solutions, Chris O'Loughlin. They explain why 5G is disrupting traditional testing and share how 5G leaders are adopting automation and "as a service" models with trusted testing partners to reinvent testing for the 5G cloud. For a majority of organizations for whom testing is not a core competency, this approach represents a practical cost-effective strategy to achieve comprehensive testing efficiencies, powered by seasoned expertise in the continuously evolving 5G technology front.
The webinar covers the following topics:
Service providers' transformation to the cloud: status, challenges, and headwinds
What a cloud-native 5G Core release calendar looks like and the move to CI/CD
The need for automation across the lab-to-live lifecycle
The role of "as a service" models and case studies