UE Category Parameters

 
•  UE HS-DSCH Category Control

   If UE HS-DSCH Category Control is set to Auto , the UE category in use by the test set ( Current UE HS-DSCH Category ), is equal to the UE Reported HS-DSCH Category if the category reported by the UE is valid. Otherwise, if the UE reported an invalid category or did not report a category, the Current UE HS-DSCH Category is equal to the Manual UE HS-DSCH Category setting.

   If UE HS-DSCH Category Control is set to Manual , the UE category in use by the test set ( Current UE HS-DSCH Category ), is equal to the Manual UE HS-DSCH Category setting.

   GPIB command: CALL:HSDPa:MS:HSDSchannel:CATegory:CONTrol:AUTO

   This parameter can only be set when the data/call status is Idle .

•  Manual UE HS-DSCH Category

   This setting determines the UE category in use by the test set ( Current UE HS-DSCH Category ) when UE HS-DSCH Category Control is set to Manual or if the UE Reported HS-DSCH Category is invalid.

   GPIB command: CALL:HSDPa:MS:HSDSchannel:CATegory:MANual

   This parameter can only be set when the Data/Call Status is Idle .

•  Manual UE DC-HSDPA HS-DSCH Category

   This parameter is only used when DC-HSDPA is active. You can set HS-DSCH category for DC-HSDPA capable UEs when UE HS-DSCH Category Control is set to Manual or if the UE Reported HS-DSCH Category is invalid.

   GPIB command: CALL:HSDPa:MS:HSDSchannel:CATegory:DCHSdpa:MANual

•  Manual UE MIMO HS-DSCH Category

   This parameter is only used when MIMO is active. You can set HS-DSCH category for MIMO capable UEs when UE HS-DSCH Category Control is set to Manual or if the UE Reported HS-DSCH Category is invalid.

   This parameter can only be set when the Data/Call Status is Idle .

   GPIB command: CALL:HSDPa:MS:HSDSchannel:CATegory:MIMO:MANual

 The UE category currently in use by the test set is reported by the Current UE HS-DSCH Category result.

 

 MAC-hs Parameters

 The test set schedules new blocks and retransmissions based on the acknowledge/negative acknowledge (ACK/NACK) information on the uplink HS-DPCCH. If a NACK is received and the block has not been transmitted more than the Number of Transmissions setting allows (and if the TSN to be transmitted is within the transmit window, see MAC-hs Window Size ), the HARQ process retransmits the block using the next redundancy version (RV) from the RV Sequence list. If a NACK is received and the block has been retransmitted the maximum number of allowed times (or if the TSN lies outside the transmit window), or if an ACK is received, the MAC-hs layer transmits a new block using the first RV in the list. If the expected HS-DPCCH transmission is not received on the uplink at the appropriate time, the test set reacts according to the statDTX Reception Behavior setting. The test set records the number of ACKs, NACKs, and statDTXs and displays them in the HSDPA Information window and reports them to the HSDPA BLER measurement (see HSDPA Block Error Ratio Measurement Description ).

 
•  Number of Transmissions

   The number of times a MAC-hs HARQ process will attempt to transmit a particular data block (one to eight).

   GPIB command: CALL:HSDPa:MACHs:NTRans

•  RV Sequence

   As described in 3GPP TS 25.212, the RV parameter controls exactly which bits are transmitted to the UE (i.e. the systematic bits versus the convolutionally coded bits) and for 16QAM modulation, which symbols are mapped to which modulation points when the Current MIMO Configuration State is Inactive . By selecting a different RV each time a block is retransmitted, the network increases the chance that the turbo decoder in the UE will be able to recover the original block. Alternatively, the network can use the same RV for each retransmission and the UE uses chase combining on the received bits to increase the likelihood of receiving the block correctly.

   The RV Sequence setting indicates the sequence of RV parameters to be used by the test set for block transmissions. You may specify up to eight integer values (between zero and seven), but the number of RV parameters actually used by the test set is determined by the Number of Transmissions setting (the RV parameters at the end of the sequence are not used if the Number of Transmissions setting is less than the number of RV parameters in the sequence). If you enter fewer than eight values for the RV sequence, the test set fills the remaining values with zeroes. The default RV sequence matches 3GPP TS 34.121 s9.2.1.

   GPIB command: CALL:HSDPa:MACHs:RVSequence

•  RV Sequence for MIMO Primary Transport Block

   When the Current MIMO Configuration Status is Active , this parameter specifies the RV Sequence used for each transmission of a particular primary transport block.

   GPIB command: CALL:HSDPa:MACEHS:PTBLock:RVSequence

•  RV Sequence for MIMO Secondary Transport Block

   When the Current MIMO Configuration State is Active , this parameter specifies the RV Sequence used for each transmission of a particular secondary transport block.

   GPIB command: CALL:HSDPa:MACEHS:STBLock:RVSequence

•  MAC-hs Window Size

   MAC-hs Window Size can be set to 4, 6, 8, 12, 16, 24, or 32. In accordance with 3GPP TS 25.321 11.6.2.3.2, the test set will not retransmit a block with a TSN that is outside the transmit window. This parameter sets both the MAC-hs transmit and receive window sizes.

   GPIB command: CALL:HSDPa:MPOWer:OFFSet:MANual

   This parameter can only be set when the data/call status is Idle .

•  MAC-hs T1

   This parameter controls the value of the MAC-hs T1 timer that is signaled to the UE in the Radio Bearer Setup message. 3GPP TS 25.331 s10.3.5.1a defines T1 as "Timer (in milliseconds) when PDUs are released to the upper layers even though there are outstanding PDUs with lower TSN values."

   The behavior of T1 (the "re-ordering release timer") is defined in 3GPP TS 25.321 s11.6.2.3.

   GPIB command: CALL:HSDPa:MACHs:T1

   This parameter can only be set when the data/call status is Idle .

•  statDTX Reception Behavior

   You can configure how the test set responds to a statDTX from the UE (the options are as defined in 3GPP TS 34.121 Table 9.2.1.2). When the Current MIMO Configuration Status is Active , this parameter also applies to the case when one transport block was scheduled.

   
  • Handle as ACK

     When statDTX Reception Behavior is set to Handle as ACK , when a statDTX occurs, the test set transmits a new block from the MAC-hs transmit queue using the first entry in the RV Sequence and resets the transmission counter to one.

     Note, if you would like the test set to continuously transmit a stream of new (PRBS) data regardless of the uplink HS-DPCCH presence (to allow you to measure BER in an external program, for example), set statDTX Reception Behavior to Handle as ACK , set Number of Transmissions to 1 , FDD Test "HS-DSCH Data Pattern" to CCITT PRBS15 or CCITT PRBS9 , and MAC-hs Header to Data .

  •  Handle as NACK

     When statDTX Reception Behavior is set to Handle as NACK , when a statDTX occurs, if the transmission counter is less than the Number of Transmissions setting, the test set transmits the same block using the next entry in the RV Sequence and increments the transmission counter by one. If the transmission counter equals the Number of Transmissions setting, then the Handle as ACK process is followed instead.

  •  Handle as statDTX

     When statDTX Reception Behavior is set to Handle as statDTX , when a statDTX occurs, the test set transmits the same block using the same entry in the RV Sequence and does not increment the transmission counter.

     Note that when statDTX Reception Behavior is set to Handle as statDTX , if the UE never transmits an ACK or NACK, the test set will continuously transmit the same block (even if you change HS-DSCH Data Pattern ).

   GPIB command: CALL:HSDPa:MACHs:SDTX:RBEHavior

•  statDTX Reception Behavior for Two Trans Blks

   When the Current MIMO Configuration Status is Active , you can configure how the test set responds to a statDTX from the UE when two transport blocks were scheduled.

   GPIB command: CALL:HSDPa:MACEHS:DTBLocks:SDTX:RBEHavior

 

 MAC-ehs Parameters

 
•  MAC-ehs Segmentation Strategy

   This setting specifies the segmentation strategy at the MAC-ehs layer in Active Cell mode.

   The following settings are available:

   
  • Standard : Segmentation at the MAC-ehs layer is done as required to fit as many re-ordering SDUs as possible into the MAC-ehs PDU.
  •  Minimum : Segmentation at the MAC-ehs is avoided as much as possible. The test set fits as many re-ordering SDUs as possible into the MAC-ehs PDU. Each of the SDUs contains only a single complete MAC-d PDU. However, if the MAC-ehs PDU size is smaller than the MAC-d PDU size, segmentation is performed.

   This parameter can only be set when call status is Idle .

   GPIB Command: CALL:HSDPa:MACEHS:SEGMentation

 

 Secondary Serving Cell Parameters

 

•  Dual Carrier Band Configuration

   The parameter  specifies whether the primary and secondary serving cell downlink UARFCN should use UARFCNs in the Single Band or Dual Band or any customized band.

   This parameter can only be set when the Data/Call Status is Idle .

   GPIB Command: CALL:HSDPa:MCARrier:BAND:CONFig[:TYPE]

 

•  Secondary Serving Cell Power

   The parameter Secondary Serving Cell Power State sets the state of the secondary serving cell power. This parameter only affects the power of the DC-HSDPA secondary serving cell while a DC-HSDPA call is established, it does not affect whether the UE is told to enable DC-HSDPA or not. When the Secondary Serving Cell Power State is set to ON, the parameter Secondary Serving Cell Power sets the absolute power of the secondary serving cell.

   GPIB Command: CALL:SSCell:POWer[:SAMPLitude]

 

•  Secondary Serving Cell DL Channel Config

   The parameter sets whether the Secondary Serving Cell DL Adjacent UARFCN or Secondary Serving Cell DL M anual UARFCN is used as the secondary serving cell downlink UARFCN when Dual Carrier Band Configuration is set to Single Band .

   This parameter can only be set when the Data/Call Status is Idle .

   GPIB Command: CALL:SSCell:CHANnel:CONFig[:TYPE]

 

•  Secondary Serving Cell DL Adjacent UARFCN

   This parameter sets the downlink adjacent UARFCN of the secondary serving cell.

   This parameter can only be set while the Call Status is Idle .

   GPIB Command: CALL:SSCell:CHANnel:ADJacent

 

 
•  Secondary Serving Cell DL Manual UARFCN

   This parameter sets the downlink UARFCN of the secondary serving cell when:

   
  • Dual Carrier Band Configuration is set to Single Band , and Secondary Serving Cell DL Channel Config is set to Manual
  •  Dual Carrier Band Configuration is set to Dual Band or User Defined

   This parameter can only be set while the Call/Data Status is Idle .

   GPIB Command: CALL:SSCell:CHANnel:MANual:UARFcn

 

•  Secondary Serving Cell Manual Band Arbitrator

   This parameter determines the second serving cell's band when the Secondary Serving Cell DL M anual UARFCN is used as the secondary serving cell's UARFCN and that UARFCN is a shared Band V and VI value.

   This parameter can only be set while the Call/Data Status is Idle .

   GPIB Command: CALL:SSCell:CHANnel:MANual:BARBitrator

 

• Secondary Serving Cell Primary Scrambling Code

   The actual code number for the primary scrambling code is 16 times the value of this setting.

   GPIB Command: CALL:SSCell:SCODe[:PRIMary]

   This setting is only available in the lab application.

 

 MIMO Parameters

 

•  N_cqi_typeA/M_cqi Ratio

   When the Operating Mode is Active Cell , the parameter controls the N_cqi_typeA/M_cqi ratio on the UL HS-DPCCH when Current MIMO Configuration Status is Active .

   There are two types of CQI reports defined, type A and type B. And the Node B controls the ratio and schedule of type A CQI reports and type B CQI reports on the HS-DPCCH in the form of N_cqi_typeA/M_cqi ratio, where M_cqi is the number of feedback cycles in which type A CQI reports are sent in the first N_cqi_typeA cycles and type B CQI reports are sent in the rest cycles.

   This parameter can only be set while the Call/Data Status is Idle .

   GPIB Command: CALL:HSDPa:MIMO:NMRatio

 

•  Pr ecoding Weight Set Restriction State

   The parameter controls whether the test set will signal the UE to apply precoding weight set restriction when reporting the PCI (precoding control indication, ie., the signalled information about the preferred primary precoding vector) on the uplink.

   This parameter can only be set while the Call/Data Status is Idle .

   GPIB Command: CALL:HSDPa:MIMO:PPWRestrict[:STATe]

 

•  HSDPA MIMO Antenna 2 Pilot Configuration

   The parameter sets the pilot channel of antenna 2 when the UE is operating in MIMO mode.

   The pilot channel of antenna 2 can be set to P-CPICH or S-CPICH . If S-CPICH is selected, the power offset of S-CPICH relative to P-CPICH would be calculated and rounded to the nearest 1.00 dB (the resolution of the signalled parameter) and limited to -6.00 dB or 0.00 dB (the min/max value of the signalled parameter) automatically and signalled to the UE. The automatically calculated value is the difference between the equation of Antenna 2 S-CPICH Power Offset and Antenna 1 P-CPICH Power Offset. If either the Antenna 2 S-CPICH State or Antenna 1 P-CPICH State is set to Off, then -20.00 dB will be assumed as the relative channel power.

   This parameter can only be set while the Call/Data Status is Idle .

   GPIB Command: CALL:ANTenna2:PILot:CONFig

 

•  HSDPA MIMO S-CPICH Pow Offset Signaling State

   When HSDPA MIMO Antenna 2 Pilot Configuration is set to S-CPICH , this parameter determines whether the S-CPICH power offset relative to the P-CPICH TX power will be signalled to the UE.

   This parameter can only be set while the Call/Data Status is Idle .

   GPIB Command: CALL:HSDPa:MIMO:CPIChannel:SECondary:POFFset:SIGNaling:STATe

 

 Measurement Power Offset

 

•  Meas Pow Offset

   This setting is the difference in power levels of the CPICH and HS-PDSCH channels. The UE assumes this value to be the power level that the test set uses when transmitting the HS-PDSCHs, and therefore uses this parameter in its HSDPA CQI measurement algorithm.

   The Meas Power Offset ,Gamma (defined in 3GPP TS 25.214 s6A.2), that is used by the UE is signaled at call setup and remains unchanged unless a Transport Channel Reconfiguration procedure is performed.

   The parameters that are used to calculate the Meas Power Offset if its control state is set to Auto depend on the service type (see Current Service Type ).

   

  • If the service type is either Radio Bearer Test Mode - HSDPA or Packet Switched Data - HSDPA, then the automatic value for the Meas Power Offset is the difference of HSDPA Cell 1 Connected HS-PDSCHs Level (Sum) minus HSDPA Cell 1 Connected CPICH Level . Note: If either of the two parameters used in the calculation of the Meas Power Offset is set to Off , then the test set uses a value of -20 dB for the corresponding parameter.

  •  

    If the service type is either Radio Bearer Test Mode - HSPA or Packet Switched Data - HSPA, then the automatic value for the Meas Power Offset is the difference of HSPA Cell 1 Connected HS-PDSCHs Level (Sum) minus HSPA Cell 1 Connected CPICH Level . Note: If either of the two parameters used in the calculation of the Meas Power Offset is set to Off , then the test set uses a value of -20 dB for the corresponding parameter.

   GPIB Command: CALL:HSDPa:MPOWer[:MOFFset]

   This parameter can only be set while the call status is Idle .

   This setting is only available in the lab application. (In the test application the measurement power offset is set to -6 dB.)

 

 H-RNTI Parameters

 
•  Primary H-RNTI (Hex)

   Identifier used by the test set to transmit to the UE under test. The test set only transmits to the UE under test on HS-SCCH 1.

   GPIB command: CALL:HSDPa:HRNTi[:PRIMary]

   This parameter can only be set when call status is Idle .

•  Alternate H-RNTI (Hex)

   During TTIs where data is not transmitted to the UE under test (when inter-TTI is greater than one), the test set transmits dummy data on HS-SCCH 1 using the Alternate H-RNTI. The content of the HS-SCCH 1 when the Alternative H-RNTI is in use is the same as the data that was used the last time the Primary H-RNTI (Hex) was used.

   HS-SCCH 2-4, when turned on, are always transmitted using the Alternate H-RNTI . The content of HS-SCCH 2-4 is fixed as follows:

   
  • Code set: 0b1101110
  •  Modulation scheme: 0b0
  •  Transport block size: 0b010010
  •  HARQ process information: 0b101
  •  RV information: 0b111
  •  New data: 0b0

   When not transmitting data to the UE under test, the test set sends a fixed pattern of uncoded PRBS data on the HS-PDSCHs. The number of HS-PDSCHs transmitted is the same as the number of HS-PDSCHs transmitted during the last subframe that contained data directed to the UE under test.

   GPIB command: CALL:HSDPa:HRNTi:ALTernate

   This parameter can only be set when call status is Idle .

•  HS-SCCH1 Alternate H-RNTI (Hex)

   This parameter controls the alternate H-RNTI that is used on the HS-SCCH 1. The test set use this parameter in Active Cell when it wishes to indicate that the HS-SCCH1 is not for the UE under test.

   This parameter can not be set to be same as Primary H-RNTI (Hex) or Secondary Serving Cell H-RNTI (Hex) .

   GPIB command: CALL:HSDPa:HRNTi:ALTernate:HSSCCH1

   This parameter can only be set when call status is Idle .

•  HS-SCCH2 Alternate H-RNTI (Hex)

   This parameter controls the alternate H-RNTI that is used on the HS-SCCH2. The test set use this parameter in Active Cell when it wishes to indicate that the HS-SCCH2 is not for the UE under test.

   This parameter can not be set to be same with Primary H-RNTI (Hex) or Secondary Serving Cell H-RNTI (Hex) .

   GPIB command: CALL:HSDPa:HRNTi:ALTernate:HSSCCH2

   This parameter can only be set when call status is Idle .

•  HS-SCCH3 Alternate H-RNTI (Hex)

   This parameter controls the alternate H-RNTI that is used on the HS-SCCH3. The test set use this parameter in Active Cell when it wishes to indicate that the HS-SCCH3is not for the UE under test.

   This parameter can not be set to be same with Primary H-RNTI (Hex) or Secondary Serving Cell H-RNTI (Hex) .

   GPIB command: CALL:HSDPa:HRNTi:ALTernate:HSSCCH3

   This parameter can only be set when call status is Idle .

•  HS-SCCH4 Alternate H-RNTI (Hex)

   This parameter controls the alternate H-RNTI that is used on the HS-SCCH4. The test set use this parameter in Active Cell when it wishes to indicate that the HS-SCCH4 is not for the UE under test.

   This parameter can not be set to be same with Primary H-RNTI (Hex) or Secondary Serving Cell H-RNTI (Hex) .

   GPIB command: CALL:HSDPa:HRNTi:ALTernate:HSSCCH4

   This parameter can only be set when call status is Idle .

•  Secondary Serving Cell H-RNTI (Hex)

   Controls the primary H-RNTI of the secondary serving cell.

   The Primary H-RNTI cannot be the same as the Alternate H-RNTI. If you attempt to set this parameter to a value that is same with any FDD Test Mode HS-SCCH Alternate H-RNTI; i.e. HS-SCCH1 Alternate H-RNTI (Hex) , HS-SCCH2 Alternate H-RNTI (Hex) , HS-SCCH3 Alternate H-RNTI (Hex) and HS-SCCH4 Alternate H-RNTI (Hex) , the attempt will be rejected.

   GPIB command: CALL:HSDPa:SSCell:HRNTi

   This parameter can only be set when call status is Idle .

• Number of HS-DSCH Common HRNTIs

  This setting controls the number of HS-DSCH common H-RNTIs included in IE HS-DSCH Common System Information.

  GPIB command: CALL[:CELL]:CHSDschannel:HRNTi:COMMon:COUNt

  This parameter can only be set when call status is Idle.

• HS-SCCH 1Common H-RNTI (Hex)

  GPIB command: CALL[:CELL]:CHSDschannel:HRNTi:COMMon:HSSCCH1

  This parameter can only be set when call status is Idle.

•  HS-SCCH 2 Common H-RNTI (Hex)

  GPIB command: CALL[:CELL]:CHSDschannel:HRNTi:COMMon:HSSCCH2

  This parameter can only be set when call status is Idle.

• HS-SCCH 3 Common H-RNTI (Hex)

  GPIB command: CALL[:CELL]:CHSDschannel:HRNTi:COMMon:HSSCCH3

  This parameter can only be set when call status is Idle.

• HS-SCCH 4 Common H-RNTI (Hex)

  GPIB command: CALL[:CELL]:CHSDschannel:HRNTi:COMMon:HSSCCH4

  This parameter can only be set when call status is Idle.

• BCCH Specific H-RNTI

  There are several H-RNTIs defined in 3GPP Release 7 standards: common HRNTIs, dedicated H-RNTI and BCCH specific H-RNTI. Common H-RNTIs and BCCH specific H-RNTI are broadcasted in BCCH and can be used by any UE. Dedicated H-RNTIs are explicitly configured in signalling message during RRC connection setup phase or RB setup/reconfiguration phase.

The enhanced CELL_FACH feature allows System information (on BCCH) to be sent on HS-DSCH in CELL_FACH state. To avoid the BCCH data transmission using different H-RNTIs of all UEs in CELL_FACH state, a BCCH specific H-RNTI, which is also included in the HS-DSCH common system information IE, is introduced to notify all UEs in CELL_FACH state that BCCH information is transmitted. Users in CELL_FACH state may have been configured with a dedicated H-RNTI and are able to receive dedicated data on HS-DSCH. Other users without dedicated H-RNTI only receive data on common channels based on a common H-RNTI. Both users with and without dedicated H-RNTI can receive BCCH data using BCCH specific H-RNTI.

GPIB command: CALL[:CELL]:CHSDschannel:HRNTi:SPECific:BCCHannel

This parameter can only be set when call status is Idle.

 

Related Topics

 

Manual Operation: How Do I Change HSDPA Parameters?

 HSDPA in Active Cell Operating Mode

 HSDPA in FDD Test Operating Mode

 HSDPA/HSPA DL Channel Codes

 HSDPA Connected DL Channel Levels