18.3.5 Combinations on SCCPCH
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
18.3.5.1 Stand-alone signalling RB for PCCH
18.3.5.1.1 Stand-alone signalling RB for PCCH at 12 kbps
18.3.5.1.1.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.1.1.2 Test Purpose
To verify establishment and data transfer of Paging 1 message which comprises IE "BCCH Modification Information", with the "Value Tag" different from the "MIB Value Tag" of the current Master Information Block. This test is specified in TS 34.108, clause 6.11.6.4.4.1. The SCCPCH carries the PCH at 12 kbps.
18.3.5.1.1.3 Method of Test
The contents of the System Information Block type 5 are specified in clause 8.1.2.2.
Downlink TFS for PCCH:
|
SRBs |
||
|
TFS |
TF0, bits |
0x240 |
|
TF1, bits |
1×240 |
Downlink TFCS for PCCH:
|
TFCI |
(SRB) |
|
DL_TFC0 |
(TF0) |
|
DL_TFC1 |
(TF1) |
Sub-test:
See 18.3.1.1 for test procedure.
18.3.5.1.1.4 Test Requirements
See 18.3.1.1 for definition of step 6
1. At step 6 the UE transmitted PAGING RESPONSE (DCCH) received at the SS shall complete the test and end gracefully.
18.3.5.1.2 Stand-alone signalling RB for PCCH at 8 kbps
18.3.5.1.2.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.1.2.2 Test Purpose
To verify establishment and data transfer of Paging 1 message which comprises IE "BCCH Modification Information", with the "Value Tag" different from the "MIB Value Tag" of the current Master Information Block. This test specified in TS 34.108, clause 6.11.6.4.4.1. The SCCPCH carries the PCH at 8 kbps.
18.3.5.1.2.3 Method of Test
The contents of the System Information Block type 5 is specified in clause 8.1.2.2.
Downlink TFS for PCCH:
|
SRBs |
||
|
TFS |
TF0, bits |
0x80 |
|
TF1, bits |
1×80 |
|
|
TF2, bits |
2×80 |
Downlink TFCS:
|
TFCI |
(SRB) |
|
DL_TFC0 |
(TF0) |
|
DL_TFC1 |
(TF1) |
|
DL_TFC2 |
(TF2) |
Sub-tests:
See 18.3.1.1 for test procedure.
18.3.5.1.2.4 Test Requirements
See 18.3.1.1 for definition of step 6
1. At step 6 the UE transmitted PAGING RESPONSE (DCCH) received at the SS shall complete the test and end gracefully.
18.3.5.2 Interactive/Background 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.6.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(TDD FFS).
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 PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH.
This configuration is verified in test case 18.3.5.2.1.
2. The contents of System Information Block type 5 as specified in TS 34.108, clause 6.1.3 (TDD FFS).
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 PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH.
This configuration is verified in test case 18.3.5.2.2.
3. The contents of System Information Block type 5 and 6 as specified in TS 34.108, clause 6.1.2 (TDD FFS).
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 PS RAB and the FACH for SRBs on CCCH/ DCCH/ BCCH for connected mode UEs.
This configuration is verified in test case 18.3.5.2.3.
18.3.5.2.1 One SCCPCH: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.2.1.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.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.6.4.4.2 and 6.11.6.4.5.2 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.6.4.5.2(Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.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 (TDD FFS).
Uplink TFS:
|
TFI |
RB7+SRB |
|
|
TFS |
TF0, bits |
1 x 170 |
Uplink TFCS:
|
TFCI |
RB7+SRB |
|
UL_TFC0 |
TF0 |
Downlink TFS for SCCPCH#2:
|
TFI |
RB7 (32 kbps) |
SRBs |
|
|
TFS |
TF0, bits |
0x363 |
0x171 |
|
TF1, bits |
1×363 |
1×171 |
|
|
TF2, bits |
2×363 |
2×171 |
|
|
TF3, bits |
N/A |
3×171 |
|
|
TF4, bits |
N/A |
4×171 |
Downlink TFCS for SCCPCH#2:
|
TFCI |
(RB7,SRB) |
|
DL_TFC0 |
(TF0, TF0) |
|
DL_TFC1 |
(TF0, TF1) |
|
DL_TFC2 |
(TF0, TF2) |
|
DL_TFC3 |
(TF0, TF3) |
|
DL_TFC4 |
(TF0, TF4) |
|
DL_TFC5 |
(TF1, TF0) |
|
DL_TFC6 |
(TF1, TF1) |
|
DL_TFC7 |
(TF1, TF2) |
|
DL_TFC8 |
(TF2, TF0) |
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_TFC7 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 376 bits |
RB7: 312 bits |
|
2 |
DL_TFC8 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 632 bits |
RB7: 632 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
||||||
See 18.3.1.1 for test procedure.
18.3.5.2.1.4 Test Requirements
See 18.3.1.1 for definition of step 15
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15 the UE shall return
– for sub-test 1: an RLC SDU on RB7 having the same content as 1 times plus 64 lsb’s of the DL RLC SDU sent by the SS.
– for sub-test 2: an RLC SDU on RB7 having the same content as the DL RLC SDU sent by the SS.
18.3.5.2.2 Two SCCPCHs: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.2.2.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.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.6.4.4.2 and 6.11.6.4.5.2 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.6.4.5.2 (Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.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 (TDD FFS).
Uplink TFS:
|
TFI |
RB7+SRB |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
RB7+SRB |
|
UL_TFC0 |
TF0 |
Downlink TFS (for SCCPCH#2 & SCCPCH#3):
|
TFI |
RB7 (32 kbps) |
SRBs |
|
|
TFS |
TF0, bits |
0x363 |
0x171 |
|
TF1, bits |
1×363 |
1×171 |
|
|
TF2, bits |
2×363 |
2×171 |
|
|
TF3,bits |
N/A |
3×171 |
|
|
TF4,bits |
N/A |
4×171 |
Downlink TFCS (for SCCPCH#2 & SCCPCH#3):
|
TFCI |
(RB7,SRB) |
|
DL_TFC0 |
(TF0, TF0) |
|
DL_TFC1 |
(TF0, TF1) |
|
DL_TFC2 |
(TF0, TF2) |
|
DL_TFC3 |
(TF0, TF3) |
|
DL_TFC4 |
(TF0, TF4) |
|
DL_TFC5 |
(TF1, TF0) |
|
DL_TFC6 |
(TF1, TF1) |
|
DL_TFC7 |
(TF1, TF2) |
|
DL_TFC8 |
(TF2, TF0) |
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_TFC7 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 376 bits |
RB7: 312 bits |
|
2 |
DL_TFC8 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 632 bits |
RB7: 632 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
||||||
See 18.3.1.1 for test procedure.
18.3.5.2.2.4 Test Requirements
See 18.3.1.1 for definition of step 15
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15 the UE shall return
– for sub-test 1: an RLC SDU on RB7 having the same content as 1 times plus 64 lsb’s of the DL RLC SDU sent by the SS.
– for sub-test 2: an RLC SDU on RB7 having the same content as the DL RLC SDU sent by the SS.
18.3.5.2.3 One SCCPCH/connected mode: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.2.3.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.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.6.4.4.2 and 6.11.6.4.5.2 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.6.4.5.2 (Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.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 (TDD FFS).
Uplink TFS:
|
TFI |
RB7+SRB |
|
|
TFS |
TF0, bits |
1 x 170 |
Uplink TFCS:
|
TFCI |
RB7+SRB |
|
UL_TFC0 |
TF0 |
Downlink TFS for SCCPCH#3:
|
TFI |
RB7 (32 kbps) |
SRBs |
|
|
TFS |
TF0, bits |
0x363 |
0x171 |
|
TF1, bits |
1×363 |
1×171 |
|
|
TF2, bits |
2×363 |
2×171 |
|
|
TF3,bits |
N/A |
3×171 |
|
|
TF4,bits |
N/A |
4×171 |
Downlink TFCS for SCCPCH#3:
|
TFCI |
(SRB, RB7) |
|
DL_TFC0 |
(TF0, TF0) |
|
DL_TFC1 |
(TF0, TF1) |
|
DL_TFC2 |
(TF0, TF2) |
|
DL_TFC3 |
(TF0, TF3) |
|
DL_TFC4 |
(TF0, TF4) |
|
DL_TFC5 |
(TF1,TF0) |
|
DL_TFC6 |
(TF1,TF2) |
|
DL_TFC7 |
(TF1,TF3) |
|
DL_TFC8 |
(TF2,TF0) |
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_TFC7 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 376 bits |
RB7: 312 bits |
|
2 |
DL_TFC8 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 632 bits |
RB7: 632 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
||||||
See 18.3.1.1 for test procedure.
18.3.5.2.3.4 Test Requirements
See 18.3.1.1 for definition of step 15
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15 the UE shall return
– for sub-test 1: an RLC SDU on RB7 having the same content as 1 times plus 64 lsb’s of the DL RLC SDU sent by the SS.
– for sub-test 2: an RLC SDU on RB7 having the same content as the DL RLC SDU sent by the SS.
18.3.5.2a Interactive/Background 32 kbps PS RAB + 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.6.4.4.2a.
This radio bearer configuration is tested with three different SYSTEM INFORMATION (BCCH) configurations:
1. The contents of System Information Block type 5 shall be as per the message specific content below.
Two SCCPCHs are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the PCH and the second SCCPCH carries the FACH for two Interactive/Background 32 kbps PS RABs and the FACH for SRBs on CCCH/ DCCH/ BCCH.
This configuration is verified in test case 18.3.5.2a.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 two Interactive/Background 32 kbps PS RABs and the FACH for SRBs on CCCH/ DCCH/ BCCH.
This configuration is verified in test case 18.3.5.2a.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 two Interactive/Background 32 kbps PS RABs and the FACH for SRBs on CCCH/ DCCH/ BCCH for connected mode UEs.
This configuration is verified in test case 18.3.5.2a.3.
Specific Message Content for Radio Bearer Setup message to be used for these test cases:
Use the RADIO BEARER SETUP message as defined in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|---|---|
|
– RAB information for setup – RAB info |
(AM DTCH for PS domain) |
|
– RAB identity |
0000 0101B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
|
– CN domain identity |
PS domain |
|
– NAS Synchronization Indicator |
Not Present |
|
– Re-establishment timer |
useT315 |
|
– RB information to setup |
|
|
– RB identity |
20 |
|
– PDCP Info |
Not Present |
|
– CHOICE RLC info type – CHOICE Uplink RLC mode |
RLC info AM RLC |
|
– Transmission RLC discard – CHOICE SDU discard mode – MAX_DAT |
No Discard 15 |
|
– Transmission window size – Timer_RST |
128 500 |
|
– Max_RST |
4 |
|
– Polling info |
|
|
– Timer_poll_prohibit |
200 |
|
– Timer_poll |
200 |
|
– Poll_PDU |
Not Present |
|
– Poll_SDU |
1 |
|
– Last transmission PDU poll |
TRUE |
|
– Last retransmission PDU poll |
TRUE |
|
– Poll_Windows |
99 |
|
– Timer_poll_periodic |
Not Present |
|
– CHOICE Downlink RLC mode |
AM RLC |
|
– In-sequence delivery |
TRUE |
|
– Receiving window size |
128 |
|
– Downlink RLC status info |
|
|
– Timer_status_prohibit |
200 |
|
– Timer_EPC |
Not Present |
|
– Missing PDU indicator |
TRUE |
|
– Timer_STATUS_periodic |
Not Present |
|
– RB mapping info |
|
|
– Information for each multiplexing option |
2 RBMuxOptions |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
DCH |
|
– UL Transport channel identity |
1 |
|
– Logical channel identity |
7 |
|
– CHOICE RLC size list |
Configured |
|
– MAC logical channel priority |
8 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
DCH |
|
– DL DCH Transport channel identity |
6 |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
|
– CHOICE RLC size list |
Explicit list |
|
– RLC size index |
Reference to TS34.108 clause 6 Parameter Set |
|
– MAC logical channel priority |
8 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
FACH |
|
– DL DCH Transport channel identity |
Not Present |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
|
– RAB identity |
0000 0110B The first/ leftmost bit of the bit string contains the most significant bit of the RAB identity. |
|
– CN domain identity |
PS domain |
|
– NAS Synchronization Indicator |
Not Present |
|
– Re-establishment timer |
useT315 |
|
– RB information to setup |
|
|
– RB identity |
24 |
|
– PDCP info |
Not Present |
|
– CHOICE RLC info type |
RLC info |
|
– CHOICE Uplink RLC mode |
AM RLC |
|
– Transmission RLC discard |
|
|
– CHOICE SDU discard mode |
No Discard |
|
– MAX_DAT |
15 |
|
– Transmission window size |
128 |
|
– Timer_RST |
500 |
|
– Max_RST |
4 |
|
– Polling info |
|
|
– Timer_poll_prohibit |
200 |
|
– Timer_poll |
200 |
|
– Poll_PDU |
Not Present |
|
– Poll_SDU |
1 |
|
– Last transmission PDU poll |
TRUE |
|
– Last retransmission PDU poll |
TRUE |
|
– Poll_Windows |
99 |
|
– Timer_poll_periodic |
Not Present |
|
– CHOICE Downlink RLC mode |
AM RLC |
|
– In-sequence delivery |
TRUE |
|
– Receiving window size |
128 |
|
– Downlink RLC status info |
|
|
– Timer_status_prohibit |
200 |
|
– Timer_EPC |
Not Present |
|
– Missing PDU indicator |
TRUE |
|
– Timer_STATUS_periodic |
Not Present |
|
– RB mapping info |
|
|
– Information for each multiplexing option |
2 RBMuxOptions |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
DCH |
|
– UL Transport channel identity |
1 |
|
– Logical channel identity |
10 |
|
– CHOICE RLC size list |
Configured |
|
– MAC logical channel priority |
8 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
DCH |
|
– DL DCH Transport channel identity |
6 |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
10 |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
10 |
|
– CHOICE RLC size list |
Explicit list |
|
– RLC size index |
Reference to TS34.108 clause 6 Parameter Set |
|
– MAC logical channel priority |
8 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
FACH |
|
– DL DCH Transport channel identity |
Not Present |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
10 |
18.3.5.2a.1 One SCCPCH: Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.2a.1.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.2a.1.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.6.4.4.2a and 6.11.6.4.5.3 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 two Interactive/Background 32 kbps PS RABs 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.6.4.5.3.1 (Interactive/Background 12.8 kbps PS RAB + Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.2a.1.3 Method of Test
The contents of System Information Block type 5 per the specific message content below.
See 18.3.1.1 for test procedure.
NOTE: The test procedure for single radio bearer configurations is used as there are no uplink transport format combinations for simultaneous data transmission on the PS radio bearers, nor any transport format combination for simultaneous data transmission and signalling.
Uplink TFS:
|
TFI |
RB7+RB8+SRB |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
RB7 + RB8 |
|
UL_TFC0 |
TF0 |
Downlink TFS for SCCPCH#2:
|
TFI |
RB7 + RB8 |
SRBs |
|
|
TFS |
TF0, bits |
0x363 |
0x171 |
|
TF1, bits |
1×363 |
1×171 |
|
|
TF2, bits |
2×363 |
2×171 |
|
|
TF3, bits |
N/A |
3×171 |
|
|
TF4, bits |
N/A |
4×171 |
Downlink TFCS for SCCPCH #2:
|
TFCI |
(RB7+RB8, SRB) |
|
DL_TFC0 |
(TF0,TF0) |
|
DL_TFC1 |
(TF0,TF1) |
|
DL_TFC2 |
(TF0,TF2) |
|
DL_TFC3 |
(TF0,TF3) |
|
DL_TFC4 |
(TF0,TF4) |
|
DL_TFC5 |
(TF1,TF0) |
|
DL_TFC6 |
(TF1,TF1) |
|
DL_TFC7 |
(TF1,TF2) |
|
DL_TFC8 |
(TF2,TF0) |
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_TFC7 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 376 bits RB8: 376 bits |
RB7: 312 bits RB8: No Data |
|
2 |
DL_TFC8 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 632 bits RB8: 632 bits |
RB7: No Data RB8: 632 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
||||||
Specific Message Contents
Use the default parameter values for the system information block 5 with the same type specified in clause 6.1.1 of TS 34.108, with the following exceptions
|
Information Element |
Value/remark |
|
– SIB6 indicator |
FALSE |
See 18.3.1.1 for test procedure.
18.3.5.2.3.4 Test Requirements
See 18.3.1.1 for definition of step 15
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15 the UE shall return
– for sub-test 1: an RLC SDU on RB7 having the same content as 1 times plus 64 lsb’s of the DL RLC SDU sent by the SS.
– for sub-test 2: an RLC SDU on RB8 having the same content as the DL RLC SDU sent by the SS.
18.3.5.2a.2 Two SCCPCHs: Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.2a.2. 1 Conformance requirement
See 18.3.2.4.1.
18.3.5.2a.2. 2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.11.6.4.4.2a and 6.11.6.4.5.3 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 two Interactive/Background 32 kbps PS RABs 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.6.4.5.3.1 (Interactive/Background 12.8 kbps PS RAB + Interactive/Background 12.8 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.2a.2.1.3 Method of Test
The contents of System Information Block type 5 shall be as specified in TS 34.108, clause 6.1.3.
See 18.3.1.1 for test procedure.
NOTE: The test procedure for single radio bearer configurations is used as there are no uplink transport format combinations for simultaneous data transmission on the PS radio bearers, nor any transport format combination for simultaneous data transmission and signalling.
Uplink TFS:
|
TFI |
RB7 + RB8 |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
RB7 + RB8 |
|
UL_TFC0 |
TF0 |
Downlink TFS:
|
TFI |
RB7 + RB8 |
SRBs |
|
|
TFS |
TF0, bits |
0x363 |
0x171 |
|
TF1, bits |
1×363 |
1×171 |
|
|
TF2, bits |
2×363 |
2×171 |
|
|
TF3, bits |
N/A |
3×171 |
|
|
TF4, bits |
N/A |
4×171 |
Downlink TFCS for SCCPCH#2 & #3:
|
TFCI |
(SRB, RB7+RB8) |
|
DL_TFC0 |
(TF0,TF0) |
|
DL_TFC1 |
(TF0,TF1) |
|
DL_TFC2 |
(TF0,TF2) |
|
DL_TFC3 |
(TF0,TF3) |
|
DL_TFC4 |
(TF0,TF4) |
|
DL_TFC5 |
(TF1,TF0) |
|
DL_TFC6 |
(TF1,TF1) |
|
DL_TFC7 |
(TF1,TF2) |
|
DL_TFC8 |
(TF2,TF0) |
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_TFC7 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 376 bits RB8: 376 bits |
RB7: 312 bits RB8: No Data |
|
2 |
DL_TFC8 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 632 bits RB8: 632 bits |
RB7: No Data RB8: 632 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
||||||
See 18.3.1.1 for test procedure.
18.3.5.2.3.4 Test Requirements
See 18.3.1.1 for definition of step 15
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15 the UE shall return
– for sub-test 1: an RLC SDU on RB7 having the same content as 1 times plus 64 lsb’s of the DL RLC SDU sent by the SS.
– for sub-test 2: an RLC SDU on RB8 having the same content as the DL RLC SDU sent by the SS.
18.3.5.2a.3 One SCCPCH/connected mode: Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.2a.3.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.2a.3. 2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.10.2.4.3.2 and 6.10.2.4.4.2 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 two Interactive/Background 32 kbps PS RABs 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.10.2.4.4.2 (Interactive/Background 32 kbps PS RAB + Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.2a.3.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.2.
See 18.3.1.1 for test procedure.
NOTE: The test procedure for single radio bearer configurations is used as there are no uplink transport format combinations for simultaneous data transmission on the PS radio bearers, nor any transport format combination for simultaneous data transmission and signalling.
Uplink TFS:
|
TFI |
RB7+RB8+SRB |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
RB7 + RB8 |
|
UL_TFC0 |
TF0 |
Downlink TFS for SCCPCH #3:
|
TFI |
RB7 + RB8 |
SRBs |
|
|
TFS |
TF0, bits |
0x363 |
0x171 |
|
TF1, bits |
1×363 |
1×171 |
|
|
TF2, bits |
2×363 |
2×171 |
|
|
TF3, bits |
N/A |
3×171 |
|
|
TF4, bits |
N/A |
4×171 |
Downlink TFCS for third SCCPCH:
|
TFCI |
(SRB, RB7+RB8) |
|
DL_TFC0 |
(TF0, TF0) |
|
DL_TFC1 |
(TF0,TF1) |
|
DL_TFC2 |
(TF0,TF2) |
|
DL_TFC3 |
(TF0,TF3) |
|
DL_TFC4 |
(TF0,TF4) |
|
DL_TFC5 |
(TF1,TF0) |
|
DL_TFC6 |
(TF1,TF1) |
|
DL_TFC7 |
(TF1,TF2) |
|
DL_TFC8 |
(TF2,TF0) |
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_TFC7 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 376 bits RB8: 376 bits |
RB7: 312 bits RB8: No Data |
|
2 |
DL_TFC8 |
UL_TFC0 |
DL_TFC0 |
UL_TFC0 |
RB7: 632 bits RB8: 632 bits |
RB7: No Data RB8: 632 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
||||||
See 18.3.1.1 for test procedure.
18.3.5.2.3.4 Test Requirements
See 18.3.1.1 for definition of step 15
1. At step 10 the UE shall send RADIO BEARER SETUP COMPLETE.
2. At step 15 the UE shall return
– for sub-test 1: an RLC SDU on RB7 having the same content as 1 times plus 64 lsb’s of the DL RLC SDU sent by the SS.
– for sub-test 2: an RLC SDU on RB8 having the same content as the DL RLC SDU sent by the SS.
18.3.5.2b 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.6.4.4.2b.
This radio bearer configuration is tested with one SYSTEM INFORMATION (BCCH) configuration:
1. The contents of System Information Block type 5 and 6 as specified in TS 34.108, clause 6.1.1 (TDD FSS).
Two SCCPCHs are used in this SYSTEM INFORMATION configuration. The first SCCPCH carries the PCH and the second SCCPCH carries the FACH for SRBs on CCCH/ DCCH/ BCCH.
18.3.5.2b.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.2b.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.6.4.4.2b and 6.11.6.4.5.1 for the case when one SCCPCH is used in this SYSTEM INFORMATION configuration. The SCCPCH carries the FACH for SRBs on CCCH/ DCCH/ BCCH.
18.3.5.2b.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(TDD FSS).
See 18.3.1.1 for test procedure.
NOTE: The test procedure for single radio bearer configurations is used as there are no uplink transport format combinations for simultaneous data transmission on the PS radio bearers, nor any transport format combination for simultaneous data transmission and signalling.
Uplink TFS:
|
TFI |
SRB |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
SRB |
|
UL_TFC0 |
TF0 |
Downlink TFS for SCCPCH:
|
TFI |
SRBs |
|
|
TFS |
TF0, bits |
0x171 |
|
TF1, bits |
1×171 |
|
|
TF2, bits |
2×171 |
|
|
TF3, bits |
3×171 |
|
|
TF4, bits |
4×171 |
Downlink TFCS for SCCPCH:
|
TFCI |
(SRB) |
|
DL_TFC0 |
(TF0) |
|
DL_TFC1 |
(TF1) |
|
DL_TFC2 |
(TF2) |
|
DL_TFC3 |
(TF3) |
|
DL_TFC4 |
(TF4) |
18.3.5.2b.4 Test Requirements
See 18.3.1.1 for definition of step 6
1. At step 6 the UE transmitted PAGING RESPONSE (DCCH) received at the SS shall complete the test and end gracefully.
18.3.5.3 Interactive/Background RAB + SRBs for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.3.1 Interactive/Background 32 kbps RAB + SRBs for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.3.1.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.3.1.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.11.6.4.4.3 and 6.11.6.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.6.4.5.2 (Interactive/Background – 12.2 kbps) PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.3.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.0b.
Uplink TFS:
|
TFI |
RB8 |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
RB8 |
|
UL_TFC0 |
TF0 |
Downlink TFS:
|
TFI |
RB8 (32 kbps) |
PCCH |
SRBs |
|
|
TFS |
TF0, bits |
0x363 |
0x240 |
0x171 |
|
TF1, bits |
1×363 |
1×240 |
1×171 |
|
|
TF2, bits |
2×363 |
N/A |
2×171 |
|
|
TF3, bits |
N/A |
N/A |
3×171 |
|
|
TF4, bits |
N/A |
N/A |
4×171 |
Downlink TFCS:
|
TFCI |
(RB8, PCCH, SRB) |
|
DL_TFC0 |
(TF0, TF0, TF0), |
|
DL_TFC1 |
(TF0, TF0, TF1), |
|
DL_TFC2 |
(TF0, TF0, TF2), |
|
DL_TFC3 |
(TF0, TF0, TF3), |
|
DL_TFC4 |
(TF0, TF0, TF4), |
|
DL_TFC5 |
(TF0, TF1, TF0), |
|
DL_TFC6 |
(TF0, TF1, TF1), |
|
DL_TFC7 |
(TF0, TF1, TF2), |
|
DL_TFC8 |
(TF0, TF1, TF3), |
|
DL_TFC9 |
(TF0, TF1, TF4), |
|
DL_TFC10 |
(TF1, TF0, TF0), |
|
DL_TFC11 |
(TF1, TF0, TF1), |
|
DL_TFC12 |
(TF1, TF0, TF2), |
|
DL_TFC13 |
(TF1, TF0, TF3), |
|
DL_TFC14 |
(TF1, TF0, TF4), |
|
DL_TFC15 |
(TF1, TF1, TF0), |
|
DL_TFC16 |
(TF1, TF1, TF1), |
|
DL_TFC17 |
(TF1, TF1, TF2), |
|
DL_TFC18 |
(TF1, TF1, TF3), |
|
DL_TFC19 |
(TF1, TF1, TF4), |
|
DL_TFC20 |
(TF2, TF0, TF0), |
|
DL_TFC21 |
(TF2, TF0, TF1), |
|
DL_TFC22 |
(TF2, TF0, TF2), |
|
DL_TFC23 |
(TF2, TF0, TF3), |
|
DL_TFC24 |
(TF2, TF0, TF4), |
|
DL_TFC25 |
(TF2, TF1, TF0), |
|
DL_TFC26 |
(TF2, TF1, TF1), |
|
DL_TFC27 |
(TF2, TF1, TF2), |
|
DL_TFC28 |
(TF2, TF1, TF3), |
|
DL_TFC29 |
(TF2, TF1, TF4) |
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_TFC20 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
UL_TFC0 |
RB8:632 bits |
RB8: 632 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
||||||
See 18.3.1.1 for test procedure.
18.3.5.3.1.4 Test requirements
See 18.3.1.1 for definition of step 15
1. At step 15 the UE shall return an RLC SDU on RB8 having the same content as sent by SS
18.3.5.3.2 Interactive/Background 16 kbps RAB + SRBs for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.3.2.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.3.2.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.11.6.4.4.3 and 6.11.6.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.6.4.5.2 (Interactive/Background – 12.2 kbps) PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.3.2.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.0b.
Uplink TFS:
|
TFI |
RB8 |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
RB8 |
|
UL_TFC0 |
TF0 |
Downlink TFS:
|
TFI |
RB8 (32 kbps) |
PCCH |
SRBs |
|
|
TFS |
TF0, bits |
0x363 |
0x80 |
0x171 |
|
TF1, bits |
1×363 |
1×80 |
1×171 |
|
|
TF2, bits |
N/A |
2×80 |
2×171 |
Downlink TFCS:
|
TFCI |
(SRB, PCCH,RB8) |
|
DL_TFC0 |
(TF0, TF0, TF0), |
|
DL_TFC1 |
(TF0, TF0, TF1), |
|
DL_TFC2 |
(TF0, TF0, TF2), |
|
DL_TFC3 |
(TF0, TF1, TF0), |
|
DL_TFC4 |
(TF0, TF1, TF1), |
|
DL_TFC5 |
(TF0, TF2, TF0), |
|
DL_TFC6 |
(TF0, TF2, TF1), |
|
DL_TFC7 |
(TF1, TF0, TF0) |
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_TFC7 |
UL_TFC0 |
DL_TFC0, UL_TFC0 |
UL_TFC0 |
RB8: 376 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.3.1.1 for test procedure.
18.3.5.3.2.4 Test requirements
See 18.3.1.1 for definition of step 15
1. At step 15 the UE shall return an RLC SDU on RB7 having the same content as 1 times plus 64 lsb’s of the DL RLC SDU sent by the SS.
18.3.5.3a SRBs for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH
18.3.5.3a.1 SRBs for PCCH at 12 kbps + SRB for CCCH + SRB for DCCH + SRB for BCCH at 32 kbps
18.3.5.3a.1.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.3a.1.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause for the case when one SCCPCH is used in this SYSTEM INFORMATION (BCCH) configuration. The SCCPCH carries the PCH at 12 kbps and the FACH for SRBs on CCCH/ DCCH/ BCCH at 32 kbps.
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.6.4.5.1 (SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.3a.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.0b.
Uplink TFS:
|
TFI |
SRB |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
SRB |
|
UL_TFC0 |
TF0 |
Downlink TFS:
|
TFI |
PCCH |
SRBs |
|
|
TFS |
TF0, bits |
0x240 |
0x171 |
|
TF1, bits |
1×240 |
1×171 |
|
|
TF2, bits |
N/A |
2×171 |
|
|
TF3,bits |
N/A |
3×171 |
|
|
TF4,bits |
N/A |
4×171 |
Downlink TFCS:
|
TFCI |
(PCCH, SRB) |
|
DL_TFC0 |
(TF0, TF0) |
|
DL_TFC1 |
(TF0, TF1) |
|
DL_TFC2 |
(TF0, TF2) |
|
DL_TFC3 |
(TF0, TF3) |
|
DL_TFC4 |
(TF0, TF4) |
|
DL_TFC5 |
(TF1, TF0) |
|
DL_TFC6 |
(TF1, TF1) |
|
DL_TFC7 |
(TF1, TF2) |
|
DL_TFC8 |
(TF1, TF3) |
|
DL_TFC9 |
(TF1, TF4) |
Sub-tests:
See 18.3.1.1 for test procedure.
18.3.5.3a.1.4 Test requirements
See 18.3.1.1 for definition of step 6x
1. At step 6x the UE transmitted SECURITY MODE COMPLETE (DCCH) received at the SS shall complete the test and end gracefully.
18.3.5.3a.2 SRBs for PCCH at 8 kbps kbps + SRB for CCCH + SRB for DCCH + SRB for BCCH at 16 kbps
18.3.5.3a.2.1 Conformance requirement
See 18.3.2.4.1.
18.3.5.3a.2.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause for the case when one SCCPCH is used in this SYSTEM INFORMATION (BCCH) configuration. The SCCPCH carries the PCH at 8 kbps and the FACH for SRBs on CCCH/ DCCH/ BCCH at 16 kbps.
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.6.4.5.1 (SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
18.3.5.3a.2.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.0b.
Uplink TFS:
|
TFI |
SRB |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
SRB |
|
UL_TFC0 |
TF0 |
Downlink TFS:
|
TFI |
PCCH |
SRBs |
|
|
TFS |
TF0, bits |
0x80 |
0x171 |
|
TF1, bits |
1×80 |
1×171 |
|
|
TF2, bits |
2×80 |
2×171 |
Downlink TFCS:
|
TFCI |
(PCCH, SRB) |
|
DL_TFC0 |
(TF0, TF0) |
|
DL_TFC1 |
(TF0, TF1) |
|
DL_TFC2 |
(TF0, TF2) |
|
DL_TFC3 |
(TF1, TF0) |
|
DL_TFC4 |
(TF1, TF1) |
|
DL_TFC5 |
(TF2, TF0) |
|
DL_TFC6 |
(TF2, TF1) |
Sub-tests:
See 18.3.1.1 for test procedure.
18.3.5.3a.2.4 Test requirements
See 18.3.1.1 for definition of step 6x
1. At step 6x the UE transmitted SECURITY MODE COMPLETE (DCCH) received at the SS shall complete the test and end gracefully.
18.3.5.4 RB for CTCH + SRB for CCCH +SRB for BCCH.
18.3.5.4.1 Definition and applicability
Applicable only for a UE supporting Cell Broadcast Services (CBS) as a type of Broadcast/Multicast Services.
It shall be possible to indicate the reception of certain CBS message contents carried with certain activated CG message types in a clear way on UE side.
18.3.5.4.2 Conformance Requirement
See 18.3.2.4.1 and 7.4.2.1.2.
18.3.5.4.3 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.6.4.4.4 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 verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clauses 6.11.6.4.4.3. Data transfer on CTCH is tested similar to testing BMC for a UE in idle mode as specified in TS 34.123-1, clause 7.4.2, data transfer on CCCH is tested by establishing a RRC connection.
18.3.5.4.4 Method of Test
18.3.5.4.4.1 Initial conditions:
The contents of System Information Block type 5 and 6 shall be as specified in TS 34.108, clause 6.1.2.
The UE is RRC idle mode, the BMC entity is established.
The CB message ID stored on the SIM shall be known for this test (parameter for CBS PDUs). The CBS data type shall be allocated and activated in the UE.
Related ICS/IXIT Statement(s):
As in clause 7.4.2.1.4
Uplink TFS:
|
TFI |
RB7+SRB |
|
|
TFS |
TF0, bits |
1×170 |
Uplink TFCS:
|
TFCI |
RB7+SRB |
|
UL_TFC0 |
TF0 |
Downlink TFS:
|
TFI |
RB7 |
SRBs |
|
|
TFS |
TF0, bits |
0x163 |
0x171 |
|
TF1, bits |
1×163 |
1×171 |
|
|
TF2, bits |
2×163 |
2×171 |
Downlink TFCS:
|
TFCI |
(RB7, SRB) |
|
DL_TFC0 |
(TF0, TF0) |
|
DL_TFC1 |
(TF0, TF1) |
|
DL_TFC2 |
(TF0, TF2) |
|
DL_TFC3 |
(TF1, TF0) |
|
DL_TFC4 |
(TF1, TF1) |
|
DL_TFC5 |
(TF2, TF0) |
18.3.5.4.4.2 Test Procedure:
a) The UE in RRC Idle mode is triggered to wait for the next system information. The UE is activated to receive CBS messages.
b) The UE and the SS have configured their RLC, MAC, and PHYs layers with all CB related system information.
c) The SS sends the CVS message containing an activated CGS message type according to CB-Data 1 to the UE; this shall be repeated for CPREP times (indicated by the parameter "repetition period").
d) The UE indicates in an unambiguous way, that this message was received.
e) Steps 1a 1d in the Expected sequence are followed by the steps 2 – 6 of the test procedure according to clause 18.3.1.1.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1a |
|
SYSTEM INFORMATION |
||
|
1b |
The SS waits for about 10 s to make sure, that the UE is configured to receive CBS data |
|||
|
1c |
|
BMC CBS Message |
Activated CBS message with CB Data 1 message content as described by the manufacturer. This message shall be repeated "CPREP" times, Parameter: – Message_ID, – Serial-No, – Data coding scheme, – CB-Data 1, |
|
|
1d |
After having received the BMC CBS message the UE shall indicate the reception of CB Data 1 in a clear way. |
|||
18.3.5.4.5 Test Requirements
At step 1d in the table above, the UE shall store and decode a received activated CBS message.
At step 5 of the test procedure according to clause 18.3.1.1 the RRC Connection shall be established.
18.3.5.5 64.8kbps RB for MTCH with 80 ms TTI
18.3.5.5.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.3.5.5.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.10.3.4.4.5.
18.3.5.5.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 |
|
|
TF5, bits |
5×665 |
|
|
TF6, bits |
6×665 |
|
|
TF7, bits |
7×665 |
|
|
TF8, bits |
8×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) |
|
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.3.5.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.3.5.6 129.6 kbps RB for MTCH with 80 ms TTI
18.3.5.6.1 Conformance Requirement
See 18.3.5.5.1.
18.3.5.6.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.10.3.4.4.6.
18.3.5.6.3 Method of Test
See 14.1.5 for test procedure.
Downlink TFS:
|
TFI |
RB for MTCH (129.6 kbps) |
|
|
TFS |
TF0, bits |
0x664 |
|
TF1, bits |
1×664 |
|
|
TF2, bits |
2×664 |
|
|
TF3, bits |
3×664 |
|
|
TF4, bits |
4×664 |
|
|
TF5, bits |
5×664 |
|
|
TF6, bits |
6×664 |
|
|
TF7, bits |
7×664 |
|
|
TF8, bits |
8×664 |
|
|
TF9, bits |
9×664 |
|
|
TF10, bits |
10×664 |
|
|
TF11, bits |
11×664 |
|
|
TF12, bits |
12×664 |
|
|
TF13, bits |
13×664 |
|
|
TF14, bits |
14×664 |
|
|
TF15, bits |
15×664 |
|
|
TF16, bits |
16×664 |
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) |
|
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.3.5.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.3.5.7 259.2 kbps RB for MTCH with 40 ms TTI
18.3.5.7.1 Conformance Requirement
See 18.3.5.5.1.
18.3.5.7.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.10.3.4.4.7.
18.3.5.7.3 Method of Test
See 14.1.5 for test procedure.
Downlink TFS:
|
TFI |
RB for MTCH (259.2 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.3.5.7.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.3.5.8 124.4kbps RB for MBSFN MTCH with 80 ms TTI
18.3.5.8.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.3.5.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.6.4.4.9.
18.3.5.8.3 Method of Test
See subclause 18.3.1.6 for test procedure.
Downlink TFS:
|
TFI |
RB for MTCH (124.4 kbps) |
|
|
TFS |
TF0, bits |
0x4993 |
|
TF1, bits |
1×4993 |
|
|
TF2, bits |
2×4993 |
Downlink TFCS:
|
TFCI |
RB for MTCH (124.4 kbps) |
|
DL_TFC0 |
(TF0) |
|
DL_TFC1 |
(TF1) |
|
DL_TFC2 |
(TF2) |
Sub-tests:
|
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (NOTE 1) |
|
1 |
DL_TFC1 |
DL_TFC0 |
4960 |
|
2 |
DL_TFC2 |
DL_TFC0 |
9936 |
|
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.3.5.8.4 Test Requirements
See subclause 18.3.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.2.1.6 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.3.5.9 320.4 kbps RB for MBSFN MTCH with 80 ms TTI
18.3.5.9.1 Conformance Requirement
See 18.3.5.8.1.
18.3.5.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.6.4.4.10.
18.3.5.9.3 Method of Test
See subclause 18.3.1.6 for test procedure.
Downlink TFS:
|
TFI |
RB for MTCH (320.4 kbps) |
|
|
TFS |
TF0, bits |
0x4289 |
|
TF1, bits |
1×4289 |
|
|
TF2, bits |
6×4289 |
Downlink TFCS:
|
TFCI |
RB for MTCH (320.4 kbps) |
|
DL_TFC0 |
(TF0) |
|
DL_TFC1 |
(TF1) |
|
DL_TFC2 |
(TF2) |
Sub-tests:
|
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (NOTE 1) |
|
1 |
DL_TFC1 |
DL_TFC0 |
4256 |
|
2 |
DL_TFC2 |
DL_TFC0 |
25616 |
|
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.3.5.9.4 Test Requirements
See subclause 18.3.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.2.1.6 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.3.5.10 497.6 kbps RB for MBSFN MTCH with 80 ms TTI
18.3.5.10.1 Conformance Requirement
See 18.3.5.8.1.
18.3.5.10.2 Test purpose
Test to verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.11.6.4.4.11.
18.3.5.10.3 Method of Test
See subclause 18.3.1.6 for test procedure.
Downlink TFS:
|
TFI |
RB for MTCH (497.6 kbps) |
|
|
TFS |
TF0, bits |
0x4993 |
|
TF1, bits |
1×4993 |
|
|
TF2, bits |
8×4993 |
Downlink TFCS:
|
TFCI |
RB for MTCH (497.6 kbps) |
|
DL_TFC0 |
(TF0) |
|
DL_TFC1 |
(TF1) |
|
DL_TFC2 |
(TF2) |
Sub-tests:
|
Sub-test |
Downlink TFCS Under test |
Implicitly tested |
Test data size (bits) (NOTE 1) |
|
1 |
DL_TFC1 |
DL_TFC0 |
4960 |
|
2 |
DL_TFC2 |
DL_TFC0 |
39792 |
|
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.3.5.10.4 Test Requirements
See subclause 18.3.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.2.1.6 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.