Agilent Technologies Home Page 8960 Series 10 Wireless Communications Test Set
- +
Home | Product Web Site | Contact Us
+
- -
+ -
8960 W-CDMA/HSPA Online User's Guide
E1963A, E6703E
Search this guide for     
search tips


Feedback
Did the information on this web page help answer your question or solve a problem?

Yes
No
Did not apply

Please provide additional comments about this page.
(Optional, 255 character max)


Email address (optional):

Privacy Notice: We will not sell or give away your email address to any third party.

 

HSDPA RB Test Mode Setup

Last updated: February 12, 2009

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.

When HS-DSCH Configuration Type is set to FRC , the downlink channel is configured as the FRC specified by the FRC Type setting. When HS-DSCH Configuration Type is set to User 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 H-Sets 1-3 (QPSK and 16QAM), H-Sets 4 and 5 (QPSK), H-Set 6 (QPSK and 16QAM), H-Set 8 (64QAM), and H-Set 10 (QPSK and 16QAM) as defined in 3GPP TS 34.121 sC.8.

    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 set FRC Type to match the capabilities of your UE (the UE categories are defined in 3GPP TS 25.306 Table 5.1a.).

    Note that changing FRC 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 set FRC Type to H-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 is Idle , and is only applicable when RB Test HS-DSCH Configuration Type is set to FRC .

  • 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 to FRC , the MAC-hs PDU size is determined by the FRC Type .

    When HS-DSCH Configuration Type is set to FRC , 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 (when HS-DSCH Configuration Type is set to User Defined , the MAC-d PDU size is fixed to 112 bits). When FRC MAC-d PDU Size is set to Maximize , 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 a MAC-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 is Idle , and is only applicable when RB Test HS-DSCH Configuration Type is set to FRC .

   

User Defined Configuration of the HS-DSCH

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

   

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)
 
0*1***
0*1***


(12 ms)
 
0*1*2*
0*1*2*


(12 ms)
 
0*1*2*
3*0*1*


(16 ms)
 
0*1*2*
3*4*0*


(20 ms)
 
0*1*2*
3*4*5*
0*1*2*

(24 ms)
 
0*1*2*
3*4*5*
6*0*1*

(28 ms)
 
0*1*2*
3*4*5*
6*7*0*

(32 ms)
 
3
0*****
0*****




(12 ms)
0**1**
0**1**




(12 ms)
0**1**
2**0**




(18 ms)
0**1**
2**3**
0**1**



(24 ms)
0**1**
2**3**
4**0**



(30 ms)
0**1**
2**3**
4**5**
0**1**


(36 ms)
0**1**
2**3**
4**5**
6**0**


(42 ms)
0**1**
2**3**
4**5**
6**7**
0**1**

(48 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 to Explicit (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 0**1**

534 kbps
H-Set 1 16QAM 4 16QAM 36
(4664 bits)		 3 2 9600 0**1** 777 kbps
H-Set 2 QPSK 5 QPSK 41
(3202 bits)		 2 3 9600 0*1*2* 801 kbps
H-Set 2 16QAM 4 16QAM 36
(4664 bits)		 2 3 9600 0*1*2* 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 0**1** 534 kbps
H-Set 5 QPSK 5 QPSK 41
(3202 bits)		 1 3 9600 012*** 801 kbps
H-Set 6 QPSK 10 1 QPSK 41
(6438 bits)		 1 6 19200 012345 3.22 Mbps
H-Set 6 16QAM 8 16QAM 36
(9377 bits)		 1 6 19200 012345 4.69 Mbps

1 You must set RB Test Mode First HS-PDSCH Channel Code to 5 before you can set Number of Active HS-PDSCHs to 10.

   

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 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. 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's Cell 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 0**1** 1.22 Mbps
2 5 16QAM 48
(7298 bits)		 3 2 28800/2=14400 0**1** 1.22 Mbps
3 5 16QAM 48
(7298 bits)		 2 3 28800/3=9600 0*1*2* 1.83 Mbps
4 5 16QAM 48
(7298 bits)		 2 3 38400/3=12800 0*1*2* 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 1 16QAM 48
(14411 bits)		 1 6 115200/6=19200 012345 7.21 Mbps
8 10 1 16QAM 48
(14411 bits)		 1 6 134400/6=22400 012345 7.21 Mbps
11 5 QPSK 48
(3630 bits)		 2 3 14400/3=4800 0*1*2*

908 kbps
12 5 QPSK 48
(3630 bits)		 1 6 28800/6=4800 012345

1.82 Mbps

1 You must set RB Test Mode First HS-PDSCH Channel Code to 5 before you can set Number of Active HS-PDSCHs to 10.

   

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 the CN Domain (Core Network Domain) setting.

    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 the CS/PS Domain connection procedure (by reference to 3GPP TS 34.108 s7.3.6). However, using the CS Domain or PS 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 the CS Domain procedure offers two advantages:

    • The CS 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 to Absent (to prevent the UE from attaching upon power-up), enter the appropriate Paging IMSI , power on the UE and then select Originate Call . To further speed up the connection process, you can set Repeat Paging to On , select Originate Call , then power on the UE.
    • The CS 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, if CN Domain is set to PS Domain or CS/PS Domain , the UE must have performed the Attach procedure before you can page it ( PS Domain Information must be set to Present when the UE registers with the test set).

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

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

  • 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).

    • When Uplink 0k DTCH for HSDPA Loopback State is set to On , 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 to Off , 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 is Idle , and cannot be set to On when Uplink 64k DTCH for HSDPA Loopback State is set to On .

  • 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).

    • When Uplink 64k DTCH for HSDPA Loopback State is set to On , 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 to On 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 to Off , 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 is Idle , and cannot be set to On when Uplink 0k DTCH for HSDPA Loopback State is set to On .

  • 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 , or Alternating .

    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

    The RLC 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 is Idle .

  • 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 to Off , 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 to On , the F-DPCH is configured and SRBs will be mapped onto the E-DCH/HS-DSCH in the uplink and downlink respectively.

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

    GPIB Command: CALL:HSDPa:SERVice:RBTest:FDPChannel:STATe

Top of pagetop of page     

+
Privacy Statement | Terms of Use | Webmaster  +  © Agilent 2000-2008
+