hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.30 Timer based discard, with explicit signalling / Obsolete MRW_ACK | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.30.1 Definition | This case tests the ability of the receiving AM RLC entity to handle obsolete information that can be received during a failure of the SDU discard procedure. SDU discard is used to keep network delays within limits, and incorrect operation will effect the quality of service. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.30.2 Conformance requirement | If Timer_MRW expires before the discard procedure is terminated, the MRW SUFI shall be retransmitted, VT(MRW) is incremented by one and Timer_MRW restarted. MRW SUFI shall be exactly the same as previously transmitted even though some new SDUs would have been discarded during the running of the Timer_MRW.
The received ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.30.3 Test purpose | 1. To verify that the MRW SUFI is retransmitted if Timer_MRW expires before a valid MRW_ACK is received.
2. To verify that the MRW_ACK is discarded if the SN_ACK field < SN_MRWLENGTH.
3. To verify that the MRW_ACK is discarded if the N field is not equal to NLENGTH transmitted in the MRW SUFI.
4. To verify that the MR... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.30.4 Method of test | Initial conditions
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.
The fo... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.30.5 Test requirements | 1. The measured time T2 – T1 shall be 500 ms.
2. The measured time T3 – T2 shall be 500 ms.
3. The STATUS PDUs received in steps 8, 10, 12 and 14 shall contain an identical MRW SUFI. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.31 Timer based discard, with explicit signalling / Failure of MRW procedure | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.31.1 Definition | This case tests that if a failure occurs during the signalling of an SDU discard to the receiver, the retransmission protocol operates correctly. SDU discard is used to keep network delays within limits, and incorrect operation will effect the quality of service. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.31.2 Conformance requirement | If VT(MRW) = MaxMRW, the Sender shall:
- terminate the SDU discard with explicit signalling procedure;
- stop the timer Timer_MRW if it was started;
- initiate the RLC RESET procedure (see clause 11.4).
If Timer_MRW expires before the discard procedure is terminated, the Sender shall:
- increment VT(MRW) by one;
- if V... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.31.3 Test purpose | 1. To verify that when the number of retransmissions of a MRW command reaches MaxMRW, an error indication is passed to RRC and RESET procedure is initiated. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.31.4 Method of test | Initial conditions
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.
The fo... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.31.5 Test requirements | The measured time T2 – T1 shall be 500 ms.
After step 17, the SS shall detect 3 repeats of the MRW command sent in step 17 before a RESET PDU is sent. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.32 SDU discard after MaxDAT-1 number of transmissions | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.32.1 Definition | This case tests that if a PDU is unsuccessfully transmitted MaxDAT-1 times, the SDU it carries, and therefore all other associated PDUs, are discarded by the transmitter and receiver. This mode of SDU discard is used to minimize data loss, and incorrect operation will effect the quality of service. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.32.2 Conformance requirement | 1. There shall be one VT(DAT) for each PDU and each shall be incremented every time the corresponding AMD PDU is scheduled to be transmitted. The initial value of this variable is 0.
2. If the number of times an AMD PDU is scheduled for transmission reaches MaxDAT, the Sender shall:
- discard all SDUs segments of which... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.32.3 Test purpose | 1. To verify that if VT(DAT) = MaxDAT for any PDU the sender initiates the SDU discard with explicit signalling procedure. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.32.4 Method of test | Initial conditions
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 ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.32.5 Test requirements | The uplink RLC PDU with sequence number 0 shall be retransmitted twice, then the SS shall detect a STATUS PDU with an MRW command. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.33 Operation of the RLC Reset procedure / UE Originated | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.33.1 Definition | This case tests that when the maximum number of retransmissions is exceeded, the UE initiates and performs the RLC Reset procedure. Incorrect operation of this procedure may cause loss of service. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.33.2 Conformance requirement | The Sender shall:
- if one of the following triggers is detected:
1) "No_Discard after MaxDAT number of transmissions" is configured and VT(DAT) equals the value MaxDAT (see TS 25.322 subclause 9.7.3.4);
…
- stop transmitting any AMD PDU or STATUS PDU;
- increment VT(RST) by 1;
- if VT(RST) = MaxRST:
- the Sender may s... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.33.3 Test purpose | 1. To verify that the Reset procedure is initiated when the maximum number of retransmissions has been exceeded (Reset trigger condition 1) in subclause 11.4.2 of 3GPP TS 25.322 (R1999).
2. To verify that the sender resets state variables to their initial value and resets configurable parameters to their configured val... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.33.4 Method of test | Initial conditions
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.
The fo... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.33.5 Test requirements | 1. The measured time T2 – T1 shall be 500 ms.
2. In steps 20 to 21 the SS shall receive an RLC SDU with contents that match the third RLC SDU sent to the UE. The first RLC PDU containing that SDU shall have sequence number 0.
3. The RSN bit of the first and second RESET PDUs received shall be set to 0. The RSN bit of t... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.34 Operation of the RLC Reset procedure / UE Terminated | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.34.1 Definition | This case tests that the UE responds correctly to the RLC Reset procedure initiated by the network. Incorrect operation of this procedure may cause loss of service. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.34.2 Conformance requirement | Upon reception of a RESET PDU the Receiver shall:
- if the RSN value in the RESET PDU is the same as the RSN value in the last received RESET PDU:
- either only submit a RESET ACK PDU to the lower layer with the contents set exactly as in the last transmitted RESET ACK PDU (i.e., in this case the RLC entity is not rese... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.34.3 Test purpose | 1. To verify that upon reception of a RESET PDU the receiver responds with a RESET ACK PDU.
2. To verify that the receiver resets its state variables to their initial value and resets configurable parameters to their configured value. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.34.4 Method of test | Initial conditions
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.
The fo... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.34.5 Test requirements | 1. The SS shall receive a RESET ACK PDU in step 7.
2. The SS shall receive a STATUS PDU in step 10 acknowledging for the third RLC SDU transmitted with PDUs starting at SN=0. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.35 Reconfiguration of RLC parameters by upper layers | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.35.1 Definition | This case verifies the UE behaviour after a reconfiguration of RLC parameters on an established RLC AM entity. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.35.2 Conformance requirement | Upon reception of the IE "RLC Info", the UE shall:
1> configure the transmitting and receiving RLC entities in the UE for that radio bearer accordingly;
1> if the IE "Polling info" is present in the IE "RLC info":
2> for each present IE in the IE "Polling info":
3> configure RLC to use the corresponding function accord... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.35.3 Test purpose | To verify that the UE starts to use the new set of RLC parameters when an already established AM RLC radio bearer is reconfigured. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.35.4 Method of test | Initial conditions
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.
The Ra... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.35.5 Test requirements | The measured time T2 – T1 shall be 500 ms.
The measured time T4 – T3 shall be 600 ms. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.36 Flexible handling of RLC PDU sizes for AM RLC | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.36.1 Definition | When flexible “RLC PDU size” is configured in downlink, RLC SDUs are segmented if the SDU is larger than the maximum RLC PDU size. Concatenation may be performed up to the maximum RLC PDU size. If flexible RLC PDU size is configured, the downlink AMD PDU size is variable up to the maximum RLC PDU size. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.36.2 Conformance requirement | Unless the "Extension bit" indicates that a UMD PDU contains a complete SDU which is not segmented, concatenated or padded, or the HE field indicates that an AMD PDU contains the last octet of the RLC SDU, a "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU
[…]
This two-bit [He... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.36.3 Test purpose | 1. To test that a large SDU is correctly received for varying RLC PDU sizes up to the maximum RLC PDU size
2. To test that a segmented is SDU reassembled correctly and delivered to higher layers |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.36.4 Method of test | Initial conditions
No specific as included in the test procedure (steps a and b) for each test execution
Downlink length indicators of size 15 shall be used
Test procedure
Table 7.2.3.36.4.1 Max_RLC_PDU_size values for different test executions
Test execution
1
2
3
Max_RLC_PDU_size [octets]
90
300
1500
Let Max_RLC_PDU_... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.36.5 Test requirements | For each execution of the test procedure:
1. In steps 4, the UE shall return two RLC SDUs with the same size and content as the transmitted SDUs
2. In steps 6, the UE shall return two RLC SDUs with the same size and content as the transmitted SDUs
3. In steps 8, the UE shall return two RLC SDUs with the same size ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.37 RLC PDU Size Adaptation in Uplink | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.37.1 Definition and applicability | Applicable for all UEs supporting MAC-i/is. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.37.2 Conformance Requirement | [..]
For the Unacknowledged mode data and Acknowledged mode data, if MAC-i/is has been configured on the uplink:
- if the UE pre-generates RLC PDUs for transmission in a later TTI:
- provided that the UE has sufficient amount of data available for transmission, the size of the data field of the RLC PDU shall be chosen ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.37.3 Test purpose | 1. To verify that the UE adapts the RLC PDU size according to the current radio conditions and current grant. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.37.4 Method of test | Initial conditions
System Simulator:
1 cell, default parameters, Ciphering Off
User Equipment:
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 Bearer is replaced with the RB acc... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.37.5 Test requirements | 1. In step 4, the SS shall receive RLC PDUs of the maximum possible size for the absolute grant (value 5) allowed.
2. In step 6, the SS shall receive between 0 and 5 RLC PDUs on LCH1 of the maximum possible size for the previous grant (5) allowed to cater for the pre-generation of RLC PDUs by the UE for transmission i... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.38 Flexible handling of RLC PDU sizes for AM RLC in uplink | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.38.1 Definition | If flexible RLC PDU size is configured in uplink, RLC SDUs are segmented and/or concatenated to create RLC PDUs larger than or equal to the Minimum UL RLC PDU size and smaller than or equal to the largest UL AMD PDU size. If data to be transmitted is not enough to create an AMD PDU of the minimum size, it is allowed to... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.38.2 Conformance requirement | - if "Flexible RLC PDU size" is configured:
[…]
- in uplink, the last segment of an RLC SDU shall be concatenated with the first segment of the next RLC SDU in order to fill the data field at least up to the Minimum UL RLC PDU size. It is allowed to concatenate up to the largest UL AMD PDU size for Acknowledged mode da... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.38.3 Test purpose | 1. To test that SDUs are correctly concatenated/segmented into RLC PDUs not smaller than “Minimum UL RLC PDU size” (unless there is no other data in the buffer) and not larger than “Largest UL RLC PDU size” |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.38.4 Method of test | Initial conditions
The following parameters are specific for this test case:
Parameter
Value
Minimum UL RLC PDU size
320 bit
Largest UL RLC PDU size
640 bit
a) 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 ex... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.3.38.5 Test requirements | For each execution of the test procedure:
1. In step 6, the UE shall return 4 RLC SDUs with the same content as the transmitted SDUs. The size of all AMD PDUs, except the final AMD PDU, shall be equal to “Minimum UL RLC PDU size”. The size of the last AMD PDU can be less than or equal to the "Minimum UL RLC PDU size".
... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.4 MBMS | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.4.1 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.4.2 MTCH duplicate avoidance and reordering / MBMS Broadcast Service | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.4.2.1 Definition | This test is applicable for Rel-6 UEs supporting MBMS broadcast services. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 w... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.4.2.3 Test purpose | To verify the MTCH duplicate avoidance and reordering procedure |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 Re... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.4.3 MCCH Out Of Sequence Delivery handling / MBMS Broadcast Service | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.4.3.1 Definition | This test is applicable for Rel-6 UEs supporting MBMS broadcast services. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.4.3.3 Test purpose | To verify MCCH Out Of Sequence Delivery handling. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 r... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5 Multiflow | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.1 RLC Timer_Reordering with Inter-Node B Multiflow operation | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.1.1 Definition and applicability | All UEs that support Multiflow HSDPA operation.
UE supports FDD. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.1.3 Test purpose | To confirm that the UE runs RLC Timer_Reordering and waits for missing RLC PDUs. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 s... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.2 Expiry of RLC Timer_Reordering with Inter-Node B Multiflow operation | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.2.1 Definition and applicability | All UEs that support Multiflow HSDPA operation.
UE supports FDD. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 s... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.3 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.4 Erroneous Sequence Number Processing with Inter Node B Mutiflow operation | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.4.3 Test purpose | To confirm that the UE does not initiate RLC PDU Reset Procedure/Inter-Node B |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 s... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.4.5 Test requirements | In steps 10 and 20, the SS should not receive RESET PDU from UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.5.5 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3 PDCP | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1 General | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.1 General assumptions | If not otherwise mentioned, the same procedures as used in RRC test specification (TS 34.123-1) or in the Generic procedure (TS 34.108) applies to reach Initial conditions for PDCP testing. In this test description, common test sequences for PDCP (clause 7.3.1.2) are defined and are applied either as preamble or post a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.2 Common Test sequences and Default message contents for PDCP | General
The settings and parameter used in the "Common Test sequences for PDCP" are described in the "Default PDCP Message Contents". If not explicitly shown there, the message contents are identical with the default contents for the same message type of layer 3 messages for RRC tests, to establish a packet switched se... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.2.1 Common Test sequences for PDCP | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.2.1.1 Setup a UE terminated PS session using IP Header compression in AM RLC (using UE Test loop test mode 1) | Initial Conditions
UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108.
Test procedure
After having received the System Information, the SS starts to setup a RRC connection. After connection establishment and Radio Bearer Setup, the UE test loop mode 1 is activated and the UE test loop mode ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.2.1.2 Setup a UE terminated PS session using IP Header compression in UM RLC (using UE Test loop test mode 1) | Initial Conditions
UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108.
Test procedure
After having received the System Information, the SS starts to setup a RRC connection. After connection establishment and Radio Bearer Setup, the UE test loop mode 1 is activated and the UE test loop mode ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.2.1.3 Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) | Initial Conditions
UE is in connected mode, a UE test loop mode 1 for PDCP is activated, and the UE loop mode 1 is "closed".
Test procedure
The UE opens the UE test loop mode 1, deactivates the test mode and the PS session, releases the Radio Bearer and enters Idle mode.
Expected Sequence
Step
Direction
Message
Comment... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.2.1.4.1 Specific message contents | For step 2a, the messages in clause 9 of TS 34.108 are used. To execute the procedure for the CELL_DCH case, use the message titled "Packet to CELL_DCH from CELL_DCH in PS". To execute the procedure for the CELL_FACH case, use the message titled "Packet to CELL_FACH from CELL_FACH in PS".
Specific message contents
T... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.2.1.5 Setup a UE terminated CS session in UM RLC (using UE Test loop test mode 1) | Initial Conditions
UE is in Idle mode (state 2 or state 7) as specified in clause 7.4 of TS 34.108.
Test procedure
After having received the System Information, the SS starts to setup a RRC connection. After connection establishment and Radio Bearer Setup, the UE test loop mode 1 is activated and the UE test loop mode ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.3.1.2.2 Default PDCP Message Contents | This clause contains the default values of RRC messages used for PDCP testing, other than those specified in TS 34.108 clauses 6 and 9, and default values of PDCP messages. Unless indicated otherwise in specific test cases, only PDCP related specific message contents are described here which shall be transmitted by the... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.