Last updated: 2010-03-10
This section is only applicable to the feature-licensed test application.
You can choose one of the three HS-DSCH configurations to do different HSDPA performance tests in 3GPP TS 34.122 9.3. If RMC is selected, the test set will set the downlink properties according to RMC Type, and you can use this option to test 9.3.1A to 9.3.1E; If VRC is selected, the test set will vary the downlink properties according to the UE's indication, and you can use this option to test 9.3.2A to 9.3.2E. The HSSCCH Detection option allows you to perform 9.3.4. See HSDPA Channel Configuration Information for the detailed downlink channel configuration for each HS-DSCH configuration.
GPIB Command: CALL:HSDPa:SERVice:RBTest:HSDSchannel:CONFig[:TYPE]
When HS-DSCH Config is RMC, this parameter determines the HSDPA RMC configuration that is used to perform the HS-DSCH throughput test as in 3GPP TS 34.122 9.3.1A to 9.3.1E.
Each RMC is associated with a particular UE class/category and defines a static configuration at the transport channel and physical channel level as below:
HSDPA RMC Configuration
|
RMC Configuration |
Modulation |
HS-DSCH TSs |
HS-PDSCH codes |
No. of HARQ |
IR Buffer Allocation |
TB Size |
Throughput (kbps) |
|
HSDPA RMC for 0.5M UE Class |
QPSK |
2 |
10 (SF16) |
4 |
implicit |
996 |
199.2 |
|
HSDPA RMC for 1.1M UE Class |
QPSK/16QAM |
2 |
10/12 (SF16) |
4 |
implicit |
995/2893 |
199.0/578.6 |
|
HSDPA RMC for 1.6M UE Class |
QPSK/16QAM |
3 |
10/12 (SF16) |
4 |
implicit |
1787/3173 |
357.4/634.6 |
|
HSDPA RMC for 2.2M UE Class |
QPSK/16QAM |
4 |
10/12 (SF16) |
4 |
implicit |
2695/3911 |
539/782.2 |
|
HSDPA RMC for 2.8M UE Class |
QPSK/16QAM |
5 |
10/12 (SF16) |
4 |
implicit |
3105/6393 |
621/1278.6 |
|
2.8M UE Class Max Throughput* |
16QAM |
5 |
1 (SF1) |
4 |
implicit |
14043 |
2808.6 |
* The option of 2.8M UE Class Max Throughput is not standard-specified configuration.
This setting cannot be changed in Active Cell operating mode and the Call Status is not Idle.
GPIB Command: CALL:HSDPa:SERVice:RBTest:RMC:TYPE
RMC MAC-d PDU Size
This setting determines the MAC-d PDU size that is used for MAC-hs PDU. You can set it to 336 bits, 656 bits, or Maximize. When Maximize is selected, it means that the MAC_d PDU size is the smaller one of the largest PDU size fit for the MAC-hs PDU and 5000 bits.
This setting cannot be changed in Active Cell operating mode and the Call Status is not Idle.
GPIB Command: CALL:HSDPa:SERVice:RBTest:RMC:MACD:PDUSize
CN Domain
Non-HSDPA RB test mode connections are always established using CS domain (Core Network Domain) entities. In contrast, an HSDPA RB test mode connection can be established using PS domain or CS+PS domain.
If CN Domain is set to PS Domain, the 12.2k RMC connection is established on the PS domain. See RB Test Mode HSDPA PS Domain Call Setup Procedure. The PS domain is used to establish the RMC and FRC.
If CN Domain is set to CS/PS Domain, the HSDPA RMC connection is established as shown in RB Test Mode HSDPA CS/PS Domain Call Setup Procedure. The CS domain is used to establish the RMC and the PS domain is used to establish the FRC.
This setting cannot be changed in Active Cell operating mode and the Call Status or Data Status is not Idle.
GPIB Command: CALL:HSDPa:SERVice:RBTest:CNDomain
HS-DSCH Data Pattern
This parameter determines the data pattern that is sent in each HS-DSCH transport block.
GPIB Command: CALL:HSDPa:SERVice:RBTest:HSDSchannel:DATA?
Uplink 0k DTCH for HSDPA Loopback
This parameter determines whether 0K uplink transport channel is to be created for HSDPA RB Test Mode.
This setting cannot be changed while in Active Cell operating mode and the Call Status or Data Status is not Idle.
GPIB Command: CALL:HSDPa:SERVice:RBTest:DTCHannel0:HLOopback:STATe
This parameter controls how the HS-DSCH is configured.
If it is set to User Defined CQI, the test set uses PS Data User Defined Modulation Type and PS Data User Defined TB Index to configure the HS-DSCH.
If it is set to UE Reported CQI, the test set uses UE reported CQI to configure the HS-DSCH, except that:
If the UE reported CQI is smaller than the lower limit of CQI (TB Index) calculated based on MAD-d PDU size, the lower limit of CQI(TB Index) is used to configure the HS-DSCH;
If the UE reported CQI is greater than the CQI upper limit, the upper limit of CQI(TB Index) is used to configure the HS-DSCH.
GPIB Command: CALL:HSDPa:SERVice:PSData:HSDSchannel:CONFig[:TYPE]
This parameter determines MAC-d PDU size that is used on DTCH for a HSDPA PS data connection. This DTCH is the logical channel that carries the downlink user traffic data (i.e. the IP datagrams).
This setting is only allowed to be changed when call status is Idle.
GPIB Command: CALL:HSDPa:SERVice:PSData:MACD:PDUSize
This parameter controls the midamble allocation mode of HS-PDSCH for a PS data connection. According to 3GPP TS 25.221 5A.6, midambles are part of the physical channel configuration which is performed by higher layers. There are four different midamble allocation schemes defined in the standard. The test set supports the following two midamble allocation schemes:
Default - The DL/UL midamble is allocated by layer 1 depending on the associated channelisation code. The fixed association between midambles and channelisation codes is given in 3GPP TS 25.221 Annex AA.2.
Common - The DL midamble is allocated by layer 1 depending on the number of channelisation codes currently being present in the DL time slot. The fixed association between midambles and channelisation codes is given in 3GPP TS 25.221 Annex BA.
This setting can only be changed while the Call Status is Idle. Otherwise, it will post the error +201 (+200 through +299 Error Message Descriptions).
GPIB Commands: CALL:HSDPa:SERVice:PSData:HSPDschannel:MIDamble:MODE
Sets the number of HS-PDSCH timeslots transmitted by the test set. The valid range of this setting depends on PS Data Start of HS-PDSCH Timeslot.
GPIB Command: CALL:HSDPa:SERVice:PSData:HSPDschannel:TSNumber
This parameter determines the start timeslot for the HS-PDSCH allocation. This setting, together with PS Data Number of HS-DPSCH Timeslots, determines the valid HS-PDSCH channels that are used by the test set.
GPIB Command: CALL:HSDPa:SERVice:PSData:HSPDschannel:TSSTart
This parameter determines the OVSF code for the HS-PDSCH channel. If it is set to TS1, then PS Data Number of HS-PDSCH Channel Codes is not available.
GPIB Command: CALL:HSDPa:SERVice:PSData:HSPDschannel:OVSF
This parameter is only available when PS Data HS-PDSCH OVSF is set to SF16.
This parameter determines the number of channel codes are used for HS-PDSCH when PS Data HS-PDSCH OVSF is set to SF16.
GPIB Command: CALL:HSDPa:SERVice:PSData:HSPDschannel:CCODe:NUMBer
PS Data DL DPCH/HS-SCCH Timeslot
This parameter determines how to allocate the downlink DPCH and HS-SCCH channels.
If TS0 is selected, the downlink channel codes and power levels (except DPCH) are configured as in HSDPA RMC mode;
If TS6 is selected, the downlink channel codes and power levels (except DPCH) are configured as in HSDPA HS-SCCH detection mode. See Generator Info and Channel Config Information.
This setting is only allowed to be changed when call status is Idle.
GPIB Command: CALL:HSDPa:SERVice:PSData:DOWNlink:DPCHannel:TSLot
This parameter is only applicable when PS Data HS-DSCH Configuration Type is set to User Defined CQI.
GPIB Command: CALL:HSDPa:SERVice:PSData:UDEFined:MODulation[:TYPE]
This parameter is only applicable when PS Data HS-DSCH Configuration Type is set to User Defined CQI.
GPIB Command: CALL:HSDPa:SERVice:PSData:UDEFined:TBSize:INDex
This parameter determines the number of times a MAC-hs HARQ process will attempt to transmit a particular data block from the MAC-hs queue.
GPIB Command: CALL:HSDPa:MACHs:NTRans
This parameter determines the Redundancy Version (RV) parameter that the test set shall use for each transmission of a particular block. The first element in the list is the RV parameter that the test set will use for the first transmission of a block, the second element is for the second transmission of the same block etc.
You may specify up to eight integer values (between 0 and 7), but the number of RV parameters actually used by the test set is determined by the Number of Transmissions setting (the RV parameters at the end of the sequence are not used if the Number of Transmissions setting is less than the number of RV parameters in the sequence). If you enter fewer than eight values for the RV sequence, the test set fills the remaining values with zeroes.
GPIB Command: CALL:HSDPa:MACHs:RVSequence
MAC-hs Window Size
This parameter determines the value of the MAC-hs window size that is signaled to the UE during the call setup procedure.
This setting cannot be changed in Active Cell operating mode and the Call Status is not Idle.
GPIB Command: CALL:HSDPa:MACHs:WSIZe[:VALue]
MAC-hs T1
This parameter determines the value of the MAC-hs T1 timer that is signaled to the UE. It is signaled to the UE in the Radio Bearer Setup message in the 25.331 s10.3.5.1a "Added or reconfigured MAC-d flow" information element.
This setting cannot be changed in Active Cell operating mode and the Call Status is not Idle.
GPIB Command: CALL:HSDPa:MACHs:T1
This parameter determines how the test set handles the statDTX when it was expecting an ACK or NACK on the HS-SICH.
Handle as ACK: When a statDTX occurs, the test set transmits a new block from the MAC-hs transmit queue using the first entry in the RV Sequence and resets the transmission counter to one.
Handle as NACK: When a statDTX occurs, if the transmission counter is less than the Number of Transmissions setting, the test set transmits the same block using the next entry in the RV Sequence and increments the transmission counter by one. If the transmission counter equals the Number of Transmissions setting, then the Handle as ACK process is followed instead.
Handle as statDTX: When a statDTX occurs, the test set transmits the same block using the same entry in the RV Sequence and does not increment the transmission counter.
This setting does not affect the HSDPA throughput or the HSDPA BLER results.
GPIB Command: CALL:HSDPa:MACHs:SDTX:RBEHavior
Primary H-RNTI (Hex)
This parameter determines the primary H-RNTI that is used on the HS-SCCH. This is the ID that the test set uses when it wishes to transmit data to the UE in Active Cell operating mode.
This setting cannot be changed in Active Cell operating mode and the Call Status is not Idle.
GPIB Command: CALL:HSDPa:HRNTi[:PRIMary]
HS-SCCH2-4 H-RNTIs (Hex)
These are the H-RNTIs that the test set does not transmit data to. The default values are set to match 3GPP TS34.122 s9.3.4 HS-SCCH Detection Performance measurement.
Each HS-SCCH H-RNTI should not be set identical to other HS-SCCH H-RNTIs, nor should it be identical with the Primary H-RNTI (Hex).
GPIB Command: CALL:HSDPa:HRNTi:ALTernate:HSSCCH2|3|4