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.6.4.3.3 Test purpose
The purpose of this test case is to verify that the UE correctly handles a MAC-es/e reset procedure.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.6.4.3.4 Method of test
Initial conditions System Simulator: 1 cell, default parameters, Ciphering Off. User Equipment: The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4c (FDD) /6.11.5.4.7.6 (1.28Mcps TDD) using condition A12 (FDD) / A11 (1.28Mcps TDD) as specified in clause 9.1 of TS 34.108 as s...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.6.4.3.5 Test requirements
1. In step 9, UE shall abort transmission of the MAC-e PDU 2. In step 11, UE shall start sending loop backed PDU, with one RLC PDU per TTI. 3. In step 11, The TSN field in the MAC-es PDU shall be set to zero. 7.1.6a E-DCH MAC-es/e for 3.84 and 7.68Mcps TDD 7.1.6a.1 MAC-es/e multiplexing 7.1.6a.1.1 MAC-es/e multiplexing...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7 E-DCH MAC-i/is
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.1 MAC-i/is multiplexing (multiple PDUs from different LC in one TTI)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.1.1 Definition and applicability
Applicable for all UEs supporting MAC-i/is.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.1.2 Conformance Requirement
From 25.321 clause 9.1.5: When MAC-i/is is configured, there are two MAC sublayers, MAC-i and MAC-is. MAC-is sits on top of MAC-i and receives PDUs directly from MAC-d. When MAC-i/is is configured, a MAC PDU for E-DCH consists of one MAC-i header and one or more MAC-is PDUs. Each MAC-is PDU consists of one or more MAC-...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.1.3 Test purpose
1. To verify that the UE multiplexes data from multiple PDUs from different logical channels in the same TTI
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.1.4 Method of test
Initial conditions System Simulator: 1 cells, 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 Radio...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.1.5 Test requirements
1. After step 3 the SS shall receive an SI indicating that data is available on LCH 1, LCH 2 and LCH3 but no RLC PDUs shall be received 2. In step 7, the SS shall receive 1 RLC PDU on LCH 1 and 1 RLC PDU on LCH 3 in the same TTI 3. In step 8, the SS shall receive 1 RLC PDU on LCH2 in the next TTI
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.2 MAC-i/is segmentation / Correct Usage of Segmentation Status Field
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.2.1 Definition and applicability
Applicable for all UEs supporting MAC-i/is.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.2.2 Conformance requirement
The transmitting UM RLC entity segments the RLC SDU into UMD PDUs of appropriate size, if the RLC SDU is larger than the length of available space in the UMD PDU. The size of the UMD PDUs after segmentation and/or concatenation shall be smaller than or equal to the largest UL UMD PDU size. If MAC-i/is has been configur...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.2.3 Test purpose
To test UE is able to segment data at MAC layer and use all 4 SS values in MAC-is header.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.2.4 Method of test
Initial conditions Downlink length indicators of size 15 shall be used Uplink length indicator of size 15 shall be used Test procedure The following parameters are specific for this test case: Parameter Value Minimum UL RLC PDU 1600 bits Largest UL RLC PDU size 1600 bits Max_RLC_PDU_size 200 octets Periodicity for sche...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.2.5 Test requirements
a) In step 6, UE loop backs RLC SDU1 and first segment of RLC SDU2 in MAC-i PDU. b) In step 7, UE loop backs the final segment of RLC SDU2 in MAC-i PDU. c) In step 12, UE loops back RLC SDU3, SDU4, SDU5 in a single MAC-i PDU. d) In step 16, UE loops back RLC SDU6 in several TTIs. In the first MAC-i PDU has SS = 10, con...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.3 Correct settings of MAC-i/is header fields
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.3.1 Definition and applicability
Applicable for all UEs supporting MAC-i/is
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.3.2 Conformance requirement
Extract from 25.321: […] When MAC-i/is is configured, there are two MAC sublayers, MAC-i and MAC-is. MAC-is sits on top of MAC-i and receives PDUs directly from MAC-d and MAC-c (FDD and 1.28 Mcps TDD only). When MAC-i/is is configured, a MAC PDU for E-DCH consists of one MAC-i header and one or more MAC-is PDUs. Each M...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.3.3 Test purpose
The purpose of this test case is to verify that the UE sets the MAC-i/is header fields in the correct way for multiple logical channels on multiple flows mapped onto a single MAC-i PDU.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.3.4 Method of test
Initial conditions System Simulator: 1 cell, default parameters, Ciphering Off. User Equipment: The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.11.4k.4 (FDD) / 6.11.5.4.9.4(1.28Mcps TDD) using condition A26 (FDD) /A22 (1.28Mcps TDD) in UM as specified in clause 9.1 of TS 34.1...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.3.5 Test requirements
1. After step 4, the SS shall receive 1 MAC-is PDU shall be received where: - For MAC-is header content,, TSN = 0, SS = 00 - The content of MAC-i headers received shall be set to : LCH-ID = 0111’B, L = 22’D or 21’D, F = 0 header for MAC-is SDU1 LCH-ID = 0111'B, L = 22’D, F = 0 header for MAC-is SDU2 LCH-ID = 0111'B, L...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.4 MAC-is/i transport block size selection/ UL QPSK
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.4.1 Definition and applicability
Applicable for all UEs supporting MAC-i/is.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.4.2 Conformance requirement
Extract from TS 25.321 clause 11.8.1.4 The transmission format and data allocation shall follow the requirements below: - Only E-TFCs from the configured E-TFCS shall be considered for the transmission; […] - The UE shall not use the following E-TFCIs; - If the UE is configured with E-TFCI table 0 (see [7]) and 2ms TTI...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.4.3 Test purpose
To verify that the UE is able to transmit all possible transport block sizes when MAC-i/is is configured and within the UE capability.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.4.4 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-6 IE “E-DCH physical layer category”. All UEs supporting E-DCH should signal a category between 1 and 6 for this IE even if the UE physical capability category is above 6. NOTE: The reference to HS-DSCH Categories refers to the UE...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.4.5 Test requirements
1. In step 20, the SS verifies that the received E-TFC has the correct size. The SS checks that the UE has not used the transport block sizes correspondent to the E-TFCI values as listed in table 7.1.7.4.6, but instead used the transport block size correspondent to the next possible larger E-TFCI value. 2. In step 20, ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.5 MAC-is/i transport block size selection/ UL 16QAM
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.5.1 Definition and applicability
Applicable for all UEs supporting MAC-i/is and UL 16QAM.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.5.1 Conformance requirement
Extract from TS 25.321 clause 11.8.1.4 The transmission format and data allocation shall follow the requirements below: - Only E-TFCs from the configured E-TFCS shall be considered for the transmission; […] - The UE shall not use the following E-TFCIs; - If the UE is configured with E-TFCI table 0 (see [7]) and 2ms TTI...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.5.3 Test purpose
To verify that the UE is able to transmit all possible transport block sizes when 16QAM uplink and MAC-i/is is configured.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.5.4 Method of test
NOTE: The reference to E-DCH Category refers to the UE capability as signalled in the Rel-7 IE “E-DCH physical layer category extension”. NOTE: The reference to HS-DSCH Categories refers to the UE capability as signalled in the Rel-5 IE “HS-DSCH physical layer category” (1 to 12). All UEs supporting HS-DSCH should sign...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.5.5 Test requirements
1. In step 20, the SS verifies that the received E-TFC has the correct size. The SS checks that the UE has not used the transport block sizes correspondent to the E-TFCI values as listed in table 7.1.7.5.4, but instead used the transport block size correspondent to the next possible larger E-TFCI value. 2. In step 20, ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.6 MAC-is/i transport block size selection (1.28Mcps TDD)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.6.1 Definition and applicability
Applicable for all UEs supporting 1.28Mcps TDD and MAC-i/is.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.6.2 Conformance requirement
Extract from TS 25.321 clause 11.9.1.4 In TDD, rules for E-TFC selection shall be applied as provided below. UEs shall apply E-TFC selection when invoked by the HARQ entity (see subclause 11.9.1.1.1). For CELL-DCH state in TDD, for each MAC-d flow, RRC configures MAC-e with a HARQ profile and multiplexing list. Additio...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.6.3 Test purpose
To verify that the UE is able to transmit all possible transport block sizes when MAC-i/is is configured and within the UE capability.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.6.4 Method of test
Initial Condition Same initial conditions as in clause 7.1.6.3.5. Test Procedure Same test procedure as in clause 7.1.6.3.5. Expected sequence Same expected sequence as in clause 7.1.6.3.5. Specific Message Contents Same specific message contents as in clause 7.1.6.3.5.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.7.6.5 Test requirement
Same test requirements as in clause 7.1.6.3.5.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8 E-DCH MAC-is/i for RACH procedure
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.1 Release of common E-DCH resource when maximum resource allocation for E-DCH expires or uplink transmission ends for CCCH transmission
7.1.8.1.1 Definition and Applicability All UEs which support E-DCH in CELL_FACH 7.1.8.1.2 Conformance Requirement Extract from 25.321 11.2.2A: The allocated common E-DCH resource shall be used by MAC to carry either only CCCH transmission or only DTCH/DCCH transmission, but not both. The E-DCH enhanced physical ran...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.1.3 Test purpose
1. To verify that UE releases common E-DCH resource when max resource allocation timer of E-DCH expires for CCCH transmission. 2. To verify that UE releases common E-DCH resource when uplink transmission ends for CCCH transmission.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.1.4 Method of test
Initial conditions System Simulator: 1 cell, default parameters, Ciphering Off. User Equipment: UE: Idle state (state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE. Test procedure a) SS transmits the PAGING TYPE 1 with cause BCCH modificat...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.1.5 Test requirements
1. At step 7 , SS checks that the number of UL HARQ retransmissions for RRC CONNECTION REQUEST is less than mac-d flow max number of retransmissions, specified in SIB5 due to expiry of CCCH resource allocation timer. 2. At step 11 , SS shall check the use of PRACH Preamble and Acquisition Indication procedure to ac...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.2 Activation of HS-DPCCH based on the received SIB5/SIB5bis information
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.2.1 Definition and Applicability
All UEs which support E-DCH in CELL_FACH
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.2.2 Conformance requirement
25.331 section 8.5.45 If variable READY_FOR_COMMON_EDCH is set to TRUE, then after selection of a common E-DCH resource configuration, the RRC in the UE shall configure MAC and the physical layer for E-DCH and HSDPA transmission, and the UE shall: 1> configure Uplink DPCH in accordance with the uplink DPCCH slot format...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.2.3 Test purpose
The purpose of the test case is to verify that UE configures the HS-DPCCH based on the common E-DCH information received in SIB5/SIB5bis .
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.2.4 Method of test
Initial conditions System Simulator: 1 cell, default parameters, Ciphering Off. User Equipment: UE: Idle state (state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE. UE shall receive SIB5/SIB5bis with condition B3 “Only for cells which conf...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.2.5 Test Requirement
1. At step 6 and step 8 , SS checks the Nack/Ack on HS-DPCCH channel
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.3 DTCH/DCCH transmission - implicit common E-DCH resource release without receiving E-AGCH
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.3.1 Definition and applicability
Applicable for all UEs supporting Enhanced UL in Cell_FACH. 7.1.8.3.2 Conformance Requirement [..] • In case of DTCH/DCCH transmission, if no E-AGCH with UE’s E-RNTI has been received (through an E-RNTI-specific CRC attachment) within the maximum period for collision resolution phase, then this triggers a CMAC-STATUS ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.3.3 Test purpose
1. To verify that the UE releases E-DCH resources when no valid E-AGCH is received and allocates E-DCH resources when a valid E-AGCH is received.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.3.4 Method of test
Initial conditions UE is in Enhanced CELL_FACH state with DTCH/DCCH on common E-DCH / HS-DSCH. The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 9.1 using condition “AM Packet to Enhanced CELL_FACH from Enhanced CELL_FACH in PS with SRBs mapped on common E-DCH/HS-DSCH”. The radio...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.3.5 Test requirements
1. At step 6, the UE initiate a PRACH preamble and Acquisition Indication. 2. At step 8, the SS shall receive at least one loopback RLC PDU.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.4 DTCH/DCCH transmission – explicit common E-DCH resource release by E-AGCH
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.4.1 Definition and applicability
Applicable for all UEs supporting Enhanced UL in Cell_FACH.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.4.2 Conformance Requirement
[..] - Explicit common E-DCH resource release: In case of DTCH/DCCH transmission, if an E-AGCH with UE’s E-RNTI has been received (through an E-RNTI-specific CRC attachment) with absolute grant value set to 'INACTIVE', then this triggers a CMAC-STATUS which informs the RRC about end of the Enhanced Uplink for CELL_FACH...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.4.3 Test purpose
1. To verify that the UE releases E-DCH resources when a valid E-AGCH is received with a common E-DCH resource release command (INACTIVE).
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.4.4 Method of test
Initial conditions UE is in Enhanced CELL_FACH state with DTCH/DCCH on common E-DCH / HS-DSCH. The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 9.1 using condition “AM Packet to Enhanced CELL_FACH from Enhanced CELL_FACH in PS with SRBs mapped on common E-DCH/HS-DSCH”. The radio...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.4.5 Test requirements
At step 3, the SS shall receive the loopback PDU. At step 7, the SS shall receive the loopback PDU on E-DCH resource used other than step 3. 7.1.8.5 RACH procedure with both normal AIs and extended AIs (using E-AICH).
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.5.1 Definition and Applicability
All UEs which support E-DCH in CELL_FACH
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.5.2 Conformance Requirement
Extract from 25.211 5.3.3.7. The use of acquisition indicators is described in [5]. The meaning of acquisition indicators depends on whether a UE sends an access preamble signature corresponding to a PRACH message or corresponding to an E-DCH transmission. Furthermore, if a UE sends an access preamble signature corresp...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.5.3 Test purpose
The purpose of the test case is to verify that UE successfully completes raching procedure when E-AICH is not configured and when E-AICH is configured.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.5.4 Method of test
Initial conditions System Simulator: 1 cell, default parameters, Ciphering Off. User Equipment: UE: Idle state (state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE. Test procedure a) SS transmits the PAGING TYPE 1 with cause BCCH modificat...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.5.5 Test requirements
1. At step 7, SS checks UE does not try for RACH access after transmitting AICH = NEG ACQUISITION IND. 2. At step 11, SS shall receive RRC CONNECTION REQ sent by UE after transmitting AICH = POS ACQUISITION IND (with Index to default common E-DCH resource ) at step 10. 3. At step 20 , SS shall receive RRC CONNECTION RE...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.6 DTCH/DCCH transmission - Implicit release with E-DCH transmission continuation backoff - Timer Based
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.6.1 Definition and applicability
Applicable for all UEs supporting Enhanced UL in Cell_FACH.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.6.2 Conformance Requirement
[..] • Implicit release with E-DCH transmission continuation backoff Implicit resource release is enabled only if "E-DCH transmission continuation back off" is not set to "infinity". If implicit resource release is enabled, then in case of DTCH/DCCH transmission, the timer Tb is set to "E-DCH transmission continuation ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.6.3 Test purpose
1. To verify that the UE releases E-DCH resources implicitly only if “E-DCH transmission continuation backoff is not set to “infinity”. 2. To verify that, when “E-DCH transmission continuation backoff is set to “infinity” and all data have been sent, the UE send the Scheduling Information with empty buffer status repor...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.6.4 Method of test
Initial conditions System Simulator 1 cell, default parameters, Ciphering Off User Equipment: SS shall broadcast SIB5/SIB5bis with Common E-DCH/HS-DSCH information with specific message content given below. The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 9.1 using condition “AM...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.6.5 Test requirements
- at step 6a, UE shall perform PRACH preamble and receive Acquisition Indication before looping back data on allocated common E-DCH resource. - at step 14 UE shall loop back data and a SI with TEBS=0 in the same MAC-I PDU on existing common E-DCH resource without PRACH preamble and Acquisition Indication procedure. 7.1...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.7 Physical Channel Failure for EUL in CELL-FACH during initial access preamble
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.7.1 Definition and Applicability
All UEs which support E-DCH in CELL_FACH
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.7.2 Conformance Requirement
- If the UE according to subclause 8.5.4A in [7] failed to establish the physical channels, or if the criteria for radio link failure are met as specified in subclause 8.5.6 in [7], then the timer T2 is started. After the expiry of T2 a backoff timer TBO1 is started. Backoff timer TBO1 is set to an integer number NBO1 ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.7.3 Test purpose
To verify that UE detects physical channel failure in the RACH preamble procedure for enhanced uplink in CELL_FACH and ends that access attempt.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.7.4 Method of test
Initial conditions Test case shall be attempted on E-DCH TTI 10msec, irrespective of the device E-DCH category. System Simulator: 1 cell, default parameters, Ciphering Off. SS shall broadcast SIB5/SIB5bis with condition B3 “Only for cells which configure common E-DCH and HS-DSCH reception in CELL_FACH”. User Equipment:...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.7.5 Test requirements
1. At step 5, SS checks that UE sends another preamble. 2. At step 8 , UE should send an RRC Connection Request.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.8 Radio Link Failure for Enhanced UL in CELL-FACH with DTCH/DCCH active
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.8.1 Definition and Applicability
All UEs which support E-DCH in CELL_FACH
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.8.2 Conformance Requirement
For FDD, in CELL_FACH state and Idle mode, in conjunction with the Enhanced Uplink in CELL_FACH state, after receiving an indication from layer 1 that physical layer transmission stopped caused by an DL out-of-synchronisation, the UE shall: 1> consider it as a "Radio link failure". […] The E-DCH enhanced physical rando...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.8.3 Test purpose
To verify that UE releases common E-DCH resource in the event of radio link failure when DTCH/DCCH is active in Enhanced CELL_FACH state.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.8.4 Method of test
Initial conditions System Simulator: 1 cell, default parameters, Ciphering Off. System Information Block type 5 (FDD) Use the default parameter values for the system information block 5 with the same type specified in clause 6.1.0b of TS 34.108 for common E-DCH and HS-DSCH reception in CELL_FACH, with the following exc...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.8.5 Test requirements
- at step 4, the UE shall return 1 SDU with the same content as the transmitted SDU on common E-DCH resource without RACH preamble. - at step 8, UE shall send RACH preamble. - t step 9 the UE shall return 1 SDU with the same content as the transmitted SDU on common E-DCH resource.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.9 CCCH transmission E-DCH access, the UL transmission within the Scheduling Windows
7.1.8.9.1 Definition and Applicability 1.28Mcps TDD UEs which support E-DCH in CELL_FACH 7.1.8.9.2 Conformance Requirement Extract from 25.331 8.5.46: For 1.28 Mcps TDD, whenever the variable COMMON_E_DCH_TRANSMISSION is set to TRUE, the UE shall: 1> if CCCH message is submitted for transmission on the uplink and i...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.9.3 Test purpose
The purpose of the test case is to verify support of CCCH transmission E-DCH with common E-RNTI.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.9.4 Method of test
Initial conditions System Simulator: 1 cell, default parameters, Ciphering Off. User Equipment: UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE. Test procedure k) SS transmits the PAGING TYPE 1 with cause BCC...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.9.5 Test requirements
1. At step 5 , SS checks UE use correct common E-RNTI.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.10 DTCH/DCCH transmission with E-RUCCH access for dedicated control signalling or dedicated user data when dedicated E-RNTI is allocated
7.1.8.10.1 Definition and Applicability 1.28Mcps TDD UEs which support E-DCH in CELL_FACH 7.1.8.10.2 Conformance Requirement Extract from 25.331 8.5.46: For 1.28 Mcps TDD, whenever the variable COMMON_E_DCH_TRANSMISSION is set to TRUE, the UE shall: 1> if CCCH message is submitted for transmission on the uplink and...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.10.3 Test purpose
The purpose of the test case is to verify support of DTCH/DCCH transmission with E-RUCCH access for dedicated control signalling or dedicated user data when dedicated E-RNTI is allocated
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.10.4 Method of test
Initial conditions System Simulator: 1 cell, default parameters, Ciphering Off. User Equipment: UE: PS-DCCH+DTCH_FACH (state 6-11) as specified in clause 7.4 of TS 34.108 with a dedicated E-RNTI is allocated. Test procedure a) The SS establishes the reference radio bearer configuration specified in TS 34.108 clause 6.1...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.8.10.5 Test requirements
1. At step 19 , SS checks UE send correct RLC SDU.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.9 E-DCH MAC-is/i for Dual-Cell HSUPA
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.9.1 MAC-i/is multiplexing for Dual-Cell HSUPA
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.9.1.1 Definition and applicability
Applicable for all UEs supporting MAC-i/is, DC-HSDPA and DC-HSUPA
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.9.1.2 Conformance Requirement
From 25.321 clause 9.1.5: When MAC-i/is is configured, there are two MAC sublayers, MAC-i and MAC-is. MAC-is sits on top of MAC-i and receives PDUs directly from MAC-d. When MAC-i/is is configured, a MAC PDU for E-DCH consists of one MAC-i header and one or more MAC-is PDUs. Each MAC-is PDU consists of one or more MAC-...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.9.1.3 Test purpose
1. To verify that the UE, when Dual-Cell E-DCH is configured, multiplex multiple MAC-is PDUs into two MAC-i PDUs. 2. To verify that the UE, when Dual-Cell E-DCH is configured, use the extended TSN range (0 to 16383).
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.9.1.4 Method of test
Initial conditions 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. User Equipment: The generic procedure for Radio Bearer establishment (clause 7.1.3 o...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.1.9.1.5 Test requirements
1. At step 5 the SS shall receive 2 MAC-i PDU in the same TTI containing one RLC PDU on LCH1 and one RLC PDU on LCH2. 2. At step 5 the TSN value for both MAC-I PDUs shall be: - Frist iteration: ‘0’; - Iteration 2 to 65: ‘1’ to ‘64’