Handovers

Physical Channel Reconfiguration

A Physical Channel Reconfiguration can be used for inter-frequency hard handovers and also to change power control algorithm and step size while on a connection (you cannot simply change the DL Channel and Uplink Channel or power control algorithm settings while on a call, you must perform a handover to change them).

You must be on a call to perform a Physical Channel Reconfiguration.

Before executing a Physical Channel Reconfiguration, you must first specify the settings you wish to change (for example, downlink and uplink UARFCNs to which to handover). You must then select Execute Handover ( F5 ) or send the CALL:HANDoff:PCReconfig[:IMMediate] command to initiate the reconfiguration.

Upon completion of the handover (successful or not, and regardless of any errors), the handover settings are copied to their corresponding non-handover parameters (for example, the DL Channel and Uplink Channel settings are set to the value of Handover Downlink Channel (UARFCN) and Handover Uplink Channel (UARFCN) upon completion of the Physical Channel Reconfiguration).

• Handover Downlink Channel (UARFCN)

  This setting determines the downlink channel the UE is instructed to use after completion of the Physical Channel Reconfiguration. See DL Channel for more information.

  GPIB command: CALL:SETup[:PCReconfig]:CHANnel<[:SELected]|:FDD>:DOWNlink .

• You can specify the handover uplink UARFCN in one of two ways:
  • Handover Uplink Channel (UARFCN)

    You can directly set the Handover Uplink Channel (UARFCN) setting to a specific uplink UARFCN value. The UE is instructed to use this uplink channel after completion of the Physical Channel Reconfiguration.

    GPIB command: CALL:SETup[:PCReconfig]:CHANnel<[:SELected]|:FDD>:UPLink[:MCHannel] .

  • Automatic handover uplink channel

    When Handover Uplink Channel is set to Auto , the handover uplink UARFCN is automatically determined by the Handover Downlink Channel (UARFCN) setting. The test set subtracts the frequency separation associated with the handover downlink channel's band from the Handover Downlink Channel (UARFCN) setting, and instructs the UE to use this uplink channel after completion of the Physical Channel Reconfiguration.

    GPIB command: CALL:SETup[:PCReconfig]:CHANnel<[:SELected]|:FDD>:UPLink:CONTrol:AUTO

  See Uplink Channel for more information.

• Handover Band Arbitrator

  When you set Handover Downlink Channel (UARFCN) to a value in Band VI, you must specify whether you want the test set to send a Band V or Band VI Frequency Band Indicator using the Handover Band Arbitrator setting. See Band Arbitrator for more information.

  GPIB command: CALL:SETup[:PCReconfig]:CHANnel:BARBitrator

• Handover UL CL Power Ctrl Algorithm

  This setting determines the closed loop power control algorithm the UE is instructed to use after completion of the Physical Channel Reconfiguration procedure. See UL CL Power Ctrl Algorithm for more information.

  GPIB command: CALL:SETup:CLPControl:UPLink:ALGorithm

• Handover UL CL Power Ctrl Step Size

  This setting determines the power control step size the UE is instructed to use after completion of the Physical Channel Reconfiguration procedure when Handover UL CL Power Ctrl Algorithm is set to One . This setting can only be changed when Handover UL CL Power Ctrl Algorithm is set to One . Also, if Handover UL CL Power Ctrl Algorithm is set to Two , this setting is returned to its default value of 1 dB . See UL CL Power Ctrl Stepsize for more information .

  GPIB command: CALL:SETup:CLPControl:UPLink:STEPsize

• PCR Timing Indication (CFN Handling)

  You can specify whether the UE should maintain or initialise its CFN counter when performing the Physical Channel Reconfiguration. See Timing Indication (CFN Handling) for additional details. Note that 3GPP 25.331 v5.17.0 s8.6.6.28 states that the UE's behavior is undefined if the network sets the Timing Indication IE to Initialise on a non-hard handover (i.e. where the UARFCNs and one or more Primary Scrambling Codes remain unchanged as part of the reconfiguration).

  • Auto: When PCR Timing Indication (CFN Handling) is set to Auto , the Timing Indication information element sent in the Physical Channel Reconfiguration message is set to Initialise if Handover Downlink Channel (UARFCN) and Handover Uplink Channel (UARFCN) are set such that a hard handover will occur (UARFCNs will change). Otherwise, the Timing Indication information element sent in the Physical Channel Reconfiguration message is set to Maintain.
  • Initialise: the Timing Indication information element sent in the Physical Channel Reconfiguration message is set to Initialise.
  • Maintain: the Timing Indication information element sent in the Physical Channel Reconfiguration message is set to Maintain.

  GPIB command: CALL:HANDoff:PCReconfig:CFNHandling .

• RB Test Mode PCR Loopback Messaging State

  You can specify whether the UE loopback is opened and closed as part of a Physical Channel Reconfiguration. This parameter only affects the Physical Channel Reconfiguration procedure when an RB Test Mode call is active (as the loopback is never closed on any other call type).

  • On : The test set sends an Open UE Test Loop message before sending the Physical Channel Reconfiguration message and a Close UE Test Loop message after receiving the Physical Channel Reconfiguration Complete message from the UE.

    Note, opening and closing the UE test loop clears the UE's buffer and resets its loopback delay (see BER Synchronization requirements ).

    Note, if a Close UE Test Loop message is not sent to the UE when establishing an asymmetrical RMC, you cannot send an Open UE Test Loop message as part of the Physical Channel Reconfiguration (see Asymmetric RMC Loopback Messaging ). If RB Test Mode PCR Loopback Messaging State is set to On and Asymmetric RMC Loopback Messaging is set to Off and the current connection is an asymmetrical RMC, the test set will not send the Open/Close UE Test Loop messages.

  • Off : The test set does not send any loopback control messages as part of the Physical Channel Reconfiguration procedure.

  GPIB command: CALL:HANDoff:PCReconfig:RBTest:LMESsaging:STATe

• PCR Activation Time

  This parameter allows you to set the Activation Time that is signaled to the UE in the Physical Channel Reconfiguration message (see 3GPP TS 25.331 s10.3.3.1). Activation Time controls the frame number at which the operation caused by the related message shall take effect (in other words, how long the UE should wait before moving to the new frequency). It can be set between 0 and 255, and indicates the absolute value of the CFN (Connection Frame Number) at which the UE should perform the handover. If set to 0, the Activation Time IE is not sent in the Physical Channel Reconfiguration message.

  For most UEs, an Activation Time of 0 ("now") is appropriate. But for some UEs, the handover will fail if Activation Time is left at its default value of 0, as explained in the following:

  When the test set orders a Physical Channel Reconfiguration, it takes a finite amount of time for the test set to move to and settle at the new frequency. When the Physical Channel Reconfiguration is ordered, most UEs wait a time of T312 at the new frequency before determining that the handover has failed (T312 is signalled by the test set in SIB1 with a value of 5 seconds). If your UE does not wait once moving to the new frequency, the handover may fail. If it does, set the Activation Time as needed to cause the UE to wait until the test set has moved to the new frequency (a setting of 100 (100 x 10 ms = 1 s) is usually sufficient).

  Do not set PCR Activation Time to a value other than 0 unless necessary, as it slows down the handover procedure.

  GPIB command: CALL:HANDoff:PCReconfig:ATIMe

Transport Channel Reconfiguration

The Transport Channel Reconfiguration provides three main functions:

• Switching Between Symmetrical RMCs while on an RB Test Mode Connection
• Changing Parameters that Require Cell Off Operating Mode or Idle Connection Status while on a Connection
• Changing HSPA Parameters that Require Idle Connection Status while on a Connection ( lab application or feature-licensed test application only )

Before executing a Transport Channel Reconfiguration, you must first specify the settings you wish to change (for example, RMC to which to handover). You must then select Execute Handover ( F5 ) or send the CALL:HANDoff:TCReconfig[:IMMediate] command to initiate the reconfiguration.

Upon completion of the Transport Channel Reconfiguration (successful or not, and regardless of any errors), the handover settings are copied to their corresponding non-handover parameters (for example, the Channel Type setting is set to the value of the RB Test Mode TCR RAB setting).

Switching Between Symmetrical RMCs while on an RB Test Mode Connection

The Transport Channel Reconfiguration operation allows you to handover between Symmetrical RMCs while on a Radio Bearer Test Mode call. You must be on a (non-HSDPA/non-HSPA) RB test mode symmetrical RMC connection to perform a Transport Channel Reconfiguration between RMCs.

• RB Test Mode TCR RAB

  This setting determines the symmetrical RMC the UE is instructed to use after completion of the Transport Channel Reconfiguration. See Channel Type for more information.

  GPIB command: CALL:SETup:TCReconfig:RBTest:RAB

Changing Parameters that Require Cell Off Operating Mode or Idle Connection Status while on a Connection

Some Cell Parameters and Uplink Parameters cannot be changed when in Active Cell Operating Mode or while on a connection. The Transport Channel Reconfiguration operation allows you to change some of the key cell and uplink settings while on a connection. The Transport Channel Reconfiguration also allows you to perform an inter-frequency hard handover.

You must be on an RB test mode symmetrical RMC connection (non-HSDPA, HSDPA or HSPA) to change these settings.

• TCR Channel (UARFCN) State

  You can perform a hard handover (change UARFCNs) as part of the Transport Channel Reconfiguration. This allows you to perform a legal timing re-initialised handover (see Timing Indication (CFN Handling) and Current DPCH Offset for more details).

  When TCR Channel (UARFCN) State is set to On , TCR Downlink Channel (UARFCN) and TCR Uplink Channel (UARFCN) are signalled to the UE during the Transport Channel Reconfiguration if either differs from the current UARFCNs. When TCR Channel (UARFCN) State is set to Off , no UARFCN information is sent to the UE.

  GPIB command: CALL:HANDoff:TCReconfig:CHANnel:STATe

• TCR Downlink Channel (UARFCN)

  This setting determines the downlink channel the UE is instructed to use after completion of the Transport Channel Reconfiguration. See DL Channel for more information.

  GPIB command: CALL:SETup:TCReconfig:CHANnel:DOWNlink

  This setting is only applicable when TCR Channel (UARFCN) State is set to On .

• You can specify the handover uplink UARFCN in one of two ways:
  • TCR Uplink Channel (UARFCN)

    You can directly set the TCR Uplink Channel (UARFCN) setting to a specific uplink UARFCN value. The UE is instructed to use this uplink channel after completion of the Transport Channel Reconfiguration.

    GPIB command: CALL:SETup:TCReconfig:CHANnel:UPLink[:MCHannel]

    This setting is only applicable when TCR Channel (UARFCN) State is set to On .

  • Automatic handover uplink channel

    When TCR Uplink Channel is set to Auto , the handover uplink UARFCN is automatically determined by the TCR Downlink Channel (UARFCN) setting. The test set subtracts the frequency separation associated with the handover downlink channel's band from the TCR Downlink Channel (UARFCN) setting, and instructs the UE to use this uplink channel after completion of the Transport Channel Reconfiguration.

    GPIB command: CALL:SETup:TCReconfig:CHANnel:UPLink:CONTrol:AUTO

    This setting is only applicable when TCR Channel (UARFCN) State is set to On .

  See Uplink Channel for more information.

• TCR Band Arbitrator

  When you set TCR Downlink Channel (UARFCN) to a value in Band VI, you must specify whether you want the test set to send a Band V or Band VI Frequency Band Indicator using the TCR Band Arbitrator setting. See Band Arbitrator for more information.

  GPIB command: CALL:SETup:TCReconfig:CHANnel:BARBitrator

• TCR DPCH Bc/Bd Control

  This parameter selects whether the DPCH gain settings signalled to the UE during the Transport Channel Reconfiguration are set manually (using the TCR Manual Uplink DPCH Bc and TCR Manual Uplink DPCH Bd settings) or automatically by the test set (using the RB Test Mode TCR RAB setting). Note that configuring Bc and Bd such that neither is set to 15 is undefined in the standards, and may result in unexpected behavior. See Uplink DPCH Bc/Bd Control for more information about how the test set automatically determines the gain settings.

  You can query the beta _c and beta _d values that the test set will signal to the UE during the Transport Channel Reconfiguration using the CALL:STATus:SETup:TCReconfig:DPCHannel:CBETa? and CALL:STATus:SETup:TCReconfig:DPCHannel:DBETa? commands.

  GPIB command: CALL:SETup:TCReconfig:DPCHannel:BETA:AUTO

• TCR Manual Uplink DPCH Bc

  When TCR DPCH Bc/Bd Control is set to Manual , this parameter controls the uplink DPCCH gain setting (beta _c ) signalled to the UE during the Transport Channel Reconfiguration. Range is 1 to 15 (see 3GPP TS 25.213 s4.2.1.1 Table 1 for a mapping of the signalled values to the resulting quantized amplitude ratios).

  See Manual Uplink DPCH Bc for more information.

  GPIB command: CALL:SETup:TCReconfig:DPCHannel:MANual:CBETa

• TCR Manual Uplink DPCH Bd

  When TCR DPCH Bc/Bd Control is set to Manual , this parameter controls the uplink DPDCH gain setting (beta _d ) signalled to the UE during the Transport Channel Reconfiguration.

  See Manual Uplink DPCH Bd for more information.

  GPIB command: CALL:SETup:TCReconfig:DPCHannel:MANual:DBETa

• TCR Timing Indication (CFN Handling)

  You can specify whether the UE should maintain or initialise its CFN counter when performing the Transport Channel Reconfiguration. See Timing Indication (CFN Handling) for additional details. Note that 3GPP 25.331 v5.17.0 s8.6.6.28 states that the UE's behavior is undefined if the network sets the Timing Indication IE to Initialise on a non-hard handover (i.e. where the UARFCNs and one or more Primary Scrambling Codes remain unchanged as part of the reconfiguration).

  • Auto: When TCR Timing Indication (CFN Handling) is set to Auto , the Timing Indication information element sent in the Transport Channel Reconfiguration message is set to Initialise if TCR Downlink Channel (UARFCN) and TCR Uplink Channel (UARFCN) are set such that a hard handover will occur (UARFCNs will change) or if TCR Default DPCH Offset (DOFF) is set to a value other than the Current DPCH Offset (this latter condition is to maintain backwards-compatibility with earlier releases). Otherwise, the Timing Indication information element sent in the Transport Channel Reconfiguration message is set to Maintain.
  • Initialise: the Timing Indication information element sent in the Transport Channel Reconfiguration message is set to Initialise.
  • Maintain: the Timing Indication information element sent in the Transport Channel Reconfiguration message is set to Maintain.

  GPIB command: CALL:HANDoff:TCReconfig:CFNHandling .

• TCR Default DPCH Offset (DOFF)

  When TCR Timing Indication (CFN Handling) is set to Initialise , the test set includes both the Default DPCH Offset and DPCH Frame Offset information elements in the Transport Channel Reconfiguration message. Both information elements are sent with a value equal to the TCR Default DPCH Offset (DOFF) setting. Note, however, that the resolution of the Default DPCH Offset information element is 512 chips and the resolution of the DPCH Frame Offset information element is 256 chips. Thus, if TCR Default DPCH Offset (DOFF) is set to 3 x 512 chips, for example, then Default DPCH Offset is sent with a value of 3 (x 512 chips) and DPCH Frame Offset is sent with a value of 6 (x 256 chips). Thus, the TCR Default DPCH Offset (DOFF) setting can be used to change the DPCH Frame Offset (tau _DPCH ) to 0, 1, 2, 3, 4 or 5 x 512 chips (or 0, 2, 4, 6, 8, or 10 x 256 chips) while on a connection.

  The Current DPCH Offset result indicates the DPCH Frame Offset currently in use by the test set (for the current operating mode).

  Note, 3GPP TS 25.331 v5.17.0 s8.6.6.28 states that the timing re-initialized reconfiguration required to send the Default DPCH Offset IE must also include a change in UARFCN or Primary Scrambling Code, or the UE's behavior is undefined.

  GPIB command: CALL:SETup:TCReconfig:DPCHannel:DOFFset

• TCR Relative DPCH Frame Offset

  When TCR Timing Indication (CFN Handling) is set to Maintain , the test set sends only the DPCH Frame Offset information element in the Transport Channel Reconfiguration message. The value of the DPCH Frame Offset information element is determined by the Current DPCH Offset and the TCR Relative DPCH Frame Offset setting. The TCR Relative DPCH Frame Offset setting can be used to change the current DPCH Frame Offset (tau _DPCH ) by -256, 0 or +256 chips while on a connection.

  The Current DPCH Offset result indicates the DPCH Frame Offset currently in use by the test set (for the current operating mode).

  GPIB command: CALL:SETup:TCReconfig:DPCHannel:RFOFfset

Changing HSPA Parameters that Require Idle Connection Status while on a Connection

This section is only applicable to the lab application or feature-licensed test application.

Some of the HSPA parameters cannot be changed while on a connection. The Transport Channel Reconfiguration operation allows you to change these parameters while on a connection.

You must be on an HSDPA or HSPA RB Test Mode connection to change these settings using a Transport Channel Reconfiguration.

• TCR DeltaACK

  Controls the DeltaACK value signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:UPLink:DACK

• TCR DeltaNACK

  Controls the DeltaNACK value signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:UPLink:DNACk

• TCR DeltaCQI

  Controls the DeltaCQI value signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:UPLink:DCQI

• TCR Ack-Nack Repetition Factor

  Controls the Ack-Nack Repetition Factor value signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:UPLink:ANACk:RFACtor

• TCR CQI Feedback Cycle (k)

  Controls the CQI Feedback Cycle (k) value signalled to the UE during the Transport Channel Reconfiguration. TCR CQI Feedback Cycle (k) must be greater than or equal to TCR CQI Repetition Factor * 2ms (except for the case when TCR CQI Feedback Cycle (k) equals 0 ms).

  GPIB command: CALL:SETup:TCReconfig:UPLink:CQI:FCYCle

• TCR CQI Repetition Factor

  Controls the CQI Repetition Factor value signalled to the UE during the Transport Channel Reconfiguration. TCR CQI Feedback Cycle (k) must be greater than or equal to TCR CQI Repetition Factor * 2ms (except for the case when TCR CQI Feedback Cycle (k) equals 0 ms).

  GPIB command: CALL:SETup:TCReconfig:UPLink:CQI:RFACtor

The following parameters are only available while on a User Defined HSDPA or HSPA RB Test Mode connection.

• TCR Number of HARQ Processes

  Controls the User Defined Number of HARQ Processes value signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:HARQ:PROCess:COUNt

• TCR UE IR Buffer Allocation

  Controls the User Defined UE IR Buffer Allocation value signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:MS:IREDundancy:BUFFer:ALLocation

• TCR Explicit UE IR Buffer Size

  Controls the User Defined Explicit UE IR Buffer Size value signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:MS:IREDundancy:BUFFer:SIZe[:EXPLicit]

  This setting is only applicable when TCR UE IR Buffer Allocation is set to Explicit .

• TCR Measurement Power Offset

  Controls the Meas Pow Offset value signaled to the UE during the Transport Channel Reconfiguration.

  GPIB commands: CALL:SETup:TCReconfig:MPOWer[:MOFFset] , CALL:SETup:TCReconfig:MPOWer:OFFSet:CONTrol:AUTO , CALL:SETup:TCReconfig:MPOWer:OFFSet:MANual

The following parameters are only available while on an HSPA RB Test Mode connection:

• TCR E-DPCCH/DPCCH Power Offset

  Controls the E-DPCCH/DPCCH Power Offset (DeltaE-DPCCH) signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:EDPCchannel[:DPCChannel]:POFFset

• TCR Reference E-TFCI Power Offsets

  Controls the Reference E-TFCI Power Offsets signalled to the UE during the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:ETFCi:POFFsets:REFerence

• TCR Absolute Grant

  Controls the serving grant that is signalled to the UE during the Transport Channel Reconfiguration. This serving grant is specified in terms of the 3GPP TS 25.321 s9.2.5.2.1.1 Scheduling Grant Table (and is not determined by the 3GPP TS 25.212 s4.10.1A.1 table that is used to communicate absolute grants on the E-AGCH). See Serving Grant for more information.

  Unlike the other Transport Channel Reconfiguration parameters, the value of this setting is not copied to any of the serving grant parameters (such as Single Shot AG or RB Setup AG ) upon completion of the Transport Channel Reconfiguration.

  GPIB command: CALL:SETup:TCReconfig:SGRant:ABSolute[:VALue]

System Handover

This functionality is only available in GSM/GPRS_W-CDMA fast switching test and lab applications.

The System Handover functionality allows you to handover to a GSM voice call from any of the following connection types:

• AMR Setup
• (non-HSDPA/non-HSPA) Radio Bearer Test Mode
• HSDPA Radio Bearer Test Mode with CN Domain set to CS Domain ( lab application or feature licensed test application only )
• HSPA Radio Bearer Test Mode ( lab application or feature licensed test application only )

You must be on one of these types of connections to perform a System Handover.

Before executing a System Handover you must specify the characteristics of the target GSM cell. You must also ensure that the GSM/GPRS format is set to Active Cell operating mode. You must then select Execute Handover ( F5 ) or send the CALL:HANDoff:SYSTem[:GSM][:IMMediate] command to initiate the handover.

Changing any of the GSM cell settings while operating in the W-CDMA format changes the corresponding parameter settings in the GSM/GPRS format of the fast switching application. Presetting the test set while operating in the W-CDMA format will not reset these parameters to their default settings. Presetting the test set while operating in the GSM/GPRS format will reset these parameters to their default values. When operating in the W-CDMA format, these settings are not saved when using the SAVE REGISTERS utility.

• RB Test Mode to GSM Handover Alerting State
  • On: When this parameter is set to On , when performing a handover from (non-HSDPA) RB test mode to a GSM voice call, the UE will ring. You must answer the ring for the connection to be completed and testing to progress (note also that the fast switch between the two applications will not complete until you answer the ring).
    This occurs because the radio bearer test mode connection terminates in the Test Control (TC) protocol entity, rather than the Call Control (CC) protocol entity used for voice communication. Thus, the UE's CC entity is in the idle state. When the handover from RB test mode to GSM voice is executed, the test set first performs the handover in the RR Connected state. If RB Test Mode to GSM Handover Alerting State is set to On , the test set then continues to establish a CC Connection for voice service. As a result, once the test set and UE have transitioned to GSM service, the UE will alert. See System Handover from W-CDMA RB Test Mode to GSM Voice (with RB Test Mode to GSM Handover Alerting State = On) .
  • Off: When this parameter is set to Off , when performing a handover from (non-HSDPA) RB test mode to a GSM voice call, the UE will not ring. When the handover is completed, the connection is left in the RR Connected state. Data loopback (for BER testing) is available in this state, but voice echo is not. See System Handover from W-CDMA RB Test Mode to GSM Voice (with RB Test Mode to GSM Handover Alerting State = Off) .

  GPIB command: CALL:SETup:SYSTem:GSM:ALERting[:STATe] .

• Wait for RLC Ack of Handover From UTRAN

  This parameter controls whether the test set waits for the UE to confirm reception of the Handover From UTRAN Command message before initiating the fast switch to the GSM/GPRS/EGPRS format (see Handover Ladder Diagrams ) or whether it switches immediately upon sending the Handover From UTRAN Command message. By default, the test set does not initiate the switch from the W-CDMA to GSM/GPRS/EGPRS application until it receives an RLC Ack confirming reception of the Handover From UTRAN Command message. To shorten the handover time, some UEs do not send any W-CDMA layer 2 acknowledgments for the handover command. If your UE does not acknowledge the Handover From UTRAN command, you must set Wait for RLC Ack of Handover From UTRAN to Off . Otherwise, the test set will not continue with the handover until it receives the expected acknowledgment, and the handover will fail.

  Setting Wait for RLC Ack of Handover From UTRAN to Off speeds up the System Handover, but is a less robust handover method.

  GPIB command: CALL:HANDoff:SYSTem[:GSM]RLCack:WAIT[:STATe]

• GSM BCC (Base Station Color Code): See

  CALL[:CELL]:BCCode

  Note, you MUST include the mnemonic :GSM at the end of this command, i.e. you must issue the command as CALL:BCCode:GSM.

• GSM NCC (Network Color Code): See

  CALL[:CELL]:NCCode

  Note, you MUST include the mnemonic :GSM at the end of this command, i.e. you must issue the command as CALL:NCCode:GSM.

• GSM Cell Band: See

  CALL[:CELL]:BAND

  Note, you MUST include the mnemonic :GSM at the end of this command, i.e. you must issue the command as CALL:BAND:GSM.

• GSM Broadcast Chan: See

  CALL:BCHannel[:ARFCn]

  Note, you MUST include the mnemonic :GSM at the end of this command, i.e. you must issue the command as CALL:BCHannel[:ARFCn]:GSM.

• GSM Traffic Band: See

  CALL:TCHannel:BAND

• GSM Traffic Channel: See

  CALL:TCHannel[:ARFCn]

• GSM TCH Timeslot: See

  CALL:TCHannel:TSLot

• GSM Logical Speech Channel: See

  CALL:TCHannel:CMODe:LSPeech:CHANnel

• GSM Half Rate Speech Sub Channel: See

  CALL:TCHannel:CMODe:HRSPeech:SCHannel

• GSM MS TX Level: See

  CALL:MS:TXLevel

Soft Handover

This functionality is only available in the lab application. See Soft Handover .

Radio Bearer Reconfiguration

This section is only applicable to the lab application or feature-licensed test application.

The Radio Bearer Reconfiguration allows you to handover from a CS Domain or CS/PS Domain HSDPA RB Test Mode connection or HSPA RB Test Mode connection to a (non-HSDPA/non-HSPA) symmetrical RMC. See CN Domain and the following ladder diagram: Radio Bearer Reconfiguration from CS Domain or CS/PS Domain HSDPA RB Test Mode Connection or HSPA RB Test Mode Connection . The Radio Bearer Reconfiguration also allows you to change many other parameters as part of the reconfiguration.

Before executing the Radio Bearer Reconfiguration, you must specify to which symmetrical RMC you wish to handover, and set any other reconfiguration parameters as desired. You must then select Execute Handover ( F5 ) or send the CALL:HANDoff:RBReconfig[:IMMediate] command to initiate the reconfiguration.

Upon completion of the Radio Bearer Reconfiguration (successful or not, and regardless of any errors), the handover settings are copied to their corresponding non-handover parameters (for example, the Channel Type setting is set to the value of the RB Test Mode RBR RAB setting).

• RB Test Mode RBR RAB

  This setting determines the (non-HSDPA) symmetrical RMC the UE is instructed to use after completion of the Radio Bearer Reconfiguration. See Channel Type for more information.

  GPIB command: CALL:SETup:RBReconfig:RBTest:RAB

• RBR Channel (UARFCN) State

  You can perform a hard handover (change UARFCNs) as part of the Radio Bearer Reconfiguration. The change in UARFCNs is performed as part of the RB Setup portion of the procedure (see Radio Bearer Reconfiguration from CS Domain or CS/PS Domain HSDPA RB Test Mode Connection or HSPA RB Test Mode Connection ). This allows you to perform a legal timing re-initialised handover (see Timing Indication (CFN Handling) and Current DPCH Offset for more details).

  When RBR Channel (UARFCN) State is set to On , RBR Downlink Channel (UARFCN) and RBR Uplink Channel (UARFCN) are signalled to the UE during the Radio Bearer Reconfiguration if either differs from the current UARFCNs. When RBR Channel (UARFCN) State is set to Off , no UARFCN information is sent to the UE.

  GPIB command: CALL:HANDoff:RBReconfig:CHANnel:STATe

• RBR Downlink Channel (UARFCN)

  This setting determines the downlink channel the UE is instructed to use after completion of the Radio Bearer Reconfiguration. See DL Channel for more information.

  GPIB command: CALL:SETup:RBReconfig:CHANnel:DOWNlink

  This setting is only applicable when RBR Channel (UARFCN) State is set to On .

• You can specify the handover uplink UARFCN in one of two ways:
  • RBR Uplink Channel (UARFCN)

    You can directly set the RBR Uplink Channel (UARFCN) setting to a specific uplink UARFCN value. The UE is instructed to use this uplink channel after completion of the Radio Bearer Reconfiguration.

    GPIB command: CALL:SETup:RBReconfig:CHANnel:UPLink[:MCHannel]

    This setting is only applicable when RBR Channel (UARFCN) State is set to On .

  • Automatic handover uplink channel

    When RBR Uplink Channel is set to Auto , the handover uplink UARFCN is automatically determined by the RBR Downlink Channel (UARFCN) setting. The test set subtracts the frequency separation associated with the handover downlink channel's band from the RBR Downlink Channel (UARFCN) setting, and instructs the UE to use this uplink channel after completion of the Radio Bearer Reconfiguration.

    GPIB command: CALL:SETup:RBReconfig:CHANnel:UPLink:CONTrol:AUTO

    This setting is only applicable when RBR Channel (UARFCN) State is set to On .

  See Uplink Channel for more information.

• RBR Band Arbitrator

  When you set RBR Downlink Channel (UARFCN) to a value in Band VI, you must specify whether you want the test set to send a Band V or Band VI Frequency Band Indicator using the RBR Band Arbitrator setting. See Band Arbitrator for more information.

  GPIB command: CALL:SETup:RBReconfig:CHANnel:BARBitrator

• RBR Uplink DTCH RMC CRC Presence

  This setting determines the Uplink DTCH RMC CRC Presence state the UE is instructed to use after completion of the Radio Bearer Reconfiguration.

  GPIB command: CALL:SETup:RBReconfig:DTCHannel:CRC[:PRESence]

• RBR UE Loopback Type

  This setting determines the UE Loopback Type the UE is instructed to use after completion of the Radio Bearer Reconfiguration.

  GPIB command: CALL:SETup:RBReconfig:MS:LOOPback:TYPE

• RBR Uplink Dummy DCCH Data

  This setting determines the Uplink Dummy DCCH Data state the UE is instructed to use after completion of the Radio Bearer Reconfiguration.

  GPIB command: CALL:SETup:RBReconfig:UPLink:DCCHannel:DDATa

• RBR Uplink DPCH Bc/Bd Control

  This parameter selects whether the DPCH gain settings signalled to the UE during the Radio Bearer Reconfiguration are set manually (using the RBR Manual Uplink DPCH Bc and RBR Manual Uplink DPCH Bd settings) or automatically by the test set (using the RB Test Mode RBR RAB setting). Note that configuring Bc and Bd such that neither is set to 15 is undefined in the standards, and may result in unexpected behavior. See Uplink DPCH Bc/Bd Control for more information about how the test set automatically determines the gain settings.

  GPIB command: CALL:SETup:RBReconfig:DPCHannel:BETA:AUTO

• RBR Manual Uplink DPCH Bc

  When RBR Uplink DPCH Bc/Bd Control is set to Manual , this parameter controls the uplink DPCCH gain setting (beta _c ) signalled to the UE during the Radio Bearer Reconfiguration. Range is 1 to 15 (see 3GPP TS 25.213 s4.2.1.1 Table 1 for a mapping of the signalled values to the resulting quantized amplitude ratios).

  See Manual Uplink DPCH Bc for more information.

  GPIB command: CALL:SETup:RBReconfig:DPCHannel:MANual:CBETa

• RBR Manual Uplink DPCH Bd

  When RBR Uplink DPCH Bc/Bd Control is set to Manual , this parameter controls the uplink DPDCH gain setting (beta _d ) signalled to the UE during the Radio Bearer Reconfiguration. See Manual Uplink DPCH Bd for more information.

  GPIB command: CALL:SETup:RBReconfig:DPCHannel:MANual:DBETa

• RBR Timing Indication (CFN Handling)

  You can specify whether the UE should maintain or initialise its CFN counter when performing the Radio Bearer Reconfiguration. See Timing Indication (CFN Handling) for additional details. Note that 3GPP 25.331 v5.17.0 s8.6.6.28 states that the UE's behavior is undefined if the network sets the Timing Indication IE to Initialise on a non-hard handover (i.e. where the UARFCNs and one or more Primary Scrambling Codes remain unchanged as part of the reconfiguration).

  • Auto: When RBR Timing Indication (CFN Handling) is set to Auto , the Timing Indication information element sent in the RB Setup message (sent as part of the Radio Bearer Reconfiguration) is set to Initialise if RBR Downlink Channel (UARFCN) and RBR Uplink Channel (UARFCN) are set such that a hard handover will occur (UARFCNs will change) or if RBR Default DPCH Offset (DOFF) is set to a value other than the Current DPCH Offset (this latter condition is to maintain backwards-compatibility with earlier releases). Otherwise, the Timing Indication information element sent in the RB Setup message (sent as part of the Radio Bearer Reconfiguration) is set to Maintain.
  • Initialise: the Timing Indication information element sent in the RB Setup message (sent as part of the Radio Bearer Reconfiguration) is set to Initialise.
  • Maintain: the Timing Indication information element sent in the RB Setup message (sent as part of the Radio Bearer Reconfiguration) is set to Maintain.

  A timing-maintained Radio Bearer Reconfiguration cannot be performed when compressed mode is enabled.

  GPIB command: CALL:HANDoff:RBReconfig:CFNHandling

• RBR Default DPCH Offset (DOFF)

  When RBR Timing Indication (CFN Handling) is set to Initialise , the test set includes both the Default DPCH Offset and DPCH Frame Offset information elements in the RB Setup message sent as part of the Radio Bearer Reconfiguration. Both information elements are sent with a value equal to the RBR Default DPCH Offset (DOFF) setting. Note, however, that the resolution of the Default DPCH Offset information element is 512 chips and the resolution of the DPCH Frame Offset information element is 256 chips. Thus, if RBR Default DPCH Offset (DOFF) is set to 3 x 512 chips, for example, then Default DPCH Offset is sent with a value of 3 (x 512 chips) and DPCH Frame Offset is sent with a value of 6 (x 256 chips). Thus, the RBR Default DPCH Offset (DOFF) setting can be used to change the DPCH Frame Offset (tau _DPCH ) to 0, 1, 2, 3, 4 or 5 x 512 chips (or 0, 2, 4, 6, 8, or 10 x 256 chips) while on a connection.

  The Current DPCH Offset result indicates the DPCH Frame Offset currently in use by the test set (for the current operating mode).

  Note, 3GPP TS 25.331 v5.17.0 s8.6.6.28 states that the timing re-initialized reconfiguration required to send the Default DPCH Offset IE must also include a change in UARFCN or Primary Scrambling Code, or the UE's behavior is undefined.

  GPIB command: CALL:SETup:RBReconfig:DPCHannel:DOFFset

• RBR Relative DPCH Frame Offset

  When RBR Timing Indication (CFN Handling) is set to Maintain , the test set sends only the DPCH Frame Offset information element in the RB Setup message sent as part of the Radio Bearer Reconfiguration. The value of the DPCH Frame Offset information element is determined by the Current DPCH Offset and the RBR Relative DPCH Frame Offset setting. The RBR Relative DPCH Frame Offset setting can be used to change the current DPCH Frame Offset (tau _DPCH ) by -256, 0 or +256 chips while on a connection.

  The Current DPCH Offset result indicates the DPCH Frame Offset currently in use by the test set (for the current operating mode).

  GPIB command: CALL:SETup:RBReconfig:DPCHannel:RFOFfset

External 8960 Handover

This section is only applicable to the lab application.

You can connect two test sets using an External Device Connection to create a Two-Cell Test System for testing your UE's ability to transition between cells while in idle mode and while actively transferring data.

You must have an External Device Connection between the two test sets to perform the Execute External 8960 Handover immediate action. Also, your UE must have an active PDP context (or simply be attached if your test set is emulating a GSM/GPRS/EGPRS cell), or be actively transferring data (voice, PS data, HSDPA, etc.) before initiating the external 8960 handover.

When the Execute External 8960 Handover action is performed, the originating test set queries the configuration of the destination test set to determine what type of handover/cell reselection to order. Note that while strictly speaking, a handover is the process by which a mobile transitions from one cell to another while maintaining a circuit-switched call, the same Execute External 8960 Handover action is used both to initiate a handover and to perform a network-initiated cell reselection, depending upon the configuration of the two test sets and the UE's current connection state.

Note that the contents of the Handover command (circuit-switched connections) or Cell Change Order (packet-switched connections) sent by the originating test set during an external 8960 handover are not based on the information in its neighbor cell lists; it is strictly based on the configuration of the destination test set. However, it is recommended that you configure the SIB11 Cell Info List to contain the other test set's information. This enables the mobile to measure the other test set before transitioning to it (some mobiles will not perform a "blind" handover) and allows you to view the mobile's measurement reports for the test set.

See Two-Cell Test System for more information on the external 8960 handover.

When performing a circuit-switched handover, you can specify the following setting in the Handover from UTRAN message:

• Activation Time

  This parameter allows you to set the Activation Time that is signaled to the UE in the Handover from UTRAN message (see 3GPP TS 25.331 s10.3.3.1). Activation Time controls the frame number at which the operation caused by the related message shall take effect (in other words, how long the UE should wait before performing the handover). It can be set between 0 and 255, and indicates the absolute value of the CFN (Connection Frame Number) at which the UE should perform the handover. If set to 0, the Activation Time IE is not sent in the Handover from UTRAN message.

  GPIB command: CALL:HANDoff:EXTernal:ATIMe

  This parameter can only be changed when connection status is idle.

Related Topics

How Do I Perform a Handover?

Step 6: Reconfigure Test Set and UE Connection Parameters

CALL:SETup

CALL:HANDoff

Channel (UARFCN) Information

Handover Ladder Diagrams

Troubleshooting Handovers