18.2.8 Combinations on DPCH, HS-DSCH and E-PUCH
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
18.2.8.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
18.2.8.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)
18.2.8.1.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.3.4.7.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.
18.2.8.1.3 Method of test
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 |
1536 |
|
5 |
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 HS-DSCH timeslots |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
5 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
6 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
7 |
3 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
8 |
3 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
9 |
3 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
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 18.2.7.1.1 (MAC-d PDU size=336) for recommended TFRC values for different transport block size. |
||||||||
The generic test procedure in 18.2.1.5 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 5 |
10ms, Table 0 |
4 |
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. |
|||||
18.2.8.1.4 Test requirements
See 18.2.1.5 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.
18.2.8.2 Void
18.2.8.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
18.2.8.3.1 Conformance requirement
See 18.2.8.1.1.
18.2.8.3.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.3.4.7.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.
18.2.8.3.3 Method of test
See 18.2.8.1.3.
18.2.8.3.4 Test requirements
See 18.2.8.1.4.
18.2.8.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
18.2.8.4.1 Conformance requirement
See 18.2.8.1.1.
18.2.8.4.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.3.4.7.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.
18.2.8.4.3 Method of test
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 HS-DSCH timeslots |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
5 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
6 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
7 |
3 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
8 |
3 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
9 |
3 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
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 18.2.7.1.1 (MAC-d PDU size=336) for recommended TFRC values for different transport block size. |
||||||||
The generic test procedure in 18.2.1.5 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 5 |
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 5 |
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 |
|
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. |
|||||||||
18.2.8.4.4 Test requirements
See 18.2.1.5 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.
18.2.8.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
18.2.8.5.1 Conformance requirement
See 18.2.8.1.1.
18.2.8.5.2 Test purpose
For the reference radio bearer configuration as specified in TS 34.108, clause 6.10.3.4.7.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.
18.2.8.5.3 Method of test
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 HS-DSCH timeslots |
TFRI |
|||
|
1 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
2 |
2 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
3 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
4 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
5 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
6 |
3 |
512 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
7 |
3 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
8 |
3 |
1536 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
9 |
3 |
2047 |
336 |
357 |
1 |
QPSK |
1 |
126 |
|
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 18.2.7.1.1 (MAC-d PDU size=336) for recommended TFRC values for different transport block size. |
||||||||
The generic test procedure in 18.2.1.5 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 5 |
10ms, Table 0 |
4 |
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. |
|||||
18.2.8.5.4 Test requirements
See 18.2.1.5 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.