
However there are standard test cases with all the OEM based on 3Gpp and 3Gpp2 Specification. There are Multiple Test cases designed especially for Lab Testing and Field testing by respective OEM’s. Results from Lab test and Live Network Testing will be different. Lab testing will be used to test the Modem With desired Network Conditions. Note: For Lab Testing, device will have Test SIM and it is connected via RF cable to the simulators. Lab Testing is where the Network is emulated with different PLMN (MCC, MNC) ID using Network simulators like Spirent, R&S, Anritsu, and Agilent. Field Testing will have Live Network Active SIM Card.
#QXDM AND QPST TOOL SOFTWARE#
This stage will be very wide and diversified depends upon OEM, Operators and Platforms.Field Testing will be mostly in live network to test the modem Hardware and Software Performance. etc.) or AT Commands or ADB (Android debug bridge) procedures Also in some Cases Modem will not have any UI (User Interface) and all the testing can be performed with either the specific Tools like (QXDM, XCAL,TEMS. It will have factory installed Software and Hardware version with Simple UI functions. In this Stage the device is called Lunch box because it will have shape of traditional Lunch box. This will be Very first step being Protocol /Modem/Device Test Engineer you will be aware off. The Modem/Device testing for any OEMs will go through the Following Life Cycle: The basic idea is the same but the protocol messages, call flow, processes might vary a little bit between all three technologies.The action may be a Attach procedure, CS/PS call, Paging response, handover or any other scenario imaginable that a device might have to execute to perform a particular action. Call flow doesn’t just mean Voice (CS) call, it is a systematic sequence of steps the Device (Sometimes called UE) needs to follow in order for it to perform any kind of action on the network.If a device fails a test a first hand analysis of the issue needs to be done to find out the root cause of the fail. Each company which has a modem has its own proprietary logging tool for example Qualcomm’s QXDM. While testing the device for conformance, the device’s logs are also being recorded. A device test Engineer’s responsibility is not to just execute the test cases but also to do a first hand analysis.What if the device doesn’t pass these tests? Every device that has been released into the market has passed these tests before being released. Every network has a document which consists of a huge set of tests that the device needs to pass in order for it to qualify to be released on to the network. The most important use is to do conformance tests on devices.

We can also vary the different parameters affecting the device in the real world like SINR, RSCP, handover, etc. These call boxes are directly connected to devices which helps overcome interference from other users.

Usually the tests performed under sanity are : CS (Voice) call setup/end – Mobile Originated/Mobile Terminated, CS call maintenance (MO/MT) PS (data) throughput tests, Multi-RAB tests (CS+PS), SMS, MMS, Manual/Automatic network selection, Sleep mode (LP0) tests and flight mode tests among a few others.
