8.1B General Measurement Requirements in CELL_DCH State (7.68 Mcps option)

25.1233GPPRelease 17Requirements for support of radio resource management (TDD)TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

8.1B.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 and GSM measurements. These measurements may be used by the UTRAN, e.g. for handover decisions. The measurements are defined in [14], the measurement model is defined in [15] and measurement accuracies are specified in section 9. Control of measurement reporting is specified in [16] and parallel measurements are specified in section 8.2B. For the description of the idle intervals see [14].

8.1B.2 Requirements

8.1B.2.1 UE Measurement Capability

The UE shall be able to monitor up to

– 32 intra frequency TDD cells (including serving cell), and

– 32 inter frequency cells, including

– TDD mode cells distributed on up to 2 additional TDD carriers and

– Depending on UE capability, FDD mode cells, distributed on up to 3 FDD carriers.

– Depending on UE capability, 32 inter RAT GSM cells.

– 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.

The requirements in section 9 are applicable for a UE performing measurements according to this section.

For measurements on intra- and inter-frequency TDD, inter-frequency FDD and GSM cells, idle intervals as described in [14] can be used. The time T_measure per 480 ms period available for these measurements is the sum of the duration of all idle intervals during any given 480 ms period, i.e. the amount of time not used by the UE for receiving in active DL timeslots or for transmission in active UL timeslots. Note that Beacon timeslots of the serving cell can be located inside idle intervals and that implementation margin due to frequency switching is not taken into account for T_measure.

The requirements in this section are based upon the assumption, that the time durations T_intra and T_inter during any given 480 ms period for the purpose of measurements on intra-frequency TDD cells and for measurements on inter-frequency TDD, inter-frequency FDD and GSM cells are respectively,

where, M_intra is equal to the number of intra-frequency TDD cells in the neighbour list

The time duration T_inter shall be equally shared for inter-frequency measurements on the different modes and systems which the UE has capability for and that are in the monitored set signalled by UTRAN, i.e.

For this, the following parameters are defined,

T_{TDD inter} is the time duration allocated for the purpose of TDD inter-frequency measurements.

T_{FDD inter}is the time duration allocated for the purpose of FDD inter-frequency measurements.

T_{GSM inter}is the time duration allocated for the purpose of GSM measurements.

N_TDDis equal to 1 if there are inter-frequency TDD cells in the neighbour list, equal to 0 otherwise.

N_FDDis equal to 1 if the UE has capability for FDD and if there are inter-frequency FDD cells in the neighbour list, equal to 0 otherwise.

N_GSM is equal to 1 if the UE has capability for GSM and if there are GSM cells in the neighbour list, equal to 0 otherwise.

8.1B.2.2 TDD intra frequency measurements

During the CELL_DCH state, the UE shall continuously measure identified intra frequency TDD cells and search for new intra frequency TDD 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 TDD cells outside the monitored and active 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 [16].

In order for the requirements in the following subsections to apply, the Beacon timeslots of the intra-frequency TDD cells indicated in the measurement control information shall either be synchronised with the Beacon timeslots of the serving cell or non-overlapping in time with the active UL timeslots used by the UE for transmission, such that the UE can measure an intra-frequency TDD cell at least once every frame for the slot allocation case in use in this cell. The UE shall be capable of intra frequency measurements during active DL timeslots.

8.1B.2.2.1 Identification of a new cell

The UE shall be able to identify a new detectable intra-frequency TDD cell belonging to the monitored set within T_{identify intra} ms, where T_{identify intra} = 800 ms.

When L3 filtering is used, an additional delay can be expected.

8.1B.2.2.2 UE P-CCPCH RSCP measurement capability

In CELL_DCH state, the UE shall be capable of performing P-CCPCH RSCP measurements for X_{measurement intra} identified intra-frequency TDD cells of the monitored set with a measurement period for intra-frequency P-CCPCH RSCP measurements T_{measurement period intra,}where

X_{measurement intra} = 6 (cells)

T_{measurement period intra} = 200 ms

The UE physical layer shall be capable of reporting these measurements to higher layers with the measurement period T_{measurement period intra}.

If the UE has identified more than X_{measurement intra} intra-frequency TDD cells, the UE shall perform measurements of all identified cells but the reporting rate of P-CCPCH RSCP measurements of cells from the UE physical layer to higher layers may be decreased.. The measurement accuracy for all measured cells shall be as specified in the section 9.

8.1B.2.2.3 Timeslot ISCP measurement capability

In 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 10 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 capable of performing Timeslot ISCP measurements for at least Y_{measurement intra ISCP}different combinations, where Y_{measurement 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.

– X_{basic measurement ISCP}= 10 (combinations of an arbitrary DL timeslot and an intra-frequency cell)

– T_{measurement_period, intra, ISCP}= 400 ms. The measurement period for intra frequency Timeslot ISCP measurements.

– T_intra is specified in 8.1B.2.1.

8.1B.2.2.4 Periodic Reporting

Reported measurements in periodically triggered measurement reports shall meet the requirements in section 9.

8.1B.2.2.5 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.1B.2.2.6 Event Triggered Reporting.

8.1B.2.2.6 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.

For P-CCPCH RSCP measurements, the event triggered measurement reporting delay, on cells belonging to the monitored set, measured without L3 filtering shall be less than T _{identify intra} defined in Section 8.1B.2.2.1.When L3 filtering is used an additional delay can be expected..

If a cell, belonging to the monitored set has been detectable at least for the time period T_{identify intra} and then enters the reporting range, the event triggered P-CCPCH RSCP measurement reporting delay shall be less than T_{measurement_period intra} when the L3 filter has not been used and the UE P-CCPCH RSCP measurement capabilities of section 8.1B.2.2.1 are valid.

8.1B.2.3 TDD inter frequency measurements

When signalled by UTRAN during CELL_DCH state, the UE shall continuously measure detected inter-frequency TDD cells and search for new inter-frequency TDD cells indicated in the measurement control information.

In order for the requirements in the following subsections to apply, the Beacon timeslots of the inter-frequency TDD cells indicated in the measurement control information shall be non-overlapping in time with the active DL and UL timeslots used by the UE for reception and transmission such that the UE can measure an inter-frequency cell TDD cell at least once every frame for the slot allocation case in use in this cell and by assuming 2*0.5 ms implementation margin for frequency switching per idle interval.

8.1B.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 inter-frequency TDD 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.

When L3 filtering is used, an additional delay can be expected.

8.1B.2.3.2 P-CCPCH RSCP measurement period

When idle intervals are used for TDD inter frequency measurements, the UE shall be capable of performing P-CCPCH RSCP measurements for X_{measurement TDD inter} inter-frequency TDD cells per TDD frequency of the monitored set.

The UE physical layer shall be capable of reporting measurements to higher layers with measurement accuracy as specified in section 9 and with a measurement period of T_{measurement inter}.

If the UE does not require idle intervals to perform TDD inter-frequency measurements, the measurement period for inter frequency P-CCPCH RSCP measurements shall be 480 ms.

Where,

X_{measurement TDD inter} = 6 (cells)

T_{measurement_period inter}= 480 ms. The time period used for calculating the measurement period T_{measurement_inter} for inter frequency P-CCPCH RSCP measurements.

N_TDD _inter: This is the available number of measurement opportunities for a Beacon timeslot of an inter-frequency TDD cell during the time period T_{TDD inter}. The UE shall consider that a measurement opportunity on a Beacon timeslot of an inter-frequency TDD cell is provided if an idle interval of length equal to or greater than 3 timeslots less 2*0.5 ms implementation margin for frequency switching per idle interval completely overlaps in time with the Beacon timeslot of the inter-frequency TDD cell.

N_{basic_identify_TDD inter} = 80. This is a number of measurement opportunities for a Beacon timeslot of an inter-frequency TDD cell during the time period used in the inter frequency TDD equation where the maximum allowed time for the UE to identify a new detectable inter-frequency TDD cell is defined.

N_{basic_measurement_TDD inter} = 5. This is a number of measurement opportunities for a Beacon timeslot of an inter-frequency TDD cell during the time period T_{TDD inter} used in the inter-frequency TDD equation where the measurement period for inter-frequency P-CCPCH RSCP measurements is defined.

N_{Freq TDD}: This is the number of TDD frequencies indicated in the inter frequency measurement control information.

Note that the number of measurement opportunities available to the UE depends on UL and DL timeslot assignments for transmission and reception and on Beacon timeslot allocations in the inter-frequency TDD cells.

8.1B.2.3.3 Periodic Reporting

Reported measurements in periodically triggered measurement reports shall meet the requirements in section 9.

8.1B.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.1B.2.3.1When L3 filtering is used an additional delay can be expected.

If an intra frequency TDD cell has been detectable at least for the time period T_{identify_ inter} and then enters the reporting range, the event triggered measurement reporting delay shall be less than T_{measurement_period inter} when the L3 filter has not been used.

8.1B.2.4 FDD measurements

The requirements in this section shall apply to UE supporting TDD and FDD.

In the CELL_DCH state when FDD inter frequency measurements are scheduled the UE shall continuously measure detected inter frequency FDD cells and search for new inter frequency FDD cells indicated in the measurement control information.

8.1B.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 inter-frequency FDD cell belonging to the monitored set within

If the UE does not require idle intervals to perform FDD inter-frequency 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.

An inter-frequency FDD 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.1B.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 require idle intervals to perform FDD inter-frequency measurements, the measurement period for inter frequency CPICH measurements shall be 480 ms.

The UE shall be capable of performing CPICH measurements for X_{measurement FDD inter} inter-frequency FDD cells per frequency of the monitored set and the UE physical layer shall be capable of reporting measurements to higher layers with the measurement period of T_{measurement FDD inter}.

X_{basic measurement FDD inter} = 6 (cells)

T_{measurement_period FDD inter}= 480 ms. The time period used for calculating the measurement period T_{measurement_FDD inter} for inter frequency CPICH measurements.

T_FDD _{inter: available}: This is the available time for measurements on inter-frequency FDD cells. T_{FDD inter available} shall be derived from T_{FDD inter} by assuming 2*0.5 ms implementation margin for frequency switching per idle interval and by only taking into account the remaining number of full timeslots per idle interval. Idle intervals smaller than 3 timeslots shall not be taken into account for calculating T_{FDD inter available}.

T_{basic_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 detectable inter-frequency FDD cell is defined.

T_{basic_measurement_FDD inter} = 50 ms. This is the time period used in the inter-frequency equation for defining the measurement period for inter frequency CPICH measurements.

N_Freq: This is the number of FDD frequencies indicated in the inter frequency measurement control information.

8.1B.2.4.3 Periodic Reporting

Reported measurements in periodically triggered measurement reports shall meet the requirements in section 9.

8.1B.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.1B.2.4.1.When L3 filtering is used an additional delay can be expected.

If an inter frequency FDD cell has been detectable at least for the time period T_{identify_FDD inter} and then enters the reporting range, the event triggered measurement reporting delay shall be less than T_{measurement_period FDD inter} provided the timing to that cell has not changed more than +/-32 chips during the time period T_{identify FDD inter} and the L3 filter has not been used.

8.1B.2.5 GSM measurements

The requirements in this section shall apply to UE supporting TDD and GSM.

In CELL_DCH state, measurements opportunities for GSM measurements are provided by means of idle intervals.

Measurements on GSM cells can be requested with BSIC verified or BSIC non-verified.

a) In CELL_DCH state, when signaled by UTRAN and when idle intervals are used for GSM measurements, the UE shall continuously measure GSM cells and search for new GSM cells given in the monitored set.

– In section 8.1B.2.1 the split of measurements between different modes and systems is defined. Every second measurement opportunity scheduled for GSM measurements, as given by 8.1B.2.1 shall be allocated for GSM initial BSIC identification.

– The remaining measurements opportunities scheduled for GSM measurements shall be used as follows. 3 measurement opportunities out of 4 shall be allocated for GSM carrier RSSI measurements and 1 out of 4 shall be allocated for GSM BSIC reconfirmation. The scheduling of measurement opportunities between GSM carrier RSSI measurements and GSM BSIC reconfirmation is up to the UE.

b) In CELL_DCH state, when signaled by UTRAN and when the UE does not need 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 [21] shall apply. This is further detailed in the following sub-sections.

8.1B.2.5.1 GSM carrier RSSI

a) For a UE using idle intervals to perform GSM measurements

A UE supporting GSM measurements using idle intervals shall meet the minimum number of GSM carrier RSSI measurements specified in table 8.1B.

In the CELL_DCH state the measurement period, T_{measurement period GSM}, for the GSM carrier RSSI measurement is 480 ms.

The UE shall meet the measurement accuracy requirements stated for RXLEV in [21], 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.1B

Idle interval length (timeslots)	Number of GSM carrier RSSI samples in each idle interval
3	1
4	2
5	3
6	4
7	6
8	7
9	8
10	10
11	11
12	12
13	14

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.

b) For a UE not using 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 GSM carrier RSSI measurement. The measurement period shall be 480 ms.

8.1B.2.5.2 BSIC verification

a) For a UE using 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 requirements for Initial BSIC identification can be found in section 8.1B.2.5.2.1.

2) BSIC re-confirmation: Tracking and decoding the BSIC of a GSM cell after initial BSIC identification is performed.. The requirements for Initial BSIC identification can be found in section 8.1B.2.5.2.2.

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.

If the UTRAN requests measurements on a GSM cell with BSIC verified, the UE shall behave as follows:

– The UE shall perform GSM carrier RSSI measurements according to Section 8.1B.2.5.1 and the UE shall perform measurement reporting as defined in Section 8.6.7.6 of [16].

– 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 BSIC re-confirmation according to Section 8.1B.2.5.2.2

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 the given reporting period even if the BSIC of a GSM cell has not been verified as defined in Sections 8.6.7.5 and 8.6.7.6 of [16]. Non verified BSIC shall be indicated in the measurement report.

The UE shall consider the BSIC of a GSM cell to be "verified", if it has decoded the SCH of the BCCH carrier and identified the BSIC at least one time (initial BSIC identification). From that time instant, the UE shall attempt to re-confirm the BSIC at least once every T_{re-confirm abort} seconds. Otherwise, the UE shall consider the BSIC of the GSM cell to be "non-verified".

The time requirement for initial BSIC identification, T_{identify abort}, and the BSIC re-confirmation interval T_{re-confirm abort} can be found in the sections below.

The UE shall be able to decode a BSIC for the purpose of initial BSIC identification or BSIC reconfirmation within an idle interval, when the time difference between the middle of the received GSM synchronisation burst at the UE and the middle of the idle interval is within the limits specified in Table 8.1C.

Table 8.1C

Idle Interval Length (timeslots)	Maximum time difference [s]
3	± 65
4	± 398
5	± 732
6	± 1065
7	± 1398
8	± 1732
9	± 2065
10	± 2398
11	± 2732
12	± 3065
13	± 3398

The UE shall be able to perform BSIC verification at levels down to the reference sensitivity level or reference interference levels as specified in [20].

b) For a UE not using idle intervals to perform GSM measurements

If a BSIC is decoded and matches the expected value, the UE shall consider it as "verified", otherwise it shall consider it 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 [20].

8.1B.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 the 8 strongest BCCH carriers of the GSM cells indicated in the measurement control information. The UE shall give priority for BSIC decodingattempts 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 inmediately 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 T_{identify abort}, the UE shall abort the BSIC decoding attempts for that GSMBCCH carrier. The UE shall continue to try to perform BSIC decoding of the next GSM BCCH carrier in signal strength order. The GSM BCCH carrier for which the BSIC decoding failed shall not be re-considered for BSIC decoding 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.

Where T_{identify abort} = 5000 ms.

8.1B.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 decoding. The timing information shall be updated every time the BSIC is decoded.

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 T_{re-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.1B.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.

Where T_{re-confirm abort} =5000 ms.

8.1B.2.5.3 Periodic Reporting

Reported measurements in periodically triggered measurement reports shall meet the requirements in section 9.

8.1B.2.5.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 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 T_{measurement period GSM} (see section 8.1B.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*T_{measurement period GSM}, where T_{measurement period GSM} is defined in Section 8.1B.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.1B.2.5.2.1 Initial BSIC identification can be expected.

8.1B.2.6 TDD Synchronisation to new cells

For the requirements in section 8 and 9 to apply, an intra-frequency or inter-frequency TDD cell shall be considered detectable when,

where the received P-CCPCH E_c/I_o is defined as

and the received SCH E_c/I_o is defined as

and SCH_Ec/Ior is equally divided between primary synchronisation code and the sum of all secondary synchronisation codes, where the secondary synchronisation codes are also equally divided.

8.1B.2.7 E-UTRAN FDD measurements

The requirements in this section apply only to UEs supporting 7.68Mcps TDD and E-UTRAN FDD.

1) For a UE requiring idle intervals to perform E-UTRAN FDD measurements. In CELL_DCH state when signalled by UTRAN and when idle intervals are used, 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.1B.2.7.1.

8.1B.2.7.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:

T_{E-UTRAN FDD}: This is the minimum time that is available for E-UTRAN FDD measurements during the measurement period T_{Measurement_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.

T_{Basic_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.3 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_E_S/Iot. according to Annex B.2.3 for a corresponding Band

8.1B.2.7.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 T_{Measurement_Period_E-UTRAN FDD} = 480 x N_Freq ms where N_Freq 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.1B.2.7.3 Periodic reporting

Reported measurements contained in periodically triggered measurement reports shall meet the requirements in section 9.

8.1B.2.7.4 Void

8.1B.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 T_{identify E-UTRAN FDD} defined in Section 8.1B.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 T_{identify E-UTRAN FDD} and then enters or leaves the reporting range, the event triggered measurement reporting delay shall be less than T_{Measurement_Period_E-UTRAN_FDD} provided the timing to that cell has not changed more than ±50 T_S while idel interval has not been available and the L3 filter has not been used.

8.1B.2.8 E-UTRAN TDD measurements

The requirements in this section apply only to UEs supporting 7.68Mcps TDD and E-UTRAN TDD.

1) For a UE requiring idle intervals to perform E-UTRAN TDD measurements. In CELL_DCH state when signalled by UTRAN and when idle intervals are used, 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.1B.2.8.1.

8.1B.2.8.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:

T_{E-UTRAN TDD}: This is the minimum time that is available for E-UTRAN TDD measurements during the measurement period T_{Measurement_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.

T_{Basic_Identify_E-UTRAN TDD} = 480ms

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.3 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.3 for a corresponding Band

8.1B.2.8.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 T_{Measurement_Period_E-UTRAN TDD} = 480 x N_Freq ms where N_Freq 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.1B.2.8.3 Periodic reporting

Reported measurements contained in periodically triggered measurement reports shall meet the requirements in section 9.

8.1B.2.8.4 Void

8.1B.2.8.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 event triggered measurement reporting delay, measured without L3 filtering shall be less than T_{Identify E-UTRAN TDD} defined in Section 8.1B.2.8.1. When L3 filtering is used an additional delay can be expected.

If a cell has been detectable at least for the time period T_{Identify E-UTRAN TDD} and then enters or leaves the reporting range, the event triggered measurement reporting delay shall be less than T_{Measurement_Period_E-UTRAN_TDD} provided the timing to that cell has not changed more than ±50 T_S while idel interval has not been available and the L3 filter has not been used.