14.4 Combinations on SCCPCH
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
14.4.1 Stand-alone signalling RB for PCCH
Void
14.4.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.10.2.4.3.2.
This radio bearer configuration is tested with three different SYSTEM INFORMATION (BCCH) configurations:
1. The contents of System Information Block type 5 / System Information Block type 5bis shall be as per the specific message content.
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 14.4.2.1.
2. The contents of System Information Block type 5 / System Information Block type 5bis 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 14.4.2.2.
3. The contents of System Information Block type 5 / System Information Block type 5bis 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 14.4.2.3.
14.4.2.1 One SCCPCH: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
14.4.2.1.1 Conformance requirement
See 14.2.4.1.
14.4.2.1.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.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.10.2.4.4.1 (Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
14.4.2.1.3 Method of Test
The contents of System Information Block type 5 / System Information Block type 5bis shall be as per the specific message content.
Uplink TFS:
|
TFI |
RB7+SRB |
|
|
TFS |
TF0, bits |
1×168 |
|
TF1, bits |
1×360 |
Uplink TFCS:
|
TFCI |
RB7+SRB |
|
UL_TFC0 |
TF0 |
|
UL_TFC1 |
TF1 |
Downlink TFS:
|
SRBs |
RB7 (32 kbps) |
||
|
TFS |
TF0, bits |
0x168 |
0x360 |
|
TF1, bits |
1×168 |
1×360 |
|
|
TF2, bits |
2×168 |
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 |
UL RLC SDU size (note) |
Test data size (note) |
|
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, 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 14.1.1 for test procedure.
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 |
14.4.2.1.4 Test Requirements
See 14.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be RB7/TF1 (1×360).
2. At step 15 the UE shall return an RLC SDU on RB7 having the same content as sent by SS
14.4.2.2 Two SCCPCHs: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
14.4.2.2.1 Conformance requirement
See 14.2.4.1.
14.4.2.2.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.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.10.2.4.4.1 (Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
14.4.2.2.3 Method of Test
The contents of System Information Block type 5 / System Information Block type 5bis shall be as specified in TS 34.108, clause 6.1.3.
Uplink TFS:
|
TFI |
RB7+SRB |
|
|
TFS |
TF0, bits |
1×168 |
|
TF1, bits |
1×360 |
Uplink TFCS:
|
TFCI |
RB7+SRB |
|
UL_TFC0 |
TF0 |
|
UL_TFC1 |
TF1 |
Downlink TFS:
|
SRBs |
RB7 (32 kbps) |
||
|
TFS |
TF0, bits |
0x168 |
0x360 |
|
TF1, bits |
1×168 |
1×360 |
|
|
TF2, bits |
2×168 |
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 |
UL RLC SDU size (note) |
Test data size (note) |
|
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, 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 14.1.1 for test procedure.
14.4.2.2.4 Test Requirements
See 14.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be RB7/TF1 (1×360).
2. At step 15 the UE shall return an RLC SDU on RB7 having the same content as sent by SS
14.4.2.3 One SCCPCH/connected mode: Interactive/Background 32 kbps PS RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH
14.4.2.3.1 Conformance requirement
See 14.2.4.1.
14.4.2.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.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.10.2.4.4.1 (Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
14.4.2.3.3 Method of Test
The contents of System Information Block type 5 / System Information Block type 5bis and 6 shall be as specified in TS 34.108, clause 6.1.2.
Uplink TFS:
|
TFI |
RB7+SRB |
|
|
TFS |
TF0, bits |
1×168 |
|
TF1, bits |
1×360 |
Uplink TFCS:
|
TFCI |
RB7+SRB |
|
UL_TFC0 |
TF0 |
|
UL_TFC1 |
TF1 |
Downlink TFS:
|
SRBs |
RB7 (32 kbps) |
||
|
TFS |
TF0, bits |
0x168 |
0x360 |
|
TF1, bits |
1×168 |
1×360 |
|
|
TF2, bits |
2×168 |
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 |
UL RLC SDU size (note) |
Test data size (note) |
|
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, 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 14.1.1 for test procedure.
14.4.2.3.4 Test Requirements
See 14.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be RB7/TF1 (1×360).
2. At step 15 the UE shall return an RLC SDU on RB7 having the same content as sent by SS
14.4.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.10.2.4.3.2a.
This radio bearer configuration is tested with three different SYSTEM INFORMATION (BCCH) configurations:
1. The contents of System Information Block type 5 / System Information Block type 5bis shall be as per the message specific content.
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 14.4.2a.1.
2. The contents of System Information Block type 5 / System Information Block type 5bis 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 14.4.2a.2.
3. The contents of System Information Block type 5 / System Information Block type 5bis 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 14.4.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 |
14.4.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
14.4.2a.1.1 Conformance requirement
See 14.2.4.1.
14.4.2a.1.2 Test purpose
To verify establishment and data transfer of reference radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.3.2a and 6.10.2.4.4.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 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.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.
14.4.2a.1.3 Method of Test
The contents of System Information Block type shall be as per the specific message content below.
See 14.1.1 for test procedure.
NOTE The test procedure for single radio bearer configurations is used as there are no uplink transport format combination 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×168 |
|
TF1, bits |
1×360 |
Uplink TFCS:
|
TFCI |
RB7 + RB8 |
|
UL_TFC0 |
TF0 |
|
UL_TFC1 |
TF1 |
Downlink TFS:
|
SRBs |
RB7 + RB8 |
||
|
TFS |
TF0, bits |
0x168 |
0x360 |
|
TF1, bits |
1×168 |
1×360 |
|
|
TF2, bits |
2×168 |
N/A |
Downlink TFCS:
|
TFCI |
(SRB, RB7+RB8) |
|
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 |
UL RLC SDU size (note) |
Test data size (note) |
|
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
RB7: 312 bits RB8: 312 bits |
RB7: 312 bits RB8: No data |
|
2 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
RB7: 312 bits RB8: 312 bits |
RB7: No data RB8: 312 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 |
14.4.2a.1.4 Test Requirements
See 14.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be TF1 (1×360).
2. At step 15 the UE shall return
– for sub test 1: RLC SDUs on RB7 having the same content as sent by SS
– for sub test 2: RLC SDUs on RB8 having the same content as sent by SS
14.4.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
14.4.2a.2.1 Conformance requirement
See 14.2.4.1.
14.4.2a.2.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 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.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.
14.4.2a.2.3 Method of Test
The contents of System Information Block type 5 / System Information Block type 5bis shall be as specified in TS 34.108, clause 6.1.3.
See 14.1.1 for test procedure.
NOTE The test procedure for single radio bearer configurations is used as there are no uplink transport format combination 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×168 |
|
TF1, bits |
1×360 |
Uplink TFCS:
|
TFCI |
RB7 + RB8 |
|
UL_TFC0 |
TF0 |
|
UL_TFC1 |
TF1 |
Downlink TFS:
|
SRBs |
RB7 + RB8 |
||
|
TFS |
TF0, bits |
0x168 |
0x360 |
|
TF1, bits |
1×168 |
1×360 |
|
|
TF2, bits |
2×168 |
N/A |
Downlink TFCS:
|
TFCI |
(SRB, RB7+RB8) |
|
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 |
UL RLC SDU size (note) |
Test data size (note) |
|
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
RB7: 312 bits RB8: 312 bits |
RB7: 312 bits RB8: No data |
|
2 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
RB7: 312 bits RB8: 312 bits |
RB7: No data RB8: 312 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
|||||
14.4.2a.2.4 Test Requirements
See 14.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be TF1 (1×360).
2. At step 15 the UE shall return
– for sub test 1: RLC SDUs on RB7 having the same content as sent by SS
– for sub test 2: RLC SDUs on RB8 having the same content as sent by SS
14.4.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
14.4.2a.3.1 Conformance requirement
See 14.2.4.1.
14.4.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.
14.4.2a.3.3 Method of Test
The contents of System Information Block type 5 / System Information Block type 5bis and 6 shall be as specified in TS 34.108, clause 6.1.2.
See 14.1.1 for test procedure.
NOTE The test procedure for single radio bearer configurations is used as there are no uplink transport format combination 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×168 |
|
TF1, bits |
1×360 |
Uplink TFCS:
|
TFCI |
RB7 + RB8 |
|
UL_TFC0 |
TF0 |
|
UL_TFC1 |
TF1 |
Downlink TFS:
|
SRBs |
RB7 + RB8 |
||
|
TFS |
TF0, bits |
0x168 |
0x360 |
|
TF1, bits |
1×168 |
1×360 |
|
|
TF2, bits |
2×168 |
N/A |
Downlink TFCS:
|
TFCI |
(SRB, RB7+RB8) |
|
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 |
UL RLC SDU size (note) |
Test data size (note) |
|
1 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
RB7: 312 bits RB8: 312 bits |
RB7: 312 bits RB8: No data |
|
2 |
DL_TFC3 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
RB7: 312 bits RB8: 312 bits |
RB7: No data RB8: 312 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
|||||
14.4.2a.3.4 Test Requirements
1. At step 15 the UE transmitted transport format shall be TF1 (1×360).
2. At step 15 the UE shall return
– for sub test 1: RLC SDUs on RB7 having the same content as sent by SS
– for sub test 2: RLC SDUs on RB8 having the same content as sent by SS
14.4.3 Interactive/Background 32 kbps RAB + SRBs for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH
14.4.3.1 Conformance requirement
See 14.2.4.1.
14.4.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.3 and 6.10.2.4.4.1 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.10.2.4.4.1 (Interactive/Background 32 kbps PS RAB + SRB for CCCH + SRB for DCCH on PRACH) is used in uplink.
14.4.3.3 Method of Test
The contents of System Information Block type 5 / System Information Block type 5bis and 6 shall be as specified in TS 34.108, clause 6.1.
Uplink TFS:
|
TFI |
RB8 |
|
|
TFS |
TF0, bits |
1×168 |
|
TF1, bits |
1×360 |
Uplink TFCS:
|
TFCI |
RB8 |
|
UL_TFC0 |
TF0 |
|
UL_TFC1 |
TF1 |
Downlink TFS:
|
PCCH |
SRBs |
RB8 (32 kbps) |
||
|
TFS |
TF0, bits |
0x240 |
0x168 |
0x360 |
|
TF1, bits |
1×240 |
1×168 |
1×360 |
|
|
TF2, bits |
N/A |
2×168 |
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 |
UL RLC SDU size (note) |
Test data size (note) |
|
1 |
DL_TFC6 |
UL_TFC1 |
DL_TFC0, UL_TFC0 |
RB8: 312 bits |
RB8: 312 bits |
|
NOTE: See TS 34.109 [10] clause 5.3.2.6.2 for details regarding loopback of RLC SDUs. |
|||||
See 14.1.1 for test procedure.
14.4.3.4 Test requirements
See 14.1.1 for definition of step 15
1. At step 15 the UE transmitted transport format shall be RB8/TF1 (1×360).
2. At step 15 the UE shall return an RLC SDU on RB8 having the same content as sent by SS
14.4.4 RB for CTCH + SRB for CCCH +SRB for BCCH
14.4.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.
14.4.4.2 Conformance Requirement
See 14.2.4.1 and 7.4.2.1.2.
14.4.4.3 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.3.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.10.2.4.3.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.
14.4.4.4 Method of Test
Initial conditions:
The contents of System Information Block type 1 shall be as per the specific message content.
The contents of System Information Block type 5 / System Information Block type 5bis 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×168 |
|
TF1, bits |
1×360 |
Uplink TFCS:
|
TFCI |
RB7+SRB |
|
UL_TFC0 |
TF0 |
|
UL_TFC1 |
TF1 |
Downlink TFS:
|
RB7 |
SRBs |
||
|
TFS |
TF0, bits |
0x168 |
0x168 |
|
TF1, bits |
1×168 |
1×168 |
Downlink TFCS:
|
TFCI |
(RB7, SRB) |
|
DL_TFC0 |
(TF0, TF0) |
|
DL_TFC1 |
(TF1, TF0) |
|
DL_TFC2 |
(TF0, TF1) |
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 1 – 4 in the Expected sequence are followed by the steps 2 – 6 of the test procedure according to clause 14.1.1.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
SYSTEM INFORMATION |
||
|
2 |
The SS waits for about 10 s to make sure, that the UE is configured to receive CBS data |
|||
|
3 |
|
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, |
|
|
4 |
After having received the BMC CBS message the UE shall indicate the reception of CB Data 1 in a clear way. |
|||
Specific Message Contents
Use the default parameter values for the System Information Block type 1 with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions
|
Information Element |
Conditions |
Value/remark |
|
|
– CN domain identity |
|
PS |
|
|
– CHOICE CN Type |
|
GSM-MAP |
|
|
– CN domain specific NAS system information |
|
|
|
|
– GSM-MAP NAS system information |
|
05 00H |
|
|
– CN domain specific DRX cycle length coefficient |
|
9 |
|
|
– CN domain identity |
|
CS |
|
|
– CHOICE CN Type |
|
GSM-MAP |
|
|
– CN domain specific NAS system information |
|
|
|
|
– GSM-MAP NAS system information |
|
1E 01H |
|
|
– CN domain specific DRX cycle length coefficient |
|
9 |
|
14.4.4.5 Test Requirements
At step 4 in the Expected sequence, the UE shall store and decode a received activated CBS message.
At step e of the test procedure according to clause 14.1.1 the RRC Connection shall be established.
14.4.5 64.8kbps RB for MTCH with 80 ms TTI / MBMS Broadcast Service
14.4.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)
14.4.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.2.4.3.5.
14.4.5.3 Method of Test
Initial Condition
The UE is interested in the broadcast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).Related ICS/IXIT statements
MBMS Broadcast service application available on UE Yes / No
Test Procedure
See 14.1.5 for test procedure.
Downlink TFS:
|
TFI |
RB for MTCH (64.8 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 |
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 16 bits (size of 2, 7 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
|||
14.4.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.
14.4.5m 64.8kbps RB for MTCH with 80 ms TTI / MBMS Multicast Service
14.4.5m.1 Conformance Requirement
Same conformance requirement as in clause 14.4.5.1.
14.4.5m.2 Test purpose
Same test purpose as in clause 14.4.5.2.
14.4.5m.3 Method of Test
Initial Condition
The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Related ICS/IXIT statements
MBMS Multicast service application available on UE Yes / No
Test Procedure
Same test procedure as in clause 14.4.5.3
14.4.5m.4 Test Requirements
Same test requirements as in clause 14.4.5.4.
14.4.5n 64.8kbps RB for MTCH with 80 ms TTI / MBMS Multicast Service in MBSFN mode
14.4.5n.1 Conformance Requirement
Same conformance requirement as in clause 14.4.5.1.
14.4.5n.2 Test purpose
Same test purpose as in clause 14.4.5.2.
14.4.5n.3 Method of Test
Initial conditions
System Simulator:
– MBSFN carrier: 1 cell, Cell 31 (PLMN1). In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 and Default1 MCCH scheduling (No ongoing session) according to subclause 11.2 of TS 34.108.
– Unicast carrier : 1 cell, Cell 1 with default parameters.
User Equipment:
– On the unicast carrier cell the UE is in registered Idle Mode on PS (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domains, as specified in clause 7.2.2 of TS 34.108.
– The UE is in MBSFN Idle mode with one activated service as specified in clause 7.6.4 of TS 34.108. The UE has selected (i.e. it is included in MBMS_ACTIVATED_SERVICES variable) a national service for which a session will start on MBSFN Cell 31 (see TS 34.108 clause 11.2.4) during the test.
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode application available on UE Yes/No.
– Support of transmit and receive functions available on UE Yes/No.
– Support of MBSFN receive only function available on UE Yes/No.
Test Procedure
See 14.1.5m for test procedure.
Same Downlink TFS, Downlink TFCS and Sub-tests as in clause 14.4.5.3
14.4.5n.4 Test Requirements
Same test requirements as in clause 14.4.5.4.
14.4.6 129.6 kbps RB for MTCH with 80 ms TTI / MBMS Broadcast Service
14.4.6.1 Conformance Requirement
See 14.4.5.1.
14.4.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.2.4.3.6.
14.4.6.3 Method of Test
Initial Condition
The UE is interested in the broadcast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Related ICS/IXIT statements
MBMS Broadcast service application available on UE Yes / No
Test Procedure
See 14.1.5 for test procedure.
Downlink TFS:
|
TFI |
RB for MTCH (129.6 kbps 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 16 bits (size of 2, 7 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
|||
14.4.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.
14.4.6m 129.6 kbps RB for MTCH with 80 ms TTI / MBMS Multicast Service
14.4.6m.1 Conformance Requirement
Same conformance requirement as in clause 14.4.6.1.
14.4.6m.2 Test purpose
Same test purpose as in clause 14.4.6.2.
14.4.6m.3 Method of Test
Initial Condition
The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Related ICS/IXIT statements
MBMS Multicast service application available on UE Yes / No
Test Procedure
Same test procedure as in clause 14.4.6.3.
14.4.6m.4 Test Requirements
Same test requirements as in clause 14.4.6.4.
14.4.6n 129.6 kbps RB for MTCH with 80 ms TTI / MBMS Broadcast Service in MBSFN mode
14.4.6n.1 Conformance Requirement
Same conformance requirement as in clause 14.4.6.1.
14.4.6n.2 Test purpose
Same test purpose as in clause 14.4.6.2.
14.4.6n.3 Method of Test
Initial conditions
System Simulator:
– MBSFN carrier: 1 cell, Cell 31 (PLMN1). In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 and Default1 MCCH scheduling (No ongoing session) according to subclause 11.2 of TS 34.108.
– Unicast carrier : 1 cell, Cell 1 with default parameters.
User Equipment:
– On the unicast carrier cell the UE is in registered Idle Mode on PS (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domains, as specified in clause 7.2.2 of TS 34.108.
– The UE is in MBSFN Idle mode with one activated service as specified in clause 7.6.4 of TS 34.108. The UE has selected (i.e. it is included in MBMS_ACTIVATED_SERVICES variable) a national service for which a session will start on MBSFN Cell 31 (see TS 34.108 clause 11.2.4) during the test.
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode application available on UE Yes/No.
– Support of transmit and receive functions available on UE Yes/No.
– Support of MBSFN receive only function available on UE Yes/No.
Test Procedure
See 14.1.5m for test procedure.
Same Downlink TFS, Downlink TFCS and Sub-tests as in clause 14.4.6.3
14.4.6n.4 Test Requirements
Same test requirements as in clause 14.4.6.4.
14.4.7 259.2 kbps RB for MTCH with 40 ms TTI / MBMS Broadcast Service
14.4.7.1 Conformance Requirement
See 14.4.5.1.
14.4.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.2.4.3.7.
14.4.7.3 Method of Test
Initial Condition
The UE is interested in the broadcast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).Related ICS/IXIT statements
MBMS Broadcast service application available on UE Yes / No
Test Procedure
See 14.1.5 for test procedure.
Downlink TFS:
|
TFI |
RB for MTCH (259.2 kbps 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 (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 16 bits (size of 2, 7 bit length indicator and expansion bit), where N is the number of transport blocks in the transport format combination under test. |
|||
14.4.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.
14.4.7m 259.2 kbps RB for MTCH with 40 ms TTI / MBMS Multicast Service
14.4.7m.1 Conformance Requirement
Same conformance requirement as in clause 14.4.7.1.
14.4.7m.2 Test purpose
Same test purpose as in clause 14.4.7.2.
14.4.7m.3 Method of Test
Initial Condition
The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Related ICS/IXIT statements
MBMS Multicast service application available on UE Yes / No
Test Procedure
Same test procedure as in clause 14.4.7.3.
14.4.7m.4 Test Requirements
Same test requirements as in clause 14.4.7.4.
14.4.7n 259.2 kbps RB for MTCH with 40 ms TTI / MBMS Broadcast Service in MBSFN mode
14.4.7n.1 Conformance Requirement
Same conformance requirement as in clause 14.4.7.1.
14.4.7n.2 Test purpose
Same test purpose as in clause 14.4.7.2.
14.4.7n.3 Method of Test
Initial conditions
System Simulator:
– MBSFN carrier: 1 cell, Cell 31 (PLMN1). In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 and Default1 MCCH scheduling (No ongoing session) according to subclause 11.2 of TS 34.108.
– Unicast carrier : 1 cell, Cell 1 with default parameters.
User Equipment:
– On the unicast carrier cell the UE is in registered Idle Mode on PS (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domains, as specified in clause 7.2.2 of TS 34.108.
– The UE is in MBSFN Idle mode with one activated service as specified in clause 7.6.4 of TS 34.108. The UE has selected (i.e. it is included in MBMS_ACTIVATED_SERVICES variable) a national service for which a session will start on MBSFN Cell 31 (see TS 34.108 clause 11.2.4) during the test.
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode application available on UE Yes/No.
– Support of transmit and receive functions available on UE Yes/No.
– Support of MBSFN receive only function available on UE Yes/No.
Test Procedure
See 14.1.5m for test procedure.
Same Downlink TFS, Downlink TFCS and Sub-tests as in clause 14.4.7.3
14.4.7n.4 Test Requirements
Same test requirements as in clause 14.4.7.4.