14.1.3 General information interoperability radio bearer tests for HS-DSCH
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
14.1.3.1 HS-DSCH radio bearer test parameters
In the radio bearer tests on radio bearers mapped on HS-DSCH, the following UE specific parameters should be used.
Table 14.1.3.1.1: FDD HS-DSCH physical layer parameters for FDD HS-DSCH physical layer categories
HS-DSCH category |
Maximum number of HS-DSCH codes received |
Minimum inter-TTI interval |
Maximum number of bits of an HS-DSCH transport block received within an HS-DSCH TTI |
Total number of soft channel bits |
Supported modula-tions without MIMO operation |
Supported modula-tions with MIMO operation and without dual cell operation |
Supported modula-tions with dual cell operation |
Supported modula-tions with simulta-neous dual cell and MIMO operation |
---|---|---|---|---|---|---|---|---|
Category 1 |
5 |
3 |
7298 |
19200 |
QPSK, 16QAM |
Not applicable |
Not applicable (dual cell operation not supported) |
Not applicable (simultaneous dual cell and MIMO operation not supported) |
Category 2 |
5 |
3 |
7298 |
28800 |
||||
Category 3 |
5 |
2 |
7298 |
28800 |
||||
Category 4 |
5 |
2 |
7298 |
38400 |
||||
Category 5 |
5 |
1 |
7298 |
57600 |
||||
Category 6 |
5 |
1 |
7298 |
67200 |
||||
Category 7 |
10 |
1 |
14411 |
115200 |
||||
Category 8 |
10 |
1 |
14411 |
134400 |
||||
Category 9 |
15 |
1 |
20251 |
172800 |
||||
Category 10 |
15 |
1 |
27952 |
172800 |
||||
Category 11 |
5 |
2 |
3630 |
14400 |
QPSK |
|||
Category 12 |
5 |
1 |
3630 |
28800 |
||||
Category 13 |
15 |
1 |
35280 |
259200 |
QPSK, 16QAM, 64QAM |
|||
Category 14 |
15 |
1 |
42192 |
259200 |
||||
Category 15 |
15 |
1 |
23370 |
345600 |
QPSK, 16QAM |
|||
Category 16 |
15 |
1 |
27952 |
345600 |
||||
Category 17 NOTE 2 |
15 |
1 |
35280 |
259200 |
QPSK, 16QAM, 64QAM |
– |
||
23370 |
345600 |
– |
QPSK, 16QAM |
|||||
Category 18 NOTE 3 |
15 |
1 |
42192 |
259200 |
QPSK, 16QAM, 64QAM |
– |
||
27952 |
345600 |
– |
QPSK, 16QAM |
|||||
Category 19 |
15 |
1 |
35280 |
518400 |
QPSK, 16QAM, 64QAM |
|||
Category 20 |
15 |
1 |
42192 |
518400 |
||||
Category 21 |
15 |
1 |
23370 |
345600 |
– |
– |
QPSK, 16QAM |
|
Category 22 |
15 |
1 |
27952 |
345600 |
||||
Category 23 |
15 |
1 |
35280 |
518400 |
QPSK, 16QAM, 64QAM |
|||
Category 24 |
15 |
1 |
42192 |
518400 |
||||
Category 25 |
15 |
1 |
23370 |
691200 |
– |
– |
– |
QPSK, 16QAM |
Category 26 |
15 |
1 |
27952 |
691200 |
||||
Category 27 |
15 |
1 |
35280 |
1036800 |
– |
– |
– |
QPSK, 16QAM, 64QAM |
Category 28 |
15 |
1 |
42192 |
1036800 |
NOTE 1: Depending on the HS-DSCH configuration, the indicated maximum number of bits of an HS-DSCH transport block does not have to correspond exactly to an entry in the transport block size table to be applied [9].
NOTE 2: A UE of category 17 supports the physical capabilities of categories 13 and 15, but not simultaneously. The first row of category 17 in table 5.1a specifies the capabilities when MIMO is not configured and the capabilities of category 13 apply, the second row specifies the capabilities when MIMO is configured and the capabilities of category 15 apply.
NOTE 3: A UE of category 18 supports the physical capabilities of categories 14 and 16, but not simultaneously. The first row of category 18 in table 5.1a specifies the capabilities when MIMO is not configured and the capabilities of category 14 apply, the second row specifies the capabilities when MIMO is configured and the capabilities of category 16 apply.
14.1.3.2 Selecting TFRC test points
14.1.3.2.1 Principle for non-enhanced Layer 2
The transport format and resource combination (TFRC) is identified by the UE by the type of modulation, number of channalisation codes and the transport format and resource identifier (TFRI) signalled on the HS-SCCH.
For the HSDPA radio bearer test cases the principle for selecting typical test points for TFRC is:
1. Select one TFRC per modulation scheme and number of MAC-d PDUs.
2. For each number of MAC-d PDUs select the TFRC minimizing padding.
3. Any TFRC that would cause turbo coder irregularities should be avoided.
The problem with turbo coder regularities appears at certain coding rates. The coding rate for a certain TFCR is:
, where
TBsize is the selected transport block,
NCRC is the number of CRC bits,
Ncodes is the number of channelistion codes, and
Nphy_bits is the number physical bits per code (960 for QPSK, 1920 for 16QAM and 2880 for 64 QAM).
Table 14.1.3.2.1 lists the coding rates that cause turbo coder irregularities. In case a candidate TFRC value is causing turbo coder irregularities then the closest higher TFRI value, which do not cause any turbo coder irregularities, is selected.
Table 14.1.3.2.1: Coding rates causing degradation due to turbo coder irregularities
Coding rate |
Comment |
0.77-0.79 |
Cause loss up to 3.5 dB |
0.835-0.84 |
Cause loss up to 1.5 dB |
0.871-0.878 |
Cause loss up to 2 dB |
0.91-0.914 |
Cause loss up to 2 dB |
NOTE The coding rates in Table 14.2.3.2.1 is based on the simulations as described in RAN WG1 document R1-030444 (Turbo-coding and puncturing interactions on HS-DSCH in R5 HSDPA)
The selection algorithm for the TFRC test points for a certain UE category and MAC-d PDU size is:
1. Set the number of MAC-d PDUs, N_PDU, to 1
2. Calculate the minimum transport block size to fit the number of MAC-d PDUs.
3. If the transport block size is less or equal to the UE capability for “Maximum number of bits of an HS-DSCH transport block received within an HS-DSCH TTI” in Table 14.1.3.1.1 then continue with step 4 else there is no more testing points.
4. Select the QPSK test point:
If it, for the actual UE category and for the selected transport block size, exists a TFRI for QPSK then select the TFRI that maximises the number of codes.
5. Select the 16QAM test point:
If it, for the actual UE category and for the selected transport block size, exists a TFRI for 16QAM then select the TFRI that maximises the number of codes.
6. Check that the coding rate for the selected TFRC does not cause turbo coder irregularities, see Table 14.1.3.2.1. If the coding rate is ok then accept the testing point and continue with step 8 else continue with step 7.
7. If the coding rate is not ok then select the next higher TFRI value that corresponds to an acceptable coding rate. Calculate the transport block size correspondent to the modified TFRI values and if it is less or equal to the UE capability for “Maximum number of bits of an HS-DSCH transport block received within an HS-DSCH TTI” in Table 14.1.3.1.1 then accept the testing point else skip it.
8. Increment N_PDUs. If N_PDU is less or equal to 70 then repeat from step 2 else there are no more testing points.
14.1.3.2.1a Principle for enhanced Layer 2
For the combination of MAC-ehs and Fixed RLC then the same principle to select test points as for the non-enhanced Layer 2 case as described in sub-clause 14.1.3.2.1 is used (MAC-d PDU size 336 and 656 bits).
For the combination of MAC-ehs and Flexible RLC then the same TFRI test points as for the fixed MAC-d PDU size=656 bits case are used.
14.1.3.3 TFRC test points for MAC-d PDU size=336
Table 14.1.3.3.1: TFRC test points for UE category 1 to UE category 6 for MAC-d PDU size=336
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
---|---|---|---|---|---|
1 |
365 |
QPSK |
1 |
19 |
|
2 |
699 |
QPSK |
2 |
8 |
|
2 |
699 |
16QAM |
1 |
8 |
|
3 |
1036 |
QPSK |
3 |
7 |
|
3 |
1036 |
16QAM |
1 |
30 |
|
4 |
1380 |
QPSK |
4 |
7 |
|
4 |
1380 |
16QAM |
2 |
7 |
|
5 |
1711 |
QPSK |
5 |
6 |
|
5 |
1711 |
16QAM |
2 |
19 |
|
6 |
2046 |
QPSK |
5 |
16 |
|
6 |
2046 |
16QAM |
3 |
6 |
|
7 |
2404 |
QPSK |
5 |
25 |
|
7 |
2404 |
16QAM |
3 |
15 |
|
8 |
2726 |
QPSK |
5 |
32 |
|
8 |
2726 |
16QAM |
4 |
6 |
|
9 |
3090 |
QPSK |
5 |
39 |
|
9 |
3090 |
16QAM |
5 |
0 |
|
10 |
3440 |
QPSK |
5 |
45 |
|
10 |
3440 |
16QAM |
5 |
6 |
|
11 |
3830 |
QPSK |
5 |
51 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.78875) would have given 3.5 dB due to turbo coder irregularities. TFRI=51 is selected. |
11 |
3762 |
16QAM |
5 |
11 |
|
12 |
4115 |
QPSK |
5 |
55 |
|
12 |
4115 |
16QAM |
5 |
16 |
|
13 |
4420 |
QPSK |
5 |
59 |
|
13 |
4420 |
16QAM |
5 |
20 |
|
14 |
4748 |
16QAM |
5 |
24 |
|
15 |
5101 |
16QAM |
5 |
28 |
|
16 |
5480 |
16QAM |
5 |
32 |
|
17 |
5782 |
16QAM |
5 |
35 |
|
18 |
6101 |
16QAM |
5 |
38 |
|
19 |
6438 |
16QAM |
5 |
41 |
|
20 |
6793 |
16QAM |
5 |
44 |
|
21 |
7168 |
16QAM |
5 |
47 |
Table 14.1.3.3.2: TFRC test points for UE category 7 and UE category 8 for MAC-d PDU size=336
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
---|---|---|---|---|---|
1 |
365 |
QPSK |
1 |
19 |
|
2 |
699 |
QPSK |
2 |
8 |
|
2 |
699 |
16QAM |
1 |
8 |
|
3 |
1036 |
QPSK |
3 |
7 |
|
3 |
1036 |
16QAM |
1 |
30 |
|
4 |
1380 |
QPSK |
4 |
7 |
|
4 |
1380 |
16QAM |
2 |
7 |
|
5 |
1711 |
QPSK |
5 |
6 |
|
5 |
1711 |
16QAM |
2 |
19 |
|
6 |
2046 |
QPSK |
6 |
6 |
|
6 |
2046 |
16QAM |
3 |
6 |
|
7 |
2404 |
QPSK |
7 |
6 |
|
7 |
2404 |
16QAM |
3 |
15 |
|
8 |
2726 |
QPSK |
8 |
6 |
|
8 |
2726 |
16QAM |
4 |
6 |
|
9 |
3090 |
QPSK |
10 |
0 |
|
9 |
3090 |
16QAM |
5 |
0 |
|
10 |
3440 |
QPSK |
10 |
6 |
|
10 |
3440 |
16QAM |
5 |
6 |
|
11 |
3762 |
QPSK |
10 |
11 |
|
11 |
3762 |
16QAM |
6 |
1 |
|
12 |
4115 |
QPSK |
10 |
16 |
|
12 |
4115 |
16QAM |
6 |
6 |
|
13 |
4420 |
QPSK |
10 |
20 |
|
13 |
4420 |
16QAM |
7 |
1 |
|
14 |
4748 |
QPSK |
10 |
24 |
|
14 |
4748 |
16QAM |
7 |
5 |
|
15 |
5101 |
QPSK |
10 |
28 |
|
15 |
5101 |
16QAM |
8 |
2 |
|
16 |
5480 |
QPSK |
10 |
32 |
|
16 |
5480 |
16QAM |
8 |
6 |
|
17 |
5782 |
QPSK |
10 |
35 |
|
17 |
5782 |
16QAM |
9 |
2 |
|
18 |
6101 |
QPSK |
10 |
38 |
|
18 |
6101 |
16QAM |
10 |
0 |
|
19 |
6438 |
QPSK |
10 |
41 |
|
19 |
6438 |
16QAM |
10 |
3 |
|
20 |
6793 |
QPSK |
10 |
44 |
|
20 |
6793 |
16QAM |
10 |
6 |
|
21 |
7168 |
QPSK |
10 |
47 |
|
21 |
7168 |
16QAM |
10 |
9 |
|
22 |
7564 |
QPSK |
10 |
50 |
TFRI = 49 would have minimised padding but is not acceptable as the coding rate (0.7765) would have given 3.5 dB due to turbo coder irregularities. TFRI=50 is selected. |
22 |
7430 |
16QAM |
10 |
11 |
|
23 |
7981 |
QPSK |
10 |
52 |
|
23 |
7840 |
16QAM |
10 |
14 |
|
24 |
8125 |
QPSK |
10 |
54 |
|
24 |
8125 |
16QAM |
10 |
16 |
|
25 |
8422 |
QPSK |
10 |
56 |
|
25 |
8422 |
16QAM |
10 |
18 |
|
26 |
8886 |
QPSK |
10 |
59 |
|
26 |
8886 |
16QAM |
10 |
21 |
|
27 |
9210 |
QPSK |
10 |
61 |
|
27 |
9210 |
16QAM |
10 |
23 |
|
28 |
9546 |
16QAM |
10 |
25 |
|
29 |
9894 |
16QAM |
10 |
27 |
|
30 |
10255 |
16QAM |
10 |
29 |
|
31 |
10440 |
16QAM |
10 |
30 |
|
32 |
10821 |
16QAM |
10 |
32 |
|
33 |
11216 |
16QAM |
10 |
34 |
|
34 |
11625 |
16QAM |
10 |
36 |
|
35 |
11835 |
16QAM |
10 |
37 |
|
36 |
12266 |
16QAM |
10 |
39 |
|
37 |
12488 |
16QAM |
10 |
40 |
|
38 |
12943 |
16QAM |
10 |
42 |
|
39 |
13177 |
16QAM |
10 |
43 |
|
40 |
13657 |
16QAM |
10 |
45 |
|
41 |
13904 |
16QAM |
10 |
46 |
|
42 |
14155 |
16QAM |
10 |
47 |
Table 14.1.3.3.3: TFRC test points for UE category 9 for MAC-d PDU size=336
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
---|---|---|---|---|---|
1 |
365 |
QPSK |
1 |
19 |
|
2 |
699 |
QPSK |
2 |
8 |
|
2 |
699 |
16QAM |
1 |
8 |
|
3 |
1036 |
QPSK |
3 |
7 |
|
3 |
1036 |
16QAM |
1 |
30 |
|
4 |
1380 |
QPSK |
4 |
7 |
|
4 |
1380 |
16QAM |
2 |
7 |
|
5 |
1711 |
QPSK |
5 |
6 |
|
5 |
1711 |
16QAM |
2 |
19 |
|
6 |
2046 |
QPSK |
6 |
6 |
|
6 |
2046 |
16QAM |
3 |
6 |
|
7 |
2404 |
QPSK |
7 |
6 |
|
7 |
2404 |
16QAM |
3 |
15 |
|
8 |
2726 |
QPSK |
8 |
6 |
|
8 |
2726 |
16QAM |
4 |
6 |
|
9 |
3090 |
QPSK |
10 |
0 |
|
9 |
3090 |
16QAM |
5 |
0 |
|
10 |
3440 |
QPSK |
11 |
1 |
|
10 |
3440 |
16QAM |
5 |
6 |
|
11 |
3762 |
QPSK |
12 |
1 |
|
11 |
3762 |
16QAM |
6 |
1 |
|
12 |
4115 |
QPSK |
13 |
2 |
|
12 |
4115 |
16QAM |
6 |
6 |
|
13 |
4420 |
QPSK |
14 |
1 |
|
13 |
4420 |
16QAM |
7 |
1 |
|
14 |
4748 |
QPSK |
15 |
2 |
|
14 |
4748 |
16QAM |
7 |
5 |
|
15 |
5101 |
QPSK |
15 |
6 |
|
15 |
5101 |
16QAM |
8 |
2 |
|
16 |
5480 |
QPSK |
15 |
10 |
|
16 |
5480 |
16QAM |
8 |
6 |
|
17 |
5782 |
QPSK |
15 |
13 |
|
17 |
5782 |
16QAM |
9 |
2 |
|
18 |
6101 |
QPSK |
15 |
16 |
|
18 |
6101 |
16QAM |
10 |
0 |
|
19 |
6438 |
QPSK |
15 |
19 |
|
19 |
6438 |
16QAM |
10 |
3 |
|
20 |
6793 |
QPSK |
15 |
22 |
|
20 |
6793 |
16QAM |
11 |
0 |
|
21 |
7168 |
QPSK |
15 |
25 |
|
21 |
7168 |
16QAM |
11 |
3 |
|
22 |
7430 |
QPSK |
15 |
27 |
|
22 |
7430 |
16QAM |
12 |
0 |
|
23 |
7840 |
QPSK |
15 |
30 |
|
23 |
7840 |
16QAM |
12 |
3 |
|
24 |
8125 |
QPSK |
15 |
32 |
|
24 |
8125 |
16QAM |
13 |
1 |
|
25 |
8422 |
QPSK |
15 |
34 |
|
25 |
8422 |
16QAM |
13 |
3 |
|
26 |
8886 |
QPSK |
15 |
37 |
|
26 |
8886 |
16QAM |
14 |
2 |
|
27 |
9210 |
QPSK |
15 |
39 |
|
27 |
9210 |
16QAM |
15 |
0 |
|
28 |
9546 |
QPSK |
15 |
41 |
|
28 |
9546 |
16QAM |
15 |
2 |
|
29 |
9894 |
QPSK |
15 |
43 |
|
29 |
9894 |
16QAM |
15 |
4 |
|
30 |
10255 |
QPSK |
15 |
45 |
|
30 |
10255 |
16QAM |
15 |
6 |
|
31 |
10440 |
QPSK |
15 |
46 |
|
31 |
10440 |
16QAM |
15 |
7 |
|
32 |
10821 |
QPSK |
15 |
48 |
|
32 |
10821 |
16QAM |
15 |
9 |
|
33 |
11418 |
QPSK |
15 |
51 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.78056) would have given 3.5 dB due to turbo coder irregularities. TFRI=51 is selected. |
33 |
11216 |
16QAM |
15 |
11 |
|
34 |
11625 |
QPSK |
15 |
52 |
|
34 |
11625 |
16QAM |
15 |
13 |
|
35 |
11835 |
QPSK |
15 |
53 |
|
35 |
11835 |
16QAM |
15 |
14 |
|
36 |
12266 |
QPSK |
15 |
55 |
|
36 |
12266 |
16QAM |
15 |
16 |
|
37 |
12488 |
QPSK |
15 |
56 |
|
37 |
12488 |
16QAM |
15 |
17 |
|
38 |
12943 |
QPSK |
15 |
58 |
|
38 |
12943 |
16QAM |
15 |
19 |
|
39 |
13177 |
QPSK |
15 |
59 |
|
39 |
13177 |
16QAM |
15 |
20 |
|
40 |
13657 |
QPSK |
15 |
61 |
|
40 |
13657 |
16QAM |
15 |
22 |
|
41 |
13904 |
QPSK |
15 |
62 |
|
41 |
13904 |
16QAM |
15 |
23 |
|
42 |
14155 |
16QAM |
15 |
24 |
|
43 |
14671 |
16QAM |
15 |
26 |
|
44 |
14936 |
16QAM |
15 |
27 |
|
45 |
15206 |
16QAM |
15 |
28 |
|
46 |
15481 |
16QAM |
15 |
29 |
|
47 |
16045 |
16QAM |
15 |
31 |
|
48 |
16335 |
16QAM |
15 |
32 |
|
49 |
16630 |
16QAM |
15 |
33 |
|
50 |
16931 |
16QAM |
15 |
34 |
|
51 |
17237 |
16QAM |
15 |
35 |
|
52 |
17548 |
16QAM |
15 |
36 |
|
53 |
17865 |
16QAM |
15 |
37 |
|
54 |
18188 |
16QAM |
15 |
38 |
|
55 |
18517 |
16QAM |
15 |
39 |
|
56 |
18851 |
16QAM |
15 |
40 |
|
57 |
19192 |
16QAM |
15 |
41 |
|
58 |
19538 |
16QAM |
15 |
42 |
|
59 |
19891 |
16QAM |
15 |
43 |
|
60 |
20251 |
16QAM |
15 |
44 |
Table 14.1.3.3.4: TFRC test points for UE category 10 for MAC-d PDU size=336
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
---|---|---|---|---|---|
1 |
365 |
QPSK |
1 |
19 |
|
2 |
699 |
QPSK |
2 |
8 |
|
2 |
699 |
16QAM |
1 |
8 |
|
3 |
1036 |
QPSK |
3 |
7 |
|
3 |
1036 |
16QAM |
1 |
30 |
|
4 |
1380 |
QPSK |
4 |
7 |
|
4 |
1380 |
16QAM |
2 |
7 |
|
5 |
1711 |
QPSK |
5 |
6 |
|
5 |
1711 |
16QAM |
2 |
19 |
|
6 |
2046 |
QPSK |
6 |
6 |
|
6 |
2046 |
16QAM |
3 |
6 |
|
7 |
2404 |
QPSK |
7 |
6 |
|
7 |
2404 |
16QAM |
3 |
15 |
|
8 |
2726 |
QPSK |
8 |
6 |
|
8 |
2726 |
16QAM |
4 |
6 |
|
9 |
3090 |
QPSK |
10 |
0 |
|
9 |
3090 |
16QAM |
5 |
0 |
|
10 |
3440 |
QPSK |
11 |
1 |
|
10 |
3440 |
16QAM |
5 |
6 |
|
11 |
3762 |
QPSK |
12 |
1 |
|
11 |
3762 |
16QAM |
6 |
1 |
|
12 |
4115 |
QPSK |
13 |
2 |
|
12 |
4115 |
16QAM |
6 |
6 |
|
13 |
4420 |
QPSK |
14 |
1 |
|
13 |
4420 |
16QAM |
7 |
1 |
|
14 |
4748 |
QPSK |
15 |
2 |
|
14 |
4748 |
16QAM |
7 |
5 |
|
15 |
5101 |
QPSK |
15 |
6 |
|
15 |
5101 |
16QAM |
8 |
2 |
|
16 |
5480 |
QPSK |
15 |
10 |
|
16 |
5480 |
16QAM |
8 |
6 |
|
17 |
5782 |
QPSK |
15 |
13 |
|
17 |
5782 |
16QAM |
9 |
2 |
|
18 |
6101 |
QPSK |
15 |
16 |
|
18 |
6101 |
16QAM |
10 |
0 |
|
19 |
6438 |
QPSK |
15 |
19 |
|
19 |
6438 |
16QAM |
10 |
3 |
|
20 |
6793 |
QPSK |
15 |
22 |
|
20 |
6793 |
16QAM |
11 |
0 |
|
21 |
7168 |
QPSK |
15 |
25 |
|
21 |
7168 |
16QAM |
11 |
3 |
|
22 |
7430 |
QPSK |
15 |
27 |
|
22 |
7430 |
16QAM |
12 |
0 |
|
23 |
7840 |
QPSK |
15 |
30 |
|
23 |
7840 |
16QAM |
12 |
3 |
|
24 |
8125 |
QPSK |
15 |
32 |
|
24 |
8125 |
16QAM |
13 |
1 |
|
25 |
8422 |
QPSK |
15 |
34 |
|
25 |
8422 |
16QAM |
13 |
3 |
|
26 |
8886 |
QPSK |
15 |
37 |
|
26 |
8886 |
16QAM |
14 |
2 |
|
27 |
9210 |
QPSK |
15 |
39 |
|
27 |
9210 |
16QAM |
15 |
0 |
|
28 |
9546 |
QPSK |
15 |
41 |
|
28 |
9546 |
16QAM |
15 |
2 |
|
29 |
9894 |
QPSK |
15 |
43 |
|
29 |
9894 |
16QAM |
15 |
4 |
|
30 |
10255 |
QPSK |
15 |
45 |
|
30 |
10255 |
16QAM |
15 |
6 |
|
31 |
10440 |
QPSK |
15 |
46 |
|
31 |
10440 |
16QAM |
15 |
7 |
|
32 |
10821 |
QPSK |
15 |
48 |
|
32 |
10821 |
16QAM |
15 |
9 |
|
33 |
11418 |
QPSK |
15 |
51 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.78056) would have given 3.5 dB due to turbo coder irregularities. TFRI=51 is selected. |
33 |
11216 |
16QAM |
15 |
11 |
|
34 |
11625 |
QPSK |
15 |
52 |
|
34 |
11625 |
16QAM |
15 |
13 |
|
35 |
11835 |
QPSK |
15 |
53 |
|
35 |
11835 |
16QAM |
15 |
14 |
|
36 |
12266 |
QPSK |
15 |
55 |
|
36 |
12266 |
16QAM |
15 |
16 |
|
37 |
12488 |
QPSK |
15 |
56 |
|
37 |
12488 |
16QAM |
15 |
17 |
|
38 |
12943 |
QPSK |
15 |
58 |
|
38 |
12943 |
16QAM |
15 |
19 |
|
39 |
13177 |
QPSK |
15 |
59 |
|
39 |
13177 |
16QAM |
15 |
20 |
|
40 |
13657 |
QPSK |
15 |
61 |
|
40 |
13657 |
16QAM |
15 |
22 |
|
41 |
13904 |
QPSK |
15 |
62 |
|
41 |
13904 |
16QAM |
15 |
23 |
|
42 |
14155 |
16QAM |
15 |
24 |
|
43 |
14671 |
16QAM |
15 |
26 |
|
44 |
14936 |
16QAM |
15 |
27 |
|
45 |
15206 |
16QAM |
15 |
28 |
|
46 |
15481 |
16QAM |
15 |
29 |
|
47 |
16045 |
16QAM |
15 |
31 |
|
48 |
16335 |
16QAM |
15 |
32 |
|
49 |
16630 |
16QAM |
15 |
33 |
|
50 |
16931 |
16QAM |
15 |
34 |
|
51 |
17237 |
16QAM |
15 |
35 |
|
52 |
17548 |
16QAM |
15 |
36 |
|
53 |
17865 |
16QAM |
15 |
37 |
|
54 |
18188 |
16QAM |
15 |
38 |
|
55 |
18517 |
16QAM |
15 |
39 |
|
56 |
18851 |
16QAM |
15 |
40 |
|
57 |
19192 |
16QAM |
15 |
41 |
|
58 |
19538 |
16QAM |
15 |
42 |
|
59 |
19891 |
16QAM |
15 |
43 |
|
60 |
20251 |
16QAM |
15 |
44 |
|
61 |
20617 |
16QAM |
15 |
45 |
|
62 |
20989 |
16QAM |
15 |
46 |
|
63 |
21368 |
16QAM |
15 |
47 |
|
64 |
21754 |
16QAM |
15 |
48 |
|
65 |
22147 |
16QAM |
15 |
49 |
|
66 |
22955 |
16QAM |
15 |
51 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.78375) would have given 3.5 dB due to turbo coder irregularities. TFRI=51 is selected. |
67 |
22955 |
16QAM |
15 |
51 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.78375) would have given 3.5 dB due to turbo coder irregularities. TFRI=51 is selected. |
68 |
22955 |
16QAM |
15 |
51 |
|
69 |
23370 |
16QAM |
15 |
52 |
|
70 |
23792 |
16QAM |
15 |
53 |
Table 14.1.3.3.5: TFRC test points for UE category 11 and UE category 12 for MAC-d PDU size=336
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
---|---|---|---|---|---|
1 |
365 |
QPSK |
1 |
19 |
|
2 |
699 |
QPSK |
2 |
8 |
|
3 |
1036 |
QPSK |
3 |
7 |
|
4 |
1380 |
QPSK |
4 |
7 |
|
5 |
1711 |
QPSK |
5 |
6 |
|
6 |
2046 |
QPSK |
5 |
16 |
|
7 |
2404 |
QPSK |
5 |
25 |
|
8 |
2726 |
QPSK |
5 |
32 |
|
9 |
3090 |
QPSK |
5 |
39 |
|
10 |
3440 |
QPSK |
5 |
45 |
14.1.3.4 TFRC test points for MAC-d PDU size=656
Table 14.1.3.4.1: TFRC test points for UE category 1 to UE category 6 for MAC-d PDU size=656
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
1 |
686 |
QPSK |
2 |
7 |
|
1 |
686 |
16QAM |
1 |
7 |
|
2 |
1356 |
QPSK |
4 |
6 |
|
2 |
1356 |
16QAM |
2 |
6 |
|
3 |
2010 |
QPSK |
5 |
15 |
|
3 |
2010 |
16QAM |
3 |
5 |
|
4 |
2677 |
QPSK |
5 |
31 |
|
4 |
2677 |
16QAM |
4 |
5 |
|
5 |
3319 |
QPSK |
5 |
43 |
|
5 |
3319 |
16QAM |
5 |
4 |
|
6 |
3970 |
QPSK |
5 |
53 |
|
6 |
3970 |
16QAM |
5 |
14 |
|
7 |
4664 |
QPSK |
5 |
62 |
|
7 |
4664 |
16QAM |
5 |
23 |
|
8 |
5287 |
16QAM |
5 |
30 |
|
9 |
5993 |
16QAM |
5 |
37 |
|
10 |
6673 |
16QAM |
5 |
43 |
|
11 |
7298 |
16QAM |
5 |
48 |
Table 14.1.3.4.2: TFRC test points for UE category 7 and UE category 8 for MAC-d PDU size=656
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
---|---|---|---|---|---|
1 |
686 |
QPSK |
2 |
7 |
|
1 |
686 |
16QAM |
1 |
7 |
|
2 |
1356 |
QPSK |
4 |
6 |
|
2 |
1356 |
16QAM |
2 |
6 |
|
3 |
2010 |
QPSK |
6 |
5 |
|
3 |
2010 |
16QAM |
3 |
5 |
|
4 |
2677 |
QPSK |
8 |
5 |
|
4 |
2677 |
16QAM |
4 |
5 |
|
5 |
3319 |
QPSK |
10 |
4 |
|
5 |
3319 |
16QAM |
5 |
4 |
|
6 |
3970 |
QPSK |
10 |
14 |
|
6 |
3970 |
16QAM |
6 |
4 |
|
7 |
4664 |
QPSK |
10 |
23 |
|
7 |
4664 |
16QAM |
7 |
4 |
|
8 |
5287 |
QPSK |
10 |
30 |
|
8 |
5287 |
16QAM |
8 |
4 |
|
9 |
5993 |
QPSK |
10 |
37 |
|
9 |
5993 |
16QAM |
9 |
4 |
|
10 |
6673 |
QPSK |
10 |
43 |
|
10 |
6673 |
16QAM |
10 |
5 |
|
11 |
7298 |
QPSK |
10 |
48 |
|
11 |
7298 |
16QAM |
10 |
10 |
|
12 |
7981 |
QPSK |
10 |
53 |
|
12 |
7981 |
16QAM |
10 |
15 |
|
13 |
8574 |
QPSK |
10 |
57 |
|
13 |
8574 |
16QAM |
10 |
19 |
|
14 |
9210 |
QPSK |
10 |
61 |
|
14 |
9210 |
16QAM |
10 |
23 |
|
15 |
9894 |
16QAM |
10 |
27 |
|
16 |
10629 |
16QAM |
10 |
31 |
|
17 |
11216 |
16QAM |
10 |
34 |
|
18 |
11835 |
16QAM |
10 |
37 |
|
19 |
12488 |
16QAM |
10 |
40 |
|
20 |
13177 |
16QAM |
10 |
43 |
|
21 |
13904 |
16QAM |
10 |
46 |
Table 14.1.3.4.3: TFRC test points for UE category 9 for MAC-d PDU size=656
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
---|---|---|---|---|---|
1 |
686 |
QPSK |
2 |
7 |
|
1 |
686 |
16QAM |
1 |
7 |
|
2 |
1356 |
QPSK |
4 |
6 |
|
2 |
1356 |
16QAM |
2 |
6 |
|
3 |
2010 |
QPSK |
6 |
5 |
|
3 |
2010 |
16QAM |
3 |
5 |
|
4 |
2677 |
QPSK |
8 |
5 |
|
4 |
2677 |
16QAM |
4 |
5 |
|
5 |
3319 |
QPSK |
10 |
4 |
|
5 |
3319 |
16QAM |
5 |
4 |
|
6 |
3970 |
QPSK |
13 |
0 |
|
6 |
3970 |
16QAM |
6 |
4 |
|
7 |
4664 |
QPSK |
15 |
1 |
|
7 |
4664 |
16QAM |
7 |
4 |
|
8 |
5287 |
QPSK |
15 |
8 |
|
8 |
5287 |
16QAM |
8 |
4 |
|
9 |
5993 |
QPSK |
15 |
15 |
|
9 |
5993 |
16QAM |
9 |
4 |
|
10 |
6673 |
QPSK |
15 |
21 |
|
10 |
6673 |
16QAM |
10 |
5 |
|
11 |
7298 |
QPSK |
15 |
26 |
|
11 |
7298 |
16QAM |
11 |
4 |
|
12 |
7981 |
QPSK |
15 |
31 |
|
12 |
7981 |
16QAM |
13 |
0 |
|
13 |
8574 |
QPSK |
15 |
35 |
|
13 |
8574 |
16QAM |
14 |
0 |
|
14 |
9210 |
QPSK |
15 |
39 |
|
14 |
9210 |
16QAM |
15 |
0 |
|
15 |
9894 |
QPSK |
15 |
43 |
|
15 |
9894 |
16QAM |
15 |
4 |
|
16 |
10629 |
QPSK |
15 |
47 |
|
16 |
10629 |
16QAM |
15 |
8 |
|
17 |
11418 |
QPSK |
15 |
51 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.7806) would have given 3.5 dB due to turbo coder irregularities TFRI=51 is selected. |
17 |
11216 |
16QAM |
15 |
11 |
|
18 |
11835 |
QPSK |
15 |
53 |
|
18 |
11835 |
16QAM |
15 |
14 |
|
19 |
12488 |
QPSK |
15 |
56 |
|
19 |
12488 |
16QAM |
15 |
17 |
|
20 |
13177 |
QPSK |
15 |
59 |
|
20 |
13177 |
16QAM |
15 |
20 |
|
21 |
13904 |
QPSK |
15 |
62 |
|
21 |
13904 |
16QAM |
15 |
23 |
|
22 |
14671 |
16QAM |
15 |
26 |
|
23 |
15206 |
16QAM |
15 |
28 |
|
24 |
16045 |
16QAM |
15 |
31 |
|
25 |
16630 |
16QAM |
15 |
33 |
|
26 |
17237 |
16QAM |
15 |
35 |
|
27 |
17865 |
16QAM |
15 |
37 |
|
28 |
18517 |
16QAM |
15 |
39 |
|
29 |
19192 |
16QAM |
15 |
41 |
|
30 |
19891 |
16QAM |
15 |
43 |
Table 14.1.3.4.4: TFRC test points for UE category 10 for MAC-d PDU size=656
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
1 |
686 |
QPSK |
2 |
7 |
|
1 |
686 |
16QAM |
1 |
7 |
|
2 |
1356 |
QPSK |
4 |
6 |
|
2 |
1356 |
16QAM |
2 |
6 |
|
3 |
2010 |
QPSK |
6 |
5 |
|
3 |
2010 |
16QAM |
3 |
5 |
|
4 |
2677 |
QPSK |
8 |
5 |
|
4 |
2677 |
16QAM |
4 |
5 |
|
5 |
3319 |
QPSK |
10 |
4 |
|
5 |
3319 |
16QAM |
5 |
4 |
|
6 |
3970 |
QPSK |
13 |
0 |
|
6 |
3970 |
16QAM |
6 |
4 |
|
7 |
4664 |
QPSK |
15 |
1 |
|
7 |
4664 |
16QAM |
7 |
4 |
|
8 |
5287 |
QPSK |
15 |
8 |
|
8 |
5287 |
16QAM |
8 |
4 |
|
9 |
5993 |
QPSK |
15 |
15 |
|
9 |
5993 |
16QAM |
9 |
4 |
|
10 |
6673 |
QPSK |
15 |
21 |
|
10 |
6673 |
16QAM |
10 |
5 |
|
11 |
7298 |
QPSK |
15 |
26 |
|
11 |
7298 |
16QAM |
11 |
4 |
|
12 |
7981 |
QPSK |
15 |
31 |
|
12 |
7981 |
16QAM |
13 |
0 |
|
13 |
8574 |
QPSK |
15 |
35 |
|
13 |
8574 |
16QAM |
14 |
0 |
|
14 |
9210 |
QPSK |
15 |
39 |
|
14 |
9210 |
16QAM |
15 |
0 |
|
15 |
9894 |
QPSK |
15 |
43 |
|
15 |
9894 |
16QAM |
15 |
4 |
|
16 |
10629 |
QPSK |
15 |
47 |
|
16 |
10629 |
16QAM |
15 |
8 |
|
17 |
11418 |
QPSK |
15 |
51 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.7806) would have given 3.5 dB due to turbo coder irregularities TFRI=51 is selected. |
17 |
11216 |
16QAM |
15 |
11 |
|
18 |
11835 |
QPSK |
15 |
53 |
|
18 |
11835 |
16QAM |
15 |
14 |
|
19 |
12488 |
QPSK |
15 |
56 |
|
19 |
12488 |
16QAM |
15 |
17 |
|
20 |
13177 |
QPSK |
15 |
59 |
|
20 |
13177 |
16QAM |
15 |
20 |
|
21 |
13904 |
QPSK |
15 |
62 |
|
21 |
13904 |
16QAM |
15 |
23 |
|
22 |
14671 |
16QAM |
15 |
26 |
|
23 |
15206 |
16QAM |
15 |
28 |
|
24 |
16045 |
16QAM |
15 |
31 |
|
25 |
16630 |
16QAM |
15 |
33 |
|
26 |
17237 |
16QAM |
15 |
35 |
|
27 |
17865 |
16QAM |
15 |
37 |
|
28 |
18517 |
16QAM |
15 |
39 |
|
29 |
19192 |
16QAM |
15 |
41 |
|
30 |
19891 |
16QAM |
15 |
43 |
|
31 |
20617 |
16QAM |
15 |
45 |
|
32 |
21368 |
16QAM |
15 |
47 |
|
33 |
21754 |
16QAM |
15 |
48 |
|
34 |
22955 |
16QAM |
15 |
51 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.78375) would have given 3.5 dB due to turbo coder irregularities TFRI=51 is selected. |
35 |
23370 |
16QAM |
15 |
52 |
|
36 |
23792 |
16QAM |
15 |
53 |
|
37 |
24659 |
16QAM |
15 |
55 |
|
38 |
25558 |
16QAM |
15 |
57 |
TFRI = 56 would have minimised padding but is not acceptable as the coding rate (0.8725) would have given 2 dB due to turbo coder irregularities TFRI=57 is selected. |
39 |
26020 |
16QAM |
15 |
58 |
|
40 |
26490 |
16QAM |
15 |
59 |
|
41 |
26969 |
16QAM |
15 |
60 |
|
42 |
27952 |
16QAM |
15 |
62 |
Table 14.1.3.4.5: TFRC test points for UE category 11 and UE category 12 for MAC-d PDU size=656
Number of MAC-d PDUs |
Selected transport block size [bits] |
Modulation scheme |
Number of codes |
TFRI |
Comments |
---|---|---|---|---|---|
1 |
686 |
QPSK |
2 |
7 |
|
2 |
1356 |
QPSK |
4 |
6 |
|
3 |
2010 |
QPSK |
5 |
15 |
|
4 |
2677 |
QPSK |
5 |
31 |
|
5 |
3319 |
QPSK |
5 |
43 |
14.1.3.4b TB test points for enhanced Layer 2
14.1.3.4b.1 TFRC test points for MAC-ehs and QPSK with fixed MAC-d PDU size=336
NOTE 1 For M= QPSK then table 14.1.3.4b.1.1 is used. For M= 16QAM then table 14.1.3.4b.1.2 is used. For M= 64QAM then table 14.1.3.4b.1.3 is used.
NOTE 2 Column “Applicable Physical HS-DSCH UE categories” defines the applicability of test points vs. Physical HS-DSCH UE categories.
Table 14.1.3.4b.1.1: Test points for QPSK and fixed MAC-d PDU size=336
# MAC-d PDUs |
Selected TBS |
Modulation scheme |
Number of codes |
TFRI |
Applicable Physical HS-DSCH UE categories |
Comments |
1 |
360 |
QPSK |
1 |
30 |
1 to 20 |
|
2 |
712 |
QPSK |
2 |
9 |
1 to 20 |
|
3 |
1072 |
QPSK |
3 |
9 |
1 to 20 |
|
4 |
1432 |
QPSK |
4 |
9 |
1 to 20 |
|
5 |
1776 |
QPSK |
5 |
9 |
1 to 20 |
|
6 |
2128 |
QPSK |
5 |
19 |
1 to 6,11 and 12 |
|
6 |
2128 |
QPSK |
7 |
0 |
7 to 10 and 13 to 20 |
|
7 |
2496 |
QPSK |
5 |
28 |
1 to 6,11 and 12 |
|
7 |
2496 |
QPSK |
8 |
1 |
7 to 10 and 13 to 20 |
|
8 |
2832 |
QPSK |
5 |
35 |
1 to 6,11 and 12 |
|
8 |
2832 |
QPSK |
9 |
2 |
7 to 10 and 13 to 20 |
|
9 |
3208 |
QPSK |
5 |
42 |
1 to 6,11 and 12 |
|
9 |
3208 |
QPSK |
10 |
3 |
7 to 10 and 13 to 20 |
|
10 |
3576 |
QPSK |
5 |
48 |
1 to 6,11 and 12 |
|
10 |
3576 |
QPSK |
10 |
9 |
7 and 8 |
|
10 |
3576 |
QPSK |
11 |
4 |
9 to 10 and 13 to 20 |
|
11 |
3912 |
QPSK |
5 |
53 |
1 to 6 |
|
11 |
3912 |
QPSK |
10 |
14 |
7 and 8 |
|
11 |
3912 |
QPSK |
12 |
4 |
9 to 10 and 13 to 20 |
|
12 |
4272 |
QPSK |
5 |
58 |
1 to 6 |
|
12 |
4272 |
QPSK |
10 |
19 |
7 and 8 |
|
12 |
4272 |
QPSK |
14 |
0 |
9 to 10 and 13 to 20 |
|
13 |
4592 |
QPSK |
5 |
62 |
1 to 6 |
|
13 |
4592 |
QPSK |
10 |
23 |
7 and 8 |
|
13 |
4592 |
QPSK |
15 |
0 |
9 to 10 and 13 to 20 |
|
14 |
4936 |
QPSK |
10 |
27 |
7 and 8 |
|
14 |
4936 |
QPSK |
15 |
4 |
9 to 10 and 13 to 20 |
|
15 |
5296 |
QPSK |
10 |
31 |
7 and 8 |
|
15 |
5296 |
QPSK |
15 |
8 |
9 to 10 and 13 to 20 |
|
16 |
5688 |
QPSK |
10 |
35 |
7 and 8 |
|
16 |
5688 |
QPSK |
15 |
12 |
9 to 10 and 13 to 20 |
|
17 |
6008 |
QPSK |
10 |
38 |
7 and 8 |
|
17 |
6008 |
QPSK |
15 |
15 |
9 to 10 and 13 to 20 |
|
18 |
6448 |
QPSK |
10 |
42 |
7 and 8 |
|
18 |
6448 |
QPSK |
15 |
19 |
9 to 10 and 13 to 20 |
|
19 |
6808 |
QPSK |
10 |
45 |
7 and 8 |
|
19 |
6808 |
QPSK |
15 |
22 |
9 to 10 and 13 to 20 |
|
20 |
7056 |
QPSK |
10 |
47 |
7 and 8 |
|
20 |
7056 |
QPSK |
15 |
24 |
9 to 10 and 13 to 20 |
|
21 |
7576 |
QPSK |
10 |
51 |
7 and 8 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.777) would have given 3.5 dB due to turbo coder irregularities. TFRI=51 is selected. |
21 |
7440 |
QPSK |
15 |
27 |
9 to 10 and 13 to 20 |
|
22 |
7856 |
QPSK |
10 |
53 |
7 and 8 |
|
22 |
7856 |
QPSK |
15 |
30 |
9 to 10 and 13 to 20 |
|
23 |
8136 |
QPSK |
10 |
55 |
7 and 8 |
|
23 |
8136 |
QPSK |
15 |
32 |
9 to 10 and 13 to 20 |
|
24 |
8592 |
QPSK |
10 |
58 |
7 and 8 |
|
24 |
8592 |
QPSK |
15 |
35 |
9 to 10 and 13 to 20 |
|
25 |
8904 |
QPSK |
10 |
60 |
7 and 8 |
|
25 |
8904 |
QPSK |
15 |
37 |
9 to 10 and 13 to 20 |
|
26 |
9224 |
QPSK |
10 |
62 |
7 and 8 |
|
26 |
9224 |
QPSK |
15 |
39 |
9 to 10 and 13 to 20 |
Table 14.1.3.4b.1.2: Test points for 16QAM and fixed MAC-d PDU size=336
# MAC-d PDUs |
Selected TBS |
Modulation scheme |
Number of codes |
TFRI |
Applicable Physical HS-DSCH UE categories |
Comments |
2 |
712 |
16QAM |
1 |
9 |
1 to 10 and 13 to 20 |
|
3 |
1072 |
16QAM |
1 |
32 |
1 to 10 and 13 to 20 |
|
4 |
1432 |
16QAM |
2 |
9 |
1 to 10 and 13 to 20 |
|
5 |
1776 |
16QAM |
2 |
21 |
1 to 10 and 13 to 20 |
|
6 |
2128 |
16QAM |
3 |
9 |
1 to 10 and 13 to 20 |
|
7 |
2496 |
16QAM |
4 |
1 |
1 to 10 and 13 to 20 |
|
8 |
2832 |
16QAM |
4 |
8 |
1 to 10 and 13 to 20 |
|
9 |
3208 |
16QAM |
5 |
3 |
1 to 10 and 13 to 20 |
|
10 |
3576 |
16QAM |
5 |
9 |
1 to 10 and 13 to 20 |
|
11 |
3912 |
16QAM |
5 |
14 |
1 to 6 |
|
11 |
3912 |
16QAM |
6 |
4 |
7 to 10 and 13 to 20 |
|
12 |
4272 |
16QAM |
5 |
19 |
1 to 6 |
|
12 |
4272 |
16QAM |
7 |
0 |
7 to 10 and 13 to 20 |
|
13 |
4592 |
16QAM |
5 |
23 |
1 to 6 |
|
13 |
4592 |
16QAM |
7 |
4 |
7 to 10 and 13 to 20 |
|
14 |
4936 |
16QAM |
5 |
27 |
1 to 6 |
|
14 |
4936 |
16QAM |
8 |
1 |
7 to 10 and 13 to 20 |
|
15 |
5296 |
16QAM |
5 |
31 |
1 to 6 |
|
15 |
5296 |
16QAM |
8 |
5 |
7 to 10 and 13 to 20 |
|
16 |
5688 |
16QAM |
5 |
35 |
1 to 6 |
|
16 |
5688 |
16QAM |
9 |
2 |
7 to 10 and 13 to 20 |
|
17 |
6008 |
16QAM |
5 |
38 |
1 to 6 |
|
17 |
6008 |
16QAM |
9 |
5 |
7 to 10 and 13 to 20 |
|
18 |
6448 |
16QAM |
5 |
42 |
1 to 6 |
|
18 |
6448 |
16QAM |
10 |
3 |
7 to 10 and 13 to 20 |
|
19 |
6808 |
16QAM |
5 |
45 |
1 to 6 |
|
19 |
6808 |
16QAM |
10 |
6 |
7 and 8 |
|
19 |
6808 |
16QAM |
11 |
1 |
9 to 10 and 13 to 20 |
|
20 |
7056 |
16QAM |
5 |
47 |
1 to 6 |
|
20 |
7056 |
16QAM |
10 |
8 |
7 and 8 |
|
20 |
7056 |
16QAM |
11 |
3 |
9 to 10 and 13 to 20 |
|
21 |
7440 |
16QAM |
10 |
11 |
7 and 8 |
|
21 |
7440 |
16QAM |
12 |
1 |
9 to 10 and 13 to 20 |
|
22 |
7856 |
16QAM |
10 |
14 |
7 and 8 |
|
22 |
7856 |
16QAM |
13 |
0 |
9 to 10 and 13 to 20 |
|
23 |
8136 |
16QAM |
10 |
16 |
7 and 8 |
|
23 |
8136 |
16QAM |
13 |
2 |
9 to 10 and 13 to 20 |
|
24 |
8592 |
16QAM |
10 |
19 |
7 and 8 |
|
24 |
8592 |
16QAM |
14 |
0 |
9 to 10 and 13 to 20 |
|
25 |
8904 |
16QAM |
10 |
21 |
7 and 8 |
|
25 |
8904 |
16QAM |
14 |
2 |
9 to 10 and 13 to 20 |
|
26 |
9224 |
16QAM |
10 |
23 |
7 and 8 |
|
26 |
9224 |
16QAM |
15 |
1 |
9 to 10 and 13 to 20 |
Table 14.1.3.4b.1.3: Test points for 64QAM and fixed MAC-d PDU size=336
# MAC-d PDUs |
Selected TBS |
Modulation scheme |
Number of codes |
TFRI |
Applicable Physical HS-DSCH UE categories |
Comments |
3 |
1072 |
64QAM |
1 |
9 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
4 |
1432 |
64QAM |
1 |
25 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
5 |
1776 |
64QAM |
1 |
37 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
6 |
2128 |
64QAM |
2 |
9 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
7 |
2496 |
64QAM |
2 |
18 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
8 |
2832 |
64QAM |
3 |
2 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
9 |
3208 |
64QAM |
3 |
9 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
10 |
3576 |
64QAM |
3 |
15 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
11 |
3912 |
64QAM |
4 |
4 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
12 |
4272 |
64QAM |
4 |
9 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
13 |
4592 |
64QAM |
5 |
0 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
14 |
4936 |
64QAM |
5 |
4 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
15 |
5296 |
64QAM |
5 |
8 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
16 |
5688 |
64QAM |
6 |
2 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
17 |
6008 |
64QAM |
6 |
5 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
18 |
6448 |
64QAM |
7 |
0 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
19 |
6808 |
64QAM |
7 |
3 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
20 |
7056 |
64QAM |
7 |
5 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
21 |
7440 |
64QAM |
8 |
1 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
22 |
7856 |
64QAM |
8 |
4 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
23 |
8136 |
64QAM |
8 |
6 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
24 |
8592 |
64QAM |
9 |
2 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
25 |
8904 |
64QAM |
9 |
4 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
|
26 |
9224 |
64QAM |
10 |
1 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20 |
14.1.3.4b.2 TFRC test points for MAC-ehs and fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
NOTE 1 For M= QPSK then table 14.1.3.4b.2.1 is used. For M= 16QAM then table 14.1.3.4b.2.2 is used. For M= 64QAM then table 14.1.3.4b.2.3 is used. For the case of Dual Cell or MIMO and mix of QPSK and 16QAM for MIMO data flow#1 and MIMO data flow#2 then table 14.1.3.4b.2.4 is used. For the case of 3C-HSDPA without MIMO or 4C-HSDPA without MIMO and M=QPSK then table 14.1.3.4b.2.1 is used. For the case of 3C-HSDPA without MIMO or 4C-HSDPA without MIMO and M=16QAM then table 14.1.3.4b.2.2 is used. For the case of 3C-HSDPA without MIMO or 4C-HSDPA without MIMO and M=64QAM then table 14.1.3.4b.2.3 is used.
NOTE 2 Column “Applicable Physical HS-DSCH UE categories” defines the applicability of test points vs. Physical HS-DSCH UE categories.
NOTE 3 For the case a configuration with flexible MAC-d PDU size is under test then the parameter as denoted NPDUs is only used to index the test points. For the case of configuration with fixed MAC-d PDU size=656 then this parameter also indicates the number of MAC-d PDUs the SS use when transmitting the test data in downlink.
Table 14.1.3.4b.2.1: Test points for QPSK, fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS |
Modulation scheme |
Number of codes |
TFRI |
Applicable Physical HS-DSCH UE categories |
Comments |
1 |
688 |
QPSK |
2 |
7 |
1 to 24 |
|
2 |
1360 |
QPSK |
4 |
6 |
1 to 24 |
|
3 |
2048 |
QPSK |
5 |
17 |
1 to 6,11 and 12 |
|
3 |
2048 |
QPSK |
6 |
7 |
7 to 10 and 13 to 24 |
|
4 |
2736 |
QPSK |
5 |
33 |
1 to 6,11 and 12 |
|
4 |
2736 |
QPSK |
9 |
0 |
7 to 10 and 13 to 24 |
|
5 |
3384 |
QPSK |
5 |
45 |
1 to 6,11 and 12 |
|
5 |
3384 |
QPSK |
10 |
6 |
7 and 8 |
|
5 |
3384 |
QPSK |
11 |
1 |
9 to 10 and 13 to 24 |
|
6 |
4048 |
QPSK |
5 |
55 |
1 to 6 |
|
6 |
4048 |
QPSK |
10 |
16 |
7 and 8 |
|
6 |
4048 |
QPSK |
13 |
1 |
9 to 10 and 13 to 24 |
|
7 |
4760 |
QPSK |
10 |
25 |
7 and 8 |
|
7 |
4760 |
QPSK |
15 |
2 |
9 to 10 and 13 to 24 29 and 31 |
|
8 |
5392 |
QPSK |
10 |
32 |
7 and 8 |
|
8 |
5392 |
QPSK |
15 |
9 |
9 to 10 and 13 to 24 29 and 31 |
|
9 |
6112 |
QPSK |
10 |
39 |
7 and 8 |
|
9 |
6112 |
QPSK |
15 |
16 |
9 to 10 and 13 to 24 29 and 31 |
|
10 |
6808 |
QPSK |
10 |
45 |
7 and 8 |
|
10 |
6808 |
QPSK |
15 |
22 |
9 to 10 and 13 to 24 29 and 31 |
|
11 |
7576 |
QPSK |
10 |
51 |
7 and 8 |
TFRI = 50 would have minimised padding but is not acceptable as the coding rate (0.777) would have given 3.5 dB due to turbo coder irregularities. TFRI=51 is selected. |
11 |
7440 |
QPSK |
15 |
27 |
9 to 10 and 13 to 24 29 and 31 |
|
12 |
8136 |
QPSK |
10 |
55 |
7 and 8 |
|
12 |
8136 |
QPSK |
15 |
32 |
9 to 10 and 13 to 24 29 and 31 |
|
13 |
8904 |
QPSK |
10 |
60 |
7 and 8 |
TFRI = 59 would have minimised padding but is not acceptable as the coding rate (0.913) would have given 2 dB due to turbo coder irregularities. TFRI=60 is selected. |
13 |
8744 |
QPSK |
15 |
36 |
9 to 10 and 13 to 24 29 and 31 |
|
14 |
9560 |
QPSK |
15 |
41 |
9 to 10 and 13 to 24 29 and 31 |
|
15 |
10088 |
QPSK |
15 |
44 |
9 to 10 and 13 to 24 29 and 31 |
|
16 |
10840 |
QPSK |
15 |
48 |
9 to 10 and 13 to 24 29 and 31 |
|
17 |
11432 |
QPSK |
15 |
51 |
9 to 10 and 13 to 24 29 and 31 |
|
18 |
12280 |
QPSK |
15 |
55 |
9 to 10 and 13 to 24 29 and 31 |
|
19 |
12960 |
QPSK |
15 |
58 |
9 to 10 and 13 to 24 29 and 31 |
|
20 |
13672 |
QPSK |
15 |
61 |
9 to 10 and 13 to 24 29 and 31 |
Table 14.1.3.4b.2.2: Test points for 16QAM, fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS |
Modulation scheme |
Number of codes |
TFRI |
Applicable Physical HS-DSCH UE categories |
Comments |
1 |
688 |
16QAM |
1 |
7 |
1 to 10 and 13 to 28 |
|
2 |
1360 |
16QAM |
2 |
6 |
1 to 10 and 13 to 28 |
|
3 |
2048 |
16QAM |
3 |
7 |
1 to 10 and 13 to 28 |
|
4 |
2736 |
16QAM |
4 |
6 |
1 to 10 and 13 to 28 |
|
5 |
3384 |
16QAM |
5 |
6 |
1 to 10 and 13 to 28 |
|
6 |
4048 |
16QAM |
5 |
16 |
1 to 6 |
|
6 |
4048 |
16QAM |
6 |
6 |
7 to 10 and 13 to 28 |
|
7 |
4760 |
16QAM |
5 |
25 |
1 to 6 |
|
7 |
4760 |
16QAM |
7 |
6 |
7 to 10 and 13 to 28 |
|
8 |
5392 |
16QAM |
5 |
32 |
1 to 6 |
|
8 |
5392 |
16QAM |
8 |
6 |
7 to 10 and 13 to 28 |
|
9 |
6112 |
16QAM |
5 |
39 |
1 to 6 |
|
9 |
6112 |
16QAM |
10 |
0 |
7 to 10 and 13 to 28 |
|
10 |
6808 |
16QAM |
5 |
45 |
1 to 6 |
|
10 |
6808 |
16QAM |
10 |
6 |
7 and 8 |
|
10 |
6808 |
16QAM |
11 |
1 |
9 to 10 and 13 to 28 |
|
11 |
7440 |
16QAM |
10 |
11 |
7 and 8 |
|
11 |
7440 |
16QAM |
12 |
1 |
9 to 10 and 13 to 28 |
|
12 |
8136 |
16QAM |
10 |
16 |
7 and 8 |
|
12 |
8136 |
16QAM |
13 |
2 |
9 to 10 and 13 to 28 |
|
13 |
8744 |
16QAM |
10 |
20 |
7 and 8 |
|
13 |
8744 |
16QAM |
14 |
1 |
9 to 10 and 13 to 28 |
|
14 |
9560 |
16QAM |
10 |
25 |
7 and 8 |
|
14 |
9560 |
16QAM |
15 |
3 |
9 to 10 and 13 to 28 29 and 31 |
|
15 |
10088 |
16QAM |
10 |
28 |
7 and 8 |
|
15 |
10088 |
16QAM |
15 |
6 |
9 to 10 and 13 to 28 29 and 31 |
|
16 |
10840 |
16QAM |
10 |
32 |
7 and 8 |
|
16 |
10840 |
16QAM |
15 |
10 |
9 to 10 and 13 to 28 29 and 31 |
|
17 |
11432 |
16QAM |
10 |
35 |
7 and 8 |
|
17 |
11432 |
16QAM |
15 |
13 |
9 to 10 and 13 to 28 29 and 31 |
|
18 |
12280 |
16QAM |
10 |
39 |
7 and 8 |
|
18 |
12280 |
16QAM |
15 |
17 |
9 to 10 and 13 to 28 29 and 31 |
|
19 |
12960 |
16QAM |
10 |
42 |
7 and 8 |
|
19 |
12960 |
16QAM |
15 |
20 |
9 to 10 and 13 to 28 29 and 31 |
|
20 |
13672 |
16QAM |
10 |
45 |
7 and 8 |
|
20 |
13672 |
16QAM |
15 |
23 |
9 to 10 and 13 to 28 29 and 31 |
|
21 |
14168 |
16QAM |
10 |
47 |
7 and 8 |
|
21 |
14168 |
16QAM |
15 |
25 |
9 to 10 and 13 to 28 29 and 31 |
|
22 |
14952 |
16QAM |
15 |
28 |
9 to 10 and 13 to 28 29 and 31 |
|
23 |
15496 |
16QAM |
15 |
30 |
9 to 10 and 13 to 28 29 and 31 |
|
24 |
16352 |
16QAM |
15 |
33 |
9 to 10 and 13 to 28 29 and 31 |
|
25 |
16944 |
16QAM |
15 |
35 |
9 to 10 and 13 to 28 29 and 31 |
|
26 |
17568 |
16QAM |
15 |
37 |
9 to 10 and 13 to 28 29 and 31 |
|
(27) |
17880 |
16QAM |
15 |
38 |
9 to 10 and 13 to 28 29 and 31 |
See Note 1 |
(28) |
18536 |
16QAM |
15 |
40 |
9 to 10 and 13 to 28 29 and 31 |
See Note 1 |
(29) |
19208 |
16QAM |
15 |
42 |
9 to 10 and 13 to 28 29 and 31 |
See Note 1 |
(30) |
19904 |
16QAM |
15 |
44 |
9 to 10 and 13 to 28 29 and 31 |
See Note 1 |
(31) |
20632 |
16QAM |
15 |
46 |
10 and 13 to 28 29 and 31 |
See Note 1 |
(32) |
21384 |
16QAM |
15 |
48 |
10 and 13 to 28 |
See Note 1 |
(33) |
21768 |
16QAM |
15 |
49 |
10 and 13 to 28 29 and 31 |
See Note 1 |
(34) |
22968 |
16QAM |
15 |
52 |
10 and 13 to 28 29 and 31 |
See Note 1 TFRI = 51 would have minimised padding but is not acceptable as the coding rate (0.784) would have given 3.5 dB due to turbo coder irregularities TFRI=52 is selected. |
(35) |
23384 |
16QAM |
15 |
53 |
10, 13, 14,16, 17 non-MIMO, 20, 24 and 28 29 and 31 |
See Note 1 |
(36) |
23808 |
16QAM |
15 |
54 |
10, 13, 14,16, 17 non-MIMO, 20, 24 and 28 29 and 31 |
See Note 1 |
(37) |
24672 |
16QAM |
15 |
56 |
10, 13, 14,16, 17 non-MIMO, 20, 24 and 28 29 and 31 |
See Note 1 |
(38) |
25568 |
16QAM |
15 |
58 |
10, 13, 14,16, 17 non-MIMO, 20, 24 and 28 29 and 31 |
See Note 1 TFRI = 57 would have minimised padding but is not acceptable as the coding rate (0.873) would have given 2 dB due to turbo coder irregularities TFRI=58 is selected. |
(39) |
26032 |
16QAM |
15 |
59 |
10, 13, 14,16, 17 non-MIMO, 20, 24 and 28 29 and 31 |
See Note 1 |
(40) |
26504 |
16QAM |
15 |
60 |
10, 13, 14,16, 17 non-MIMO, 20, 24 and 28 29 and 31 |
See Note 1 |
(41) |
26976 |
16QAM |
15 |
61 |
10, 13, 14,16, 17 non-MIMO, 20, 24 and 28 29 and 31 |
See Note 1 |
Note 1: This test point is not applicable for the fixed RLC case as the number of MAC-d PDUs would have exceeded the maximum limit of 26 as specified by TS 25.321 clause 9.1.4. When flexible MAC-d PDU size is under test then the parameter as denoted (x) is only used to index the test points |
Table 14.1.3.4b.2.3: Test points for 64QAM, fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS |
Modulation scheme |
Number of codes |
TFRI |
Applicable Physical HS-DSCH UE categories |
Comments |
2 |
1360 |
64QAM |
1 |
22 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
3 |
2048 |
64QAM |
2 |
7 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
4 |
2736 |
64QAM |
3 |
0 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
5 |
3384 |
64QAM |
3 |
12 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
6 |
4048 |
64QAM |
4 |
6 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
7 |
4760 |
64QAM |
5 |
2 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
8 |
5392 |
64QAM |
5 |
9 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
9 |
6112 |
64QAM |
6 |
6 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
10 |
6808 |
64QAM |
7 |
3 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
11 |
7440 |
64QAM |
8 |
1 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
12 |
8136 |
64QAM |
8 |
6 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
13 |
8744 |
64QAM |
9 |
3 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
14 |
9560 |
64QAM |
10 |
3 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
15 |
10088 |
64QAM |
11 |
0 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
16 |
10840 |
64QAM |
11 |
4 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
17 |
11432 |
64QAM |
12 |
2 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
18 |
12280 |
64QAM |
13 |
2 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
19 |
12960 |
64QAM |
14 |
1 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
20 |
13672 |
64QAM |
14 |
4 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 |
|
21 |
14168 |
64QAM |
15 |
1 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
|
22 |
14952 |
64QAM |
15 |
4 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
|
23 |
15496 |
64QAM |
15 |
6 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
|
24 |
16352 |
64QAM |
15 |
9 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
|
25 |
16944 |
64QAM |
15 |
11 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
|
26 |
17568 |
64QAM |
15 |
13 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
|
(27) |
17880 |
64QAM |
15 |
14 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(28) |
18536 |
64QAM |
15 |
16 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(29) |
19208 |
64QAM |
15 |
18 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(30) |
19904 |
64QAM |
15 |
20 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(31) |
20632 |
64QAM |
15 |
22 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(32) |
21384 |
64QAM |
15 |
24 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(33) |
21768 |
64QAM |
15 |
25 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(34) |
22560 |
64QAM |
15 |
27 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(35) |
23384 |
64QAM |
15 |
29 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(36) |
23808 |
64QAM |
15 |
30 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(37) |
24672 |
64QAM |
15 |
32 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(38) |
25120 |
64QAM |
15 |
33 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(39) |
26032 |
64QAM |
15 |
35 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(40) |
26504 |
64QAM |
15 |
36 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(41) |
26976 |
64QAM |
15 |
37 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(42) |
27960 |
64QAM |
15 |
39 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(43) |
28464 |
64QAM |
15 |
40 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(44) |
28976 |
64QAM |
15 |
41 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(45) |
30032 |
64QAM |
15 |
43 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(46) |
30576 |
64QAM |
15 |
44 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(47) |
31128 |
64QAM |
15 |
45 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(48) |
31688 |
64QAM |
15 |
46 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(49) |
32264 |
64QAM |
15 |
47 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(50) |
32848 |
64QAM |
15 |
48 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(51) |
Void |
|||||
(52) |
34656 |
64QAM |
15 |
51 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(53) |
35280 |
64QAM |
15 |
52 |
13, 14, 17 non-MIMO, 18 non-MIMO, 19, 20, 23, 24, 27, 28 29 and 31 |
See Note 1 |
(54) |
35920 |
64QAM |
15 |
53 |
14 and 18 non-MIMO, 20, 24, 28 29 and 31 |
See Note 1 |
(55) |
36568 |
64QAM |
15 |
54 |
14 and 18 non-MIMO, 20, 24, 28 29 and 31 |
See Note 1 |
(56) |
37224 |
64QAM |
15 |
55 |
14 and 18 non-MIMO, 20, 24, 28 29 and 31 |
See Note 1 |
(57) |
Void |
|||||
(58) |
38576 |
64QAM |
15 |
57 |
14 and 18 non-MIMO, 20, 24, 28 29 and 31 |
See Note 1 |
(59) |
39272 |
64QAM |
15 |
58 |
14 and 18 non-MIMO, 20, 24, 28 29 and 31 |
See Note 1 |
(60) |
39984 |
64QAM |
15 |
59 |
14 and 18 non-MIMO, 20, 24, 28 29 and 31 |
See Note 1 |
(61) |
40704 |
64QAM |
15 |
60 |
14 and 18 non-MIMO, 20, 24, 28 29 and 31 |
See Note 1 |
(62) |
Void |
|||||
(63) |
Void |
|||||
(64) |
42192 |
64QAM |
15 |
62 |
14 and 18 non-MIMO, 20, 24, 28 29 and 31 |
See Note 1 |
Note 1: This test point is not applicable for the fixed RLC case as the number of MAC-d PDUs would have exceeded the maximum limit of 26 as specified by TS 25.321 clause 9.1.4. When flexible MAC-d PDU size is under test then the parameter as denoted (x) is only used to index the test points |
Table 14.1.3.4b.2.4: Test points for Dual Cell or MIMO and mix of 16QAM and QPSK for Dual Cell or MIMO data flow#1 and Dual Cell or MIMO data flow#2, fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
Test point Index See note 1 |
Number of codes |
Dual Cell or MIMO Flow#1 |
Dual Cell or MIMO Flow#2 |
Applicable Physical HS-DSCH UE categories |
Comments |
||||||
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS1) |
Modulation scheme (M1) |
TFRI1 |
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS2) |
Modulation scheme (M2) |
TFRI2 |
||||
1 |
2 |
2 |
1360 |
16QAM |
6 |
1 |
688 |
QPSK |
7 |
15 to 24 |
|
2 |
4 |
4 |
2736 |
16QAM |
6 |
2 |
1360 |
QPSK |
6 |
15 to 24 |
|
3 |
Void |
||||||||||
4 |
6 |
6 |
4048 |
16QAM |
6 |
3 |
2048 |
QPSK |
7 |
15 to 24 |
|
5 |
Void |
||||||||||
6 |
9 |
8 |
6112 |
16QAM |
6 |
4 |
2736 |
QPSK |
0 |
15 to 24 |
|
7 |
Void |
||||||||||
8 |
Void |
||||||||||
9 |
11 |
10 |
6608 |
16QAM |
1 |
5 |
3384 |
QPSK |
1 |
15 to 24 |
|
10 |
Void |
||||||||||
11 |
Void |
||||||||||
12 |
13 |
12 |
8136 |
16QAM |
2 |
6 |
4048 |
QPSK |
1 |
15 to 24 |
|
13 |
Void |
||||||||||
14 |
15 |
14 |
9560 |
16QAM |
3 |
7 |
4760 |
QPSK |
2 |
15 to 24 |
|
15 |
Void |
||||||||||
16 |
15 |
15 |
10088 |
16QAM |
6 |
8 |
5392 |
QPSK |
9 |
15 to 24 |
|
17 |
Void |
||||||||||
18 |
15 |
16 |
10840 |
16QAM |
10 |
9 |
6112 |
QPSK |
16 |
15 to 24 |
|
19 |
Void |
||||||||||
20 |
15 |
17 |
11432 |
16QAM |
13 |
10 |
6808 |
QPSK |
22 |
15 to 24 |
|
21 |
Void |
||||||||||
22 |
15 |
18 |
12280 |
16QAM |
17 |
11 |
7440 |
QPSK |
27 |
15 to 24 |
|
23 |
Void |
||||||||||
24 |
15 |
19 |
12960 |
16QAM |
20 |
12 |
8136 |
QPSK |
32 |
15 to 24 |
|
25 |
Void |
||||||||||
26 |
15 |
20 |
13672 |
16QAM |
23 |
13 |
8744 |
QPSK |
36 |
15 to 24 |
|
27 |
Void |
||||||||||
28 |
15 |
21 |
14168 |
16QAM |
25 |
14 |
9560 |
QPSK |
41 |
15 to 24 |
|
29 |
15 |
22 |
14952 |
16QAM |
28 |
15 |
10088 |
QPSK |
44 |
15 to 24 |
|
30 |
15 |
23 |
15496 |
16QAM |
30 |
16 |
10840 |
QPSK |
48 |
15 to 24 |
|
31 |
15 |
24 |
16352 |
16QAM |
33 |
17 |
11432 |
QPSK |
51 |
15 to 24 |
|
32 |
15 |
25 |
16944 |
16QAM |
35 |
18 |
12280 |
QPSK |
55 |
15 to 24 |
|
33 |
15 |
26 |
17568 |
16QAM |
37 |
19 |
12960 |
QPSK |
58 |
15 to 24 |
|
34 |
15 |
n/a (27) |
17880 |
16QAM |
38 |
20 |
13672 |
QPSK |
61 |
15 to 24 |
See note 2 |
35 |
Void |
||||||||||
Note 1: The test point index is included to provide a unique reference to the different test points for the Dual Cell or MIMO mixed modulation case. Note 2: This test point is not applicable for the fixed RLC case as the number of MAC-d PDUs would have exceeded the maximum limit of 26 as specified by TS 25.321 clause 9.1.4. |
Table 14.1.3.4b.2.5: Test points for Dual Cell or MIMO and mix of 64QAM and QPSK for Dual Cell or MIMO data flow#1 and Dual Cell or MIMO data flow#2, fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
Test point Index See note 1 |
Number of codes |
Dual Cell or MIMO Flow#1 |
Dual Cell or MIMO Flow#2 |
Applicable Physical HS-DSCH UE categories |
Comments |
||||||
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS1) |
Modulation scheme (M1) |
TFRI1 |
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS2) |
Modulation scheme (M2) |
TFRI2 |
||||
1 |
2 |
3 |
2048 |
64QAM |
7 |
1 |
688 |
QPSK |
7 |
19, 20, 23, 24 |
|
2 |
4 |
6 |
4048 |
64QAM |
6 |
2 |
1360 |
QPSK |
6 |
19, 20, 23, 24 |
|
3 |
Void |
||||||||||
4 |
6 |
9 |
6112 |
64QAM |
6 |
3 |
2048 |
QPSK |
7 |
19, 20, 23, 24 |
|
5 |
Void |
||||||||||
6 |
8 |
12 |
8136 |
64QAM |
6 |
4 |
2736 |
QPSK |
6 |
19, 20, 23, 24 |
|
7 |
Void |
||||||||||
8 |
Void |
||||||||||
9 |
11 |
16 |
10840 |
64QAM |
4 |
5 |
3384 |
QPSK |
1 |
19, 20, 23, 24 |
|
10 |
Void |
||||||||||
11 |
Void |
||||||||||
12 |
13 |
18 |
12280 |
64QAM |
2 |
6 |
4048 |
QPSK |
1 |
19, 20, 23, 24 |
|
13 |
Void |
||||||||||
14 |
15 |
21 |
14168 |
64QAM |
1 |
7 |
4760 |
QPSK |
2 |
19, 20, 23, 24 |
|
15 |
Void |
||||||||||
16 |
15 |
22 |
14952 |
64QAM |
4 |
8 |
5392 |
QPSK |
9 |
19, 20, 23, 24 |
|
17 |
Void |
||||||||||
18 |
15 |
23 |
15496 |
64QAM |
6 |
9 |
6112 |
QPSK |
16 |
19, 20, 23, 24 |
|
19 |
Void |
||||||||||
20 |
15 |
24 |
16352 |
64QAM |
9 |
10 |
6808 |
QPSK |
22 |
19, 20, 23, 24 |
|
21 |
Void |
||||||||||
22 |
15 |
25 |
16944 |
64QAM |
11 |
11 |
7440 |
QPSK |
27 |
19, 20, 23, 24 |
|
23 |
Void |
||||||||||
24 |
15 |
26 |
17568 |
64QAM |
13 |
12 |
8136 |
QPSK |
32 |
19, 20, 23, 24 |
|
25 |
Void |
||||||||||
26 |
15 |
(27) |
17880 |
64QAM |
14 |
13 |
8744 |
QPSK |
36 |
19, 20, 23, 24 |
See note 2 |
27 |
Void |
||||||||||
28 |
15 |
(32) |
21384 |
64QAM |
24 |
14 |
9560 |
QPSK |
41 |
19, 20, 23, 24 |
See note 2 |
29 |
15 |
(37) |
24672 |
64QAM |
32 |
15 |
10088 |
QPSK |
44 |
19, 20, 23, 24 |
See note 2 |
30 |
15 |
(42) |
27960 |
64QAM |
39 |
16 |
10840 |
QPSK |
48 |
19, 20, 23, 24 |
See note 2 |
31 |
15 |
(46) |
30576 |
64QAM |
44 |
17 |
11432 |
QPSK |
51 |
19, 20, 23, 24 |
See note 2 |
32 |
15 |
(50) |
32848 |
64QAM |
48 |
18 |
12280 |
QPSK |
55 |
19, 20, 23, 24 |
See note 2 |
33 |
15 |
(56) |
37224 |
64QAM |
55 |
19 |
12960 |
QPSK |
58 |
20, 24 |
See note 2 |
34 |
15 |
(59) |
39272 |
64QAM |
58 |
20 |
13672 |
QPSK |
61 |
20, 24 |
See note 2 |
35 |
Void |
||||||||||
Note 1: The test point index is included to provide a unique reference to the different test points for the Dual-Cell or MIMO mixed modulation case. Note 2: This test point is not applicable for the fixed RLC case as the number of MAC-d PDUs would have exceeded the maximum limit of 26 as specified by TS 25.321 clause 9.1.4. |
Table 14.1.3.4b.2.6: Test points for Dual-Cell or MIMO and mix of 64QAM and 16QAM for Dual-Cell or MIMO data flow#1 and Dual-Cell or MIMO data flow#2, fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
Test point Index See note 1 |
Number of codes |
Dual-Cell or MIMO Flow#1 |
Dual-Cell or MIMO Flow#2 |
Applicable Physical HS-DSCH UE categories |
Comments |
||||||
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS1) |
Modulation scheme (M1) |
TFRI1 |
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS2) |
Modulation scheme (M2) |
TFRI2 |
||||
1 |
2 |
3 |
2048 |
64QAM |
7 |
2 |
1360 |
16QAM |
6 |
19, 20, 23, 24, 27, 28 |
|
2 |
4 |
6 |
4048 |
64QAM |
6 |
4 |
2736 |
16QAM |
6 |
19, 20, 23, 24, 27, 28 |
|
3 |
5 |
8 |
5392 |
64QAM |
9 |
5 |
3384 |
16QAM |
6 |
19, 20, 23, 24, 27, 28 |
|
4 |
6 |
9 |
6112 |
64QAM |
6 |
6 |
4048 |
16QAM |
6 |
19, 20, 23, 24, 27, 28 |
|
5 |
7 |
10 |
6808 |
64QAM |
3 |
7 |
4760 |
16QAM |
6 |
19, 20, 23, 24, 27, 28 |
|
6 |
8 |
12 |
8136 |
64QAM |
6 |
8 |
5392 |
16QAM |
6 |
19, 20, 23, 24, 27, 28 |
|
7 |
10 |
14 |
9560 |
64QAM |
3 |
9 |
6112 |
16QAM |
0 |
19, 20, 23, 24, 27, 28 |
|
8 |
Void |
||||||||||
9 |
11 |
16 |
10840 |
64QAM |
4 |
10 |
6808 |
16QAM |
1 |
19, 20, 23, 24, 27, 28 |
|
10 |
Void |
||||||||||
11 |
12 |
17 |
11432 |
64QAM |
2 |
11 |
7440 |
16QAM |
1 |
19, 20, 23, 24, 27, 28 |
|
12 |
13 |
18 |
12280 |
64QAM |
2 |
12 |
8136 |
16QAM |
2 |
19, 20, 23, 24, 27, 28 |
|
13 |
14 |
20 |
13672 |
64QAM |
4 |
13 |
8744 |
16QAM |
1 |
19, 20, 23, 24, 27, 28 |
|
14 |
15 |
21 |
14168 |
64QAM |
1 |
14 |
9560 |
16QAM |
3 |
19, 20, 23, 24, 27, 28 |
|
15 |
Void |
||||||||||
16 |
15 |
22 |
14952 |
64QAM |
4 |
15 |
10088 |
16QAM |
6 |
19, 20, 23, 24, 27, 28 |
|
17 |
Void |
||||||||||
18 |
15 |
23 |
15496 |
64QAM |
6 |
16 |
10840 |
16QAM |
10 |
19, 20, 23, 24, 27, 28 |
|
19 |
Void |
||||||||||
20 |
15 |
24 |
16352 |
64QAM |
9 |
17 |
11432 |
16QAM |
13 |
19, 20, 23, 24, 27, 28 |
|
21 |
Void |
||||||||||
22 |
15 |
25 |
16944 |
64QAM |
11 |
18 |
12280 |
16QAM |
17 |
19, 20, 23, 24, 27, 28 |
|
23 |
Void |
||||||||||
24 |
15 |
26 |
17568 |
64QAM |
13 |
19 |
12960 |
16QAM |
20 |
19, 20, 23, 24, 27, 28 |
|
25 |
Void |
||||||||||
26 |
15 |
(27) |
17880 |
64QAM |
14 |
20 |
13672 |
16QAM |
23 |
19, 20, 23, 24, 27, 28 |
See note 2 |
27 |
– |
– |
– |
– |
– |
Void |
|||||
28 |
15 |
(32) |
21384 |
64QAM |
24 |
21 |
14168 |
16QAM |
25 |
19, 20, 23, 24, 27, 28 |
See note 2 |
29 |
15 |
(37) |
24672 |
64QAM |
32 |
22 |
14952 |
16QAM |
28 |
19, 20, 23, 24, 27, 28 |
See note 2 |
30 |
15 |
(42) |
27960 |
64QAM |
39 |
23 |
15496 |
16QAM |
30 |
19, 20, 23, 24, 27, 28 |
See note 2 |
31 |
15 |
(46) |
30576 |
64QAM |
44 |
24 |
16352 |
16QAM |
33 |
19, 20, 23, 24, 27, 28 |
See note 2 |
32 |
15 |
(50) |
32848 |
64QAM |
48 |
25 |
16944 |
16QAM |
35 |
19, 20, 23, 24, 27, 28 |
See note 2 |
33 |
15 |
(56) |
37224 |
64QAM |
55 |
26 |
17568 |
16QAM |
37 |
20, 24, 28 |
See note 2 |
34 |
15 |
(59) |
39272 |
64QAM |
58 |
(27) |
17880 |
16QAM |
38 |
20, 24, 28 |
See note 2 |
35 |
15 |
(64) |
42192 |
64QAM |
62 |
(28) |
18536 |
16QAM |
40 |
20, 24, 28 |
See note 2 |
Note 1: The test point index is included to provide a unique reference to the different test points for the Dual-Cell or MIMO mixed modulation case. Note 2: This test point is not applicable for the fixed RLC case as the number of MAC-d PDUs would have exceeded the maximum limit of 26 as specified by TS 25.321 clause 9.1.4. |
Table 14.1.3.4b.2.7: Test points for Three-Cell and mix of 64QAM and 16QAM for Three-Cell data flow#1 and Three-Cell data flow#2 and Three-Cell data flow#3, fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
Test point Index See note 1 |
Number of codes |
Three-Cell Flow#1 |
Three-Cell Flow#2 |
Three-Cell Flow#3 |
Applicable Physical HS-DSCH UE categories |
Comments |
|||||||||
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS1) |
Modulation scheme (M1) |
TFRI1 |
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS2) |
Modulation scheme (M2) |
TFRI2 |
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS3) |
Modulation scheme (M3) |
TFRI3 |
||||
1 |
2 |
3 |
2048 |
64QAM |
7 |
3 |
2048 |
64QAM |
7 |
2 |
1360 |
16QAM |
6 |
29-32 |
|
2 |
4 |
6 |
4048 |
64QAM |
6 |
6 |
4048 |
64QAM |
6 |
4 |
2736 |
16QAM |
6 |
29-32 |
|
3 |
5 |
8 |
5392 |
64QAM |
9 |
8 |
5392 |
64QAM |
9 |
5 |
3384 |
16QAM |
6 |
29-32 |
|
4 |
6 |
9 |
6112 |
64QAM |
6 |
9 |
6112 |
64QAM |
6 |
6 |
4048 |
16QAM |
6 |
29-32 |
|
5 |
7 |
10 |
6808 |
64QAM |
3 |
10 |
6808 |
64QAM |
3 |
7 |
4760 |
16QAM |
6 |
29-32 |
|
6 |
8 |
12 |
8136 |
64QAM |
6 |
12 |
8136 |
64QAM |
6 |
8 |
5392 |
16QAM |
6 |
29-32 |
|
7 |
10 |
14 |
9560 |
64QAM |
3 |
14 |
9560 |
64QAM |
3 |
9 |
6112 |
16QAM |
0 |
29-32 |
|
8 |
Void |
||||||||||||||
9 |
11 |
16 |
10840 |
64QAM |
4 |
16 |
10840 |
64QAM |
4 |
10 |
6808 |
16QAM |
1 |
29-32 |
|
10 |
Void |
||||||||||||||
11 |
12 |
17 |
11432 |
64QAM |
2 |
17 |
11432 |
64QAM |
2 |
11 |
7440 |
16QAM |
1 |
29-32 |
|
12 |
13 |
18 |
12280 |
64QAM |
2 |
18 |
12280 |
64QAM |
2 |
12 |
8136 |
16QAM |
2 |
29-32 |
|
13 |
14 |
20 |
13672 |
64QAM |
4 |
20 |
13672 |
64QAM |
4 |
13 |
8744 |
16QAM |
1 |
29-32 |
|
14 |
15 |
21 |
14168 |
64QAM |
1 |
21 |
14168 |
64QAM |
1 |
14 |
9560 |
16QAM |
3 |
29-32 |
|
15 |
Void |
||||||||||||||
16 |
15 |
22 |
14952 |
64QAM |
4 |
22 |
14952 |
64QAM |
4 |
15 |
10088 |
16QAM |
6 |
29-32 |
|
17 |
Void |
||||||||||||||
18 |
15 |
23 |
15496 |
64QAM |
6 |
23 |
15496 |
64QAM |
6 |
16 |
10840 |
16QAM |
10 |
29-32 |
|
19 |
Void |
||||||||||||||
20 |
15 |
24 |
16352 |
64QAM |
9 |
24 |
16352 |
64QAM |
9 |
17 |
11432 |
16QAM |
13 |
29-32 |
|
21 |
Void |
||||||||||||||
22 |
15 |
25 |
16944 |
64QAM |
11 |
25 |
16944 |
64QAM |
11 |
18 |
12280 |
16QAM |
17 |
29-32 |
|
23 |
Void |
||||||||||||||
24 |
15 |
26 |
17568 |
64QAM |
13 |
26 |
17568 |
64QAM |
13 |
19 |
12960 |
16QAM |
20 |
29-32 |
|
25 |
Void |
||||||||||||||
26 |
15 |
(27) |
17880 |
64QAM |
14 |
(27) |
17880 |
64QAM |
14 |
20 |
13672 |
16QAM |
23 |
29-32 |
See Note 2 |
27 |
– |
– |
– |
– |
– |
Void |
|||||||||
28 |
15 |
(32) |
21384 |
64QAM |
24 |
(32) |
21384 |
64QAM |
24 |
21 |
14168 |
16QAM |
25 |
29-32 |
See Note 2 |
29 |
15 |
(37) |
24672 |
64QAM |
32 |
(37) |
24672 |
64QAM |
32 |
22 |
14952 |
16QAM |
28 |
29-32 |
See Note 2 |
30 |
15 |
(42) |
27960 |
64QAM |
39 |
(42) |
27960 |
64QAM |
39 |
23 |
15496 |
16QAM |
30 |
29-32 |
See Note 2 |
31 |
15 |
(46) |
30576 |
64QAM |
44 |
(46) |
30576 |
64QAM |
44 |
24 |
16352 |
16QAM |
33 |
29-32 |
See Note 2 |
32 |
15 |
(50) |
32848 |
64QAM |
48 |
(50) |
32848 |
64QAM |
48 |
25 |
16944 |
16QAM |
35 |
29-32 |
See Note 2 |
33 |
15 |
(56) |
37224 |
64QAM |
55 |
(56) |
37224 |
64QAM |
55 |
26 |
17568 |
16QAM |
37 |
29-32 |
See Note 2 |
34 |
15 |
(59) |
39272 |
64QAM |
58 |
(59) |
39272 |
64QAM |
58 |
(27) |
17880 |
16QAM |
38 |
29-32 |
See Note 2 |
35 |
15 |
(64) |
42192 |
64QAM |
62 |
(64) |
42192 |
64QAM |
62 |
(28) |
18536 |
16QAM |
40 |
29-32 |
See Note 2 |
Note 1: The test point index is included to provide a unique reference to the different test points for the Three-Cell mixed modulation case. Note 2: This test point is not applicable for the fixed RLC case as the number of MAC-d PDUs would have exceeded the maximum limit of 26 as specified by TS 25.321 clause 9.1.4. |
Table 14.1.3.4b.2.8: Test points for Three-Cell and mix of 64QAM and 16QAM and QPSK for Three-Cell data flow#1 and Three-Cell data flow#2 and Three-Cell data flow#3, fixed MAC-d PDU size=656 or flexible MAC-d PDU size; or for radio bearer combinations with mix of fixed and flexible MAC-d PDU sizes
Test point Index See note 1 |
Number of codes |
Three-Cell Flow#1 |
Three-Cell Flow#2 |
Three-Cell Flow#3 |
Applicable Physical HS-DSCH UE categories |
Comments |
|||||||||
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS1) |
Modulation scheme (M1) |
TFRI1 |
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS2) |
Modulation scheme (M2) |
TFRI2 |
# MAC-d PDUs# MAC-d PDUs for the fixed RLC case |
Selected TBS (TBS3) |
Modulation scheme (M3) |
TFRI3 |
||||
1 |
2 |
3 |
2048 |
64QAM |
7 |
2 |
1360 |
16QAM |
6 |
1 |
688 |
QPSK |
7 |
29-32 |
|
2 |
4 |
6 |
4048 |
64QAM |
6 |
4 |
2736 |
16QAM |
6 |
2 |
1360 |
QPSK |
6 |
29-32 |
|
3 |
Void |
||||||||||||||
4 |
6 |
9 |
6112 |
64QAM |
6 |
6 |
4048 |
16QAM |
6 |
3 |
2048 |
QPSK |
7 |
29-32 |
|
5 |
Void |
||||||||||||||
6 |
Void |
||||||||||||||
7 |
10 |
14 |
9560 |
64QAM |
3 |
9 |
6112 |
16QAM |
0 |
4 |
2736 |
QPSK |
0 |
29-32 |
|
8 |
Void |
||||||||||||||
9 |
11 |
16 |
10840 |
64QAM |
4 |
10 |
6808 |
16QAM |
1 |
5 |
3384 |
QPSK |
1 |
29-32 |
Void |
10 |
Void |
||||||||||||||
Void |
|||||||||||||||
12 |
13 |
18 |
12280 |
64QAM |
2 |
12 |
8136 |
16QAM |
2 |
6 |
4048 |
QPSK |
1 |
29-32 |
|
Void |
|||||||||||||||
14 |
15 |
21 |
14168 |
64QAM |
1 |
14 |
9560 |
16QAM |
3 |
7 |
4760 |
QPSK |
2 |
29-32 |
|
15 |
Void |
||||||||||||||
16 |
15 |
22 |
14952 |
64QAM |
4 |
15 |
10088 |
16QAM |
6 |
8 |
5392 |
QPSK |
9 |
29-32 |
|
17 |
Void |
||||||||||||||
18 |
15 |
23 |
15496 |
64QAM |
6 |
16 |
10840 |
16QAM |
10 |
9 |
6112 |
QPSK |
16 |
29-32 |
|
19 |
Void |
||||||||||||||
20 |
15 |
24 |
16352 |
64QAM |
9 |
17 |
11432 |
16QAM |
13 |
10 |
6808 |
QPSK |
22 |
29-32 |
|
21 |
Void |
||||||||||||||
22 |
15 |
25 |
16944 |
64QAM |
11 |
18 |
12280 |
16QAM |
17 |
11 |
7440 |
QPSK |
27 |
29-32 |
|
23 |
Void |
||||||||||||||
24 |
15 |
26 |
17568 |
64QAM |
13 |
19 |
12960 |
16QAM |
20 |
12 |
8136 |
QPSK |
32 |
29-32 |
|
25 |
Void |
||||||||||||||
26 |
15 |
(27) |
17880 |
64QAM |
14 |
20 |
13672 |
16QAM |
23 |
13 |
8744 |
QPSK |
36 |
29-32 |
See Note 2 |
27 |
Void |
||||||||||||||
28 |
15 |
(32) |
21384 |
64QAM |
24 |
21 |
14168 |
16QAM |
25 |
14 |
9560 |
QPSK |
41 |
29-32 |
See Note 2 |
29 |
15 |
(37) |
24672 |
64QAM |
32 |
22 |
14952 |
16QAM |
28 |
15 |
10088 |
QPSK |
44 |
29-32 |
See Note 2 |
30 |
15 |
(42) |
27960 |
64QAM |
39 |
23 |
15496 |
16QAM |
30 |
16 |
10840 |
QPSK |
48 |
29-32 |
See Note 2 |
31 |
15 |
(46) |
30576 |
64QAM |
44 |
24 |
16352 |
16QAM |
33 |
17 |
11432 |
QPSK |
51 |
29-32 |
See Note 2 |
32 |
15 |
(50) |
32848 |
64QAM |
48 |
25 |
16944 |
16QAM |
35 |
18 |
12280 |
QPSK |
55 |
29-32 |
See Note 2 |
33 |
15 |
(56) |
37224 |
64QAM |
55 |
26 |
17568 |
16QAM |
37 |
19 |
12960 |
QPSK |
58 |
29-32 |
See Note 2 |
34 |
15 |
(59) |
39272 |
64QAM |
58 |
(27) |
17880 |
16QAM |
38 |
20 |
13672 |
QPSK |
61 |
29-32 |
See Note 2 |
35 |
Void |
||||||||||||||
Note 1: The test point index is included to provide a unique reference to the different test points for the Three-Cell mixed modulation case. Note 2: This test point is not applicable for the fixed RLC case as the number of MAC-d PDUs would have exceeded the maximum limit of 26 as specified by TS 25.321 clause 9.1.4. |
14.1.3.5 Generic test procedure for HS-DSCH radio bearer combinations with non-enhanced Layer 2
This procedure is used to test HS-DSCH radio bearer combinations with non-enhanced layer 2. The procedure is run once for each sub-test of the actual HS-DSCH radio bearer test case.
Definition of test variables:
Ncodes |
Number of HS-DSCH codes (1..15, maximum number dependent on UE category) |
M |
Type of modulation scheme (QPSK, 16QAM, 64QAM) |
TBsize |
Transport Block size |
NPDUs |
Number of MAC-d PDUs |
HID |
HARQ process identifier (0..7) |
Initial conditions
UE in idle mode
Test procedure
a) The SS establish the reference radio bearer configuration as specified in TS 34.108, clause 6.10 for the actual radio bearer test. For the case when the reference radio bearer configuration includes radio bearers for both CS and PS domain then the radio bearer setup procedure has to be performed once per domain. The first radio bearer setup procedure shall perform configuration of the physical channel for the radio bearer combination under test as well as the transport channels for the CS radio bearer(s). The second radio bearer procedure shall perform the configuration for the transport channel for the PS radio bearers . The Physical channel configuration shall be done for both CS and PS radio bearers combined. Here the transport format combination set for both CS and PS radio bearers shall be provided. See note 1 and note 3.
b) The SS limits the UE allowed uplink transport format combinations according to the "Restricted UL TFCIs", as specified for the sub-test of the actual radio bearer test, using the RRC transport format combination control procedure. See note 2.
c) The SS closes the test loop using UE test loop mode 1 and setting the UL RLC SDU size parameter, for all radio bearers under test, according to the "UL RLC SDU size" value as specified for the sub-test of the actual radio bearer test.
d) The SS selects the first TFRC test point (NPDUs , M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.3 (MAC-d PDU size=336) or 14.1.3.4 (MAC-d PDU size=656).
e) The SS sets HID = 0.
f) The SS creates 4 DL RLC SDUs of size (NPDUs * MAC-d PDU payload size) / 4 minus 8 bits (size of 7 bit length indicator and expansion bit). See note 4.
g) The SS transmits, for each DTCH mapped to HS-DSCH, 4 DL RLC SDUs concatenated into a MAC-hs PDU using the selected TFRC and HID. If the radio bearer combination under test includes downlink DTCHs mapped to DCH then the SS transmits, for all DTCHs mapped to DCH, one or more RLC SDUs having the size equal to the "Test data size" as specified for the sub-test of the actual radio bearer test case.
h) The SS checks that the content of the UE returned RLC SDUs have the correct content and are received having the correct transport format. See TS 34.109 [10] clause 5.3.2.6.2 for details regarding the UE loopback of RLC SDUs.
i) The SS sets HID = (HID + 1) modulo Max_HID, where Max_HID equals the number of HARQ processes to be verified by the actual sub-test
j) The SS repeats steps f) to i) for the remaining TFRC test point (NPDUs , M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.3 (MAC-d PDU size=336) or 14.1.3.4 (MAC-d PDU size=656) for the UE category and MAC-d PDU size under test.
k) The SS opens the UE test loop.
l) The SS release the radio bearer. See note 5.
m) Steps a) to l) are repeated for all sub-tests. See note 6.
n) The SS may optionally deactivate the radio bearer test mode.
NOTE 1: The SS configures the physical channel parameters according to the actual UE category under test. The number of soft channel bits per HARQ process is split equally among the number of HARQ processes configured for the actual sub-test – i.e. “Total number of soft channel bits” for the UE category according to table 14.1.3.1.1 divided by the number of HARQ processes under test. The number of reordering queues is 1 for single HS-DSCH radio bearer configurations. The MAC-hs window size, RLC Transmission window size and RLC Receiving window size shall be configured as specified for the actual sub-test.
NOTE 2: The restricted set of uplink TFCIs shall contain all possible TFCI that could happen in a sub-test. The actual TTI of the different radio bearers and signalling radio bearers as well as the possible UE processing delays shall be taken into consideration. The restricted set of TFCIs must comply with the minimum set of TFCIs as specified in TS 25.331, clause 8.6.5.2.
NOTE 3: The MAC-hs window size and RLC Receiver and transmitter window sizes need to be chosen such that the UE capability for “Minimum total RLC AM and MAC-hs buffer size” is not exceeded for the UE category under test.
NOTE 4: The test data for DTCHs mapped on HS-DSCH is divided into 4 RLC SDUs to keep the maximum SDU size below or equal to 1500 octets (1500 octets is the limit of QoS parameter “Max SDU size” in SM).
NOTE 5: The Secondary scrambling code in the RADIO BEARER RELEASE message is set to the same value used in the RADIO BEARER SETUP MESSAGE.
NOTE 6: CS radio bearer is setup once during the first sub-test.
Expected sequence (repeated for each sub-test, see note 3)
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
Case A: PS radio bearers only |
||||
A1 |
<– |
SYSTEM INFORMATION (BCCH) |
Broadcast |
|
A2 |
<– |
PAGING TYPE 1 (PCCH) |
Paging (PS domain, P-TMSI) |
|
A3 |
–> |
RRC CONNECTION REQUEST (CCCH) |
RRC |
|
A4 |
<– |
RRC CONNECTION SETUP (CCCH) |
RRC |
|
A5 |
–> |
RRC CONNECTION SETUP COMPLETE (DCCH) |
RRC |
|
A6 |
–> |
SERVICE REQUEST (DCCH) |
GMM |
|
A7 |
<– |
SECURITY MODE COMMAND |
RRC see note 1 |
|
A8 |
–> |
SECURITY MODE COMPLETE |
RRC see note 1 |
|
A9 |
<– |
ACTIVATE RB TEST MODE (DCCH) |
TC |
|
A10 |
–> |
ACTIVATE RB TEST MODE COMPLETE (DCCH) |
TC |
|
A11 |
<– |
RADIO BEARER SETUP (DCCH) |
RRC PS radio bearer(s) are configured. For the PS radio bearer(s) the ‘pdcp info’ IE shall be omitted. |
|
A12 |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
End of branch for Case A |
||||
Case B: CS + PS radio bearers |
||||
B1 |
<– |
SYSTEM INFORMATION (BCCH) |
Broadcast |
|
B2 |
<– |
PAGING TYPE 1 (PCCH) |
Paging (CS domain, TMSI) |
|
B3 |
–> |
RRC CONNECTION REQUEST (CCCH) |
RRC |
|
B4 |
<– |
RRC CONNECTION SETUP (CCCH) |
RRC |
|
B5 |
–> |
RRC CONNECTION SETUP COMPLETE (DCCH) |
RRC |
|
B6 |
–> |
PAGING RESPONSE (DCCH) |
RR |
|
B6a |
<– |
AUTHENTICATION REQUEST |
||
B6b |
–> |
AUTHENTICATION RESPONSE |
||
B7 |
<– |
SECURITY MODE COMMAND |
||
B8 |
–> |
SECURITY MODE COMPLETE |
||
B9 |
<– |
PAGING TYPE 2 (DCCH) |
TMSI (GSM-MAP)/ P-TMSI |
|
B9a |
–> |
SERVICE REQUEST (DCCH) |
GMM |
|
B9b |
<– |
SECURITY MODE COMMAND |
RRC See note 2 |
|
B9c |
–> |
SECURITY MODE COMPLETE |
RRC |
|
B10 |
<– |
ACTIVATE RB TEST MODE (DCCH) |
TC |
|
B10a |
–> |
ACTIVATE RB TEST MODE COMPLETE (DCCH) |
TC |
|
B11 |
<– |
RADIO BEARER SETUP (DCCH) |
RRC CS radio bearer(s) are configured |
|
B12 |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
B12a |
<– |
RADIO BEARER SETUP (DCCH) |
RRC PS radio bearer(s) are configured. For the PS radio bearer the ‘pdcp info’ IE shall be omitted. |
|
B12b |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
End of branch for Case B |
||||
13 |
<– |
TRANSPORT FORMAT COMBINATION CONTROL (DCCH) |
RRC Transport format combinations is limited to "Restricted UL TFCIs", as specified for the sub-test |
|
14 |
<– |
CLOSE UE TEST LOOP (DCCH) |
TC UE test mode 1 RLC SDU size is for every active radio bearer set to "UL RLC SDU size", as specified for the sub-test. |
|
15 |
–> |
CLOSE UE TEST LOOP COMPLETE (DCCH) |
TC |
|
16 |
SS |
For each DTCHs mapped on HS-DSCH the SS creates test data for the first TFRC . The test data shall be dived into 4 RLC SDUs of size (NPDUs * MAC-d PDU payload size) / 4 – 8 bits. The SS sets HID = 0. |
||
17 |
<– |
DOWNLINK MAC-hs PDU (HS-DSCH#1) … DOWNLINK MAC-hs PDU (HS-DSCH#N) DL RLC SDU (DL DCH#1) … DL RLC SDU (DL DCH#M) |
For each DTCH mapped on HS-DSCH the SS sends test data divided into 4 RLC SDUs for HARQ processed HID. For each DTCH mapped on DCH the SS sends test data using the downlink transport format combination under test. |
|
18 |
–> |
UPLINK RLC SDUs |
The SS checks, for each DTCH, that the content and transport format of the received UL RLC SDUs are correct. |
|
19 |
SS |
The SS sets HID = (HID + 1) modulo Max_HID. The SS creates test data for the next TFRC and repeat steps 17 to 18 until all TFRCs have been tested. |
||
20 |
<– |
OPEN UE TEST LOOP (DCCH) |
TC |
|
21 |
–> |
OPEN UE TEST LOOP COMPLETE (DCCH) |
TC |
|
22 |
RB RELEASE |
RRC |
||
23 |
<– |
DEACTIVATE RB TEST MODE |
TC Optional step |
|
24 |
–> |
DEACTIVATE RB TEST MODE COMPLETE |
TC Optional step |
NOTE 1: In addition to activate integrity protection Step 6 and Step 7 are inserted in order to stop T3317 timer in the UE, which starts after transmitting SERVICE REQUEST message.
NOTE 2: For case B (CS+PS radio bearers) the second security mode procedure is needed to enable testing of ciphering on the PS radio bearers.
NOTE 3: For case A (PS radio bearers) steps A1 to A10 will be executed once during first sub-test. For case B (CS+PS radio bearers) steps B1 to B12 will be executed once during first sub-test.
14.1.3.5a Generic test procedure for HS-DSCH radio bearer combinations with enhanced Layer 2
This procedure is used to test HS-DSCH radio bearer combinations with enhanced Layer 2. The procedure is run once for each sub-test of the actual HS-DSCH radio bearer test case.
Definition of test variables common for both the flexible and fixed RLC cases:
Ncodes |
Number of HS-DSCH codes (1..15, maximum number dependent on UE category) |
M |
Type of modulation scheme (QPSK, 16QAM, 64QAM) |
M1 |
Type of modulation scheme for MIMO or Dual-Cell data flow#1 for the case different modulations schemes are used for the different data flows (QPSK, 16QAM, 64QAM) |
M2 |
Type of modulation scheme for MIMO or Dual-Cell data flow#2 for the case different modulations schemes are used for the different data flows (QPSK, 16QAM, 64QAM) |
M3 |
Type of modulation scheme for MIMO or Dual-Cell data flow#3 for the case different modulations schemes are used for the different data flows (QPSK, 16QAM, 64QAM) |
M4 |
Type of modulation scheme for MIMO or Dual-Cell data flow#4 for the case different modulations schemes are used for the different data flows (QPSK, 16QAM, 64QAM) |
TBsize |
Transport Block size |
TBsize1 |
Transport Block size for M1 modulation scheme. Applicable for Mimo or Dual Cell or combination of Dual Cell with MIMO |
TBsize2 |
Transport Block size for M2 modulation scheme. Applicable for Mimo or Dual Cell or combination of Dual Cell with MIMO |
TBsize3 |
Transport Block size for M3 modulation scheme. Applicable for combination of Dual Cell with MIMO |
TBsize4 |
Transport Block size for M4 modulation scheme. Applicable for combination of Dual Cell with MIMO |
HID |
HARQ process identifier (0..7 when MIMO is not supported or when Dual-Cell is supported 0..15 when MIMO is supported) |
HCONF |
Configured number of HARQ processes for the subtest |
Definition of additional test variables for the fixed RLC case:
NPDUs |
Number of MAC-d PDUs. |
Initial conditions
UE in idle mode
Test procedure
NOTE The test case should specify if the test procedure is to be executed for the MIMO case, Dual-Cell case or the combination Dual-Cell with MIMO case. If nothing is stated in the test case then the test procedure is to be executed for the non-MIMO or non-Dual-Cell case. The test case should also specify which modulation scheme M the testing is intended for, i.e. if more than one modulation schemes are to be tested then the test case need to specify multiple test executions, one for each modulation scheme. If nothing is specified in the test case then M=QPSK shall be assumed.
a) The SS establish the reference radio bearer configuration as specified in TS 34.108, clause 6.10 for the actual radio bearer test. For the case when the reference radio bearer configuration includes radio bearers for both CS and PS domain then the radio bearer setup procedure has to be performed once per domain. The first radio bearer setup procedure shall perform configuration of the physical channel for the radio bearer combination under test as well as the transport channels for the CS radio bearer(s). The second radio bearer procedure shall perform the configuration for the transport channel for the PS radio bearers . The Physical channel configuration shall be done for both CS and PS radio bearers combined. Here the transport format combination set for both CS and PS radio bearers shall be provided. See note 1 and note 3.
b) The SS limits the UE allowed uplink transport format combinations according to the "Restricted UL TFCIs", as specified for the sub-test of the actual radio bearer test, using the RRC transport format combination control procedure. See note 2.
c) The SS closes the test loop using UE test loop mode 1 and setting the UL RLC SDU size parameter, for all radio bearers under test, according to the "UL RLC SDU size" value as specified for the sub-test of the actual radio bearer test.
d) For the non-MIMO or non-Dual-Cell case: The SS selects the first TFRC test point (NPDUs , M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.4b.1 (MAC-d PDU size=336) or 14.1.3.4b.2 (MAC-d PDU size=656 or Flexible MAC-d PDU size).
For the MIMO or the Dual-Cell case and M1=M2=QPSK: The SS selects the first TFRC test point (NPDUs , M, Ncodes and TFRI) according to table 14.1.3.4b.2.1. Same TFRC test point is used for both data flows and TBsize1= TBsize2.
For the MIMO or the Dual-Cell case and M1=M2=16QAM: The SS selects the first TFRC test point (NPDUs , M, Ncodes and TFRI) according to table 14.1.3.4b.2.2. Same TFRC test point is used for both data flows and TBsize1= TBsize2.
For the MIMO or the Dual-Cell case and M1=M2=64QAM: The SS selects the first TFRC test point (NPDUs , M, Ncodes and TFRI) according to table 14.1.3.4b.2.3. Same TFRC test point is used for both data flows and TBsize1= TBsize2.
For the MIMO or the Dual-Cell case and M1=16QAM and M2=QPSK: The SS selects the first TFRC test points for data flows#1 (NPDUs1 , M1, Ncodes , TBsize1 and TFRI1) and data flows#2 (NPDUs2 , M2, Ncodes , TBsize2 and TFRI2) according to table 14.1.3.4b.2.4.
For the MIMO or the Dual-Cell case and M1=64QAM and M2=QPSK: The SS selects the first TFRC test points for data flows#1 (NPDUs1 , M1, Ncodes , TBsize1 and TFRI1) and data flows#2 (NPDUs2 , M2, Ncodes , TBsize2 and TFRI2) according to table 14.1.3.4b.2.5.
For the MIMO or the Dual-Cell case and M1=64QAM and M2=16QAM: The SS selects the first TFRC test points for data flows#1 (NPDUs1 , M1, Ncodes , TBsize1 and TFRI1) and data flows#2 (NPDUs2 , M2, Ncodes , TBsize2 and TFRI2) according to table 14.1.3.4b.2.6.
For the MIMO and Dual-Cell case and M1=M2=M3=M4=16QAM: The SS selects the first TFRC test point (NPDUs , Ncode, s,TBsize1 and TFRI) according to table 14.1.3.4b.2.2. The Same TFRC test point is used for all four data flows.
For the MIMO and Dual-Cell case and M1=M3=64QAM and M2=M4=16QAM: The SS selects the first TFRC test point for data flow#1 and data flow#3 in accordance to first 64QAM test point (NPDUs , Ncodes, TBsize and TFRI) in table 14.1.3.4b.2.6. The SS selects the first TFRC test point for data flow#2 and data flow#4 in accordance to first 16QAM test point (NPDUs , Ncodes, TBsize and TFRI) in table 14.1.3.4b.2.6.
For the MIMO and Dual-Cell case and M1=M2=M3=M4=64QAM: The SS selects the first TFRC test point (NPDUs , M, Ncodes and TFRI) according to table 14.1.3.4b.2.3. The Same TFRC test point is used for all four data flows.
e) The SS sets HID = 0.
f) For the fixed MAC-d PDU size case when neither MIMO nor Dual Cell is used: The SS creates 4 DL RLC SDUs of size (NPDUs * MAC-d PDU payload size) / 4 minus 8 bits (size of 7 bit length indicator and expansion bit). See note 4.
For the fixed MAC-d PDU size case when MIMO or Dual-Cell is used: The SS creates 8 DL RLC SDUs of size (NPDUs1 + NPDUs2 )* MAC-d PDU payload size) / 8 minus 8 bits (size of 7 bit length indicator and expansion bit). See note 4.
For the fixed MAC-d PDU size case when MIMO combined with Dual-Cell is used: The SS creates 16 DL RLC SDUs of size (NPDUs1 + NPDUs2 + NPDUs3 + NPDUs4)* MAC-d PDU payload size) / 16 minus 8 bits (size of 7 bit length indicator and expansion bit). See note 4.
For the flexible MAC-d PDU size case when neither MIMO nor Dual Cell is used: If the transport block size TBsize is >12032 bits the SS creates 4 DL RLC SDUs of size 8*FLOOR ((TBsize – 136 bit)/32). If the transport block size TBsize is ≤ 12032 bits the SS creates 1 DL RLC SDUs of size 8*FLOOR((TBsize – 40 bit)/8). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See note 4 and note 7.
For the flexible MAC-d PDU size case when MIMO or Dual-Cell is used and M1=M2: If the transport block size (TBsize1+ TBsize2) is >12032 bits the SS creates 8 DL RLC SDUs of size 8*FLOOR (((TBsize1 + TBsize2)– 272 bit)/64). If the transport block size (TBsize1+ TBsize2) is ≤ 12032 bits the SS creates 2 DL RLC SDUs of size 8*FLOOR(((TBsize1 + TBsize2)– 80 bit)/16). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See note 4 and note 7.
For the flexible MAC-d PDU size case when MIMO or Dual-Cell is used and M1 is different from M2: If the transport block size (TBsize1+ TBsize2) is >12032 bits the SS creates 8 DL RLC SDUs of size 8*FLOOR (((TBsize1 + TBsize2)– 288 bit)/64). If the transport block size (TBsize1+ TBsize2) is ≤ 12032 bits the SS creates 2 DL RLC SDUs of size 8*FLOOR(((TBsize1 + TBsize2)– 96 bit)/16). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See note 4 and note 7.
For the flexible MAC-d PDU size case when MIMO combined with Dual-Cell is used and M1=M2 and M3=M4: For Cell 1: If the transport block size (TBsize1+ TBsize2) is >12032 bits the SS creates 8 DL RLC SDUs of size 8*FLOOR (((TBsize1 + TBsize2)– 272 bit)/64). If the transport block size TBsize is ≤ 12032 bits the SS creates 2 DL RLC SDUs of size 8*FLOOR(((TBsize1 + TBsize2)– 80 bit)/16). For Cell 2: If the transport block size (TBsize3+ TBsize4) is >12032 bits the SS creates 8 DL RLC SDUs of size 8*FLOOR (((TBsize3 + TBsize4)– 272 bit)/64). If the transport block size (TBsize3+ TBsize4) is ≤ 12032 bits the SS creates 2 DL RLC SDUs of size 8*FLOOR(((TBsize3 + TBsize4)– 80 bit)/16). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See note 4.
For the flexible MAC-d PDU size case when MIMO combined with Dual-Cell is used and M1 is different from M2 and M3 is different from M4: For Cell 1: If the transport block size (TBsize1+ TBsize2) is >12032 bits the SS creates 8 DL RLC SDUs of size 8*FLOOR (((TBsize1 + TBsize2)– 288 bit)/64). If the transport block size (TBsize1+ TBsize2) is ≤ 12032 bits the SS creates 2 DL RLC SDUs of size 8*FLOOR(((TBsize1 + TBsize2)– 96 bit)/16). For Cell 2: If the transport block size (TBsize3+ TBsize4) is >12032 bits the SS creates 8 DL RLC SDUs of size 8*FLOOR (((TBsize3 + TBsize4)– 288 bit)/64). If the transport block size (TBsize3+ TBsize4) is ≤ 12032 bits the SS creates 2 DL RLC SDUs of size 8*FLOOR(((TBsize3 + TBsize4)– 96 bit)/16). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See note 4.
g) If neither MIMO nor Dual-Cell is used, then the SS transmits in one TTI, for each DTCH mapped to HS-DSCH, all the DL RLC PDUs generated in step f) concatenated into a MAC-ehs PDU using the selected TFRC and HID.
If Dual-Cell is used then the SS transmits in one TTI, for each DTCH mapped to HS-DSCH, all the DL RLC PDUs generated in step f) concatenated into two MAC-ehs PDU using the selected TFRC and HID.
If the radio bearer combination under test includes downlink DTCHs mapped to DCH then the SS transmits, for all DTCHs mapped to DCH, one or more RLC SDUs having the size equal to the "Test data size" as specified for the sub-test of the actual radio bearer test case. Goto step i).
h) If MIMO for non Dual-Cell case is used then the SS transmits in one TTI, for each DTCH mapped to HS-DSCH, the DL RLC PDUs generated in step f) concatenated into two MAC-ehs PDUs using the selected TFRC and the HARQ processes HID and (HID + HCONF/2) mod HCONF respectively.
If MIMO combined with Dual Cell is used then the SS transmits in one TTI, for each DTCH mapped to HS-DSCH, the DL RLC PDUs generated in step f) concatenated into two MAC-ehs PDUs per cell using the selected TFRC and the HARQ processes HID , (HID + HCONF/4) mod HCONF , (HID + HCONF/2) mod HCONF and (HID + 3*HCONF/4) mod HCONF respectively.
If the radio bearer combination under test includes downlink DTCHs mapped to DCH then the SS transmits, for all DTCHs mapped to DCH, one or more RLC SDUs having the size equal to the "Test data size" as specified for the sub-test of the actual radio bearer test case.
i) The SS checks that the content of the UE returned RLC SDUs have the correct content and are received having the correct transport format. See TS 34.109 [10] clause 5.3.2.6.2 for details regarding the UE loopback of RLC SDUs.
j) The SS sets HID = (HID + 1) modulo HCONF where HCONF is the configured number of processes and equals the number of HARQ processes to be verified by the actual sub-test
k) The SS repeats steps e) to j) for the remaining TFRC test points according to the applicable table in sub-clause 14.1.3.2.1a (principle for Enhanced Layer 2)
l) The SS repeats steps e) to j) for the remaining TFRC test point (NPDUs , M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.4b.1 (MAC-d PDU size=336) or 14.1.3.4b.2 (MAC-d PDU size=656 or Flexible MAC-d PDU size). m) The SS opens the UE test loop.
n) The SS release the radio bearer. See note 5.
o) Steps a) to n) are repeated for all sub-tests. See note 6.
p) The SS may optionally deactivate the radio bearer test mode.
NOTE 1: The SS configures the physical channel parameters according to the actual UE category under test. The number of soft channel bits per HARQ process is split equally among the number of HARQ processes configured for the actual sub-test – i.e. “Total number of soft channel bits” for the UE category according to table 14.1.3.1.1 divided by the number of HARQ processes under test. The number of reordering queues is 1 for single HS-DSCH radio bearer configurations. The MAC-hs window size, RLC Transmission window size and RLC Receiving window size shall be configured as specified for the actual sub-test.
NOTE 2: The restricted set of uplink TFCIs shall contain all possible TFCI that could happen in a sub-test. The actual TTI of the different radio bearers and signalling radio bearers as well as the possible UE processing delays shall be taken into consideration. The restricted set of TFCIs must comply with the minimum set of TFCIs as specified in TS 25.331, clause 8.6.5.2. Not applicable for Cell-FACH state.
NOTE 3: The MAC-hs window size and RLC Receiver and transmitter window sizes need to be chosen such that the UE capability for “Minimum total RLC AM and MAC-hs buffer size” is not exceeded for the UE category under test.
NOTE 4: The test data for DTCHs mapped on HS-DSCH is divided into multiple RLC SDUs to keep the maximum SDU size below or equal to 1500 octets (1500 octets is the limit of QoS parameter “Max SDU size” in SM). To allow for testing of the smallest TB sizes a single RLC PDU is used when the TB size is equal or below 12032 bits to reduce the L2 header overhead. 12032 bits corresponds to maximum RLC SDU size of 1500 octets (12000 bits) plus MAC-ehs header size of 24 bits and minimum possible RLC PDU header (8 bits for UM RLC). The actual maximum RLC SDU size to be used will depend of the RLC configuration for the radio bearer under test. For UM radio bearer the maximum RLC SDU will be 1500 octets for the case UMD PDU header of 8 bits. For AM radio bearers the maximum RLC SDU size will be 1499 octets for AMD PDU header of 16 bits.
NOTE 5: The Secondary scrambling code in the RADIO BEARER RELEASE message is set to the same value used in the RADIO BEARER SETUP MESSAGE.
NOTE 6: CS radio bearer is setup once during the first sub-test.
NOTE 7: The formulas for calculating the largest possible RLC SDU sizes take into account the required MAC-ehs headers and maximum RLC PDU AM headers to concatenate the RLC PDUs into MAC-ehs PDU(s). For the case when two MAC-ehs PDUs are used (MIMO or Dual-Cell) and the transport block sizes for the two data streams are different then additional space is reserved for the MAC-ehs header due to the MAC-ehs SDU segmentation between the two MAC-ehs PDUs (additional 16 bit LCH-ID+L+F MAC-ehs header). In the test procedure this will happen when the different data streams use different modulation schemes (M1 and M2 not equal).
Expected sequence (repeated for each sub-test, see note 3)
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
Case A: PS radio bearers only |
||||
A1 |
<– |
SYSTEM INFORMATION (BCCH) |
Broadcast |
|
A2 |
<– |
PAGING TYPE 1 (PCCH) |
Paging (PS domain, P-TMSI) |
|
A3 |
–> |
RRC CONNECTION REQUEST (CCCH) |
RRC |
|
A4 |
<– |
RRC CONNECTION SETUP (CCCH) |
RRC |
|
A5 |
–> |
RRC CONNECTION SETUP COMPLETE (DCCH) |
RRC |
|
A6 |
–> |
SERVICE REQUEST (DCCH) |
GMM |
|
A7 |
<– |
SECURITY MODE COMMAND |
RRC see note 1 |
|
A8 |
–> |
SECURITY MODE COMPLETE |
RRC see note 1 |
|
A9 |
<– |
ACTIVATE RB TEST MODE (DCCH) |
TC |
|
A10 |
–> |
ACTIVATE RB TEST MODE COMPLETE (DCCH) |
TC |
|
A11 |
<– |
RADIO BEARER SETUP (DCCH) |
RRC PS radio bearer(s) are configured. For the PS radio bearer(s) the ‘pdcp info’ IE shall be omitted. |
|
A12 |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
End of branch for Case A |
||||
Case B: CS + PS radio bearers |
||||
B1 |
<– |
SYSTEM INFORMATION (BCCH) |
Broadcast |
|
B2 |
<– |
PAGING TYPE 1 (PCCH) |
Paging (CS domain, TMSI) |
|
B3 |
–> |
RRC CONNECTION REQUEST (CCCH) |
RRC |
|
B4 |
<– |
RRC CONNECTION SETUP (CCCH) |
RRC |
|
B5 |
–> |
RRC CONNECTION SETUP COMPLETE (DCCH) |
RRC |
|
B6 |
–> |
PAGING RESPONSE (DCCH) |
RR |
|
B6a |
<– |
AUTHENTICATION REQUEST |
||
B6b |
–> |
AUTHENTICATION RESPONSE |
||
B7 |
<– |
SECURITY MODE COMMAND |
||
B8 |
–> |
SECURITY MODE COMPLETE |
||
B9 |
<– |
PAGING TYPE 2 (DCCH) |
TMSI (GSM-MAP)/ P-TMSI |
|
B9a |
–> |
SERVICE REQUEST (DCCH) |
GMM |
|
B9b |
<– |
SECURITY MODE COMMAND |
RRC See note 2 |
|
B9c |
–> |
SECURITY MODE COMPLETE |
RRC |
|
B10 |
<– |
ACTIVATE RB TEST MODE (DCCH) |
TC |
|
B10a |
–> |
ACTIVATE RB TEST MODE COMPLETE (DCCH) |
TC |
|
B11 |
<– |
RADIO BEARER SETUP (DCCH) |
RRC CS radio bearer(s) are configured |
|
B12 |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
B12a |
<– |
RADIO BEARER SETUP (DCCH) |
RRC PS radio bearer(s) are configured. For the PS radio bearer the ‘pdcp info’ IE shall be omitted. |
|
B12b |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
End of branch for Case B |
||||
13 |
<– |
TRANSPORT FORMAT COMBINATION CONTROL (DCCH) |
RRC Transport format combinations is limited to "Restricted UL TFCIs", as specified for the sub-test Not applicable for Cell-FACH state |
|
14 |
<– |
CLOSE UE TEST LOOP (DCCH) |
TC UE test mode 1 RLC SDU size is for every active radio bearer set to "UL RLC SDU size", as specified for the sub-test. |
|
15 |
–> |
CLOSE UE TEST LOOP COMPLETE (DCCH) |
TC |
|
16 |
SS |
For each DTCHs mapped on HS-DSCH the SS creates test data for the first test point. |
||
17 |
<– |
DOWNLINK MAC-ehs PDU (HS-DSCH#1) … DOWNLINK MAC-ehs PDU (HS-DSCH#N) DL RLC SDU (DL DCH#1) … DL RLC SDU (DL DCH#M) |
For each DTCH mapped on HS-DSCH the SS sends test for HARQ processed HID. For each DTCH mapped on DCH the SS sends test data using the downlink transport format combination under test. |
|
18 |
–> |
UPLINK RLC SDUs |
The SS checks, for each DTCH, that the content and transport format of the received UL RLC SDUs are correct. |
|
19 |
SS |
The SS sets HID = (HID + 1) modulo HCONF. The SS creates test data for the next TFRC and repeat steps 17 to 18 until all TFRCs have been tested. |
||
20 |
<– |
OPEN UE TEST LOOP (DCCH) |
TC |
|
21 |
–> |
OPEN UE TEST LOOP COMPLETE (DCCH) |
TC |
|
22 |
RB RELEASE |
RRC |
||
23 |
<– |
DEACTIVATE RB TEST MODE |
TC Optional step |
|
24 |
–> |
DEACTIVATE RB TEST MODE COMPLETE |
TC Optional step |
NOTE 1: In addition to activate integrity protection Step 6 and Step 7 are inserted in order to stop T3317 timer in the UE, which starts after transmitting SERVICE REQUEST message.
NOTE 2: For case B (CS+PS radio bearers) the second security mode procedure is needed to enable testing of ciphering on the PS radio bearers.
NOTE 3: For case A (PS radio bearers) steps A1 to A10 will be executed once during first sub-test. For case B (CS+PS radio bearers) steps B1 to B12 will be executed once during first sub-test.
Specific Message Content:
Use the same RADIO BEARER SETUP message as specified in 34.108 with the following exceptions for step A11, B12a :
Information Element |
Value/remark |
Version |
---|---|---|
HS-DSCH TB size table |
octet aligned |
Rel-7 |
14.1.3.5b Generic test procedure for HS-DSCH radio bearer combinations with enhanced Layer 2 for Three-Cell case
This procedure is used to test HS-DSCH radio bearer combinations with enhanced Layer 2 for three-cell case. The procedure is run once for each sub-test of the actual HS-DSCH radio bearer test case.
Definition of test variables common for both the flexible and fixed RLC cases:
Ncodes |
Number of HS-DSCH codes (1..15, maximum number dependent on UE category) |
M |
Type of modulation scheme (QPSK, 16QAM, 64QAM) |
M1 |
Type of modulation scheme for Three-Cell data flow#1 for the case different modulations schemes are used for the different data flows (QPSK, 16QAM, 64QAM) |
M2 |
Type of modulation scheme for Three-Cell data flow#2 for the case different modulations schemes are used for the different data flows (QPSK, 16QAM, 64QAM) |
M3 |
Type of modulation scheme for Three-Cell data flow#3 for the case different modulations schemes are used for the different data flows (QPSK, 16QAM, 64QAM) |
TBsize |
Transport Block size |
TBsize1 |
Transport Block size for M1 modulation scheme. Applicable for Three-Cell |
TBsize2 |
Transport Block size for M2 modulation scheme. Applicable for Three-Cell |
TBsize3 |
Transport Block size for M3 modulation scheme. Applicable for Three-Cell |
HID |
HARQ process identifier (0..7) |
HCONF |
Configured number of HARQ processes for the subtest |
Definition of additional test variables for the fixed RLC case:
NPDUs |
Number of MAC-d PDUs. |
Initial conditions
UE in idle mode
Test procedure
NOTE The test case should specify if the test procedure is to be executed for Three-Cell case. If nothing is stated in the test case then the test procedure is to be executed for the non-Three-Cell case. The test case should also specify which modulation scheme M the testing is intended for, i.e. if more than one modulation schemes are to be tested then the test case need to specify multiple test executions, one for each modulation scheme. If nothing is specified in the test case then M=QPSK shall be assumed.
a) The SS establish the reference radio bearer configuration as specified in TS 34.108, clause 6.10 for the actual radio bearer test. For the case when the reference radio bearer configuration includes radio bearers for both CS and PS domain then the radio bearer setup procedure has to be performed once per domain. The first radio bearer setup procedure shall perform configuration of the physical channel for the radio bearer combination under test as well as the transport channels for the CS radio bearer(s). The second radio bearer procedure shall perform the configuration for the transport channel for the PS radio bearers. The Physical channel configuration shall be done for both CS and PS radio bearers combined. Here the transport format combination set for both CS and PS radio bearers shall be provided. See NOTE 1 and NOTE 3.
b) The SS limits the UE allowed uplink transport format combinations according to the "Restricted UL TFCIs", as specified for the sub-test of the actual radio bearer test, using the RRC transport format combination control procedure. See NOTE 2.
c) The SS closes the test loop using UE test loop mode 1 and setting the UL RLC SDU size parameter, for all radio bearers under test, according to the "UL RLC SDU size" value as specified for the sub-test of the actual radio bearer test.
d) For the non-Three-Cell case: The SS selects the first TFRC test point (NPDUs, M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.4b.1 (MAC-d PDU size=336) or 14.1.3.4b.2 (MAC-d PDU size=656 or Flexible MAC-d PDU size).
For the Three-Cell case and M1=M2=M3=QPSK: The SS selects the first TFRC test point (NPDUs, M, Ncodes and TFRI) according to table 14.1.3.4b.2.1. Same TFRC test point is used for all data flows and TBsize1=TBsize2=TBsize3.
For the Three-Cell case and M1=M2=M3=16QAM: The SS selects the first TFRC test point (NPDUs, M, Ncodes and TFRI) according to table 14.1.3.4b.2.2. Same TFRC test point is used for all data flows and TBsize1=TBsize2=TBsize3.
For the Three-Cell case and M1=M2=M3=64QAM: The SS selects the first TFRC test point (NPDUs, M, Ncodes and TFRI) according to table 14.1.3.4b.2.3. Same TFRC test point is used for all data flows and TBsize1=TBsize2=TBsize3.
For the Three-Cell case and M1=M2=64QAM and M3=16QAM: The SS selects the first TFRC test points for data flows#1 (NPDUs1, M1, Ncodes, TBsize1 and TFRI1) and data flows#2 (NPDUs2, M2, Ncodes, TBsize2 and TFRI2) and data flows#3 (NPDUs2, M3, Ncodes, TBsize3 and TFRI3) according to table 14.1.3.4b.2.7.
For the Three-Cell case and M1= 64QAM and M2=16QAM and M3=QPSK: The SS selects the first TFRC test points for data flows#1 (NPDUs1, M1, Ncodes, TBsize1 and TFRI1) and data flows#2 (NPDUs2, M2, Ncodes, TBsize2 and TFRI2) and data flows#3 (NPDUs3, M3, Ncodes, TBsize3 and TFRI3) according to table 14.1.3.4b.2.8.
e) The SS sets HID = 0.
f) For the fixed MAC-d PDU size case when no Three-Cell is used: The SS creates 4 DL RLC SDUs of size (NPDUs * MAC-d PDU payload size) / 4 minus 8 bits (size of 7 bit length indicator and expansion bit). See NOTE 4.
For the fixed MAC-d PDU size case when Three-Cell is used: The SS creates 12 DL RLC SDUs of size (NPDUs1 + NPDUs2 + NPDUs3)* MAC-d PDU payload size) / 12 minus 8 bits (size of 7 bit length indicator and expansion bit). See NOTE 4.
For the flexible MAC-d PDU size case when no Three-Cell is used: If the transport block size TBsize is >12032 bits the SS creates 4 DL RLC SDUs of size 8*FLOOR ((TBsize – 136 bit)/32). If the transport block size TBsize is ≤ 12032 bits the SS creates 1 DL RLC SDUs of size 8*FLOOR((TBsize – 40 bit)/8). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See NOTE 4 and NOTE 7.
For the flexible MAC-d PDU size case Three-Cell is used and M1=M2=M3: If the transport block size (TBsize1+TBsize2+TBsize3)is >12032 bits the SS creates 12 DL RLC SDUs of size 8*FLOOR (((TBsize1 + TBsize2+TBsize3)– 408 bit)/96). If the transport block size (TBsize1+TBsize2+TBsize3) is ≤ 12032 bits the SS creates 3 DL RLC SDUs of size 8*FLOOR(((TBsize1 + TBsize2 +TBsize3)– 120 bit)/24). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See NOTE 4 and NOTE 7.
For the flexible MAC-d PDU size case Three-Cell is used and M1= M2 but different to M3: If the transport block size (TBsize1+TBsize2+TBsize3)is >12032 bits the SS creates 12 DL RLC SDUs of size 8*FLOOR (((TBsize1 + TBsize2+TBsize3)– 440 bit)/96). If the transport block size (TBsize1+TBsize2+TBsize3) is ≤ 12032 bits the SS creates 3 DL RLC SDUs of size 8*FLOOR(((TBsize1 + TBsize2 +TBsize3)– 152 bit)/24). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See NOTE 4 and NOTE 7.
For the flexible MAC-d PDU size case Three-Cell is used and M1, M2 and M3 are different: If the transport block size (TBsize1+TBsize2+TBsize3)is >12032 bits the SS creates 12 DL RLC SDUs of size 8*FLOOR (((TBsize1 + TBsize2+TBsize3)– 456 bit)/96). If the transport block size (TBsize1+TBsize2+TBsize3) is ≤ 12032 bits the SS creates 3 DL RLC SDUs of size 8*FLOOR(((TBsize1 + TBsize2 +TBsize3)– 168 bit)/24). The SS creates a DL RLC PDU for each DL RLC SDU using the special value of HE field (‘10’) in the RLC PDU header. See NOTE 4 and NOTE 7
g) If no Three-Cell is used, then the SS transmits in one TTI, for each DTCH mapped to HS-DSCH, all the DL RLC PDUs generated in step f) concatenated into a MAC-ehs PDU using the selected TFRC and HID.
If Three-Cell is used then the SS transmits in one TTI, for each DTCH mapped to HS-DSCH, all the DL RLC PDUs generated in step f) concatenated into two MAC-ehs PDU using the selected TFRC and HID.
If the radio bearer combination under test includes downlink DTCHs mapped to DCH then the SS transmits, for all DTCHs mapped to DCH, one or more RLC SDUs having the size equal to the "Test data size" as specified for the sub-test of the actual radio bearer test case. Goto step i).
h) The SS checks that the content of the UE returned RLC SDUs have the correct content and are received having the correct transport format. See TS 34.109 [10] clause 5.3.2.6.2 for details regarding the UE loopback of RLC SDUs.
i) The SS sets HID = (HID + 1) modulo HCONF where HCONF is the configured number of processes and equals the number of HARQ processes to be verified by the actual sub-test
j) The SS repeats steps e) to i) for the remaining TFRC test points according to the applicable table in sub-clause 14.1.3.2.1a (principle for Enhanced Layer 2)
k) The SS repeats steps e) to j) for the remaining TFRC test point (NPDUs , M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.4b.1 (MAC-d PDU size=336) or 14.1.3.4b.2 (MAC-d PDU size=656 or Flexible MAC-d PDU size).
l) The SS opens the UE test loop.
m) The SS release the radio bearer. See NOTE 5.
n) Steps a) to m) are repeated for all sub-tests. See NOTE 6.
o) The SS may optionally deactivate the radio bearer test mode.
NOTE 1: The SS configures the physical channel parameters according to the actual UE category under test. The number of soft channel bits per HARQ process is split equally among the number of HARQ processes configured for the actual sub-test – i.e. “Total number of soft channel bits” for the UE category according to table 14.1.3.1.1 divided by the number of HARQ processes under test. The number of reordering queues is 1 for single HS-DSCH radio bearer configurations. The MAC-hs window size, RLC Transmission window size and RLC Receiving window size shall be configured as specified for the actual sub-test.
NOTE 2: The restricted set of uplink TFCIs shall contain all possible TFCI that could happen in a sub-test. The actual TTI of the different radio bearers and signalling radio bearers as well as the possible UE processing delays shall be taken into consideration. The restricted set of TFCIs must comply with the minimum set of TFCIs as specified in TS 25.331, clause 8.6.5.2. Not applicable for Cell-FACH state.
NOTE 3: The MAC-hs window size and RLC Receiver and transmitter window sizes need to be chosen such that the UE capability for “Minimum total RLC AM and MAC-hs buffer size” is not exceeded for the UE category under test.
NOTE 4: The test data for DTCHs mapped on HS-DSCH is divided into multiple RLC SDUs to keep the maximum SDU size below or equal to 1500 octets (1500 octets is the limit of QoS parameter “Max SDU size” in SM). To allow for testing of the smallest TB sizes a single RLC PDU is used when the TB size is equal or below 12032 bits to reduce the L2 header overhead. 12032 bits corresponds to maximum RLC SDU size of 1500 octets (12000 bits) plus MAC-ehs header size of 24 bits and minimum possible RLC PDU header (8 bits for UM RLC). The actual maximum RLC SDU size to be used will depend of the RLC configuration for the radio bearer under test. For UM radio bearer the maximum RLC SDU will be 1500 octets for the case UMD PDU header of 8 bits. For AM radio bearers the maximum RLC SDU size will be 1499 octets for AMD PDU header of 16 bits.
NOTE 5: The Secondary scrambling code in the RADIO BEARER RELEASE message is set to the same value used in the RADIO BEARER SETUP MESSAGE.
NOTE 6: CS radio bearer is setup once during the first sub-test.
NOTE 7: The formulas for calculating the largest possible RLC SDU sizes take into account the required MAC-ehs headers and maximum RLC PDU AM headers to concatenate the RLC PDUs into MAC-ehs PDU(s). For the case when three MAC-ehs PDUs are used (Three-Cell) and the transport block sizes for the three data streams are different then additional space is reserved for the MAC-ehs header due to the MAC-ehs SDU segmentation between the three MAC-ehs PDUs (additional 16 bit LCH-ID+L+F MAC-ehs header). In the test procedure this will happen when the different data streams use different modulation schemes (M1 and M2 and M3 not equal).
Expected sequence (repeated for each sub-test, see note 3)
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
Case A: PS radio bearers only |
||||
A1 |
<– |
SYSTEM INFORMATION (BCCH) |
Broadcast |
|
A2 |
<– |
PAGING TYPE 1 (PCCH) |
Paging (PS domain, P-TMSI) |
|
A3 |
–> |
RRC CONNECTION REQUEST (CCCH) |
RRC |
|
A4 |
<– |
RRC CONNECTION SETUP (CCCH) |
RRC |
|
A5 |
–> |
RRC CONNECTION SETUP COMPLETE (DCCH) |
RRC |
|
A6 |
–> |
SERVICE REQUEST (DCCH) |
GMM |
|
A7 |
<– |
SECURITY MODE COMMAND |
RRC see note 1 |
|
A8 |
–> |
SECURITY MODE COMPLETE |
RRC see note 1 |
|
A9 |
<– |
ACTIVATE RB TEST MODE (DCCH) |
TC |
|
A10 |
–> |
ACTIVATE RB TEST MODE COMPLETE (DCCH) |
TC |
|
A11 |
<– |
RADIO BEARER SETUP (DCCH) |
RRC PS radio bearer(s) are configured. For the PS radio bearer(s) the ‘pdcp info’ IE shall be omitted. |
|
A12 |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
End of branch for Case A |
||||
Case B: CS + PS radio bearers |
||||
B1 |
<– |
SYSTEM INFORMATION (BCCH) |
Broadcast |
|
B2 |
<– |
PAGING TYPE 1 (PCCH) |
Paging (CS domain, TMSI) |
|
B3 |
–> |
RRC CONNECTION REQUEST (CCCH) |
RRC |
|
B4 |
<– |
RRC CONNECTION SETUP (CCCH) |
RRC |
|
B5 |
–> |
RRC CONNECTION SETUP COMPLETE (DCCH) |
RRC |
|
B6 |
–> |
PAGING RESPONSE (DCCH) |
RR |
|
B6a |
<– |
AUTHENTICATION REQUEST |
||
B6b |
–> |
AUTHENTICATION RESPONSE |
||
B7 |
<– |
SECURITY MODE COMMAND |
||
B8 |
–> |
SECURITY MODE COMPLETE |
||
B9 |
<– |
PAGING TYPE 2 (DCCH) |
TMSI (GSM-MAP)/ P-TMSI |
|
B9a |
–> |
SERVICE REQUEST (DCCH) |
GMM |
|
B9b |
<– |
SECURITY MODE COMMAND |
RRC See note 2 |
|
B9c |
–> |
SECURITY MODE COMPLETE |
RRC |
|
B10 |
<– |
ACTIVATE RB TEST MODE (DCCH) |
TC |
|
B10a |
–> |
ACTIVATE RB TEST MODE COMPLETE (DCCH) |
TC |
|
B11 |
<– |
RADIO BEARER SETUP (DCCH) |
RRC CS radio bearer(s) are configured |
|
B12 |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
B12a |
<– |
RADIO BEARER SETUP (DCCH) |
RRC PS radio bearer(s) are configured. For the PS radio bearer the ‘pdcp info’ IE shall be omitted. |
|
B12b |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
End of branch for Case B |
||||
13 |
<– |
TRANSPORT FORMAT COMBINATION CONTROL (DCCH) |
RRC Transport format combinations is limited to "Restricted UL TFCIs", as specified for the sub-test Not applicable for Cell-FACH state |
|
14 |
<– |
CLOSE UE TEST LOOP (DCCH) |
TC UE test mode 1 RLC SDU size is for every active radio bearer set to "UL RLC SDU size", as specified for the sub-test. |
|
15 |
–> |
CLOSE UE TEST LOOP COMPLETE (DCCH) |
TC |
|
16 |
SS |
For each DTCHs mapped on HS-DSCH the SS creates test data for the first test point. |
||
17 |
<– |
DOWNLINK MAC-ehs PDU (HS-DSCH#1) … DOWNLINK MAC-ehs PDU (HS-DSCH#N) DL RLC SDU (DL DCH#1) … DL RLC SDU (DL DCH#M) |
For each DTCH mapped on HS-DSCH the SS sends test for HARQ processed HID. For each DTCH mapped on DCH the SS sends test data using the downlink transport format combination under test. |
|
18 |
–> |
UPLINK RLC SDUs |
The SS checks, for each DTCH, that the content and transport format of the received UL RLC SDUs are correct. |
|
19 |
SS |
The SS sets HID = (HID + 1) modulo HCONF. The SS creates test data for the next TFRC and repeat steps 17 to 18 until all TFRCs have been tested. |
||
20 |
<– |
OPEN UE TEST LOOP (DCCH) |
TC |
|
21 |
–> |
OPEN UE TEST LOOP COMPLETE (DCCH) |
TC |
|
22 |
RB RELEASE |
RRC |
||
23 |
<– |
DEACTIVATE RB TEST MODE |
TC Optional step |
|
24 |
–> |
DEACTIVATE RB TEST MODE COMPLETE |
TC Optional step |
NOTE 1: In addition to activate integrity protection Step 6 and Step 7 are inserted in order to stop T3317 timer in the UE, which starts after transmitting SERVICE REQUEST message.
NOTE 2: For case B (CS+PS radio bearers) the second security mode procedure is needed to enable testing of ciphering on the PS radio bearers.
NOTE 3: For case A (PS radio bearers) steps A1 to A10 will be executed once during first sub-test. For case B (CS+PS radio bearers) steps B1 to B12 will be executed once during first sub-test.
Specific Message Content:
Use the same RADIO BEARER SETUP message as specified in 34.108 with the following exceptions for step A11, B12a:
Information Element |
Value/remark |
Version |
---|---|---|
HS-DSCH TB size table |
octet aligned |
Rel-7 |
14.1.3.6 Generic test procedure for HS-DSCH radio bearer combinations with AMR RB configurations using SRB#5 for TFC control
This procedure is used to test AMR radio bearer using SRB#5 for TFC control in combination with HS-DSCH radio bearers. The procedure is run once for each sub-test of the actual HS-DSCH radio bearer test case.
Definition of test variables:
Ncodes |
Number of HS-DSCH codes (1..15, maximum number dependent on UE category) |
M |
Type of modulation scheme (QPSK, 16QAM) |
TBsize |
Transport Block size |
NPDUs |
Number of MAC-d PDUs |
HID |
HARQ process identifier (0..7) |
Initial conditions
UE in idle mode
Test procedure
a) The SS establish the reference radio bearer configuration as specified in TS 34.108, clause 6.10 for the actual radio bearer test. As part of the RADIO BEARER SETUP the TFC subsets as defined for the actual radio bearer configuration is setup. The radio bearer setup procedure has to be performed once per domain. The first radio bearer setup procedure shall perform configuration of the physical channel for the radio bearer combination under test as well as the transport channels for the CS radio bearer(s). The second radio bearer procedure shall perform the configuration for the transport channel for the PS radio bearers . The Physical channel configuration shall be done for both CS and PS radio bearers combined. Here the transport format combination set for both CS and PS radio bearers shall be provided. See note 1 and note 3.
b) The SS signals the “TFC subset identity” in the TRANSPORT FORMAT COMBINATION CONTROL message on SRB#5 as specified for the sub-test of the actual AMR radio bearer test. See note 6.
c) The SS closes the test loop using UE test loop mode 1 and setting the UL RLC SDU size parameter, for all radio bearers under test, according to the "UL RLC SDU size" value as specified for the sub-test of the actual radio bearer test.
d) The SS selects the first TFRC test point (NPDUs , M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.3 (MAC-d PDU size=336) or 14.1.3.4 (MAC-d PDU size=656).
e) The SS sets HID = 0.
f) The SS creates 4 DL RLC SDUs of size (NPDUs * MAC-d PDU payload size) / 4 minus 8 bits (size of 7 bit length indicator and expansion bit). See note 4.
g) The SS transmits, for each DTCH mapped to HS-DSCH, 4 DL RLC SDUs concatenated into a MAC-hs PDU using the selected TFRC and HID. If the radio bearer combination under test includes downlink DTCHs mapped to DCH then the SS transmits, for all DTCHs mapped to DCH, one or more RLC SDUs having the size equal to the "Test data size" as specified for the sub-test of the actual radio bearer test case.
h) The SS checks that the content of the UE returned RLC SDUs have the correct content and are received having the correct transport format. See TS 34.109 [10] clause 5.3.2.6.2 for details regarding the UE loopback of RLC SDUs.
i) The SS sets HID = (HID + 1) modulo Max_HID, where Max_HID equals the number of HARQ processes to be verified by the actual sub-test
j) The SS repeats steps f) to i) for the remaining TFRC test point (NPDUs , M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.3 (MAC-d PDU size=336) or 14.1.3.4 (MAC-d PDU size=656) for the UE category and MAC-d PDU size under test.
k) The SS opens the UE test loop.
l) The SS release the radio bearer. See note 5.
m) Steps a) to l) are repeated for all sub-tests. See note 7.
n) The SS may optionally deactivate the radio bearer test mode.
NOTE 1: The SS configures the physical channel parameters according to the actual UE category under test. The number of soft channel bits per HARQ process is split equally among the number of HARQ processes configured for the actual sub-test – i.e. “Total number of soft channel bits” for the UE category according to table 14.1.3.1.1 divided by the number of HARQ processes under test. The number of reordering queues is 1 for single HS-DSCH radio bearer configurations. The MAC-hs window size, RLC Transmission window size and RLC Receiving window size shall be configured as specified for the actual sub-test.
NOTE 2: Void
NOTE 3: The MAC-hs window size and RLC Receiver and transmitter window sizes need to be chosen such that the UE capability for “Minimum total RLC AM and MAC-hs buffer size” is not exceeded for the UE category under test.
NOTE 4: The test data for DTCHs mapped on HS-DSCH is divided into 4 RLC SDUs to keep the maximum SDU size below or equal to 1500 octets (1500 octets is the limit of QoS parameter “Max SDU size” in SM).
NOTE 5: The Secondary scrambling code in the RADIO BEARER RELEASE message is set to the same value used in the RADIO BEARER SETUP MESSAGE.
NOTE 6: The TFC subset associated with the signalled “TFC subset identity” in the TRANSPORT FORMAT COMBINATION CONTROL message is defined by the actual AMR reference radio bearer under test.
NOTE 7: CS radio bearer is setup once during the first sub-test.
Expected sequence (repeated for each sub-test, see note 3)
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
1 |
<– |
SYSTEM INFORMATION (BCCH) |
Broadcast |
|
2 |
<– |
PAGING TYPE 1 (PCCH) |
Paging (CS domain, TMSI) |
|
3 |
–> |
RRC CONNECTION REQUEST (CCCH) |
RRC |
|
4 |
<– |
RRC CONNECTION SETUP (CCCH) |
RRC |
|
5 |
–> |
RRC CONNECTION SETUP COMPLETE (DCCH) |
RRC |
|
6 |
–> |
PAGING RESPONSE (DCCH) |
RR |
|
6a |
<– |
AUTHENTICATION REQUEST |
||
6b |
–> |
AUTHENTICATION RESPONSE |
||
7 |
<– |
SECURITY MODE COMMAND |
||
8 |
–> |
SECURITY MODE COMPLETE |
||
9 |
<– |
PAGING TYPE 2 (DCCH) |
TMSI (GSM-MAP)/ P-TMSI |
|
9a |
–> |
SERVICE REQUEST (DCCH) |
GMM |
|
9b |
<– |
SECURITY MODE COMMAND |
RRC See note 2 |
|
9c |
–> |
SECURITY MODE COMPLETE |
RRC |
|
10 |
<– |
ACTIVATE RB TEST MODE (DCCH) |
TC |
|
10a |
–> |
ACTIVATE RB TEST MODE COMPLETE (DCCH) |
TC |
|
11 |
<– |
RADIO BEARER SETUP (DCCH) |
RRC CS radio bearer(s) are configured The TFC subsets associated with the signalling of the TFC subset identity in the TRANSPORT FORMAT COMBINATION CONTROL message on SRB#5 are setup as part of the RADIO BEARER SETUP message. |
|
12 |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
12a |
<– |
RADIO BEARER SETUP (DCCH) |
RRC PS radio bearer(s) are configured. For the PS radio bearer the ‘pdcp info’ IE shall be omitted. |
|
12b |
–> |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
12c |
<– |
TRANSPORT FORMAT COMBINATION CONTROL message |
SRB#5, includes the TFS subset identity IE |
|
13 |
Void |
|||
14 |
<– |
CLOSE UE TEST LOOP (DCCH) |
TC UE test mode 1 RLC SDU size is for every active radio bearer set to "UL RLC SDU size", as specified for the sub-test. |
|
15 |
–> |
CLOSE UE TEST LOOP COMPLETE (DCCH) |
TC |
|
16 |
SS |
For each DTCHs mapped on HS-DSCH the SS creates test data for the first TFRC . The test data shall be dived into 4 RLC SDUs of size (NPDUs * MAC-d PDU payload size) / 4 – 8 bits. The SS sets HID = 0. |
||
17 |
<– |
DOWNLINK MAC-hs PDU (HS-DSCH#1) … DOWNLINK MAC-hs PDU (HS-DSCH#N) DL RLC SDU (DL DCH#1) … DL RLC SDU (DL DCH#M) |
For each DTCH mapped on HS-DSCH the SS sends test data divided into 4 RLC SDUs for HARQ processed HID. For each DTCH mapped on DCH the SS sends test data using the downlink transport format combination under test. |
|
18 |
–> |
UPLINK RLC SDUs |
The SS checks, for each DTCH, that the content and transport format of the received UL RLC SDUs are correct. |
|
19 |
SS |
The SS sets HID = (HID + 1) modulo Max_HID. The SS creates test data for the next TFRC and repeat steps 17 to 18 until all TFRCs have been tested. |
||
20 |
<– |
OPEN UE TEST LOOP (DCCH) |
TC |
|
21 |
–> |
OPEN UE TEST LOOP COMPLETE (DCCH) |
TC |
|
22 |
RB RELEASE |
RRC |
||
23 |
<– |
DEACTIVATE RB TEST MODE |
TC Optional step |
|
24 |
–> |
DEACTIVATE RB TEST MODE COMPLETE |
TC Optional step |
NOTE 1: In addition to activate integrity protection Step 6 and Step 7 are inserted in order to stop T3317 timer in the UE, which starts after transmitting SERVICE REQUEST message.
NOTE 2: The second security mode procedure is needed to enable testing of ciphering on the PS radio bearers.
NOTE 3: Steps 1 to 12 will be executed once during first sub-test.