• No se han encontrado resultados

2. Calabazas Cucurbita moschata

2.3. Evaluación de la vida útil

RF testing is on-target testing (i.e., it is performed with the PRL loaded in one or more handsets). Handsets are tested in a simulated RF environment. A typical set up and flow of a lab test of a PRL is shown in Figure 8-1.

The RF environment is created by use of one or more base station emulators (BSE) configured to a particular technology, band-class, channel and SID/NID combination using the technical data from which the PRL was constructed.

Figure 8-1 PRL Lab Test Environment

The BSE is configured according to the technology, band-class and channel to be simulated (from information in the TDS). The handset is loaded with the PRL under test; the handset is also connected to a logging tool (such as QUALCOMM CDMA Air

Interface Tester (CAIT)). The logging tool will show the over-the-air messages indicating the selected network. If CAIT is used and the device is a QUALCOMM MSM-based device that has not had debugging information disabled by the manufacturer, debug messages can be examined to show the system acquisition progress.

8.3.1 BSE Requirements

The base station emulator should support IS-95/2000 and IS-856 (EV-DO) operation and should allow the configuration of overhead channel messages. Ideally it should support multiple sectors of 1x/IS-95 and 1X-EvDO (optional). It should have a radio network simulator capable of operating at 800 MHz and 1900 MHz and radiating sufficient amounts of power to provide a good coverage and be able to demodulate the reverse link (RL) from the mobile station in a good coverage environment. To simulate scenarios such as losing a system an emulator should have an ability to vary the transmitted signal power.

In order to test the PRL and simulate different markets, the BSE should have

configurable network settings such as the technology, band-class, channel, the SID/NID and any required overhead messages.

There are a number of suppliers of commercial or base station simulators, examples are the Racal Instruments, Spirent, Agilent Technologies and Anritsu.

8.3.2 PRL Test Scenarios

There are multiple scenarios under which a PRL may be tested. The level of test to be performed would be chosen based on the changes in the PRL being tested. PRL test scenarios include:

ƒ

Initial acquisition

ƒ

Reselection

ƒ

System loss

ƒ

System avoidance

ƒ

Handset system preferences settings

ƒ

No selectable network

ƒ

Emergency service on an available system 8.3.2.1 Initial Acquisition

The purpose of an initial acquisition test would be to verify that power-up acquisition is based on the normal scan list. The normal scan list is based on:

Recent channels: Sometimes known as the most recently used (MRU) list or as

the recent channel list (RCL).

ƒ

Acquisition Table: An implicit statement acquisition table is that the order in

which channels appear is the order into which they are entered in to the scan list. Section 5.3.2 describes initial acquisition. The test equipment (BSE) should broadcast on multiple sectors, as appropriate, with combinations of SID and NID and channels of roaming partners in the same market and/or GEO.

This test should verify, for a given radio environment, that service should be provided on the most preferred system available. The results of this test should show that initial acquisition occurred as expected in the following scenarios

ƒ

Service on most preferred system in a GEO

ƒ

Service on a less preferred system in a GEO

ƒ

Service on an available system

ƒ

Dual band device

ƒ

Acquisition on every preferred system record in the system table

ƒ

No service on a negative system 8.3.2.2 Better Service Reselection

The objective of a reselection test is to verify reacquisition of a more preferred system. Section 5.3.5 describes better service reselection, which, when served by a less preferred system, tries to obtain better service based on a reselection scan list of

channels of systems in the same GEO. A better service reselection test should configure the test environment to verify that

ƒ

Most preferred system acquired on rescan

ƒ

More preferred system acquired, when most preferred is not available

ƒ

Only available system found on rescan where the PRL permits service on available systems

8.3.2.3 System Loss

The objective of the system loss tests would be to verify reacquisition after network loss. Section 5.3.7 describes system loss reselection based on the system lost scan list. The scan is punctured on a time-based schedule with the system that was lost (it would be important to understand which schedule applied before any verification). A system loss test would, through appropriate configuration of the test environment (based on the TDS information), verify that:

ƒ

A lost system is reacquired

ƒ

The most preferred system - same GEO, acquired

ƒ

Most preferred system - another GEO, acquired

ƒ

Less preferred system - another GEO, acquired

ƒ

Available system acquired 8.3.2.4 System Avoidance

The objective of such a test would be to verify avoidance of unusable systems. Section 5.3.4 describes an unusable system in terms of system determination. A system

avoidance test would, through appropriate configuration of the test environment (based on the TDS information), verify that, when any one of the avoidance conditions occur, there is an avoidance timer which is set (this timer varies between 30 to 60 seconds)

and that the system is avoided. Avoiding a system does not imply that system is re- acquired after avoidance timer expires it just means that it is eligible to be scanned again. The avoidance timer can be understood to be a flag set to skip the channel during the normal scanning process. After the avoidance timer expires, the channel can now be scanned during the next scanning schedule. The following conditions would need to be created to test for system avoidance:

ƒ

The supported protocol level does not provide a match to the protocol revision of the handset i.e. a P_REV mismatch. Could occur for Mobile P_Rev Max=5 and base station P_Rev Min=6 (Typical avoidance time = 60 seconds)

ƒ

The registration is rejected by the serving system. (Typical avoidance time = 30 seconds)

ƒ

The handset exceeds the maximum number of access attempts (probes) without success

ƒ

The Sync Channel is acquired but not Paging Channel

ƒ

The overhead messages do not provide the handset the information or

configuration to operate correctly (i.e. bad overhead messages). For the purposes of testing, a bad overhead message condition can be mimicked by:

- Sending a global service redirect to a ‘non-broadcasting’ frequency with the return if fail flag (RIF) set to ‘don’t come back’ (0). (Typical avoidance time = 30 seconds).

- The setting of the persistence values (PSIST (0-9)) in the Access Parameters Message to a value of 63. (Typical avoidance time = 60 seconds.)

8.3.2.5 Handset Preferences

As section 5.1.1detailed, there are handset preferences that can affect the behavior of the PRL and system selection. A lab test suite may include testing PRL behavior for these settings, as appropriate. Such test may include:

ƒ

Mode preference: Setting to digital only or automatic. This only affects PRLs with

AMPS systems

ƒ

Roam preference: A setting of ‘Home Only’ to verify that service is not provided

on SIDs that are not defined as HOME SID. (See section 5.3.8.) A setting of ‘Automatic’ to verify that service is provided on all preferred SIDs.

8.3.2.6 No Selectable Network

As section 5.3.11 describes, when there is no CDMA system present: MS will keep searching for 10 -15 minutes and then go into power-save mode to minimize battery life.

8.4 Field Testing

Documento similar