Thank you for Subscribing to Telecom Business Review Weekly Brief
Telecom Business Review | Wednesday, April 19, 2023
Testing 5G networks would be nearly as complicated as developing the network itself. This is due to its wide range of use cases, support for millimeter wavelengths, extremely high throughput, ultra-low latency, etc. Undoubtedly, a one-size-fits-all approach will only work with 5G.
Fremont, CA: Mobile phones were always the primary network-connected devices until 4G. This will drastically alter with 5G.
In contrast to 4G, 5G's influence extends beyond the telecom sector to a wide range of industry sectors. Every gadget in the homes, practically every machine in our industries, automobiles, robots, and medical equipment will connect to the network in the not-too-distant future.
Stay ahead of the industry with exclusive feature stories on the top companies, expert insights and the latest news delivered straight to your inbox. Subscribe today.
Testing 5G networks would be nearly as complicated as developing the network itself. This is due to its wide range of use cases, support for millimeter wavelengths, extremely high throughput, ultra-low latency, etc. Undoubtedly, a one-size-fits-all approach will only work with 5G.
5G complexity is a gift in disguise since it gives vendors and CSPs a chance to develop new testing and assurance methods while also evolving their current testing procedures. CSPs will need to stand out from the competition. They by using faster and more effective testing techniques. It is challenging to validate a 5G network for quality user experience because of 5G's service-based design and many use cases. To ensure quick time to market for products and win the 5G race for CSPs and suppliers, the test approach must be overhauled.
With 3G and 4G, testing the latest features, throughput needs, radio circumstances, handovers, etc., was traditionally the major priority.
Testing was mainly conducted using test tools that replicate or imitate a small number of UEs up to hundreds of UEs.
When a product was provided to a CSP, vendors used to perform stability, capacity, RF-based, and other tests. The CSP then performed drive, scenario, and radio antenna calibration tests before the products (RNC and eNodeb) were placed in the network. Bugs were corrected in the upcoming product edition, or if too severe, in a matter of days. This was based on problems discovered during network testing.
This is a suggested plan for telecom operators to ensure they deploy 5G services more quickly and with bug-free software:
Use case-driven testing techniques
Identifying the most relevant use cases and sectors is critical, given the hundreds of use cases and tens of industries now on the 5G radar. The test approach should be built on the top 10-15 use-case scenarios CSPs have modeled. Different test architectural requirements are needed for 5G use cases. These include high throughput, sub-millisecond latency, enormous IoT connectivity, remote surgery, and enhanced video capabilities.
Analytics-driven automation
Automation is required for 5G compatibility issues and assurance. One key use case for 5G is network slicing. Slices will be made, consumed, and destroyed on demand. Also, depending on the use and requirements, portions can only be formed for a short time (a few seconds to a few hours). Only automation makes it feasible to control such dynamic behavior. Automation based on analytics and machine learning is essential for testing and deploying 5G systems. This is because changes will occur quicker than humans can grasp. Automation should be set up such that test systems automatically recommend remedial measures if the System Under Test (SUT) is about to fail, have large alarms, or have service degraded.
Continuously everything
Continuous connectivity isn't simply a technical cliché for 5G; it is perhaps the most significant transformation that telecom suppliers and operators must embrace as they enter the next decade. A DevOps-based strategy with continuous testing, integration, and deployment across the lifecycle is required for 5G's unparalleled complexity. In this fast-paced DevOps era, static test methodologies will no longer be effective.
Deploying test libraries and APIs based on microservices will enable quicker and more flexible integration with upcoming releases and products from various suppliers. Continuous integration test suites and use cases would be dynamic and updated regularly.
Optimizing the legacy testing framework
The 3G/4G legacy testing framework may be improved to interact with the upcoming 5G test framework, providing legacy, inter-RAT, and inter-system handover testing scenarios. For faster resolution of issues discovered when testing the System Under Test, the current debugging and logging mechanisms must also be improved. The end-to-end (E2E) debugging of complete network simulation and real network testing will be significantly enhanced by a consistent logging system across all test tools, including functional, load, performance, and RF tools.
More in News