14.7 Combinations on DPCH, HS-PDSCH and E-DPDCH
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
NOTE: The testing of radio bearer combinations on DPCH, HSPDSCH and E-DPDCH is focusing on verifying that the UE is capable to establish the radio bearer combination and to verify correct data transfer using all the possible uplink TFS for transport channels mapped on DCH and all the configured MAC-d PDU sizes for the transport channel mapped to E-DCH. The verification of MAC-e/es transport block size selection and that the UE is capable of transmitting all the possible transport block sizes within the UE capability is tested in the MAC-e/es test case 7.1.6.3.2. (UL QPSK), 7.1.6.3.2a (UL 16QAM), 7.1.7.4 (UL QPSK and MAC-i/is) and 7.1.7.5 (UL 16 QAM and MAC-i/is)
14.7.1 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH on DCH
14.7.1.1 Conformance requirement
The UE shall be able to establish the UTRAN requested radio bearers within the UE’s signalled radio access capabilities.
The UE shall correctly transfer user data from peer to peer RLC entities according to the requested radio bearer configuration.
Reference(s)
3GPP TS 25.331, clause 8.2.1
3GPP TS 25.2xx series (Physical Layer)
3GPP TS 25.321 (MAC)
3GPP TS 25.322 (RLC)
14.7.1.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.1:
1. To verify that the UE is able to establish the radio bearer combination.
2. To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.1.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
5 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
6 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
7 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
8 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
9 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
10 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
11 |
3 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
12 |
6 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size. |
||||||||
The generic test procedure in 14.1.4.1 is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
312 |
312 |
|
2 |
2,4 and 6 |
2ms, Table 0 |
8 |
312 |
312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested. |
|||||
14.7.1.4 Test requirements
See 14.1.4.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.
14.7.1a Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL DCH/ UL 16QAM
14.7.1a.1 Conformance requirement
The UE shall be able to establish the UTRAN requested radio bearers within the UE’s signalled radio access capabilities.
The UE shall correctly transfer user data from peer to peer RLC entities according to the requested radio bearer configuration.
Reference(s)
3GPP TS 25.331, clause 8.2.1
3GPP TS 25.2xx series (Physical Layer)
3GPP TS 25.321 (MAC)
3GPP TS 25.322 (RLC)
14.7.1a.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.2:
1. To verify that the UE is able to establish the radio bearer combination.
2. To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.1a.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
7 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS (note 2) |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
5 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
6 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
7 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
8 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
9 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
10 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
11 |
3 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
12 |
6 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size. |
||||||||
The generic test procedure in 14.1.4.1 is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL RLC SDU size (note 2 &4) |
Test data size (note 3) |
|
1 |
7 |
2ms, Table 2 |
8 |
7992 |
312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested. NOTE 4: The UL RLC SDU size is calculated as 25*320-8= 7992, such that TB size 8450 corresponding to E-TFCI 103 will be selected. With PLnon-max = 0.84, [(8450+24[CRC] ) *3 [TC] ]= 25422 bits. 25422* PLnon-max =21355 , this guarantees as per algorithm in 25.212 clause 4.8.4.1,16QAM to be selected [2M2+2M4] |
|||||
14.7.1a.4 Test requirements
See 14.1.4.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU with first 312 bits equal to the content of the DL RLC SDU sent by the SS.
14.7.2 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL DCH
14.7.2.1 Conformance requirement
See 14.7.1.1.
14.7.2.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.2:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.2.3 Method of test
See 14.7.1.3.
14.7.2.4 Test requirements
See 14.7.1.4.
14.7.3 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH
14.7.3.1 Conformance requirement
See 14.7.1.1.
14.7.3.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.3:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.3.3 Method of test
See 14.7.1.3.
14.7.3.4 Test requirements
See 14.7.1.4.
14.7.3a Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] with Flexible RLC, MAC-ehs and MAC-i/is / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH with MAC-ehs and MAC-i/is
14.7.3a.1 Conformance requirement
See 14.7.1.1.
14.7.3a.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.3 and for the case when Flexible RLC and MAC-i/is is configured:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.3a.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
Radio bearer |
TS 34.108, clause 6.10.2.4.6.3 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-i/is) and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4. |
|
MAC-ehs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
2 |
2 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
3 |
3 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
4 |
3 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
5 |
6 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
6 |
6 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
7 |
6 |
1536 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
8 |
6 |
1536 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
9 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
10 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
11 |
3 |
1024 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
12 |
6 |
1024 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
13 to 20 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size is bigger than the “Minimum TBS” that equals maximum MAC-d PDU size under test + the MAC-ehs header size (24 bits). |
||||||||
The generic test procedure in 14.1.4.1b is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
Flexible |
Flexible |
320 |
320 |
|
2 |
2,4 and 6 |
2ms, Table 0 |
8 |
Flexible |
Flexible |
320 |
320 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size. |
|||||||
14.7.3a.4 Test requirements
See 14.1.4.1b for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.
14.7.3b Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] with Flexible RLC, MAC-ehs and MAC-i/is / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH with MAC-ehs and MAC-i/is / UL: QPSK and Dual-Cell DL: 16QAM and Dual-Cell
14.7.3b.1 Conformance requirement
See 14.7.1.1.
14.7.3b.2 Test purpose
When the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.3 is configured for Dual-cell E-DCH and Dual-cell HSDPA, with uplink QPSK, Flexible RLC and MAC-i/is and downlink 16QAM, flexible RLC and MAC-ehs:
1. Verify that the UE is able to establish the radio bearer combination on both cells.
2 Verify correct data transfer of the established radio bearer combination on both cells.
14.7.3b.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-9 IE “E-DCH physical layer category extension 2”.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-8 IE “HS-DSCH physical layer category extension 2”. This IE corresponds to the HS-DSCH category supported by the UE when Dual-Cell and MAC-ehs is configured.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
Radio bearer |
TS 34.108, clause 6.10.2.4.6.3 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-i/is) and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4. |
|
MAC-ehs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
8 |
1536 |
|
9 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
21 to 24 |
6 |
2047 |
336 |
360 |
1 |
16QAM |
1 |
0 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size is bigger than the “Minimum TBS” that equals maximum MAC-d PDU size under test + the MAC-ehs header size (24 bits). |
||||||||
The generic test procedure in 14.1.4.1c is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
8 and 9 |
2ms, Table 0 |
8 |
Flexible |
Flexible |
320 |
320 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size. |
|||||||
14.7.3b.4 Test requirements
See 14.1.4.1c for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.
14.7.3c Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] with Flexible RLC, MAC-ehs and MAC-i/is / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH with MAC-ehs and MAC-i/is / UL: 16QAM and Dual-Cell DL: 16QAM and Dual-Cell
14.7.3c.1 Conformance requirement
See 14.7.1.1.
14.7.3c.2 Test purpose
When the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.3 is configured for Dual-cell E-DCH and Dual-cell HSDPA, with uplink 16QAM, Flexible RLC and MAC-i/is and downlink 16QAM, flexible RLC and MAC-ehs:
1. Verify that the UE is able to establish the radio bearer combination on both cells.
2 Verify correct data transfer of the established radio bearer combination on both cells.
14.7.3c.3 Method of test
NOTE 1: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-9 IE “E-DCH physical layer category extension 2”.
NOTE 2: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-8 IE “HS-DSCH physical layer category extension 2”. This IE corresponds to the HS-DSCH category supported by the UE when Dual-Cell and MAC-ehs is configured.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
Radio bearer |
TS 34.108, clause 6.10.2.4.6.3 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-i/is) and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4. |
|
MAC-ehs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
9 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
21 to 24 |
6 |
2047 |
336 |
360 |
1 |
16QAM |
1 |
0 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size is bigger than the “Minimum TBS” that equals maximum MAC-d PDU size under test + the MAC-ehs header size (24 bits). |
||||||||
The generic test procedure in 14.1.4.1c is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2 & 4) |
Test data size (note 3) |
|
1 |
9 |
2ms, Table 0 |
8 |
Flexible |
Flexible |
7992 |
312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size. NOTE 4: The UL RLC SDU size is calculated as 25*320-8= 7992, with the UL RLC ACK (status) PDU of 336 bits and 32 bits of MAC-is, MAC-i headers such that TB size 8810 corresponding to E-TFCI 104 will be selected. With PLnon-max = 0.84, [((8810+24[CRC] )/2[numblocks] ) *3 [TC] +12[Trellis bits]*2[numblocks] = 26526 bits. 26526 * PLnon-max = 22281.84, this guarantees as per algorithm in 25.212 clause 4.8.4.1,16QAM to be selected [2M2+2M4] |
|||||||
14.7.3c.4 Test requirements
See 14.1.4.1c for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.
14.7.4 Conversational / speech / UL:12.2 DL:12.2 kbps / CS RAB + Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH
14.7.4.1 Conformance requirement
See 14.7.1.1.
14.7.4.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.4:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH in combination with the possible TFCI of the conversional speech radio bearer.
14.7.4.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The following parameters are specific for this test case:
Uplink TFS:
|
RB5 (RAB subflow #1) |
RB6 (RAB subflow #2) |
RB7 (RAB subflow #3) |
DCCH |
||
|
TFS |
TF0, bits |
1×0 |
0x103 |
0x60 |
0x148 |
|
TF1, bits |
1×39 |
1×103 |
1×60 |
1×148 |
|
|
TF2, bits |
1×81 |
N/A |
N/A |
N/A |
Uplink TFCS:
|
TFCI |
(RB5, RB6, RB7, DCCH) |
|
UL_TFC0 |
(TF0, TF0, TF0, TF0) |
|
UL_TFC1 |
(TF1, TF0, TF0, TF0) |
|
UL_TFC2 |
(TF2, TF1, TF1, TF0) |
|
UL_TFC3 |
(TF0, TF0, TF0, TF1) |
|
UL_TFC4 |
(TF1, TF0, TF0, TF1) |
|
UL_TFC5 |
(TF2, TF1, TF1, TF1) |
Downlink TFS:
|
RB5 (RAB subflow #1) |
RB6 (RAB subflow #2) |
RB7 (RAB subflow #3) |
DCCH |
||
|
TFS |
TF0, bits |
1×0 |
0x103 |
0x60 |
0x148 |
|
TF1, bits |
1×39 |
1×103 |
1×60 |
1×148 |
|
|
TF2, bits |
1×81 |
N/A |
N/A |
N/A |
Downlink TFCS:
|
TFCI |
(RB5, RB6, RB7, DCCH) |
|
DL_TFC0 |
(TF0, TF0, TF0, TF0) |
|
DL_TFC1 |
(TF1, TF0, TF0, TF0) |
|
DL_TFC2 |
(TF2, TF1, TF1, TF0) |
|
DL_TFC3 |
(TF0, TF0, TF0, TF1) |
|
DL_TFC4 |
(TF1, TF0, TF0, TF1) |
|
DL_TFC5 |
(TF2, TF1, TF1, TF1) |
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
5 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
6 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
7 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
8 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
9 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
10 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
11 |
3 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
12 |
6 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size (“Minimum TBS”) is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size. |
||||||||
The generic test procedure in 14.1.4.1 is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
DCH |
UL RLC SDU size (note 3) |
Test data size (note 4) |
|||
|
DL TFCS Under test |
UL TFCS Under test |
Implicitly tested |
Restricted UL TFCIs (note 2) |
||||||
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
DL_TFC1 |
UL_TFC1 |
DL_TFC0, DL_TFC3, UL_TFC0, UL_TFC3 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC3, UL_TFC4 |
RB5: 39 RB6: 103 RB7: 60 RB8: 312 |
RB5: 39 RB6: No data RB7: No data RB8: 312 |
|
2 |
1 to 6 |
10ms, Table 0 |
4 |
DL_TFC2 |
UL_TFC2 |
DL_TFC0, DL_TFC3, UL_TFC0, UL_TFC3 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC3, UL_TFC5 |
RB5: 81 RB6: 103 RB7: 60 RB8: 312 |
RB5: 81 RB6: 103 RB7: 60 RB8: 312 |
|
3 |
2, 4 and 6 |
2ms, Table 0 |
8 |
DL_TFC1 |
UL_TFC1 |
DL_TFC0, DL_TFC3, UL_TFC0, UL_TFC3 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC3 UL_TFC4 |
RB5: 39 RB6: 103 RB7: 60 RB8: 312 |
RB5: 39 RB6: No data RB7: No data RB8: 312 |
|
4 |
2, 4 and 6 |
2ms, Table 0 |
8 |
DL_TFC2 |
UL_TFC2 |
DL_TFC0, DL_TFC3, UL_TFC0, UL_TFC3 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC3, UL_TFC5 |
RB5: 81 RB6: 103 RB7: 60 RB8: 312 |
RB5: 81 RB6: 103 RB7: 60 RB8: 312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: UL_TFC0, UL_TFC1, UL_TFC2 and UL_TFC3 are part of minimum set of TFCIs. NOTE 3: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 4: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested. |
|||||||||
14.7.4.4 Test requirements
See 14.1.4.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At steps 17 to 20 the UE transmitted transport format shall be within the set of restricted TFCIs as specified for the sub-test.
3. At step 18 and for each radio bearer where test data is sent in downlink the UE shall return a RLC SDU with same content as sent in downlink. For radio bearers where no data is sent in downlink then no data shall be received in uplink.
14.7.5 Streaming or interactive or background / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL:3.4 kbps SRBs for DCCH on E-DCH and DL DCH
14.7.5.1 Conformance requirement
See 14.7.1.1.
14.7.5.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.5:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.5.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The first Streaming or background or interactive / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5 and the second Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6.
The following parameters are specific for this test case and RB5 and RB6:
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
5 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
6 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
7 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
8 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
9 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
10 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
11 |
3 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
12 |
6 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size (“Minimum TBS”) is bigger than the maximum MAC-d PDU size under test + the MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336) for recommended TFRC values for different transport block size. |
||||||||
The generic test procedure in 14.1.4.1 is run for each sub-test.
Sub-tests:
|
Sub-test |
E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL RLC SDU size (note 2) |
Test data size (note 2) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:312 RB6:312 |
RB5:312 RB6:312 |
|
2 |
2,4 and 6 |
2ms, Table 0 |
8 |
RB5:312 RB6:312 |
RB5:312 RB6:312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested. |
|||||
14.7.5.4 Test requirements
See 14.1.4.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU on RB5 and RB6 with same content as sent in downlink.
14.7.6 Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Streaming or Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL: :[max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH
14.7.6.1 Conformance requirement
See 14.7.1.1.
14.7.6.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.6:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.6.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5 and the Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6
The following parameters are specific for this test case and RB5 and RB6:
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
RB5: HS-DSCH MAC-d PDU size |
See sub-test table |
|
RB6: HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS (note 2) |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
2 |
2 |
512 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
3 |
3 |
512 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
4 |
3 |
512 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
5 |
6 |
512 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
6 |
6 |
512 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
7 |
6 |
1536 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
8 |
6 |
1536 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
9 |
6 |
2047 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
10 |
6 |
2047 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
11 |
3 |
1024 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
12 |
6 |
1024 |
344 |
365 |
1 |
QPSK |
1 |
19 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-hs transport block size (“Minimum TBS”) is bigger than the maximum MAC-d PDU size under test + the MAC-hs header size. NOTE 2: For RB5 (UM) the maximum MAC-d PDU size is 344 and the MAC-hs header size is 21 bits, this result in the maximum required TBS for RB5 of 365 bits. For RB6 (AM) the maximum MAC-d PDU size is 336 and the MAC-hs header size is 21 bits, this result in the maximum required TBS for RB6 of 357 bits. The HS-PDSCH TFRC need to be selected for a TBS bigger or equal to 365. |
||||||||
The generic test procedure in 14.1.4.1 is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:96 RB6:336 |
RB5:112 RB6:336 |
RB5:80 RB6:312 |
RB5:96 RB6:312 |
|
2 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:112 RB6:336 |
RB5:112 RB6:336 |
RB5:96 RB6:312 |
RB5:96 RB6:312 |
|
3 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:144 RB6:336 |
RB5:144 RB6:336 |
RB5:128 RB6:312 |
RB5:128 RB6:312 |
|
4 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:160 RB6:336 |
RB5:160 RB6:336 |
RB5:144 RB6:312 |
RB5:144 RB6:312 |
|
5 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:176 RB6:336 |
RB5:176 RB6:336 |
RB5:160 RB6:312 |
RB5:160 RB6:312 |
|
6 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:192 RB6:336 |
RB5:192 RB6:336 |
RB5:176 RB6:312 |
RB5:176 RB6:312 |
|
7 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:208 RB6:336 |
RB5:224 RB6:336 |
RB5:192 RB6:312 |
RB5:208 RB6:312 |
|
8 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:224 RB6:336 |
RB5:224 RB6:336 |
RB5:208 RB6:312 |
RB5:208 RB6:312 |
|
9 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:288 RB6:336 |
RB5:296 RB6:336 |
RB5:272 RB6:312 |
RB5:280 RB6:312 |
|
10 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:296 RB6:336 |
RB5:296 RB6:336 |
RB5:280 RB6:312 |
RB5:280 RB6:312 |
|
11 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:312 RB6:336 |
RB5:344 RB6:336 |
RB5:296 RB6:312 |
RB5:328 RB6:312 |
|
12 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:344 RB6:336 |
RB5:344 RB6:336 |
RB5:328 RB6:312 |
RB5:328 RB6:312 |
|
13 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:96 RB6:336 |
RB5:112 RB6:336 |
RB5:80 RB6:312 |
RB5:96 RB6:312 |
|
14 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:112 RB6:336 |
RB5:112 RB6:336 |
RB5:96 RB6:312 |
RB5:96 RB6:312 |
|
15 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:144 RB6:336 |
RB5:144 RB6:336 |
RB5:128 RB6:312 |
RB5:128 RB6:312 |
|
16 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:160 RB6:336 |
RB5:160 RB6:336 |
RB5:144 RB6:312 |
RB5:144 RB6:312 |
|
17 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:176 RB6:336 |
RB5:176 RB6:336 |
RB5:160 RB6:312 |
RB5:160 RB6:312 |
|
18 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:192 RB6:336 |
RB5:192 RB6:336 |
RB5:176 RB6:312 |
RB5:176 RB6:312 |
|
19 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:208 RB6:336 |
RB5:224 RB6:336 |
RB5:192 RB6:312 |
RB5:208 RB6:312 |
|
20 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:224 RB6:336 |
RB5:224 RB6:336 |
RB5:208 RB6:312 |
RB5:208 RB6:312 |
|
21 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:288 RB6:336 |
RB5:296 RB6:336 |
RB5:272 RB6:312 |
RB5:280 RB6:312 |
|
22 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:296 RB6:336 |
RB5:296 RB6:336 |
RB5:280 RB6:312 |
RB5:280 RB6:312 |
|
23 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:312 RB6:336 |
RB5:344 RB6:336 |
RB5:296 RB6:312 |
RB5:328 RB6:312 |
|
24 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:344 RB6:336 |
RB5:344 RB6:336 |
RB5:328 RB6:312 |
RB5:328 RB6:312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size minus 8 bits (size of 7 bit length indicator and expansion bit). |
|||||||
14.7.6.4 Test requirements
See 14.1.4.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU on RB5 and RB6 with same content as sent in downlink. For the case the returned UL RLC SDU size under test is smaller than the sent DL RLC SDU size then the payload of the received UL RLC SDU shall have the same content as the first N bits of the DL RLC SDU payload, where N equals the payload size of the UL RLC SDU.
14.7.6a Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Streaming or Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL: :[max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH/ UL 16QAM
14.7.6a.1 Conformance requirement
See 14.7.1.1.
14.7.6a.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.6:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.6a.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-7 IE “E-DCH physical layer category extension”.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5 and the Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6
The following parameters are specific for this test case and RB5 and RB6:
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
RB5: HS-DSCH MAC-d PDU size |
See sub-test table |
|
RB6: HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
7 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
||||
|
Max MAC-d PDU size |
Max MAC-d PDU size |
Max MAC-d PDU size |
Max MAC-d PDU size |
Max MAC-d PDU size |
|||
|
1 |
2 |
512 |
344 |
365 |
1 |
QPSK |
1 |
|
2 |
2 |
512 |
344 |
365 |
1 |
QPSK |
1 |
|
3 |
3 |
512 |
344 |
365 |
1 |
QPSK |
1 |
|
4 |
3 |
512 |
344 |
365 |
1 |
QPSK |
1 |
|
5 |
6 |
512 |
344 |
365 |
1 |
QPSK |
1 |
|
6 |
6 |
512 |
344 |
365 |
1 |
QPSK |
1 |
|
7 |
6 |
1536 |
344 |
365 |
1 |
QPSK |
1 |
|
8 |
6 |
1536 |
344 |
365 |
1 |
QPSK |
1 |
|
9 |
6 |
2047 |
344 |
365 |
1 |
QPSK |
1 |
|
10 |
6 |
2047 |
344 |
365 |
1 |
QPSK |
1 |
|
11 |
3 |
1024 |
344 |
365 |
1 |
QPSK |
1 |
|
12 |
6 |
1024 |
344 |
365 |
1 |
QPSK |
1 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-hs transport block size (“Minimum TBS”) is bigger than the maximum MAC-d PDU size under test + the MAC-hs header size. NOTE 2: For RB5 (UM) the maximum MAC-d PDU size is 344 and the MAC-hs header size is 21 bits, this result in the maximum required TBS for RB5 of 365 bits. For RB6 (AM) the maximum MAC-d PDU size is 336 and the MAC-hs header size is 21 bits, this result in the maximum required TBS for RB6 of 357 bits. The HS-PDSCH TFRC need to be selected for a TBS bigger or equal to 365. |
|||||||
The generic test procedure in 14.1.4.1 is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
7 |
2ms, Table 2 |
8 |
RB5:96 RB6:336 |
RB5:112 RB6:336 |
RB5:80 RB6: 7992 |
RB5:96 RB6:312 |
|
2 |
7 |
2ms, Table 2 |
8 |
RB5:112 RB6:336 |
RB5:112 RB6:336 |
RB5:96 RB6: 7992 |
RB5:96 RB6:312 |
|
3 |
7 |
2ms, Table 2 |
8 |
RB5:144 RB6:336 |
RB5:144 RB6:336 |
RB5:128 RB6: 7992 |
RB5:128 RB6:312 |
|
4 |
7 |
2ms, Table 2 |
8 |
RB5:160 RB6:336 |
RB5:160 RB6:336 |
RB5:144 RB6: 7992 |
RB5:144 RB6:312 |
|
5 |
7 |
2ms, Table 2 |
8 |
RB5:176 RB6:336 |
RB5:176 RB6:336 |
RB5:160 RB6: 7992 |
RB5:160 RB6:312 |
|
6 |
7 |
2ms, Table 2 |
8 |
RB5:192 RB6:336 |
RB5:192 RB6:336 |
RB5:176 RB6: 7992 |
RB5:176 RB6:312 |
|
7 |
7 |
2ms, Table 2 |
8 |
RB5:208 RB6:336 |
RB5:224 RB6:336 |
RB5:192 RB6: 7992 |
RB5:208 RB6:312 |
|
8 |
7 |
2ms, Table 2 |
8 |
RB5:224 RB6:336 |
RB5:224 RB6:336 |
RB5:208 RB6: 7992 |
RB5:208 RB6:312 |
|
9 |
7 |
2ms, Table 2 |
8 |
RB5:288 RB6:336 |
RB5:296 RB6:336 |
RB5:272 RB6: 7992 |
RB5:280 RB6:312 |
|
10 |
7 |
2ms, Table 2 |
8 |
RB5:296 RB6:336 |
RB5:296 RB6:336 |
RB5:280 RB6: 7992 |
RB5:280 RB6:312 |
|
11 |
7 |
2ms, Table 2 |
8 |
RB5:312 RB6:336 |
RB5:344 RB6:336 |
RB5:296 RB6: 7992 |
RB5:328 RB6:312 |
|
12 |
7 |
2ms, Table 2 |
8 |
RB5:344 RB6:336 |
RB5:344 RB6:336 |
RB5:328 RB6: 7992 |
RB5:328 RB6:312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size minus 8 bits (size of 7 bit length indicator and expansion bit). NOTE 4: The UL RLC SDU size is calculated as 25*320-8= 7992, such that TB size 8450 corresponding to E-TFCI 103 will be selected. With PLnon-max = 0.84, [(8450+24[CRC] ) *3 [TC] ]= 25422 bits. 25422* PLnon-max =21355 , this guarantees as per algorithm in 25.212 clause 4.8.4.1,16QAM to be selected [2M2+2M4] |
|||||||
14.7.6a.4 Test requirements
See 14.1.4.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU on RB5 with same content as sent in downlink and on RB6 with first 312 bits equal to the content of the DL RLC SDU sent by the SS. For the case the returned UL RLC SDU size under test is smaller than the sent DL RLC SDU size then the payload of the received UL RLC SDU shall have the same content as the first N bits of the DL RLC SDU payload, where N equals the payload size of the UL RLC SDU.
14.7.6b Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps with Flexible RLC and MAC-ehs / PS RAB + Streaming or Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] with Fixed RLC and MAC-ehs / PS RAB + UL:[max bit rate depending on UE category and TTI] DL: :[max bit rate depending on UE category] SRBs for DCCH on E-DCH and SRBs with Fixed RLC and MAC-ehs on HS-DSCH / UL: QPSK and DL: QPSK
14.7.6b.1 Conformance requirement
See 14.7.1.1.
14.7.6b.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.6 for the case for the QPSK and non-MIMO case using the downlink enhanced Layer 2 configuration with MAC-ehs and Fixed and Flexible RLC configured:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.6b.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.
The Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5 and the Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6
The following parameters are specific for this test case and RB5 and RB6:
|
Parameter |
Value |
|
Radio bearer |
TS 34.108, clause 6.10.2.4.6.6 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) for RB5; using downlink MAC-d flow parameters according to Alt 2 (Fixed RLC and MAC-ehs) for RB6; and using Alt 2 (Fixed RLC and MAC-ehs) for the SRB#1 to SRB#4. |
|
MAC-ehs receiver window size |
16 |
|
Alternative E-bit interpretation |
TRUE |
|
RB5: HS-DSCH MAC-d PDU size |
See sub-test table |
|
RB6: HS-DSCH MAC-d PDU size |
336 |
|
RB5: DL UM RLC LI size |
7 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS (note 2) |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
2 |
2 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
3 |
3 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
4 |
3 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
5 |
6 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
6 |
6 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
7 |
6 |
1536 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
8 |
6 |
1536 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
9 |
6 |
2047 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
10 |
6 |
2047 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
11 |
3 |
1024 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
12 |
6 |
1024 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
13 to 20 |
6 |
2047 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-hs transport block size (“Minimum TBS”) is bigger than the maximum MAC-d PDU size under test + the MAC-ehs header size. NOTE 2: For RB5 (UM) the maximum MAC-d PDU size is 344 and the MAC-ehs header size is 24 bits, this result in the maximum required TBS for RB5 of 368 bits. For RB6 (AM) the maximum MAC-d PDU size is 336 and the MAC-ehs header size is 24 bits, this result in the maximum required TBS for RB6 of 360 bits. The HS-PDSCH TFRC need to be selected for a TBS bigger or equal to 368. |
||||||||
The generic test procedure in 14.1.4.1a is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:96 RB6:336 |
RB5:Flexible RB6:336 |
RB5:80 RB6:312 |
RB5:96 RB6:312 |
|
2 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:112 RB6:336 |
RB5:Flexible RB6:336 |
RB5:96 RB6:312 |
RB5:96 RB6:312 |
|
3 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:144 RB6:336 |
RB5:Flexible RB6:336 |
RB5:128 RB6:312 |
RB5:128 RB6:312 |
|
4 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:160 RB6:336 |
RB5:Flexible RB6:336 |
RB5:144 RB6:312 |
RB5:144 RB6:312 |
|
5 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:176 RB6:336 |
RB5:Flexible RB6:336 |
RB5:160 RB6:312 |
RB5:160 RB6:312 |
|
6 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:192 RB6:336 |
RB5:Flexible RB6:336 |
RB5:176 RB6:312 |
RB5:176 RB6:312 |
|
7 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:208 RB6:336 |
RB5:Flexible RB6:336 |
RB5:192 RB6:312 |
RB5:208 RB6:312 |
|
8 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:224 RB6:336 |
RB5:Flexible RB6:336 |
RB5:208 RB6:312 |
RB5:208 RB6:312 |
|
9 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:288 RB6:336 |
RB5:Flexible RB6:336 |
RB5:272 RB6:312 |
RB5:280 RB6:312 |
|
10 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:296 RB6:336 |
RB5:Flexible RB6:336 |
RB5:280 RB6:312 |
RB5:280 RB6:312 |
|
11 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:312 RB6:336 |
RB5:Flexible RB6:336 |
RB5:296 RB6:312 |
RB5:328 RB6:312 |
|
12 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:344 RB6:336 |
RB5:Flexible RB6:336 |
RB5:328 RB6:312 |
RB5:328 RB6:312 |
|
13 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:96 RB6:336 |
RB5:Flexible RB6:336 |
RB5:80 RB6:312 |
RB5:96 RB6:312 |
|
14 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:112 RB6:336 |
RB5:Flexible RB6:336 |
RB5:96 RB6:312 |
RB5:96 RB6:312 |
|
15 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:144 RB6:336 |
RB5:Flexible RB6:336 |
RB5:128 RB6:312 |
RB5:128 RB6:312 |
|
16 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:160 RB6:336 |
RB5:Flexible RB6:336 |
RB5:144 RB6:312 |
RB5:144 RB6:312 |
|
17 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:176 RB6:336 |
RB5:Flexible RB6:336 |
RB5:160 RB6:312 |
RB5:160 RB6:312 |
|
18 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:192 RB6:336 |
RB5:Flexible RB6:336 |
RB5:176 RB6:312 |
RB5:176 RB6:312 |
|
19 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:208 RB6:336 |
RB5:Flexible RB6:336 |
RB5:192 RB6:312 |
RB5:208 RB6:312 |
|
20 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:224 RB6:336 |
RB5:Flexible RB6:336 |
RB5:208 RB6:312 |
RB5:208 RB6:312 |
|
21 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:288 RB6:336 |
RB5:Flexible RB6:336 |
RB5:272 RB6:312 |
RB5:280 RB6:312 |
|
22 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:296 RB6:336 |
RB5:Flexible RB6:336 |
RB5:280 RB6:312 |
RB5:280 RB6:312 |
|
23 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:312 RB6:336 |
RB5:Flexible RB6:336 |
RB5:296 RB6:312 |
RB5:328 RB6:312 |
|
24 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:344 RB6:336 |
RB5:Flexible RB6:336 |
RB5:328 RB6:312 |
RB5:328 RB6:312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size minus 8 bits (size of 7 bit length indicator and expansion bit). |
|||||||
14.7.6b.4 Test requirements
See 14.1.4.1a for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU on RB5 and RB6 with same content as sent in downlink. For the case the returned UL RLC SDU size under test is smaller than the sent DL RLC SDU size then the payload of the received UL RLC SDU shall have the same content as the first N bits of the DL RLC SDU payload, where N equals the payload size of the UL RLC SDU.
14.7.6c Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps with Flexible RLC, MAC-ehs and MAC-i/is / PS RAB + Streaming or Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] with Fixed RLC, MAC-ehs and MAC-i/is / PS RAB + UL:[max bit rate depending on UE category and TTI] DL: :[max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH with MAC-ehs and MAC-i/is / UL: QPSK and DL: QPSK
14.7.6c.1 Conformance requirement
See 14.7.1.1.
14.7.6c.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.6 for the case QPSK and non-MIMO case when MAC-ehs and MAC-i/is and the mix of Fixed and Flexible RLC is configured:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.6c.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.
The Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5 and the Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6
The following parameters are specific for this test case and RB5 and RB6:
|
Parameter |
Value |
|
Radio bearer |
TS 34.108, clause 6.10.2.4.6.6 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 2 (Flexible RLC and MAC-i/is) for RB5; using downlink MAC-d flow parameters according to Alt 2 (Fixed RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 2 (Fixed RLC and MAC-i/is) for RB6; and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4. |
|
MAC-ehs receiver window size |
16 |
|
RB5: Alternative E-bit interpretation |
TRUE |
|
RB5: HS-DSCH MAC-d PDU size |
See sub-test table |
|
RB6: HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS (note 2) |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
2 |
2 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
3 |
3 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
4 |
3 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
5 |
6 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
6 |
6 |
512 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
7 |
6 |
1536 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
8 |
6 |
1536 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
9 |
6 |
2047 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
10 |
6 |
2047 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
11 |
3 |
1024 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
12 |
6 |
1024 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
13 to 20 |
6 |
2047 |
344 |
368 |
1 |
QPSK |
1 |
31 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size (“Minimum TBS”) is bigger than the maximum MAC-d PDU size under test + the MAC-ehs header size. NOTE 2: For RB5 (UM) the maximum MAC-d PDU size is 344 and the MAC-ehs header size is 24 bits, this result in the maximum required TBS for RB5 of 368 bits. For RB6 (AM) the maximum MAC-d PDU size is 336 and the MAC-ehs header size is 24 bits, this result in the maximum required TBS for RB6 of 360 bits. The HS-PDSCH TFRC need to be selected for a TBS bigger or equal to 368. |
||||||||
The generic test procedure in 14.1.4.1b is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:88 RB6:320 |
RB5:104 RB6:320 |
|
2 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:104 RB6:320 |
RB5:104 RB6:320 |
|
3 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:136 RB6:320 |
RB5:136 RB6:320 |
|
4 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:152 RB6:320 |
RB5:152 RB6:320 |
|
5 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:168 RB6:320 |
RB5:168 RB6:320 |
|
6 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:184 RB6:320 |
RB5:184 RB6:320 |
|
7 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:200 RB6:320 |
RB5:216 RB6:320 |
|
8 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:216 RB6:320 |
RB5:216 RB6:320 |
|
9 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:280 RB6:320 |
RB5:288 RB6:320 |
|
10 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:288 RB6:320 |
RB5:288 RB6:320 |
|
11 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:304 RB6:320 |
RB5:336 RB6:320 |
|
12 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:336 RB6:320 |
RB5:336 RB6:320 |
|
13 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:88 RB6:320 |
RB5:104 RB6:320 |
|
14 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:104 RB6:320 |
RB5:104 RB6:320 |
|
15 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:136 RB6:320 |
RB5:136 RB6:320 |
|
16 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:152 RB6:320 |
RB5:152 RB6:320 |
|
17 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:168 RB6:320 |
RB5:168 RB6:320 |
|
18 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:184 RB6:320 |
RB5:184 RB6:320 |
|
19 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:200 RB6:320 |
RB5:216 RB6:320 |
|
20 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:216 RB6:320 |
RB5:216 RB6:320 |
|
21 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:280 RB6:320 |
RB5:288 RB6:320 |
|
22 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:288 RB6:320 |
RB5:288 RB6:320 |
|
23 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:304 RB6:320 |
RB5:336 RB6:320 |
|
24 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:Flexible RB6:336 |
RB5:Flexible RB6:336 |
RB5:336 RB6:320 |
RB5:336 RB6:320 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size. The selected DL test data sizes for RB5 are the same as specified for the DL fixed case (Alt 2) of the reference radio bearer configuration in TS 34.108, clause 6.10.2.4.6.6 (104, 136, 152, 168, 184, 216, 288 and 336). |
|||||||
14.7.6c.4 Test requirements
See 14.1.4.1b for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU on RB5 and RB6 with same content as sent in downlink. For the case the returned UL RLC SDU size under test is smaller than the sent DL RLC SDU size then the payload of the received UL RLC SDU shall have the same content as the first N bits of the DL RLC SDU payload, where N equals the payload size of the UL RLC SDU.
14.7.7 Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB + Streaming or Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + Streaming or Interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:[max bit rate depending on UE category and TTI] DL: :[max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH
14.7.7.1 Conformance requirement
See 14.7.1.1.
14.7.7.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.7:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.7.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The Conversational / unknown or speech / UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to as RB5, the first Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB6 and the second the first Streaming or interactive or background UL:[max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] kbps / PS RAB is referred to RB7.
The following parameters are specific for this test case and RB5, RB6 and RB7:
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
RB5: HS-DSCH MAC-d PDU size |
See sub-test table |
|
RB6: HS-DSCH MAC-d PDU size |
336 |
|
RB7: HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS (note 2) |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
5 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
6 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
7 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
8 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
9 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
10 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
11 |
3 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
12 |
6 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-hs transport block size (“Minimum TBS”) is bigger than the maximum MAC-d PDU size under test + the MAC-hs header size. NOTE 2: For RB5 (UM) the maximum MAC-d PDU size is 336 and the MAC-hs header size is 21 bits, this result in the maximum required TBS for RB5 of 357 bits. For RB6 and RB7 the maximum MAC-d PDU size is 336 and the MAC-hs header size is 21 bits, this result in the maximum required TBS for RB6 of 357 bits. The HS-PDSCH TFRC need to be selected for a TBS bigger or equal to 357. |
||||||||
The generic test procedure in 14.1.4.1 is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:96 RB6:336 RB7:336 |
RB5:112 RB6:336 RB7:336 |
RB5:80 RB6:312 RB7:312 |
RB5:96 RB6:312 RB7:312 |
|
2 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:112 RB6:336 RB7:336 |
RB5:112 RB6:336 RB7:336 |
RB5:96 RB6:312 RB7:312 |
RB5:96 RB6:312 RB7:312 |
|
3 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:144 RB6:336 RB7:336 |
RB5:144 RB6:336 RB7:336 |
RB5:128 RB6:312 RB7:312 |
RB5:128 RB6:312 RB7:312 |
|
4 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:160 RB6:336 RB7:336 |
RB5:160 RB6:336 RB7:336 |
RB5:144 RB6:312 RB7:312 |
RB5:144 RB6:312 RB7:312 |
|
5 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:176 RB6:336 RB7:336 |
RB5:176 RB6:336 RB7:336 |
RB5:160 RB6:312 RB7:312 |
RB5:160 RB6:312 RB7:312 |
|
6 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:192 RB6:336 RB7:336 |
RB5:192 RB6:336 RB7:336 |
RB5:176 RB6:312 RB7:312 |
RB5:176 RB6:312 RB7:312 |
|
7 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:208 RB6:336 RB7:336 |
RB5:224 RB6:336 RB7:336 |
RB5:192 RB6:312 RB7:312 |
RB5:208 RB6:312 RB7:312 |
|
8 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:224 RB6:336 RB7:336 |
RB5:224 RB6:336 RB7:336 |
RB5:208 RB6:312 RB7:312 |
RB5:208 RB6:312 RB7:312 |
|
9 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:288 RB6:336 RB7:336 |
RB5:296 RB6:336 RB7:336 |
RB5:272 RB6:312 RB7:312 |
RB5:280 RB6:312 RB7:312 |
|
10 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:296 RB6:336 RB7:336 |
RB5:296 RB6:336 RB7:336 |
RB5:280 RB6:312 RB7:312 |
RB5:280 RB6:312 RB7:312 |
|
11 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:312 RB6:336 RB7:336 |
RB5:336 RB6:336 RB7:336 |
RB5:296 RB6:312 RB7:312 |
RB5:320 RB6:312 RB7:312 |
|
12 |
1 to 6 |
10ms, Table 0 |
4 |
RB5:336 RB6:336 RB7:336 |
RB5:336 RB6:336 RB7:336 |
RB5:320 RB6:312 RB7:312 |
RB5:320 RB6:312 RB7:312 |
|
13 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:96 RB6:336 RB7:336 |
RB5:112 RB6:336 RB7:336 |
RB5:80 RB6:312 RB7:312 |
RB5:96 RB6:312 RB7:312 |
|
14 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:112 RB6:336 RB7:336 |
RB5:112 RB6:336 RB7:336 |
RB5:96 RB6:312 RB7:312 |
RB5:96 RB6:312 RB7:312 |
|
15 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:144 RB6:336 RB7:336 |
RB5:144 RB6:336 RB7:336 |
RB5:128 RB6:312 RB7:312 |
RB5:128 RB6:312 RB7:312 |
|
16 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:160 RB6:336 RB7:336 |
RB5:160 RB6:336 RB7:336 |
RB5:144 RB6:312 RB7:312 |
RB5:144 RB6:312 RB7:312 |
|
17 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:176 RB6:336 RB7:336 |
RB5:176 RB6:336 RB7:336 |
RB5:160 RB6:312 RB7:312 |
RB5:160 RB6:312 RB7:312 |
|
18 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:192 RB6:336 RB7:336 |
RB5:192 RB6:336 RB7:336 |
RB5:176 RB6:312 RB7:312 |
RB5:176 RB6:312 RB7:312 |
|
19 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:208 RB6:336 RB7:336 |
RB5:224 RB6:336 RB7:336 |
RB5:192 RB6:312 RB7:312 |
RB5:208 RB6:312 RB7:312 |
|
20 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:224 RB6:336 RB7:336 |
RB5:224 RB6:336 RB7:336 |
RB5:208 RB6:312 RB7:312 |
RB5:208 RB6:312 RB7:312 |
|
21 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:288 RB6:336 RB7:336 |
RB5:296 RB6:336 RB7:336 |
RB5:272 RB6:312 RB7:312 |
RB5:280 RB6:312 RB7:312 |
|
22 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:296 RB6:336 RB7:336 |
RB5:296 RB6:336 RB7:336 |
RB5:280 RB6:312 RB7:312 |
RB5:280 RB6:312 RB7:312 |
|
23 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:312 RB6:336 RB7:336 |
RB5:336 RB6:336 RB7:336 |
RB5:296 RB6:312 RB7:312 |
RB5:320 RB6:312 RB7:312 |
|
24 |
2,4,6 |
2ms, Table 0 |
8 |
RB5:336 RB6:336 RB7:336 |
RB5:336 RB6:336 RB7:336 |
RB5:320 RB6:312 RB7:312 |
RB5:320 RB6:312 RB7:312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size minus 8 bits (size of 7 bit length indicator and expansion bit). |
|||||||
Specific Message Contents
Use the same RADIO BEARER SETUP message as specified in 34.108 using condition A16 with the following exceptions:
|
– RAB information for setup |
The IE “RAB information for setup” shall be present in addition to the IE “RAB information for setup” present in the default message for condition A16. This means that three RABs shall be established. |
|
– RAB info |
(high-speed AM DTCH for PS domain) |
|
– RAB identity |
0000 0111B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
|
– CN domain identity |
PS domain |
|
– NAS Synchronization Indicator |
Not Present |
|
– Re-establishment timer |
useT315 |
|
– RB information to setup |
|
|
– RB identity |
27 |
|
– PDCP info |
Not Present |
|
– CHOICE RLC info type |
RLC info |
|
– CHOICE Uplink RLC mode |
AM RLC |
|
– Transmission RLC discard |
|
|
– Transmission RLC discard |
|
|
– CHOICE SDU discard mode |
No Discard |
|
– MAX_DAT |
15 |
|
– Transmission window size |
256 |
|
– Timer_RST |
500 |
|
– Max_RST |
4 |
|
– Polling info |
|
|
– Timer_poll_prohibit |
100 |
|
– Timer_poll |
100 |
|
– Poll_PDU |
Not Present |
|
– Poll_SDU |
1 |
|
– Last transmission PDU poll |
TRUE |
|
– Last retransmission PDU poll |
TRUE |
|
– Poll_Windows |
99 |
|
– Timer_poll_periodic |
Not Present |
|
– CHOICE Downlink RLC mode |
AM RLC |
|
– CHOICE Downlink RLC PDU Size |
Reference to clause 6 Parameter Set |
|
– In-sequence delivery |
TRUE |
|
– Receiving window size |
768 |
|
– Downlink RLC status info |
|
|
– Timer_status_prohibit |
100 |
|
– Timer_EPC |
Not Present |
|
– Missing PDU indicator |
TRUE |
|
– Timer_STATUS_periodic |
Not Present |
|
– One sided RLC re-establishment |
FALSE |
|
– RB mapping info |
|
|
– Information for each multiplexing option |
1 RBMuxOption |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
E-DCH |
|
– Logical channel identity |
8 |
|
– E-DCH MAC-d flow identity |
4 |
|
– DDI |
7 |
|
– RLC PDU size list |
1 RLC PDU size |
|
– RLC PDU size |
336 bits |
|
– Include in scheduling info |
TRUE |
|
– MAC logical channel priority |
8 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
HS-DSCH |
|
– DL DCH Transport channel identity |
Not present |
|
– DL DSCH Transport channel identity |
Not present |
|
– DL HS-DSCH MAC-d flow identity |
3 |
|
– Logical channel identity |
Not Present |
|
Added or Reconfigured UL TrCH information |
1 E-DCH added with one DCCH MAC-d flow and three DTCH MAC-d flows |
|
– Uplink transport channel type |
E-DCH |
|
– CHOICE UL parameters |
E-DCH |
|
– E-DCH Transmission Time Interval |
10 ms |
|
– HARQ info for E-DCH |
|
|
– HARQ RV Configuration |
rvtable |
|
– Added or reconfigured E-DCH MAC-d flow |
(for DCCH) |
|
– E-DCH MAC-d flow identity |
1 |
|
– E-DCH MAC-d flow power offset |
0 |
|
– E-DCH MAC-d flow maximum number of retransmissions |
7 |
|
– E-DCH MAC-d flow multiplexing list |
Not Present |
|
– CHOICE transmission grant type |
Non-scheduled grant info |
|
– Max MAC-e PDU contents size |
162 bits |
|
– 2 ms non-scheduled transmission grant HARQ process allocation |
Not Present |
|
– Uplink transport channel type |
E-DCH |
|
– CHOICE UL parameters |
E-DCH |
|
– E-DCH Transmission Time Interval |
10 ms |
|
– HARQ info for E-DCH |
|
|
– HARQ RV Configuration |
rvtable |
|
– Added or reconfigured E-DCH MAC-d flow |
(for first DTCH) |
|
– E-DCH MAC-d flow identity |
2 |
|
– E-DCH MAC-d flow power offset |
0 |
|
– E-DCH MAC-d flow maximum number of retransmissions |
7 |
|
– E-DCH MAC-d flow multiplexing list |
Not Present |
|
– CHOICE transmission grant type |
Scheduled grant info |
|
– Added or reconfigured E-DCH MAC-d flow |
(for second DTCH) |
|
– E-DCH MAC-d flow identity |
3 |
|
– E-DCH MAC-d flow power offset |
0 |
|
– E-DCH MAC-d flow maximum number of retransmissions |
7 |
|
– E-DCH MAC-d flow multiplexing list |
Not Present |
|
– CHOICE transmission grant type |
Scheduled grant info |
|
– Added or reconfigured E-DCH MAC-d flow |
(for third DTCH) |
|
– E-DCH MAC-d flow identity |
4 |
|
– E-DCH MAC-d flow power offset |
0 |
|
– E-DCH MAC-d flow maximum number of retransmissions |
7 |
|
– E-DCH MAC-d flow multiplexing list |
Not Present |
|
– CHOICE transmission grant type |
Scheduled grant info |
|
Added or Reconfigured DL TrCH information |
1 TrCH (HS-DSCH for DTCH and DCCH) |
|
– Downlink transport channel type |
HS-DSCH |
|
– DL Transport channel identity |
Not Present |
|
– CHOICE DL parameters |
HS-DSCH |
|
– HARQ Info |
|
|
– Number of Processes |
Reference to clause 6.10.2.4.5 Parameter Set |
|
– CHOICE Memory Partitioning |
Implicit |
|
– Added or reconfigured MAC-d flow |
|
|
– MAC-hs queue to add or reconfigure list |
(four queues) |
|
– MAC-hs queue Id |
0 (for first DTCH) |
|
– MAC-d Flow Identity |
0 |
|
– T1 |
50 |
|
– MAC-hs window size |
16 |
|
– MAC-d PDU size Info |
|
|
– MAC-d PDU size |
336 |
|
– MAC-d PDU size index |
0 |
|
– MAC-hs queue Id |
1 (for DCCH) |
|
– MAC-d Flow Identity |
1 |
|
– T1 |
50 |
|
– MAC-hs window size |
16 |
|
– MAC-d PDU size Info |
|
|
– MAC-d PDU size |
148 |
|
– MAC-d PDU size index |
0 |
|
– MAC-hs queue Id |
2 (for second DTCH) |
|
– MAC-d Flow Identity |
0 |
|
– T1 |
50 |
|
– MAC-hs window size |
16 |
|
– MAC-d PDU size Info |
|
|
– MAC-d PDU size |
336 |
|
– MAC-d PDU size index |
0 |
|
– MAC-hs queue Id |
3 (for third DTCH) |
|
– MAC-d Flow Identity |
0 |
|
– T1 |
50 |
|
– MAC-hs window size |
16 |
|
– MAC-d PDU size Info |
|
|
– MAC-d PDU size |
336 |
|
– MAC-d PDU size index |
0 |
|
– MAC-hs queue to delete list |
Not present |
|
– DCH quality target |
Not present |
14.7.7.4 Test requirements
See 14.1.4.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU on RB5, RB6 and RB7 with same content as sent in downlink. For the case the returned UL RLC SDU size under test is smaller than the sent DL RLC SDU size then the payload of the received UL RLC SDU shall have the same content as the first N bits of the DL RLC SDU payload, where N equals the payload size of the UL RLC SDU.
14.7.8 Conversational / speech / UL:(12.65 8.85 6.6) DL:(12.65 8.85 6.6) kbps / CS RAB + Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH + DL:0.15 kbps SRB#5 for DCCH
14.7.8.1 Conformance requirement
See 14.7.1.1.
14.7.8.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.8:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to E-DCH.
14.7.8.3 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The following parameters are specific for this test case:
Uplink TFS:
|
TFI |
RB5 (RAB subflow #1) |
RB6 (RAB subflow #2) |
RB7 (RAB subflow #3) |
DCCH 3.4 |
|
|
TFS |
TF0, bits |
0x72 |
0x181 |
0x60 |
0x148 |
|
TF1, bits |
1×40 |
1×78 |
N/A |
1×148 |
|
|
TF2, bits |
1×54 |
1×113 |
N/A |
N/A |
|
|
TF3, bits |
1×64 |
1×181 |
N/A |
N/A |
|
|
TF4, bits |
1×72 |
N/A |
N/A |
N/A |
Uplink TFCS:
|
TFCI |
(RB5, RB6, RB7, DCCH 3.4) |
|
UL_TFC0 |
(TF0,TF0,TF0,TF0) |
|
UL_TFC1 |
(TF1,TF0,TF0,TF0) |
|
UL_TFC2 |
(TF2,TF1,TF0,TF0) |
|
UL_TFC3 |
(TF3,TF2,TF0,TF0) |
|
UL_TFC4 |
(TF4,TF3,TF0,TF0) |
|
UL_TFC5 |
(TF0,TF0,TF0,TF1) |
|
UL_TFC6 |
(TF1,TF0,TF0,TF1) |
|
UL_TFC7 |
(TF2,TF1,TF0,TF1) |
|
UL_TFC8 |
(TF3,TF2,TF0,TF1) |
|
UL_TFC9 |
(TF4,TF3,TF0,TF1) |
Downlink TFS:
|
RB5 (RAB subflow #1) |
RB6 (RAB subflow #2) |
RB7 (RAB subflow #3) |
DCCH 3.4 |
DCCH 0.15 (SRB #5) |
||
|
TFS |
TF0, bits |
1×0 |
0x181 |
0x60 |
0x148 |
0x3 |
|
TF1, bits |
1×40 |
1×78 |
N/A |
1×148 |
1×3 |
|
|
TF2, bits |
1×54 |
1×113 |
N/A |
N/A |
N/A |
|
|
TF3, bits |
1×64 |
1×181 |
N/A |
N/A |
N/A |
|
|
TF4, bits |
1×72 |
N/A |
N/A |
N/A |
N/A |
Downlink TFCS:
|
TFCI |
(RB5, RB6, RB7,DCCH 3.4, DCCH 0.15) |
|
DL_TFC0 |
(TF0,TF0,TF0,TF0,TF0) |
|
DL_TFC1 |
(TF1,TF0,TF0,TF0,TF0) |
|
DL_TFC2 |
(TF2,TF1,TF0,TF0,TF0) |
|
DL_TFC3 |
(TF3,TF2,TF0,TF0,TF0) |
|
DL_TFC4 |
(TF4,TF3,TF0,TF0,TF0) |
|
DL_TFC5 |
(TF0,TF0,TF0,TF1,TF0) |
|
DL_TFC6 |
(TF1,TF0,TF0,TF1,TF0) |
|
DL_TFC7 |
(TF2,TF1,TF0,TF1,TF0) |
|
DL_TFC8 |
(TF3,TF2,TF0,TF1,TF0) |
|
DL_TFC9 |
(TF4,TF3,TF0,TF1,TF0) |
|
DL_TFC10 |
(TF0,TF0,TF0,TF0,TF1) |
|
DL_TFC11 |
(TF1,TF0,TF0,TF0,TF1) |
|
DL_TFC12 |
(TF2,TF1,TF0,TF0,TF1) |
|
DL_TFC13 |
(TF3,TF2,TF0,TF0,TF1) |
|
DL_TFC14 |
(TF4,TF3,TF0,TF0,TF1) |
|
DL_TFC15 |
(TF0,TF0,TF0,TF1,TF1) |
|
DL_TFC16 |
(TF1,TF0,TF0,TF1,TF1) |
|
DL_TFC17 |
(TF2,TF1,TF0,TF1,TF1) |
|
DL_TFC18 |
(TF3,TF2,TF0,TF1,TF1) |
|
DL_TFC19 |
(TF4,TF3,TF0,TF1,TF1) |
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
5 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
6 |
6 |
512 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
7 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
8 |
6 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
9 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
10 |
6 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
11 |
3 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
12 |
6 |
1024 |
336 |
357 |
1 |
QPSK |
1 |
19 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size (“Minimum TBS”) is bigger than the maximum MAC-d PDU size under test data + RLC, MAC-d and MAC-hs header size (21 bits). See 14.1.3.3 (MAC-d PDU size=336). |
||||||||
The generic test procedure in 14.1.4.2 is run for each sub-test.
Sub-tests:
The principle used to select sub-tests has been to cover all uplink and downlink TFS for the Speech radio bearer.
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
DCH |
UL RLC SDU size (note 3) |
Test data size (note 4) |
|||
|
DL TFCS Under test |
UL TFCS Under test |
Implicitly tested |
TFC subset identity (note 5) |
||||||
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
DL_TFC1 |
UL_TFC1 |
DL_TFC0, DL_TFC5, DL_TFC6, DL_TFC10, UL_TFC0, UL_TFC5, UL_TFC6 |
0 |
RB5: 40 RB6: 181 RB7: 60 RB8: 312 |
RB5: 40 RB6: No data RB7: No data RB8: 312 |
|
2 |
1 to 6 |
10ms, Table 0 |
4 |
DL_TFC2 |
UL_TFC2 |
DL_TFC0, DL_TFC5, DL_TFC7, DL_TFC10, UL_TFC0, UL_TFC5, UL_TFC7 |
0 |
RB5: 54 RB6: 78 RB7: 60 RB8: 312 |
RB5: 54 RB6: 78 RB7: No data RB8: 312 |
|
3 |
2,4 and 6 |
2ms, Table 0 |
8 |
DL_TFC3 |
UL_TFC3 |
DL_TFC0, DL_TFC5, DL_TFC8, DL_TFC10, UL_TFC0, UL_TFC5, UL_TFC8 |
1 |
RB5: 64 RB6: 113 RB7: 60 RB8: 312 |
RB5: 64 RB6: 113 RB7: No data RB8: 312 |
|
4 |
2,4 and 6 |
2ms, Table 0 |
8 |
DL_TFC4 |
UL_TFC4 |
DL_TFC0, DL_TFC5, DL_TFC9, DL_TFC10, UL_TFC0, UL_TFC5, UL_TFC9 |
2 |
RB5: 72 RB6: 181 RB7: 60 RB8: 312 |
RB5: 72 RB6: 181 RB7: No data RB8: 312 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: Void NOTE 3: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 4: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested. NOTE 5: TFC subset identity shall be signalled by the SS on the downlink SRB#5, see generic test procedure in clause 14.1.4.2. |
|||||||||
14.7.8.4 Test requirements
See 14.1.4.2 for definition of step numbers. For each sub-test:
1. At step 20 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At steps 26 the UE transmitted transport format shall be within the set of restricted TFCIs as specified for the sub-test.
3. At step 26 and for each radio bearer where test data is sent in downlink the UE shall return a RLC SDU with same content as sent in downlink. For radio bearers where no data is sent in downlink then no data shall be received in uplink.
14.7.9 Conversational / speech / UL:(12.2, 7.95, 5.9, 4.75) kbps DL: (12.2, 7.95, 5.9, 4.75) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH
14.7.9.1 Conformance requirement
See 14.7.1.1.
14.7.9.2 Test purpose
To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.9 (Alt.2)
14.7.9.3 Method of test
The following parameters are specific for this test case:
|
E-DCH Category |
RLC Transmission window size |
Modulation Scheme |
|
1 |
512 |
QPSK |
|
2 |
512 |
|
|
3 |
512 |
|
|
4 |
512 |
|
|
5 |
1536 |
|
|
6 |
1536 |
|
|
7 |
1536 |
|
HS-DSCH Category |
Number of HARQ processes |
RLC Receiving window size |
|
1 |
2 |
512 |
|
2 |
2 |
512 |
|
3 |
3 |
512 |
|
4 |
3 |
512 |
|
5 |
6 |
512 |
|
6 |
6 |
512 |
|
7 |
6 |
1536 |
|
8 |
6 |
1536 |
|
9 |
6 |
2047 |
|
10 |
6 |
2047 |
|
11 |
3 |
1024 |
|
12 |
6 |
1024 |
|
13 to 20 |
6 |
2047 |
|
HS-PDSCH TFRC for mac-ehs (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|
56 |
80 |
1 |
QPSK |
1 |
0 |
|
112 |
136 |
1 |
QPSK |
1 |
2 |
|
136 |
160 |
1 |
QPSK |
1 |
5 |
|
176 |
200 |
1 |
QPSK |
1 |
10 |
|
264 |
288 |
1 |
QPSK |
1 |
21 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-ehs transport block size is equal to or bigger than the maximum MAC-d PDU size under test + MAC-ehs header size (24 bits). |
|||||
The generic test procedure in 14.1.4.1a is run for each sub-test using condition A23 for radio bearer setup, as specified in 34.108.
Testing of UE supporting UE HS-DSCH physical layer category 13 to 20 shall be performed in accordance to test parameters, sub-tests and test points for UE HS-DSCH physical layer category 10.
Testing of UE supporting UE E-DCH category 7 shall be performed in accordance to test parameters, sub-tests and test points for E-DCH category 6.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
MAC-d PDU size under test ( UL and DL ) |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 7 |
10ms, Table 0 |
4 |
56 |
40 |
40 |
|
2 |
1 to 7 |
10ms, Table 0 |
4 |
112 |
96 |
96 |
|
3 |
1 to 7 |
10ms, Table 0 |
4 |
136 |
120 |
120 |
|
4 |
1 to 7 |
10ms, Table 0 |
4 |
176 |
160 |
160 |
|
5 |
1 to 7 |
10ms, Table 0 |
4 |
264 |
248 |
248 |
|
6 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
56 |
40 |
40 |
|
7 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
112 |
96 |
96 |
|
8 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
136 |
120 |
120 |
|
9 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
176 |
160 |
160 |
|
10 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
264 |
248 |
248 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested. |
||||||
14.7.9.4 Test requirements
See 14.1.4.1a for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU on RB5 with same content as sent in downlink.
14.7.10 Conversational / speech / UL:(12.65, 8.85, 6.6) kbps DL: (12.65, 8.85, 6.6) kbps / CS RAB on E-DCH and HS-DSCH + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH
14.7.10.1 Conformance requirement
See 14.7.1.1.
14.7.10.2 Test purpose
To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.10 (Alt.2)
14.7.10.3 Method of test
The following parameters are specific for this test case:
|
E-DCH Category |
RLC Transmission window size |
Modulation Scheme |
|
1 |
512 |
QPSK |
|
2 |
512 |
|
|
3 |
512 |
|
|
4 |
512 |
|
|
5 |
1536 |
|
|
6 |
1536 |
|
|
7 |
1536 |
|
HS-DSCH Category |
Number of HARQ processes |
RLC Receiving window size |
|
1 |
2 |
512 |
|
2 |
2 |
512 |
|
3 |
3 |
512 |
|
4 |
3 |
512 |
|
5 |
6 |
512 |
|
6 |
6 |
512 |
|
7 |
6 |
1536 |
|
8 |
6 |
1536 |
|
9 |
6 |
2047 |
|
10 |
6 |
2047 |
|
11 |
3 |
1024 |
|
12 |
6 |
1024 |
|
13 to 20 |
6 |
2047 |
|
HS-PDSCH TFRC for mac-ehs (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|
56 |
80 |
1 |
QPSK |
1 |
0 |
|
152 |
176 |
1 |
QPSK |
1 |
7 |
|
200 |
224 |
1 |
QPSK |
1 |
13 |
|
272 |
296 |
1 |
QPSK |
1 |
22 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-ehs transport block size is equal to or bigger than the maximum MAC-d PDU size under test + MAC-ehs header size (24 bits). |
|||||
The generic test procedure in 14.1.4.1a is run for each sub-test using condition A23 for radio bearer setup, as specified in 34.108.
Testing of UE supporting UE HS-DSCH physical layer category 13 to 20 shall be performed in accordance to test parameters, sub-tests and test points for UE HS-DSCH physical layer category 10.
Testing of UE supporting UE E-DCH category 7 shall be performed in accordance to test parameters, sub-tests and test points for E-DCH category 6.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
MAC-d PDU size under test ( UL and DL ) |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 7 |
10ms, Table 0 |
4 |
56 |
40 |
40 |
|
2 |
1 to 7 |
10ms, Table 0 |
4 |
152 |
136 |
136 |
|
3 |
1 to 7 |
10ms, Table 0 |
4 |
200 |
184 |
184 |
|
4 |
1 to 7 |
10ms, Table 0 |
4 |
272 |
256 |
256 |
|
5 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
56 |
40 |
40 |
|
6 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
152 |
136 |
136 |
|
7 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
200 |
184 |
184 |
|
8 |
2,4, 6, 7 |
2ms, Table 0 |
8 |
272 |
256 |
256 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH selected according to the MAC-d PDU size to be tested. |
||||||
14.7.10.4 Test requirements
See 14.1.4.1a for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU on RB5 with same content as sent in downlink.
14.7.11 Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on E-DCH and HS-DSCH for enhanced uplink/downlink in CELL_FACH
14.7.11.1 Conformance requirement
Conformance requirement
See 14.7.1.1
14.7.11.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.3:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer using all the possible MAC-d PDU sizes of the transport channel mapped to common E-DCH in CELL_FACH.
14.7.11.3 Method of test
NOTE 1: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE 2: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
Radio bearer |
TS 34.108, clause 6.10.2.4.6.3 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-i/is) and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4. |
|
MAC-ehs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
6 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
2 |
2 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
3 |
3 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
4 |
3 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
5 |
6 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
6 |
6 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
7 |
6 |
1536 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
8 |
6 |
1536 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
9 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
10 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
11 |
3 |
1024 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
12 |
6 |
1024 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
13 to 20 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size is bigger than the “Minimum TBS” that equals maximum MAC-d PDU size under test + the MAC-ehs header size (24 bits). |
||||||||
The generic test procedure in 14.1.4.3 is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
Flexible |
Flexible |
320 |
320 |
|
2 |
2,4 and 6 |
2ms, Table 0 |
8 |
Flexible |
Flexible |
320 |
320 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size. |
|||||||
14.7.11.4 Test requirements
See 14.1.5.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.
14.7.11a Streaming or interactive or background / UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] / PS RAB + UL: [max bit rate depending on UE category and TTI] DL: [max bit rate depending on UE category] SRBs for DCCH on common E-DCH and HS-DSCH for enhanced CELL_FACH with DRX configured
14.7.11a.1 Conformance requirement
Conformance requirement
See 14.7.1.1
14.7.11a.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.6.3:
1. To verify that the UE is able to establish the radio bearer combination.
2 To verify correct data transfer corresponding to Enhanced DRX reception pattern by UE when transport channel is mapped to common E-DCH in CELL_FACH.
14.7.11a.3 Method of test
NOTE 1: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6.
NOTE 2: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-7 IE “HS-DSCH physical layer category extension”. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is configured.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
Radio bearer |
TS 34.108, clause 6.10.2.4.6.3 using downlink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-ehs) and uplink MAC-d flow parameters according to Alt 3 (Flexible RLC and MAC-i/is) and using downlink Alt 2 (Fixed RLC and MAC-ehs) and uplink Alt 2 (Fixed RLC and MAC-i/is) for the SRB#1 to SRB#4. |
|
MAC-ehs receiver window size |
16 |
|
HS-DSCH MAC-d PDU size |
336 |
|
E-DCH Category |
RLC Transmission window size |
|
1 |
512 |
|
2 |
512 |
|
3 |
512 |
|
4 |
512 |
|
5 |
1536 |
|
16 |
1536 |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size |
HS-PDSCH TFRC (note 1) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
|||
|
1 |
2 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
2 |
2 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
3 |
3 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
4 |
3 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
5 |
6 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
6 |
6 |
512 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
7 |
6 |
1536 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
8 |
6 |
1536 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
9 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
10 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
11 |
3 |
1024 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
12 |
6 |
1024 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
13 to 20 |
6 |
2047 |
336 |
360 |
1 |
QPSK |
1 |
30 |
|
NOTE 1: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI considering all sub-tests. i.e. such that the MAC-ehs transport block size is bigger than the “Minimum TBS” that equals maximum MAC-d PDU size under test + the MAC-ehs header size (24 bits). |
||||||||
The generic test procedure in 14.1.4.3 is run for each sub-test.
Sub-tests:
|
Sub-test |
Applicable E-DCH Category |
E-DPDCH TTI and E-TFCI Table (note 1) |
E-DPDCH Number of HARQ processes |
UL MAC-d PDU size under test |
DL MAC-d PDU size under test |
UL RLC SDU size (note 2) |
Test data size (note 3) |
|
1 |
1 to 6 |
10ms, Table 0 |
4 |
Flexible |
Flexible |
320 |
320 |
|
2 |
2,4 and 6 |
2ms, Table 0 |
8 |
Flexible |
Flexible |
320 |
320 |
|
NOTE 1: E-DPDCH TTI and E-TFCI table according to TS 25.321 Annex B. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. NOTE 3: The test data size is for DTCH mapped to E-DCH is selected according to the MAC-d PDU size to be tested = DL RLC payload size for the MAC-d PDU size. |
|||||||
Specific Message Contents
Use the default parameter values for the system information block 5 with the same type specified in clause
6.1.1 of TS 34.108 for common E-DCH and HS-DSCH reception in CELL_FACH, with the following exceptions
|
Information Element |
Value/remark |
|
HS-DSCH DRX in CELL_FACH Information |
|
|
-T321 |
200ms |
|
– HS-DSCH DRX cycleFACH |
4 |
|
– HS-DSCH Rx burstFACH |
1 |
|
– DRX Interruption by HS-DSCH data |
FALSE |
14.7.11a.4 Test requirements
See 14.1.5.1 for definition of step 12 and step 18.
1. At step 12 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 18 the UE shall return a RLC SDU with same content as sent in downlink.