5g cnf弹性测试

5G CNFResiliency Testing Contents Cloud-native Architectures for 5G Success3Cloud-native Efficiencies and Challenges4The mobile evolution to cloud-native architectures4Adoption challenges for 5G cloud-native architectures5A New Way: CNF Resiliency Testing7The cloud-native approach to resiliency7The challenges of pre-production CNF resiliency testing8How CNF resiliency testing addresses cloud-native challenges10How CNF resiliency testing supports production11Outcomes from CNF resiliency testing12Testing hard and soft cloud failures13The importance of automation in CNF resiliency testing15The Business Value of CNF Resiliency Testing16How Spirent Can Help16 Cloud-native Architectures for 5G Success Service providers expect 5G to help power critical businesstransformation by diversifying and growing revenue streams. The rightstrategy will support rollout of new services in weeks versus months, withalways-on, high-performance, and expansive coverage attracting anddelighting customers. This vision cannot be achieved without cloud-native architectures, which service providersare adopting in anticipation of myriad benefits, including: •Agility to adapt quicklyto changing market demands and customer needs byrapidly deploying network services and applications.•Scalability to support 5G adoptionby provisioning additional network capacityon demand.•Cost-efficiency to reduce operational spendby leveraging cloud infrastructureand automation tools. In short, cloud-native architectures provide the foundation service providers need tosuccessfully pursue 5G opportunities across consumers and industry. Cloud-native Efficiencies and Challenges Cloud-native architectures represent a technology evolution to software-based services and networksthat enable agility and efficiency. However, these advancements introduce considerable complexity. This guide addresses the challenges associated with cloud-native mobile network deployments, andexplores how test and assurance must evolve to mitigate service disruptions. The mobile evolution to cloud-native architectures Mobile infrastructures have become increasingly software-based, comprisingever-smaller software entities that communicate and run on commodityhardware. Over time, these functional building blocks, known as networkfunctions, have progressed from physical to virtual, and now, cloud-native.It’s helpful to understand the advancements each of these evolutions haveintroduced: •Physical.Single vendors provide network nodes or functions (e.g., a switch)with integrated hardware and software.•Virtualized.Virtualized network functions are disaggregated fromunderlying virtual machines to improve hardware utilization, but rigidcoupling between network function and virtual machines limits flexibility.•Cloud-native.Containerized cloud-native functions (CNFs) communicatevia standardized APIs, supporting multiple vendors with servicesabstracted and exposed to smaller units of code (pods). A cloud-native architecture increases network efficiency and hardwareutilization to enable automation by: •Breaking software into smaller piecesso more network functions can runon existing hardware and serve more customers with the same hardwareinvestment.•Automatically adding or removing podsto efficiently and quickly meetdemand changes.•Easily migrating all pods to different hardwarewhen current hardwareneeds to be updated.•Quickly replacing a dysfunctional podwithout impacting users.•Automatically optimizing resource utilizationaccording to service providerpolicies. A Spirent Guide Adoption challenges for 5G cloud-native architectures The benefits of cloud-native architectures are also accompanied by technology and business challenges. Technology challenges The fine granularity of containerized cloud-native software, dynamic nature of 5G networks and services, and customer and use cases withreal-time response expectations pose new challenges versus monolithic physical networks or virtualized networks. Let’s review the impact each of these challenges has on deployments. Dynamic, “multi” environment. Performance dependencies. Performance expectations. CNFs and the clouds that interconnect themchange continuously based on demandand routine operational challenges. Thesechanges can introduce subtle, hiddenissues that may not manifest until thesystem is under stress in the productionnetwork. Risk is increased because: The performance of a 5G service dependson the CNF’s performance, the cloud-native infrastructure’s performance, andthe performance of the CNF-to-cloudinterface. Service performance is put atrisk when: 5G use cases require strict real-timeresponses for millions of concurrent users.Real-time responsiveness is challengedbecause each: •5G service contains multiple CNFs, thatare highly interconnected, complexsoftware elements that execute multipleworkloads on a common hardware andsoftware infrastructure.•CNF and its pods rely on shared cloudinfrastructure resources to func