HSDPA RB Test Mode Settings

Last updated: April 27, 2013

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

RB Test HS-DSCH Configuration Type

You can configure the HSDPA RB Test Mode downlink HS-DSCH in one of two ways. You can specify an FRC, which automatically configures the downlink properties, or you can manually define the downlink properties such as Number of HARQ Processes, Modulation Type, Transport Block Size Index etc. using the "User Defined" parameters.

WhenHS-DSCH Configuration Type is set toFRC , the downlink channel is configured as the FRC specified by the FRC Type setting. WhenHS-DSCH Configuration Type is set toUser Defined , the downlink channel is configured according to the settings described in User Defined Configuration of the HS-DSCH .

GPIB command: CALL:HSDPa:SERVice:RBTest:HSDSchannel:CONFig[:TYPE]

This parameter can only be changed while the call status is idle.

Configuring the HS-DSCH as an FRC

FRC Type
The test set supports the following H-Sets defined in 3GPP TS 34.121 sC.8: H-Sets 1-3 (QPSK and 16QAM), H-Sets 4 and 5 (QPSK), H-Set 6 (QPSK and 16QAM), H-Set 8 (64QAM), H-Set 9, H-Set 11, H-Set 10 (QPSK and 16QAM) and the DC-HSDPA H-Sets 3A, 6A, 8A 10A and 12.

The test set sets the Inter-TTI Distance, Number of HARQ Processes, Information Bit Payload, Number of SMLs per HARQ Process, Number of Physical Channel Codes, etc. to the values specified by 34.121 for each FRC. It is essential that you setFRC Type to match the capabilities of your UE (the UE categories are defined in 3GPP TS 25.306 Table 5.1a.).

Note that changingFRC Type may change the number of active HS-PDSCHs. You must set RB Test Mode First HS-PDSCH Channel Code to 5 before you can setFRC Type toH-Set 6 (because H-Set 6 utilizes 10 HS-PDSCHs).

GPIB command: CALL:HSDPa:SERVice:RBTest:FRC:TYPE

This parameter can only be set when call status isIdle , and is only applicable when RB Test HS-DSCH Configuration Type is set toFRC .


FRC MAC-d PDU Size

While on an RB Test Mode connection, the test set sends as many MAC-d PDUs as it can pack into the MAC-hs PDU, up to the maximum of 70 allowed by 3GPP TS 25.321 s9.2.2. Each MAC-d PDU consists of a single RLC UM PDU (which may or may not include an RLC header, as determined by the RLC Header on HS-DSCH setting). The data pattern used to fill the data fields of the RLC UM PDU is specified by the HS-DSCH Data Pattern setting.

When RB Test HS-DSCH Configuration Type is set toFRC , the MAC-hs PDU size is determined by the FRC Type .

WhenHS-DSCH Configuration Type is set toFRC , you can set the size of the MAC-d PDU to 112 bits, 336 bits, 656 bits, or maximize the size of the MAC-d PDU (whenHS-DSCH Configuration Type is set toUser Defined , the MAC-d PDU size is fixed to 112 bits). WhenFRC MAC-d PDU Size is set toMaximize , the MAC-d PDU size is set to the largest multiple of 8 bits that doesn't exceed the MAC-hs PDU size minus 21 MAC-hs header bits, or 5000 bits (3GPP TS 25.331 s10.3.5.1a specifies a maximum MAC-d PDU size of 5000 bits).

MAC-hs PDU size and maximum MAC-d PDU size for each FRC type
FRC Type	MAC-hs PDU size	MAC-d PDU size when`FRC MAC-d PDU Size` =`Maximize`
H-Set 1-5 QPSK	3202	3176
H-Set 1-3 16QAM	4664	4640
H-Set 6 QPSK	6438	5000
H-Set 6 16QAM	9377	5000

If the MAC-d PDU plus the MAC-hs header does not completely fill the MAC-hs PDU, the test set fills the unused portion with padding that consists of the payload data of the next UM RLC PDU(s). The following diagram provides an example for aMAC-d PDU Size of 112 bits, no RLC header and a MAC-hs PDU size of 3202:

GPIB command: CALL:HSDPa:SERVice:RBTest:FRC:MACD:PDUSize

This parameter can only be set when call status isIdle , and is only applicable when RB Test HS-DSCH Configuration Type is set toFRC .

Configuring the DC-HSDPA RB Test Mode Settings

When the required feature license is available, you can set the DC-HSDPA RB test mode settings as below. See Serving Cell Parms and Secondary Cell Parms for the parameters of each cell.

RB Test User Defined DC-HSDPA State
This parameter allows you to enable or disable DC-HSDPA operation.

Note: You must set the User Defined Number of HARQ Processes and User Defined HS-DSCH MAC Entity correctly before setting RB Test User Defined DC-HSDPA State to On .

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:DCHSdpa[:STATe]

This parameter can only be changed when call status isIdle .
DC-HSDPA DPCH Loopback State
This parameter controls whether the loopback procedure for 12.2k RMC should be performed during the "CS/PS Combined Call Setup Procedure" for the DC-HSDPA call setup. When this setting is set to On , the loopback procedure is performed.

GPIB command: CALL:HSDPa:SERVice:RBTest:DCHSdpa:DPCH:LOOPback[:STATe]

This parameter can only be changed when call status isIdle .

User Defined Configuration of the HS-DSCH

The following parameters are only applicable when RB Test HS-DSCH Configuration Type is set toUser Defined .

User Defined Number of Active HS-PDSCHs
Sets the number of HS-PDSCHs being transmitted by the test set. This setting affects the transport block size (see User Defined Transport Block Size Index ). You can change this setting while on a connection.

The number of HS-PDSCHs specified by this setting, when added to the RB Test Mode First HS-PDSCH Channel Code cannot exceed 16 (otherwise the HS-PDSCHs would collide with the downlink OCNS channels).

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:HSPDschannel:COUNt
User Defined Transport Block Size Index
Sets k_i (transport block size index) as described in 3GPP TS 25.321 s9.2.3. You can change this setting while on a connection.

You cannot directly set the HS-DSCH (MAC-hs) transport block size. Rather, you must set the User Defined Number of Active HS-PDSCHs , User Defined Modulation Type , andUser Defined Transport Block Size Index . The test set then calculates the HS-DSCH transport block size from these three settings. You can query the transport block size using the CALL:STATus:HSDSchannel:TBSize? command.

3GPP TS 25.321 Annex A provides a mapping of the index k_t to HS-DSCH transport block size. 25.321 s9.2.3.1 specifies that k_t = k_i + k_0,i . 25.321 Table 9.2.3.1 provides values for k_0,i for different modulation types and number of active HS-PDSCHs. Thus, the HS-DSCH transport block size can be directly determined from the modulation type, number of active HS-PDSCHs, and transport block size index. For example, for a modulation type of 16QAM and 5 HS-PDSCHs, k_0,i = 131. Choosing a value of k_i = 48 results in a value of 179 for k_t , which is an HS-DSCH transport block size of 7298 bits.

Note, if you setUser Defined Transport Block Size Index to a value that results in a transport block size that exceeds the maximum value for the Current UE HS-DSCH Category (see 3GPP TS 25.306 Table 5.1a), the test set will post a warning, but will still transmit using the requested block size. Transmitting too large of a block to the UE will likely result in undesirable behavior (the UE may stop its HS-DSCH reception altogether, and you may need to end and re-establish the connection with a smaller block size).

See Example User Defined Configuration: Maximum Data Rate for each UE Category to determine the settings to achieve the highest data rate for your UE.

Note, the MAC-d PDU size for the user defined channel is fixed to 112 bits.

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:TBSize:INDex
User Defined Modulation Type
Sets the modulation type used on the HS-PDSCHs. This setting affects the transport block size (see User Defined Transport Block Size Index ). You can change this setting while on a connection.

Note, not all UE categories support 16QAM. If you setUser Defined Modulation Type to16QAM when Current UE HS-DSCH Category is reporting a category that does not support 16QAM (see 3GPP TS 25.306 Table 5.1a), the test set will post a warning, but will still transmit using 16QAM modulation.

Note, if you setUser Defined Modulation Type to a value that results in a transport block size that exceeds the maximum value for the Current UE HS-DSCH Category (see 3GPP TS 25.306 Table 5.1a), the test set will post a warning, but will still transmit using the requested block size. See User Defined Transport Block Size Index for more details.

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:MODulation[:TYPE]
User Defined Flexible RLC SDU Size
Sets the RLC SDU size in octets of the DTCH that will be mapped to HS-DSCH. The range of this setting is 1 byte to 1503 bytes.

This parameter can only be set when the data/call status isIdle , and is only applicable when User Defined HS-DSCH MAC Entity is set to MAC-ehs .

GPIB Command: CALL:HSDPa:SERVice:RBTest:UDEFined:MACEHS:RLC:SDU[:SIZE]
User Defined Inter-TTI Interval
Sets the inter-TTI interval used on the downlink. For example, an inter-TTI interval of 1 indicates that data will be transmitted to the UE in every TTI (if there are enough active HARQ processes to provide data in every TTI). How often data is actually transmitted to the UE depends also upon the User Defined Number of HARQ Processes . See Interaction of Inter-TTI Interval and Number of HARQ Processes . You can change this setting while on a connection.

Note, not all UE categories support an inter-TTI interval of less than 3 (see 3GPP TS 25.306 Table 5.1a). If you setUser Defined Inter-TTI Interval to a value that is not supported by the Current UE HS-DSCH Category , the test set will post a warning, but will still transmit using the specified inter-TTI interval.

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:ITTI[:INTerval]
User Defined Number of HARQ Processes
Sets the number of HARQ processes that are active. The number of HARQ processes, along with the User Defined Inter-TTI Interval , affects how often data is transmitted to the UE. See Interaction of Inter-TTI Interval and Number of HARQ Processes .

Note: For DC-HSDPA, when User Defined UE IR Buffer Allocation is set toImplicit , you are not allowed to set the number of HARQ processes to a value less than 6, and vice versa. Also, When User Defined UE IR Buffer Allocation is set toExplicit , the number of HARQ processes can be 1 through 8, but the memory size for each HARQ process can not be greater than the number of soft channel bits for an implicit memory partitioning with 6 processes per HS-DSCH channel (3GPP TS 25.331 s8.6.5.6b).

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:HARQ:PROCess:COUNt

This setting can only be changed when Call Status is Idle (to change this value while on a call, you must perform a Transport Channel Reconfiguration ).
User Defined Number of HARQ Processes for MIMO
Sets the number of HARQ processes that are active in the MAC-ehs layer when User Defined HSDPA MIMO State is set to On and HS-DSCH Configuration Type is set to User Defined .

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:MIMO:HARQ:PROCess:COUNt

This setting can only be changed when Call/Data Status is Idle .
User Defined UE IR Buffer Allocation
Controls how the IR buffer size for each active HARQ process is determined.

WhenUser Defined UE IR Buffer Allocation is set toImplicit , the total IR buffer size for the Current UE HS-DSCH Category ("total number of soft channel bits" in 3GPP TS 25.306 Table 5.1a) is divided equally among the active HARQ processes. Using this setting helps ensure that the HSDPA connection will be successfully established, as the IR buffer size used by the test set is automatically set to match the current UE category. However, please note that to configure the user defined downlink to emulate an FRC, you may need to setUser Defined UE IR Buffer Allocation toExplicit , and then set User Defined Explicit UE IR Buffer Size accordingly (see Example User Defined Configuration: Configuring the Downlink as an FRC ).

WhenUser Defined UE IR Buffer Allocation is set toExplicit , the IR buffer size allocated to each active HARQ process is determined directly by the User Defined Explicit UE IR Buffer Size setting. This setting allows you to allocate less than your UE's maximum total IR buffer size (which may be required if you wish to emulate an FRC, see Example User Defined Configuration: Configuring the Downlink as an FRC ). Note that if you set the User Defined Explicit UE IR Buffer Size beyond your UE's capability (based on the number of HARQ processes), the HSDPA connection attempt will fail.

See User Defined Number of HARQ Processes on DC-HSDPA operating restrictions.

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:MS:IREDundancy:BUFFer:ALLocation

This setting can only be changed when call status is idle (to change this value while on a call, you must perform a Transport Channel Reconfiguration ).


User Defined Explicit UE IR Buffer Size

When User Defined UE IR Buffer Allocation is set toExplicit , this setting determines the size of the IR buffer allocated to each HARQ process. The total IR buffer size is thus determined by multiplying theUser Defined Explicit UE IR Buffer Size by the User Defined Number of HARQ Processes .

Note, different UE categories support different total IR buffer sizes ("total number of soft channel bits" in 3GPP TS 25.306 Table 5.1a). If you set the total IR buffer size beyond the specified limit for the Current UE HS-DSCH Category , the test set will post a warning, but will still allocate the total IR buffer size you've set. This will cause the HSDPA connection attempt to fail.

UE Categories supports corresponding Total Available IR Buffer Size
UE Category	Total Available IR Buffer Size
1	19200
2	28800
3	28800
4	38400
5	57600
6	67200
7	115200
8	134400
9	172800
10	172800
11	14400
12	28800
13	259200
14	259200
15/17 (with MIMO)	345600
16/18 (with MIMO)	345600
19	518400
20	518400
21	345600
22	345600
23	518400
24	518400

The range for this setting is 800-16000 by step of 800, 17600-32000 by step of 1600, 36000-80000 by step of 4000, 88000-160000 by step of 8000, and 176000-304000 by step of 16000, as per 3GPP TS 25.331 s10.3.5.7a.

For DC-HSDPA, if the Current Secondary Serving Cell State is Configured-Active or Configured-Inactive , the User Defined Explicit UE IR Buffer Size can not be greater than the number of soft channel bits for an implicit memory partitioning with 6 processes per HS-DSCH channel (Total Available IR Buffer Size divided by 2 and then by the number of HARQ processes). Or an warning message will pop up reminding you that the Explicit UE IR Buffer Size exceeds the limit.

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:MS:IREDundancy:BUFFer:SIZe[:EXPLicit]

This setting can only be changed when call status is idle (to change this value while on a call, you must perform a Transport Channel Reconfiguration ).

User Defined HS-DSCH MAC Entity
This setting controls the HS-DSCH MAC entity to be used, either MAC-hs or MAC-ehs. This setting also determines the HS-DSCH TB size table.

DC-HSDPA operation requires the MAC-ehs to be configured. You must set the User Defined HS-DSCH MAC Entity to MAC-ehs before setting the Configuring the DC-HSDPA RB Test Mode Settings to On .

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:HSDSchannel:MAC
User Defined HSDPA MIMO State
When the HS-DSCH Configuration Type is set to User Defined , the User Defined HS-DSCH MAC Entity is MAC-ehs , and the Transmission Mode is Normal , this setting controls whether to configure the MIMO or not for the RB Test Mode HSDPA/HSPA call.

This setting can only be changed when Call/Data Status is Idle .

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:MIMO[:STATe]
Number of Transport Blocks
Sets the number of transport blocks scheduled on the HS-DSCH when MIMO is configured.

GPIB command: CALL:HSDPa:SERVice:RBTest:MIMO:TBLock:COUNt
Primary Precoding Weight Config
Specifies how the test set determines its downlink primary precoding weight when MIMO is configured in RB Test Mode.
- If Primary Precoding Weight Config is set to Static , Static Primary Precoding Weight is used as the primary precoding weight.
- If Primary Precoding Weight Config is set to 34.121-1 s9.2.4 , the downlink primary precoding weight will be determined as per the specification in the 3GPP TS 34.121-1 section 9.2.4 (TTI basis).
GPIB command: CALL:HSDPa:SERVice:RBTest:FRC:MIMO:PPWeight:CONFig
Secondary TB Size Index
This setting specifies the secondary transport block size index for MIMO when the HS-DSCH Configuration Type is set to User Defined and the User Defined HS-DSCH MAC Entity is MAC-ehs .

This setting can only be changed when Call Status is Idle or Active .

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:STBSize:INDex
Secondary TB Modulation Type
This setting specifies the modulation type used on the secondary transport block for MIMO when the HS-DSCH Configuration Type is set to User Defined and the User Defined HS-DSCH MAC Entity is MAC-ehs .

Note that not all MIMO-capable UEs support 64QAM modulation. When the Current Service Type is RB Test Mode-HSDPA/HSPA, HS-DSCH Configuration Type is User Defined and User Defined HSDPA MIMO State is On, setting UE Reported HS-DSCH Category to 17 or 18 will post the warning message indicating it does not support 64QAM modulation simultaneously with MIMO, and setting UE Reported HS-DSCH Category to 15 or 16 will post the warning message indicating it does not support 64QAM modulation. Though you are alerted about the potentially invalid condition, yet 64QAM is still being used.

This setting can only be changed when Call Status is Idle or Active .

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:STBLock:MODulation[:TYPE]
Static Primary Precoding Weight
When Current MIMO Configuration State is set to Active and Primary Precoding Weight Config is set to Static , this setting specifies the primary precoding weight in RB Test Mode FRC configuration type.

GPIB command: CALL:HSDPa:SERVice:PSData:MIMO:PPWeight[:STATic]
User Defined 64QAM State
When the User Defined HS-DSCH MAC Entity is set to MAC-ehs , this setting controls whether 64QAM modulation is used or not.

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:QAM64:STATe
User Defined MAC-ehs HS-DSCH TB Size Table
When the User Defined HS-DSCH MAC Entity is set to MAC-ehs, and the User Defined 64QAM State is set to Off, this setting controls the HS-DSCH TB size table.

GPIB command: CALL:HSDPa:SERVice:RBTest:UDEFined:MACEHS:HSDSchannel:TBSTable:ALIGnment

Interaction of Inter-TTI Interval and Number of HARQ Processes

How often data is transmitted to the UE depends upon the inter-TTI interval and number of HARQ processes. The following table, Data Transmission Pattern Based on Inter-TTI Interval and Number of HARQ Processes , indicates how often data is transmitted to the UE under test depending upon the User Defined Inter-TTI Interval and the User Defined Number of HARQ Processes settings.

In the table, "0" represents HARQ0 data directed to the UE under test (using the Primary H-RNTI (Hex) ), "1" represents HARQ1 data directed to the UE under test, "2" represents HARQ2 data directed to the UE under test, etc. "*" represents data sent by the test set that is not directed to the UE under test (i.e. data directed to the Alternate H-RNTI (Hex) ).

The bottom of each cell also explicitly indicates how often the HARQ0 process transmits for each combination of settings. Note that when inter-TTI interval * number of HARQ processes > 6, HARQ0 does not transmit every 12 ms.

Data Transmission Pattern Based on Inter-TTI Interval and Number of HARQ Processes
	Number of HARQ Processes
Inter-TTI Interval	1	2	3	4	5	6	7	8
1	0*** 0*** (12 ms)	01** 01** (12 ms)	012* 012* (12 ms)	0123 0123 (12 ms)	01234* 01234* (12 ms)	012345 012345 (12 ms)	012345 601234 (14 ms)	012345 670123 (16 ms)
2	0*** 0*** (12 ms)	01** 01** (12 ms)	012* 012* (12 ms)	012* 301* (16 ms)	012* 340* (20 ms)	012* 345* 012* (24 ms)	012* 345* 601* (28 ms)	012* 345* 670* (32 ms)
3	0*** 0*** (12 ms)	01 01 (12 ms)	01 20 (18 ms)	01 23 01 (24 ms)	01 23 40 (30 ms)	01 23 45 01 (36 ms)	01 23 45 60 (42 ms)	01 23 45 67 01 (48 ms)
4	0*** 0*** (12 ms)	0**1 0**1 (12 ms)	0**1 2* 0**1 (24 ms)	0**1 2* 3**0 (32 ms)	0**1 2* 3**4 0* (40 ms)	0**1 2* 3**4 5* 0**1 (48 ms)	0**1 2* 3**4 5* 6**0 (56 ms)	0**1 2* 3**4 5* 6**7 0* (64 ms)
5	0*** 0*** (12 ms)	0**1 0**1 (12 ms)	0**1 *2 *0 (30 ms)	0**1 *2 *3 0* (40 ms)	0**1 *2 *3 4* 0*** (50 ms)	0**1 *2 *3 4* 5* 0**1 (60 ms)	0**1 *2 *3 4* 5* 6**0 (70 ms)	0**1 *2 *3 4* 5* 67 *0 (80 ms)
6	0*** 0*** (12 ms)	0*** 1* 0*** (24 ms)	0*** 1* 2* 0*** (36 ms)	0*** 1* 2* 3* 0*** (48 ms)	0*** 1* 2* 3* 4* 0*** (60 ms)	0*** 1* 2* 3* 4* 5* 0*** (72 ms)	0*** 1* 2* 3* 4* 5* 6* 0*** (84 ms)	0*** 1* 2* 3* 4* 5* 6* 7* 0*** (96ms)
7	0***** 0*** (14 ms)	0***** 1* 0*** (28 ms)	0***** 1* 2* 0* (42 ms)	0***** 1* 2* 3* ***0 (56 ms)	0***** 1* 2* 3* ***4 *****0 (70 ms)	0***** 1* 2* 3* ***4 ***5 ** 0*** (84 ms)	0***** 1* 2* 3* ***4 ***5 ** 6*** 0*** (98 ms)	0***** 1* 2* 3* ***4 ***5 ** 6*** 7* 0*** (112 ms)
8	0*** 0*** (16 ms)	0*** 1* *0 (32 ms)	0*** 1* *2 **** 0*** (48 ms)	0*** 1* *2 **** 3* 0*** (64 ms)	0*** 1* *2 **** 3* 4* *0 (80 ms)	0*** 1* *2 **** 3* 4* *5 **** 0*** (96 ms)	0*** 1* *2 **** 3* 4* *5 **** 6* 0*** (112 ms)	0*** 1* *2 **** 3* 4* *5 **** 6* 7* *0 (128 ms)

Example User Defined Configuration: Configuring the Downlink as an FRC

The following table, User Defined Settings to Configure the Downlink as an FRC , indicates the settings required to configure the user defined downlink channel as an FRC.

Note that 3GPP TS 34.121 Annex C refers to transport block size as "Information Bit Payload (N_INF )".

Note that 3GPP TS 34.121 Annex C refers to UE IR buffer size as "Number of SML's per HARQ Process". Depending upon the category of your UE, you may need to set User Defined UE IR Buffer Allocation toExplicit (and manually set the User Defined Explicit UE IR Buffer Size to the appropriate value), to achieve the "Number of SML's per HARQ Process" specified by 34.121 for the FRC you are emulating.

The data transmission pattern column indicates how often data is transmitted to the UE under test, and by which HARQ process. See Interaction of Inter-TTI Interval and Number of HARQ Processes for more information.

The Nominal Avg. Inf. Bit Rate is determined by multiplying the transport block size by the number of blocks transmitted per second. For an FRC, the number of blocks transmitted in 12 ms is equal to the number of HARQ processes (this is because for FRCs, inter-TTI interval * number of HARQ processes < 6). Thus, for an FRC, the Nominal Avg. Inf. Bit Rate is equal to: (transport block size in bits)*(number of HARQ processes)/12 ms.

User Defined Settings to Configure the Downlink as an FRC
FRC	Number of Active HS-PDSCHs	Modulation Type	Transport Block Size Index k_i (Corresponding Transport Block Size)	Inter-TTI Interval	Number of HARQ Processes	User Defined Explicit UE IR Buffer Size (per HARQ process)	Data transmission pattern	Nominal Avg. Inf. Bit Rate
H-Set 1 QPSK	5	QPSK	41 (3202 bits)	3	2	9600	01	534 kbps
H-Set 1 16QAM	4	16QAM	36 (4664 bits)	3	2	9600	01	777 kbps
H-Set 2 QPSK	5	QPSK	41 (3202 bits)	2	3	9600	012*	801 kbps
H-Set 2 16QAM	4	16QAM	36 (4664 bits)	2	3	9600	012*	1.17 Mbps
H-Set 3 QPSK³	5	QPSK	41 (3202 bits)	1	6	9600	012345	1.60 Mbps
H-Set 3 16QAM³	4	16QAM	36 (4664 bits)	1	6	9600	012345	2.33 Mbps
H-Set 4 QPSK	5	QPSK	41 (3202 bits)	2	2	7200	01	534 kbps
H-Set 5 QPSK	5	QPSK	41 (3202 bits)	1	3	9600	012***	801 kbps
H-Set 6 QPSK³	10¹	QPSK	41 (643815 bits)	1	6	19200	012345	3.22 Mbps
H-Set 6 16QAM³	8	16QAM	36 (9377 bits)	1	6	19200	012345	4.69 Mbps
H-Set 8 64QAM³	15²	64QAM	36 (26504 bits)	1	6	259200	012345	13.25Mbps
H-Set 10 QPSK³	15²	16QAM	36 (17548 bits)	1	6	28800	012345	8.77 Mbps
H-Set 10 16QAM³	15²	QPSK	42 (9719 bits)	1	6	28800	012345	4.86 Mbps
H-Set 12 (QPSK)³	1	QPSK	0 (120 bits)	1	6	3200	012345	60 kbps
¹ You must set RB Test Mode First HS-PDSCH Channel Code to 6 before you can set`Number of Active HS-PDSCHs` to 10. ² You must set RB Test Mode First HS-PDSCH Channel Code to 1 before you can set`Number of Active HS-PDSCHs` to 15. ³ For H-Set 12 and other DC-HSDPA H-Sets (H-Set 3A, 6A, 8A, 10A), the parameter settings are for each of the serving cells (carriers).

Example User Defined Configuration: Maximum Data Rate for each UE Category

The following table, User Defined Settings to Achieve Maximum Data Rate for each UE Category , indicates the settings required to configure the user defined downlink channel to achieve the maximum data rate for each UE category supported by the test set.

The Nominal Avg. Inf. Bit Rate is determined by multiplying the transport block size by the number of blocks transmitted per second. If inter-TTI interval * number of HARQ processes < 6, the number of blocks transmitted in 12 ms is equal to the number of HARQ processes, and Nominal Avg. Inf. Bit Rate is equal to: (transport block size in bits)*(number of HARQ processes)/12 ms. Note that although the Nominal Avg. Inf. Bit Rate is equal between categories 1/2, 3/4, and 5/6, due to the larger IR buffer size of categories 2, 4 and 6, in a network these categories may realize a higher actual data rate.

Note, you may need to increase the test set'sCell 1 Sum of Active Conn HS-PDSCH Levels setting to allow the UE to reliably receive the test set's downlink and therefore achieve the UE's maximum data rate.

User Defined Settings to Achieve Maximum Data Rate for each UE Category
UE Category	Number of Active HS-PDSCHs	Modulation Type	Transport Block Size Index k_i (Corresponding Transport Block Size)	Inter-TTI Interval	Number of HARQ Processes	User Defined Explicit UE IR Buffer Size (per HARQ process)	Data transmission pattern	Nominal Avg. Inf. Bit Rate
1	5	16QAM	48 (7298 bits)	3	2	19200/2=9600	01	1.22 Mbps
2	5	16QAM	48 (7298 bits)	3	2	28800/2=14400	01	1.22 Mbps
3	5	16QAM	48 (7298 bits)	2	3	28800/3=9600	012*	1.83 Mbps
4	5	16QAM	48 (7298 bits)	2	3	38400/3=12800	012*	1.83 Mbps
5	5	16QAM	48 (7298 bits)	1	6	57600/6=9600	012345	3.65 Mbps
6	5	16QAM	48 (7298 bits)	1	6	67200/6=11200	012345	3.65 Mbps
7	10¹	16QAM	48 (14411 bits)	1	6	115200/6=19200	012345	7.21 Mbps
8	10¹	16QAM	48 (14411 bits)	1	6	134400/6=22400	012345	7.21 Mbps
9	15²	16QAM	44 (20251 bits)	1	6	172800/6=28800	012345	10.13 Mbps
10	15²	16QAM	62 (27952 bits)	1	6	172800/6=28800	012345	13.976 Mbps
11	5	QPSK	48 (3630 bits)	2	3	14400/3=4800	012*	908 kbps
12	5	QPSK	48 (3630 bits)	1	6	28800/6=4800	012345	1.82 Mbps
13	15²	64QAM	52 (35280 bits)	1	6	259200/6=43200	012345	17.640 Mbps
14	15²	64QAM	62 (42192 bits)	1	6	259200/6=43200	012345	21.096 Mbps
21³	15²	16QAM	52 (23370 bits)	1	6	345600/2/6=28800	012345	23.4 Mbps (two cells combined)
22³	15²	16QAM	62 (27952 bits)	1	6	345600/2/6=28800	012345	28 Mbps (two cells combined)
23³	15²	64QAM	52 (35280 bits)	1	6	518400/2/6=43200	012345	35.3 Mbps (two cells combined)
24³	15²	64QAM	62 (42192 bits)	1	6	518400/2/6=43200	012345	42.2 Mbps (two cells combined)
¹ You must set RB Test Mode First HS-PDSCH Channel Code to 6 before you can set`Number of Active HS-PDSCHs` to 10. ² You must set RB Test Mode First HS-PDSCH Channel Code to 1 before you can set`Number of Active HS-PDSCHs` to 15. ³ For UE Categories 21 to 24 that support DC-HSDPA, the parameter settings are for each of the serving cells (carriers).

General HSDPA RB Test Mode Settings

CN Domain
Non-HSDPA/non-HSPA RB test mode connections are always established using CS domain entities (see Radio Bearer Test Mode Origination to CELL_DCH - CS Domain (Non-HSPA or HSDPA) ). In contrast, an HSDPA RB test mode connection can be established using CS domain entities, PS domain entities, or both, as determined by theCN Domain (Core Network Domain) setting.
- IfCN Domain is set toPS Domain , the connection is established as shown in Radio Bearer Test Mode Origination to CELL_DCH - PS Domain (HSDPA) . The PS domain is used to establish the RMC and FRC.
- IfCN Domain is set toCS Domain , the connection is established as shown in Radio Bearer Test Mode Origination to CELL_DCH - CS Domain (Non-HSPA or HSDPA) . The CS domain is used to establish the RMC and FRC.
- IfCN Domain is set toCS/PS Domain , the connection is established as shown in Radio Bearer Test Mode Origination to CELL_DCH - CS/PS Domain (HSDPA or HSPA) . The CS domain is used to establish the RMC and the PS domain is used to establish the FRC.
Note that HSPA RB Test Mode connections are always established using both the CS and PS domains, so this setting is not applicable to HSPA RB Test Mode.

Many 3GPP TS 34.121 tests specify theCS/PS Domain connection procedure (by reference to 3GPP TS 34.108 s7.3.6). However, using theCS Domain orPS Domain connection procedures do not compromise the results of the 34.121 tests. Regardless of which domain is used to establish the connection, the resulting channel configuration (radio bearers) is identical.

Using theCS Domain procedure offers two advantages:
- TheCS Domain procedure allows the UE to be paged without first going through the Attach procedure (which reduces the total time from UE power-up to establishing an HSDPA connection). To use this alternate method, set PS Domain Information toAbsent (to prevent the UE from attaching upon power-up), enter the appropriate Paging IMSI , power on the UE and then selectOriginate Call . To further speed up the connection process, you can set Repeat Paging toOn , selectOriginate Call , then power on the UE.
- TheCS Domain procedure allows you to perform a System Handover to GSM/GPRS/EGPRS when you have completed your W-CDMA/HSDPA testing, if desired ( fast switching applications only ).
Note, ifCN Domain is set toPS Domain orCS/PS Domain , the UE must have performed the Attach procedure before you can page it ( PS Domain Information must be set toPresent when the UE registers with the test set).

If FRC Type is set to one of the DC-HSDPA type (H-Set 3A, 6A, 8A, 10A or 12) or if the RB Test User Defined DC-HSDPA State is set to On , this parameter is not applicable and the test set uses "CS(RMC) / PS(FRC)" as the CN domain.

GPIB command: CALL:HSDPa:SERVice:RBTest:CNDomain

This parameter can only be set when call status isIdle .
Uplink 0k DTCH for HSDPA Loopback State
This setting only applies to an HSDPA RB Test Mode connection, it does not apply to an HSPA RB Test Mode connection (because on an HSPA RB Test Mode connection, the downlink HSDPA channel is looped back onto the uplink HSUPA channel).
- WhenUplink 0k DTCH for HSDPA Loopback State is set toOn , the RB Setup message sent to establish the HSDPA RB test mode connection includes a 0k DTCH, onto which the UE is instructed to loop back the downlink HSDPA radio bearer with a Loopback SDU size of 0 (ensuring no data is transmitted on the 0k DTCH). This DTCH is defined identically to the Uplink 64k DTCH for HSDPA Loopback, except only the 0 block transport format is defined in the transport format set.
- Off : When this parameter is set toOff , the UE analyzes the data it receives on the HSDPA downlink radio bearer so that it can respond with ACK/NACK information on the uplink HS-DPCCH, but then discards the data (the UE loopback function sits above the RLC layer so the data is discarded after it has been processed at the MAC-hs layer).
GPIB command: CALL:HSDPa:SERVice:RBTest:DTCHannel0:HLOopback:STATe

This parameter can only be set when call status isIdle , and cannot be set toOn when Uplink 64k DTCH for HSDPA Loopback State is set toOn .
Uplink 64k DTCH for HSDPA Loopback State
This setting only applies to an HSDPA RB Test Mode connection, it does not apply to an HSPA RB Test Mode connection (because on an HSPA RB Test Mode connection, the downlink HSDPA channel is looped back onto the uplink HSUPA channel).
- WhenUplink 64k DTCH for HSDPA Loopback State is set toOn , the RB Setup message sent to establish the HSDPA RB test mode connection includes a 64k DTCH, onto which the UE is instructed to loop back the downlink HSDPA radio bearer with a Loopback SDU size of 0 (ensuring no data is transmitted on the 64k DTCH). See 3GPP TSG-RAN5 R5-050720.
  
  HSDPA RB Test Mode Channel Configuration with Uplink 64k DTCH for Loopback State On
  
  You must set this parameter toOn if your UE does not support closing the test loop on a unidirectional radio bearer (if your UE was implemented according to 3GPP TS 34.109 v5.4.0 which did not specify what the UE should do when told to close the test loop on a unidirectional radio bearer). Note: even if an uplink DTCH is provided for the HSDPA radio bearer to loop onto, no data is ever sent on this channel as the Loopback SDU size is zero for the HSDPA radio bearer (this ensures the uplink DPCH consists solely of a 12.2k RMC).
- Off : When this parameter is set toOff , the UE analyzes the data it receives on the HSDPA downlink radio bearer so that it can respond with ACK/NACK information on the uplink HS-DPCCH, but then discards the data (the UE loopback function sits above the RLC layer so the data is discarded after it has been processed at the MAC-hs layer).
  
  HSDPA RB Test Mode Channel Configuration with Uplink 64k DTCH for Loopback State Off
GPIB command: CALL:HSDPa:SERVice:RBTest[:DTCHannel64]:HLOopback:STATe

This parameter can only be set when call status isIdle , and cannot be set toOn when Uplink 0k DTCH for HSDPA Loopback State is set toOn .
HS-DSCH Data Pattern
You can specify the data pattern sent in each HS-DSCH transport block on the downlink HS-PDSCH(s). HS-DSCH Data Pattern can be set to: CCITT PRBS23 , CCITT PRBS20 , CCITT PRBS15 ,CCITT PRBS9 ,All Zeros ,All Ones ,Incrementing , orAlternating .

For PRBS data types, the seed that is used to initialize the PRBS generator for each RLC UM PDU is the seed that the generator had at the point when it finished creating the bits that were placed into the data field of the previously transmitted RLC UM PDU. This means that the PRBS sequence is continuous across the RLC UM PDU data fields (if you were to extract all of the data fields from the transmitted RLC UM PDUs, you would observe an unbroken PRBS sequence).

GPIB command: CALL:HSDPa:SERVice:RBTest:HSDSchannel:DATA
RLC Header on HS-DSCH
TheRLC Header on HS-DSCH parameter allows you to configure whether the RLC UM block contains a valid UM header or whether that header is filled with data according to the HS-DSCH Data Pattern setting.

Note: As part of Release 6, 3GPP introduced an alternative interpretation of the E-bit in the RLC header to improve transmission efficiency for the specific case when an SDU always fits into a PDU. The network tells the UE whether or not to use the alternative at call setup. This alternative E-bit representation is not used in the test set.

GPIB command: CALL:HSDPa:SERVice:RBTest:HSDSchannel:RLCHeader

This parameter can only be set when call status isIdle .
RB Test Mode F-DPCH State
This setting is used to indicate whether the F-DPCH is configured instead of the associated DPCH in the downlink when an HSPA RB Test Mode call is activated.

When this parameter is set toOff , the F-DPCH is not configured and SRBs will be mapped onto the E-DCH/DCH in the uplink and downlink respectively.

When this parameter is set toOn , the F-DPCH is configured and SRBs will be mapped onto the E-DCH/HS-DSCH in the uplink and downlink respectively.

If FRC Type is set to one of the DC-HSDPA type (H-Set 3A, 6A, 8A, 10A or 12) or if the RB Test User Defined DC-HSDPA State is set to On , you are not allowed to set this parameter to On because F-DPCH is not available with MAC-ehs.

This parameter can only be set when call status isIdle .

GPIB Command: CALL:HSDPa:SERVice:RBTest:FDPChannel:STATe
Target Quality On F-DPCH
This parameter determines the TPC command error rate target, which is sent to UE via the RadioBearSetup message when F-DPCH is configured.

This setting is only available when the RB Test Mode F-DPCH State is set to On .

GPIB Command: CALL:HSDPa:SERVice:RBTest:FDPChannel:TARGet[:QUALity]

	Number of HARQ Processes
Inter-TTI Interval	1	2	3	4	5	6	7	8
1	0*** 0*** (12 ms)	01** 01** (12 ms)	012* 012* (12 ms)	0123 0123 (12 ms)	01234* 01234* (12 ms)	012345 012345 (12 ms)	012345 601234 (14 ms)	012345 670123 (16 ms)
2	0*** 0*** (12 ms)	01** 01** (12 ms)	012* 012* (12 ms)	012* 301* (16 ms)	012* 340* (20 ms)	012* 345* 012* (24 ms)	012* 345* 601* (28 ms)	012* 345* 670* (32 ms)
3	0*** 0*** (12 ms)	01 01 (12 ms)	01 20 (18 ms)	01 23 01 (24 ms)	01 23 40 (30 ms)	01 23 45 01 (36 ms)	01 23 45 60 (42 ms)	01 23 45 67 01 (48 ms)
4	0*** 0*** (12 ms)	0**1 0**1 (12 ms)	0**1 2* 0**1 (24 ms)	0**1 2* 3**0 (32 ms)	0**1 2* 3**4 0* (40 ms)	0**1 2* 3**4 5* 0**1 (48 ms)	0**1 2* 3**4 5* 6**0 (56 ms)	0**1 2* 3**4 5* 6**7 0* (64 ms)
5	0*** 0*** (12 ms)	0**1 0**1 (12 ms)	0**1 *2 *0 (30 ms)	0**1 *2 *3 0* (40 ms)	0**1 *2 *3 4* 0*** (50 ms)	0**1 *2 *3 4* 5* 0**1 (60 ms)	0**1 *2 *3 4* 5* 6**0 (70 ms)	0**1 *2 *3 4* 5* 67 *0 (80 ms)
6	0*** 0*** (12 ms)	0*** 1* 0*** (24 ms)	0*** 1* 2* 0*** (36 ms)	0*** 1* 2* 3* 0*** (48 ms)	0*** 1* 2* 3* 4* 0*** (60 ms)	0*** 1* 2* 3* 4* 5* 0*** (72 ms)	0*** 1* 2* 3* 4* 5* 6* 0*** (84 ms)	0*** 1* 2* 3* 4* 5* 6* 7* 0*** (96ms)
7	0***** 0*** (14 ms)	0***** 1* 0*** (28 ms)	0***** 1* 2* 0* (42 ms)	0***** 1* 2* 3* ***0 (56 ms)	0***** 1* 2* 3* ***4 *****0 (70 ms)	0***** 1* 2* 3* ***4 ***5 ** 0*** (84 ms)	0***** 1* 2* 3* ***4 ***5 ** 6*** 0*** (98 ms)	0***** 1* 2* 3* ***4 ***5 ** 6*** 7* 0*** (112 ms)
8	0*** 0*** (16 ms)	0*** 1* *0 (32 ms)	0*** 1* *2 **** 0*** (48 ms)	0*** 1* *2 **** 3* 0*** (64 ms)	0*** 1* *2 **** 3* 4* *0 (80 ms)	0*** 1* *2 **** 3* 4* *5 **** 0*** (96 ms)	0*** 1* *2 **** 3* 4* *5 **** 6* 0*** (112 ms)	0*** 1* *2 **** 3* 4* *5 **** 6* 7* *0 (128 ms)