7.2.5 Multiflow
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
7.2.5.1 RLC Timer_Reordering with Inter-Node B Multiflow operation
7.2.5.1.1 Definition and applicability
All UEs that support Multiflow HSDPA operation.
UE supports FDD.
7.2.5.1.2 Conformance requirement
There are several functions that can prohibit the Receiver from sending a status report containing any of the SUFIs LIST, BITMAP, RLIST or ACK. Status reports containing other SUFIs are not prohibited. Upper layers control which functions should be used for each RLC entity. If any of the following functions is used the transmission of the status report shall be delayed, even if any of the triggering conditions above are fulfilled:
1) STATUS prohibit.
The timer Timer_Status_Prohibit is started according to subclause 9.5 f). The Receiver is not allowed to transmit a status report while acknowledgement is prohibited (see subclause 9.5 f)). If a status report was triggered during this time, the status report is transmitted after the timer Timer_Status_Prohibit has expired, as described below.
2) Void
3) Timer_Reordering
The timer Timer_Reordering is started according to subclause 11.3.3. The receiver is not allowed to transmit a status report while the timer is running. If a status report was triggered during this time, the status report is transmitted after the timer Timer_Reordering has expired, as described below.
When a status report is triggered the Receiver shall:
– if transmission of status reports is not prohibited by any of the functions "STATUS prohibit" or "Timer_Reordering":
– assemble and transmit the status report to the Sender, as specified in subclauses 11.5.2.2 and 11.5.2.3.
– otherwise (if the status report is prohibited by at least one of the functions "STATUS prohibit"):
– if MRW, MRW_ACK, WINDOW or POLL SUFIs are required in the status report:
– send a status report immediately excluding ACK, LIST, BITMAP, and RLIST SUFIs;
– if ACK, LIST, BITMAP, or RLIST SUFIs are required in the status report:
– delay sending these SUFIs until the prohibit function terminates.
Upon expiry of the timer Timer_Status_Prohibit, the Receiver shall:
– if at least one status report was triggered during the time the transmission of a status reports was prohibited that could not be transmitted due to prohibition; and
– if transmission of a status reports is no longer prohibited by any of the functions "STATUS prohibit" or "Timer_Reordering":
– transmit one status report to the Sender, using the procedure described in subclause 11.5.2.3.
Upon expiry of the timer Timer_Reordering, the Receiver shall:
– if at least one status report was triggered during the time the transmission of a status reports was prohibited that could not be transmitted due to prohibition; and
– if transmission of a status reports is no longer prohibited by any of the functions "STATUS prohibit" or "Timer_Reordering":
– update VR(MS) to the SN of the first AMD PDU with SN >= VR(X) which has not been received;
– transmit one status report to the Sender, using the procedure described in subclause 11.5.2.3.
– if VR(H) > VR(MS):
– start Timer_Reordering;
– set VR(X) to VR(H).
Reference
3GPP TS 25.322 clause 9.7.2
7.2.5.1.3 Test purpose
To confirm that the UE runs RLC Timer_Reordering and waits for missing RLC PDUs.
7.2.5.1.4 Method of test
Initial Condition
The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed, with all the parameters as specified in the procedure, with the exception that the default Radio Access Bearer is replaced with the RAB defined for AM 7-bit "Length Indicator" tests in clause 7.2.3.1.
These settings apply to both the uplink and downlink DTCH.
System Simulator: 2 cells
Node B 1: Cell 1 (f1, serving HS-DSCH cell)
Node B 2: Cell 2 (f1, assisting serving HS-DSCH cell)
Tcell of Cell 1 is set to 0 chips, Tcell of Cell 2 is set to 1280 chips (0.5 slots).
User equipment:
CELL_DCH (state 6-18 PS-DCCH+DTCH E-DCH/HS-DSCH) under condition A44 as specified in clause 7.4 of TS 34.108 [9]. The procedure P9b in TS 34.108 [9], clause 7.4.2.4a is executed to add Cell 2 in the active set.
Related ICS/IXIT statement(s)
– UE supports FDD
– UE category supports Multiflow HSDPA operation on 2 cells on single frequency (UE Category 21-24)
Test Procedure
The SS starts sending 4 RLC PDUs with SN 4-7 via cell 1. After that the SS starts sending 4 RLC PDUs with SN 0-3 via cell 2. The "Polling bit" (P) should be set in all RLC PDUs.
The SS waits for a STATUS PDU from the UE indicating successful reception of all the RLC PDUs with SN 0-7.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
DOWNLINK RLC PDUs |
RLC PDUs with SN 4-7 to cell 1 |
|
2 |
|
DOWNLINK RLC PDUs |
RLC PDUs with SN 0-3 to cell 2 |
|
3 |
|
STATUS PDU |
ACK SN 0-7 |
7.2.5.1.5 Test requirements
In step 3, the SS should receive STATUS PDU from the UE with ACKs for RLC PDUs with SN 0-7.
7.2.5.2 Expiry of RLC Timer_Reordering with Inter-Node B Multiflow operation
7.2.5.2.1 Definition and applicability
All UEs that support Multiflow HSDPA operation.
UE supports FDD.
7.2.5.2.2 Conformance requirement
There are several functions that can prohibit the Receiver from sending a status report containing any of the SUFIs LIST, BITMAP, RLIST or ACK. Status reports containing other SUFIs are not prohibited. Upper layers control which functions should be used for each RLC entity. If any of the following functions is used the transmission of the status report shall be delayed, even if any of the triggering conditions above are fulfilled:
1) STATUS prohibit.
The timer Timer_Status_Prohibit is started according to subclause 9.5 f). The Receiver is not allowed to transmit a status report while acknowledgement is prohibited (see subclause 9.5 f)). If a status report was triggered during this time, the status report is transmitted after the timer Timer_Status_Prohibit has expired, as described below.
2) Void
3) Timer_Reordering
The timer Timer_Reordering is started according to subclause 11.3.3. The receiver is not allowed to transmit a status report while the timer is running. If a status report was triggered during this time, the status report is transmitted after the timer Timer_Reordering has expired, as described below.
When a status report is triggered the Receiver shall:
– if transmission of status reports is not prohibited by any of the functions "STATUS prohibit" or "Timer_Reordering":
– assemble and transmit the status report to the Sender, as specified in subclauses 11.5.2.2 and 11.5.2.3.
– otherwise (if the status report is prohibited by at least one of the functions "STATUS prohibit"):
– if MRW, MRW_ACK, WINDOW or POLL SUFIs are required in the status report:
– send a status report immediately excluding ACK, LIST, BITMAP, and RLIST SUFIs;
– if ACK, LIST, BITMAP, or RLIST SUFIs are required in the status report:
– delay sending these SUFIs until the prohibit function terminates.
Upon expiry of the timer Timer_Status_Prohibit, the Receiver shall:
– if at least one status report was triggered during the time the transmission of a status reports was prohibited that could not be transmitted due to prohibition; and
– if transmission of a status reports is no longer prohibited by any of the functions "STATUS prohibit" or "Timer_Reordering":
– transmit one status report to the Sender, using the procedure described in subclause 11.5.2.3.
Upon expiry of the timer Timer_Reordering, the Receiver shall:
– if at least one status report was triggered during the time the transmission of a status reports was prohibited that could not be transmitted due to prohibition; and
– if transmission of a status reports is no longer prohibited by any of the functions "STATUS prohibit" or "Timer_Reordering":
– update VR(MS) to the SN of the first AMD PDU with SN >= VR(X) which has not been received;
– transmit one status report to the Sender, using the procedure described in subclause 11.5.2.3.
– if VR(H) > VR(MS):
– start Timer_Reordering;
– set VR(X) to VR(H).
Reference
3GPP TS 25.322 clause 9.7.2
7.2.5.2.3 Test purpose
To confirm that the UE runs RLC Timer_Reordering and waits for missing RLC PDUs before generating STATUS PDU with NACKs.
7.2.5.2.4 Method of test
Initial Condition
The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed, with all the parameters as specified in the procedure, with the exception that the default Radio Access Bearer is replaced with the RAB defined for AM 7-bit "Length Indicator" tests in clause 7.2.3.1.
These settings apply to both the uplink and downlink DTCH.
System Simulator: 2 cells
Node B 1: Cell 1 (f1, serving HS-DSCH cell)
Node B 2: Cell 2 (f1, assisting serving HS-DSCH cell)
Tcell of Cell 1 is set to 0 chips, Tcell of Cell 2 is set to 1280 chips (0.5 slots).
User equipment:
CELL_DCH (state 6-18 PS-DCCH+DTCH E-DCH/HS-DSCH) under condition A44 as specified in clause 7.4 of TS 34.108 [9]. The procedure P9b in TS 34.108 [9], clause 7.4.2.4a is executed to add Cell 2 in the active set.
Related ICS/IXIT statement(s)
– UE supports FDD
– UE category supports Multiflow HSDPA operation on 2 cells on single frequency (UE Category 21-24)
Test Procedure
The SS starts sending 4 RLC PDUs with SN 4-7 via cell 1. After that the SS starts sending 2 RLC PDUs with SN 2-3 via cell 2. The "Polling bit" (P) should be set in all RLC PDUs.
The SS waits for a STATUS PDU from the UE indicating successful reception of RLC PDUs with SN 2-7 and missing RLC PDUs with SN 0-1.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
DOWNLINK RLC PDUs |
RLC PDUs with SN 4-7 to cell 1 |
|
2 |
|
DOWNLINK RLC PDUs |
RLC PDUs with SN 2-3 to cell 2 |
|
3 |
|
STATUS PDU |
NACK SN 0-1, ACK SN 2-7 |
7.2.5.2.5 Test requirements
In step 3, the SS should receive STATUS PDU from the UE with NACK for RLC PDUs 0-1 and ACK for RLC PDUs with SN 2-7.
7.2.5.3 Void
7.2.5.4 Erroneous Sequence Number Processing with Inter Node B Mutiflow operation
7.2.5.4.1 Definition and applicability
UE categories (Cat 21, Cat 22, Cat 23, Cat 24) which support combination of Multiflow HSDPA on Single Frequency/2 Cell on Single Band (SF-DC).
UE supports FDD.
7.2.5.4.2 Conformance requirement
A STATUS PDU or Piggybacked STATUS PDU including "erroneous Sequence Number" is a STATUS PDU or Piggybacked STATUS PDU that contains:
– a LIST, BITMAP or RLIST SUFI in which the "Sequence Number" of at least one AMD PDU that is negatively acknowledged is outside the interval VT(A)"Sequence Number"< VT(S); or
– an ACK SUFI in which "LSN" is outside the interval VT(A)"LSN" VT(S).
If an AM RLC entity receives a STATUS PDU or a Piggybacked STATUS PDU including "erroneous Sequence Number", it shall:
– discard the STATUS PDU or the Piggybacked STATUS PDU;
– if inter-Node B Multiflow operation is not configured by higher layers, initiate the RLC reset procedure (see subclause 11.4).
[…]
The Sender shall:
– if one of the following triggers is detected:
…
3) A STATUS PDU or a piggybacked STATUS PDU including "erroneous Sequence Number" is received (see clause 10);
– stop transmitting any AMD PDU or STATUS PDU;
– ignore any incoming AMD PDU, piggybacked STATUS PDU or STATUS PDU;
– increment VT(RST) by 1;
– if VT(RST) = MaxRST:
– perform the actions specified in subclause 11.4.4a.
– else (if VT(RST) < MaxRST):
– submit a RESET PDU to the lower layer;
– start the timer Timer_RST according to the description in subclause 9.5.
NOTE: If the TFC selection exchange has been initiated by sending the RLC Entity Info parameter to MAC, the RLC entity may delay the RLC reset procedure until the end of the next TTI.
[…]
Reference
3GPP TS 25.322 clause 10.1, 11.4.2
7.2.5.4.3 Test purpose
To confirm that the UE does not initiate RLC PDU Reset Procedure/Inter-Node B
7.2.5.4.4 Method of test
Initial Condition
The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) is executed, with all the parameters as specified in the procedure, with the exception that the default Radio Access Bearer is replaced with the RAB defined for AM 7-bit "Length Indicator" tests in clause 7.2.3.1.
These settings apply to both the uplink and downlink DTCH.
The Radio Bearer is placed in UE test loop mode 1 with the UL SDU size set to (2 * AM_7_PayloadSize) – 1 bytes.
System Simulator:
2 cells –Cell 1/2 with Cell 1 (f1) (Serving HS-DSCH cell), and Cell 2 (f1) (Assisting Serving HS-DSCH cell) – One frequency on Band A. (SF-DC). Configure with inter-Node-B multiflow operation. Tcell of Cell 2 is set to 3840 chips (1.5 slots).
UE: CELL_DCH (state 6-18) with condition A44 – SRBs mapped on DCH/DCH with the RLC parameters specified in clause 7.2.3.1. The procedure P9b in TS 34.108 [9], clause 7.4.2.4a is executed to add Cell 2 in the active set.
Related ICS/IXIT statement(s)
– UE supports FDD
– UE category supports Multiflow HSDPA operation on 2 cells on single frequency (UE Category 21-24)
Test Procedure
The SS sends 2 RLC SDUs of size (2 * AM_7_PayloadSize) – 1 bytes. One SDU is sent to cell 1, and another SDU is sent to cell 2 at the same time, where cell 1 and cell 2 are in inter-NodeB multiflow operation.
The SS checks the RLC PDUs received on the uplink and responds to all poll requests with a SUFI acknowledging the RLC PDU with sequence number 3, then SS sends a STATUS PDU acknowledging the RLC PDU with sequence number 1 that is outside the interval VT(A)"Sequence Number"< VT(S).
The SS waits for 1 second. The SS should not receive RESET PDU from UE.
Repeating the above steps, the SS sends 2 more RLC SDUs of size (2 * AM_7_PayloadSize) – 1 bytes. One SDU is sent to cell 1, and another SDU is sent to cell 2 at the same time.
The SS checks the RLC PDUs received on the uplink and responds to all poll requests with an ACK SUFI positively acknowledging the RLC PDU with sequence number 7, then SS sends a STATUS PDU negatively acknowledging the RLC PDU with sequence number 5 that is outside the interval VT(A)"Sequence Number"< VT(S).
The SS waits for 1 second. The SS should not receive RESET PDU from UE. UE shall retransmit the RLC PDU with sequence number 5.
Expected sequence
Step |
Direction |
Message |
Comments |
|
UE |
SS |
|||
1 |
|
DOWNLINK RLC PDU#0 |
SDU 1 to cell 1 |
|
2 |
|
DOWNLINK RLC PDU#1 |
SDU 1 to cell 1 |
|
3 |
|
DOWNLINK RLC PDU#2 |
SDU 2 to cell 2 |
|
4 |
|
DOWNLINK RLC PDU#3 |
SDU 2 to cell 2 |
|
5 |
|
UPLINK RLC PDU |
SDU 1 |
|
6 |
|
… |
SS continues to receive RLC PDUs |
|
7 |
|
UPLINK RLC PDU |
SDU, Poll. The Poll may appear in returned PDU for either SDU 1 or 2 |
|
8 |
|
STATUS PDU |
ACK SUFI SN 3 . |
|
9 |
|
STATUS PDU |
ACK SUFI SN 0-1 |
|
10 |
|
… |
SS shall not receive RESET PDU from UE |
|
11 |
|
DOWNLINK RLC PDU#4 |
SDU 3 to cell 1 |
|
12 |
|
DOWNLINK RLC PDU#5 |
SDU 3 to cell 1 |
|
13 |
|
DOWNLINK RLC PDU#6 |
SDU 4 to cell 2 |
|
14 |
|
DOWNLINK RLC PDU#7 |
SDU 4 to cell 2 |
|
15 |
|
UPLINK RLC PDU |
SDU 3 |
|
16 |
|
… |
SS continues to receive RLC PDUs |
|
17 |
|
UPLINK RLC PDU |
SDU, Poll. The Poll may appear in returned PDU for either SDU 3 or 4 |
|
18 |
|
STATUS PDU |
ACK SUFI SN 0-7 . |
|
19 |
|
STATUS PDU |
NAK SN 5 |
|
20 |
|
… |
SS should not receive RESET PDU from UE |
|
21 |
|
UPLINK RLC PDU |
Retransmit PDU SN 5, poll |
|
22 |
|
STATUS PDU |
ACK SN 5 |
|
NOTE: The Expected Sequence shown is informative. The UPLINK and DOWNLINK PDU flows may overlap, but are shown separate for clarity. Information such as SDU, PDU or Sequence numbers given in the comments column shall be considered informative only, for test case development purposes. |
Specific message contents
DOWNLINK AMD RLC PDU#0, PDU#2, PDU#4, PDU#6
Information Element |
Value/remark |
D/C |
‘1’B |
Sequence Number (SN) |
Set to the PDU number |
Pool bit (P) |
‘0’B |
Header Extension (HE) |
‘00’B |
Length indicator (LI) |
Not present |
Extension bit (E) |
Not present |
Data |
Any data of size AM_7_PayloadSize |
Padding |
Not present |
PiggyBacked status |
Not present |
DOWNLINK AMD RLC PDU#1, PDU#3, PDU#5, PDU#7
Information Element |
Value/remark |
D/C |
‘1’B |
Sequence Number (SN) |
Set to the PDU number |
Pool bit (P) |
‘0’B |
Header Extension (HE) |
‘01’B |
Length Indicator (LI) |
(AM_7_PayloadSize-1) |
Extension bit (E) |
‘0’B |
Data |
Any data of size AM_7_PayloadSize |
Padding |
Not present |
PiggyBacked status |
Not present |
7.2.5.4.5 Test requirements
In steps 10 and 20, the SS should not receive RESET PDU from UE.