hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.2 Happy bit setting and SI handling for Dual-Cell HSUPA | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.2.1 Definition and applicability | All UEs which support Dual-Cell HSDPA and Dual-Cell E-DCH. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.2.2 Conformance requirement | The happy bit is a single bit field that is passed from MAC to the physical layer for inclusion on the E-DPCCH. This field takes two values, "Not Happy" and "Happy" indicating respectively whether the UE could use more resources or not. The setting of the Happy Bit is defined in subclause [TS 25.321] 11.8.1.5.
A happy... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.2.3 Test purpose | 1 To verify that UE makes the correct settings of happy bit for the primary and secondary frequency.
2. To verify that UE makes the correct settings of scheduling information for the primary and secondary frequency. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.2.4 Method of test | Initial conditions
System Simulator:
2 cell – Cell 1/2 DC HSDPA and DC HSUPA cell(s) with Cell 1 (Serving HS-DSCH cell/Primary uplink frequency) and 2 (Secondary serving HS-DSCH/Secondary uplink frequency), Ciphering Off.
User Equipment:
The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) i... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.2.5 Test requirements | 1. In step 2 the SS shall receive a Scheduling Information on both Activated Uplink Frequencies indicating a total E-DCH Buffer Status (TEBS) Index > 0
2. In step 4 the SS shall for each Activated Uplink Frequency receive data and happy bit information. For each E-DPCCH the happy bit shall be set to happy in the first ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.3 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.4 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.5 Deactivation and activation of secondary uplink frequency using HS-SCCH orders | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.5.1 Definition and applicability | This test apply for Release 9 and later releases for the FDD UE that supports HSDPA and Dual Cell E-DCH. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.5.2 Conformance requirement | If the UE receives:
- a HS-SCCH order for secondary uplink frequency activation/deactivation
it shall:
1> if the variable SECONDARY_CELL_E_DCH_TRANSMISSION is set to TRUE and the HS-SCCH order is to activate the secondary uplink frequency:
2> consider the secondary uplink frequency as activated;
2> initiate the physica... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.5.3 Test purpose | 1. To verify that UE deactivates the secondary uplink frequency when deactivation command is received on the HS-SCCH.
2. To verify that UE activates the secondary uplink frequency when activation command is received on the HS-SCCH. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.5.4 Method of test | Initial Condition
System Simulator:
2 cells –Cell 1/2 DC HSDPA and DC HSUPA cell(s) with Cell 1 (Serving HS-DSCH cell/Primary uplink frequency) and Cell 2 (Secondary serving HS-DSCH cell /Secondary uplink frequency) and Ciphering Off.
UE:
The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS 34.108) ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.9.5.4 Test requirement | At step 2 the UE shall transmit a HS-DPCCH ACK to respond the Activation Command.
At step 7 the UE shall transmit data to SS on the secondary uplink carrier.
At step 9 the UE shall transmit a HS-DPCCH ACK to respond the De-Activation Command.
After step 11 the UE should not send any data on the primary or secondary upl... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10 Fallback to R99 PRACH in CELL_FACH | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.1 Fallback to R99 PRACH in CELL_FACH / Network indicates fallback to R99 PRACH on CCCH | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.1.1 Definition and applicability | This test apply for Release 11 and later releases for a FDD UE that supports Fallback to R99 PRACH in CELL_FACH. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.1.2 Conformance requirement | [TS 25.319, clause 23.2]
The sub-feature of fallback to R99 PRACH allows the network to indicate to the UE to use a RACH resource instead of a common E-DCH resource for an uplink transmission, when a UE attempts to access on common E-DCH in CELL_FACH state and IDLE mode.
If configured by the network, the UE may be indi... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.1.3 Test purpose | With UE in CELL_FACH with HS-DSCH and E-DCH configured and the network in SIB22 indicates fallback to R99 PRACH on CCCH, but not on DCCH:
1. To verify that UE, when UE has CCCH data to transmit in uplink and NodeB rejects a common E-DCH resource request, use the RACH random access procedure to obtain a R99 RACH resourc... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.1.4 Method of test | Initial Condition
System Simulator:
1 cell, default parameters, Ciphering Off, SIB configuration 10 according to TS 34.108 clause 6.10a2 using the specific message content for SIB1, SIB3, SIB4, SIB5 and SIB22 as specified below.
UE:
UE is in Enhanced CELL_FACH state with DTCH/DCCH on common E-DCH / HS-DSCH.
The SS esta... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.1.4 Test requirement | At step 4 the UE shall perform a RACH random access procedure to obtain a R99 RACH resource.
At step 6 the UE shall transmit a CELL UPDATE message on CCCH using the R99 RACH resource.
At step 9 the UE shall perform a PRACH Preamble and Acquisition Indication reception procedure prior to acquiring common E-DCH resource ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.2 Fallback to R99 PRACH in CELL_FACH / Network indicates fallback to R99 PRACH on DCCH | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.2.1 Definition and applicability | This test apply for Release 11 and later releases for a FDD UE that supports Fallback to R99 PRACH in CELL_FACH. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.2.2 Conformance requirement | Same as in 7.1.10.1.2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.2.3 Test purpose | With UE in CELL_FACH with HS-DSCH and E-DCH configured and the network in SIB22 indicates fallback to R99 PRACH on DCCH, but not on CCCH:
1. To verify that UE, when UE has DCCH data to transmit in uplink and when a common E-DCH is rejected by the NodeB uses the RACH random access procedure to obtain a R99 RACH resource... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.2.4 Method of test | Initial Condition
System Simulator:
1 cell, default parameters, Ciphering Off, SIB configuration 10 according to TS 34.108 clause 6.10a2 using the specific message content for SIB1, SIB3, SIB4, SIB5 and SIB22 as specified below.
UE:
UE is in Enhanced CELL_FACH state with DTCH/DCCH on common E-DCH / HS-DSCH.
The SS esta... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.10.2.4 Test requirement | At step 4 the UE shall perform a PRACH Preamble and Acquisition Indication reception procedure prior to acquiring common E-DCH resource and sending the CELL UPDATE message on CCCH.
At step 8 the UE shall perform a RACH random access procedure to obtain a R99 RACH resource.
At step 10 the UE shall transmit a UE CAPABILI... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11 HS-DSCH MAC-ehs with Multiflow | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.1 Maximum number of re-ordering SDUs with inter-Node B operation on two cells on one frequency | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.1.1 Definition and applicability | A UEs that support Multiflow operation on two cells on one frequency. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.1.2 Conformance requirement | The UE behaviour is unspecified, if any of the following conditions are met when Multiflow is not configured or when intra-Node B Multiflow is configured:
- if reordering SDUs in one TTI belong to more than 3 priority queues,
- if the TSN field extension for MAC-ehs entity is not configured and MAC-ehs PDU(s) received ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.1.3 Test purpose | To confirm that the UE can handle the maximum number of re-ordering SDUs per each MAC-ehs entity. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.1.4 Method of test | Initial conditions
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). Ciphering off.
User equipment:
CELL_DCH (state 6-18 PS-DCCH+DTCH E-DCH/HS-DSCH) under condit... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.1.5 Test requirements | In Step 2, SS receives loop backed all RLC PDUs. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.2 Maximum number of re-ordering SDUs with inter-Node B operation on three cells on two frequencies | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.2.1 Definition and applicability | All UEs that support Multiflow operation on three cells on two frequencies. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.2.2 Conformance requirement | The UE behaviour is unspecified, if any of the following conditions are met when Multiflow is not configured or when intra-Node B Multiflow is configured:
- if reordering SDUs in one TTI belong to more than 3 priority queues,
- if the TSN field extension for MAC-ehs entity is not configured and MAC-ehs PDU(s) received ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.2.4 Method of test | Initial conditions
System Simulator: 3 cells
Node B 1: Cell 1 (f1, serving HS-DSCH cell)
Node B 2: Cell 2 (f1, assisting serving HS-DSCH cell)
Node B 1: Cell 3 (f2, secondary serving HS-DSCH cell)
Tcell of Cell 1 and Cell 3 is set to 0 chips, Tcell of Cell 2 is set to 1280 chips (0.5 slots). Ciphering off.
User equipme... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.1.11.2.5 Test requirements | In Step 2, SS receives loop backed all RLC PDUs. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2 RLC testing | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.0 General | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.0.1 Radio bearer setup | For radio bearer setup the following settings shall be used in both CS and PS mode:
- Re-establishment Timer: useT314
- MAC logical channel priority: 7
- UL Logical Channel Identity:7
- DL Logical Channel Identity:7 |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.1 Transparent mode | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.1.1 Segmentation and reassembly | Transparent mode segmentation and reassembly are not tested in this release of the specification. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2 Unacknowledged mode | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.1 General information for UM tests | Two generic Radio Access Bearers are provided for UM tests.
The UM test RAB is set up using the Generic Procedure described in clause 7.1.3 of 3GPP TS 34.108, and with the default RAB replaced as follows:
- For UM 7-bit "Length Indicator" tests: the RB configuration described in 3GPP TS 34.108 clause 6.11.1 is used. Fo... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.2 Segmentation and reassembly / Selection of 7 or 15 bit "Length Indicators" | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.2.1 Definition | The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. The selection of the size of the "Length Indicator" fields used must follow the specified rules. Incorrect operation of segmentation, concatenation, or ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.2.2 Conformance requirement | Except for the predefined values reserved for special purposes and listed in TS 25.322 section 9.2.2.8 the "Length Indicator" shall:
- be set to the number of octets between the end of the RLC header and up to and including the last octet of an RLC SDU segment;
- be included in the PDUs that they refer to.
The size of ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.2.3 Test purpose | To test that if the size of the largest PDU is l25 octets, 7 bit indicators are used, otherwise, 15 bit indicators are used. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.2.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 UM 7-bit "Length Indicator" tests in clause 7.2.2.1.
These ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.2.5 Test requirements | 1. The UE shall send 7 bit "Length Indicators" with values that correctly indicate the end of the SDU received in step 3.
2. The UE shall send 15 bit "Length Indicators" with values that correctly indicate the end of the SDU received in step 7. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.3 Segmentation and reassembly / 7-bit "Length Indicators" / Padding | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.3.1 Definition | The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.3.2 Conformance requirement | A "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU.
Except for the predefined values reserved for special purposes and listed in the tables below, the "Length Indicator" shall:
- be set to the number of octets between the end of the RLC header and up to and including the last ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.3.3 Test purpose | 1. To test that the UE correctly segments a large SDU, includes a "Length Indicator" indicating padding in the RLC PDU carrying the last SDU segment, and adds padding at the end.
2. To test that the UE correctly deals with a 7-bit padding "Length Indicator" when present in a received PDU. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.3.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 UM 7-bit "Length Indicator" tests in clause 7.2.2.1.
These ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.3.5 Test requirements | 1. The UE shall return two RLC PDUs. The first RLC PDU shall not include "Length Indicators". except for presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel5 and later UE. The second RLC PDU shall have a "Length Indicator" indicating the PDU contains an SDU boundary a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.4 Segmentation and Reassembly / 7-bit "Length Indicators" / LI = 0 | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.4.1 Definition | The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. A pre-defined "Length Indicator" value is used to indicate when a SDU ends coincident with the end of the previous PDU. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in fai... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.4.2 Conformance requirement | A "Length Indicator" is used to indicate the last octet of each RLC SDU ending within the PDU.
Except for the predefined values reserved for special purposes and listed in TS 25.322 subclause 9.2.2.8, the "Length Indicator" shall:
- be set to the number of octets between the end of the RLC header and up to and includin... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.4.3 Test purpose | 1. To test that where a SDU exactly fills a PDU, a "Length Indicator" of all 0's is placed by the transmitter as the first "Length Indicator" in the next PDU.
2. To test that where a SDU exactly fills a PDU, the receiver accepts a "Length Indicator" of all 0's, placed as the first "Length Indicator" in the next PDU. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.4.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 UM 7-bit "Length Indicator" tests in clause 7.2.2.1.
These ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.4.5 Test requirements | The UE shall return two RLC PDUs. The first RLC PDU shall not include "Length Indicators" except for presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel-5 and later UE.. The second RLC PDU shall have a "Length Indicator" indicating that the SDU exactly filled the prev... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.5 Reassembly / 7-bit "Length Indicators" / Invalid LI value | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.5.1 Definition | The RLC segments and concatenates SDUs into UMD PDU according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of an invalid "Length Indicator" value has been specified. Incorrect operation of segmentation, concatenation, or c... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.5.2 Conformance requirement | Upon delivery by the lower layer of an UMD PDU that contains a "Length Indicator" value specified to be reserved for UMD PDUs in this version of the protocol, the Receiver shall:
- ignore that UMD PDU.
[...]
Length: 7 bits
Bit
Description
1111101
Reserved (PDUs with this coding will be discarded by this version of the ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.5.3 Test purpose | To test that PDUs with invalid "Length indicator" '111 1110' are discarded by the receiving RLC. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.5.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 UM 7-bit "Length Indicator" tests in clause 7.2.2.1.
These ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.5.5 Test requirements | The UE shall return two RLC PDUs. The first RLC PDU shall not include any "Length Indicators" except for presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel-5 and later UE. The second RLC PDU shall have a "Length Indicator" indicating the end of the SDU, and a padding... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.6 Reassembly / 7-bit "Length Indicators" / LI value > PDU size | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.6.1 Definition | The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. The behaviour of the RLC on reception of an invalid "Length Indicator" value has been specified. Incorrect operation of segmentation, concatenation, or ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.6.2 Conformance requirement | If the "Length Indicator" of an UMD PDU has a value that is larger than the PDU size – RLC header size and is not one of the predefined values listed in the table of TS 25.322 subclause 9.2.2.8, the Receiver shall:
- ignore the UMD PDU.
[...]
Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall:
... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.6.3 Test purpose | To test that PDUs with "Length Indicators" that point beyond the end of the PDU are ignored by the receiving RLC entity. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.6.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 UM 7-bit "Length Indicator" tests in clause 7.2.2.1.
These ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.6.5 Test requirements | The UE shall return two RLC PDUs. The first RLC PDU shall not include "Length Indicators" except for presence of Special “Length Indicator” indicating “beginning of an SDU” that will be included by a Rel-5 and later UE. The second RLC PDU shall have a LI indicating the end of an SDU and an "Length Indicator" indicatin... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.7 Reassembly / 7-bit "Length Indicators" / First data octet LI | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.7.1 Definition | The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. "Length indicators" are added to allow correct reconstruction of SDUs. A special "Length Indicator" is defined to indicate that the start of an SDU is coincident with the start of the PDU. The special "Length Indicator" is ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.7.2 Conformance requirement | 1. "Length Indicator" = 1111100, UMD PDU: The first data octet in this RLC PDU is the first octet of a RLC SDU.
2. Upon delivery of a set of UMD PDUs from the lower layer, the Receiver shall:
...
- if the special "Length Indicator" "1111 100" or "1111 1111 1111 100" is the first "Length Indicator" of a UMD PDU received... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.7.3 Test purpose | To test that a UE in unacknowledged mode correctly handles a received RLC PDU with a 7-bit "Length Indicator" having its value equal to the special "Length Indicator" value 1111100 when the sequence number of the first received PDU is different from zero. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.7.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 UM 7-bit "Length Indicator" tests in clause 7.2.2.1.
These ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.7.5 Test requirements | 1. The UE shall return two RLC PDUs.
2. The length and data content of each received SDU shall be the same as the transmitted SDU. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.8 Segmentation and reassembly / 15-bit "Length Indicators" / Padding | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.8.1 Definition | The RLC segments and concatenates SDUs into UMD PDU according to the PDU size requested by MAC. "Length Indicators" are added to allow correct reconstruction of SDUs. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in failure of the UE to communicate. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.8.2 Conformance requirement | A PDU that has unused space, to be referred to as padding, shall use a "Length Indicator" to indicate that this space is used as padding unless the padding size is one octet for PDUs with 15-bit "Length Indicators". A padding "Length Indicator" must be placed after any "Length Indicators" for a PU.
One "Length Indicato... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.8.3 Test purpose | 1. To test that the UE correctly segments a large SDU and padding is added at the end.
2. To test that the UE correctly deals with a 15-bit padding "Length Indicator" when present in a received PDU. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.8.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 UM 15-bit "Length Indicator" tests in clause 7.2.2.1.
These... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.8.5 Test requirements | 1. The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have a "Length Indicator" indicating the PDU contains a SDU boundary after octet 1 of the data field, and the second shall indicate that the remainder of the PDU contains padding.
2. The length and data content of the... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.9 Segmentation and Reassembly / 15-bit "Length Indicators" / LI = 0 | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.9.1 Definition | The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. A pre-defined "Length Indicator" value is used to indicate when an SDUs ends coincident with the end of the previous PU. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result in fa... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.9.2 Conformance requirement | If the PDU is exactly filled with the last segment of a SDU and there is no room for an "Length Indicator" field, a "Length Indicator" field set to all 0's shall be included as the first "Length Indicator" in the following PDU.
Reference(s)
TS 25.322 clause 11.2.2.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.9.3 Test purpose | 1. To test that where a SDU exactly fills a PDU, a "Length Indicator" of all 0's is placed by the transmitter as the first "Length Indicator" in the next PDU.
2. To test that where an SDU exactly fills a PDU, and an "Length Indicator" of all 0's is the first "Length Indicator" in the next PDU, the receiver correctly re... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.9.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 UM 15-bit "Length Indicator" tests in clause 7.2.2.1.
These... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.9.5 Test requirements | The UE shall return two RLC PDUs. The first shall not include "Length Indicators". The second shall have an "Length Indicators" indicating that the SDU exactly filled the previous UMD PDU, and a "Length Indicators" indicating that the remainder of the PDU contains padding.
The length of the received SDU shall be UM_15_... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.10 Segmentation and reassembly / 15-bit "Length Indicators" / One octet short LI | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.10.1 Definition | The RLC segments and concatenates SDUs into UMD PDUs according to the PDU size requested by MAC. A pre-defined "Length Indicator" value is used to indicate when an SDUs ends one octet short of the end of the previous PDU. Incorrect operation of segmentation, concatenation, or coding of "Length Indicators" will result i... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.10.2 Conformance requirement | In the case where the last segment of an RLC SDU is one octet short of exactly filling the last RLC PDU, and 15-bit "Length Indicators" are used, the next "Length Indicator" shall be placed as the first "Length Indicator" in the next PDU and have value "Length Indicator"=111 1111 1111 1011.
In the case where a PDU cont... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.10.3 Test purpose | 1. To test that where the UE transmits an SDU, which is one byte short of filling a PDU, an "Length Indicator" indicating one byte short is placed as the first "Length Indicator" in the next PDU.
2. To test that where the UE correctly handles a received PDU containing an "Length Indicator" indicating that an SDU ended ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.10.4 Method of test | Initial conditions
The generic procedure for Radio Bearer establishment (clause 7.1.3 of TS34.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 UM 15-bit "Length Indicator" tests in clause 7.2.2.1.
These ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 7.2.2.10.5 Test requirements | 1. The UE shall return two RLC PDUs. The first shall have no "Length Indicators". The second shall have 2 "Length Indicators". The first "Length Indicator" shall be a "Length Indicator" indicating that the SDU was one byte short of filling the previous PDU, and the second shall be a "Length Indicator" indicating that t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.