14.6.10 Streaming MBMS PTP / unknown / UL:16 DL: [max bit rate depending on UE category] kbps / PS RAB + Interactive or background / UL:64 DL: [max bit rate depending on UE category] / PS RAB + Interactive or background / UL:64 DL: [max bit rate depending on UE category] / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH / MBMS Selected Service
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
NOTE: The testing of MBMS PTP radio bearer combinations on DPCH and HSPDSCH is focusing on verifying that the UE is capable to establish the radio bearer combination and to verify correct data transfer using all the possible uplink TFS for transport channels mapped on DCH. The verification of MAC-hstransport block size selection and that the UE is capable of transmitting all the possible transport block sizes within the UE capability is tested in the MAC-hs test case 7.1.5.6.
14.6.10.1 Conformance requirement
The UE shall be able to establish the UTRAN requested MBMS PTP radio bearers within the UE’s signalled radio access capabilities.
The UE shall correctly transfer user data from peer to peer RLC entities according to the requested MBMS PTP radio bearer configuration.
Reference(s)
3GPP TS 25.2xx series (Physical Layer)
3GPP TS 25.321 (MAC)
3GPP TS 25.322 (RLC)
3GPP TS 25.331 (RRC)
14.6.10.2 Test purpose
To verify radio bearer establishment and correct data transfer for reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.5.10:
14.6.10.3 Method of test
NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should signal a category between 1 and 12 for this IE even if the UE physical capability category is above 12. This IE corresponds to the HS-DSCH category supported by the UE when MAC-ehs is not configured.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
MAC-hs receiver window size |
16 |
|
RLC Transmission window size |
See sub-test table |
|
RLC Receiving window size |
See table for parameters for different HS-DSCH Categories |
|
HS-DSCH Category |
HS-PDSCH Number of HARQ processes |
RLC Receiving window size (note 1) |
RLC Trans-mission window size (note 1) |
HS-PDSCH TFRC (note 2) |
|||||
|
Max MAC-d PDU size |
Minimum TBS |
Number of MAC-d PDUs |
Modulation scheme |
Number of codes |
TFRI |
||||
|
1 |
2 |
256 |
128 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
2 |
2 |
256 |
128 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
3 |
3 |
256 |
128 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
4 |
3 |
256 |
128 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
5 |
6 |
256 |
256 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
6 |
6 |
256 |
256 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
7 |
6 |
512 |
512 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
8 |
6 |
512 |
512 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
9 |
6 |
1024 |
512 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
10 |
6 |
1024 |
1024 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
11 |
3 |
512 |
128 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
12 |
6 |
512 |
128 |
656 |
677 |
1 |
QPSK |
2 |
7 |
|
NOTE 1: The SS shall configure the RLC transmission and receiver window size depending on the UE category. The values are set to cope with the number of SDUs used in the sub-test and within the UE capabilities for the actual UE category under test. NOTE 2: The HS-PDSCH TFRC should be selected to enable all test data on DTCH on HS-DSCH to be transmitted in one TTI, i.e. such that the MAC-hs transport block size is bigger than the maximum MAC-d PDU size under test + MAC-hs header size (21 bits). See 14.1.3.4 (MAC-d PDU size=656) for recommended TFRC values for different transport block size. |
|||||||||
Uplink TFS:
|
TFI |
RB5 (16 kbps, 20 ms TTI) |
RB6 + RB7 (64 kbps RAB, 20 ms TTI) |
DCCH |
|
|
TFS |
TF0, bits |
0x336 |
0x340 |
0x148 |
|
TF1, bits |
1×336 |
1×340 |
1×148 |
|
|
TF2, bits |
N/A |
2×340 |
N/A |
|
|
TF3, bits |
N/A |
3×340 |
N/A |
|
|
TF4, bits |
N/A |
4×340 |
N/A |
Uplink TFCS:
|
TFCI |
(RB5, RB6 + RB7, DCCH) |
|
UL_TFC0 |
(TF0, TF0, TF0) |
|
UL_TFC1 |
(TF1, TF0, TF0) |
|
UL_TFC2 |
(TF0, TF1, TF0) |
|
UL_TFC3 |
(TF1, TF1, TF0) |
|
UL_TFC4 |
(TF0, TF2, TF0) |
|
UL_TFC5 |
(TF1, TF2, TF0) |
|
UL_TFC6 |
(TF0, TF3, TF0) |
|
UL_TFC7 |
(TF1, TF3, TF0) |
|
UL_TFC8 |
(TF0, TF4, TF0) |
|
UL_TFC9 |
(TF1, TF4, TF0) |
|
UL_TFC10 |
(TF0, TF0, TF1) |
|
UL_TFC11 |
(TF1, TF0, TF1) |
|
UL_TFC12 |
(TF0, TF1, TF1) |
|
UL_TFC13 |
(TF1, TF1, TF1) |
|
UL_TFC14 |
(TF0, TF2, TF1) |
|
UL_TFC15 |
(TF1, TF2, TF1) |
|
UL_TFC16 |
(TF0, TF3, TF1) |
|
UL_TFC17 |
(TF1, TF3, TF1) |
|
UL_TFC18 |
(TF0, TF4, TF1) |
|
UL_TFC19 |
(TF1, TF4, TF1) |
The generic test procedure in 14.1.6, using the MBMS Selected Service branch, is run for each sub-test.
Sub-tests:
|
Sub-test |
Uplink TFCS Under test |
Implicitly tested |
Restricted UL TFCIs (note 1) |
UL RLC SDU size (bits) (note 2) |
Test data for RB6+RB7 |
|
1 |
UL_TFC1 |
UL_TFC0, UL_TFC11 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC10, UL_TFC11 |
RB5: 312 RB6: 312 RB7: 312 |
Test data for RB6+RB7 sent on RB6 |
|
2 |
UL_TFC2 |
UL_TFC0, UL_TFC12 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC10, UL_TFC12 |
RB5: 312 RB6: 312 RB7: 312 |
Test data for RB6+RB7 sent on RB6 |
|
3 |
UL_TFC3 |
UL_TFC0, UL_TFC13 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC3, UL_TFC10, UL_TFC13 |
RB5: 312 RB6: 312 RB7: 312 |
Test data for RB6+RB7 sent on RB6 |
|
4 |
UL_TFC4 |
UL_TFC0,UL_TFC14 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC4, UL_TFC10, UL_TFC14 |
RB5: 312 RB6: 632 RB7: 632 |
Test data for RB6+RB7 sent on RB6 |
|
5 |
UL_TFC5 |
UL_TFC0, UL_TFC15 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC5, UL_TFC10, UL_TFC15 |
RB5: 312 RB6: 632 RB7: 632 |
Test data for RB6+RB7 sent on RB6 |
|
6 |
UL_TFC6 |
UL_TFC0, UL_TFC16 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC6, UL_TFC10, UL_TFC16 |
RB5: 312 RB6: 952 RB7: 952 |
Test data for RB6+RB7 sent on RB6 |
|
7 |
UL_TFC7 |
UL_TFC0, UL_TFC17 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC7, UL_TFC10, UL_TFC17 |
RB5: 312 RB6: 952 RB7: 952 |
Test data for RB6+RB7 sent on RB6 |
|
8 |
UL_TFC8 |
UL_TFC0, UL_TFC18 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC8, UL_TFC10, UL_TFC18 |
RB5: 312 RB6: 1272 RB7: 1272 |
Test data for RB6+RB7 sent on RB6 |
|
9 |
UL_TFC9 |
UL_TFC0, UL_TFC19 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC9, UL_TFC10, UL_TFC19 |
RB5: 312 RB6: 1272 RB7: 1272 |
Test data for RB6+RB7 sent on RB6 |
|
10 |
UL_TFC9 |
UL_TFC0, UL_TFC19 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC9, UL_TFC10, UL_TFC19 |
RB5: 312 RB6: 1272 RB7: 1272 |
Test data for RB6+RB7 sent on RB7 |
|
NOTE 1: UL_TFC0, UL_TFC1, UL_TFC2 and UL_TFC10 are part of minimum set of TFCIs. NOTE 2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
|||||
14.6.10.4 Test requirements
See 14.1.6 for definition of step 14 and step 22.
1. At step 14 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 22 the UE shall return
– for sub-test 1: RLC SDU on RB5 where the first 312 bits has the same content as the RLC SDUs sent by the SS in downlink and no data on RB6 and RB7.
– for sub-test 2: RLC SDU on RB6 where the first 312 bits has the same content as the RLC SDUs sent by the SS in downlink and no data on RB5 and RB7.
– for sub-test 3: RLC SDU on RB5 and RB6 where the first 312 bits has the same content as the RLC SDUs sent by the SS in downlink and no data on RB7.
– for sub-test 4: RLC SDU on RB6 where the first 632 bits has the same content as the RLC SDUs sent by the SS in downlink and no data on RB5 and RB7.
– for sub-test 5: RLC SDU on RB5 and RB6 where the first 312 bits for RB5 and the .first 632 bits for RB6 has the same content as the RLC SDUs sent by the SS in downlink and no data on RB7.
– for sub-test 6: RLC SDU on RB6 where the first 952 bits has the same content as the RLC SDUs sent by the SS in downlink and no data on RB5 and RB7.
– for sub-test 7: RLC SDU on RB5 and RB6 where the first 312 bits for RB5 and the first 952 bits for RB6 has the same content as the RLC SDUs sent by the SS in downlink and no data on RB7.
– for sub-test 8: RLC SDU on RB6 where the first 1272 bits has the same content as the RLC SDUs sent by the SS in downlink and no data on RB5 and RB7.
– for sub-test 9: RLC SDU on RB5 and RB6 where the first 312 bits for RB5 and the first 1272 bits for RB6 has the same content as the RLC SDUs sent by the SS in downlink and no data on RB7.
– for sub-test 10: RLC SDU on RB5 and RB7 where the first 312 bits for RB5 and the first 1272 bits for RB7 has the same content as the RLC SDUs sent by the SS in downlink and no data on RB6.