8.1A General Measurements Requirements in CELL_DCH State (1.28 Mcps option)
25.1233GPPRelease 17Requirements for support of radio resource management (TDD)TS
8.1A.1 Introduction
This section contains requirements on the UE regarding measurement reporting in CELL_DCH state. The requirements are split in TDD intra frequency, TDD inter frequency, FDD, GSM and E-UTRAN measurements. These measurements may be used by the UTRAN, e.g. for handover decisions. The measurements are defined in TS 25.225, the measurement model is defined in TS 25.302 and measurement accuracies are specified in section 9. Control of measurement reporting is specified in TS 25.331 and parallel measurements are specified in section 8.2A. For the description of the idle intervals see TS 25.225, Annex A.
8.1A.2 Requirements
8.1A.2.1 UE Measurement Capability
The UE shall be able to monitor up to
– 32 intra frequency TDD cells, and
– 32 inter frequency cells, including
– TDD cells on up to minimum 8 additional TDD carriers, and
– Depending on UE capability, FDD cells, distributed on up to 3 FDD carriers, and
– Depending on UE capability, 32 GSM cells distributed on up to 32 GSM carriers.
– Depending on UE capability, 4 E-UTRA FDD cells per E-UTRA FDD carrier for up to 4 E-UTRA FDD carriers; and
– Depending on UE capability, 4 E-UTRA TDD cells per E-UTRA TDD carrier for up to 4 E-UTRA TDD carriers.
Performance requirements for different types of measurements and different number of cells are defined in the following sections.
The requirements in section 9 are applicable for a UE performing measurements according to this section.
The received P-CCPCH Ec/Io is defined as
The received DwPTS Ec/Io is defined as
8.1A.2.2 TDD intra frequency measurements
During the CELL_DCH state the UE shall continuously measure identified intra frequency cells and search for new intra frequency cells in the monitored set. In case the UTRAN requests the UE to report detected set cells, the UE shall also search for intra frequency cells outside the monitored and active set set. Cells, which are neither included in the active set nor in the monitored set, and are identified by the UE belong to the detected set according to TS 25.331. Intra frequency measurements can be performed (simultaneously to data reception from the active cell) in all time slots not used for inter frequency measurements.
8.1A.2.2.1 Identification of a new cell
The UE shall be able to identify a new detectable cell belonging to the monitored set within
ms
A cell shall be considered detectable when P-CCPCH Ec/Io > -8 dB and DwPCH_Ec/Io > -5 dB. When L3 filtering is used an additional delay can be expected.
The UE shall be able to identify a new detectable cell not belonging to the monitored set within
when P-CCPCH Ec/Io > -8 dB, DwPCH_Ec/Io > -5 dB. When L3 filtering is used an additional delay can be expected.
8.1A.2.2.2 UE P-CCPCH RSCP measurement capability
In the CELL_DCH state the measurement period for intra frequency P-CCPCH RSCP measurements is 200 ms. When all TS0, DwPTS and main guard periods in the measurement period are scheduled for intra frequency measurements, the UE shall be capable of performing P-CCPCH RSCP measurements for 6 identified intra-frequency cells of the monitored set and the UE physical layer shall be capable of reporting these measurements to higher layers with the measurement period of 200 ms. When inter-frequency measurements required by the network have to be performed during periods of TS0, DwPTS or main guard period, the UE shall be capable of performing P-CCPCH RSCP measurements for at least Ymeasurement intra cells , where Ymeasurement intra is defined in the following equation. The measurement accuracy for all measured cells shall be as specified in the section 9. If the UE has identified more than Ymeasurement intra cells, the UE shall perform measurements of all identified cells but the reporting rate of P-CCPCH RSCP measurements of cells from UE physical layer to higher layers may be decreased.
whereby function Floor(x) takes the integer part of x.
Xbasic measurement TDD= 6 (cells)
TMeasurement_Period, Intra =200 ms. The measurement period for Intra frequency P-CCPCH RSCP measurements.
NPeriod,Intra: = 40 Number of subframes in TMeasurement_Period, Intra.
NIntra : This is the minimum number of sub-frame in that the period of TS0, DwPTS and main guard period is available for intra frequency measurements, during the measurement period.
Tbasic_identify_TDD, intra = 800 ms. This is the time period used in the intra frequency equation where the maximum allowed time for the UE to identify a new TDD cell is defined.
The UE shall furthermore be capable of performing P-CCPCH measurements for at least 1 detected intra-frequency cell, in the detected set, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement period of 10 s. The measurement accuracy for all measured cells shall be as specified in the section 9.
8.1A.2.2.2A Timeslot ISCP measurement capability
In the CELL_DCH state the measurement period for intra frequency Timeslot ISCP measurements on arbitrary DL timeslots, including Beacon timeslots is 400 ms. When no inter frequency measurement is scheduled, the UE shall be capable of performing Timeslot ISCP measurements for a total of 5 different combinations of an arbitrary DL timeslot and an intra-frequency cell [16], including the current serving cell. The UE physical layer shall be capable of reporting Timeslot ISCP measurements to higher layers with the measurement period of 400 ms.
When inter-frequency measurements are required by the network, the UE shall be able to perform Timeslot ISCP measurements for at least Ymeasurement intra ISCP different combinations, where Ymeasurement intra ISCP is defined in the following equation. Any Timeslot ISCP measurement that could not be performed during that measurement period, shall be measured in the following measurement periods. The measurement accuracy of the Timeslot ISCP measurement shall be as specified in the section 9.
whereby function Floor(x) takes the integer part of x.
Xbasic measurement ISCP = 5 (combinations of an arbitrary DL timeslot and an intra-frequency cell)
TMeasurement_Period, Intra, ISCP = 400 ms. The measurement period for Intra frequency Timeslot ISCP measurements.
TIntra: This is the minimum time (representing a time corresponding to an integer number of full slots) that is available for intra frequency measurements, during the measurement period with an arbitrarily chosen timing.
8.1A.2.2.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in section 9.
8.1A.2.2.4 Event-triggered Periodic Reporting
Reported measurements in event triggered periodic measurement reports shall meet the requirements in section 9.
The first report in event triggered periodic measurement reporting shall meet the requirements specified in section 8.1A.2.2.5 Event Triggered Reporting.
8.1A.2.2.5 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in section 9.
The UE shall not send event triggered measurement reports, as long as the reporting criteria are not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report, until the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH . The delay uncertainty is twice the TTI of the uplink DCCH.
The event triggered measurement reporting delay, on cells belonging to monitored set, measured without L3 filtering shall be less than T identify intra defined in Section 8.1A.2.2.1
If a cell belonging to monitored set has been detectable at least for the time period Tidentify_intra and then enters or leaves the reporting range, the event triggered measurement reporting delay shall be less than TMeasurement_Period Intra when the L3 filter has not been used and the UE P-CCPCH measurement capabilities of Section 8.1A.2.2.2 are valid.
The event triggered measurement reporting delay on cells not belonging to monitored set, measured without L3 filtering, shall be less than the above defined T identify detected set . defined in Section 8.1A.2.2.1.
8.1A.2.3 TDD inter frequency measurements
When signalled by the network during CELL_DCH state, the UE shall continuously measure identified inter frequency TDD cells and search for new inter frequency TDD cells indicated in the measurement control information.
8.1A.2.3.1 Identification of a new cell
When idle intervals are used for inter-frequency TDD measurements, the UE shall be able to identify a new detectable cell belonging to the monitored set within
If the UE does not require idle intervals to perform inter-frequency TDD measurements, the UE shall be able to identify a new detectable inter-frequency TDD cell belonging to the monitored set within 5000 ms.
A cell shall be considered detectable when P-CCPCH Ec/Io > -8 dB and DwPCH_Ec/Io > -5 dB. When L3 filtering is used an additional delay can be expected.
8.1A.2.3.2 UE P-CCPCH RSCP measurement capability
When idle intervals are used for TDD inter frequency measurements, the UE physical layer shall be capable of reporting P-CCPCH RSCP measurements to higher layers with measurement accuracy as specified in section 9 and with measurement period given by
If the UE does not require idle intervals to perform TDD inter-frequency measurements, the measurement period for inter frequency P-CCPCH RSCP measurements is 480 ms.
The UE shall be capable of performing P-CCPCH RSCP measurements for Xbasic measurement TDD inter inter-frequency cells per TDD frequency of the monitored set, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement period of TMeasurement_ Inter.
Xbasic measurement TDDinter =6
TMeasurement_Period Inter=480 ms. The period used for calculating the measurement period Tmeasurement_inter for inter frequency P-CCPCH RSCP measurements.
NInter: This is the minimum number of sub-frame in that the signal of P-CCPCH and DwPCH can be received for inter frequency target cell during the period TMeasurement_Period inter with an arbitrarily chosen timing. It depends on the channel allocation and is calculated by assuming 2*0.1ms for implementation margin (for the description of the idle intervals see Annex A of 25.225).
Tbasic_identify_TDD,inter= 800ms. This is the time period used in the inter frequency equation where the maximum allowed time for the UE to identify a new TDD cell is defined.
Nbasic identify TDD, Inter= 160, Number of subframes in Tbasic identify TDD, inter.
Tbasic_measurement_TDD inter = 50 ms. This is the time period used in the equation for defining the measurement period for inter frequency P-CCPCH RSCP measurements.
Nbasic measurement TDD, Inter= 10, Number of subframes in Tbasic measurement TDD Inter.
NFreq Number of TDD frequencies indicated in the inter frequency measurement control information.
8.1A.2.3.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in section 9.
8.1A.2.3.4 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in section 9.
The UE shall not send event triggered measurement reports, as long as the reporting criteria is not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report, until the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH . The delay uncertainty is twice the TTI of the uplink DCCH.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify inter defined in Section 8.1A.2.3.1. When L3 filtering is used an additional delay can be expected.
8.1A.2.4 FDD measurements
The requirements in this section shall apply to UE supporting 1.28Mcps TDD and FDD.
In the CELL_DCH state when FDD inter frequency measurements are scheduled the UE shall continuously measure identified inter frequency FDD cells and search for new inter frequency FDD cells indicated in the measurement control information.
8.1A.2.4.1 Identification of a new cell
When idle intervals are used for inter-frequency FDD measurements, the UE shall be able to identify a new detectable cell belonging to the monitored set within
IF the UE does not require idle intervals to perform inter-frequency FDD measurements, the UE shall be able to identify a new detectable inter-frequency FDD cell belonging to the monitored set within 5000 ms.
When L3 filtering is used an additional delay can be expected.
A cell shall be considered detectable when CPICH Ec/Io > -20 dB, SCH_Ec/Io > -17 dB and SCH_Ec/Ior is equally divided between primary synchronisation code and secondary synchronisation code.
8.1A.2.4.2 UE CPICH measurement capability
When idle intervals are used for FDD inter frequency measurements, the UE physical layer shall be capable of reporting measurements to higher layers with measurement accuracy as specified in sub-clause 9 with measurement period given by
If the UE does not need idle intervals to perform FDD measurements, the measurement period for inter frequency measurements is 480 ms.
The UE shall be capable of performing FDD measurements for Xbasic measurement FDD inter inter-frequency cells per FDD frequency of the monitored set, and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement period of TMeasurement_FDDInter.
Xbasic measurement FDDinter = 6
TMeasurement_Period FDD inter = 480 ms. The period used for calculating the measurement period Tmeasurement_FDD inter for inter frequency CPICH measurements.
TFDD inter: This is the minimum time that is available for inter frequency measurements, during the period TMeasurement_Period FDD inter with an arbitrarily chosen timing. The minimum time depends on the channel allocation and is calculated by assuming 2*0.1 ms for implementation margin (for the description of the idle intervals see Annex A of 25.225). It is assumed for the requirement that the slot allocation allows measurement windows in the idle periods to be of minimum duration necessary to perform the measurements.
Tbasic_identify_FDD,inter = 800 ms. This is the time period used in the inter frequency equation where the maximum allowed time for the UE to identify a new FDD cell is defined.
Tbasic_measurement_FDD inter = 50 ms. This is the time period used in the equation for defining the measurement period for inter frequency CPICH measurements.
NFreq: Number of FDD frequencies indicated in the inter frequency measurement control information.
8.1A.2.4.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in section 9.
8.1A.2.4.4 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in section 9.
The UE shall not send event triggered measurement reports as long as the reporting criteria are not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report until the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertanty is twice the TTI of the uplink DCCH.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than T identify FDD inter defined in Section 8.1A.2.4.1. When L3 filtering is used an additional delay can be expected.
If a cell has been detectable at least for the time period Tidentify_FDD inter and then enters the reporting range, the event triggered measurement reporting delay shall be less than TMeasurement_Period FDD Inter provided the timing to that cell has not changed more than +/-32 chips while idle intervals have has not been available and the L3 filter has not been used.
8.1A.2.5 GSM measurements
The requirements in this section shall apply to UE supporting 1.28Mcps TDD and GSM.
Measurements on GSM cells can be requested with BSIC verified or BSIC non-verified.
1) For a UE requiring idle intervals to perform GSM measurements. In CELL_DCH state when signalled by UTRAN and when idle intervals are used, the UE shall continuously measure GSM cells and search for new GSM cells given in the monitored set.
2) For a UE not requiring idle intervals to perform GSM measurements:
– the UE shall measure all GSM cells present in the monitored set
– the relevant requirements for GSM dedicated mode when a TCH channel is assigned in TS 45.008 shall apply. This is further detailed in the following sub-sections.
8.1A.2.5.1 GSM carrier RSSI
1) For a UE requiring idle intervals to perform GSM measurements
An UE supporting GSM measurements using idle intervals shall meet the minimum number of GSM RSSI carrier measurements specified in table 8.1A.
In the CELL_DCH state the measurement period, TMeasurement Period, GSM, for the GSM carrier RSSI measurement is 480 ms.
The UE shall meet the measurement accuracy requirements stated for RXLEV in TS 45.008, when the given measurement time allows the UE to the take at least 3 GSM carrier RSSI samples per GSM carrier in the monitored set during the measurement period.
Table 8.1A
Idle Interval Length (timeslots) |
Number of GSM carrier RSSI samples in each idle interval |
3 |
1 |
4 |
2 |
5 |
3 |
For the description of the idle intervals see Annex A of 25.225.
In case the UE is not able to acquire the required number of samples per GSM carrier during one measurement period, the UE shall measure as many GSM carriers as possible during that measurement period using at least 3 samples per GSM carrier. The GSM carriers that were not measured during that measurement period shall be measured in the following measurement periods. This means that, in this particular case, the L1 reporting period to higher layers of a GSM neighbour can be a multiple of the measurement period.
2) For a UE not requiring idle intervals to perform GSM measurements
The samples allocated to each carrier shall as far as possible be uniformly distributed over each measurement period. At least 3 received signal level measurement samples are required per RSSI value. The measurement period is 480 ms.
8.1A.2.5.2 BSIC verification
1) For a UE requiring idle intervals to perform GSM measurements
The procedure for BSIC verification on a GSM cell can be divided into the following two tasks:
1) Initial BSIC identification
Includes searching for the BSIC and decoding the BSIC for the first time when there is no knowledge about the relative timing between the TDD and GSM cell. The UE shall trigger the initial BSIC identification within the available idle intervals. The requirements for Initial BSIC identification can be found in section 8.1A.2.5.2.1,"Initial BSIC identification".
2) BSIC re-confirmation
Tracking and decoding the BSIC of a GSM cell after initial BSIC identification is performed. The UE shall trigger the BSIC re-confirmation within the available idle intervals. The requirements for BSIC re-confirmation can be found in section 8.1A.2.5.2.2, "BSIC re-confirmation".
Measurements on a GSM cell can be requested with BSIC verified or BSIC non-verified. If GSM measurements are requested with BSIC verified the UE shall be able to report the GSM cells with BSIC verified for those cells where the verification of BSIC has been successful.
The UE shall use the last available GSM carrier RSSI measurement results for arranging GSM cells in signal strength order for performing BSIC identification. The UE shall perform event evaluation for event-triggered reporting after the BSIC has been verified for a GSM cell. The UE shall use the last available GSM carrier RSSI measurement results in event evaluation and event-triggered reporting. Periodic reports shall be triggered according to Sections 8.6.7.5 and 8.6.7.6 of [16]
The BSIC of a GSM cell is considered to be "verified" if the UE has decoded the SCH of the BCCH carrier and identified the BSIC at least one time (initial BSIC identification) and from that moment the BSIC shall be re-confirmed at least once every Tre-confirm abort seconds. Otherwise the BSIC of the GSM cell is considered as "non-verified". The time requirement for initial BSIC identification, Tidentify abort, and the BSIC re-confirmation interval Tre-confirm abort can be found in the sections below.
The UE shall be able to perform BSIC verification at levels down to the reference sensitivity level or reference interference levels as specified in TS 45.005.
2) For a UE not requiring idle intervals to perform GSM measurements
If a BSIC is decoded and matches the expected value, it is considered as "verified", else it is considered as "non verified".
The UE shall be able to perform BSIC verification at levels down to the reference sensitivity level or reference interference levels as specified in TS 45.005.
8.1A.2.5.2.1 Initial BSIC identification
For GSM cells that are requested with BSIC verified the UE shall attempt to decode the SCH on the BCCH carrier of the8 strongest BCCH carriers of the GSM cells indicated in the measurement control information. The UE shall give priority for BSIC decoding attempts in decreasing signal strength order to BSIC carriers with unknown BSIC. The strongest BCCH carrier is defined as the BCCH carrier having the highest measured GSM carrier RSSI value after layer 3 filtering. The GSM signal strength levels used in BSIC identification for arranging GSM cells in signal strength order shall be based on the latest GSM carrier RSSI measurement results available.
If the BSIC of a GSM BCCH carriers has been successfully decoded the UE shall immediately continue BSIC identification with the next BCCH carrier, in signal strength order, with unknown BSIC. The GSM cell for which the BSIC has been successfully identified shall be moved to the BSIC re-confirmation procedure.
If the UE has not successfully decoded the BSIC of the GSM BCCH carrier within Tidentify abort, the UE shall abort the BSIC identification attempts for that GSMBCCH carrier. The UE shall continue to try to perform BSIC identification of the next GSM BCCH carrier in signal strength order. The GSM BCCH carrier for which the BSIC identification failed shall not be re-considered for BSIC identification until BSIC decoding attempts have been made for all the rest of the 8 strongest GSM BCCH carriers in the monitored set with unknown BSIC.
Tidentify abort = 5000 ms. This is the time necessary to identify one new GSM cell. It is assumed for the requirement that the slot allocation allows measurement windows in the idle periods to be of minimum duration necessary to perform the measurements.
8.1A.2.5.2.2 BSIC re-confirmation
The requirements of this section are applicable for BSIC re-confirmation.
The UE shall maintain the timing information of at least 8 identified GSM cells. Initial timing information is obtained from the initial BSIC identification. The timing information shall be updated every time the BSIC is decoded.
For each idle interval, the UE is able to use for BSIC re-confirmation, the UE shall attempt to decode the BSIC falling within the effective measurement window. If more than one BSIC can be decoded within the same measurement window given by the idle intervals, priority shall be given to the least recently decoded BSIC.
If the UE fails to decode the BSIC after two successive attempts or if the UE has not been able to re-confirm the BSIC for a GSM BCCH carrier within Tre-confirm_abort seconds, the UE shall abort the BSIC re-confirmation attempts for that GSM BCCH carrier. The GSM BCCH carrier shall be treated as a new GSM BCCH carrier with unidentified BSIC and the GSM BCCH carrier shall be moved to the initial BSIC decoding procedure, see section 8.1A.2.5.2.1. The UE shall be able to make BSIC re-confirmation attempts for the 8 strongest GSM cells in the monitored list.
Tre-confirm abort =5000 ms. This is the BSIC reconfirmation interval.
It is assumed for the requirement that the slot allocation allows measurement windows in the idle periods to be of minimum duration necessary to perform the measurements.
8.1A.2.5.2.3 Periodic Reporting
Reported measurements in periodically triggered measurement reports shall meet the requirements in section 9.
8.1A.2.5.2.4 Event Triggered Reporting
Reported measurements in event triggered measurement reports shall meet the requirements in section 9.
The UE shall not send any event triggered measurement reports, as long as the reporting criteria is not fulfilled.
The measurement reporting delay is defined as the time between any event that will trigger a measurement report until the UE starts to transmit the measurement report over the Uu interface. This requirement assumes that that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH.
The event triggered reporting delay requirement is valid when the UE for each GSM carrier in the monitored set can take the required number of samples during the measurement period TMeasurement Period, GSM (see section 8.1A.2.5.1).
The event triggered measurement reporting delay for a GSM cell with verified BSIC, measured without L3 filtering shall be less than 2*TMeasurement Period, GSM, where TMeasurement Period, GSM is defined in Section 8.1A.2.5.1. When L3 filtering is used an additional delay can be expected. For a GSM cell with non-verified BSIC an additional delay according to section 8.1A.2.5.2.1 Initial BSIC identification can be expected.
8.1A.2.6 E-UTRAN FDD measurements
The requirements in this section apply only to UEs supporting 1.28Mcps TDD and E-UTRAN FDD.
1) For a UE requiring idle intervals to perform E-UTRAN FDD measurements:
– a minimum idle interval of 6ms shall be scheduled by the network.
– when signalled by UTRAN, the UE shall continuously measure previously detected E-UTRAN FDD cells and search for new E-UTRAN FDD cells.
2) For a UE not requiring idle intervals to perform E-UTRAN FDD measurements:
– the UE shall measure either all E-UTRAN FDD cells present in the monitored set or, if only frequencies are provided in the neighbour cell list, the strongest cells present in the detected set, up to the monitoring capabilities of the UE.
– the relevant requirements for E-UTRAN RRC_CONNECTED mode specified in 3GPP TS 36.133 [24] shall apply. This is further detailed in the following subclauses 8.1A.2.6.1.
8.1A.2.6.1 Identification of a new cell
When idle intervals are used for E-UTRAN FDD measurements, the UE shall be able to identify a new detectable E-UTRAN FDD cell within
;
If the UE does not need idle intervals to perform E-UTRAN FDD measurements, the UE shall be able to identify a new detectable E-UTRAN FDD cell within ms.
Where:
TE-UTRAN FDD: This is the minimum time that is available for E-UTRAN FDD measurements during the measurement period TMeasurement_Period_E-UTRAN FDD with an arbitrarily chosen timing. The minimum time per idle interval is calculated by assuming 2*0.5 ms for implementation margin.
TBasic_Identify_E-UTRAN FDD = 480 ms
When L3 filtering is used an additional delay can be expected.
An E-UTRAN FDD cell shall be considered detectable when
– RSRP|dBm and RSRP Ês/Iot, according to Annex B.2.2 for a corresponding Band
– Other RSRP and RSRQ related side condition given in Section 9.1 of [24] are fulfilled for a corresponding Band,
– SCH_RP|dBm and SCH_ES/Iot, according to Annex B.2.2 for a corresponding Band
8.1A.2.6.2 E-UTRAN RSRP and RSRQ measurement period
When idle intervals are scheduled for E-UTRAN FDD measurements the UE physical layer shall be capable of reporting measurements to higher layers with measurement accuracy as specified in sub-clause 9.1.1.5a and 9.1.1.5b with measurement period of TMeasurement_Period_E-UTRAN FDD = 480 x NFreq ms where NFreq is the number of FDD frequencies indicated in the E-UTRAN measurement control information.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 4 E-UTRAN FDD cells per E-UTRAN FDD frequency for up to 4 FDD E-UTRAN frequencies.
8.1A.2.6.3 Periodic reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in section 9.
8.1A.2.6.4 void
8.1A.2.6.5 Event Triggered reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in section 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. This measurement reporting delay excludes a delay which caused by no UL resources for UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than Tidentify E-UTRAN FDD defined in Section 8.1A.2.6.1. When L3 filtering is used an additional delay can be expected.
- If a cell has been detectable at least for the time period Tidentify E-UTRAN FDD and then enters or leaves the reporting range, the event triggered measurement reporting delay shall be less than TMeasurement_Period_E-UTRAN_FDD provided the timing to that cell has not changed more than ±50 TS while idle interval has not been available and the L3 filter has not been used.
8.1A.2.7 E-UTRAN TDD measurements
The requirements in this section apply only to UEs supporting 1.28Mcps TDD and E-UTRAN TDD.
1) For a UE requiring idle intervals to perform E-UTRAN TDD measurements:
– a minimum idle interval of 6ms shall be scheduled by the network.
– when signalled by UTRAN, the UE shall continuously measure previously detected E-UTRAN TDD cells and search for new E-UTRAN TDD cells.
2) For a UE not requiring idle intervals to perform E-UTRAN TDD measurements:
– the UE shall measure either all E-UTRAN TDD cells present in the monitored set or, if only frequencies are provided in the neighbour cell list, the strongest cells present in the detected set, up to the monitoring capabilities of the UE.
– the relevant requirements for E-UTRAN RRC_CONNECTED mode specified in 3GPP TS 36.133 [24] shall apply. This is further detailed in the following subclauses 8.1A.2.7.1.
8.1A.2.7.1 Identification of a new cell
When idle intervals are used for E-UTRAN measurements, the UE shall be able to identify a new detectable E-UTRAN TDD cell within
;
If the UE does not need idle intervals to perform E-UTRAN TDD measurements, the UE shall be able to identify a new detectable E-UTRAN TDD cell within ms.
Where:
TE-UTRAN TDD: This is the minimum time that is available for E-UTRAN TDD measurements during the measurement period TMeasurement_Period_E-UTRAN TDD with an arbitrarily chosen timing. The minimum time per idle interval is calculated by assuming 2*0.5 ms for implementation margin.
TBasic_Identify_E-UTRAN TDD = 480 ms
When L3 filtering is used an additional delay can be expected.
– An E-UTRAN TDD cell shall be considered detectable when
– RSRP|dBm and RSRP Ês/Iot, according to Annex B.2.2 for a corresponding Band
– Other RSRP and RSRQ related side condition given in Section 9.1 of [24] are fulfilled for a corresponding Band,
– SCH_RP|dBm and SCH Ês/Iot, according to Annex B.2.2 for a corresponding Band
8.1A.2.7.2 E-UTRAN RSRP and RSRQ measurement period
When idle intervals are scheduled for E-UTRAN TDD measurements the UE physical layer shall be capable of reporting measurements to higher layers with measurement accuracy as specified in sub-clause 9.1.1.5a and 9.1.1.5b with measurement period of TMeasurement_Period_E-UTRAN TDD = 480 x NFreq ms where NFreq is the number of TDD frequencies indicated in the E-UTRAN measurement control information.
The UE shall be capable of performing RSRP and RSRQ measurements of at least 4 E-UTRAN TDD cells per E-UTRAN TDD frequency for up to 4 E-UTRAN TDD frequencies.
8.1A.2.7.3 Periodic reporting
Reported measurements contained in periodically triggered measurement reports shall meet the requirements in section 9.
8.1A.2.7.4 void
8.1A.2.7.5 Event Triggered reporting
Reported measurements contained in event triggered measurement reports shall meet the requirements in section 9.
The UE shall not send any event triggered measurement reports, as long as no reporting criteria are fulfilled.
The measurement reporting delay is defined as the time between an event that will trigger a measurement report and the point when the UE starts to transmit the measurement report over the air interface. This requirement assumes that the measurement report is not delayed by other RRC signalling on the DCCH. This measurement reporting delay excludes a delay uncertainty resulted when inserting the measurement report to the TTI of the uplink DCCH. The delay uncertainty is twice the TTI of the uplink DCCH. This measurement reporting delay excludes a delay which caused by no UL resources for UE to send the measurement report.
The event triggered measurement reporting delay, measured without L3 filtering shall be less than TIdentify E-UTRAN TDD defined in Section 8.1A.2.7.1. When L3 filtering is used an additional delay can be expected.
- If a cell has been detectable at least for the time period TIdentify E-UTRAN TDD and then enters or leaves the reporting range, the event triggered measurement reporting delay shall be less than TMeasurement_Period_E-UTRAN_TDD provided the timing to that cell has not changed more than ±50 TS while idel interval has not been available and the L3 filter has not been used.