hsdpa ps data setup
TRANSCRIPT
-
7/27/2019 Hsdpa Ps Data Setup
1/42
HSDPA PS Data Setup
Last updated: October 19, 2012
This section is only applicable to the lab application.
HSDPA PS Data Parameters Serving Cell Parameters Secondary Serving Cell Parameters
HSDPA PS Data Parameters
PS Data DC-HSDPA StateThis parameter controls whether to set up a DC-HSDPA PS Data call. DC-HSDPA
operation requires:
o The serving cell and the secondary serving cell are in the same frequency band;o The total number of HS-SCCHs configured for both the cells be 6 or less;o PS Data HS-DSCH MAC entityis set to Mac-ehs ;o The Number of HARQ Processes shall be more than 6 whenPS Data UE IR
Buffer Allocationis set to Implicit . whenPS Data UE IR Buffer Allocationis
set to Explicit , the number of HARQ processes can be 1 through 8, but thememory 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-DSCHchannel (3GPP TS 25.331 s8.6.5.6b).
o The current UE HS-DSCH Category is between 21 to 24.This parameter can only be changed when Call Status is idle.
GPIB command:CALL:HSDPa:SERVice:PSData:DCHSdpa[:STATe]
PS Data HS-DSCH MAC-d PDU Size ControlThis setting determines whetherPS Data HS-DSCH MAC-d PDU Size orPS Data HS-
DSCH MAC-d PDU Size Manual is to be used on HS-DSCH channel.
GPIB command:CALL:HSDPa:SERVice:PSData:MACD:PDUSize:CONTrol
PS Data HS-DSCH MAC-d PDU SizeThis parameter specifies the size of the MAC-d PDU that is used on the DTCH that is
mapped to the HS-DSCH for an HSDPA PS data connection. The DTCH is the logicalchannel that carries the downlink user traffic data (for example, IP datagrams).
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBIAGHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBIAGHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBDBJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBDBJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDFHEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDFHEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDEEEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDEEEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDEEEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEAHFChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEAHFChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEAHFChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEAHFChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDEEEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDFHEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBDBJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBIAGH -
7/27/2019 Hsdpa Ps Data Setup
2/42
Some UEs require a 656 bit MAC-d PDU size to achieve maximum data throughput
(because sending fewer blocks reduces the load on the UE's CPU). 3GPP TS 34.108
s6.10.2.4.5.1 lists 656 bits as an alternate MAC-d PDU size. PS Data HS-DSCH MAC-d
PDU Size cannot be changed to 656 bits ifPS Data HS-DSCH Configuration Typeis setto 7 or less (because doing so would cause the MAC-d PDU to be too large for the MAC-
hs block).
This parameter can only be changed when connection status is idle.
GPIB command:CALL:HSDPa:SERVice:PSData:MACD:PDUSize
PS Data HS-DSCH MAC-d PDU Size ManualWhen PS Data HS-DSCH MAC-d PDU Size Control is set to Manual , this setting
determines the size of the MAC-d PDU that is used on the DTCH that is mapped to the
HS-DSCH for a HSDPA PS data connection.
GPIB command:CALL:HSDPa:SERVice:PSData:MACD:PDUSize:MANual
PS Data Number of HARQ ProcessesSets the control state and value for the number of active HARQ processes.
The control state can be set to Auto or Manual mode. When the control state is set to
Auto, the number of HARQ processes active in the MAC-hs layer is set such that the
fewest number of HARQ processes are used that will still result in maximum throughput
based on the Current UE HS-DSCH Category. These values for the AUTO control state
are as follows.
UE Category
Number of HARQ Processes
(if the control state is AUTO)
1 2
2 2
3 3
4 3
5 6
6 6
7 6
8 6
9 6
10 6
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDIABAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDIABAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDIABAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDFJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDFJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDFJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDFJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDIABAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJG -
7/27/2019 Hsdpa Ps Data Setup
3/42
UE Category
Number of HARQ Processes
(if the control state is AUTO)
11 3
12 613 6
14 6
15 12
16 12
17 6
18 6
21 6
22 6
23 6
24 6
When the control state is set to a value (manual mode), the test set uses this value for the
number of HARQ processes active in the MAC-hs layer.
SeePS Data DC-HSDPA Stateon restrictions with DC-HSDPA operation.
This setting can only be changed when the call status is idle.
GPIB command:Control State:
CALL:HSDPa:SERVice:PSData:HARQ:PROCess:COUNt:CONTrol:AUTO
Manual Setting:CALL:HSDPa:SERVice:PSData:HARQ:PROCess:COUNt:MANual
PS Data Manual Num of HARQ Processes for MIMOThis parameter controls the number of active HARQ processes in the MAC_ehs layer
when PS Data HS-DSCH MAC Entity is set to MAC_ehs and PS Data HSDPA MIMO
State is set to On .
This setting can only be changed when Call Status is Idle .
GPIB command:CALL:HSDPa:SERVice:PSData:MIMO:HARQ:PROCess:COUNt:MANuall
PS Data UE IR Buffer AllocationControls how the IR buffer size for each active HARQ process is determined.
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBJCAFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBJCAFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHBFHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHBFHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHBFHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDAJFIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDAJFIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDAJFIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHBFHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBJCAFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJ -
7/27/2019 Hsdpa Ps Data Setup
4/42
When PS Data UE IR Buffer Allocation is set to Implicit , the total IR buffersize for theCurrent UE HS-DSCH Category("total number of soft channel bits" in 3GPPTS 25.306 Table 5.1a) is divided equally among the active HARQ processes. For DC-
HSDPA, the soft memory buffer is initially equally partitioned among the HS-DSCH
transport channels and then equally partitioned among the HARQ processes per HS-
DSCH transport channel. Using this setting helps ensure that the HSDPA connection willbe successfully established, as the IR buffer size used by the test set is automatically set
to match the current UE category. However, to configure the size of the IR buffer
allocated to each HARQ process in the user defined downlink, you may need to set PS
Data UE IR Buffer Allocation to Explicit , and then setPS Data Explicit UE IRBuffer Sizeaccordingly.
When PS Data UE IR Buffer Allocation is set to Explicit , the IR buffer sizeallocated to each active HARQ process is determined directly by thePS Data Explicit UE
IR Buffer Sizesetting. This setting allows you to allocate less than your UE's maximumtotal IR buffer size. Note that if you set thePS Data Explicit UE IR Buffer Sizebeyond
your UE's capability (based on the number of HARQ processes), the HSDPA connectionattempt will fail.
SeePS Data DC-HSDPA Stateon restrictions with DC-HSDPA operation.
This setting can only be changed when call status is idle.
GPIB command:
CALL:HSDPa:SERVice:PSData:MS:IREDundancy:BUFFer:ALLocation
PS Data Explicit UE IR Buffer SizeWhenPS Data UE IR Buffer Allocationis set to Explicit , this setting determines the
size of the IR buffer allocated to each HARQ process. The total IR buffer size is thus
determined by multiplying the PS Data Explicit UE IR Buffer Size by thePSData Number of HARQ Processes.
Note, different UE categories support different total IR buffer sizes ("total number of softchannel bits" in 3GPP TS 25.306 Table 5.1a). If you set the total IR buffer size beyond
the specified limit for theCurrent 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. The limits for the IR buffer size based on the UE
category are listed in the table below. UE Categories 21,22,23 and 24 support DC-HSDPA.
UE Category IR Buffer Size Limit
1 19200
2 28800
3 28800
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCHJAJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCHJAJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCBDGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCBDGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCBDGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCBDGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCBDGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCBDGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCJGABhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCHJAJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDGIHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIA -
7/27/2019 Hsdpa Ps Data Setup
5/42
UE Category IR Buffer Size Limit
4 38400
5 57600
6 67200
7 115200
8 134400
9 172800
10 172800
11 14400
12 28800
13 259200
14 259200
17 25920018 259200
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.
SeePS Data DC-HSDPA Stateon restrictions with DC-HSDPA operation.
This setting can only be changed when call status is idle.
GPIB command:
CALL:HSDPa:SERVice:PSData:MS:IREDundancy:BUFFer:SIZE[:EXPLicit]
PS Data HS-DSCH MAC entity
IfPS Data DC-HSDPA Stateis set to On , you can not set this parameter to MAC-hsbecause DC-HSDPA must be configured with MAC-ehs.
This setting can only be changed when call status is idle.
GPIB command:CALL:HSDPa:SERVice:PSData:HSDSchannel:MAC
Downlink AM RLC Mode
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABEBIADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABEBIADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDJIDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDJIDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDJIDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDJIDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABEBIADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCIDCJ -
7/27/2019 Hsdpa Ps Data Setup
6/42
GPIB command:CALL:HSDPa:SERVice:PSData:RLC:DOWNlink:MODE
DL Flexible RLC Header Extension Special ValueGPIB command:
CALL:HSDPa:SERVice:PSData:RLC:DOWNlink:HEXTension:SVALue
DL Max PDU Payload SizeThis setting is only available when thePS Data HS-DSCH MAC entityis set to MAC-ehs
and theDownlink AM RLC Modeis Flexible .
This setting determines the downlink maximum flexible AM RLC PDU payload size. If
the AM RLC SDU size is greater than the DL Max PDU Payload Size , it is segmented
to multiple RLC PDUs so that the payload in each PDU is equal to or less than the DL
Max PDU Payload Size . The payload size in those PDUs which are not the last one is
set to DL Max PDU Payload Size , and the remaining segment will be put into the lastRLC PDU.
This setting can only be changed when call status is idle.
GPIB command:
CALL:HSDPa:SERVice:PSData:RLC:DOWNlink:MAXimum:PDU:PSIZe
Serving Cell Parameters
PS Data HSDPA MIMO StateThis parameter controls whether to set up a MIMO PS Data HSDPA/HSPA call. This
operation requires:
o The test set is installed with the 8.0 hardware or above;o PS Data HS-DSCH MAC entityis set to Mac-ehs ;o The PS Data DC-HSDPA State is set to Off ;o The current UE HS-DSCH Category is between 15 to 20.
This setting can only be changed when Call/Data Status is Idle .
GPIB command:CALL:HSDPa:SERVice:PSData:MIMO[:STATe]
PS Data HS-DSCH Configuration TypeThis parameter controls how the HS-DSCH is configured. There are three settings:
o CQI Value
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDJEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDJEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDJEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEBJBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEBJBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABEBFHAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABEBFHAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABEBFHAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBECGDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBECGDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#CHDDBGIFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#CHDDBGIFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#CHDDBGIFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#CHDDBGIFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBECGDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABEBFHAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCGFAGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEBJBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBDJEG -
7/27/2019 Hsdpa Ps Data Setup
7/42
This setting uses the value assigned toCQI Value(separate parameter) along with
the Current UE HS-DSCH Category to automatically configure the HS-DSCH
based on tables defined in 3GPP TS 25.214. In order for the test set to accept thissetting, the MAC-hs block size must be large enough to carry at least a single
MAC-d PDU.
When Current MIMO Configuration Status is Active , the primary precodingweight will be static and is determined by the PS Data Primary Precoding Weight,and the number of scheduled transport blocks will be static and is determined by
the PS Data Primary Precoding Weight and HS-DSCH CQI Value for MIMO.
o Reported CQIThis setting is similar to theCQI Valuesetting except that the test set uses the UE
reported CQI values received on the HS-DPCCH channel rather than the assignedCQI Value.
The test set continually adjusts the HS-DSCH configuration to match the CQItable in 3GPP TS 25.214 that corresponds to the Current UE HS-DSCH Category.
If the test set has not yet received a CQI report from the UE, it uses a CQI value
of 8 to configure the HS-DSCH each time a call is connected. Note: The test setcannot receive CQI reports if theCQI Feedback Cycle (k)is set to zero.
The test set ensures that the MAC-hs block size is large enough to contain at leastone MAC-d PDU. Therefore, the smallest CQI value the test set uses for a 336 bit
MAC-d PDUs is 5 and the smallest CQI value the test set uses for 656 bit MAC-d
PDUs is 8 regardless of whether the UE reports smaller CQI values.
When Current MIMO Configuration Status is Active , the test setcontunually adjusts the number of DL transport blocks as per the UE-preferred
number of transport blocks from the reported CQI value. If one tranport block is
preferred by the UE, the test set continually adjusts the number of DL HS-PDSCHs as per the reported CQI value that corresponds to the Current UE HS-
DSCH Category. If two tranport blocks are preferred by the UE, the UE always
asks for 15 HS-PDSCHs in the downlink.
When Current MIMO Configuration Status is Active , the test setcontunually adjusts the DL primary precoding weight as per the UE-preferredprimary precoding weight from the reported PCI value.
o User DefinedWhen this setting is selected, the test set applies the user defined PS data
parameters ( PS Data User Defined Active HS-PDSCHs,PS Data User DefTransport Block Size Index, andPS Data User Defined Modulation Type) rather
than automatically configuring them as is done when the PS Data Configuration
Type is set toCQI ValueorReported CQI. In order for the test set to accept this
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDEGJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDEGJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDEGJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBEEHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBEEHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBEEHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDEGJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDEGJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_ul_parms.html#BABBGFEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_ul_parms.html#BABBGFEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_ul_parms.html#BABBGFEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDAEJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDAEJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDAEJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBEEHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBEEHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBEEHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBACFIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBACFIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBACFIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBACFIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBEEHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDAEJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_ul_parms.html#BABBGFEGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDEGJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBEEHJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDEGJG -
7/27/2019 Hsdpa Ps Data Setup
8/42
setting, the MAC-hs block size must be large enough to carry at least a single
MAC-d PDU
When Current MIMO Configuration Status is Active , the primary precodingweight will be static and is determined by the PS Data Primary Precoding Weight,
and the number of scheduled transport blocks will be static and is determined bythe PS Data Primary Precoding Weight and HS-DSCH CQI Value for MIMO.
GPIB command:CALL:HSDPa:SERVice:PSData:HSDSchannel:CONFig[:TYPE]
CQI ValueThis parameter is only applicable when thePS Data HS-DSCH Configuration Typeis set
to CQI Value . The test set supports an HSDPA packet data connection as defined by3GPP TS 34.108 6.10.2.4.5.1 (seeGPRS Radio Access Bearer). You must specify some
aspects of the channel configuration by specifying a CQI Value .
Based on the CQI Value setting and theCurrent UE HS-DSCH Category, the test setsets the MAC-hs transport block size, number of HS-PDSCHs, modulation type and IR
buffer size (N IR) to the values in 3GPP TS 25.214 s6A.2 Tables 7A-E. The test set uses
theCurrent UE HS-DSCH Categoryto set the inter-TTI interval, number of HARQprocesses, and IR buffer size (N IR) as described inGPRS Radio Access Bearer.
CQI Value cannot be set to 7 or less ifPS Data HS-DSCH MAC-d PDU Sizeis set to
656 bits (because doing so would cause the MAC-hs transport block size to be too small
to carry even a single MAC-d PDU). The number of HS-PDSCHs specified by the CQI
Value , when added to thePS Data First HS-PDSCH Channel Codecannot exceed 15
(otherwise the HS-PDSCHs would collide with the downlink OCNS channels).
Note that when you select a CQI Value that is defined by 3GPP TS 25.214 to have anon-zero "Reference power adjustment", the test set decreases the power present in the
HS-PDSCHs accordingly (as expected, throughput no longer increases once you pass thispoint in the CQI table; rather, throughput decreases as HS-PDSCH power decreases).
This change in power is reflected in the Conn Desired column of theDownlink Code
Channel Informationscreen. For example, for a category 12 UE, if you set CQI Value
to 18 , the power in the HS-PDSCHs is reduced from theHSDPA Cell 1 Connected HS-
PDSCHs Level (Sum)setting of -3 dB to -6 dB.
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCDFFDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCDFFDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCDFFDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdmala_dc_packet_data.html#CIADICBIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdmala_dc_packet_data.html#CIADICBIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdmala_dc_packet_data.html#CIADICBIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdmala_dc_packet_data.html#CIADICBIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdmala_dc_packet_data.html#CIADICBIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdmala_dc_packet_data.html#CIADICBIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_gen_info.html#BCGDJDEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_gen_info.html#BCGDJDEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_gen_info.html#BCGDJDEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_gen_info.html#BCGDJDEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJDEDADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJDEDADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJDEDADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJDEDADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJDEDADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJDEDADhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_gen_info.html#BCGDJDEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_gen_info.html#BCGDJDEEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdmala_dc_packet_data.html#CIADICBIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdmala_dc_packet_data.html#CIADICBIhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCDFFD -
7/27/2019 Hsdpa Ps Data Setup
9/42
CQI Value can be set between 5 and 30. The following table,MAC-hs and IP Bit Rates
(kbps) versus CQI Value and UE Category, summarizes the MAC-hs and IP bit ratesachieved for each CQI Value , based on UE category.
The MAC-hs bit rate is determined by multiplying the MAC-hs block size by the number
of MAC-hs blocks transmitted per second. If inter-TTI interval * number of HARQ
processes < 6, the number of MAC-hs blocks transmitted in 12 ms is equal to the numberof HARQ processes, and the following formula applies:
MAC-hs bit rate = (MAC-hs block size in bits)*(number of HARQ processes)/12 ms
The maximum theoretical IP bit rate is determined by multiplying the number of IP bits
delivered in each MAC-hs block by the number of MAC-hs blocks transmitted persecond. If inter-TTI interval * number of HARQ processes < 6, then the following
formula applies:
IP bit rate = FLOOR[((MAC-hs block size in bits) - (21 MAC-hs header bits))/(MAC-d
PDU Size)]*(MAC-d PDU Size - 16 header bits)*(number of HARQ processes)/12 ms
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBAHBGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBAHBGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBAHBGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBAHBGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBAHBGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBAHBG -
7/27/2019 Hsdpa Ps Data Setup
10/42
Note that although the bit rates are 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
higher actual data rates.
MAC-hs and IP Bit Rates (kbps) versus CQI Value and UE Category
UE Category
1, 2 3, 4 5, 6 7, 8
9, 13, 17
(64QAM
/MIMO
not
configur
ed)
10, 14,
18
(64QAM
/MIMO
not
configur
ed)
11 12
13, 17
(64QAM
configure
d)
14, 18
(64QAM
configur
ed)
C
Q
I
V
al
u
e
M
A
C
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
A
C
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
A
C
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
A
C
-
hs
(k
b
ps
)
IP
(k
bps
)
M
A
C
-d
P
D
U
Si
ze=
33
6
bi
ts
IP
(k
bps
)
M
A
C
-d
P
D
U
Si
ze=
65
6
bi
ts
M
A
C
-
hs
(k
b
ps
)
IP
(k
bps
)
M
A
C
-d
P
D
U
Si
ze=
33
6
bi
ts
IP
(k
bps
)
M
A
C
-d
P
D
U
Si
ze=
65
6
bi
ts
M
A
C
-
hs
(k
b
ps
)
IP
(k
bps
)
M
A
C
-d
P
D
U
Si
ze=
33
6
bi
ts
IP
(k
bps
)
M
A
C
-d
P
D
U
Si
ze=
65
6
bi
ts
M
A
C
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
A
C
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
A
C-
hs
(k
bp
s)
IP
(k
bps)
M
A
C-
d
P
D
U
Si
ze
=33
6
bi
ts
IP
(k
bps)
M
A
C-
d
P
D
U
Si
ze
=65
6
bi
ts
M
A
C
-
hs
(k
b
ps
)
IP
(k
bps
)
M
A
C
-d
P
D
U
Si
ze=
33
6
bi
ts
IP
(k
bps
)
M
A
C
-d
P
D
U
Si
ze=
65
6
bi
ts
5 63 53 94 8018
9
16
0
18
9
16
0
N/
A
18
9
16
0
N/
A
18
9
16
0
N/
A94 80
18
9
16
0
18
8
16
0
N/
A
18
8
16
0
N/
A
6 77 5311
580
23
1
16
0
23
1
16
0
N/
A
23
1
16
0
N/
A
23
1
16
0
N/
A
11
580
23
1
16
0
23
2
16
0
N/
A
23
2
16
0
N/
A
7 108 53 163 80 325 160 325 160 N/A 325 160 N/A 325 160 N/A 163 80 325 160 324 160 N/A 324 160 N/A
8132
107
198
160
396
320
396
320
320
396
320
320
396
320
320
198
160
396
320
396
320
320
396
320
320
9155
107
233
160
466
320
466
320
320
466
320
320
466
320
320
233
160
466
320
464
320
320
464
320
320
1 21 16 31 24 63 48 63 48 32 63 48 32 63 48 32 31 24 63 48 63 48 32 63 48 32
-
7/27/2019 Hsdpa Ps Data Setup
11/42
MAC-hs and IP Bit Rates (kbps) versus CQI Value and UE Category
UE Category
1, 2 3, 4 5, 6 7, 8
9, 13, 17
(64QAM
/MIMOnot
configur
ed)
10, 14,
18
(64QAM
/MIMO
not
configur
ed)
11 12
13, 17
(64QAMconfigure
d)
14, 18
(64QAMconfigur
ed)
CQ
I
V
al
u
e
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
MA
C-
hs
(k
bp
s)
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
33
6
bi
ts
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
65
6
bi
ts
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
0 0 0 6 0 1 0 1 0 0 1 0 0 1 0 0 6 0 1 0 2 0 0 2 0 0
1
1
24
7
21
3
37
1
32
0
74
2
64
0
74
2
64
0
64
0
74
2
64
0
64
0
74
2
64
0
64
0
37
1
32
0
74
2
64
0
74
4
64
0
64
0
74
4
64
0
64
0
1
2
29
0
26
7
43
6
40
0
87
1
80
0
87
1
80
0
64
0
87
1
80
0
64
0
87
1
80
0
64
0
43
6
40
0
87
1
80
0
87
2
80
0
64
0
87
2
80
0
64
0
1
3
38
0
32
0
57
0
48
0
11
40
96
0
11
40
96
0
96
0
11
40
96
0
96
0
11
40
96
0
96
0
57
0
48
0
11
40
96
0
11
44
96
0
96
0
11
44
96
0
96
0
1
4
43
1
37
3
64
6
56
0
12
92
11
20
12
92
11
20
96
0
12
92
11
20
96
0
12
92
11
20
96
0
64
6
56
0
12
92
11
20
12
96
11
20
96
0
12
96
11
20
96
0
15
553
480
830
720
1660
1440
1660
1440
1600
1660
1440
1600
1660
1440
1600
830
720
1660
1440
1664
1440
1600
1664
1440
1600
1
659
453
389
180
017
8316
0017
8316
0016
0017
8316
0016
0017
8316
0016
00
830
*
720
*
1660
*
1440
*
17
8816
0016
0017
8816
0016
00
-
7/27/2019 Hsdpa Ps Data Setup
12/42
MAC-hs and IP Bit Rates (kbps) versus CQI Value and UE Category
UE Category
1, 2 3, 4 5, 6 7, 8
9, 13, 17
(64QAM
/MIMOnot
configur
ed)
10, 14,
18
(64QAM
/MIMO
not
configur
ed)
11 12
13, 17
(64QAMconfigure
d)
14, 18
(64QAMconfigur
ed)
CQ
I
V
al
u
e
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
MA
C-
hs
(k
bp
s)
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
33
6
bi
ts
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
65
6
bi
ts
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
1
769
8
64
0
10
47
96
0
20
95
19
20
20
95
19
20
19
20
20
95
19
20
19
20
20
95
19
20
19
20
830
*
720
*
1660
*
1440
*
21
00
19
20
19
20
21
00
19
20
19
20
1
877
769
311
6610
4023
3220
8023
3220
8022
4023
3220
8022
4023
3220
8022
40
83
0
*
72
0
*
16
60
*
14
40
*
23
3620
8022
4023
3620
8022
40
1
988
180
013
2212
0026
4424
0026
4424
0025
6026
4424
0025
6026
4424
0025
60
83
0
*
72
0
*
16
60
*
14
40
*
26
4824
0025
6026
4824
0025
60
20
98
190
714
7213
6029
4427
2029
4427
2025
6029
4427
2025
6029
4427
2025
60
83
0
*
72
0
*
16
60
*
14
40
*
29
4827
2025
6029
4827
2025
60
2
110
9210
1316
3915
2032
7730
4032
7730
4028
8032
7730
4028
8032
7730
4028
80
83
0*
72
0*
16
60*
14
40*
32
8430
4028
8032
8430
4028
80
-
7/27/2019 Hsdpa Ps Data Setup
13/42
MAC-hs and IP Bit Rates (kbps) versus CQI Value and UE Category
UE Category
1, 2 3, 4 5, 6 7, 8
9, 13, 17
(64QAM
/MIMOnot
configur
ed)
10, 14,
18
(64QAM
/MIMO
not
configur
ed)
11 12
13, 17
(64QAMconfigure
d)
14, 18
(64QAMconfigur
ed)
CQ
I
V
al
u
e
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
MA
C-
hs
(k
bp
s)
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
33
6
bi
ts
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
65
6
bi
ts
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
2
211
95
11
20
17
92
16
80
35
84
33
60
35
84
33
60
32
00
35
84
33
60
32
00
35
84
33
60
32
00
830
*
720
*
1660
*
1440
*
35
92
33
60
32
00
35
92
33
60
32
00
2
3
11
95*
11
20*
17
92*
16
80*
35
84*
33
60*
48
6044
8044
8048
6044
8044
8048
6044
8044
80
83
0
*
72
0
*
16
60
*
14
40
*
48
6844
8044
8048
6844
8044
80
2
4
11
95
*
11
20
*
17
92
*
16
80
*
35
84
*
33
60
*
57
0952
8054
4057
0952
8054
4057
0952
8054
40
83
0
*
72
0
*
16
60
*
14
40
*
57
1652
8054
4057
1652
8054
40
25
11
95*
11
20*
17
92*
16
80*
35
84*
33
60*
72
0667
2067
2072
0667
2067
2072
0667
2067
20
83
0
*
72
0
*
16
60
*
14
40
*
72
1267
2067
2072
1267
2067
20
2
6
11
95*
11
20*
17
92*
16
80*
35
84*
33
60*
72
06*
67
20*
67
20
*
86
1981
6083
2086
1981
6083
20
83
0*
72
0*
16
60*
14
40*
78
88
73
60
76
80
78
88
73
60
76
80
-
7/27/2019 Hsdpa Ps Data Setup
14/42
MAC-hs and IP Bit Rates (kbps) versus CQI Value and UE Category
UE Category
1, 2 3, 4 5, 6 7, 8
9, 13, 17
(64QAM
/MIMOnot
configur
ed)
10, 14,
18
(64QAM
/MIMO
not
configur
ed)
11 12
13, 17
(64QAMconfigure
d)
14, 18
(64QAMconfigur
ed)
CQ
I
V
al
u
e
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
MA
C-
hs
(k
bp
s)
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
33
6
bi
ts
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
65
6
bi
ts
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
2
7
11
95*
11
20*
17
92*
16
80*
35
84*
33
60*
72
06*
67
20*
67
20
*
86
19
*
81
60
*
83
20
*
10
87
7
10
24
0
10
56
0
830
*
720
*
1660
*
1440
*
10
884
10
240
10
560
10
884
10
240
10
560
2
8
11
95*
11
20*
17
92*
16
80*
35
84*
33
60*
72
06*
67
20*
67
20
*
86
19
*
81
60
*
83
20
*
11
68
5
11
04
0
11
20
0
83
0
*
72
0
*
16
60
*
14
40
*
1325
2
1248
0
1280
0
1325
2
1248
0
1280
0
2
9
11
95
*
11
20
*
17
92
*
16
80
*
35
84
*
33
60
*
72
06
*
67
20
*
67
20
*
86
19
*
81
60
*
83
20
*
12
11
1
11
52
0
11
52
0
83
0
*
72
0
*
16
60
*
14
40
*
16
13
2
15
20
0
15
68
0
16
13
2
15
20
0
15
68
0
30
11
95*
11
20*
17
92*
16
80*
35
84*
33
60*
72
06*
67
20*
67
20
*
86
19
*
81
60
*
83
20
*
12
77
9
12
16
0
12
16
0
83
0
*
72
0
*
16
60
*
14
40
*
16
13
2*
15
20
0*
15
68
0*
19
28
8
18
24
0
18
56
0
* denotes that a "Reference power adjustment" is specified by the CQI Value (in other
words, although the bit rate is the same as the bit rate for the preceding CQI Value , thepower in the HS-PDSCHs is reduced).
-
7/27/2019 Hsdpa Ps Data Setup
15/42
MAC-hs and IP Bit Rates (kbps) versus CQI Value and UE Category
UE Category
1, 2 3, 4 5, 6 7, 8
9, 13, 17
(64QAM
/MIMOnot
configur
ed)
10, 14,
18
(64QAM
/MIMO
not
configur
ed)
11 12
13, 17
(64QAMconfigure
d)
14, 18
(64QAMconfigur
ed)
CQ
I
V
al
u
e
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
MA
C-
hs
(k
bp
s)
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
33
6
bi
ts
IP
(k
bp
s)
M
A
C-d
P
D
U
Si
ze
=
65
6
bi
ts
M
AC
-
hs
(k
b
ps
)
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
33
6
bits
IP
(k
b
ps
)
M
AC
-d
P
D
U
Si
ze
=
65
6
bits
Bold font denotes 16QAM modulation.Emphasis font denotes 64QAM modulation.
GPIB command:CALL:HSDPa:SERVice:PSData:CQI[:VALue]
CQI Valuefor MIMOThis parameter specifies the CQI value used to configure the HSDPA channel when
Current MIMO Configuration State is Active ,PS Data HS-DSCH Configuration
Typeis set to CQI Value , and PS Data HS-DSCH MAC Entity is set to MAC_ehs .
GPIB command:CALL:HSDPa:SERVice:PSData:MIMO:CQI:VALue
PS Data Primary Precoding WeightThis parameter specifies the primary precoding weight when MIMO is configured in the
PS Data call. This seeting applies when PS Data HSDPA MIMO State is On ,PS Data
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBEFCAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBEFCAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBEFCAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABEAHDBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABEAHDBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABEAHDBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABEAHDBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBEFCA -
7/27/2019 Hsdpa Ps Data Setup
16/42
HS-DSCH Configuration Typeis set to CQI Value orUser Defined , and PS Data
HS-DSCH MAC Entity is set to MAC_ehs .
GPIB command:CALL:HSDPa:SERVice:PSData:MIMO:PPWeight[:STATic]
PS Data User Def Number of Transport Blocks
This parameter specifies the number of DL transport blocks whenPS Data HS-DSCH
Configuration Typeis set to User Defined , PS Data HS-DSCH MAC Entity is set to
MAC_ehs , and PS Data HSDPA MIMO State is On , .
GPIB command:CALL:HSDPa:SERVice:PSData:UDEFined:MIMO:TBLock:COUNt
PS Data User Defined Active HS-PDSCHsSets the number of HS-PDSCHs transmitted by the test set. This setting affects the
transport block size (seePS Data User Def Transport Block Size Index). You can changethis setting while on a connection.
The number of HS-PDSCHs specified by this setting, when added to thePS Data First
HS-PDSCH Channel Codecannot exceed 15 (otherwise the HS-PDSCHs would collide
with the downlink OCNS channels).
This parameter is only applicable when thePS Data HS-DSCH Configuration Typeis set
to User Defined .
GPIB command: CALL:HSDPa:SERVice:PSData:UDEFined:HSPDschannel:COUNt
PS Data User Def Transport Block Size IndexGPIB command:CALL:HSDPa:SERVice:PSData:UDEFined:TBSize:INDex
PS Data User Defined Modulation TypeGPIB command:CALL:HSDPa:SERVice:PSData:UDEFined:MODulation[:TYPE]
PS Data User Def Secondary TB Size IndexThis parameter specifies the secondary transport block size index for MIMO whenPS
Data HS-DSCH Configuration Typeis set to User Defined , PS Data HS-DSCH MAC
Entity is set to MAC_ehs , and PS Data HSDPA MIMO State is On , .
GPIB command:CALL:HSDPa:SERVice:PSData:UDEFined:STBSize:INDex
PS Data User Def Secondary TB Modulation Type
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDBEDHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDBEDHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDBEDHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBEDDAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBEDDAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBEDDAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCHJJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCHJJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCHJJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHIIChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHIIChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHIIChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBDEJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBDEJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBDEJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBCHGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBCHGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBCHGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBCHGDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBDEJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHIIChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABCHJJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_dl_codes_lvls.html#CBJBGIJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBEDDAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABDBEDHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJG -
7/27/2019 Hsdpa Ps Data Setup
17/42
This parameter specifies the modulation type of the secondary transport block and
determines the actual secondary transport block size. The setting applies whenPS Data
HS-DSCH Configuration Typeis set to User Defined , PS Data HS-DSCH MAC
Entity is set to MAC_ehs , and PS Data HSDPA MIMO State is On , .
GPIB command:CALL:HSDPa:SERVice:PSData:UDEFined:STBLock:MODulation[:TYPE]
PS Data HS-DSCH 64QAM Configured StateGPIB command:CALL:HSDPa:SERVice:PSData:QAM64:STATe
PS Data HS-DSCH TB Size TableGPIB command:
CALL:HSDPa:SERVice:PSData:MACEHS:HSDSchannel:TBSTable:ALIGnment
PS Data User Def Transport Block Size IndexSets ki (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 mustset thePS Data User Defined Active HS-PDSCHs,PS Data User Defined Modulation
Type, and PS Data User Def Transport Block Size Index . The test set then
calculates the HS-DSCH transport block size from these three settings. You can query thetransport block size using theCALL:STATus:HSDSchannel:TBSize?command.
3GPP TS 25.321 Annex A provides a mapping of the index kt to HS-DSCH transportblock size. 25.321 s9.2.3.1 specifies that kt = ki + k0,i . 25.321 Table 9.2.3.1 provides
values for k0,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, k0,i = 131. Choosing a value of ki = 48
results in a value of 179 for kt , which is an HS-DSCH transport block size of 7298 bits.
Note, if you set PS Data User Def Transport Block Size Index to a value thatresults in a transport block size that exceeds the maximum value for theCurrent 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 receptionaltogether, and you may need to end and re-establish the connection with a smaller block
size).
Note, the test set ensures that the transport block size index does not cause the MAC-hs
to become too small to carry a single MAC-d PDU (configured using thePS Data HS-
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBJGCEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBJGCEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDCJHFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDCJHFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDCJHFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEBJAChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEBJAChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDAEJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDAEJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDAEJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_status.html#CJACCFIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_status.html#CJACCFIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_status.html#CJACCFIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_status.html#CJACCFIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABDBDDGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDDAEJJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEBJAChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDCJHFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBJGCEhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJG -
7/27/2019 Hsdpa Ps Data Setup
18/42
DSCH MAC-d PDU Sizeparameter). Therefore, if a change is made to this parameter
that results in too small of MAC-hs block size it will be rejected by the test set.
GPIB command:CALL:HSDPa:SERVice:RBTest:UDEFined:TBSize:INDex
This parameter is only applicable when thePS Data HS-DSCH Configuration Typeis setto User Defined .
GPIB command:CALL:HSDPa:SERVice:PSData:UDEFined:TBSize:INDex
PS Data User Defined Modulation TypeSets the modulation type used on the HS-PDSCHs. This setting affects the transport
block size (seePS Data User Def Transport Block Size Index). You can change this
setting while on a connection.
Note, not all UE categories support 16QAM. If you set PS Data User DefinedModulation Type to 16QAM whenCurrent UE HS-DSCH Categoryis reporting a
category that does not support 16QAM (see 3GPP TS 25.306 Table 5.1a), the test set willpost a warning, but will still transmit using 16QAM modulation.
Note, if you set PS Data User Defined Modulation Type to a value that results in atransport block size that exceeds the maximum value for theCurrent UE HS-DSCHCategory(see 3GPP TS 25.306 Table 5.1a), the test set will post a warning, but will still
transmit using the requested block size. SeePS Data User Def Transport Block Size
Indexfor more details.
This parameter is only applicable when thePS Data HS-DSCH Configuration Typeis setto User Defined .
GPIB command:CALL:HSDPa:SERVice:PSData:UDEFined:MODulation[:TYPE]
PS Data Minimum Inter-TTI IntervalThis parameter sets the control state and value of the of the minimum inter-TTI intervalused on the downlink.
The control state can be set to Auto or Manual mode. When in Auto mode, the minimum
inter-TTI used on an HSDPA or HSPA PS data call is the minimum inter-TTI supportedby the Current UE HS-DSCH Category. When in set to a value (manual mode), this
parameter controls the absolute inter-TTI interval.
Note, not all UE categories support an inter-TTI interval of less than 3 (see 3GPP TS
25.306 Table 5.1a). If you set PS Data Minimum Inter-TTI Interval to a value thatis not supported by theCurrent UE HS-DSCH Category, the test set will post a warning,
but will still transmit using the specified inter-TTI interval.
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBCGACBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBCGACBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBCGACBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHIIChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHIIChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHIIChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBDEJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBDEJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBDEJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBDEJBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.html#CHDCDEIAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABBGHDJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBHIIChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#CHDBJDJGhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBCGACBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_psdata_setup.html#BABCCBBA -
7/27/2019 Hsdpa Ps Data Setup
19/42
You can change this setting while on a connection.
GPIB commands:Control State:
CALL:HSDPa:SERVice:PSData:ITTI[:INTerval]:MINimum:CONTrol:AUTO
Manual Setting:CALL:HSDPa:SERVice:PSData:ITTI[:INTerval]:MINimum:MANual
PS Data HS-DSCH 64QAM Configured StateGPIB command:CALL:HSDPa:SERVice:PSData:QAM64:STATe
PS Data HS-DSCH TB Size TableGPIB command:
CALL:HSDPa:SERVice:PSData:MACEHS:HSDSchannel:TBSTable:ALIGnment
Secondary Serving Cell Parameters Secondary Serving Cell HS-DSCH Configuration Type
GPIB command:CALL:HSDPa:SSCell:PSData:HSDschannel:CONFig[:TYPE]
Secondary Serving Cell CQI ValueGPIB command:CALL:HSDPa:SSCell:PSData:CQI[:VALue]
PS Data User Defined Secondary Cell Active HS-PDSCHsGPIB command: CALL:HSDPa:SSCell:PSData:UDEFined:HSPDschannel:COUNt
PS Data User Def Secondary Cell TB Size IndexGPIB command:CALL:HSDPa:SSCell:PSData:UDEFined:TBSize:INDex
PS Data User Defined Secondary Cell Modulation TypeGPIB command:CALL:HSDPa:SSCell:PSData:UDEFined:MODulation[:TYPE]
PSD Secondary Cell Minimum Inter-TTI IntervalGPIB commands:
Control State:
CALL:HSDPa:SSCell:PSData:ITTI[:INTerval]:MINimum:CONTrol:AUTO
Manual Setting:CALL:HSDPa:SSCell:PSData:ITTI[:INTerval]:MINimum:MANual
PSD Secondary Cell HS-DSCH 64QAM Configured State
http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBFCDDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBBFCDDhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBEFBChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBEFBChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BABBEFBChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDCJHFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDCJHFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDCJHFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEBJAChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBEBJAChttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBCFGAHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBCFGAHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBCFGAHhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#CBHCFAJFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#CBHCFAJFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#CBHCFAJFhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDFBFBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDFBFBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDFBFBhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBECHFJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBECHFJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBECHFJhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDGGJAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDGGJAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBDGGJAhttp://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_hpib_call_hsdpa.html#BGBCAFAAht