Field Testing

Field testing is performed to ensure the device is built to standardized specifications by validating the device hardware and software. A few of the things this involves are checking basic features like Call performance (monitor point and monitor route testing), interoperability testing and re-testing in different fields.

Field Testing Considerations & Logistics

• On- and Off-Site Carrier testing
• Call Hand off
• Interoperability and compatibility testing
• Inbound/Outbound Voice Call
• GPRS
• SMS/MMS
• Multimedia Application Usage
• Enterprise Settings Checkpoints

Live Network Field Trials & IOT

• Field Testing is carried out with the product connected to a live network in real conditions. Field trials give confidence in end to-end product performance. This highlights software quality and stability issues and how the product performs for the customer. This testing can be carried out to customer-specific requirements, network operator requirements or to the GCF field trial recommendations.

Test Case provided by:

• OEM/ODM
• Operator Acceptance
• User Acceptance (UAT)

Features Tested in a Field Trials

Some of the features tested in a field trial are:

• Cell selection and reselection
• Network selection
• Location updating
• Speech quality (FR / HR / EFR, AMR)
• Roaming
• Hand over (GSM/GPRS)
• Signal strength
• Routing area updates for GPRS
• GPRS attach and detach
• GPRS PDP activation and deactivation
• Verification of different QOS Parameters.
• TCP/IP traffic (UL/DL) with different Multi slot configurations
• GPRS Authentication

Field Test Preparation

• Field test objective definitions (Performance Test: RF Drive test, Call Test )
• Diagnostic monitor
• Laptop computer
• Test and reference mobiles, chargers, extra batteries, etc.
• Mass storage device
• GPS receiver ( For guided RF Drive Test , normally applicable to typical topographies)
• Data/RF cables
• Dual UART for data testing
• Extension cord (s)
• USIM/ RUIM card reader/writer along with its software (for RUIM-capable mobiles)

Field Testing Tools

Phone Flashing Tool:

• Generally these tools are used to download or upgrade the software in phone using desktop/laptop with the help of data cables.

Logging/Tracing Tool:

• Tracing tool are used to capture the message of device, exchanged between the different layer and
• with network while in operation .This help in debugging the errors and problem with the device or network.

DUT and reference device:

• During a testing phase of a device there should be a reference model for benchmarking and comparing the performance of the DUT.

Engineering Mode:

• Engineering Mode is designed to allow a field engineer to view and test the network information received by a handset, when the handset is either in idle mode or dedicated mode (that is: with a call active). In each mode, the engineer is able to view network interaction for the “serving cell” (the cell the handset is currently registered with) or for the neighboring cells. Test cases:
• Test Case of OEM/ODM (Open Market)
• Test Case Operator Acceptance (operator specific)

QM Management tool:

• Web based Defect tracking tool, Repository & Centrally Controlled Tool
• Organize & Manage all Phases of Testing Process
• Specifying Testing Requirements
• Planning Tests
• Executing Tests
• Tracking Defects (e.g.. Test Director)

Test Environment

Dense Urban

• Dense urban environments consist of lots of multi paths, and 4-, 5-, and 6-way handoffs are highly visible. Also, the network is usually loaded.

Urban

• Urban environments also have enough multi paths to test 3-, 4-, 5-, and 6-way handoffs. The network is usually loaded, as well.

Suburban

• There are some multi paths present in suburban environments, but not a lot. Usually, 1- or 2-way handoffs are normal, and the network is lightly loaded. The mobile may not be locked to one active Pilot in traffic.

Stationary Environment (MP)

• Stationary environments can be divided into near, middle, and far scenarios.
• Good (near) coverage area, Rx -70 dBm or better
• Medium (middle) coverage area, Rx -70 to -85 dBm
• Poor (far) coverage area, Rx -85 to -103 dBm
• Most mobile feature and conformance testing is done in a good
• GSM/WCDMA coverage area.

Moving Environment (MR)

• Moving environments are very dynamic, and most mobile field testing is carried out in moving conditions.
• 25–45 km/h
• 45–65 km/h
• 65–100 km/h
• Variable speed

Drive test Route Selection

Test Route

• A test route is a prescribed traveling/driving route in a GSM/CDMA/WCDMA coverage area used for field testing in a real, dynamic RF environment.
• Depending on the feature being tested and the test equipment involved, the test route can be walked.

The test route plays a key role in field testing.

• Most field testing of network features can be performed in a stationary location in a good GSM/CDMA/WCDMA coverage area.

A drive route may consist of, but is not limited to, these features:

• Various received signal strengths along the drive route (coverage areas)
• Known cell site locations
• Soft/softer handoff areas
• Boundaries of hard handoff, idle handoff, SID/NID, Zone and IP registrations, etc.
• Various vehicle speeds along the drive route (stop signs, intersections, freeways, boulevards, etc.)
• Single- and dual-mode areas, CDMA ,GSM,WCDMA, etc.
• GSM, CDMA,WCDMA boundaries and vice versa

Quality of Service Testing

Network Services are considered end-to-end, this means from a Terminal Equipment (TE) to another TE. An End-to-End Service may have a certain Quality of Service (QoS) which is provided for the user of a network service. It is the user that decides whether he is satisfied with the provided QoS or not. To realize a certain network QoS a Bearer Service with clearly defined characteristics and functionality is to be set up from the source to the destination of a service. A bearer service includes all aspects to enable the provision of a contracted QoS. These aspects are among others the control signaling, user plane transport and QoS management functionality.
Measuring Voice and Data Service Quality
Traditionally, wireless operators have used a number of metrics that collectively provide a measurement of network service quality from the user perspective. Various operators may define and measure network performance somewhat differently, but overall service quality will generally be determined by a combination of the following four key performance indicators (KPIs).

• System coverage
• Call blockage
• Voice quality
• BER bit error rate