Ensuring compliance with 5G network deployment of MNOs
Verifying device interoperability and performance with mobile network operators (MNOs) network configuration requires running RF / RRM tests to validate carrier acceptance requirements. The tests expand the scope of compliance testing with certifications held by third parties such as the Global Certification Forum (GCF) and PCS Type Certification Review Board (PTCRB) and aim to invest additional testing efforts to ensure that the device meets quality expectations in specific MNO network deployments. There are typically two reasons MNOs add test cases to their supplementary test plans. In the first case, global certification groups such as GCF must balance the testing depth and test time or cost. In the second case, 3GPP may not complete test cases for a specific feature in a timeframe that coincides with MNO rollout plans.
MNOs can add those tests to their certification programs later. Test engineers need an integrated solution that enables RF performance testing of 5G devices against MNO-defined test specifications across frequency range 1 (sub-6 GHz) and frequency range 2 (millimeter-wave or mmWave). They must select and order the tests they need to run, perform the actions when prompted, or automate them using automation tools. Viewing the signaling trace during the test execution saves time by uncovering issues early. Once the results are available, test engineers can use the log files to troubleshoot issues. The ability to filter test information helps identify and resolve issues faster. The solution’s architecture must allow support for future requirements as well.
5G RF / RRM carrier acceptance test solution
Ensuring the performance of a mobile device requires running RF / RRM tests. The Keysight RF / RRM carrier acceptance solution provides comprehensive access to RF / RRM carrier acceptance test plans mandated by the world’s major 5G mobile network operators. The toolset addresses a wide range of test scenarios in sub-6 GHz and mmWave frequencies for both non-standalone and standalone modes. The solution’s architecture supports future requirements as they become available.
