Q-DAAT is a family of automated testing tools for data related testing of mobile handsets and devices.  Operators and Device manufacturers run Q-DAAT to verify data processes, calculate data throughput, and monitor overall data performances in an ongoing effort to enhance data devices.

Q-DAAT provides automated testing tools for Live and Emulated network environments.  The automation scripts simulate users accessing the data features and functions available on the mobile device.  The test systems monitor data throughput, OTA messages, and IP packets to ensure the device is performing up to the required specifications.  Reports generated by Q-DAAT provide extensive results that can be analyzed and evaluated by the user to verify data functionality of the mobile devices.

Q-DAAT™ system setup for data throughput testing

The Q-DAAT test suites include:

• A12–  Data Authentication
• DT-MAX – Data Throughput (1x, EVDO Rev 0, Rev A)
• MIP/DMU – Mobile IP/Dynamic Mobile IP Key Update
• OTADM – Over The Air Device Management
• OTADM Firmware Package Verification
• DM Logging – Diagnostic Message Log Analysis
• FV – Feature Validation
  

A12  Data Authentication

The A12 automated test solution was developed in response to a need to test A12 authentication in emulated mode.  The test plan calls for lab testing in an emulated network environment. The automated solution allows testing for both Alcatel-Lucent and Nortel infrastructure implementations.

DT-MAX

Delivery of higher data rates for data transmission on mobile devices is a key strategy for carriers and device manufacturers. To support the growing need to test these devices, w2bi created DT MAX, a standalone application that provides a fully automated testing environment for data throughput testing of 1x and EVDO devices. The test environment supports device interface via USB/Modem connection for tethered mode and IR, Active Sync & Network Sharing connection for non-tethered mode. HTML and Excel logs provide both summary and detail test results. The test suites run on an emulated network using the Spirent and Anritsu emulators.

Spirent (1x, EVDO Rev 0 & Rev A) Supported Devices Supported Connection Tethered Non-tethered Feature Phones √   Data Cards √   Smart Phones √ √**

Anritsu (1x, EVDO  Rev 0 & Rev A*) Supported Devices Supported Connection Tethered Non-tethered Feature Phones √   Data Cards √   Smart Phones √ √**

*   Anritsu solution available for Rev A now, 1X and Rev 0 planned for Q2, 2008
** Availability of Rev A for Smart Phones to be announced

MIP/DMU

Support for data transmission on mobile devices is a key strategy for carriers. In support of this, carriers are deploying Mobile IP (MIP) with optional support for Dynamic Mobile IP Key Update (DMU) procedure within  1x and 1xEV-DO network.

To meet the needs of live network Mobile IP testing, w2bi created Q-DAAT MIP/DMU a standalone application which implements emulated and live network tests. These can be run either in  lab or in field testing operations. In addition to execution of  test procedures, the application captures both over the air messages and data packets. This information is correlated, decoded and presented to the user along with standard test results. The packet data provides a deeper insight into the interaction of the device with the network, and provides vital information for root cause analysis when test failures are encountered.

When first executed, the application allows the user to configure the test unit with all parameters needed to execute the test scripts. The user executes the test scripts either as a group or individually.

Tests can be performed on tethered or non-tethered devices and cover PPP negotiation, PAP/CHAP authentication,  MIP registration/re-registration, SIP/MIP fallback, DMU Key updates, Inter/intra PDSN handoffs, as well as inter-technology handoffs (1x-EVDO).

OTADM

The Q-DAAT - Over The Air Device Management (OTADM) test suite enables automated performance testing of OTADM in an emulated environment. During a wireless device over the air firmware update, the messages and firmware downloads are initiated and processed in several ways. Testing for correct device performance in live network environment is challenging, particularly for test scenarios which require a download interruption due to a network or a device initiated event. For example, a handoff to a roaming partner during download is a significant challenge to reproduce in the live network. 

Verizon Wireless recently developed and certified a manual test plan for emulated network operation. w2bi’s OTADM automates execution of the test plan, and integrates all the required components under the Q-DAAT execution environment including Spirent 1X emulators, EVDO network emulators, and OMASS (OMA Server Simulator) server.  An OTADM programmable vDC power supply, for handset battery elimination, is available to emulate varying battery charge levels during FOTA testing, with impact measurement results provided by OTADM.

Additionally, OTADM provides OCR (optical character recognition) technology to facilitate device display message analysis, further simplifying the Testers set-up and execution of the automated tests.

A companion suite, OTADM Firmware Package Verification, allows testing the update packages in the emulated environment before releasing into the live network.

DM Logging

The Diagnostic Message (DM) Log Analysis test suite enables testing for performance impact based on diagnostic logging. During wireless device testing, OTA messages are logged using various tools such as CAIT and UDM to help debug failures and augment test results. Although logging and log messages provide support during testing, these processes place additional load on the wireless device’s processor and operating system. This in turn can degrade the device’s performance. Thus, to understand the true performance of a wireless device, it is imperative to assess and understand the impact of logging. 

DM Log Analysis evaluates two aspects of the DM operation. First it measures the impact of logging on the wireless device features and functions performance. Second, if the required log messages available for each tested feature and function when logging is enabled.

Feature Validation: Regression testing takes place after a device undergoes changes to software or hardware that does not require a complete retesting of the device. Feature Validation checks the device’s major functions to ensure that minor changes to software or hardware intended to fix or improve a particular function have not impacted key functional areas.