7.2.4 MBMS
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
7.2.4.1 Void
7.2.4.2 MTCH duplicate avoidance and reordering / MBMS Broadcast Service
7.2.4.2.1 Definition
This test is applicable for Rel-6 UEs supporting MBMS broadcast services.
7.2.4.2.2 Conformance requirement
The receiving UM-RLC entity receives UMD PDUs through the configured logical channels from the lower layer. When duplicate avoidance and reordering is configured there may be one or more than one input from the lower layer. Inputs can be added or removed without changing the buffer contents, state variables or timers within the receiving UM RLC entity. Where duplicate avoidance and reordering is not configured there is only one input from the lower layer and it is not reconfigured.
When configured, duplicate avoidance and reordering is the first receive function that is applied to the input UMD PDU streams in the receiving UM RLC entity. It can only be configured in a UE, it is not used in UTRAN. It completes duplicate detection and re-ordering of the UMD PDUs that are received from the one or more inputs to produce a single ordered sequence of PDUs that is passed to the next in sequence RLC receiver function.
…
The duplicate avoidance and reordering function can be configured for use within a receiving UM RLC entity in the UE. It combines PDU sequences received from several sources and/or repeat transmissions from a single source to form a single ordered PDU sequence that is passed to the header removal and reassembly functions. It completes duplicate detection, discard and re-ordering based on the UM PDU sequence number. Where the UM RLC receives input from several sources, inputs can be added or removed without changing the buffer contents, state variables and timers associated with the duplicate avoidance and reordering function or any subsequent UM RLC function.
The duplicate avoidance and reordering function makes use of the state variable VR(UDR) and a receive window whose span is from VR(UDH) – DAR_Window_Size + 1 to VR(UDH) inclusively. For re-ordering the function uses a buffer for the temporary storage of PDUs.
For each PDU received, the duplicate avoidance and reordering function shall (in the following SN denotes the sequence number of each PDU):
Setting initial values of state variables:
– If the PDU is the first PDU received by the duplicate avoidance and reordering function:
– VR(UDH) is assigned the value SN;
– VR(UDR) is assigned the value VR(UDH) – DAR_Window_Size + 1.
Duplicate detection and re-ordering:
– if SN is within the receive window:
– if SN < VR(UDR) or if a PDU with sequence number SN is already stored in the buffer:
– the PDU shall be discarded;
– else:
– the PDU shall be stored in the buffer.
– if SN is outside of the receive window:
– the PDU shall be stored in the buffer;
– VR(UDH) shall be assigned the value SN, thereby advancing the receive window;
– for any stored PDUs with sequence numbers < VR(UDH) – DAR_Window_Size + 1, i.e. outside the receive window after its position is updated, remove the PDU from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
– if VR(UDR) < VR(UDH) – DAR_Window_Size + 1, i.e. VR(UDR) is outside the updated receive window;
– VR(UDR) shall be assigned the value VR(UDH) – DAR_Window_Size + 1.
– if PDU with sequence number VR(UDR) is stored in the buffer:
– for this PDU and any sequence of stored PDUs with consecutive sequence numbers starting at VR(UDR) + 1, remove the PDUs from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
– VR(UDR) shall be assigned the value of x + 1 where x is the sequence number of the highest numbered PDU that was delivered to the higher RLC function.
Timer operation:
– if Timer_DAR is not active when a PDU is stored by the duplicate avoidance and reordering function:
– Timer_DAR shall be started;
– VR(UDT) shall be assigned the value of the sequence number of the PDU.
– Timer_DAR shall be stopped:
– if the PDU with sequence number VR(UDT) is removed from the buffer before Timer_DAR expires.
– if Timer_DAR expires:
– for all stored PDUs with sequence numbers lower or equal to VR(UDT) and for any sequence of stored PDUs with consecutive sequence numbers starting at VR(UDT) + 1, remove the PDUs from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
– VR(UDR) shall be assigned the value x + 1 where x is the sequence number of the highest numbered PDU that was delivered to the higher RLC function.
– When Timer_DAR is stopped or expires, and there remain PDUs stored by the duplicate avoidance and reordering function:
– Timer_DAR shall be started;
– VR(UDT) shall be assigned the sequence number of the highest numbered stored PDU.
Reference
1) 3GPP TS 25.322 clauses 4.2.1.2.2, and 9.7.10
7.2.4.2.3 Test purpose
To verify the MTCH duplicate avoidance and reordering procedure
7.2.4.2.4 Method of test
Initial condition
System Simulator: 1 MBMS Cell
User Equipment:
The UE is in CELL_FACH state as specified in clause 7.6 of TS 34.108.
The UE is interested in the broadcast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
The following parameters are specific for this test case:
|
Parameter |
Value |
|
Timer_DAR |
5120 milliseconds |
|
DAR_Window_Size |
16 |
Related ICS/IXIT statements:
MBMS Broadcast service application available on UE yes/no
Test procedure
In this test procedure each SDU of size 322 octets will be formed of 4 RLC PDUs. The first of the 4 PDUs making up one SDU is of size 80 octets + 1 octet LI indicating the start of a PDU (SN= 0, 4, 8..). Every 4th PDU making up one SDU is of size 80 octets + 1 octet LI indicating the end of the SDU (SN=3, 7, 11..). The 2nd and 3rd PDUs are of size 81 octets.
a) SS indicates on MICH and modifies the MCCH to indicate the start of service 1. The UE begins reception of the MBMS service using the 64.8kbps radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.3.5.
b) The radio bearer is placed into UE test loop mode 3.
c) The SS transmits PDUs with RLC sequence number = 3, 3, 2, 2, 1, 1, 0, 0, 19
d) The SS checks that the loopback mode 3 SDU count = 1. (The purpose of SN=19 is in order that the 4 PDUS with sequence numbers < VR(UDH) – DAR_Window_Size + 1, are delivered to higher RLC function, and these 4 PDUs form 1 SDU)
e) The SS transmits PDUs with the RLC sequence number = 19, 18, 17, 16, 15, 14, 13, 12
f) The SS waits 5s for Timer_DAR to expire. PDUs sent in step c are submitted to the higher RLC function. UE sets V(UDR) = 20.
g) The SS checks that the loopback mode 3 SDU count = 3. (2 more SDUs are received, once Timer_DAR expires and the UE empties the DAR buffer)
h) The SS transmits PDUs with the RLC sequence number = 7, 6, 5, 4, 3, 2, 1, 0
i) The SS checks that the loopback mode 3 SDU count = 3. (the data PDUs with SN of 7, 6, 5, 4 in step h is discarded in the UE, because VR(UDR) shall be assigned the value 20. The data PDUs with SN 3, 2, 1, 0 are stored in the buffer because these are inside the new receive window)
j) The SS transmits PDUs with the RLC sequence number = 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12
k) The SS checks that the loopback mode 3 SDU count = 8. (Four more complete SDU’s are formed from RLC PDUs with SN of 12, 13, 14, 15 and 16, 17, 18, 19 and 20, 21, 22, 23 and 24, 25, 26, 27. One more complete SDU is formed and delivered from the data stored in step h with the PDUs with SN 0, 1, 2, 3)
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
ACTIVATE RB TEST MODE |
||
|
2 |
|
ACTIVATE RB TEST MODE COMPLETE |
||
|
3 |
|
MBMS MODIFIED SERVICES INFORMATION |
MCCH message combination C4 for 1 modification period, then combination C2. The SS waits for the UE to establish the 64.8kbps radio bearer configuration as specified in TS 34.108 clause 6.10.2.4.3.5. |
|
|
4 |
|
CLOSE UE TEST LOOP |
UE test loop mode 3 setup |
|
|
5 |
|
CLOSE UE TEST LOOP COMPLETE |
||
|
6 |
|
9 * RLC PDUs |
SN = 3, 3, 2, 2, 1, 1, 0, 0, 19 |
|
|
7 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
8 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU count = 1. |
|
|
9 |
|
8 * RLC PDUs |
SN = 19, 18, 17, 16, 15, 14, 13, 12 |
|
|
10 |
SS waits 5120 ms for Timer_DAR to expire |
|||
|
11 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
12 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU count = 3. |
|
|
13 |
|
8 * RLC PDUs |
SN = 7, 6, 5, 4, 3, 2, 1, 0 |
|
|
14 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
15 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU count = 3. |
|
|
16 |
|
16 * RLC PDUs |
SN = 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12 |
|
|
17 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
18 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU count = 8. |
|
|
19 |
|
OPEN UE TEST LOOP |
||
|
20 |
|
OPEN UE TEST LOOP COMPLETE |
||
Specific message contents
None.
7.2.4.2.5 Test requirements
In step d the UE shall report the loopback mode 3 SDU count as 1.
In steps g and i the UE shall report the loopback mode 3 SDU count as 3.
In step k the UE shall report the loopback mode 3 SDU count as 8.
7.2.4.2a MTCH duplicate avoidance and reordering / MBSFN (FDD)
7.2.4.2a.1 Definition
This test is applicable for Rel-7 UEs supporting MBSFN for FDD.
7.2.4.2a.2 Conformance requirement
The receiving UM-RLC entity receives UMD PDUs through the configured logical channels from the lower layer. When duplicate avoidance and reordering is configured there may be one or more than one input from the lower layer. Inputs can be added or removed without changing the buffer contents, state variables or timers within the receiving UM RLC entity. Where duplicate avoidance and reordering is not configured there is only one input from the lower layer and it is not reconfigured.
When configured, duplicate avoidance and reordering is the first receive function that is applied to the input UMD PDU streams in the receiving UM RLC entity. It can only be configured in a UE, it is not used in UTRAN. It completes duplicate detection and re-ordering of the UMD PDUs that are received from the one or more inputs to produce a single ordered sequence of PDUs that is passed to the next in sequence RLC receiver function.
…
The duplicate avoidance and reordering function can be configured for use within a receiving UM RLC entity in the UE. It combines PDU sequences received from several sources and/or repeat transmissions from a single source to form a single ordered PDU sequence that is passed to the header removal and reassembly functions. It completes duplicate detection, discard and re-ordering based on the UM PDU sequence number. Where the UM RLC receives input from several sources, inputs can be added or removed without changing the buffer contents, state variables and timers associated with the duplicate avoidance and reordering function or any subsequent UM RLC function.
The duplicate avoidance and reordering function makes use of the state variable VR(UDR) and a receive window whose span is from VR(UDH) – DAR_Window_Size + 1 to VR(UDH) inclusively. For re-ordering the function uses a buffer for the temporary storage of PDUs.
For each PDU received, the duplicate avoidance and reordering function shall (in the following SN denotes the sequence number of each PDU):
Setting initial values of state variables:
– If the PDU is the first PDU received by the duplicate avoidance and reordering function:
– VR(UDH) is assigned the value SN;
– VR(UDR) is assigned the value VR(UDH) – DAR_Window_Size + 1.
Duplicate detection and re-ordering:
– if SN is within the receive window:
– if SN < VR(UDR) or if a PDU with sequence number SN is already stored in the buffer:
– the PDU shall be discarded;
– else:
– the PDU shall be stored in the buffer.
– if SN is outside of the receive window:
– the PDU shall be stored in the buffer;
– VR(UDH) shall be assigned the value SN, thereby advancing the receive window;
– for any stored PDUs with sequence numbers < VR(UDH) – DAR_Window_Size + 1, i.e. outside the receive window after its position is updated, remove the PDU from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
– if VR(UDR) < VR(UDH) – DAR_Window_Size + 1, i.e. VR(UDR) is outside the updated receive window;
– VR(UDR) shall be assigned the value VR(UDH) – DAR_Window_Size + 1.
– if PDU with sequence number VR(UDR) is stored in the buffer:
– for this PDU and any sequence of stored PDUs with consecutive sequence numbers starting at VR(UDR) + 1, remove the PDUs from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
– VR(UDR) shall be assigned the value of x + 1 where x is the sequence number of the highest numbered PDU that was delivered to the higher RLC function.
Timer operation:
– if Timer_DAR is not active when a PDU is stored by the duplicate avoidance and reordering function:
– Timer_DAR shall be started;
– VR(UDT) shall be assigned the value of the sequence number of the PDU.
– Timer_DAR shall be stopped:
– if the PDU with sequence number VR(UDT) is removed from the buffer before Timer_DAR expires.
– if Timer_DAR expires:
– for all stored PDUs with sequence numbers lower or equal to VR(UDT) and for any sequence of stored PDUs with consecutive sequence numbers starting at VR(UDT) + 1, remove the PDUs from the buffer and deliver them to the higher RLC function to perform the actions specified in subclause 11.2.3;
– VR(UDR) shall be assigned the value x + 1 where x is the sequence number of the highest numbered PDU that was delivered to the higher RLC function.
– When Timer_DAR is stopped or expires, and there remain PDUs stored by the duplicate avoidance and reordering function:
– Timer_DAR shall be started;
– VR(UDT) shall be assigned the sequence number of the highest numbered stored PDU.
Reference
1) 3GPP TS 25.322 clauses 4.2.1.2.2, and 9.7.10
7.2.4.2a.3 Test purpose
To verify the MTCH duplicate avoidance and reordering procedure
7.2.4.2a.4 Method of test
Initial condition
System Simulator: 1 MBMS Cell
User Equipment:
The UE is in CELL_FACH state as specified in clause 7.6 of TS 34.108.
The UE is interested in the broadcast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
The following parameters are specific for this test case:
|
Parameter |
Value |
|
Timer_DAR |
5120 milliseconds |
|
DAR_Window_Size |
16 |
Related ICS/IXIT statements:
MBMS Broadcast service application available on UE yes/no
Test procedure
In this test procedure each SDU of size 322 octets will be formed of 4 RLC PDUs. The first of the 4 PDUs making up one SDU is of size 80 octets + 1 octet LI indicating the start of a PDU (SN= 0, 4, 8..). Every 4th PDU making up one SDU is of size 80 octets + 1 octet LI indicating the end of the SDU (SN=3, 7, 11..). The 2nd and 3rd PDUs are of size 81 octets.
a) SS indicates on MICH and modifies the MCCH to indicate the start of service 1. The UE begins reception of the MBMS service using the 64.8kbps radio bearer configuration as specified in TS 34.108, clause 6.10.2.4.3.5.
b) The radio bearer is placed into UE test loop mode 3.
c) The SS transmits PDUs with RLC sequence number = 3, 3, 2, 2, 1, 1, 0, 0, 19
d) The SS checks that the loopback mode 3 SDU count = 1. (The purpose of SN=19 is in order that the 4 PDUS with sequence numbers < VR(UDH) – DAR_Window_Size + 1, are delivered to higher RLC function, and these 4 PDUs form 1 SDU)
e) The SS transmits PDUs with the RLC sequence number = 19, 18, 17, 16, 15, 14, 13, 12
f) The SS waits 5s for Timer_DAR to expire. PDUs sent in step c are submitted to the higher RLC function. UE sets V(UDR) = 20.
g) The SS checks that the loopback mode 3 SDU count = 3. (2 more SDUs are received, once Timer_DAR expires and the UE empties the DAR buffer)
h) The SS transmits PDUs with the RLC sequence number = 7, 6, 5, 4, 3, 2, 1, 0
i) The SS checks that the loopback mode 3 SDU count = 3. (the data PDUs with SN of 7, 6, 5, 4 in step h is discarded in the UE, because VR(UDR) shall be assigned the value 20. The data PDUs with SN 3, 2, 1, 0 are stored in the buffer because these are inside the new receive window)
j) The SS transmits PDUs with the RLC sequence number = 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12
k) The SS checks that the loopback mode 3 SDU count = 8. (Four more complete SDU’s are formed from RLC PDUs with SN of 12, 13, 14, 15 and 16, 17, 18, 19 and 20, 21, 22, 23 and 24, 25, 26, 27. One more complete SDU is formed and delivered from the data stored in step h with the PDUs with SN 0, 1, 2, 3)
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
ACTIVATE RB TEST MODE |
||
|
2 |
|
ACTIVATE RB TEST MODE COMPLETE |
||
|
3 |
|
MBMS MODIFIED SERVICES INFORMATION |
MCCH message combination C4 for 1 modification period, then combination C2. The SS waits for the UE to establish the 64.8kbps radio bearer configuration as specified in TS 34.108 clause 6.10.2.4.3.5. |
|
|
4 |
|
CLOSE UE TEST LOOP |
UE test loop mode 3 setup |
|
|
5 |
|
CLOSE UE TEST LOOP COMPLETE |
||
|
6 |
|
9 * RLC PDUs |
SN = 3, 3, 2, 2, 1, 1, 0, 0, 19 |
|
|
7 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
8 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU count = 1. |
|
|
9 |
|
8 * RLC PDUs |
SN = 19, 18, 17, 16, 15, 14, 13, 12 |
|
|
10 |
SS waits 5120 ms for Timer_DAR to expire |
|||
|
11 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
12 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU count = 3. |
|
|
13 |
|
8 * RLC PDUs |
SN = 7, 6, 5, 4, 3, 2, 1, 0 |
|
|
14 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
15 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU count = 3. |
|
|
16 |
|
16 * RLC PDUs |
SN = 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12 |
|
|
17 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
18 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU count = 8. |
|
|
19 |
|
OPEN UE TEST LOOP |
||
|
20 |
|
OPEN UE TEST LOOP COMPLETE |
||
Specific message contents
None.
7.2.4.2a.5 Test requirements
In step d the UE shall report the loopback mode 3 SDU count as 1.
In steps g and i the UE shall report the loopback mode 3 SDU count as 3.
In step k the UE shall report the loopback mode 3 SDU count as 8.
7.2.4.2b-l Void
7.2.4.2m MTCH duplicate avoidance and reordering / MBMS Multicast Service
7.2.4.2m.1 Definition
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
7.2.4.2m.2 Conformance requirement
Same conformance requirement as in clause 7.2.4.2.2.
Reference
1) 3GPP TS 25.322 clauses 4.2.1.2.2, and 9.7.10
7.2.4.2m.3 Test purpose
Same test purpose as in clause 7.2.4.2.3.
7.2.4.2m.4 Method of test
Initial condition
System Simulator: 1 MBMS Cell
User Equipment:
The UE is in Idle Mode as specified in clause 7.6 of TS 34.108.
The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Same setting of Timer_DAR and DAR_Window_Size as in clause 7.2.4.2.4.
Related ICS/IXIT statements:
MBMS Multicast service application available on UE yes/no
Test procedure
Same test purpose as in clause 7.2.4.2.4.
Expected Sequence
Same expected sequence as in clause 7.2.4.2.4.
Specific message contents
None.
7.2.4.2m.5 Test requirements
Same test requirements as in clause 7.2.4.2.5.
7.2.4.3 MCCH Out Of Sequence Delivery handling / MBMS Broadcast Service
7.2.4.3.1 Definition
This test is applicable for Rel-6 UEs supporting MBMS broadcast services.
7.2.4.3.2 Conformance requirement
To enable the recovery of SDUs from UMD PDUs that are received in different transmissions the receiving function shall store PDUs until all SDUs that are associated with the PDU can be reconstructed or until they are discarded in accordance with the procedures described below. SDUs are transferred to the upper layers as soon as all PDUs that contain the segments of the SDU and the "Length Indicator" indicating the end of the SDU have been received.
Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall for each PDU (in the following SN denotes the sequence number of each PDU):
– If the PDU is the first PDU received (after the receiving entity is established or re-established or after Timer_OSD expires):
– VR(UOH) shall be assigned the value SN-1.
– if VR(UOH) > SN > VR(UOH) – OSD_Window_Size then:
– if a PDU with sequence number SN is already stored:
– discard the PDU;
– else:
– store the PDU in sequence number order.
– else:
– VR(UOH) shall be assigned the value SN, thereby advancing the storage window;
– store the PDU in sequence number order;
– remove from storage any PDUs whose sequence numbers, SN, are outside of the storage window VR(UOH) > SN > VR(UOH) – OSD_Window_Size;
– if Timer_OSD is active then Timer_OSD shall be stopped;
– Timer_OSD shall be started.
– if a PDU with sequence number SN was stored:
– if the PDU contains one or more complete SDUs and/or if the PDU contains segments of SDUs for which all the remaining segments and length indicators are contained in stored PDUs:
– re-assemble the SDUs;
– submit the SDUs to upper layers through the UM-SAP;
– remove from storage any PDUs which do not contain any segment of a SDU that has not been re-assembled, and do not contain one of the special length indicators "0000 000", "0000 0000 0000 000" or "1111 1111 1111 011" that indicate the end of a SDU that has not been re-assembled.
NOTE 0: If PDUs are removed from storage after SDU recovery then retransmitted PDUs may result in the duplicate transfer of SDUs to the higher layers.
– if Timer_OSD expires:
– remove from storage all stored PDUs.
NOTE 1: When configured for out of sequence SDU delivery, the transmitter should consider the possibility that a loss of a number of 128 OSD_Window_Size consecutively numbered PDUs may result in an undetected protocol error in the receiver, if the transmit state variable VT(US), at the end of a time interval equal to the duration of Timer_OSD, is greater than 128 + SN OSD_Window_Size + 1, where SN is the lowest sequence number of any PDU transmitted or retransmitted within that time interval.
NOTE 2: The transmitter should not concatenate within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with SDUs or fractions of SDUs that contain other MCCH message types.
NOTE 3: SDUs are contained within consecutively numbered PDUs. To enable SDUs containing MBMS Access Information messages to be transmitted at their designated times, the transmitter may transmit PDUs out of sequence order.
NOTE 4: The transmitter should not transmit within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with the special length indicator "0000 000","0000 0000 0000 000", and "1111 1111 1111 011".
Reference
1) 3GPP TS 25.322, clause 11.2.3.2
7.2.4.3.3 Test purpose
To verify MCCH Out Of Sequence Delivery handling.
7.2.4.3.4 Method of test
Initial condition
System Simulator: 1 MBMS Cell.
User Equipment:
The UE is in CELL_FACH state as specified in clause 7.6 of TS 34.108, with the following exception: MCCH Default2 scheduling as specified in TS 34.108 clause 11.1
The UE has a valid IMSI.
The UE is interested in the broadcast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
The following parameters are specific for this test case:
|
Parameter |
Value |
|
OSD_Window_Size |
64 (to contain the entire MBMS CONTROL INFORMATION on MCCH) |
Related ICS/IXIT statements:
MBMS Broadcast service application available on UE yes/no
Test procedure
a) The SS commands UE into RB Test Mode.
b) SS indicates on MICH and modifies the MCCH to indicate the start of service 1. In this step the SS shall send MCCH information as follows:
The RLC is configured at the SS as TM mode. This is in order to be able to replace encoded PDUs and header information with an invalid LI .
On the first repetition period for all critical MCCH messages, only the odd numbered RLC PDU SN are transmitted correctly, an invalid LI is inserted into the RLC header of the even numbered PDUs.
On the second repetition period for all critical MCCH messages, only the even numbered RLC PDU SN are transmitted correctly, an invalid LI is inserted into the RLC header of the odd numbered PDUs.
SS waits for the UE to begin reception of the MBMS service using the 64.8kbps radio bearer configuration specified in TS 34.108, clause 6.10.2.4.3.5.
c) The radio bearer is placed into UE test loop mode 3.
d) The SS transmits 10 * RLC SDUs of size 80 octets. (PDU is 80 octets + 1 octet special LI)
e) The SS checks that the loopback mode 3 SDU count is greater than 0.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
ACTIVATE RB TEST MODE |
||
|
2 |
|
ACTIVATE RB TEST MODE COMPLETE |
||
|
3 |
|
MCCH MESSAGES |
For all MCCH messages using message combination C4 for 1 modification period: on the first repetition period, only the odd numbered RLC PDU SN are transmitted correctly. On the second repetition period only the even numbered RLC PDU SN are transmitted correctly. Other PDUs have an invalid LI in the RLC header. Those messages requiring specific contents are shown in steps 4-6, other messages have the default contents. |
|
|
4 |
|
MBMS MODIFIED SERVICES INFORMATION |
SS indicates to the UE to Acquire PTM RB info. |
|
|
5 |
|
MBMS COMMON P-T-M RB INFORMATION |
Contains configuration for the 64.8kbps radio bearer configuration as specified in TS 34.108 clause 6.10.2.4.3.5. |
|
|
6 |
|
MBMS Current Cell p-t-m rb Information |
Indicates the radio bearer configuration to be used for reception of the service. The SS waits for the UE to establish the MTCH, according to the activation time. |
|
|
7 |
|
MCCH MESSAGES |
SS transmits PDUs using message combination C2. For all MCCH messages using message combination C2 for 1 modification period: on the first repetition period, only the odd numbered RLC PDU SN are transmitted correctly. On the second repetition period only the even numbered RLC PDU SN are transmitted correctly. Other PDUs have an invalid LI in the RLC header. After this modification period, the SS stops sending MCCH messages. |
|
|
8 |
|
CLOSE UE TEST LOOP |
UE test loop mode 3 setup |
|
|
9 |
|
CLOSE UE TEST LOOP COMPLETE |
||
|
10 |
|
10 * RLC SDU |
SS sends 10*RLC SDUs on MTCH |
|
|
11 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
12 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU counter response > 0. |
|
|
13 |
|
OPEN UE TEST LOOP |
||
|
14 |
|
OPEN UE TEST LOOP COMPLETE |
||
Specific message contents
Those PDUs indicated to have an invalid LI in the RLC header, shall encode the LI to be invalid according to TS 25.322 clause 11.2.4.2.
7.2.4.3.5 Test requirements
In step e the UE shall report the loopback mode 3 SDU count to be greater than 0.
7.2.4.3a MCCH Out Of Sequence Delivery handling / MBSFN (FDD)
7.2.4.3a.1 Definition
This test is applicable for Rel-7 UEs supporting MBSFN for FDD.
7.2.4.3a.2 Conformance requirement
To enable the recovery of SDUs from UMD PDUs that are received in different transmissions the receiving function shall store PDUs until all SDUs that are associated with the PDU can be reconstructed or until they are discarded in accordance with the procedures described below. SDUs are transferred to the upper layers as soon as all PDUs that contain the segments of the SDU and the "Length Indicator" indicating the end of the SDU have been received.
Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall for each PDU (in the following SN denotes the sequence number of each PDU):
– If the PDU is the first PDU received (after the receiving entity is established or re-established or after Timer_OSD expires):
– VR(UOH) shall be assigned the value SN-1.
– if VR(UOH) > SN > VR(UOH) – OSD_Window_Size then:
– if a PDU with sequence number SN is already stored:
– discard the PDU;
– else:
– store the PDU in sequence number order.
– else:
– VR(UOH) shall be assigned the value SN, thereby advancing the storage window;
– store the PDU in sequence number order;
– remove from storage any PDUs whose sequence numbers, SN, are outside of the storage window VR(UOH) > SN > VR(UOH) – OSD_Window_Size;
– if Timer_OSD is active then Timer_OSD shall be stopped;
– Timer_OSD shall be started.
– if a PDU with sequence number SN was stored:
– if the PDU contains one or more complete SDUs and/or if the PDU contains segments of SDUs for which all the remaining segments and length indicators are contained in stored PDUs:
– re-assemble the SDUs;
– submit the SDUs to upper layers through the UM-SAP;
– remove from storage any PDUs which do not contain any segment of a SDU that has not been re-assembled, and do not contain one of the special length indicators "0000 000", "0000 0000 0000 000" or "1111 1111 1111 011" that indicate the end of a SDU that has not been re-assembled.
NOTE 0: If PDUs are removed from storage after SDU recovery then retransmitted PDUs may result in the duplicate transfer of SDUs to the higher layers.
– if Timer_OSD expires:
– remove from storage all stored PDUs.
NOTE 1: When configured for out of sequence SDU delivery, the transmitter should consider the possibility that a loss of a number of 128 OSD_Window_Size consecutively numbered PDUs may result in an undetected protocol error in the receiver, if the transmit state variable VT(US), at the end of a time interval equal to the duration of Timer_OSD, is greater than 128 + SN OSD_Window_Size + 1, where SN is the lowest sequence number of any PDU transmitted or retransmitted within that time interval.
NOTE 2: The transmitter should not concatenate within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with SDUs or fractions of SDUs that contain other MCCH message types.
NOTE 3: SDUs are contained within consecutively numbered PDUs. To enable SDUs containing MBMS Access Information messages to be transmitted at their designated times, the transmitter may transmit PDUs out of sequence order.
NOTE 4: The transmitter should not transmit within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with the special length indicator "0000 000","0000 0000 0000 000", and "1111 1111 1111 011".
Reference
1) 3GPP TS 25.322, clause 11.2.3.2
7.2.4.3a.3 Test purpose
To verify MCCH Out Of Sequence Delivery handling.
7.2.4.3a.4 Method of test
Initial condition
System Simulator: 1 MBMS Cell.
User Equipment:
The UE is in CELL_FACH state as specified in clause 7.6 of TS 34.108, with the following exception: MCCH Default2 scheduling as specified in TS 34.108 clause 11.1
The UE has a valid IMSI.
The UE is interested in the broadcast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
The following parameters are specific for this test case:
|
Parameter |
Value |
|
OSD_Window_Size |
64 (to contain the entire MBMS CONTROL INFORMATION on MCCH) |
Related ICS/IXIT statements:
MBMS Broadcast service application available on UE yes/no
Test procedure
a) The SS commands UE into RB Test Mode.
b) SS indicates on MICH and modifies the MCCH to indicate the start of service 1. In this step the SS shall send MCCH information as follows:
The RLC is configured at the SS as TM mode. This is in order to be able to replace encoded PDUs and header information with an invalid LI .
On the first repetition period for all critical MCCH messages, only the odd numbered RLC PDU SN are transmitted correctly, an invalid LI is inserted into the RLC header of the even numbered PDUs.
On the second repetition period for all critical MCCH messages, only the even numbered RLC PDU SN are transmitted correctly, an invalid LI is inserted into the RLC header of the odd numbered PDUs.
SS waits for the UE to begin reception of the MBMS service using the 64.8kbps radio bearer configuration specified in TS 34.108, clause 6.10.2.4.3.5.
c) The radio bearer is placed into UE test loop mode 3.
d) The SS transmits 10 * RLC SDUs of size 80 octets. (PDU is 80 octets + 1 octet special LI)
e) The SS checks that the loopback mode 3 SDU count is greater than 0.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
ACTIVATE RB TEST MODE |
||
|
2 |
|
ACTIVATE RB TEST MODE COMPLETE |
||
|
3 |
|
MCCH MESSAGES |
For all MCCH messages using message combination C4 for 1 modification period: on the first repetition period, only the odd numbered RLC PDU SN are transmitted correctly. On the second repetition period only the even numbered RLC PDU SN are transmitted correctly. Other PDUs have an invalid LI in the RLC header. Those messages requiring specific contents are shown in steps 4-6, other messages have the default contents. |
|
|
4 |
|
MBMS MODIFIED SERVICES INFORMATION |
SS indicates to the UE to Acquire PTM RB info. |
|
|
5 |
|
MBMS COMMON P-T-M RB INFORMATION |
Contains configuration for the 64.8kbps radio bearer configuration as specified in TS 34.108 clause 6.10.2.4.3.5. |
|
|
6 |
|
MBMS Current Cell p-t-m rb Information |
Indicates the radio bearer configuration to be used for reception of the service. The SS waits for the UE to establish the MTCH, according to the activation time. |
|
|
7 |
|
MCCH MESSAGES |
SS transmits PDUs using message combination C2. For all MCCH messages using message combination C2 for 1 modification period: on the first repetition period, only the odd numbered RLC PDU SN are transmitted correctly. On the second repetition period only the even numbered RLC PDU SN are transmitted correctly. Other PDUs have an invalid LI in the RLC header. After this modification period, the SS stops sending MCCH messages. |
|
|
8 |
|
CLOSE UE TEST LOOP |
UE test loop mode 3 setup |
|
|
9 |
|
CLOSE UE TEST LOOP COMPLETE |
||
|
10 |
|
10 * RLC SDU |
SS sends 10*RLC SDUs on MTCH |
|
|
11 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
|
12 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
SDU counter response > 0. |
|
|
13 |
|
OPEN UE TEST LOOP |
||
|
14 |
|
OPEN UE TEST LOOP COMPLETE |
||
Specific message contents
Those PDUs indicated to have an invalid LI in the RLC header, shall encode the LI to be invalid according to TS 25.322 clause 11.2.4.2.
7.2.4.3a.5 Test requirements
In step e the UE shall report the loopback mode 3 SDU count to be greater than 0.
7.2.4.3b-l Void
7.2.4.3m MCCH Out Of Sequence Delivery handling / MBMS Multicast Service
7.2.4.3m.1 Definition
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
7.2.4.3m.2 Conformance requirement
Same conformance requirement as in clause 7.2.4.3.2.
Reference
1) 3GPP TS 25.322, clause 11.2.3.2
7.2.4.3m.3 Test purpose
Same test purpose as in clause 7.2.4.3.3.
7.2.4.3m.4 Method of test
Initial condition
System Simulator: 1 MBMS Cell.
User Equipment:
The UE is in CELL_FACH state as specified in clause 7.6 of TS 34.108, with the following exception: MCCH Default2 scheduling as specified in TS 34.108 clause 11.1
The UE has a valid IMSI.
The UE has joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Same setting of OSD_Window_Size as in clause 7.2.4.3.4.
Related ICS/IXIT statements:
MBMS Multicast service application available on UE yes/no
Test procedure
Same test procedure as in clause 7.2.4.3.4.
Specific message contents
Same specific message contents in clause 7.2.4.3.4.
7.2.4.3m.5 Test requirements
Same test requirements as in clause 7.2.4.3.5.
7.2.4.3n-r Void
7.2.4.3s MCCH Out Of Sequence Delivery handling / MBMS Broadcast Service (TDD MBSFN) (non-IMB)
7.2.4.3s.1 Definition
This test is applicable for Rel-7 UEs supporting MBMS broadcast services over MBSFN.
7.2.4.3s.2 Conformance requirement
To enable the recovery of SDUs from UMD PDUs that are received in different transmissions the receiving function shall store PDUs until all SDUs that are associated with the PDU can be reconstructed or until they are discarded in accordance with the procedures described below. SDUs are transferred to the upper layers as soon as all PDUs that contain the segments of the SDU and the "Length Indicator" indicating the end of the SDU have been received.
Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall for each PDU (in the following SN denotes the sequence number of each PDU):
– If the PDU is the first PDU received (after the receiving entity is established or re-established or after Timer_OSD expires):
– VR(UOH) shall be assigned the value SN-1.
– if VR(UOH) > SN > VR(UOH) – OSD_Window_Size then:
– if a PDU with sequence number SN is already stored:
– discard the PDU;
– else:
– store the PDU in sequence number order.
– else:
– VR(UOH) shall be assigned the value SN, thereby advancing the storage window;
– store the PDU in sequence number order;
– remove from storage any PDUs whose sequence numbers, SN, are outside of the storage window VR(UOH) > SN > VR(UOH) – OSD_Window_Size;
– if Timer_OSD is active then Timer_OSD shall be stopped;
– Timer_OSD shall be started.
– if a PDU with sequence number SN was stored:
– if the PDU contains one or more complete SDUs and/or if the PDU contains segments of SDUs for which all the remaining segments and length indicators are contained in stored PDUs:
– re-assemble the SDUs;
– submit the SDUs to upper layers through the UM-SAP;
– remove from storage any PDUs which do not contain any segment of a SDU that has not been re-assembled, and do not contain one of the special length indicators "0000 000", "0000 0000 0000 000" or "1111 1111 1111 011" that indicate the end of a SDU that has not been re-assembled.
NOTE 0: If PDUs are removed from storage after SDU recovery then retransmitted PDUs may result in the duplicate transfer of SDUs to the higher layers.
– if Timer_OSD expires:
– remove from storage all stored PDUs.
NOTE 1: When configured for out of sequence SDU delivery, the transmitter should consider the possibility that a loss of a number of 128 OSD_Window_Size consecutively numbered PDUs may result in an undetected protocol error in the receiver, if the transmit state variable VT(US), at the end of a time interval equal to the duration of Timer_OSD, is greater than 128 + SN OSD_Window_Size + 1, where SN is the lowest sequence number of any PDU transmitted or retransmitted within that time interval.
NOTE 2: The transmitter should not concatenate within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with SDUs or fractions of SDUs that contain other MCCH message types.
NOTE 3: SDUs are contained within consecutively numbered PDUs. To enable SDUs containing MBMS Access Information messages to be transmitted at their designated times, the transmitter may transmit PDUs out of sequence order.
NOTE 4: The transmitter should not transmit within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with the special length indicator "0000 000","0000 0000 0000 000", and "1111 1111 1111 011".
Reference
1) 3GPP TS 25.322, clause 11.2.3.2
7.2.4.3s.3 Test purpose
To verify MCCH Out Of Sequence Delivery handling.
7.2.4.3s.4 Method of test
Initial condition
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 Default2 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.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
OSD_Window_Size |
64 (to contain the entire MBMS CONTROL INFORMATION on MCCH) |
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) SS indicates on MICH and modifies the MCCH to indicate the start of the national service. In this step the SS shall send MCCH information as follows:
The RLC is configured at the SS as TM mode. This is in order to be able to replace encoded PDUs and header information with an invalid LI .
On the first repetition period for all critical MCCH messages, only the odd numbered RLC PDU SN are transmitted correctly, an invalid LI is inserted into the RLC header of the even numbered PDUs.
On the second repetition period for all critical MCCH messages, only the even numbered RLC PDU SN are transmitted correctly, an invalid LI is inserted into the RLC header of the odd numbered PDUs.
e) SS waits for the UE to begin reception of the MBMS service using the 8kbps radio bearer configuration specified in TS 34.108, clause 6.11.1c (3.84 Mcps TDD) or 6.11.1d (7.68 Mcps TDD) or 6.11.5.4.4.13 (1.28 Mcps TDD). The UE closes the test loop. The UE sends CLOSE UE TEST LOOP COMPLETE.
f) The SS transmits 10 * RLC SDUs of size 40 octets. (PDU is 40 octets + 1 octet special LI)
g) 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.
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 |
For all MCCH messages using message combination C4 for 1 modification period: on the first repetition period, only the odd numbered RLC PDU SN are transmitted correctly. On the second repetition period only the even numbered RLC PDU SN are transmitted correctly. Other PDUs have an invalid LI in the RLC header. Those messages requiring specific contents are shown in steps 6-8, other messages have the default contents. |
|
|
5 |
|
M |
MBMS MODIFIED SERVICES INFORMATION |
Includes the national service activated at UE in the modified services list for one modification period. SS indicates to the UE to Acquire PTM RB info. |
|
|
6 |
|
M |
MBMS COMMON P-T-M RB INFORMATION |
Contains configuration for the 8kbps radio bearer configuration |
|
|
7 |
|
M |
MBMS Current Cell p-t-m rb Information |
Indicates the radio bearer configuration to be used for reception of the service. |
|
|
8 |
|
M |
MBMS MCCH Message Configuration C2 |
SS transmits PDUs using message combination C2. For all MCCH messages using message combination C2 for 1 modification period: on the first repetition period, only the odd numbered RLC PDU SN are transmitted correctly. On the second repetition period only the even numbered RLC PDU SN are transmitted correctly. Other PDUs have an invalid LI in the RLC header. After this modification period, the SS stops sending MCCH messages. |
|
|
9 |
|
M |
MBMS COMMON P-T-M RB INFORMATION |
Contains configuration for the 8kbps radio bearer configuration |
|
|
10 |
|
M |
MBMS Current Cell p-t-m rb Information |
Indicates the radio bearer configuration to be used for reception of the service. |
|
|
11 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE establishes the MTCH according to the activation time and closes the test loop. |
|
|
12 |
|
M |
10 * RLC SDU |
SS sends 10*RLC SDUs on MTCH |
|
|
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
Those PDUs indicated to have an invalid LI in the RLC header, shall encode the LI to be invalid according to TS 25.322 clause 11.2.4.2.
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 6 and Step 9) (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 |
Reference to clause 6.11.1c |
|
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
|
– Number of Transport blocks |
Reference to clause 6.11.1c |
|
|
– CHOICE mode |
TDD |
|
|
– Transmission Time Interval |
Not Present |
|
|
– CHOICE Logical Channel List |
ALL |
|
|
– no data |
||
|
– Semi-static Transport Format information |
||
|
– Transmission time interval |
Reference to clause 6.11.1c |
|
|
– Type of channel coding |
Turbo |
|
|
– Coding Rate |
Not Present |
|
|
– Rate matching attribute |
Reference to clause 6.11.1c |
|
|
– CRC size |
Reference to clause 6.11.1c |
|
|
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 6 and Step 9) (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 |
Reference to clause 6.11.1d |
|
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
|
– Number of Transport blocks |
Reference to clause 6.11.1d |
|
|
– CHOICE mode |
TDD |
|
|
– Transmission Time Interval |
Not Present |
|
|
– CHOICE Logical Channel List |
ALL |
|
|
– no data |
||
|
– Semi-static Transport Format information |
||
|
– Transmission time interval |
Reference to clause 6.11.1d |
|
|
– Type of channel coding |
Turbo |
|
|
– Coding Rate |
Not Present |
|
|
– Rate matching attribute |
Reference to clause 6.11.1d |
|
|
– CRC size |
Reference to clause 6.11.1d |
|
|
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 6 and Step 9) (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 |
Reference to clause 6.11.5.4.4.13 |
|
|
– Number of TBs and TTI List |
(This IE is repeated for each TFI) |
|
|
– Number of Transport blocks |
Reference to clause 6.11.5.4.4.13 |
|
|
– CHOICE mode |
TDD |
|
|
– Transmission Time Interval |
Not Present |
|
|
– CHOICE Logical Channel List |
ALL |
|
|
– no data |
||
|
– Semi-static Transport Format information |
||
|
– Transmission time interval |
Reference to clause 6.11.5.4.4.13 |
|
|
– Type of channel coding |
Turbo |
|
|
– Coding Rate |
Not Present |
|
|
– Rate matching attribute |
Reference to clause 6.11.5.4.4.13 |
|
|
– CRC size |
Reference to clause 6.11.5.4.4.13 |
|
|
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 7 and Step 10)
|
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.2.4.3s.5 Test requirements
1) At step 14, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a count > 0 for Cell 31 MTCH.
7.2.4.3t MCCH Out Of Sequence Delivery handling / MBMS Broadcast Service (IMB)
7.2.4.3t.1 Definition
This test is applicable for 3.84 Mcps TDD IMB UE.
7.2.4.3t.2 Conformance requirement
To enable the recovery of SDUs from UMD PDUs that are received in different transmissions the receiving function shall store PDUs until all SDUs that are associated with the PDU can be reconstructed or until they are discarded in accordance with the procedures described below. SDUs are transferred to the upper layers as soon as all PDUs that contain the segments of the SDU and the "Length Indicator" indicating the end of the SDU have been received.
Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall for each PDU (in the following SN denotes the sequence number of each PDU):
– If the PDU is the first PDU received (after the receiving entity is established or re-established or after Timer_OSD expires):
– VR(UOH) shall be assigned the value SN-1.
– if VR(UOH) > SN > VR(UOH) – OSD_Window_Size then:
– if a PDU with sequence number SN is already stored:
– discard the PDU;
– else:
– store the PDU in sequence number order.
– else:
– VR(UOH) shall be assigned the value SN, thereby advancing the storage window;
– store the PDU in sequence number order;
– remove from storage any PDUs whose sequence numbers, SN, are outside of the storage window VR(UOH) > SN > VR(UOH) – OSD_Window_Size;
– if Timer_OSD is active then Timer_OSD shall be stopped;
– Timer_OSD shall be started.
– if a PDU with sequence number SN was stored:
– if the PDU contains one or more complete SDUs and/or if the PDU contains segments of SDUs for which all the remaining segments and length indicators are contained in stored PDUs:
– re-assemble the SDUs;
– submit the SDUs to upper layers through the UM-SAP;
– remove from storage any PDUs which do not contain any segment of a SDU that has not been re-assembled, and do not contain one of the special length indicators "0000 000", "0000 0000 0000 000" or "1111 1111 1111 011" that indicate the end of a SDU that has not been re-assembled.
NOTE 0: If PDUs are removed from storage after SDU recovery then retransmitted PDUs may result in the duplicate transfer of SDUs to the higher layers.
– if Timer_OSD expires:
– remove from storage all stored PDUs.
NOTE 1: When configured for out of sequence SDU delivery, the transmitter should consider the possibility that a loss of a number of 128 OSD_Window_Size consecutively numbered PDUs may result in an undetected protocol error in the receiver, if the transmit state variable VT(US), at the end of a time interval equal to the duration of Timer_OSD, is greater than 128 + SN OSD_Window_Size + 1, where SN is the lowest sequence number of any PDU transmitted or retransmitted within that time interval.
NOTE 2: The transmitter should not concatenate within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with SDUs or fractions of SDUs that contain other MCCH message types.
NOTE 3: SDUs are contained within consecutively numbered PDUs. To enable SDUs containing MBMS Access Information messages to be transmitted at their designated times, the transmitter may transmit PDUs out of sequence order.
NOTE 4: The transmitter should not transmit within a single PDU, SDUs or fractions of SDUs that contain MBMS Access Information messages with the special length indicator "0000 000","0000 0000 0000 000", and "1111 1111 1111 011".
Reference
1) 3GPP TS 25.322, clause 11.2.3.2
7.2.4.3t.3 Test purpose
To verify MCCH Out Of Sequence Delivery handling.
7.2.4.3t.4 Method of test
Initial condition
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 Default2 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.1e (3.84 Mcps TDD IMB) 8kbps RB for MBSFN MTCH.
The following parameters are specific for this test case:
|
Parameter |
Value |
|
OSD_Window_Size |
64 (to contain the entire MBMS CONTROL INFORMATION on MCCH) |
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 MBSFN receive only function available on UE Yes/No.
Test procedure
a) The UE is camping on FDD unicast carrier cell 1 and IMB 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) SS indicates on MICH and modifies the MCCH to indicate the start of the national service. In this step the SS shall send MCCH information as follows:
The RLC is configured at the SS as TM mode. This is in order to be able to replace encoded PDUs and header information with an invalid LI .
On the first repetition period for all critical MCCH messages, only the odd numbered RLC PDU SN are transmitted correctly, an invalid LI is inserted into the RLC header of the even numbered PDUs.
On the second repetition period for all critical MCCH messages, only the even numbered RLC PDU SN are transmitted correctly, an invalid LI is inserted into the RLC header of the odd numbered PDUs.
e) SS waits for the UE to begin reception of the MBMS service using the 8kbps radio bearer configuration specified in TS 34.108, clause 6.11.1e (3.84 Mcps TDD IMB). The UE closes the test loop. The UE sends CLOSE UE TEST LOOP COMPLETE.
f) The SS transmits 10 * RLC SDUs of size 40 octets. (PDU is 40 octets + 1 octet special LI)
g) 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.
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 |
For all MCCH messages using message combination C4 for 1 modification period: on the first repetition period, only the odd numbered RLC PDU SN are transmitted correctly. On the second repetition period only the even numbered RLC PDU SN are transmitted correctly. Other PDUs have an invalid LI in the RLC header. Those messages requiring specific contents are shown in steps 6-8, other messages have the default contents. |
|
|
5 |
|
M |
MBMS MODIFIED SERVICES INFORMATION |
Includes the national service activated at UE in the modified services list for one modification period. SS indicates to the UE to Acquire PTM RB info. |
|
|
6 |
|
M |
MBMS COMMON P-T-M RB INFORMATION |
Contains configuration for the 8kbps radio bearer configuration |
|
|
7 |
|
M |
MBMS Current Cell p-t-m rb Information |
Indicates the radio bearer configuration to be used for reception of the service. |
|
|
8 |
|
M |
MBMS MCCH Message Configuration C2 |
SS transmits PDUs using message combination C2. For all MCCH messages using message combination C2 for 1 modification period: on the first repetition period, only the odd numbered RLC PDU SN are transmitted correctly. On the second repetition period only the even numbered RLC PDU SN are transmitted correctly. Other PDUs have an invalid LI in the RLC header. After this modification period, the SS stops sending MCCH messages. |
|
|
9 |
|
M |
MBMS COMMON P-T-M RB INFORMATION |
Contains configuration for the 8kbps radio bearer configuration |
|
|
10 |
|
M |
MBMS Current Cell p-t-m rb Information |
Indicates the radio bearer configuration to be used for reception of the service. |
|
|
11 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE establishes the MTCH according to the activation time and closes the test loop. |
|
|
12 |
|
M |
10 * RLC SDU |
SS sends 10*RLC SDUs on MTCH |
|
|
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
Those PDUs indicated to have an invalid LI in the RLC header, shall encode the LI to be invalid according to TS 25.322 clause 11.2.4.2.
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 6 and Step 9) (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 |
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 |
Rel-6 |
|
|
– MBMS Common TrCh identity |
1 |
|
|
– TFS |
|
|
|
– CHOICE Transport channel type |
Common transport channels |
|
|
– Dynamic Transport format information |
|
|
|
– RLC Size |
Reference to clause 6.11.1e |
|
|
– Number of TBs and TTI List |
(This IE is repeated for TFI number.) |
|
|
– Number of Transport blocks |
Reference to clause 6.11.1e |
|
|
– CHOICE mode |
FDD |
|
|
– CHOICE Logical channel list |
All |
|
|
– no data |
|
|
|
– Semi-static Transport Format information |
|
|
|
– Transmission time interval |
Reference to clause 6.11.1e |
|
|
– Type of channel coding |
Turbo Code |
|
|
– Coding Rate |
Not present |
|
|
– Rate matching attribute |
Reference to clause 6.11.1e |
|
|
– CRC size |
Reference to clause 6.11.1e |
|
|
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 |
Reference to clause 6.11.1e |
|
|
– Last channelisation code |
Reference to clause 6.11.1e |
|
|
– CHOICE modulation |
Reference to clause 6.11.1e |
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 7 and Step 10)
|
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.2.4.3t.5 Test requirements
1) At step 14, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a count > 0 for Cell 31 MTCH.