14.2.50 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
14.2.50.1 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH / 20 ms TTI
14.2.50.1.1 Conformance requirement
See 14.2.4.1.
14.2.50.1.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.1.50 for the 20 ms TTI case.
14.2.50.1.3 Method of test
Initial Conditions
The following RLC Info parameter values shall be set by the SS for the Conversational / unknown / UL:64 DL:64 kbps / CS RAB (RB5 and RB6):
RB5 (64 kbps) |
RB6 (64 kbps) |
|
Uplink RLC |
||
TM RLC |
||
Segmentation indication |
FALSE |
FALSE |
Transmission RLC discard |
||
CHOICE SDU Discard Mode |
||
Timer based no explicit |
||
Timer_discard |
100ms |
100ms |
Downlink RLC |
||
TM RLC |
||
Segmentation indication |
FALSE |
FALSE |
NOTE: Timer based discard without explicit signalling is used in uplink to secure that the UE will be able to return data for the case when the UE test loop function will not deliver all the SDUs in one and the same TTI . |
See 14.1.2 for test procedure.
Uplink TFS:
TFI |
RB5 (64 kbps) |
RB6 (64 kbps) |
DCCH |
|
TFS |
TF0, bits |
0x640 |
0x640 |
0x148 |
TF1, bits |
2×640 |
2×640 |
1×148 |
|
TF2, bits |
N/A |
N/A |
N/A |
Uplink TFCS:
TFCI |
(RB5, RB6, DCCH) |
UL_TFC0 |
(TF0, TF0, TF0) |
UL_TFC1 |
(TF1, TF0, TF0) |
UL_TFC2 |
(TF0, TF1, TF0) |
UL_TFC3 |
(TF1, TF1, TF0) |
UL_TFC4 |
(TF0, TF0, TF1) |
UL_TFC5 |
(TF1, TF0, TF1) |
UL_TFC6 |
(TF0, TF1, TF1) |
UL_TFC7 |
(TF1, TF1, TF1) |
Downlink TFS:
TFI |
RB5 (64 kbps) |
RB6 (64 kbps) |
DCCH |
|
TFS |
TF0, bits |
0x640 |
0x640 |
0x148 |
TF1, bits |
2×640 |
2×640 |
1×148 |
|
TF2, bits |
N/A |
N/A |
N/A |
Downlink TFCS:
TFCI |
(RB5, RB6, DCCH) |
DL_TFC0 |
(TF0, TF0, TF0) |
DL_TFC1 |
(TF1, TF0, TF0) |
DL_TFC2 |
(TF0, TF1, TF0) |
DL_TFC3 |
(TF1, TF1, TF0) |
DL_TFC4 |
(TF0, TF0, TF1) |
DL_TFC5 |
(TF1, TF0, TF1) |
DL_TFC6 |
(TF0, TF1, TF1) |
DL_TFC7 |
(TF1, TF1, TF1) |
Sub-tests:
Sub-test |
Downlink TFCS Under Test |
Uplink TFCS Under test |
Implicitly tested |
Restricted UL TFCIs (note1) |
UL RLC SDU size (bits) (note2) |
Test data size (bits) (note2) |
---|---|---|---|---|---|---|
1 |
DL_TFC1,DL_TFC5 |
UL_TFC1,DL_TFC5 |
DL_TFC0, DL_TFC4, UL_TFC0, UL_TFC4 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC4, UL_TFC5 |
RB5: 640 RB6: 640 |
RB5: 2×640 RB6: No data |
2 |
DL_TFC2,DL_TFC6 |
UL_TFC2,DL_TFC6 |
DL_TFC0, DL_TFC4, UL_TFC0, UL_TFC4 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC4, UL_TFC6 |
RB5: 640 RB6: 640 |
RB5: No data RB6: 2×640 |
3 |
DL_TFC3,DL_TFC7 |
UL_TFC3,DL_TFC7 |
DL_TFC0, DL_TFC4, UL_TFC0, UL_TFC4 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC3, UL_TFC4, UL_TFC5, UL_TFC6, UL_TFC7 |
RB5: 640 RB6: 640 |
RB5: 2×640 RB6: 2×640 |
NOTE1: UL_TFC0, UL_TFC1, UL_TFC2, UL_and UL_TFC4 are part of minimum set of TFCIs NOTE2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
14.2.50.1.4 Test requirements
See 14.1.2 for definition of step 10 and step 15.
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15a and 15b the UE transmitted transport format shall be within the set of restricted TFCIs as specified for the actual subtest.
3. At step 15 the UE shall return
– for sub-test 1: RLC SDUs on RB5 having the same content as sent by SS; and no data shall be received on RB6.
– for sub-test 2: RLC SDUs on RB6 having the same content as sent by SS; and no data shall be received on RB5.
– for sub-test 3: RLC SDUs on RB5 and RB6 having the same content as sent by SS.
4. At step 15b the UE shall send at least one MEASUREMENT REPORT message.
14.2.50.2 Conversational / unknown / UL:64 DL:64 kbps / CS RAB + Conversational / unknown / UL:64 DL:64 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH / 40 ms TTI
14.2.50.2.1 Conformance requirement
See 14.2.4.1.
14.2.50.2.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.1.50 for the 40 ms TTI case.
14.2.50.2.3 Method of test
Initial Conditions
The following RLC Info parameter values shall be set by the SS for the Conversational / unknown / UL:64 DL:64 kbps / CS RAB (RB5 and RB6):
RB5 (64 kbps) |
RB6 (64 kbps) |
|
Uplink RLC |
||
TM RLC |
||
Segmentation indication |
FALSE |
FALSE |
Transmission RLC discard |
||
CHOICE SDU Discard Mode |
||
Timer based no explicit |
||
Timer_discard |
100ms |
100ms |
Downlink RLC |
||
TM RLC |
||
Segmentation indication |
FALSE |
FALSE |
NOTE: Timer based discard without explicit signalling is used in uplink to secure that the UE will be able to return data for the case when the UE test loop function will not deliver all the SDUs in one and the same TTI . |
See 14.1.2 for test procedure.
Uplink TFS:
TFI |
RB5 (64 kbps) |
RB6 (64 kbps) |
DCCH |
|
TFS |
TF0, bits |
0x640 |
0x640 |
0x148 |
TF1, bits |
4×640 |
4×640 |
1×148 |
|
TF2, bits |
N/A |
N/A |
N/A |
Uplink TFCS:
TFCI |
(RB5, RB6, DCCH) |
UL_TFC0 |
(TF0, TF0, TF0) |
UL_TFC1 |
(TF1, TF0, TF0) |
UL_TFC2 |
(TF0, TF1, TF0) |
UL_TFC3 |
(TF1, TF1, TF0) |
UL_TFC4 |
(TF0, TF0, TF1) |
UL_TFC5 |
(TF1, TF0, TF1) |
UL_TFC6 |
(TF0, TF1, TF1) |
UL_TFC7 |
(TF1, TF1, TF1) |
Downlink TFS:
TFI |
RB5 (64 kbps) |
RB6 (64 kbps) |
DCCH |
|
TFS |
TF0, bits |
0x640 |
0x640 |
0x148 |
TF1, bits |
4×640 |
4×640 |
1×148 |
|
TF2, bits |
N/A |
N/A |
N/A |
Downlink TFCS:
TFCI |
(RB5, RB6, DCCH) |
DL_TFC0 |
(TF0, TF0, TF0) |
DL_TFC1 |
(TF1, TF0, TF0) |
DL_TFC2 |
(TF0, TF1, TF0) |
DL_TFC3 |
(TF1, TF1, TF0) |
DL_TFC4 |
(TF0, TF0, TF1) |
DL_TFC5 |
(TF1, TF0, TF1) |
DL_TFC6 |
(TF0, TF1, TF1) |
DL_TFC7 |
(TF1, TF1, TF1) |
Sub-tests:
Sub-test |
Downlink TFCS Under Test |
Uplink TFCS Under test |
Implicitly tested |
Restricted UL TFCIs (note1) |
UL RLC SDU size (bits) (note2) |
Test data size (bits) (note2) |
---|---|---|---|---|---|---|
1 |
DL_TFC1, DL_TFC5 |
UL_TFC1, DL_TFC5 |
DL_TFC0, DL_TFC4, UL_TFC0, UL_TFC4 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC4, UL_TFC5 |
RB5: 640 RB6: 640 |
RB5: 4×640 RB6: No data |
2 |
DL_TFC2, DL_TFC6 |
UL_TFC2, DL_TFC6 |
DL_TFC0, DL_TFC4, UL_TFC0, UL_TFC4 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC4, UL_TFC6 |
RB5: 640 RB6: 640 |
RB5: No data RB6: 4×640 |
3 |
DL_TFC3, DL_TFC7 |
UL_TFC3, DL_TFC7 |
DL_TFC0, DL_TFC4, UL_TFC0, UL_TFC4 |
UL_TFC0, UL_TFC1, UL_TFC2, UL_TFC3, UL_TFC4, UL_TFC5, UL_TFC6, UL_TFC7 |
RB5: 640 RB6: 640 |
RB5: 4×640 RB6: 4×640 |
NOTE1: UL_TFC0, UL_TFC1, UL_TFC2, UL_and UL_TFC4 are part of minimum set of TFCIs NOTE2: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
14.2.50.2.4 Test requirements
See 14.1.2 for definition of step 10 and step 15.
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15a and 15b the UE transmitted transport format shall be within the set of restricted TFCIs as specified for the actual subtest.
3. At step 15 the UE shall return
– for sub-test 1: RLC SDUs on RB5 having the same content as sent by SS; and no data shall be received on RB6.
– for sub-test 2: RLC SDUs on RB6 having the same content as sent by SS; and no data shall be received on RB5.
– for sub-test 3: RLC SDUs on RB5 and RB6 having the same content as sent by SS.
4. At step 15b the UE shall send at least one MEASUREMENT REPORT message.