7.1.1 Mapping between logical channels and transport channels
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
7.1.1.1 CCCH mapped to RACH/FACH / Invalid TCTF
7.1.1.1.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the RACH/FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.1.2 Conformance requirement
CCCH mapped to RACH/FACH:
– TCTF field is included in MAC header.
The following fields are defined for the MAC header:
– Target Channel Type Field
…
Coding of the Target Channel Type Field on FACH for FDD
TCTF |
Designation |
00 |
BCCH |
01000000 |
CCCH |
01000001-01111111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
10000000 |
CTCH |
10000001- 10111111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
11 |
DCCH or DTCH over FACH |
Coding of the Target Channel Type Field on FACH for TDD
TCTF |
Designation |
000 |
BCCH |
001 |
CCCH |
010 |
CTCH |
01100 |
DCCH or DTCH over FACH |
01101- 01111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
100 |
SHCCH |
101-111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.4.
7.1.1.1.3 Test purpose
1. To verify that the UE discards PDUs with reserved or incorrect values in the TCTF field.
2. To verify that the TCTF field is correctly applied when a CCCH is mapped to the RACH/FACH.
7.1.1.1.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters, Ciphering Off.
The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (FDD) , 6.11.5.4.4.3(1.28Mcps TDD) (Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH) with the following exceptions for the FACH:
FDD:
Higher layer |
RAB/signalling RB |
SRB#0 |
|
User of Radio Bearer |
Test |
||
RLC |
Logical channel type |
CCCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
168 |
||
Max data rate, bps |
33600 (alt. 50400) |
||
RLC header, bit |
0 |
||
MAC |
MAC header, bit |
0 (note) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
FACH |
|
TB sizes, bit |
168 |
||
TFS |
TF0, bits |
0 x 168 |
|
TF1, bits |
1 x 168 |
||
TF2, bits |
2 x 168 |
||
TF3, bits |
N/A (alt. 3 x 168) |
||
TTI, ms |
10 |
||
Coding type |
CC 1/2 |
||
CRC, bit |
16 |
||
Max number of bits/TTI before rate matching |
752 (alt. 1136) |
||
RM attribute |
200-240 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
TDD:
Higher layer |
RAB/signalling RB |
SRB#0 |
|
User of Radio Bearer |
Test |
||
RLC |
Logical channel type |
CCCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
171 |
||
Max data rate, bps |
33600 (alt. 50400) |
||
RLC header, bit |
0 |
||
MAC |
MAC header, bit |
0 (note) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
FACH |
|
TB sizes, bit |
171 |
||
TFS |
TF0, bits |
0 x 171 |
|
TF1, bits |
1 x 171 |
||
TF2, bits |
2 x 171 |
||
TF3, bits |
3 x 171 |
||
TF4, bits |
4x 171 |
||
TF5, bits |
N/A (alt. 5x 171) |
||
TF6, bits |
N/A (alt. 6 x 171) |
||
TTI, ms |
20 |
||
Coding type |
CC 1/2 |
||
CRC, bit |
16 |
||
Max number of bits/TTI before rate matching |
1528 (alt. 2292) |
||
RM attribute |
200-240 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
And using the configuration in TS 34.108 clause 6.10.2.4.3.3 (FDD), 6.11.5.4.4.3(1.28Mcps TDD) for the PCH.
The TFCS should be configured as specified in clause 6.10.2.4.3.3.1.4 (FDD), 6.11.5.4.4.3.1.4(1.28Mcps TDD).
User Equipment:
The UE shall operate under normal test conditions, Ciphering Off.
The Test-USIM shall be inserted.
The SS starts broadcasting the System Information as specified in TS 34.108 clause 6.1, using the configuration for the PRACH and SCCPCH (signalled in SYSTEM INFORMATION 5) as follows:
1. The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (FDD), 6.11.5.4.4.3(1.28Mcps TDD) (Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH).
2. The PRACH is configured as specified in TS 34.108 clause 6.10.2.4.4.1(FDD), 6.11.5.4.5.2(TDD).
The SS follows the procedure in TS 34.108 clause 7.2.2.1 (CS UE) or 7.2.2.2 (PS UE) so that the UE shall be in idle mode and registered.
Test procedure
a) The SS pages the UE.
b) The SS waits for the first RRC CONNECTION REQUEST message to arrive on the PRACH/CCCH.
c) The SS responds with an RRC CONNECTION SETUP message (specified in TS 34.108 clause 9: Contents of RRC CONNECTION SETUP message: UM (Transition to CELL_FACH)(FDD), or UM (Transition to CELL_FACH) (1.28 Mcps TDD option). In this case the SS will transmit the message in 152 bit for FDD and 160 bits for TDD (note) segments, with a valid UM RLC header and with the MAC header set as follows:
FDD:
Field |
Value |
TCTF |
01000001’B |
TDD:
Field |
Value |
TCTF |
101’B |
d) The SS waits for retransmission of the RRC CONNECTION REQUEST on the PRACH/CCCH due to expiry of timer T300. If no retransmission is received steps a) and b) are repeated.
e) The SS repeats steps c) and d), with the TCTF field set as follows:
FDD:
Iteration |
TCTF Value |
2 |
(void) |
3 |
10000000’B |
4 |
10000001’B |
5 |
(void) |
TDD:
Iteration |
TCTF Value |
2 |
010’B |
3 |
01111’B |
4 |
(void)’ |
5 |
(void) |
6 |
(void) |
f) The SS repeats steps c) and d), with the TCTF field set as to 01000000’B(FDD), 001’B(TDD).
Expected sequence
FDD:
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
PAGING TYPE 1 |
||
2 |
|
RRC CONNECTION REQUEST |
||
3 |
– |
Void |
||
4 |
– |
Void |
||
5 |
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 1)) |
Sent with incorrect TCTF = 0100 0001’B |
|
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 2)) |
Sent with incorrect TCTF = 0100 0001’B |
||
… |
||||
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT n)) |
Sent with incorrect TCTF = 0100 0001’B |
||
6 |
|
RRC CONNECTION REQUEST |
If this message is not received then the PAGING TYPE 1 message as in step 1 shall be sent again. |
|
7 |
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 1)) |
Sent with incorrect TCTF = 1000 0000’B |
|
|
MAC PDU(TCTF, UE-ID, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 2)) |
Sent with incorrect TCTF = 1000 0000’B |
||
… |
||||
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT n)) |
Sent with incorrect TCTF = 1000 0000’B |
||
8 |
|
RRC CONNECTION REQUEST |
If this message is not received then the PAGING TYPE 1 message as in step 1 shall be sent again. |
|
9 |
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 1)) |
Sent with incorrect TCTF = 1000 0001’B |
|
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 2)) |
Sent with incorrect TCTF = 1000 0001’B |
||
… |
||||
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT n)) |
Sent with incorrect TCTF = 1000 0001’B |
||
10 |
|
RRC CONNECTION REQUEST |
If this message is not received then the PAGING TYPE 1 message as in step 1 shall be sent again. |
|
11 |
– |
Void |
||
12 |
– |
Void |
||
13 |
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 1)) |
Sent with correct TCTF = 0100 0000’B |
|
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 2)) |
Sent with correct TCTF = 0100 0000’B |
||
… |
||||
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT n)) |
Sent with correct TCTF = 0100 0000’B |
||
14 |
|
RRC CONNECTION SETUP COMPLETE |
TCTF Field is recognised as correct for the DCCH |
TDD:
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
PAGING TYPE 1 |
||
2 |
|
RRC CONNECTION REQUEST |
||
3 |
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 1)) |
Sent with incorrect TCTF = 101’B |
|
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 2)) |
Sent with incorrect TCTF =101’B |
||
… |
||||
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT n)) |
Sent with incorrect TCTF = 101’B |
||
4 |
|
RRC CONNECTION REQUEST |
||
5 |
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 1)) |
Sent with incorrect TCTF = 010’B |
|
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 2)) |
Sent with incorrect TCTF = 010’B |
||
… |
||||
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT n)) |
Sent with incorrect TCTF = 010’B |
||
6 |
|
RRC CONNECTION REQUEST |
||
7 |
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 1)) |
Sent with incorrect TCTF = 01111’B |
|
|
MAC PDU(TCTF, UE-ID, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 2)) |
Sent with incorrect TCTF =01111’B |
||
… |
||||
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT n)) |
Sent with incorrect TCTF = 01111’B |
||
8 |
|
RRC CONNECTION REQUEST |
||
9 |
– |
void |
||
– |
void |
|||
… |
||||
– |
void |
|||
10 |
– |
void |
||
11 |
– |
void |
||
– |
void |
|||
… |
||||
– |
void |
|||
12 |
– |
void |
||
13 |
– |
void |
||
– |
void |
|||
… |
||||
– |
void |
|||
14 |
– |
void |
||
15 |
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 1)) |
Sent with correct TCTF = 001’B |
|
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT 2)) |
Sent with correct TCTF = 001’B |
||
… |
||||
|
MAC PDU(TCTF, RLC UM PDU(SN, RRC CONNECTION SETUP SEGMENT n)) |
Sent with correct TCTF = 001’B |
||
16 |
|
RRC CONNECTION SETUP COMPLETE |
TCTF Field is recognised as correct for the CCCH |
Specific Message Contents
None.
7.1.1.1.5 Test Requirement
On the first iteration, and on each iteration in step e) the UE should not recognise the RRC CONNECTION SETUP message and therefore should either retransmit the RRC CONNECTION REQUEST after each expiry of T300 (the UE should send up to N300=3 RRC CONNECTION REQUESTs before abandoning the procedure) or not respond (if N300 RRC CONNECTION REQUESTs have already been sent).
On the final iteration the UE should respond with an RRC CONNECTION SETUP COMPLETE message.
7.1.1.2 DTCH or DCCH mapped to RACH/FACH / Invalid TCTF
7.1.1.2.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the RACH/FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.2.2 Conformance requirement
DTCH or DCCH mapped to RACH/FACH:
TCTF field, C/T field, UE-Id type field and UE-Id are included in the MAC header.
The following fields are defined for the MAC header:
– Target Channel Type Field
…
Coding of the Target Channel Type Field on FACH for FDD
TCTF |
Designation |
00 |
BCCH |
01000000 |
CCCH |
01000001-01111111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
10000000 |
CTCH |
10000001- 10111111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
11 |
DCCH or DTCH over FACH |
Coding of the Target Channel Type Field on FACH for TDD
TCTF |
Designation |
000 |
BCCH |
001 |
CCCH |
010 |
CTCH |
01100 |
DCCH or DTCH over FACH |
01101- 01111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
100 |
SHCCH |
101-111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 c).
7.1.1.2.3 Test purpose
1. To verify that the UE discards PDUs with reserved or incorrect values in the TCTF field.
2. To verify that the TCTF field, C/T field, UE-Id type and UE-Id field are correctly applied when a DTCH or DCCH is mapped to the RACH/FACH.
7.1.1.2.4 Method of test
Initial conditions
System Simulator:
1 cell, default parameters, Ciphering Off.
The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3(FDD) and 6.11.5.4.4.3(1.28Mcps TDD) (Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH) with the following exceptions for the FACH:
FDD:
Higher layer |
RAB/signalling RB |
RB#3 (SRB#3) |
|
User of Radio Bearer |
Test |
||
RLC |
Logical channel type |
DCCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
168 |
||
Max data rate, bps |
33600 (alt. 50400) |
||
RLC header, bit |
0 |
||
MAC |
MAC header, bit |
0 (note) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
FACH |
|
TB sizes, bit |
168 |
||
TFS |
TF0, bits |
0 x 168 |
|
TF1, bits |
1 x 168 |
||
TF2, bits |
2 x 168 |
||
TF3, bits |
N/A (alt. 3 x 168) |
||
TTI, ms |
10 |
||
Coding type |
CC ½ |
||
CRC, bit |
16 |
||
Max number of bits/TTI before rate matching |
752 (alt. 1136) |
||
RM attribute |
200-240 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
TDD:
Higher layer |
RAB/signalling RB |
RB#3 (SRB#3) |
|
User of Radio Bearer |
Test |
||
RLC |
Logical channel type |
DCCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
171 |
||
Max data rate, bps |
33600 (alt. 50400) |
||
RLC header, bit |
0 |
||
MAC |
MAC header, bit |
0 (note) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
FACH |
|
TB sizes, bit |
171 |
||
TFS |
TF0, bits |
0 x 171 |
|
TF1, bits |
1 x 171 |
||
TF2, bits |
2 x 171 |
||
TF3, bits |
3 x 171 |
||
TF4, bits |
4x 171 |
||
TF5, bits |
N/A (alt. 5x 171) |
||
TF6, bits |
N/A (alt. 6 x 171) |
||
TTI, ms |
20 |
||
Coding type |
CC 1/2 |
||
CRC, bit |
16 |
||
Max number of bits/TTI before rate matching |
1528 (alt. 2292) |
||
RM attribute |
200-240 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
and using the configuration in TS 34.108 clause 6.10.2.4.3.3 (FDD), 6.11.5.4.4.3(1.28Mcps TDD) for the PCH.
The TFCS should be configured as specified in clause 6.10.2.4.3.3.1.4 (FDD), 6.11.5.4.4.3.1.4(1.28Mcps TDD).
User Equipment:
The UE shall operate under normal test conditions, Ciphering Off.
The Test-USIM shall be inserted.
The SS starts broadcasting the System Information as specified in TS 34.108 clause 6.1, using the configuration for the PRACH and SCCPCH (signalled in SYSTEM INFORMATION 5) as follows:
1. The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (FDD), 6.11.5.4.4.3(1.28Mcps TDD) (Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH).
2. The PRACH is configured as specified in TS 34.108 clause 6.10.2.4.4.1 (FDD), 6.11.5.4.5.2(1.28Mcps TDD).
The SS follows the procedure in TS 34.108 clause 7.4.2.1.1 (Mobile Terminated for CS) so that the UE shall be in state BGP 6-2 (CS-CELL_FACH_INITIAL) or clause 7.4.2.2.1 (Mobile Terminated for PS) so that the UE shall be in state BGP 6-4 PS-CELL_FACH_INITIAL.
Test procedure
a) The SS receives the PAGING RESPONSE or SERVICE REQUEST (depending on domain) message from the UE and checks the TCTF field.
b) The SS transmits MAC PDUs containing RLC AM PDUs containing a DIRECT TRANSFER message containing an AUTHENTICATION REQUEST message.
1. Dummy octet string for NAS Message, of size sufficient enough to fit in one RLC PDU of 144 bits, including the correct RLC AM header.
2. The IE CN Domain Identity is Set to PS Domain ( if UE initial state is 6-2) or CS Domain (if UE initial state is 6-4) (no signalling connection for this domain exists).
3. The polling bit in RLC header is set for transmission of RLC STATUS PDU.
The MAC header shall be set as follows:
Field |
Value |
TCTF |
01000001’B(FDD), 101(TDD) |
UE ID Type |
C-RNTI |
UE ID |
As set in RRC CONNECTION SETUP message. |
C/T |
Logical Channel ID for SRB #3 (AM-DCCH NAS High Priority) |
Where a TCTF size of 8-bits is used, 6-bits from the RLC payload shall be discarded.
c) The SS checks that UE shall neither transmit RRC Status message on SRB2 nor RLC Status PDU on SRB3.
d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct TCTF of 11’B for FDD, 01100’B for TDD. The sequence numbers in the RLC headers shall be identical with those sent in b).
e) SS Receives RLC Status PDU on SRB #3 acknowledging the receipt of the above RLC PDU.
f) The SS receives a RRC STATUS message on the uplink DCCH using AM RLC on SRB # 2.
g) The SS repeats steps b), c), d) e) and f), with the TCTF field set as follows in step b):
FDD:
Iteration |
TCTF Value |
2 |
01111111’B |
3 |
10000000’B |
4 |
10000001’B |
5 |
10111111’B |
TDD:
Iteration |
TCTF Value |
2 |
110’B |
3 |
010’B |
4 |
01111’B |
5 |
01101’B |
Expected sequence
FDD:
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
1 |
|
PAGING RESPONSE/SERVICE REQUEST |
Check TCTF |
|
2 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with incorrect TCTF = 01000001’B, 01111111’B, 10000000’B, 10000001’B, or 10111111’B |
|
2a |
wait for T = 3 s |
SS checks that UE shall neither transmit RRC-Status message on SRB 2 nor RLC Status PDU on SRB 3 See note 1 below |
||
3 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with correct TCTF = 11’B |
|
4 |
|
RLC-STATUS-PDU |
ACK PDUs with SN = x and TCTF Field is recognised as correct for the DCCH. See note 2 below |
|
5 |
|
RRC Status message |
||
NOTE 1: UE will Transmit Signalling Connection Release Indication on expiry of MM Timer T3240 or GMM Timer T3317. NOTE 2: RRC Status message may be received before RLC Status PDU. |
TDD:
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
1 |
|
PAGING RESPONSE |
Check TCTF |
|
2 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with incorrect TCTF = 101’B, 110’B, 010’B, 01111’B, or 01101’B |
|
2 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with incorrect TCTF = 010101’B, 110’B, 010’B, 01111’B, or 01101’B |
|
2a |
wait for T = 3 s |
SS checks that UE shall neither transmit RRC-Status message on SRB 2 nor RLC Status PDU on SRB 3 See note 1 below |
||
3 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with correct TCTF = 01100’B |
|
4 |
|
RLC-STATUS-PDU |
ACK PDUs with SN = x and TCTF Field is recognised as correct for the DCCH. See note 2 below |
|
5 |
|
RRC Status message |
||
NOTE 1: UE will Transmit Signalling Connection Release Indication on expiry of MM Timer T3240 or GMM Timer T3317. NOTE 2: RRC Status message may be received before RLC Status PDU. |
Steps 2 – 5 of above expected sequence are repeated for iterations 2 to 5. Note: For iteration k the SN in steps 2 and 4 starts with x + (k –1).
Specific Message Contents
None
7.1.1.2.5 Test Requirement
In step a) the TCTF field should have the value ‘01’B. Note that this may be implied from receipt of the PAGING RESPONSE/SERVICE REQUEST message correctly by the SS test script.
During the test the SS shall request an RLC status report with every transmitted PDU by setting of the Polling Bit. The UE shall not send any STATUS PDUs indicating missing PDUs.
At the end of each iteration (steps 4 and 5 of expected sequence) the SS shall receive an RRC Status message on SRB # 2, and RLC Status PDU on SRB # 3 with TCTF field set to value ’01’ B for FDD, ‘0100’ B for TDD.
7.1.1.3 DTCH or DCCH mapped to RACH/FACH / Invalid C/T Field
7.1.1.3.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the RACH/FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.3.2 Conformance requirement
DTCH or DCCH mapped to RACH/FACH:
TCTF field, C/T field, UE-Id type field and UE-Id are included in the MAC header.
The following fields are defined for the MAC header:
– C/T field
The C/T field provides identification of the logical channel instance when multiple logical channels are carried on the same transport channel…
Structure of the C/T field
C/T field |
Designation |
0000 |
Logical channel 1 |
0001 |
Logical channel 2 |
… |
… |
1110 |
Logical channel 15 |
1111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 c).
7.1.1.3.3 Test purpose
1. To verify that the UE discards PDUs with reserved or incorrect values in C/T field.
2. To verify that the TCTF field, C/T field, UE-Id type and UE-Id field are correctly applied when a DTCH or DCCH is mapped to the RACH/FACH.
7.1.1.3.4 Method of test
Initial conditions
System Simulator:
See clause 7.1.1.2.4.
User Equipment:
See clause 7.1.1.2.4.
Test procedure
a) The SS receives the PAGING RESPONSE or SERVICE REQUEST (depending on domain) message from the UE and checks the C/T field.
b) The SS transmits MAC PDUs containing RLC AM PDUs containing a DIRECT TRANSFER message containing.
1. Dummy octet string for NAS Message, of size sufficient enough to fit in one RLC PDU of 144 bits, including the correct RLC AM header.
2. The IE CN Domain Identity is Set to PS Domain (no signalling connection for this domain exists).
3. The polling bit in RLC header is set for Transmission of RLC STATUS PDU.
The MAC header shall be set as follows:
Field |
Value |
TCTF |
11’B |
UE ID Type |
C-RNTI |
UE ID |
As set in RRC CONNECTION SETUP message. |
C/T |
0111’B |
c) The SS checks that UE shall neither transmit RRC Status message on SRB2 nor RLC Status PDU on.
d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct C/T value for AM-DCCH NAS High Priority of 0010’B. The sequence numbers in the RLC headers shall be identical with those sent in b).
e) SS receives RLC Status PDU on SRB #3 acknowledging the receipt of the above RLC PDU.
f) The SS receives a RRC STATUS message on the uplink DCCH using AM RLC on SRB # 2.
g) The SS repeats steps b), c), d), e) and f), with the C/T field set as follows:
Iteration |
C/T Value |
2 |
1111’B |
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
PAGING RESPONSE/SERVICE REQUEST |
Check C/T field |
|
2 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with incorrect C/T = 0111’B, or 1111’B. |
|
2a |
wait for T = 5 s |
SS checks that UE shall neither transmit RRC-Status message on SRB 2 nor RLC Status PDU on SRB 3. See note 1 below. |
||
3 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with correct C/T = 0010’B |
|
4 |
|
RLC-STATUS-PDU |
ACK PDUs with SN = x C/T Field is recognised as correct for the DCCH. See note 2 below. |
|
5 |
|
RRC Status message |
||
NOTE 1: UE will Transmit Signalling Connection Release Indication on expiry of MM Timer T3240 or GMM Timer T3317. NOTE 2: RRC Status message may be received before RLC Status PDU. |
Steps 2 to 5 of the expected sequence are repeated for iteration 2. Note: For iteration k the SN in steps 2 and 4 starts with x + (k –1).
Specific Message Contents
None
7.1.1.3.5 Test Requirement
In step a) the C/T field should be set to the Logical Channel ID for SRB #3 (0010’B). Note that this may be implied from receipt of the PAGING RESPONSE/SERVICE REQUEST message correctly by the SS test script.
During the test the SS shall request RLC status report with every transmitted PDU by setting of the Polling Bit. The UE shall not send any STATUS PDUs indicating missing PDUs.
At the end of each iteration (steps 4 and 5 of expected sequence) the SS shall receive a RLC Status PDU on SRB # 3, with C/T field set to value ‘0010’B and RRC Status message on SRB # 2.
7.1.1.4 DTCH or DCCH mapped to RACH/FACH / Invalid UE ID Type Field
7.1.1.4.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the RACH/FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.4.2 Conformance requirement
DTCH or DCCH mapped to RACH/FACH:
TCTF field, C/T field, UE-Id type field and UE-Id are included in the MAC header.
The following fields are defined for the MAC header:
– UE-Id Type
The UE-Id Type field is needed to ensure correct decoding of the UE-Id field in MAC Headers.
Table 9.2.1.7: UE-Id Type field definition
UE-Id Type field 2 bits |
UE-Id Type |
00 |
U-RNTI |
01 |
C-RNTI |
10 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
11 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 c).
7.1.1.4.3 Test purpose
1. To verify that the UE discards PDUs with reserved values in UE-Id type field.
2. To verify that the TCTF field, C/T field, UE-Id type and UE-Id field are correctly applied when a DTCH or DCCH is mapped to the RACH/FACH.
7.1.1.4.4 Method of test
Initial conditions
System Simulator:
See clause 7.1.1.2.4.
User Equipment:
See clause 7.1.1.2.4.
Test procedure
a) The SS receives the PAGING RESPONSE or SERVICE REQUEST (depending on domain) message from the UE and checks the UE-Id Type field.
b) The SS transmits MAC PDUs containing RLC AM PDUs containing a DIRECT TRANSFER message containing.
1. Dummy octet string for NAS Message, of size sufficient enough to fit in one RLC PDU of 144 bits, including the correct RLC AM header.
2. The IE CN Domain Identity is Set to PS Domain (no signalling connection for this domain exists)
3. The polling bit in RLC header is set for transmission of RLC STATUS PDU.
The MAC header shall be set as follows:
Field |
Value |
TCTF |
11’B |
UE ID Type |
10’B |
UE ID |
As set in RRC CONNECTION SETUP message. |
C/T |
Logical Channel ID for SRB #3 (AM-DCCH NAS High Priority): 0010’B |
c) The SS checks that UE shall neither transmit RRC Status message on SRB2 nor RLC Status PDU on SRB3.
d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct UE-Id type value for C-RNTI of 01’B. The sequence numbers in the RLC headers shall be identical with those sent in b).
e) SS Receives RLC Status PDU on SRB #3 acknowledging the receipt of the above RLC PDU.
f) The SS receives a RRC STATUS message on the uplink DCCH using AM RLC on SRB # 2
g) The SS repeats steps b), c), d), e) and f), with the UE-Id type field set as follows in step b):
Iteration |
UE-Id type Value |
2 |
11’B |
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
PAGING RESPONSE/SERVICE REQUEST |
Check UE-Id Type |
|
2 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with incorrect UE-Id Type = 10’B, or 11’B. |
|
2a |
wait for T = 5 s |
SS checks that UE shall neither transmit RRC-Status message on SRB 2 nor RLC Status PDU on SRB 3. See note 1 below. |
||
3 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with correct UE-Id Type = 01’B |
|
4 |
|
RLC-STATUS-PDU |
ACK PDU with SN = x UE-Id is recognised as correct for the UE. See note 2 below. |
|
5 |
|
RRC Status message |
RRC |
|
NOTE 1: UE will Transmit Signalling Connection Release Indication on expiry of MM Timer T3240 or GMM Timer T3317. NOTE 2: RRC Status message may be received before RLC Status PDU. |
Steps 2 to 5 of the expected sequence are repeated for iteration 2. Note: For iteration k the SN in step 2 and 4 starts with x + (k –1).
Specific Message Contents
None
7.1.1.4.5 Test Requirement
In step a) the UE-Id Type field should be set to 01’B. Note that this may be implied from receipt of the PAGING RESPONSE/SERVICE REQUEST message correctly by the SS test script.
During the test the SS request an RLC status report with every transmitted PDU by setting of the Polling Bit. The UE shall not send any STATUS PDUs indicating missing PDUs.
At the end of each iteration (steps 4 and 5 of expected sequence) the SS shall receive a RLC Status PDU on SRB # 3, with UE Id type correctly set to ’01’B and RRC Status message on SRB # 2.
7.1.1.5 DTCH or DCCH mapped to RACH/FACH / Incorrect UE ID
7.1.1.5.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the RACH/FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.5.2 Conformance requirement
DTCH or DCCH mapped to RACH/FACH:
TCTF field, C/T field, UE-Id type field and UE-Id are included in the MAC header.
The following fields are defined for the MAC header:
– UE-Id
The UE-Id field provides an identifier of the UE on common transport channels…
Lengths of UE Id field
UE Id type |
Length of UE Id field |
U-RNTI |
32 bits |
C-RNTI |
16 bits |
Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 c).
7.1.1.5.3 Test purpose
1. To verify that the UE ignores PDUs with UE-Ids that do not match the Id allocated to it.
2. To verify that the TCTF field, C/T field, UE-Id type and UE-Id field are correctly applied when a DTCH or DCCH is mapped to the RACH/FACH.
7.1.1.5.4 Method of test
Initial conditions
System Simulator:
See clause 7.1.1.2.4.
User Equipment:
See clause 7.1.1.2.4.
Test procedure
a) The SS receives the PAGING RESPONSE or SERVICE REQUEST (depending on domain) message from the UE and checks the UE-Id field.
b) The SS transmits MAC PDUs containing RLC AM PDUs containing a DIRECT TRANSFER message containing.
1. Dummy Octet String for NAS Message, of size sufficient enough to fit in one RLC PDU of 144 bits, including the correct RLC AM header.
2. The IE CN Domain Identity is Sset to PS Domain (no signalling connection for this domain exists)
3. The polling bit in RLC header is set for transmission of RLC STATUS PDU.
The MAC header shall be set as follows:
Field |
Value |
TCTF |
11’B |
UE ID Type |
C-RNTI |
UE ID |
Address allocated in RRC CONNECTION SETUP message + 1. |
C/T |
Logical Channel ID for SRB #3 (AM-DCCH NAS High Priority): 0010’B |
c) The SS checks that UE shall neither transmit RRC Status message on SRB2 nor RLC Status PDU on SRB3.
d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct UE-Id value of the address allocated in the RRC CONNECTION SETUP message. The sequence numbers in the RLC headers shall be identical with those sent in b).
e) SS Receives RLC Status PDU on SRB #3 acknowledging the receipt of the above RLC PDU
f) The SS receives a RRC STATUS message on the uplink DCCH using AM RLC on SRB # 2.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
PAGING RESPONSE/SERVICE REQUEST |
Check UE-Id |
|
2 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with incorrect UE-Id = C-RNTI+1 |
|
2a |
wait for T = 10 s |
SS checks that UE shall neither transmit RRC-Status message on SRB 2 nor RLC Status PDU on SRB 3. See note 1 below. |
||
3 |
|
MAC PDU(TCTF, UE-ID, C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with correct UE-Id = C-RNTI |
|
4 |
|
RLC-STATUS-PDU |
ACK PDUs with SN = x UE-Id is recognised as correct for the UE. See note 2 below. |
|
5 |
|
RRC Status message |
||
NOTE 1: UE will Transmit Signalling Connection Release Indication on expiry of MM Timer T3240 or GMM Timer T3317. NOTE 2: RRC Status message may be received before RLC Status PDU. |
Specific Message Contents
None
7.1.1.5.5 Test Requirement
In step a) the UE-Id field should be set to the C-RNTI allocated in the RRC CONNECTION SETUP message. Note that this may be implied from receipt of the PAGING RESPONSE/SERVICE REQUEST message correctly by the SS test script.
During the test the SS shall request an RLC status report with every transmitted PDU by setting of the Polling Bit. The UE shall not send any STATUS PDUs indicating missing PDUs.
At the end of the expected sequence (steps 4 and 5) the SS shall receive RLC Status PDU on SRB # 3 with correct C-RNTI and RRC Status message on SRB # 2.
7.1.1.6 DTCH or DCCH mapped to DSCH or USCH
7.1.1.6.1 Definition and applicability
Applicable for if mode TDD only or FDD only is supported. In FDD applicable only to R99 and Rel-4 UEs.
7.1.1.6.2 Conformance requirement
The TCTF field is included in the MAC header for TDD only. The UE-Id type and UE-Id are included in the MAC header for FDD only. The C/T field is included if multiplexing on MAC is applied.
Reference(s)
TS 25.321 clause 9.2.1.1.
7.1.1.6.3 Test purpose
To verify when DTCH or DCCH is mapped to DSCH or USCH, the TCTF field is applied for TDD only, the UE-Id type and UE-Id are applied for FDD only. If multiplexing on MAC is applied, C/T field is included, otherwise, the C/T field is not included in the MAC header.
7.1.1.6.4 Method of test
Initial conditions
System Simulator:
– 1 cell, default parameters. Ciphering Off.
User Equipment:
– The UE shall operate under normal test conditions, Ciphering Off.
– The Test-USIM shall be inserted.
The UE is in Connected mode and a connection is established as described in the TS 34.123-1, 7.3 PDCP testing, clause "Setup a UE originated PS session using IP Header compression in AM RLC (using Loop back test mode 1).
Related ICS/IXIT Statement(s)
TBD
Foreseen Final State of the UE
Test procedure
a) The SS sends a certain data block to the UE.
b) After having received the data block via configured mapped channels, the UE forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its MAC configuration to the SS.
c) The SS receives the returned data block and checks its MAC header whether the TCTF is applied for TDD only, or the UE-Id type and UE-Id are applied for FDD only, and the C/T field shall not be applied.
d) The SS configures the RLC.
e) The SS starts a Radio Bearer Reconfiguration procedure to be connected in RLC transparent mode and configures the Radio Bearer for multiplexing.
f) The SS sends a certain data block to the UE.
g) After having received the data block via configured mapped channels, the UE forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its MAC configuration to the SS.
h) The SS receives the returned data block and checks its MAC header whether the TCTF is applied for TDD only, or the UE-Id type and UE-Id are applied for FDD only and the C/T field is applied.
i) The SS reconfigures its RLC mode to be in AM.
Expected sequence
Step |
Direction |
Message |
Comments |
|
---|---|---|---|---|
UE |
SS |
|||
1 |
|
DATA BLOCK |
The SS sends one data block with MAC header, sets TCTF as "DCCH or DTCH over USCH or DSCH" for TDD only, or sets UE-Id type as "C-RNTI", and UE-Id as C-RNTI of UE for FDD only. |
|
2 |
|
LOOP BACK DATA BLOCK |
SS receives the loop back data block from the Uplink RB and checks the MAC header. |
|
3 |
SS sends CMAC_MAC_HEADER_REQ with enable_mac_header and CRLC_CONFIG_REQ with RLC mode as "AM mode". |
|||
4 |
|
RADIO BEARER RECONFIGURE |
Reconfigures the downlink and uplink radio bearer as multiplexing . |
|
5 |
|
RADIO BEARER RECONFIGURATION COMPLETE |
||
6 |
SS sends CMAC_MAC_HEADER_REQ with disable_mac_header and CRLC_CONFIG_REQ with RLC mode as "Transparent mode". |
|||
7 |
|
DATA BLOCK |
The SS sends one data block with MAC header, sets TCTF as "DCCH or DTCH over USCH or DSCH" for TDD only, or sets UE-Id type as "C-RNTI", and UE-Id as C-RNTI of UE for FDD only and C/T field is included. |
|
8 |
|
LOOP BACK DATA BLOCK |
SS receives the loop back data block from the Uplink RB and checks the MAC header. |
|
9 |
SS sends CMAC_MAC_HEADER_REQ with enable_mac_header and CRLC_CONFIG_REQ with RLC mode as "AM mode". |
Specific Message Contents
RADIO BEARER SET UP:
Information Element |
Value/remark |
RLC info – RLC mode RB mapping info -Downlink – Number of logical channels – Downlink transport channel type -Uplink – Number of logical channels – Uplink transport channel type |
AM RLC 1 DSCH 1 USCH |
RADIO BEARER RECONFIGURE:
Information Element |
Value/remark |
RLC info – RLC mode RB mapping info -Downlink – Number of logical channels – Downlink transport channel type -Uplink – Number of logical channels – Uplink transport channel type |
AM RLC 2 DSCH 2 USCH |
7.1.1.6.5 Test requirements
TCTF field in the MAC header of loop back data block is "DTCH or DCCH over DSCH or USCH" for TDD only. The UE-ID type and UE-Id are applied in the MAC header for FDD only. If multiplexing on MAC is applied, C/T field is included, otherwise, C/T field is not included.
7.1.1.7 DTCH or DCCH mapped to CPCH
7.1.1.7.1 Definition and applicability
All UEs which support CPCH.
7.1.1.7.2 Conformance requirement
UE-Id type field and UE-Id are included in the MAC header. The C/T field is included in the MAC header if multiplexing on MAC is applied.
Reference(s)
TS 25.321 clauses 9.2.1.1 and 11.3.
TS 25.214 clause 6.2.
TS 25.211 clause 5.3.3.11.
7.1.1.7.3 Test purpose
To verify when DTCH or DCCH mapped to CPCH, UE-Id type field and UE-Id are included in the MAC header. if multiplexing on MAC is applied, the C/T field is included in the MAC header, otherwise, C/T field is not included.
7.1.1.7.4 Method of test
Initial conditions
System Simulator:
– 1 cell, default parameters, Ciphering Off.
User Equipment:
– The UE shall operate under normal test conditions, Ciphering Off.
– The Test-USIM shall be inserted.
The UE is in Connected mode and a connection is established as described in the TS 34.123-1, 7.3 PDCP testing, clause "Setup a UE originated PS session using IP Header compression in UM RLC (using Loop back test mode 1).
Related ICS/IXIT Statement(s)
TBD
Foreseen Final State of the UE
Test procedure
a) The SS sends SIBs 7, 8, and 9, sends CSICH information and waits 30 s.
b) The SS reconfigures its RLC mode to be in transparent mode RLC. Afterwards its sends a certain data block to the UE.
c) After having received the data block via configured mapped channels, the UE forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its MAC configuration to the SS.
d) The SS receives the returned data block and checks its MAC header, whether a UE-Id type and a UE-Id are included.
e) The SS reconfigures its RLC mode to be in AM.
f) The SS starts a Radio Bearer Reconfiguration procedure to be connected in RLC transparent mode and configures the Radio Bearer for multiplexing.
g) The SS sends the next data block via its MAC entity with MAC header, including the UE-Id type as "C-RNTI" and UE-Id as C-RNTI of the UE.C/T field.
h) After having received the data block via configured mapped channels, the UE forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its MAC configuration to the SS.
i) The SS receives the returned data block and checks its MAC header, whether UE-Id type, UE-Id field are included and C/T field is applied or not.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
SIBs 7, 8 and 9 and CSICH information |
Containing default settings for CPCH. |
|
2 |
|
DATA BLOCK |
The SS sends one data block with MAC header, sets UE-Id type as "C-RNTI", and UE-Id as C-RNTI of UE. |
|
3 |
|
LOOP BACK DATA BLOCK |
SS receives the loop back data block from the Uplink RB and checks the MAC header. |
|
4 |
SS sends CMAC_MAC_HEADER_REQ with enable_mac_header and CRLC_CONFIG_REQ with RLC mode as "AM mode". |
|||
5 |
|
RADIO BEARER RECONFIGURE |
Reconfigures the downlink and uplink radio bearer as multiplexing. |
|
6 |
|
RADIO BEARER RECONFIGURATION COMPLETE |
||
7 |
SS sends CMAC_MAC_HEADER_REQ with disable_mac_header and CRLC_CONFIG_REQ with RLC mode as "Transparent mode". |
|||
8 |
|
DATA BLOCK |
The SS sends one data block with MAC header, sets UE-Id type as "C-RNTI", and UE-Id as C-RNTI of UE. |
|
9 |
|
LOOP BACK DATA BLOCK |
SS receives the loop back data block from the Uplink RB and checks the MAC header. |
|
10 |
SS sends CMAC_MAC_HEADER_REQ with enable_mac_header and CRLC_CONFIG_REQ with RLC mode as "AM mode". |
Specific Message Contents
RADIO BEARER SET UP:
Information Element |
Value/remark |
RLC info – RLC mode RB mapping info -Downlink – Number of logical channels – Downlink transport channel type -Uplink – Number of logical channels – Uplink transport channel type |
AM RLC 1 FACH 1 CPCH |
RADIO BEARER RECONFIGURE:
Information Element |
Value/remark |
RLC info – RLC mode RB mapping info -Downlink – Number of logical channels – Downlink transport channel type -Uplink – Number of logical channels – Uplink transport channel type |
AM RLC 2 FACH 2 CPCH |
PRACH persistence level info in System Information Block type 7
Information Element |
Value/Remark |
PRACHs listed in SIB 5 – Dynamic persistence level PRACHs listed in SIB 6 – Dynamic persistence level |
All set to 8, which maps to minimum persistence value, no access allowed All set to 8, which maps to minimum persistence value, no access allowed |
CPCH parameters in System Information Block type 8
Information Element |
Value/Remark |
Back off control parameters
Power Control Algorithm TPC step size DL DPCCH BER |
15 15 15 15 15 15 0 algorithm 1 1 15 |
CPCH set info in System Information Block type 8
Information Element |
Value/Remark |
AP preamble scrambling code AP-AICH channelisation code CD preamble scrambling code CD/CA-ICH channelisation code DeltaPp-m UL DPCCH Slot Format N_start_message CPCH status indication mode PCPCH Channel #1 info
– Minimum spreading factor – NF_max
PCPCH Channel #2 info
– Minimum spreading factor – NF_max
|
16 15 17 16 0 1 8 PA mode 18 15 8 64 64 15 19 14 8 64 64 14 |
PCPCH persistence level info in System Information Block type 9
Information Element |
Value/Remark |
CPCH set persistence levels – PCPCH persistence level |
Both set to 1, immediate access allowed |
CSICH Information broadcast by SS PHY
Information Element |
Value/Remark |
PCPCH Channel Availability (PCA) : -PCA1 -PCA2 |
Available Available |
7.1.1.7.5 Test requirements
The UE-Id type and UE-Id field are included in the MAC header. When multiplexing on MAC is not applied, C/T field is included in the MAC header. Otherwise, C/T field is not included.
7.1.1.8 DTCH or DCCH mapped to DCH / Invalid C/T Field
7.1.1.8.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the DCH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.8.2 Conformance requirement
DTCH or DCCH mapped to DCH, no multiplexing of dedicated channels on MAC: -no MAC header is required.
DTCH or DCCH mapped to DCH, with multiplexing of dedicated channels on MAC: -C/T field is included in MAC header.
The following fields are defined for the MAC header:
– C/T field
The C/T field provides identification of the logical channel instance when multiple logical channels are carried on the same transport channel…
Structure of the C/T field
C/T field |
Designation |
0000 |
Logical channel 1 |
0001 |
Logical channel 2 |
… |
… |
1110 |
Logical channel 15 |
1111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.1 b).
7.1.1.8.3 Test purpose
1. To verify that the UE discards PDUs with reserved or incorrect values in C/T field.
2. To verify that the C/T field is correctly applied when a DTCH or DCCH is mapped to a DCH.
7.1.1.8.4 Method of test
Initial conditions
System Simulator:
– 1 cell, default parameters, Ciphering Off.
The DCH/DPCH is configured as specified in TS 34.108 clause 6.10.2.4.1.2 (FDD), 6.11.5.4.1.2(1.28Mcps TDD): (Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH) with the following exception:
Higher layer |
RAB/signalling RB |
RB#3 (SRB#3) |
|
User of Radio Bearer |
NAS_DT |
||
RLC |
Logical channel type |
DCCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
148 |
||
Max data rate, bps |
3700 |
||
RLC header, bit |
0 |
||
MAC |
MAC header, bit |
0 (note) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
DCH |
|
TB sizes, bit |
148 |
||
TFS |
TF0, bits |
0 x 148 |
|
TF1, bits |
1 x 148 |
||
TTI, ms |
40 |
||
Coding type |
CC 1/3 |
||
CRC, bit |
16 |
||
Max number of bits/TTI before rate matching |
516 |
||
Uplink: Max number of bits/radio frame before rate matching |
129 |
||
RM attribute |
155-165 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
The TFCS should be configured as specified in clause 6.10.2.4.1.2.1.1.2 (FDD), 6.11.5.4.1.2.1.1.2(1.28 Mcps TDD).
User Equipment:
The UE shall operate under normal test conditions, Ciphering Off.
The Test-USIM shall be inserted.
The SS starts broadcasting the System Information as specified in TS 34.108 clause 6.1, using the configuration for the PRACH and SCCPCH (signalled in SYSTEM INFORMATION 5) as follows:
1. The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (FDD), 6.11.5.4.4.3(1.28Mcps TDD) (Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH).
2. The PRACH is configured as specified in TS 34.108 clause 6.10.2.4.4.1 (FDD), 6.11.5.4.5.2(1.28Mcps TDD).
The SS follows the procedure in TS 34.108 clause 7.4.2.1 (Mobile Terminated for CS) so that the UE shall be in state BGP 6-1 (CS-CELL_DCH_INITIAL) or clause 7.4.2.2 (Mobile Terminated for PS) so that the UE shall be in state BGP 6-3 (PS-CELL_DCH_INITIAL). During this procedure the RRC CONNECTION SETUP message shall allocate a DCH to carry the signalling radio bearers as follows:
1. The DCH/DPCH is configured as specified in TS 34.108 clause 6.10.2.4.1.2 (FDD), 6.11.5.4.1.2(1.28Mcps TDD): Stand-alone UL:3.4 DL:3.4 kbps SRBs for DCCH).
Test procedure
a) The SS receives the PAGING RESPONSE or SERVICE REQUEST (depending on domain) message from the UE and checks the C/T field.
b) The SS transmits MAC PDUs containing RLC AM PDUs containing a DIRECT TRANSFER message containing
1. Dummy octet string for NAS Message, of size sufficient enough to fit in one RLC PDU of 144 bits, including the correct RLC AM header.
2. The IE CN Domain Identity is Set to PS Domain (no signalling connection for this Domain exists).
3. The polling bit in RLC header is set for transmission of RLC STATUS PDU.
The MAC header shall be set as follows:
Field |
Value |
C/T |
‘0111’B |
c) The SS checks that UE shall neither transmit RRC Status message on SRB2 nor RLC Status PDU on SRB3.
d) The SS again transmits MAC PDUs as in b) above, but this time uses the correct C/T value for AM-DCCH NAS High Priority of 0010’B. The sequence numbers in the RLC headers shall be identical with those sent in b).
e) SS Receives RLC Status PDU on SRB #3 acknowledging the receipt of the above RLC PDU.
f) The SS receives a RRC STATUS message on the uplink DCCH using AM RLC on SRB # 2.
g) The SS repeats steps b), c), d), e) and f), with the C/T field set as follows in step b):
Iteration |
C/T Value |
2 |
1111’B |
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
PAGING RESPONSE/SERVICE REQUEST |
Check C/T field |
|
2 |
|
MAC PDU(C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with incorrect C/T = 0111’B, or 1111’B |
|
2a |
wait for T = 5 s |
SS checks that UE shall neither transmit RRC-Status message on SRB 2 nor RLC Status PDU on SRB 3. See note 1 below. |
||
3 |
|
MAC PDU(C/T, RLC AM PDU(SN=x, DIRECT TRANSFER)) |
Sent with correct C/T = 0010’B |
|
4 |
|
RLC-STATUS-PDU |
ACK PDUs with SN = x C/T Field is recognised as correct for the DCCH. See note 2 below. |
|
5 |
|
RRC Status message |
||
NOTE 1: UE will Transmit Signalling Connection Release Indication on expiry of MM Timer T3240 or GMM Timer T3317. NOTE 2: RRC Status message may be received before RLC Status PDU. |
Steps 2 to 5 of the expected sequence are repeated for iteration 2.
NOTE: For iteration 2 the SN in steps 2 and 4 starts with x+1.
Specific Message Contents
None
7.1.1.8.5 Test Requirement
In step a) the C/T field should be set to the Logical Channel ID for SRB #3 (0010’B). Note that this may be implied from receipt of the PAGING RESPONSE or SERVICE REQUEST message correctly by the SS test script.
During the test the SS shall request RLC status reports with every transmitted PDU by setting of the Polling Bit. The UE shall not send any STATUS PDUs indicating missing PDUs.
At the end of each iteration (steps 4 and 5 of expected sequence) the SS shall receive a RLC Status PDU on SRB # 3 with C/T field set to ‘0010’B and RRC Status message on SRB # 2.
7.1.1.9 MTCH mapped to FACH / Invalid TCTF (TDD MBSFN)
7.1.1.9.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.9.2 Conformance requirement
MTCH mapped to FACH:
The TCTF field and MBMS-Id field are included in the MAC header for MTCH
…
Table 9.2.1.1: Coding of the Target Channel Type Field on FACH for TDD
TCTF |
Designation |
000 |
BCCH |
001 |
CCCH |
010 |
CTCH |
01100 |
DCCH or DTCH over FACH |
01101 |
MCCH |
01110 |
MTCH |
01111 |
MSCH |
100 |
SHCCH |
101-111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.8.
7.1.1.9.3 Test purpose
1. To verify that the UE discards PDUs with reserved or incorrect values in the TCTF field.
2. To verify that the TCTF field is correctly applied when a MTCH is mapped to the FACH.
7.1.1.9.4 Method of test
Initial conditions
System Simulator:
Unicast carrier: 1 cell, Cell 1 with default configuration.
– MBSFN carriers: 1 cell, Cell 31 has default parameters. 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.
The configuration of the S-CCPCH which will carry the MTCH is based upon that specified in TS 34.108 clause 6.11.1c (3.84 Mcps TDD), 6.11.1d (7.68 Mcps TDD) and 6.11.5.4.4.13 (1.28 Mcps TDD) 8kbps RB for MBSFN MTCH with the following exceptions for the FACH:
Higher layer |
RAB/signalling RB |
RAB |
|
User of Radio Bearer |
Test |
||
RLC |
Logical channel type |
MTCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
345 |
||
Max data rate, bps |
8200 |
||
UMD PDU header, bit |
0 |
||
MAC |
MAC header, bit |
0 (note) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
FACH |
|
TB sizes, bit |
345 |
||
TFS |
TF0, bits |
0x345 |
|
TF1, bits |
1×345 |
||
TTI, ms |
40 |
||
Coding type |
TC |
||
CRC, bit |
16 |
||
Max number of bits/TTI after channel coding |
1095 |
||
Max number of bits/radio frame before rate matching |
274 |
||
RM attribute |
128 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
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 there will be a session starting on MBSFN Cell 31 (see TS 34.108 clause 11.2.4).
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode available on UE Yes/No.
– Support of TDD transmit and receive functions available on UE Yes/No.
– Support of TDD MBSFN receive only function available on UE Yes/No.
Test procedure
a) The UE is camping on Cell 1 and Cell 31. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 (no session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
b) The SS sends ACTIVATE RB TEST MODE on the unicast carrier and the UE responds with ACTIVATE RB TEST MODE COMPLETE.
c) The SS sends CLOSE UE TEST LOOP to activate RLC SDU counting on Cell 31 MTCH (Transmission identity indicating the MBMS activated service).
d) The SS notifies on MCCH about the start of an MBMS session for one modification period. MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C4 (one PTM session starting) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
e) MCCH messages are then transmitted by the SS on Cell 31 using MBMS configuration C2 (one PTM session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
f) The SS waits for the UE to start reception of the MBMS data on MTCH according to the specified service activation time. The UE closes the test loop. The UE sends CLOSE UE TEST LOOP COMPLETE.
g) The SS transmits MAC PDUs containing RLC UM PDUs containing an octet string representing dummy traffic data, of size sufficient enough to fit in one RLC PDU of 338 bits, including the correct RLC UM header.
The MAC header shall be set as follows:
Field |
Value |
TCTF |
101’B |
MBMS-Id |
0000’B |
h) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The SS waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE corresponds to zero received RLC SDUs. The SS records the value.
i) The SS again transmits MAC PDUs as in b) above, but this time uses the correct TCTF of 01110’B. Where a TCTF size of 5-bits is used, 2-bits from the RLC payload (specified above as 338 bits) shall be discarded. The sequence numbers in the RLC headers shall be identical with those sent in b).
j) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The SS waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is > 0. The SS records the value.
k) The SS repeats steps g), h), i) and j), with the TCTF field set as follows in step g):
Iteration |
TCTF Value |
2 |
110’B |
3 |
111’B |
4 |
001’B |
5 |
010’B |
6 |
100’B |
7 |
01100’B |
NOTE 1: For a UE in UE test loop mode 3 the RLC SDU counter value is only reset upon reception of the CLOSE UE TEST LOOP message configuring UE test loop mode 3. To enable the SS to measure the number of received RLC SDUs for the different sub-tests the SS needs to record the reported values for each sub-test and perform the checking of the reported value relative to the previously reported value.
Expected sequence
Step |
Direction |
Carrier |
Message |
Comment |
|
UE |
SS |
||||
1 |
|
U |
ACTIVATE RB TEST MODE |
||
2 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
3 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated on Cell 31 for the selected national service on MTCH. |
|
4 |
|
M |
MBMS MCCH Message Configuration C4 |
Includes the national service activated at UE in the modified services list for one modification period. |
|
5 |
|
M |
MBMS MCCH Message Configuration C2 |
No modified services. One ongoing service corresponding to that activated at the UE. |
|
6 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE establishes the MTCH according to the activation time and closes the test loop. |
|
7 |
SS |
M |
The SS repeats steps 8 – 15 for each invalid TCTF value. |
||
8 |
MAC PDU(TCTF, MBMS-Id, RLC UM PDU(SN=x)) |
Sent with invalid TCTF = 101’B, 110’B, 111’B, 001’B, 010’B, 100’B and 01100’B |
|||
9 |
SS waits for T = 2 s |
||||
10 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
11 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is equal to zero. The SS records the value. |
|
12 |
MAC PDU(TCTF, MBMS-Id, RLC UM PDU(SN=x)) |
Sent with correct TCTF = 01110’B |
|||
13 |
SS waits for T = 2 s |
||||
14 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
15 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. The SS records the value. |
|
16 |
|
U |
OPEN UE TEST LOOP |
||
17 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
18 |
|
U |
DEACTIVATE RB TEST MODE |
||
19 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
Steps 8 – 15 of the above expected sequence are repeated for iterations 2 to 7. Note: For iteration k the SN in steps 8 and 12 starts with x + (k –1).
Specific Message Contents
With the following exceptions, all messages have the same content as defined in TS 34.108 clause 9.1.3 for the MBSFN carriers and in TS 34.108 clause 9.1.1 or 9.1.2 for the unicast carrier:
MBMS COMMON P-T-M RB INFORMATION (Step 4 and Step 5) (3.84 Mcps)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
RB information list |
1 entry in the list |
Rel-6 |
– RB identity |
||
– MBMS Common RB identity |
14 |
|
– PDCP info |
||
– Support for lossless SRNS relocation |
Not Present |
|
– Max PDCP SN window size |
Not Present |
|
– PDCP PDU header |
absent |
|
– Header compression information |
Not Present |
|
– RLC info |
||
– DL UM RLC LI size |
7 |
|
– DL Duplication Avoidance and Reordering info |
Not Present |
|
– DL Out of sequence delivery info |
Not Present |
|
TrCh information for each TrCh |
1 entry in the list |
Rel-6 |
– Transport channel identity |
||
– MBMS Common TrCh identity |
1 |
|
– TFS |
||
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport Format Information |
||
– RLC Size |
Refer to TrCh parameters defined above |
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
– Number of Transport blocks |
Refer to TrCh parameters defined above |
|
– CHOICE mode |
TDD |
|
– Transmission Time Interval |
Not Present |
|
– CHOICE Logical Channel List |
ALL |
|
– no data |
||
– Semi-static Transport Format information |
||
– Transmission time interval |
Refer to TrCh parameters defined above |
|
– Type of channel coding |
Turbo |
|
– Coding Rate |
Not Present |
|
– Rate matching attribute |
Refer to TrCh parameters defined above |
|
– CRC size |
Refer to TrCh parameters defined above |
|
TrCh information for each CCTrCh |
Not Present |
Rel-6 |
PhyCh information |
1 entry in list |
Rel-6 |
– PhyCh identity |
||
– MBMS Common PhyCh identity |
23 |
|
– Secondary CCPCH info MBMS |
||
– CHOICE mode |
1.28/3.84 Mcps TDD |
|
– Common timeslot info MBMS |
||
– 2nd interleaving mode |
Frame |
|
– TFCI coding |
Reference to clause 6.11.1c |
|
– Puncturing limit |
Reference to clause 6.11.1c |
|
– Downlink Timeslots and Codes |
||
– First individual timeslot info |
||
– Timeslot number |
||
– CHOICE TDD option |
3.84 Mcps |
|
– Timeslot number |
1 |
|
– TFCI existence |
TRUE |
|
– Midamble Shift and burst type |
||
– CHOICE TDD option |
3.84 Mcps TDD |
|
– CHOICE Burst Type |
MBSFN Burst Type |
Rel-7 |
– no data |
Rel-7 |
|
– CHOICE TDD option |
3.84Mcps TDD |
|
– no data |
||
– First timeslot channelisation codes |
||
– CHOICE codes representation |
Consecutive codes |
|
– First channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– Last channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– CHOICE more timeslots |
No more timeslots |
|
– no data |
||
– Modulation |
Reference to clause 6.11.1c |
Rel-7 |
MBMS COMMON P-T-M RB INFORMATION (Step 4 and Step 5) (7.68 Mcps)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-7 |
|
RB information list |
1 entry in the list |
Rel-7 |
– RB identity |
||
– MBMS Common RB identity |
14 |
|
– PDCP info |
||
– Support for lossless SRNS relocation |
Not Present |
|
– Max PDCP SN window size |
Not Present |
|
– PDCP PDU header |
absent |
|
– Header compression information |
Not Present |
|
– RLC info |
||
– DL UM RLC LI size |
7 |
|
– DL Duplication Avoidance and Reordering info |
Not Present |
|
– DL Out of sequence delivery info |
Not Present |
|
TrCh information for each TrCh |
1 entry in the list |
Rel-7 |
– Transport channel identity |
||
– MBMS Common TrCh identity |
1 |
|
– TFS |
||
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport Format Information |
||
– RLC Size |
Refer to TrCh parameters defined above |
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
– Number of Transport blocks |
Refer to TrCh parameters defined above |
|
– CHOICE mode |
TDD |
|
– Transmission Time Interval |
Not Present |
|
– CHOICE Logical Channel List |
ALL |
|
– no data |
||
– Semi-static Transport Format information |
||
– Transmission time interval |
Refer to TrCh parameters defined above |
|
– Type of channel coding |
Turbo |
|
– Coding Rate |
Not Present |
|
– Rate matching attribute |
Refer to TrCh parameters defined above |
|
– CRC size |
Refer to TrCh parameters defined above |
|
TrCh information for each CCTrCh |
Not Present |
Rel-7 |
PhyCh information |
1 entry in list |
Rel-7 |
– PhyCh identity |
||
– MBMS Common PhyCh identity |
23 |
|
– Secondary CCPCH info MBMS |
||
– CHOICE mode |
7.68 Mcps TDD |
|
– Common timeslot info MBMS |
||
– 2nd interleaving mode |
Frame |
|
– TFCI coding |
Reference to clause 6.11.1d |
|
– Puncturing limit |
Reference to clause 6.11.1d |
|
– Downlink Timeslots and Codes VHCR |
||
– First Individual timeslot info |
||
– Timeslot number |
||
– CHOICE TDD option |
7.68 Mcps option |
|
Timeslot number |
1 |
|
– TFCI existence |
TRUE |
|
– Midamble Shift and burst type |
||
– CHOICE TDD option |
7.68 Mcps TDD |
|
– CHOICE Burst Type |
MBSFN Burst Type |
|
– no data |
Default |
|
– CHOICE TDD option |
7.68Mcps TDD |
|
– no data |
||
– First timeslot channelisation codes VHCR |
||
– CHOICE codes representation |
Consecutive codes |
|
– First channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– Last channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– CHOICE more timeslots |
No more timeslots |
|
– no data |
||
– Modulation |
Reference to clause 6.11.1d |
MBMS COMMON P-T-M RB INFORMATION (Step 4 and Step 5) (1.28 Mcps)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
RB information list |
1 entry in the list |
Rel-6 |
– RB identity |
||
– MBMS Common RB identity |
14 |
|
– PDCP info |
||
– Support for lossless SRNS relocation |
Not Present |
|
– Max PDCP SN window size |
Not Present |
|
– PDCP PDU header |
absent |
|
– Header compression information |
Not Present |
|
– RLC info |
||
– DL UM RLC LI size |
7 |
|
– DL Duplication Avoidance and Reordering info |
Not Present |
|
– DL Out of sequence delivery info |
Not Present |
|
TrCh information for each TrCh |
1 entry in the list |
Rel-6 |
– Transport channel identity |
||
– MBMS Common TrCh identity |
1 |
|
– TFS |
||
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport Format Information |
||
– RLC Size |
Refer to TrCh parameters defined above |
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
– Number of Transport blocks |
Refer to TrCh parameters defined above |
|
– CHOICE mode |
TDD |
|
– Transmission Time Interval |
C |
|
– CHOICE Logical Channel List |
ALL |
|
– no data |
||
– Semi-static Transport Format information |
||
– Transmission time interval |
Refer to TrCh parameters defined above |
|
– Type of channel coding |
Turbo |
|
– Coding Rate |
Not Present |
|
– Rate matching attribute |
Refer to TrCh parameters defined above |
|
– CRC size |
Refer to TrCh parameters defined above |
|
TrCh information for each CCTrCh |
Not Present |
Rel-6 |
PhyCh information |
1 entry in list |
Rel-6 |
– PhyCh identity |
||
– MBMS Common PhyCh identity |
23 |
|
– Secondary CCPCH info MBMS |
||
– CHOICE mode |
1.28/3.84 Mcps TDD |
|
– Common timeslot info MBMS |
||
– 2nd interleaving mode |
Frame |
|
– TFCI coding |
Reference to clause 6.11.5.4.4.13 |
|
– Puncturing limit |
Reference to clause 6.11.5.4.4.13 |
|
– Downlink Timeslots and Codes |
||
– First individual timeslot info |
||
– Timeslot number |
||
– CHOICE TDD option |
1.28 Mcps |
|
– Timeslot number |
1 |
|
– TFCI existence |
TRUE |
|
– Midamble Shift and burst type |
||
– CHOICE TDD option |
1.28 Mcps TDD |
|
– Midamble Allocation Mode |
Common midamble |
|
– Midamble configuration |
2 |
|
– CHOICE TDD option |
1.28Mcps TDD |
|
– Modulation |
Reference to clause 6.11.5.4.4.13 |
|
– SS-TPC Symbols |
1 |
|
– Additional TPC-SS Symbols |
Not Present |
|
– First timeslot channelisation codes |
||
– CHOICE codes representation |
Consecutive codes |
|
– First channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– Last channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– CHOICE more timeslots |
No more timeslots |
|
– no data |
||
– MBSFN Special Time Slot |
TS7 |
Rel-7 |
– Modulation |
Reference to clause 6.11.5.4.4.13 |
Rel-7 |
LCR TDD MBSFN information |
Not Present |
Rel-7 |
MBMS CURRENT CELL P-T-M RB INFORMATION (Step 4 and Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
S-CCPCH list |
Contains 1 S-CCPCH |
Rel-6 |
– S-CCPCH identity |
Not Present |
|
– Secondary CCPCH info |
23 |
|
– MBMS Soft Combining Timing Offset |
Not Present |
|
– TrCh information common for all TrCh |
Not Present (MD) |
|
– TrCH information list |
||
– TrCh information |
1 |
|
– RB information list |
||
– RB information |
||
– RB information |
14 |
|
– MBMS short transmission ID |
Reference to the service which is being provided on this RB. |
|
– MBMS logical channel identity |
1 |
|
– L1 combining status |
Not Present |
|
– MSCH configuration information |
Not Present |
|
S-CCPCH in SIB type 5 |
Not Present |
Rel-6 |
MBSFN TDM Info List |
Not Present |
Rel-7 |
7.1.1.9.5 Test Requirement
1) At step 11 on each iteration, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number that corresponds to zero received RLC SDUs for Cell 31 MTCH.
2) At step 15 on each iteration, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number that corresponds to > 0 received RLC SDUs for Cell 31 MTCH.
7.1.1.9a MTCH mapped to FACH / Invalid TCTF (3.84 Mcps TDD IMB)
7.1.1.9a.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.9a.2 Conformance requirement
MTCH mapped to FACH:
The TCTF field and MBMS-Id field are included in the MAC header for MTCH
Table 9.2.1.1a: Coding of the Target Channel Type Field on FACH for 3.84 Mcps TDD IMB
TCTF |
Designation |
00 |
BCCH |
01000000 |
CCCH |
01000001-01001111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
01010000 |
MCCH |
01010001-01011110 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
01011111 |
MSCH |
0110 |
MTCH |
0111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
10000000 |
CTCH |
10000001- 10111111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
11 |
DCCH or DTCH over FACH |
Reference(s)
TS 25.321 [6] clauses 9.2.1 and 9.2.1.8.
7.1.1.9a.3 Test purpose
1. To verify that the UE discards PDUs with reserved or incorrect values in the TCTF field.
2. To verify that the TCTF field is correctly applied when a MTCH is mapped to the FACH.
7.1.1.9a.4 Method of test
Initial conditions
System Simulator:
Unicast carrier: 1 cell, Cell 1 with default configuration.
– MBSFN carriers: 1 cell, Cell 31 has default parameters. 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 [9].
The configuration of the S-CCPCH which will carry the MTCH is based upon that specified in TS 34.108 [9], clause 6.11.1e (3.84 Mcps TDD IMB) 8kbps RB for MBSFN MTCH with the following exceptions for the FACH:
Higher layer |
RAB/signalling RB |
RAB |
|
User of Radio Bearer |
Test |
||
RLC |
Logical channel type |
MTCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
344 |
||
Max data rate, bps |
8200 |
||
UMD PDU header, bit |
0 |
||
MAC |
MAC header, bit |
0 (NOTE ) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
FACH |
|
TB sizes, bit |
344 |
||
TFS |
TF0, bits |
0x344 |
|
TF1, bits |
1×344 |
||
TTI, ms |
40 |
||
Coding type |
TC |
||
CRC, bit |
16 |
||
Max number of bits/TTI after channel coding |
1092 |
||
Max number of bits/radio frame before rate matching |
273 |
||
RM attribute |
128 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
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 [9].
– The UE is in MBSFN Idle mode with one activated service as specified in clause 7.6.4 of TS 34.108 [9]. The UE has selected (i.e. it is included in MBMS_ACTIVATED_SERVICES variable) a service for which there will be a session starting on MBSFN Cell 31 (see TS 34.108 [9], clause 11.2.4).
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode available on UE Yes/No.
– Support of TDD or FDD transmit and receive functions available on UE Yes/No.
– Support of 3.84 Mcps TDD IMB receive function available on UE Yes/No.
Test procedure
a) The UE is camping on Cell 1 and Cell 31. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 (no session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108 [9].
b) The SS sends ACTIVATE RB TEST MODE on the unicast carrier and the UE responds with ACTIVATE RB TEST MODE COMPLETE.
c) The SS sends CLOSE UE TEST LOOP to activate RLC SDU counting on Cell 31 MTCH (Transmission identity indicating the MBMS activated service).
d) The SS notifies on MCCH about the start of an MBMS session for one modification period. MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C4 (one PTM session starting) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108 [9].
e) MCCH messages are then transmitted by the SS on Cell 31 using MBMS configuration C2 (one PTM session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108 [9].
f) The SS waits for the UE to start reception of the MBMS data on MTCH according to the specified service activation time. The UE closes the test loop. The UE sends CLOSE UE TEST LOOP COMPLETE.
g) The SS transmits MAC PDUs containing RLC UM PDUs containing an octet string representing dummy traffic data, of size sufficient enough to fit in one RLC PDU of 332 bits, including the correct RLC UM header.
The MAC header shall be set as follows:
Field |
Value |
TCTF |
01000001’B |
MBMS-Id |
0000’B |
h) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The SS waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE corresponds to zero received RLC SDUs. The SS records the value.
i) The SS again transmits MAC PDUs as in g) above, but this time uses the correct TCTF of 0110’B. Where a TCTF size of 4-bits is used, 4-bits to the RLC payload (specified above as 332 bits) shall be added. The sequence numbers in the RLC headers shall be identical with those sent in g).
j) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The SS waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is > 0. The SS records the value.
k) The SS repeats steps g), h), i) and j), with the TCTF field set as follows in step g):
Iteration |
TCTF Value |
2 |
01000010’B |
3 |
01001111’B |
4 |
01000000’B |
5 |
01010001’B |
6 |
01010010’B |
7 |
01011110’B |
8 |
0111’B |
9 |
10000000’B |
10 |
10000001’B |
11 |
10000010’B |
12 |
10111111’B |
13 |
11’B |
NOTE 1: For a UE in UE test loop mode 3 the RLC SDU counter value is only reset upon reception of the CLOSE UE TEST LOOP message configuring UE test loop mode 3. To enable the SS to measure the number of received RLC SDUs for the different sub-tests the SS needs to record the reported values for each sub-test and perform the checking of the reported value relative to the previously reported value.
Expected sequence
Step |
Direction |
Carrier |
Message |
Comment |
|
UE |
SS |
||||
1 |
|
U |
ACTIVATE RB TEST MODE |
||
2 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
3 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated on Cell 31 for the selected national service on MTCH. |
|
4 |
|
M |
MBMS MCCH Message Configuration C4 |
Includes the national service activated at UE in the modified services list for one modification period. |
|
5 |
|
M |
MBMS MCCH Message Configuration C2 |
No modified services. One ongoing service corresponding to that activated at the UE. |
|
6 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE establishes the MTCH according to the activation time and closes the test loop. |
|
7 |
SS |
M |
The SS repeats steps 8 – 15 for each invalid TCTF value. |
||
8 |
MAC PDU(TCTF, MBMS-Id, RLC UM PDU(SN=x)) |
Sent with invalid TCTF = 01000001’B, 01000010’B, 01001111’B, 01000000’B, 01010001’B, 01010010’B, 01011110’B, 0111’B, 10000000’B, 10000001’B, 10000010’B, 10111111’B, 11’B |
|||
9 |
SS waits for T = 2 s |
||||
10 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
11 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is equal to zero. The SS records the value. |
|
12 |
MAC PDU(TCTF, MBMS-Id, RLC UM PDU(SN=x)) |
Sent with correct TCTF = 0110’B |
|||
13 |
SS waits for T = 2 s |
||||
14 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
15 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. The SS records the value. |
|
16 |
|
U |
OPEN UE TEST LOOP |
||
17 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
18 |
|
U |
DEACTIVATE RB TEST MODE |
||
19 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
Steps 8 – 15 of the above expected sequence are repeated for iterations 2 to 13. Note: For iteration k the SN in steps 8 and 12 starts with x + (k –1).
Specific Message Contents
With the following exceptions, all messages have the same content as defined in TS 34.108 [9], clause 9.1.3 for the MBSFN carriers and in TS 34.108 [9], clause 9.1.1 or 9.1.2 for the unicast carrier:
Contents of MBMS COMMON P-T-M RB INFORMATION message: UM (3.84 Mcps TDD IMB)
Information Element |
Value/remark |
Version |
Message type |
|
Rel-6 |
RB information list |
1 entry in the list |
Rel-6 |
– RB identity |
|
Rel-6 |
– MBMS Common RB identity |
14 |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
Not Present |
|
– Max PDCP SN window size |
Not Present |
|
– PDCP PDU header |
absent |
|
– Header compression information |
Not Present |
|
– RLC info |
|
|
– DL UM RLC LI size |
7 |
|
– DL Duplication Avoidance and Reordering info |
Not Present |
|
– DL Out of sequence delivery info |
Not Present |
|
TrCh information for each TrCh |
1 entry in the list |
Rel-6 |
– Transport channel identity |
|
Rel-6 |
– MBMS Common TrCh identity |
1 |
|
– TFS |
|
|
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport format information |
|
|
– RLC Size |
Refer to TrCh parameters defined above |
|
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
|
– Number of Transport blocks |
Refer to TrCh parameters defined above |
|
– CHOICE mode |
FDD |
|
– CHOICE Logical channel list |
All |
|
– no data |
|
|
– Semi-static Transport Format information |
|
|
– Transmission time interval |
Refer to TrCh parameters defined above |
|
– Type of channel coding |
Turbo |
|
– Coding Rate |
Not present |
|
– Rate matching attribute |
Refer to TrCh parameters defined above |
|
– CRC size |
Refer to TrCh parameters defined above |
|
TrCh information for each CCTrCh |
Not Present (Default TFCS applies for each CCTrCh) |
Rel-6 |
PhyCh information |
1 entry in list |
Rel-6 |
– PhyCh identity |
|
Rel-6 |
– MBMS Common PhyCh identity |
23 |
|
CHOICE mode |
3.84 Mcps TDD IMB |
|
– Secondary CCPCH frame type 2 info |
|
Rel-8 |
– Sub-frame number |
2(check in 5.5.2) |
Rel-8 |
– Downlink channelisation codes |
|
Rel-8 |
– First channelisation code |
(1..15) or reference to 6.10 "parameter set" |
|
– Last channelisation code |
(1..15) or reference to 6.10 "parameter set" |
|
– CHOICE modulation |
16QAM(check in6.10 "parameter set") |
Rel-8 |
– CPICH secondary CCPCH power offset |
0dB |
Rel-8 |
LCR TDD MBSFN information |
Not present |
Rel-7 |
MBMS CURRENT CELL P-T-M RB INFORMATION (Step 4 and Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
S-CCPCH list |
Contains 1 S-CCPCH |
Rel-6 |
– S-CCPCH identity |
Not Present |
|
– Secondary CCPCH info |
23 |
|
– MBMS Soft Combining Timing Offset |
Not Present |
|
– TrCh information common for all TrCh |
Not Present (MD) |
|
– TrCH information list |
||
– TrCh information |
1 |
|
– RB information list |
||
– RB information |
||
– RB information |
14 |
|
– MBMS short transmission ID |
Reference to the service which is being provided on this RB. |
|
– MBMS logical channel identity |
1 |
|
– L1 combining status |
Not Present |
|
– MSCH configuration information |
Not Present |
|
S-CCPCH in SIB type 5 |
Not Present |
Rel-6 |
MBSFN TDM Info List |
Not Present |
Rel-7 |
7.1.1.9a.5 Test Requirement
1) At step 11 on each iteration, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number that corresponds to zero received RLC SDUs for Cell 31 MTCH.
2) At step 15 on each iteration, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number that corresponds to > 0 received RLC SDUs for Cell 31 MTCH.
7.1.1.10 MTCH mapped to FACH / Invalid MBMS-Id (TDD MBSFN)
7.1.1.10.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.10.2 Conformance requirement
MTCH mapped to FACH:
The TCTF field and MBMS-Id field are included in the MAC header for MTCH
…
Table 9.2.1.8: Structure of the MBMS-Id field
MBMS-Id field |
MBMS logical channel identity [7] |
0000 |
1 |
0001 |
2 |
… |
… |
1110 |
15 |
1111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
Reference(s)
TS 25.321 clauses 9.2.1 and 9.2.1.8.
7.1.1.10.3 Test purpose
1. To verify that the UE discards PDUs with reserved or incorrect values in the MBMS-Id field.
2. To verify that the MBMS-Id field is correctly applied when a MTCH is mapped to the FACH.
7.1.1.10.4 Method of test
Initial conditions
System Simulator:
Unicast carrier: 1 cell, Cell 1 with default configuration.
– MBSFN carriers: 1 cell, Cell 31 has default parameters. 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.
The configuration of the S-CCPCH which will carry the MTCH is based upon that specified in TS 34.108 clause 6.11.1c (3.84 Mcps TDD) and 6.11.1d (7.68 Mcps TDD) 8kbps RB for MBSFN MTCH with the following exceptions for the FACH:
Higher layer |
RAB/signalling RB |
RAB |
|
User of Radio Bearer |
Test |
||
RLC |
Logical channel type |
MTCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
345 |
||
Max data rate, bps |
8200 |
||
UMD PDU header, bit |
0 |
||
MAC |
MAC header, bit |
0 (note) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
FACH |
|
TB sizes, bit |
345 |
||
TFS |
TF0, bits |
0x345 |
|
TF1, bits |
1×345 |
||
TTI, ms |
40 |
||
Coding type |
TC |
||
CRC, bit |
16 |
||
Max number of bits/TTI after channel coding |
1095 |
||
Max number of bits/radio frame before rate matching |
274 |
||
RM attribute |
128 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
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 there will be a session starting on MBSFN Cell 31 (see TS 34.108 clause 11.2.4).
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode available on UE Yes/No.
– Support of TDD transmit and receive functions available on UE Yes/No.
– Support of TDD MBSFN receive only function available on UE Yes/No.
Test procedure
a) The UE is camping on Cell 1 and Cell 31. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 (no session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
b) The SS sends ACTIVATE RB TEST MODE on the unicast carrier and the UE responds with ACTIVATE RB TEST MODE COMPLETE.
c) The SS sends CLOSE UE TEST LOOP to activate RLC SDU counting on Cell 31 MTCH (Transmission identity indicating the MBMS activated service).
d) The SS notifies on MCCH about the start of an MBMS session for one modification period. MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C4 (one PTM session starting) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
e) MCCH messages are then transmitted by the SS on Cell 31 using MBMS configuration C2 (one PTM session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
f) The SS waits for the UE to start reception of the MBMS data on MTCH according to the specified service activation time. The UE closes the test loop. The UE sends CLOSE UE TEST LOOP COMPLETE.
g) The SS transmits MAC PDUs containing RLC UM PDUs containing an octet string representing dummy traffic data, of size sufficient enough to fit in one RLC PDU of 336 bits, including the correct RLC UM header.
The MAC header shall be set as follows:
Field |
Value |
TCTF |
01110’B |
MBMS-Id |
1111’B |
h) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The SS waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE corresponds to zero received RLC SDUs. The SS records the value.
i) The SS again transmits MAC PDUs as in b) above, but this time uses a valid MBMS-Id of 1110’B. The sequence numbers in the RLC headers shall be identical with those sent in b).
j) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The SS waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE corresponds to > 0 received RLC SDUs
Expected sequence
Step |
Direction |
Carrier |
Message |
Comment |
|
UE |
SS |
||||
1 |
|
U |
ACTIVATE RB TEST MODE |
||
2 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
3 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated on Cell 31 for the selected national service on MTCH. |
|
4 |
|
M |
MBMS MCCH Message Configuration C4 |
Includes the national service activated at UE in the modified services list for one modification period. |
|
5 |
|
M |
MBMS MCCH Message Configuration C2 |
No modified services. One ongoing service corresponding to that activated at the UE. |
|
6 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE establishes the MTCH according to the activation time and closes the test loop. |
|
7 |
MAC PDU(TCTF, MBMS-Id, RLC UM PDU(SN=x)) |
Sent with reserved MBMS-Id = 1111’B |
|||
8 |
SS waits for T = 2 s |
||||
9 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
10 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is equal to zero. The SS records the value. |
|
11 |
MAC PDU(TCTF, MBMS-Id, RLC UM PDU(SN=x)) |
Sent with valid MBMS-Id = 1110’B |
|||
12 |
SS waits for T = 2 s |
||||
13 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
14 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. |
|
15 |
|
U |
OPEN UE TEST LOOP |
||
16 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
17 |
|
U |
DEACTIVATE RB TEST MODE |
||
18 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
Specific Message Contents
With the following exceptions, all messages have the same content as defined in TS 34.108 clause 9.1.3 for the MBSFN carriers and in TS 34.108 clause 9.1.1 or 9.1.2 for the unicast carrier:
MBMS COMMON P-T-M RB INFORMATION (Step 4 and Step 5) (3.84 Mcps)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
RB information list |
1 entry in the list |
Rel-6 |
– RB identity |
||
– MBMS Common RB identity |
14 |
|
– PDCP info |
||
– Support for lossless SRNS relocation |
Not Present |
|
– Max PDCP SN window size |
Not Present |
|
– PDCP PDU header |
absent |
|
– Header compression information |
Not Present |
|
– RLC info |
||
– DL UM RLC LI size |
15 |
|
– DL Duplication Avoidance and Reordering info |
Not Present |
|
– DL Out of sequence delivery info |
Not Present |
|
TrCh information for each TrCh |
1 entry in the list |
Rel-6 |
– Transport channel identity |
||
– MBMS Common TrCh identity |
1 |
|
– TFS |
||
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport Format Information |
||
– RLC Size |
Refer to TrCh parameters defined above |
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
– Number of Transport blocks |
Refer to TrCh parameters defined above |
|
– CHOICE mode |
TDD |
|
– Transmission Time Interval |
Not Present |
|
– CHOICE Logical Channel List |
ALL |
|
– no data |
||
– Semi-static Transport Format information |
||
– Transmission time interval |
Refer to TrCh parameters defined above |
|
– Type of channel coding |
Turbo |
|
– Coding Rate |
Not Present |
|
– Rate matching attribute |
Refer to TrCh parameters defined above |
|
– CRC size |
Refer to TrCh parameters defined above |
|
TrCh information for each CCTrCh |
Not Present |
Rel-6 |
PhyCh information |
1 entry in list |
Rel-6 |
– PhyCh identity |
||
– MBMS Common PhyCh identity |
23 |
|
– Secondary CCPCH info MBMS |
||
– CHOICE mode |
1.28/3.84 Mcps TDD |
|
– Common timeslot info MBMS |
||
– 2nd interleaving mode |
Frame |
|
– TFCI coding |
Reference to clause 6.11.1c |
|
– Puncturing limit |
Reference to clause 6.11.1c |
|
– Downlink Timeslots and Codes |
||
– First individual timeslot info |
||
– Timeslot number |
||
– CHOICE TDD option |
3.84 Mcps |
|
– Timeslot number |
1 |
|
– TFCI existence |
TRUE |
|
– Midamble Shift and burst type |
||
– CHOICE TDD option |
3.84 Mcps TDD |
|
– CHOICE Burst Type |
MBSFN Burst Type |
Rel-7 |
– no data |
Rel-7 |
|
– CHOICE TDD option |
3.84Mcps TDD |
|
– no data |
||
– First timeslot channelisation codes |
||
– CHOICE codes representation |
Consecutive codes |
|
– First channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– Last channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– CHOICE more timeslots |
No more timeslots |
|
– no data |
||
– Modulation |
Reference to clause 6.11.1c |
Rel-7 |
MBMS COMMON P-T-M RB INFORMATION (Step 4 and Step 5) (7.68 Mcps)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-7 |
|
RB information list |
1 entry in the list |
Rel-7 |
– RB identity |
||
– MBMS Common RB identity |
14 |
|
– PDCP info |
||
– Support for lossless SRNS relocation |
Not Present |
|
– Max PDCP SN window size |
Not Present |
|
– PDCP PDU header |
absent |
|
– Header compression information |
Not Present |
|
– RLC info |
||
– DL UM RLC LI size |
15 |
|
– DL Duplication Avoidance and Reordering info |
Not Present |
|
– DL Out of sequence delivery info |
Not Present |
|
TrCh information for each TrCh |
1 entry in the list |
Rel-7 |
– Transport channel identity |
||
– MBMS Common TrCh identity |
1 |
|
– TFS |
||
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport Format Information |
||
– RLC Size |
Refer to TrCh parameters defined above |
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
– Number of Transport blocks |
Refer to TrCh parameters defined above |
|
– CHOICE mode |
TDD |
|
– Transmission Time Interval |
Not Present |
|
– CHOICE Logical Channel List |
ALL |
|
– no data |
||
– Semi-static Transport Format information |
||
– Transmission time interval |
Refer to TrCh parameters defined above |
|
– Type of channel coding |
Turbo |
|
– Coding Rate |
Not Present |
|
– Rate matching attribute |
Refer to TrCh parameters defined above |
|
– CRC size |
Refer to TrCh parameters defined above |
|
TrCh information for each CCTrCh |
Not Present |
Rel-7 |
PhyCh information |
1 entry in list |
Rel-7 |
– PhyCh identity |
||
– MBMS Common PhyCh identity |
23 |
|
– Secondary CCPCH info MBMS |
||
– CHOICE mode |
7.68 Mcps TDD |
|
– Common timeslot info MBMS |
||
– 2nd interleaving mode |
Frame |
|
– TFCI coding |
Reference to clause 6.11.1d |
|
– Puncturing limit |
Reference to clause 6.11.1d |
|
– Downlink Timeslots and Codes VHCR |
||
– First Individual timeslot info |
||
– Timeslot number |
||
– CHOICE TDD option |
7.68 Mcps option |
|
Timeslot number |
1 |
|
– TFCI existence |
TRUE |
|
– Midamble Shift and burst type |
||
– CHOICE TDD option |
7.68 Mcps TDD |
|
– CHOICE Burst Type |
MBSFN Burst Type |
|
– no data |
Default |
|
– CHOICE TDD option |
7.68Mcps TDD |
|
– no data |
||
– First timeslot channelisation codes VHCR |
||
– CHOICE codes representation |
Consecutive codes |
|
– First channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– Last channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– CHOICE more timeslots |
No more timeslots |
|
– no data |
||
– Modulation |
Reference to clause 6.11.1d |
MBMS COMMON P-T-M RB INFORMATION (Step 4 and Step 5) (1.28 Mcps)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
RB information list |
1 entry in the list |
Rel-6 |
– RB identity |
||
– MBMS Common RB identity |
14 |
|
– PDCP info |
||
– Support for lossless SRNS relocation |
Not Present |
|
– Max PDCP SN window size |
Not Present |
|
– PDCP PDU header |
absent |
|
– Header compression information |
Not Present |
|
– RLC info |
||
– DL UM RLC LI size |
15 |
|
– DL Duplication Avoidance and Reordering info |
Not Present |
|
– DL Out of sequence delivery info |
Not Present |
|
TrCh information for each TrCh |
1 entry in the list |
Rel-6 |
– Transport channel identity |
||
– MBMS Common TrCh identity |
1 |
|
– TFS |
||
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport Format Information |
||
– RLC Size |
Refer to TrCh parameters defined above |
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
– Number of Transport blocks |
Refer to TrCh parameters defined above |
|
– CHOICE mode |
TDD |
|
– Transmission Time Interval |
Not Present |
|
– CHOICE Logical Channel List |
ALL |
|
– no data |
||
– Semi-static Transport Format information |
||
– Transmission time interval |
Refer to TrCh parameters defined above |
|
– Type of channel coding |
Turbo |
|
– Coding Rate |
Not Present |
|
– Rate matching attribute |
Refer to TrCh parameters defined above |
|
– CRC size |
Refer to TrCh parameters defined above |
|
TrCh information for each CCTrCh |
Not Present |
Rel-6 |
PhyCh information |
1 entry in list |
Rel-6 |
– PhyCh identity |
||
– MBMS Common PhyCh identity |
23 |
|
– Secondary CCPCH info MBMS |
||
– CHOICE mode |
1.28/3.84 Mcps TDD |
|
– Common timeslot info MBMS |
||
– 2nd interleaving mode |
Frame |
|
– TFCI coding |
Reference to clause 6.11.5.4.4.13 |
|
– Puncturing limit |
Reference to clause 6.11.5.4.4.13 |
|
– Downlink Timeslots and Codes |
||
– First individual timeslot info |
||
– Timeslot number |
||
– CHOICE TDD option |
1.28 Mcps |
|
– Timeslot number |
1 |
|
– TFCI existence |
TRUE |
|
– Midamble Shift and burst type |
||
– CHOICE TDD option |
1.28 Mcps TDD |
|
– Midamble Allocation Mode |
Common midamble |
|
– Midamble configuration |
2 |
|
– CHOICE TDD option |
1.28Mcps TDD |
|
– Modulation |
Reference to clause 6.11.5.4.4.13 |
|
– SS-TPC Symbols |
1 |
|
– Additional TPC-SS Symbols |
Not Present |
|
– First timeslot channelisation codes |
||
– CHOICE codes representation |
Consecutive codes |
|
– First channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– Last channelisation code |
Reference clause 5.5.2 "Downlink physical channels code allocation for signalling" |
|
– CHOICE more timeslots |
No more timeslots |
|
– no data |
||
– MBSFN Special Time Slot |
TS7 |
Rel-7 |
– Modulation |
Reference to clause 6.11.5.4.4.13 |
Rel-7 |
LCR TDD MBSFN information |
Not Present |
Rel-7 |
MBMS CURRENT CELL P-T-M RB INFORMATION (Step 4 and Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
S-CCPCH list |
Contains 1 S-CCPCH |
Rel-6 |
– S-CCPCH identity |
Not Present |
|
– Secondary CCPCH info |
23 |
|
– MBMS Soft Combining Timing Offset |
Not Present |
|
– TrCh information common for all TrCh |
Not Present (MD) |
|
– TrCH information list |
||
– TrCh information |
1 |
|
– RB information list |
||
– RB information |
||
– RB information |
14 |
|
– MBMS short transmission ID |
Reference to the service which is being provided on this RB. |
|
– MBMS logical channel identity |
1 |
|
– L1 combining status |
Not Present |
|
– MSCH configuration information |
Not Present |
|
S-CCPCH in SIB type 5 |
Not Present |
Rel-6 |
MBSFN TDM Info List |
Not Present |
Rel-7 |
7.1.1.10.5 Test Requirement
1) At step 10 on each iteration, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number that corresponds to zero received RLC SDUs for Cell 31 MTCH.
2) At step 14 on each iteration, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number that corresponds to > 0 received RLC SDUs for Cell 31 MTCH.
7.1.1.10a MTCH mapped to FACH / Invalid MBMS-Id (3.84 Mcps TDD IMB)
7.1.1.10a.1 Definition
This tests that the MAC applies the correct header to the MAC PDU according to the type of logical channel carried on the FACH transport channel. Incorrect application of MAC headers would result in inoperation of the UE.
7.1.1.10a.2 Conformance requirement
MTCH mapped to FACH:
The TCTF field and MBMS-Id field are included in the MAC header for MTCH
…
Table 9.2.1.8a: Structure of the MBMS-Id field
MBMS-Id field |
MBMS logical channel identity [7] |
0000 |
1 |
0001 |
2 |
… |
… |
1110 |
15 |
1111 |
Reserved (PDUs with this coding will be discarded by this version of the protocol) |
Reference(s)
TS 25.321[6], clauses 9.2.1 and 9.2.1.8.
7.1.1.10a.3 Test purpose
1. To verify that the UE discards PDUs with reserved or incorrect values in the MBMS-Id field.
2. To verify that the MBMS-Id field is correctly applied when a MTCH is mapped to the FACH.
7.1.1.10a.4 Method of test
Initial conditions
System Simulator:
Unicast carrier: 1 cell, Cell 1 with default configuration.
– MBSFN carriers: 1 cell, Cell 31 has default parameters. 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 [9].
The configuration of the S-CCPCH which will carry the MTCH is based upon that specified in TS 34.108 [9], clause 6.11.1e (3.84 Mcps TDD IMB) 8kbps RB for MBSFN MTCH with the following exceptions for the FACH:
Higher layer |
RAB/signalling RB |
RAB |
|
User of Radio Bearer |
Test |
||
RLC |
Logical channel type |
MTCH |
|
RLC mode |
TM |
||
Payload sizes, bit |
344 |
||
Max data rate, bps |
8200 |
||
UMD PDU header, bit |
0 |
||
MAC |
MAC header, bit |
0 (NOTE ) |
|
MAC multiplexing |
Simulated by SS |
||
Layer 1 |
TrCH type |
FACH |
|
TB sizes, bit |
344 |
||
TFS |
TF0, bits |
0x344 |
|
TF1, bits |
1×344 |
||
TTI, ms |
40 |
||
Coding type |
TC |
||
CRC, bit |
16 |
||
Max number of bits/TTI after channel coding |
1092 |
||
Max number of bits/radio frame before rate matching |
273 |
||
RM attribute |
128 |
||
NOTE: The SS MAC layer must be configured not to add a MAC header so that the header can be added by the test case in order to create the necessary invalid values. |
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 [9].
– The UE is in MBSFN Idle mode with one activated service as specified in clause 7.6.4 of TS 34.108 [9]. The UE has selected (i.e. it is included in MBMS_ACTIVATED_SERVICES variable) a national service for which there will be a session starting on MBSFN Cell 31 (see TS 34.108 [9], clause 11.2.4).
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode available on UE Yes/No.
– Support of TDD or FDD transmit and receive functions available on UE Yes/No.
– Support of 3.84 Mcps TDD IMB receive only function available on UE Yes/No.
Test procedure
a) The UE is camping on Cell 1 and Cell 31. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 (no session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108 [9].
b) The SS sends ACTIVATE RB TEST MODE on the unicast carrier and the UE responds with ACTIVATE RB TEST MODE COMPLETE.
c) The SS sends CLOSE UE TEST LOOP to activate RLC SDU counting on Cell 31 MTCH (Transmission identity indicating the MBMS activated service).
d) The SS notifies on MCCH about the start of an MBMS session for one modification period. MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C4 (one PTM session starting) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108 [9].
e) MCCH messages are then transmitted by the SS on Cell 31 using MBMS configuration C2 (one PTM session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108 [9].
f) The SS waits for the UE to start reception of the MBMS data on MTCH according to the specified service activation time. The UE closes the test loop. The UE sends CLOSE UE TEST LOOP COMPLETE.
g) The SS transmits MAC PDUs containing RLC UM PDUs containing an octet string representing dummy traffic data, of size sufficient enough to fit in one RLC PDU of 336 bits, including the correct RLC UM header.
The MAC header shall be set as follows:
Field |
Value |
TCTF |
0110’B |
MBMS-Id |
1111’B |
h) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The SS waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE corresponds to zero received RLC SDUs. The SS records the value.
i) The SS again transmits MAC PDUs as in g) above, but this time uses a valid MBMS-Id of 1110’B. The sequence numbers in the RLC headers shall be identical with those sent in g).
j) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The SS waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE corresponds to > 0 received RLC SDUs
Expected sequence
Step |
Direction |
Carrier |
Message |
Comment |
|
UE |
SS |
||||
1 |
|
U |
ACTIVATE RB TEST MODE |
||
2 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
3 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated on Cell 31 for the selected national service on MTCH. |
|
4 |
|
M |
MBMS MCCH Message Configuration C4 |
Includes the national service activated at UE in the modified services list for one modification period. |
|
5 |
|
M |
MBMS MCCH Message Configuration C2 |
No modified services. One ongoing service corresponding to that activated at the UE. |
|
6 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE establishes the MTCH according to the activation time and closes the test loop. |
|
7 |
MAC PDU(TCTF, MBMS-Id, RLC UM PDU(SN=x)) |
Sent with reserved MBMS-Id = 1111’B |
|||
8 |
SS waits for T = 2 s |
||||
9 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
10 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is equal to zero. The SS records the value. |
|
11 |
MAC PDU(TCTF, MBMS-Id, RLC UM PDU(SN=x)) |
Sent with valid MBMS-Id = 1110’B |
|||
12 |
SS waits for T = 2 s |
||||
13 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
14 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. |
|
15 |
|
U |
OPEN UE TEST LOOP |
||
16 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
17 |
|
U |
DEACTIVATE RB TEST MODE |
||
18 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
Specific Message Contents
With the following exceptions, all messages have the same content as defined in TS 34.108 [9], clause 9.1.3 for the MBSFN carriers and in TS 34.108 [9] clause 9.1.1 or 9.1.2 for the unicast carrier:
MBMS COMMON P-T-M RB INFORMATION (Step 4 and Step 5) (3.84 Mcps)
Information Element |
Value/remark |
Version |
Message type |
|
Rel-6 |
RB information list |
1 entry in the list |
Rel-6 |
– RB identity |
|
Rel-6 |
– MBMS Common RB identity |
14 |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
Not Present |
|
– Max PDCP SN window size |
Not Present |
|
– PDCP PDU header |
absent |
|
– Header compression information |
Not Present |
|
– RLC info |
|
|
– DL UM RLC LI size |
7 |
|
– DL Duplication Avoidance and Reordering info |
Not Present |
|
– DL Out of sequence delivery info |
Not Present |
|
TrCh information for each TrCh |
1 entry in the list |
Rel-6 |
– Transport channel identity |
|
Rel-6 |
– MBMS Common TrCh identity |
1 |
|
– TFS |
|
|
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport format information |
|
|
– RLC Size |
Refer to TrCh parameters defined above |
|
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
|
– Number of Transport blocks |
Refer to TrCh paramters defined above |
|
– CHOICE mode |
FDD |
|
– CHOICE Logical channel list |
All |
|
– no data |
|
|
– Semi-static Transport Format information |
|
|
– Transmission time interval |
Refer to TrCh paramters defined above |
|
– Type of channel coding |
Turbo |
|
– Coding Rate |
Not present |
|
– Rate matching attribute |
Refer to TrCh paramters defined above |
|
– CRC size |
Refer to TrCh paramters defined above |
|
TrCh information for each CCTrCh |
Not Present (Default TFCS applies for each CCTrCh) |
Rel-6 |
PhyCh information |
1 entry in list |
Rel-6 |
– PhyCh identity |
|
Rel-6 |
– MBMS Common PhyCh identity |
23 |
|
CHOICE mode |
3.84 Mcps TDD IMB |
|
– Secondary CCPCH frame type 2 info |
|
Rel-8 |
– Sub-frame number |
2(check in 5.5.2) |
Rel-8 |
– Downlink channelisation codes |
|
Rel-8 |
– First channelisation code |
(1..15) or reference to 6.10 "parameter set" |
|
– Last channelisation code |
(1..15) or reference to 6.10 "parameter set" |
|
– CHOICE modulation |
16QAM(check in6.10 "parameter set") |
Rel-8 |
– CPICH secondary CCPCH power offset |
0dB |
Rel-8 |
LCR TDD MBSFN information |
Not present |
Rel-7 |
MBMS CURRENT CELL P-T-M RB INFORMATION (Step 4 and Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
S-CCPCH list |
Contains 1 S-CCPCH |
Rel-6 |
– S-CCPCH identity |
Not Present |
|
– Secondary CCPCH info |
23 |
|
– MBMS Soft Combining Timing Offset |
Not Present |
|
– TrCh information common for all TrCh |
Not Present (MD) |
|
– TrCH information list |
||
– TrCh information |
1 |
|
– RB information list |
||
– RB information |
||
– RB information |
14 |
|
– MBMS short transmission ID |
Reference to the service which is being provided on this RB. |
|
– MBMS logical channel identity |
1 |
|
– L1 combining status |
Not Present |
|
– MSCH configuration information |
Not Present |
|
S-CCPCH in SIB type 5 |
Not Present |
Rel-6 |
MBSFN TDM Info List |
Not Present |
Rel-7 |
7.1.1.10a.5 Test Requirement
1) At step 10 on each iteration, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number that corresponds to zero received RLC SDUs for Cell 31 MTCH.
2) At step 14 on each iteration, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number that corresponds to > 0 received RLC SDUs for Cell 31 MTCH.