18.1.3 Combinations on SCCPCH
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
18.1.3.1 Stand-alone signalling RB for PCCH
Implicitly tested.
NOTE The stand-alone signalling radio bearer for PCCH in TS 34.108, clause 6.11.5.4.4.1 is used in RRC test case 8.1.2.2.
18.1.3.2 Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.4.2.
This radio bearer configuration is tested with three different SYSTEM INFORMATION (BCCH) configurations:
1. The contents of System Information Block type 5 and 6 as specified in TS 34.108, clause 6.1.1.
Two SCCPCHs are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the PCH and the second SCCPCH carries the FACH for Interactive/Background 32 kbps PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH.
This configuration is verified in test case 18.1.3.2.1.
2. The contents of System Information Block type 5 as specified in TS 34.108, clause 6.1.3.
Three SCCPCHs are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the PCH and both the second and third SCCPCHs carry the FACH for Interactive/Background 32 kbps PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH.
This configuration is verified in test case 18.1.3.2.2.
3. The contents of System Information Block type 5 and 6 as specified in TS 34.108, clause 6.1.2.
Three SCCPCHs are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the PCH. The second SCCPCH carries the FACH for CTCH (Cell Broadcast Service) and the FACH for SRBs on CCCH/ BCCH for idle mode UEs. The third SCCPCH carries the FACH for Interactive/Background 32 kbps PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH for connected mode UEs.
This configuration is verified in test case 18.1.3.2.3.
18.1.3.2.1 One SCCPCH: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.1.3.2.1.1 Conformance requirement
See 18.1.2.4.1
18.1.3.2.1.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.11.5.4.4.2 and 6.11.5.4.5.1 for the case when two SCCPCHs are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the PCH and the second SCCPCH carries the FACH for Interactive/Background 32 kbps PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH.
To be able to test the downlink radio bearer using the UE loopback function, the reference radio bearer configuration according to TS 34.108, clause 6.11.5.4.5.1 (Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.1.3.2.1.3 Method of Test
The contents of System Information Block type 5 and 6 shall be as specified in TS 34.108, clause 6.1.1.
Uplink TFS:
TFI |
RB7+SRB |
|
TFS |
TF0, bits |
1×171 |
TF1, bits |
1×363 |
Uplink TFCS:
TFCI |
RB7+SRB |
UL_TFC0 |
TF0 |
UL_TFC1 |
TF1 |
Downlink TFS:
SRBs |
RB7 (32 kbps) |
||
TFS |
TF0, bits |
0x171 |
0x363 |
TF1, bits |
1×171 |
1×363 |
|
TF2, bits |
2×171 |
N/A |
|
Downlink TFCS:
TFCI |
(SRB, RB7) |
DL_TFC0 |
(TF0, TF0) |
DL_TFC1 |
(TF1, TF0) |
DL_TFC2 |
(TF2, TF0) |
DL_TFC3 |
(TF0, TF1) |
DL_TFC4 |
(TF1, TF1) |
Sub-tests:
Sub-test |
Downlink TFCS Under test |
Uplink TFCS Under test |
Implicitly tested |
Restricted UL TFCIs |
UL RLC SDU size (note) |
Test data size (note) |
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
UL_TFC1, UL_TFC0 |
RB7: 312 bits |
RB7: 312 bits |
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
See 18.1.1 for test procedure.
18.1.3.2.1.4 Test Requirements
See 18.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be RB7/TF1 (1×363).
2. At step 15 the UE shall return an RLC SDU on RB7 having the same content as sent by SS
18.1.3.2.2 Two SCCPCHs: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.1.3.2.2.1 Conformance requirement
See 18.1.2.4
18.1.3.2.2.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.11.5.4.4.2 and 6.11.5.4.5.1 for the case when three SCCPCHs are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the PCH and both the second and third SCCPCHs carry the FACH for Interactive/Background 32 kbps PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH.
To be able to test the downlink radio bearer using the UE loopback function, the reference radio bearer configuration according to TS 34.108, clause 6.11.5.4.5.1 (Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.1.3.2.2.3 Method of Test
The contents of System Information Block type 5 shall be as specified in TS 34.108, clause 6.1.3.
Uplink TFS:
TFI |
RB7+SRB |
|
TFS |
TF0, bits |
1×171 |
TF1, bits |
1×363 |
Uplink TFCS:
TFCI |
RB7+SRB |
UL_TFC0 |
TF0 |
UL_TFC1 |
TF1 |
Downlink TFS:
SRBs |
RB7 (32 kbps) |
||
TFS |
TF0, bits |
0x171 |
0x363 |
TF1, bits |
1×171 |
1×363 |
|
TF2, bits |
2×171 |
N/A |
|
Downlink TFCS:
TFCI |
(SRB, RB7) |
DL_TFC0 |
(TF0, TF0) |
DL_TFC1 |
(TF1, TF0) |
DL_TFC2 |
(TF2, TF0) |
DL_TFC3 |
(TF0, TF1) |
DL_TFC4 |
(TF1, TF1) |
Sub-tests:
Sub-test |
Downlink TFCS under test |
Uplink TFCS Under test |
Implicitly tested |
Restricted UL TFCIs |
UL RLC SDU size (note) |
Test data size (note) |
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
UL_TFC1, UL_TFC0 |
RB7: 312 bits |
RB7: 312 bits |
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
See 18.1.1 for test procedure.
18.1.3.2.2.4 Test Requirements
See 18.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be RB7/TF1 (1×363).
2. At step 15 the UE shall return an RLC SDU on RB7 having the same content as sent by SS
18.1.3.2.3 One SCCPCH/connected mode: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.1.3.2.3.1 Conformance requirement
See 18.1.2.4.1
18.1.3.2.3.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.11.5.4.4.2 and 6.11.5.4.5.1 for the case when three SCCPCHs are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the PCH. The second SCCPCH carries the FACH for CTCH (Cell Broadcast Service) and the FACH for SRBs on CCCH/ BCCH for idle mode UEs. The third SCCPCH carries the FACH for Interactive/Background 32 kbps PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH for connected mode UEs.
To be able to test the downlink radio bearer using the UE loopback function, the reference radio bearer configuration according to TS 34.108, clause 6.11.5.4.5.1 (Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.1.3.2.3.3 Method of Test
The contents of System Information Block type 5 and 6 shall be as specified in TS 34.108, clause 6.1.2.
Uplink TFS:
TFI |
RB7+SRB |
|
TFS |
TF0, bits |
1×171 |
TF1, bits |
1×363 |
Uplink TFCS:
TFCI |
RB7+SRB |
UL_TFC0 |
TF0 |
UL_TFC1 |
TF1 |
Downlink TFS:
SRBs |
RB7 (32 kbps) |
||
TFS |
TF0, bits |
0x171 |
0x363 |
TF1, bits |
1×171 |
1×363 |
|
TF2, bits |
2×171 |
N/A |
|
Downlink TFCS:
TFCI |
(SRB, RB7) |
DL_TFC0 |
(TF0, TF0) |
DL_TFC1 |
(TF1, TF0) |
DL_TFC2 |
(TF2, TF0) |
DL_TFC3 |
(TF0, TF1) |
DL_TFC4 |
(TF1, TF1) |
Sub-tests:
Sub-test |
Downlink TFCS Under test |
Uplink TFCS Under test |
Implicitly tested |
Restricted UL TFCIs |
UL RLC SDU size (note) |
Test data size (note) |
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
UL_TFC1, UL_TFC0 |
RB7: 312 bits |
RB7: 312 bits |
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
See 18.1.1 for test procedure.
18.1.3.2.3.4 Test Requirements
See 18.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be RB7/TF1 (1×363).
2. At step 15 the UE shall return an RLC SDU on RB7 having the same content as sent by SS
18.1.3.3 Interactive/Background UL:12.8 DL:32 kbps RAB + SRBs for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH
18.1.3.3.1 Conformance requirement
See 18.1.2.4
18.1.3.3.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.11.5.4.4.2 and 6.11.5.4.5.2 for the case when one SCCPCH is used in this SYSTEM INFORMATION (BCCH) configuration. The SCCPCH carries the PCH, the FACH for Interactive/Background 32 kbps PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH.
To be able to test the downlink radio bearer using the UE loopback function, the reference radio bearer configuration according to TS 34.108, clause 6.11.5.4.5.2 (Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.1.3.3.3 Method of Test
The contents of System Information Block type 5 and 6 shall be as specified in TS 34.108, clause 6.1.
Uplink TFS:
TFI |
RB8 |
|
TFS |
TF0, bits |
0x170 |
TF1, bits |
1×170 |
Uplink TFCS:
TFCI |
RB8 |
UL_TFC0 |
TF0 |
UL_TFC1 |
TF1 |
Downlink TFS:
PCCH |
SRBs |
RB8 (32 kbps) |
||
TFS |
TF0, bits |
0x240 |
0x171 |
0x363 |
TF1, bits |
1×240 |
1×171 |
1×363 |
|
TF2, bits |
N/A |
2×171 |
N/A |
|
Downlink TFCS:
TFCI |
(PCCH, SRB, RB8) |
DL_TFC0 |
(TF0, TF0, TF0) |
DL_TFC1 |
(TF1, TF0, TF0) |
DL_TFC2 |
(TF0, TF1, TF0) |
DL_TFC3 |
(TF1, TF1, TF0) |
DL_TFC4 |
(TF0, TF2, TF0) |
DL_TFC5 |
(TF1, TF2, TF0) |
DL_TFC6 |
(TF0, TF0, TF1) |
DL_TFC7 |
(TF0, TF1, TF1) |
Sub-tests:
Sub-test |
Downlink TFCS under test |
Uplink TFCS Under test |
Implicitly tested |
Restricted UL TFCIs |
UL RLC SDU size (note) |
Test data size (note) |
1 |
DL_TFC6 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
UL_TFC1, UL_TFC0 |
RB8: 128 bits |
RB8: 312 bits |
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
See 18.1.1 for test procedure.
18.1.3.3.4 Test requirements
See 18.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be RB8/TF1 (1×170).
2. At step 15 the UE shall return an RLC SDU on RB8 having the same content as sent by SS
18.1.3.4 64.8kbps RB for MTCH with 40 ms TTI
18.1.3.4.1 Conformance Requirement
The UE shall correctly receive user data on the MTCH from the peer to peer RLC entity according to the configured MTCH.
Reference(s)
3GPP TS 25.2xx series (Physical Layer)
3GPP TS 25.321 (MAC)
3GPP TS 25.322 (RLC)
3GPP TS 25.331 (RRC)
18.1.3.4.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.4.5.
18.1.3.4.3 Method of Test
See 14.1.5 for test procedure.
Downlink TFS:
TFI |
RB for MTCH (64.8 kbps) |
|
TFS |
TF0, bits |
0x665 |
TF1, bits |
1×665 |
|
TF2, bits |
2×665 |
|
TF3, bits |
3×665 |
|
TF4, bits |
4×665 |
Downlink TFCS:
TFCI |
RB for MTCH (64.8 kbps) |
DL_TFC0 |
(TF0) |
DL_TFC1 |
(TF1) |
DL_TFC2 |
(TF2) |
DL_TFC3 |
(TF3) |
DL_TFC4 |
(TF4) |
Sub-tests:
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (note 1) |
1 |
DL_TFC1 |
DL_TFC0 |
640 |
2 |
DL_TFC2 |
DL_TFC0 |
1288 |
3 |
DL_TFC3 |
DL_TFC0 |
1936 |
4 |
DL_TFC4 |
DL_TFC0 |
2584 |
NOTE 1: Test data size (=DL SDU size) has been set to the N*payload size of the DL TF under test minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
18.1.3.4.4 Test Requirements
See 14.1.5 for definition of steps 8 and 12.
1. For the first sub-test: At step 8 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than zero.
2. For the second and following sub-tests: At step 12 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than the reported value at previous sub-test.
NOTE For UE in UE test loop mode 3 then the RLC SDU counter value is only reset upon reception of CLOSE UE TEST LOOP message configuring UE test loop mode 3. As the generic test procedure in section 14.1.5 runs through all sub-tests without deactivating the UE test mode then the SS needs to check the reported counter value against the value reported at the previous sub-test.
18.1.3.5 129.6 kbps RB for MTCH with 40 ms TTI
18.1.3.5.1 Conformance Requirement
See 18.1.3.4.1.
18.1.3.5.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.4.6.
18.1.3.5.3 Method of Test
See 14.1.5 for test procedure.
Downlink TFS:
TFI |
RB for MTCH (129.6 kbps kbps) |
|
TFS |
TF0, bits |
0x665 |
TF1, bits |
1×665 |
|
TF2, bits |
2×665 |
|
TF3, bits |
3×665 |
|
TF4, bits |
4×665 |
|
TF5, bits |
5×665 |
|
TF6, bits |
6×665 |
|
TF7, bits |
7×665 |
|
TF8, bits |
8×665 |
Downlink TFCS:
TFCI |
RB for MTCH (129.6 kbps) |
DL_TFC0 |
(TF0) |
DL_TFC1 |
(TF1) |
DL_TFC2 |
(TF2) |
DL_TFC3 |
(TF3) |
DL_TFC4 |
(TF4) |
DL_TFC5 |
(TF5) |
DL_TFC6 |
(TF6) |
DL_TFC7 |
(TF7) |
DL_TFC8 |
(TF8) |
Sub-tests:
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (note 1) |
1 |
DL_TFC1 |
DL_TFC0 |
640 |
2 |
DL_TFC2 |
DL_TFC0 |
1288 |
3 |
DL_TFC3 |
DL_TFC0 |
1936 |
4 |
DL_TFC4 |
DL_TFC0 |
2584 |
5 |
DL_TFC5 |
DL_TFC0 |
3232 |
6 |
DL_TFC6 |
DL_TFC0 |
3880 |
7 |
DL_TFC7 |
DL_TFC0 |
4528 |
8 |
DL_TFC8 |
DL_TFC0 |
5176 |
NOTE 1: Test data size (=DL SDU size) has been set to the N*payload size of the DL TF under test minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
18.1.3.5.4 Test Requirements
See 14.1.5 for definition of steps 8 and 12.
1. For the first sub-test: At step 8 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than zero.
2. For the second and following sub-tests: At step 12 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than the reported value at previous sub-test.
NOTE For UE in UE test loop mode 3 then the RLC SDU counter value is only reset upon reception of CLOSE UE TEST LOOP message configuring UE test loop mode 3. As the generic test procedure in section 14.1.5 runs through all sub-tests without deactivating the UE test mode then the SS needs to check the reported counter value against the value reported at the previous sub-test.
18.1.3.6 259.2 kbps RB for MTCH with 40 ms TTI
18.1.3.6.1 Conformance Requirement
See 18.1.3.4.1.
18.1.3.6.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.4.7.
18.1.3.6.3 Method of Test
See 14.1.5 for test procedure.
Downlink TFS:
TFI |
RB for MTCH (259.2 kbps kbps) |
|
TFS |
TF0, bits |
0x665 |
TF1, bits |
1×665 |
|
TF2, bits |
2×665 |
|
TF3, bits |
3×665 |
|
TF4, bits |
4×665 |
|
TF5, bits |
5×665 |
|
TF6, bits |
6×665 |
|
TF7, bits |
7×665 |
|
TF8, bits |
8×665 |
|
TF9, bits |
9×665 |
|
TF10, bits |
10×665 |
|
TF11, bits |
11×665 |
|
TF12, bits |
12×665 |
|
TF13, bits |
13×665 |
|
TF14, bits |
14×665 |
|
TF15, bits |
15×665 |
|
TF16, bits |
16×665 |
Downlink TFCS:
TFCI |
RB for MTCH (259.2 kbps) |
DL_TFC0 |
(TF0) |
DL_TFC1 |
(TF1) |
DL_TFC2 |
(TF2) |
DL_TFC3 |
(TF3) |
DL_TFC4 |
(TF4) |
DL_TFC5 |
(TF5) |
DL_TFC6 |
(TF6) |
DL_TFC7 |
(TF7) |
DL_TFC8 |
(TF8) |
DL_TFC9 |
(TF9) |
DL_TFC10 |
(TF10) |
DL_TFC11 |
(TF11) |
DL_TFC12 |
(TF12) |
DL_TFC13 |
(TF13) |
DL_TFC14 |
(TF14) |
DL_TFC15 |
(TF15) |
DL_TFC16 |
(TF16) |
Sub-tests:
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (note 1) |
1 |
DL_TFC1 |
DL_TFC0 |
640 |
2 |
DL_TFC2 |
DL_TFC0 |
1288 |
3 |
DL_TFC3 |
DL_TFC0 |
1936 |
4 |
DL_TFC4 |
DL_TFC0 |
2584 |
5 |
DL_TFC5 |
DL_TFC0 |
3232 |
6 |
DL_TFC6 |
DL_TFC0 |
3880 |
7 |
DL_TFC7 |
DL_TFC0 |
4528 |
8 |
DL_TFC8 |
DL_TFC0 |
5176 |
9 |
DL_TFC9 |
DL_TFC0 |
5824 |
10 |
DL_TFC10 |
DL_TFC0 |
6472 |
11 |
DL_TFC11 |
DL_TFC0 |
7120 |
12 |
DL_TFC12 |
DL_TFC0 |
7768 |
13 |
DL_TFC13 |
DL_TFC0 |
8416 |
14 |
DL_TFC14 |
DL_TFC0 |
9064 |
15 |
DL_TFC15 |
DL_TFC0 |
9712 |
16 |
DL_TFC16 |
DL_TFC0 |
10360 |
NOTE 1: Test data size (=DL SDU size) has been set to the N*payload size of the DL TF under test minus 8 bits (size of 7 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
18.1.3.6.4 Test Requirements
See 14.1.5 for definition of steps 8 and 12.
1. For the first sub-test: At step 8 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than zero.
2. For the second and following sub-tests: At step 12 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than the reported value at previous sub-test.
NOTE For UE in UE test loop mode 3 then the RLC SDU counter value is only reset upon reception of CLOSE UE TEST LOOP message configuring UE test loop mode 3. As the generic test procedure in section 14.1.5 runs through all sub-tests without deactivating the UE test mode then the SS needs to check the reported counter value against the value reported at the previous sub-test.
18.1.3.7 128kbps RB for MBSFN MTCH with 40 ms TTI
18.1.3.7.1 Conformance Requirement
The UE shall correctly receive user data on the MTCH from the peer to peer RLC entity according to the configured MTCH.
Reference(s)
3GPP TS 25.2xx series (Physical Layer)
3GPP TS 25.321 (MAC)
3GPP TS 25.322 (RLC)
3GPP TS 25.331 (RRC)
18.1.3.7.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.4.9.
18.1.3.7.3 Method of Test
See subclause 18.2.1.6 for test procedure.
Downlink TFS:
TFI |
RB for MTCH (128 kbps) |
|
TFS |
TF0, bits |
0x2561 |
TF1, bits |
1×2561 |
Downlink TFCS:
TFCI |
RB for MTCH (128 kbps) |
DL_TFC0 |
(TF0) |
DL_TFC1 |
(TF1) |
Sub-tests:
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (note 1) |
1 |
DL_TFC1 |
DL_TFC0 |
2528 |
NOTE 1: Test data size (=DL SDU size) has been set to the N*payload size of the DL TF under test minus 16 bits (size of 15 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
18.1.3.7.4 Test Requirements
See subclause 18.1.1.5 for definition of steps 9 and 13.
1. For the first sub-test: At step 9 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than zero.
2. For the second and following sub-tests: At step 13 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than the reported value at previous sub-test.
NOTE: For UE in UE test loop mode 3 then the RLC SDU counter value is only reset upon reception of CLOSE UE TEST LOOP message configuring UE test loop mode 3. As the generic test procedure in section 18.1.1.5 runs through all sub-tests without deactivating the UE test mode then the SS needs to check the reported counter value against the value reported at the previous sub-test.
18.1.3.8 192kbps RB for MBSFN MTCH with 40 ms TTI
18.1.3.8.1 Conformance Requirement
See 18.1.3.7.1.
18.1.3.8.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.4.10.
18.1.3.8.3 Method of Test
See subclause 18.1.1.5 for test procedure.
Downlink TFS:
TFI |
RB for MTCH (192 kbps kbps) |
|
TFS |
TF0, bits |
0x2561 |
TF1, bits |
3×2561 |
Downlink TFCS:
TFCI |
RB for MTCH (192 kbps) |
DL_TFC0 |
(TF0) |
DL_TFC1 |
(TF1) |
Sub-tests:
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (note 1) |
1 |
DL_TFC1 |
DL_TFC0 |
7616 |
NOTE 1: Test data size (=DL SDU size) has been set to the N*payload size of the DL TF under test minus 16 bits (size of 15 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
18.1.3.8.4 Test Requirements
See subclause 18.1.1.5 for definition of steps 9 and 13.
1. For the first sub-test: At step 9 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than zero.
2. For the second and following sub-tests: At step 13 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than the reported value at previous sub-test.
NOTE For UE in UE test loop mode 3 then the RLC SDU counter value is only reset upon reception of CLOSE UE TEST LOOP message configuring UE test loop mode 3. As the generic test procedure in section 18.1.1.5 runs through all sub-tests without deactivating the UE test mode then the SS needs to check the reported counter value against the value reported at the previous sub-test.
18.1.3.9 384kbps RB for MBSFN MTCH with 40 ms TTI
18.1.3.9.1 Conformance Requirement
See 18.1.3.7.1.
18.1.3.9.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.5.4.4.11.
18.1.3.9.3 Method of Test
See subclause 18.1.1.5 for test procedure.
Downlink TFS:
TFI |
RB for MTCH (384 kbps kbps) |
|
TFS |
TF0, bits |
0x2561 |
TF1, bits |
6×2561 |
Downlink TFCS:
TFCI |
RB for MTCH (384 kbps) |
DL_TFC0 |
(TF0) |
DL_TFC1 |
(TF1) |
Sub-tests:
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (note 1) |
1 |
DL_TFC1 |
DL_TFC0 |
15250 |
NOTE 1: Test data size (=DL SDU size) has been set to the N*payload size of the DL TF under test minus 16 bits (size of 15 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
18.1.3.9.4 Test Requirements
See subclause 18.2.1.6 for definition of steps 9 and 13.
1. For the first sub-test: At step 9 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than zero.
2. For the second and following sub-tests: At step 13 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater than the reported value at previous sub-test.
NOTE For UE in UE test loop mode 3 then the RLC SDU counter value is only reset upon reception of CLOSE UE TEST LOOP message configuring UE test loop mode 3. As the generic test procedure in section 18.1.1.5 runs through all sub-tests without deactivating the UE test mode then the SS needs to check the reported counter value against the value reported at the previous sub-test.