3G Event Description

7/22/2019 3G Event Description

1/36

p MPTIntra-frequency measurementsReporting event 1A: A Primary CPICH enters the reporting rangeReporting event 1B: A primary CPICH leaves the reporting rangeReporting event 1C: A non-active primary CPICH becomes better than an active

primary CPICH

Reporting event 1D: Change of best cellReporting event 1E: A Primary CPICH becomes better than an absolute

thresholdReporting event 1F: A Primary CPICH becomes worse than an absolute

thresholdIntra-frequency reporting events for TDDReporting event 1G: Change of best cell (TDD)Reporting event 1H: Timeslot ISCP below a certain threshold (TDD)Reporting event 1I: Timeslot ISCP above a certain threshold (TDD)Inter-frequency measurementsEvent 2a: Change of best frequency.Event 2b: The estimated quality of the currently used frequency is below a

certain threshold and the estimated quality of a non-usedfrequency is above a certain threshold

Event 2c: The estimated quality of a non-used frequency is above a certainthreshold

Event 2d: The estimated quality of the currently used frequency is below acertain threshold

Event 2e: The estimated quality of a non-used frequency is below a certainthreshold

Event 2 f: The estimated quality of the currently used frequency is above a

certain thresholdInter-RAT measurementsEvent 3a: The estimated quality of the currently used UTRAN frequency is

below a certain threshold and the estimated quality of the othersystem is above a certain threshold

Event 3b: The estimated quality of other system is below a certain thresholdEvent 3c: The estimated quality of other system is above a certain thresholdEvent 3d: Change of best cell in other systemTraffic Volume MeasurementsReporting event 4 A: Transport Channel Traffic Volume becomes larger than an

absolute threshold

Reporting event 4 B: Transport Channel Traffic Volume becomes smaller thanan absolute threshold

Quality MeasurementsReporting event 5A: A predefined number of bad CRCs is exceededUE internal measurementsReporting event 6A: The UE Tx power becomes larger than an absolute

thresholdReporting event 6B: The UE Tx power becomes less than an absolute thresholdReporting event 6C: The UE Tx power reaches its minimum valueReporting event 6D: The UE Tx power reaches its maximum valueReporting event 6E: The UE RSSI reaches the UE's dynamic receiver range

Reporting event 6F: The UE Rx-Tx time difference for a RL included in theactive set becomes larger than an absolute threshold

measurement_eventids 12.J ul.06 Seite 1/2


2/36

p MPTReporting event 6G: The UE Rx-Tx time difference for a RL included in the

active set becomes less than an absolute thresholdUE positioning measurementsReporting Event 7a: The UE position changes more than an absolute thresholdReporting Event 7b: SFN-SFN measurement changes more than an absolute

thresholdReporting Event 7c: GPS time and SFN time have drifted apart more than an

absolute threshold

measurement_eventids 12.J ul.06 Seite 2/2


3/36

Reporting event 1A: A Primary CPICH enters the reporting range

When an intra-frequency measurement configuring event 1a is set up, the UE shall:

1> create a variable TRIGGERED_1A_EVENT related to that measurement, which shall initiallybe empty;

1> delete this variable when the measurement is released.

When event 1A is configured in the UE, the UE shall:

1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or moreprimary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", andEquation 2 below is fulfilled for one or more primary CPICHs, for each of these primary

CPICHs:

2> if all required reporting quantities are available for that cell; and

2> if the equations have been fulfilled for a time period indicated by "Time to trigger", and if

that primary CPICH is part of cells allowed to trigger the event according to "Triggeringcondition 2", and if that primary CPICH is not included in the "cells triggered" in the

variable TRIGGERED_1A_EVENT:

3> include that primary CPICH in the "cells recently triggered" in the variableTRIGGERED_1A_EVENT.

1> if the value of "Reporting deactivations threshold" for this event is greater than or equal to thecurrent number of cells in the active set or equal to 0 and any primary CPICHs are stored in the

"cells recently triggered" in the variable TRIGGERED_1A_EVENT:

2> if "Reporting interval" for this event is not equal to 0:

3> if the IE "Periodical reporting running" in the variable TRIGGERED_1A_EVENT is set

to FALSE:

4> start a timer with the value of "Reporting interval" for this event and set the IE"Periodical reporting running" in the variable TRIGGERED_1A_EVENT to TRUE;

3> set "sent reports" for the primary CPICHs in "cells recently triggered" in the variableTRIGGERED_1A_EVENT to 1.

2> send a measurement report with IEs set as below:

3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to

"1a"; and

3> include in "cell measurement event results" all entries of the "cells recently triggered" inthe variable TRIGGERED_1A_EVENT in descending order according to the configured

measurement quantity taking into account the cell individual offset for each of thosecells;

3> set the IE "measured results" and the IE "additional measured results" according to

subclause 8.4.2, not taking into account the cell individual offset for each cell.

2> move all entries from "cells recently triggered" to "cells triggered" in the variable

TRIGGERED_1A_EVENT.

1> if the timer for the periodical reporting has expired:

2> if any primary CPICH is included in the "cells triggered" in the variable

TRIGGERED_1A_EVENT:


4/36

3> if "Reporting interval" for this event is not equal to 0, and if "Amount of reporting" isgreater than "sent reports" stored for any of these primary CPICHs, in "cells triggered" in

the variable TRIGGERED_1A_EVENT:

4> increment the stored counter "sent reports" for all CPICHs in "cell triggered" in

variable TRIGGERED_1A_EVENT;

4> start a timer with the value of "Reporting interval" for this event;


5> set in "intra-frequency measurement event results": "Intrafrequency event

identity" to "1a"; and

5> include in "cell measurement event results" all entries of the variableTRIGGERED_1A_EVENT with value of IE "sent reports" smaller than value of

"Amount of reporting" in descending order according to the configuredmeasurement quantity taking into account the cell individual offset for each of

those cells;

5> set the IE "measured results" and the IE "additional measured results" accordingto subclause 8.4.2, not taking into account the cell individual offset for each cell.

4> if "sent reports" in variable TRIGGERED_1A_EVENT is greater than "Amount ofreporting" for all entries:

5> set the IE "Periodical Reporting running" in the variable

TRIGGERED_1A_EVENT to FALSE and disable the timer for the periodicalreporting.

1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH,or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below is

fulfilled for a primary CPICH; or

1> if a primary CPICH is no longer part of the cells allowed to trigger the event according to the"Triggering condition 2":

2> if that primary CPICH is included in the "cells triggered" or "cells recently triggered" in the

variable TRIGGERED_1A_EVENT:

3> remove the entry of that primary CPICH from "cells triggered" or "cells recentlytriggered" in the variable TRIGGERED_1A_EVENT.

3> if no entry in the variable TRIGGERED_1A_EVENT has a value of "sent reports"smaller than "Amount of reporting":

4> stop the reporting interval timer;

4> set the IE "Periodical reporting running" in the variable TRIGGERED_1A_EVENT

to FALSE.

This event is only applicable to the CELL_DCH state. When the measurement is setup in CELL_DCH

or upon transition to CELL_DCH the UE shall:

1> if the "Triggering condition 2" includes active set cells:

2> include the primary CPICH of all cells in the current active set into the "cells triggered" inthe variable TRIGGERED_1A_EVENT with the counter "sent reports" set to "Amount ofreporting".


5/36

Reporting event 1B: A primary CPICH leaves the reporting range

When an intra-frequency measurement configuring event 1b is set up, the UE shall:

1> create a variable TRIGGERED_1B_EVENT related to that measurement, which shall initially

be empty;


When event 1B is configures in the UE, the UE shall:

1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or more

primary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", andEquation 2 below is fulfilled for one or more primary CPICHs, for each of these primaryCPICHs:

2> if all required reporting quantities are available for that cell, and if the equations have beenfulfilled for a time period indicated by "Time to trigger", and if that primary CPICH is part

of cells allowed to trigger the event according to "Triggering condition 1", and if thatprimary CPICH is not included in the "cells triggered" in the variableTRIGGERED_1B_EVENT:

3> include that primary CPICH in the "cells recently triggered" in the variableTRIGGERED_1B_EVENT.

1> if any primary CPICHs are stored in the "cells recently triggered" in the variableTRIGGERED_1B_EVENT:

2> if "Periodic reporting info-1b" is present, and "Reporting interval" for this event is not equalto 0:

3> if the IE "Periodical reporting running" in the variable TRIGGERED_1B_EVENT is set

to FALSE:

4> start a timer with the value of "Reporting interval" for this event and set the IE"Periodical reporting running" in the variable TRIGGERED_1B_EVENT to TRUE;

3> set "sent reports" for the primary CPICHs in "cells recently triggered" in the variable

TRIGGERED_1B_EVENT to 1.



"1b"; and

3> include in "cell measurem3> include in "cell measurement event results" all entries of

"cells recently triggered" in the variable TRIGGERED_1B_EVENT in ascending orderaccording to the configured measurement quantity taking into account the cell individual

offset for each of those cells;

3> set the IE "measured results" and the IE "additional measured results" according tosubclause 8.4.2, not taking into account the cell individual offset for each cell.

2> move all entries from IE "cells recently triggered" to "cells triggered" in the variable

TRIGGERED_1B_EVENT.


2> if any primary CPICH is included in the "cells triggered" in the variable

TRIGGERED_1B_EVENT:

3> if "Periodic reporting info-1b" is present:


6/36

4> if "Reporting interval" is not equal to 0, and if "Amount of reporting" is greater than"sent reports" stored for any of these primary CPICHs, in "cells triggered" in the

variable TRIGGERED_1B_EVENT:

5> increment the stored counter "sent reports" for all CPICHs in "cell triggered" in

variable TRIGGERED_1B_EVENT;

5> start a timer with the value of "Reporting interval-1b" for this event;


6> set in "intra-frequency measurement event results": "Intrafrequency event

identity" to "1b"; and

6> include in "cell measurement event results" all entries of the variableTRIGGERED_1B_EVENT with value of IE "sent reports" smaller than value

of "Amount of reporting" in ascending order according to the configuredmeasurement quantity taking into account the cell individual offset for each of

those cells;

6> set the IE "measured results" and the IE "additional measured results"according to subclause 8.4.2, not taking into account the cell individual offset

for each cell.

5> if "sent reports" in variable TRIGGERED_1B_EVENT is greater than "Amount

of reporting" for all entries:

6> set the IE "Periodical Reporting running" in the variableTRIGGERED_1B_EVENT to FALSE and disable the timer for the periodical

reporting.

1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH,

or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below isfulfilled for a primary CPICH; or

1> if a primary CPICH is no longer part of the cells allowed to trigger the event according to the

"Triggering condition 1":

2> if that primary CPICH is included in the "cells triggered" in the variableTRIGGERED_1B_EVENT:

3> remove the entry of that primary CPICH from "cells triggered" in the variableTRIGGERED_1B_EVENT.

Reporting event 1C: A non-active primary CPICH becomes better thanan active primary CPICH

When an intra-frequency measurement configuring event 1c is set up, the UE shall:

1> create a variable TRIGGERED_1C_EVENT related to that measurement, which shall initially

be empty;


When event 1C is configured in the UE, the UE shall:

1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or more

primary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", andEquation 2 below is fulfilled for one or more primary CPICHs, for each of these primary

CPICHs:

2> if all required reporting quantities are available for that cell; and


7/36

2> if the equations have been fulfilled for a time period indicated by "Time to trigger", and ifthe primary CPICH that is better is not included in the active set but the other primary

CPICH is any of the primary CPICHs included in the active set, and if that first primaryCPICH is not included in the "cells triggered" in the variable TRIGGERED_1C_EVENT:

3> include that primary CPICH in the "cells recently triggered" in the variableTRIGGERED_1C_EVENT.

1> if the value of "Replacement activation threshold" for this event is less than or equal to thecurrent number of cells in the active set or equal to 0 and if any primary CPICHs are stored inthe "cells recently triggered" in the variable TRIGGERED_1C_EVENT:

2> if "Reporting interval" for this event is not equal to 0:

3> if the IE "Periodical reporting running" in the variable TRIGGERED_1C_EVENT is setto FALSE:

4> start a timer for with the value of "Reporting interval" for this event and set the IE

"Periodical reporting running" in the variable TRIGGERED_1C_EVENT to TRUE.

3> set "sent reports" for that primary CPICH in the variable TRIGGERED_1C_EVENT to1.


3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to"1c"; and

3> include in "cell measurement event results" all entries of the "cells recently triggered" in

the variable TRIGGERED_1C_EVENT not in the active set as well as the "primaryCPICH info" of all the primary CPICHs in the active set for which the measured value isworse (i.e. greater for pathloss and less for the other measurement quantities) than the

one of the entry in "cell recently triggered" that has the best measured value taking intoaccount their cell individual offset. The "primary CPICH info" for those cells shall beordered according to their measured value taking into account their cell individual offset,

beginning with the best cell to the worst one;



2> move all entries from "cells recently triggered" to "cells triggered" in the variable

TRIGGERED_1C_EVENT.


2> if any primary CPICH is included in the "cells triggered" in the variableTRIGGERED_1C_EVENT, and not included in the current active set:

3> if "Reporting interval" for this event is not equal to 0, and if "Amount of reporting" is

greater than "sent reports" stored for that primary CPICH, in "cells triggered" in thevariable TRIGGERED_1C_EVENT:

4> increment the stored counter "sent reports" for all CPICH in "cell triggered" invariable TRIGGERED_1C_EVENT;

4> start a timer with the value of "Reporting interval" for this event;


5> set in "intra-frequency measurement event results": "Intrafrequency eventidentity" to "1c"; and


8/36

5> include in "cell measurement event results" all entries of the variableTRIGGERED_1C_EVENT with value of IE "sent report" smaller than value of

"Amount of reporting" and that are not part of the active set as well as the"primary CPICH info" of all the primary CPICHs in the active set for which the

measured value is worse (i.e. greater for pathloss and less for the other

measurement quantities) than the one of the entry in "cell recently triggered" thathas the best measured value, ordering the "primary CPICH info" according totheir measured value beginning with the best cell to the worst one, taking intoaccount the cell individual offset for each cell;

5> set the IE "measured results" and the IE "additional measured results" according

to subclause 8.4.2, not taking into account the cell individual offset for each cell.

4> if "sent reports" in variable TRIGGERED_1C_EVENT is greater than "Amount ofreporting" for all entries:

5> set the IE "Periodical Reporting running" in the variableTRIGGERED_1C_EVENT to FALSE and disable the timer for the periodical

reporting.

1> if "Measurement quantity" is "pathloss" and Equation 3 below is fulfilled for a primary CPICH,

or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 4 below isfulfilled for a primary CPICH or;

1> if a primary CPICH is added to the active set:

2> if that primary CPICH is included in the "cells triggered" or "cells recently triggered" in the

variable TRIGGERED_1C_EVENT:

3> remove the entry of that primary CPICH from "cells triggered" or "cells recentlytriggered" in the variable TRIGGERED_1C_EVENT.

3> if no entry in the variable TRIGGERED_1C_EVENT has a value of "sent reports"

smaller than "Amount of reporting":

4> stop the reporting interval timer;

4> set the IE "Periodical reporting running" in the variable TRIGGERED_1C_EVENT

to FALSE.

Reportingevent 1C

Reportingevent 1C

Measurement

quantity

Time

P CPICH 2

P CPICH 1

P CPICH 3

P CPICH 4

Figure 14.1.2.3-1 [Informative]: A primary CPICH that is not included in the active setbecomes better than a primary CPICH that is in the active set

In this figure, the parameters hysteresis and time to trigger, as well as the cell individual offsets for all

cells are equal to 0. In this example the cells belonging to primary CPICH 1 and 2 are in the active set,but the cells transmitting primary CPICH 3 and CPICH 4 are not (yet) in the active set.


9/36

The first measurement report is sent when primary CPICH 4 becomes better than primary CPICH 2.The "cell measurement event result" of the measurement report contains the information of primary

CPICH 4 and CPICH 2.

Assuming that the active set has been updated after the first measurement report (active set is now

primary CPICH 1 and primary CPICH 4), the second report is sent when primary CPICH 3 becomesbetter than primary CPICH 1. The "cell measurement event result" of the second measurement report

contains the information of primary CPICH 3 and primary CPICH 1.

Reporting event 1D: Change of best cell

When an intra-frequency measurement configuring event 1d is set up, the UE shall:

1> create a variable TRIGGERED_1D_EVENT related to that measurement, which shall initially

contain the best cell in the active set when the measurement is initiated;


1> As soon as the best cell in the active set has been evaluated by the UE (and stored in theTRIGGERED_1D_EVENT variable) and provided that there is more than one cell in the activeset, trigger an immediate measurement report with IEs set as below:

2> set in "intra-frequency measurement event results"; "Intrafrequency event identity" to "1d"and "cell measurement event results" to the CPICH info of the primary CPICH stored in theTRIGGERED_1D_EVENT variable;

2> set the IE "measured results" and the IE "additional measured results" according to subclause

8.4.2

When event 1D is configured in the UE, the UE shall:

1> if IE "useCIO" is present and its value is TRUE, take into account the Cell Individual Offset for

evaluation of the Equation 1 and 2, otherwise do not take it into account.

1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for a primary CPICHthat is not stored in "Best cell" in variable BEST_CELL_1D_EVENT, or if "Measurement

quantity" is "CPICH Ec/N0" or "CPICH RSCP", and Equation 2 below is fulfilled for a primaryCPICH that is not stored in "Best cell" in variable BEST_CELL_1D_EVENT:

NOTE: If the equations are simultaneously fulfilled for more than one primary CPICH, the UEshould report only one event 1D, triggered by the best primary CPICH.

2> if all required reporting quantities are available for that cell, and if the equations have beenfulfilled for a time period indicated by "Time to trigger" and if IE "Triggering condition 2" isabsent or if it is present and that primary CPICH is part of cells allowed to trigger the event

according to "Triggering condition 2":

3> set "best cell" in the variable BEST_CELL_1D_EVENT to that primary CPICH that

triggered the event;


4> set in "intra-frequency measurement event results"; "Intrafrequency event identity" to

"1d" and "cell measurement event results" to the CPICH info of the primary CPICHthat triggered the report.

4> set the IE "measured results" and the IE "additional measured results" according tosubclause 8.4.2.

This event is only applicable to the CELL_DCH state. Upon transition to CELL_DCH the UE shall:

1> set "best cell" in the variable BEST_CELL_1D_EVENT to the best cell of the primary CPICHsincluded in the active set.


10/36

Reporting

event 1D

Measurement

quantity

Time

P CPICH 2

P CPICH 1

P CPICH3

Figure 14.1.2.4-1 [Informative]: A primary CPICH becomes better than the previouslybest primary CPICH


cells are equal to 0.

Reporting event 1E: A Primary CPICH becomes better than an absolutethreshold

When an intra-frequency measurement configuring event 1e is set up, the UE shall:

1> create a variable TRIGGERED_1E_EVENT related to that measurement, which shall initiallybe empty;


When event 1E is configured in the UE, the UE shall:


fulfilled for one or more primary CPICHs, for each of these primary CPICHs:


of cells allowed to trigger the event according to "Triggering condition 2", and that primary

CPICH is not included in the "cells triggered" in the variable TRIGGERED_1E_EVENT:

3> include that primary CPICH in the "cells recently triggered" in the variableTRIGGERED_1E_EVENT.

1> if any primary CPICHs are stored in the "cells recently triggered" in the variable

TRIGGERED_1E_EVENT:



"1e"; and

3> include in "cell measurement event results" all entries of the "cells recently triggered" inthe variable TRIGGERED_1E_EVENT in descending order according to the configured

measurement quantity taking into account the cell individual offset for each of thosecells;




11/36

2> move all entries from "cells recently triggered" to "cells triggered" in the variableTRIGGERED_1E_EVENT.




2> if that primary CPICH is included in the "cells triggered" in the variable

TRIGGERED_1E_EVENT:

3> remove that primary CPICH and sent reports from "cells triggered" in the variable

TRIGGERED_1E_EVENT.

This event is only applicable to the CELL_DCH state. When the measurement is setup in CELL_DCHor upon transition to CELL_DCH the UE shall:

1> if the "Triggering condition 2" includes active set cells:

2> include the primary CPICH of all cells in the current active set that fulfil the equations 1 or 2

according to the "Measurement quantity" of event 1e into the "cells triggered" in the variableTRIGGERED_1E_EVENT.

Absolute

threshold

Reporting

event 1E

Measurement

quantity

Time

P CPICH 1

P CPICH 2

P CPICH 3

Figure 14.1.2.5-1 [Informative]: Event-triggered report when a Primary CPICH becomesbetter than an absolute threshold


cells are equal to 0.

Reporting event 1F: A Primary CPICH becomes worse than an absolutethreshold

When an intra-frequency measurement configuring event 1F is set up, the UE shall:

1> create a variable TRIGGERED_1F_EVENT related to that measurement, which shall initially

be empty;


When event 1F is configured in the UE, the UE shall:

1> if "Measurement quantity" is "pathloss" and Equation 1 below is fulfilled for one or moreprimary CPICHs, or if "Measurement quantity" is "CPICH Ec/N0" or "CPICH RSCP", and


12/36

Equation 2 below is fulfilled for one or more primary CPICHs, for each of these primaryCPICHs:


of cells allowed to trigger the event according to "Triggering condition 1", and that primaryCPICH is not included in the "cells triggered" in the variable TRIGGERED_1F_EVENT:

3> include that primary CPICH in the "cells recently triggered" in the variableTRIGGERED_1F_EVENT.

1> if any primary CPICHs are stored in the "cells recently triggered" in the variableTRIGGERED_1F_EVENT:


3> set in "intra-frequency event measurement results": "Intrafrequency event identity" to"1f"; and

3> include in "cell measurement event results" all entries of the "cells recently triggered" in

the variable TRIGGERED_1F_EVENT in descending order according to the configuredmeasurement quantity taking into account the cell individual offset for each of those

cells;


subclause 8.4.2, not taking into account the cell individual offset for each cell;

2> move all entries from "cells recently triggered" to "cells triggered" in the variableTRIGGERED_1F_EVENT.




2> if that primary CPICH is included in the "cells triggered" in the variable

TRIGGERED_1F_EVENT:

3> remove that primary CPICH from "cells triggered" in the variableTRIGGERED_1F_EVENT.

Absolute

threshold

Reporting

event 1F

Measurement

quantity

Time

P CPICH 1

P CPICH 2

P CPICH 3

Figure 14.1.2.6-1 [Informative]: Event-triggered report when a Primary CPICH becomesworse than an absolute threshold


13/36

In this figure, the parameters hysteresis and time to trigger, as well as the cell individual offsets for allcells are equal to 0.

Intra-frequency reporting events for TDD

Reporting event 1G: Change of best cell (TDD)

When event 1G is configured in the UE, the UE shall:

1> if the equation 1 is fulfilled for a P-CCPCHs during the time "Time to trigger" and if that P-CCPCH is not included in the "primary CCPCH info" in the variableTRIGGERED_1G_EVENT:

2> include that P-CCPCH in "cells triggered" in the variable TRIGGERED_1G_EVENT;


3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to"1g";

3> set the first entry in "cell measurement event results" to the "Cell parameters ID" of the

P-CCPCH which was stored in the variable TRIGGERED_1G_EVENT;

3> include all entries in "cells triggered" in variable TRIGGERED_1G_EVENT in "cell

measurement event results" in the measurement report in descending order according to:

OLogM+10

whereMis the P-CCPCH RSCP and Othe individual offset of a cell;



1> if Equation 2 below is fulfilled for a primary CCPCH:

2> if a primary CCPCH is included in the "cells triggered" in the variable

TRIGGERED_1G_EVENT:

3> remove the entry of that primary CCPCH from "cells triggered" in the variableTRIGGERED_1G_EVENT;

The UE shall use the equations below for evaluation of reporting event 1g:

Reporting

Event 1G

Measurement

quantity

Time

P-CCPCH RSCP 2

P-CCPCH RSCP 1

Figure 14.1.3.1-1: A P-CCPCH RSCP becomes better than the previous best P-CCPCHRSCP


14/36

Reporting event 1H: Timeslot ISCP below a certain threshold (TDD)

When event 1h is configured in the UE, the UE shall:

1> if equation 1 is fulfilled for a time period indicated by "Time to trigger" and if that P-CCPCH is

not included in the IE "cells triggered" in the variable TRIGGERED_1H_EVENT:

2> include that P-CCPCH in the IE "cells triggered" in the variable TRIGGERED_1H_EVENT;

2> send a measurement report with the IEs set as below:


"1h" and in "cell measurement event results" the "Cell parameters ID" of the P-CCPCHthat triggered the report;

3> include in "Cell measured results" the "Timeslot ISCP" of those cells that are included in

the variable TRIGGERED_1H_EVENT.


TRIGGERED_1H_EVENT:


3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to"1h" and "cell measurement event results" to the "Cell parameters ID" of the P-CCPCH

that triggered the report;

3> set in "measured results " the "Timeslot ISCP" of those cells that are included in thevariable TRIGGERED_1H_EVENT and "additional measured results" according to




TRIGGERED_1H_EVENT:

3> remove the entry of that primary CCPCH from "cells triggered" in the variable

TRIGGERED_1H_EVENT.

Timeslot ISCP

ReportingEvent 1H

Time

TS 1

ISCP

Threshold

Figure 14.1.3.2-1: An ISCP value of a timeslot drops below an absolute threshold

Reporting event 1I: Timeslot ISCP above a certain threshold (TDD)

When event 1i is configured in the UE, the UE shall:


15/36

1> if equation 1 is fulfilled for a time period indicated by "Time to trigger" and if that P-CCPCH isnot included in the IE "cells triggered" in the variable TRIGGERED_1I_EVENT:

2> include that P-CCPCH in the IE "cells triggered" in the variable TRIGGERED_1I_EVENT;

2> send a measurement report with the IEs set as below:

3> set in "intra-frequency measurement event results": "Intrafrequency event identity" to"1i" and in "cell measurement event results" to the "Cell parameters ID" of the P-CCPCH

that triggered the report;

3> include in "measured results" the "Timeslot ISCP" of those cells that are included in the

variable TRIGGERED_1I_EVENT and "additional measured results" according to 8.4.2,not taking into account the cell individual offset for each cell.


TRIGGERED_1I_EVENT:



TRIGGERED_1I_EVENT:

4> remove the entry of that primary CCPCH from "cells triggered" in the variableTRIGGERED_1I_EVENT.

Timeslot ISCP

Reporting

Event 1ITime

TS 1

ISCPThreshold

Figure 14.1.3.3-1: An ISCP value of a timeslot exceeds a certain threshold


16/36

Event-triggered periodic intra-frequency measurement reports(informative)

Cell addition failure (FDD only)

Event-triggered

reportPCPICH 3

PCPICH 1

PCPICH 2

Periodic

report

Periodic

report

Reporting

range

Reporting

terminated

Figure 14.1.4.1-1: Periodic reporting triggered by event 1A

When a cell enters the reporting range and triggers event 1A, the UE shall transmit aMEASUREMENT REPORT to the UTRAN and typically this may result in an update of the active set.

However, in some situations the UTRAN may be unable to add a strong cell to the active set typicallydue to capacity shortage for example.

The UE shall continue reporting after the initial report by reverting to periodical measurement

reporting if the reported cell is not added to the active set. This is illustrated in Figure 14.1.4.1-1.During periodic reporting the UE shall transmit MEASUREMENT REPORT messages to the UTRANat predefined intervals. The reports shall include reporting information of the cells in the current active

set and of the monitored cell(s) in the reporting range.

Event-triggered periodic measurement reporting shall be terminated if:

1> there are no longer any monitored cell(s) within the reporting range; or

1> the UTRAN has added cells to the active set so that it includes the maximum number of cells(defined by the reporting deactivation thresholdparameter), which are allowed for event 1A

to be triggered; or

1> the UE has sent the maximum number of MEASUREMENT REPORT messages (defined by the

amount of reportingparameter).

The reporting period is assigned by the UTRAN (with the Reporting intervalparameter). If thereporting interval is set to zero event-triggered periodic measurement reporting shall not be applied.

Deleted:


17/36

14.1.4.1a Cell removal failure (FDD only)

Figure 14.1.4.1a: Periodic reporting triggered by event 1B

When a cell enters the removal range and triggers event 1B, the UE shall transmit a MEASUREMENT

REPORT to the UTRAN and typically this may result in the removal of the weakest active cell. If theUTRAN is unable to receive MEASUREMENT REPORT after the maximum retransmission, it is

beneficial to receive continuous reports in this case as well.

The UE shall revert to periodical measurement reporting if the UTRAN does not update the active setafter the transmission of the measurement report. This is illustrated in Figure 14.1.4.1a. During periodicreporting the UE shall transmit MEASUREMENT REPORT messages to the UTRAN at predefined

intervals.


1> there are no longer any monitored cell(s) within the removal range; or

1> the UTRAN has removed cells from the active set so that there are no longer the minimum

amount of active cells for event 1B to be triggered; or

1> the UE has sent the maximum number of MEASUREMENT REPORT messages (defined by the"amount of reporting"parameter).

The reporting period is assigned by the UTRAN (with the "Reporting interval" parameter). If the

reporting interval is set to zero, event-triggered periodic measurement reporting shall not be applied.


18/36

14.1.4.2 Cell replacement failure (FDD only)

PCPICH 1

Event-triggered

report

Periodic

report

PCPICH 4

PCPICH 2

Periodic

report

Reporting

terminated

PCPICH 3

Figure 14.1.4.1-2: Periodic reporting triggered by event 1C

When a cell enters the replacement range and triggers event 1C, the UE shall transmit aMEASUREMENT REPORT to the UTRAN and typically this may result in the replacement of the

weakest active cell. If the UTRAN is unable to replace the cell due to for example capacity shortage, itis beneficial to receive continuous reports in this case as well.

The UE shall revert to periodical measurement reporting if the UTRAN does not update the active setafter the transmission of the measurement report. This is illustrated in Figure 14.1.4.1-2. During

periodic reporting the UE shall transmit MEASUREMENT REPORT messages to the UTRAN at

predefined intervals. The reports shall include reporting information of the cells in the current active setand of the monitored cell(s) in the replacement range.


1> there are no longer any monitored cell(s) within the replacement range; or

1> the UTRAN has removed cells from the active set so that there are no longer the minimum

amount of active cells for event 1C to be triggered (as defined by the replacement activationthreshold parameter); or

1> the UE has sent the maximum number of MEASUREMENT REPORT messages (defined by the

amount of reportingparameter).

The reporting period is assigned by the UTRAN (with the Reporting intervalparameter). If thereporting interval is set to zero, event-triggered periodic measurement reporting shall not be applied.

14.1.5 Mechanisms available for modifying intra-frequencymeasurement reporting behaviour (informative)

14.1.5.1 Hysteresis

To limit the amount of event-triggered reports, a hysteresis parameter may be connected with eachreporting event given above. The value of the hysteresis is given to the UE in the Reporting criteria

field of the Measurement Control message.

In the example in Figure 14.1.5.1-1, the hysteresis ensures that the event 1D (FDD) or IG(TDD)(primary CPICH(FDD)/CCPCH(TDD) 2 becomes the best cell) is not reported until the difference is

equal to the hysteresis value. The fact that primary CPICH(FDD)/CCPCH(TDD) 1 becomes bestafterwards is not reported at all in the example since the primary CPICH(FDD)/CCPCH(TDD) 1 doesnot become sufficiently better than the primary CPICH(FDD)/CCPCH(TDD) 2.


19/36

Hysteresis

Reporting

event 1D

Hysteresis

Measurement

quantity

Time

P CCPCH 1

P CCPCH 2

Figure 14.1.5.1-1: Hysteresis limits the amount of measurement reports

Time-to-trigger

To limit the measurement signalling load, a time-to-trigger parameter could be connected with eachreporting event given above. The value of the time-to-trigger is given to the UE in the Reporting

criteria field of the Measurement Control message.

The effect of the time-to-trigger is that the report is triggered only after the conditions for the event

have existed for the specified time-to-trigger. In the following FDD example in Figure 14.1.5.2-1, theuse of time-to-trigger means that the event (primary CPICH 3 enters the reporting range) is not

reported until is has been within the range for the time given by the time-to-trigger parameter.

Reporting

event 1A

Measurement

quantity

Time

Time-to-trigger

P CPICH 1Reporting

range

P CPICH 2

P CPICH 3

Figure 14.1.5.2-1: Time-to-trigger limits the amount of measurement reports

In the following TDD example in Figure 14.1.5.2-2, the use of time-to-trigger means that the event

(Timeslot ISCP upon certain threshold) is not reported until it has been upon the threshold for the timegiven by the time-to trigger parameter.

Deleted:


20/36

Time-to-trigger

Timeslot ISCP

Reporting

Event 1JTime

TS 1

ISCP

Threshold

Figure 14.1.5.2-2: Time-to-trigger limits the amount of measurement reports

NOTE: The time-to-trigger could be combined with hysteresis, i.e. a hysteresis value is added tothe measurement quantity before evaluating if the time-to-trigger timer should be started.

Inter-frequency reporting eventsWithin the measurement reporting criteria field in the MEASUREMENT CONTROL messageUTRAN notifies the UE which events should trigger the UE to send a MEASUREMENT REPORTmessage. The listed events are the toolbox from which the UTRAN can choose the reporting events

that are needed for the implemented handover evaluation function, or other radio network functions.

All events are evaluated with respect to one of the measurement quantities given in subclause 14.2.0a.The measurement quantities are measured on the monitored primary common pilot channels (CPICH)

in FDD mode and the monitored primary common control channels (PCCPCH) in TDD mode of thecell defined in the measurement object. A "non-used frequency" is a frequency that the UE has beenordered to measure upon but is not used for the connection. A "used frequency" is a frequency that the

UE has been ordered to measure upon and is also currently used for the connection.

The "monitored set on non-used frequency" consists of cells in "cells for measurement" (or all cells inCELL_INFO_LIST if "cells for measurement" is not present) that are not part of the virtual active set

on that non-used frequency.

When one inter-frequency measurement identity corresponds to multiple intra-frequency or inter-frequency events with identical event identities, the UE behaviour is not specified.

Event 2a: Change of best frequency.

When event 2a is configured in the UE within a measurement, the UE shall:

1> when the measurement is initiated or resumed:

2> store the used frequency in the variable BEST_FREQUENCY_2A_EVENT.

1> if equation 1 below has been fulfilled for a time period indicated by "Time to trigger" for a

frequency included for that event and which is not stored in the variableBEST_FREQUENCY_2A_EVENT:


3> set in "inter-frequency measurement event results":

4> "inter-frequency event identity" to "2a"; and

4> "Frequency info" to the frequency that triggered the event; and


21/36

4> "Non frequency related measurement event results" to the "Primary CPICH info" ofthe best primary CPICH for FDD cells or "Primary CCPCH info" to the "Cells

parameters ID" of the best primary CCPCH for TDD cells on that frequency, nottaking into account the cell individual offset.

3> if a non-used frequency triggered the measurement report:

4> include in IE " Inter-frequency measured results list" the measured results for the non-used frequency that triggered the event, not taking into account the cell individualoffset.

3> if the used frequency triggered the measurement report:

4> do not include the IE "Inter-frequency measured results list" in the measurement

report.

3> set the IE "additional measured results" according to subclause 8.4.2, not taking intoaccount the cell individual offset;

2> update the variable BEST_FREQUENCY_2A_EVENT with that frequency.

Event 2b: The estimated quality of the currently used frequency is below

a certain threshold and the estimated quality of a non-usedfrequency is above a certain threshold.

When an inter-frequency measurement configuring event 2b is set up, the UE shall:

1> create a variable TRIGGERED_2B_EVENT related to that measurement, which shall initially

be empty;


When event 2b is configured in the UE within a measurement, the UE shall:

1> if equations 1 and 2 below have been fulfilled for a time period indicated by "Time to Trigger"

from the same instant, respectively for one or several non-used frequencies included for thatevent and for the used frequency:

2> if any of those non-used frequency is not stored in the variable TRIGGERED_2B_EVENT:

3> store the non-used frequencies that triggered the event and that were not previouslystored in the variable TRIGGERED_2B_EVENT into that variable;



5> "inter-frequency event identity" to "2b"; and

5> for each non-used frequency that triggered the event, beginning with the best

frequency:

6> "Frequency info" to that non-used frequency; and

6> "Non frequency related measurement event results" to the "Primary CPICH

info" of the best primary CPICH for FDD cells or "Primary CCPCH info" tothe "Cell parameters ID" of the best primary CCPCH for TDD cells on that

non-used frequency, not taking into account the cell individual offset.

4> include in IE "Inter-frequency measured results list" the measured results for each

non-used frequency that triggered the event, not taking into account the cellindividual offset;


22/36

4> set the IE "additional measured results" according to subclause 8.4.2, not taking intoaccount the cell individual offset.

1> if equation 3 below is fulfilled for a non-used frequency stored in the variableTRIGGERED_2B_EVENT:

2> remove that non-used frequency from the variable TRIGGERED_2B_EVENT.

1> if equation 4 below is fulfilled for the used frequency:

2> clear the variable TRIGGERED_2B_EVENT.

Event 2c: The estimated quality of a non-used frequency is above acertain threshold

When an inter-frequency measurement configuring event 2c is set up, the UE shall:

1> create a variable TRIGGERED_2C_EVENT related to that measurement, which shall initiallybe empty;


When event 2c is configured in the UE within a measurement, the UE shall:

1> if equation 1 below has been fulfilled for one or several non-used frequencies included for thatevent during the time "Time to trigger":

2> if any of those non-used frequencies is not stored in the variable TRIGGERED_2C_EVENT:

3> store the non-used frequencies that triggered the event and that were not previously

stored in the variable TRIGGERED_2C_EVENT into that variable;



5> "inter-frequency event identity" to "2c"; and

5> for each non-used frequency that triggered the event, beginning with the best

frequency:





4> include in IE "Inter-frequency measured results list" the measured results for eachnon-used frequency that triggered the event, not taking into account the cellindividual offset;

4> set the IE "additional measured results" according to subclause 8.4.2 not taking into

account the cell individual offset.

1> if equation 2 below is fulfilled for a non-used frequency stored in the variable

TRIGGERED_2C_EVENT:

2> remove that non-used frequency from the variable TRIGGERED_2C_EVENT.


23/36

Event 2d: The estimated quality of the currently used frequency is belowa certain threshold

A UE shall be able to perform this measurement and the corresponding event reporting withoutrequiring compressed mode.

When an inter-frequency measurement configuring event 2d is set up, the UE shall:

1> create a variable TRIGGERED_2D_EVENT related to that measurement, which shall initiallybe set to FALSE;


When event 2d is configured in the UE within a measurement, the UE shall:

1> if equation 1 below has been fulfilled for the used frequency during the time "Time to trigger":

2> if the variable TRIGGERED_2D_EVENT is set to FALSE:

3> set the variable TRIGGERED_2D_EVENT to TRUE;


4> set in "inter-frequency event results": "inter-frequency event identity" to "2d" and no

IE "Inter-frequency cells", not taking into account the cell individual offset;

4> include in IE "Inter-frequency measured results list" the measured results for the usedfrequency, not taking into account the cell individual offset;

4> set the IE "additional measured results" according to subclause 8.4.2, not taking into

account the cell individual offset.

1> if the variable TRIGGERED_2D_EVENT is set to TRUE and if equation 2 is fulfilled for theused frequency:

2> set the variable TRIGGERED_2D_EVENT to FALSE.

Event 2e: The estimated quality of a non-used frequency is below acertain threshold

When an inter-frequency measurement configuring event 2e is set up, the UE shall:

1> create a variable TRIGGERED_2E_EVENT related to that measurement, which shall initiallybe empty;


When event 2e is configured in the UE within a measurement, the UE shall:

1> if equation 1 below has been fulfilled for one or several non-used frequencies included for thatevent during the time "Time to trigger":

2> if any of those non-used frequencies is not stored in the variable TRIGGERED_2E_EVENT:

3> store the non-used frequencies that triggered the event and that were not previouslystored in the variable TRIGGERED_2E_EVENT into that variable;



5> "inter-frequency event identity" to "2e"; and

5> for each non-used frequency that triggered the event, beginning with the bestfrequency:


24/36





4> include in the IE "Inter-frequency measured results list" the measuredresults for each non-used frequency that triggered the event, not taking intoaccount the cell individual offset;


1> if equation 2 below is fulfilled for a non-used frequency stored in the variableTRIGGERED_2E_EVENT:

2> remove that non-used frequency from the variable TRIGGERED_2E_EVENT.

Event 2 f: The estimated quality of the currently used frequency is abovea certain threshold

A UE shall be able to perform this measurement and the corresponding event reporting without

requiring compressed mode.

When an inter-frequency measurement configuring event 2f is set up, the UE shall:

1> create a variable TRIGGERED_2F_EVENT related to that measurement, which shall initially

be set to FALSE;


When event 2f is configured in the UE within a measurement, the UE shall:

1> if equation 1 below has been fulfilled for the used frequency during the time "Time to trigger":

2> if the variable TRIGGERED_2F_EVENT is set to FALSE:

3> set the variable TRIGGERED_2F_EVENT to TRUE;


4> set in "inter-frequency event results": "inter-frequency event identity" to "2f", and noIE "Inter-frequency cells";

4> include in IE "Inter-frequency measured results list" the measured results for the used

frequency, not taking into account the cell individual offset;


1> if the variable TRIGGERED_2F_EVENT is set to TRUE and if equation 2 is fulfilled for theused frequency:

2> set the variable TRIGGERED_2F_EVENT to FALSE.

14.3.1 Inter-RAT reporting eventsWithin the measurement reporting criteria field in the MEASUREMENT CONTROL message theUTRAN notifies the UE which events should trigger the UE to send a MEASUREMENT REPORTmessage. The listed events are the toolbox from which the UTRAN can choose the reporting events

that are needed for the implemented handover evaluation function, or other radio network functions.

All events are measured with respect to one of the measurement quantities given in subclause 14.3.0a,and of the frequency quality estimate given in subclause 14.3.0b. For UTRAN the measurement


25/36

quantities are measured on the monitored primary common pilot channels (CPICH) in FDD mode andthe monitored primary common control channels (PCCPCH) in TDD mode of the cell defined in the

measurement object. For other RATs the measurement quantities are system-specific. A "used UTRANfrequency" is a frequency that the UE have been ordered to measure upon and is also currently used for

the connection to UTRAN. "Other system" is e.g. GSM.

In the text below describing the events:

- "The BCCH ARFCN and BSIC combinations considered in that inter-RAT measurement" shallbe understood as the BCCH ARFCN and BSIC combinations of the inter-RAT cells pointed atin the IE "Cells for measurement" if it has been received for that inter-RAT measurement, or

otherwise of the cells included in the "inter-RAT cell info" part of the variable CELL_INFOLIST.

- "The BCCH ARFCNs considered in that inter-RAT measurement" shall be understood as theBCCH ARFCNs of the inter-RAT cells pointed at in the IE "Cells for measurement" if it has

been received for that inter-RAT measurement, or otherwise of the cells included in the "inter-RAT cell info" part of the variable CELL_INFO LIST.

When one inter-RAT measurement identity corresponds to multiple inter-RAT events with identical

event identities, the UE behaviour is not specified.

Event 3a: The estimated quality of the currently used UTRAN frequencyis below a certain threshold and the estimated quality of theother system is above a certain threshold.

When an inter-RAT measurement configuring event 3a is set up, the UE shall:

1> create a variable TRIGGERED_3A_EVENT related to that measurement, which shall initiallybe empty;


When event 3a is configured in the UE within a measurement, the UE shall:

1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "required":

2> if equations 1 and 2 below have both been fulfilled for a time period indicated by "Time to

trigger" from the same instant, respectively for the used UTRAN frequency and for one orseveral GSM cells that match any of the BCCH ARFCN and BSIC combinations consideredin that inter-RAT measurement:

3> if the Inter-RAT cell id of any of those GSM cells is not stored in the variable

TRIGGERED_3A_EVENT:

4> store the Inter-RAT cell ids of the GSM cells that triggered the event and that were

not previously stored in the variable TRIGGERED_3A_EVENT into that variable.


5> in "inter-RAT measurement event result": "inter-RAT event identity" to "3a","CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cells

that triggered the event (best one first), taking into account the cell individual

offset of the GSM cells;

5> "measured results" and possible "additional measured results" according tosubclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell

individual offset.

2> if equation 4 is fulfilled for a GSM cell whose inter-RAT cell id is stored in the variableTRIGGERED_3A_EVENT:

3> remove the inter-RAT cell id of that GSM cell from the variableTRIGGERED_3A_EVENT.


26/36

2> if equation 3 is fulfilled for the used frequency in UTRAN:

3> clear the variable TRIGGERED_3A_EVENT.

1> if the other RAT is GSM, and if IE "BSIC verification required" is set to "not required":

2> if equations 1 and 2 below have been fulfilled for a time period indicated by "Time to

trigger" from the same instant, respectively for the used UTRAN frequency and for one orseveral BCCH ARFCNs considered in that inter-RAT measurement:

3> if any of those BCCH ARFCNs is not stored into the variableTRIGGERED_3A_EVENT:

4> store the BCCH ARFCNs that triggered the event and that were not previously stored

in the variable TRIGGERED_3A_EVENT into that variable;


5> in "inter-RAT measurement event result": "inter-RAT event identity" to "3a","CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to BCCH

ARFCNs that triggered the event (best one first), taking into account the cell

individual offset of the GSM cells;

5> "measured results" and possible "additional measured results" according tosubclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell

individual offset.

2> if equation 4 is fulfilled for a BCCH ARFCN that is stored in the variableTRIGGERED_3A_EVENT:

3> remove that BCCH ARFCN from the variable TRIGGERED_3A_EVENT.

2> if equation 3 is fulfilled for the used frequency in UTRAN:

3> clear the variable TRIGGERED_3A_EVENT.

Event 3b: The estimated quality of other system is below a certainthreshold

When an inter-RAT measurement configuring event 3b is set up, the UE shall:

1> create a variable TRIGGERED_3B_EVENT related to that measurement, which shall initiallybe empty;


When event 3b is configured in the UE within a measurement, the UE shall:


2> if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for one

or several GSM cells that match any of the BCCH ARFCN and BSIC combinationsconsidered in that inter-RAT measurement:

3> if the inter-RAT cell id of any of those GSM cell is not stored in the variable

TRIGGERED_3B_EVENT:

4> store the inter-RAT cell ids of the GSM cells that triggered the event and that werenot previously stored in the variable TRIGGERED_3B_EVENT into that variable;


5> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3b","CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cells


27/36

that triggered the event (worst one first), taking into account the cell individualoffset of the GSM cells;

5> set the IE "measured results" and the IE "additional measured results" accordingto subclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell

individual offset.

2> if equation 2 below is fulfilled for a GSM cell whose inter-RAT cell id is stored in thevariable TRIGGERED_3B_EVENT:

3> remove the inter-RAT cell id of that GSM cell from the variable

TRIGGERED_3B_EVENT.



or several of the BCCH ARFCNs considered in that inter-RAT measurement:

3> if any of those BCCH ARFCN is not stored into the variable TRIGGERED_3B_EVENT:

4> store the BCCH ARFCNs that triggered the event and that were not previously stored

in the variable TRIGGERED_3B_EVENT into that variable;


5> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3b","CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to BCCH

ARFCNs that triggered the event (worst one first), taking into account the cellindividual offset of the GSM cells;


individual offset.

2> if equation 2 below is fulfilled for a BCCH ARFCN that is stored in the variableTRIGGERED_3B_EVENT:

3> remove that BCCH ARFCN from the variable TRIGGERED_3B_EVENT.

Event 3c: The estimated quality of other system is above a certainthreshold

When an inter-RAT measurement configuring event 3c is set up, the UE shall:

1> create a variable TRIGGERED_3C_EVENT related to that measurement, which shall initiallybe empty;


When event 3c is configured in the UE within a measurement, the UE shall:


2> if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for oneor several GSM cells that match any of the BCCH ARFCN and BSIC combinations

considered in that inter-RAT measurement:

3> if the inter-RAT cell id of any of those GSM cell is not stored in the variableTRIGGERED_3C_EVENT:

4> store the Inter-RAT cell ids of the GSM cells that triggered the event and that werenot previously stored in the variable TRIGGERED_3C_EVENT into that variable;



28/36

5> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3c","CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cells

that triggered the event (best one first), taking into account the cell individualoffset of the GSM cells;


individual offset.

2> if equation 2 below is fulfilled for a GSM cell whose inter-RAT cell id is stored in thevariable TRIGGERED_3C_EVENT:

3> remove the inter-RAT cell id of that GSM cell from the variable

TRIGGERED_3C_EVENT.



or several of the BCCH ARFCNs considered in that inter-RAT measurement:

3> if any of those BCCH ARFCN is not stored into the variable TRIGGERED_3C_EVENT:

4> store the BCCH ARFCNs that triggered the event and that were not previously storedin the variable TRIGGERED_3C_EVENT into that variable;


5> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3c","CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to BCCH

ARFCNs that triggered the event (best one first), taking into account the cellindividual offset of the GSM cells;


individual offset.

2> if equation 2 is fulfilled for a BCCH ARFCN that is stored in the variable

TRIGGERED_3C_EVENT:

3> remove that BCCH ARFCN from the variable TRIGGERED_3C_EVENT.

Event 3d: Change of best cell in other system

When an inter-RAT measurement configuring event 3d is set up, the UE shall:

1> create a variable BEST_CELL_3D_EVENT related to that measurement;


When event 3d is configured in the UE within a measurement, the UE shall:



3> store in the variable BEST_CELL_3D_EVENT the Inter-RAT cell id of the GSM cellthat has the best measured quantity among the GSM cells that match any of the BCCHARFCN and BSIC combinations considered in that inter-RAT measurement, not takinginto account the cell individual offset of the GSM cells;

3> send a measurement report with IE set as below:

4> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d","CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cell that is

stored in the variable BEST_CELL_3D_EVENT;


29/36

4> set the IE "measured results" and the IE "additional measured results" according tosubclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual

offset.

2> if equation 1 has been fulfilled for a time period indicated by "time to trigger" for a GSM

cell that is different from the one stored in BEST_CELL_3D_EVENT and that matches anyof the BCCH ARFCN and BSIC combinations considered in that inter-RAT measurement:

3> store the Inter-RAT cell id of that GSM cell in the variable BEST_CELL_3D_EVENT;


4> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d","CHOICE BSIC" to "verified BSIC" and "Inter-RAT cell id" to the GSM cell is now

stored in BEST_CELL_3D_EVENT;

4> set the IE "measured results" and the IE "additional measured results" according tosubclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individual

offset.



3> store in the variable BEST_CELL_3D_EVENT the BCCH ARFCN of the GSM cell that

has the best measured quantity among the BCCH ARFCNs considered in that inter-RATmeasurement;

3> send a measurement report with IE set as below:

4> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d","CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to the BCH ARFCN

that is stored in the variable BEST_CELL_3D_EVENT;

4> set the IE "measured results" and the IE "additional measured results" according tosubclause 8.6.7.5 and 8.4.2, respectively, not taking into account the cell individualoffset.

2> if equation 1 below has been fulfilled for a time period indicated by "time to trigger" for oneof the BCCH ARFCNs considered in that inter-RAT measurement and different from the

one stored in BEST_CELL_3D_EVENT:

3> store the BCCH ARFCN of that GSM cell in the variable BEST_CELL_3D_EVENT;


4> set in "inter-RAT measurement event result": "inter-RAT event identity" to "3d",

"CHOICE BSIC" to "non verified BSIC" and "BCCH ARFCN" to the BCCHARFCN that is now stored in the variable BEST_CELL_3D_EVENT;

4> set the IE "measured results" and the IE "additional measured results" according tosubclause8.4.2, not taking into account the cell individual offset.


30/36

14.6 UE internal measurements

14.6.1 UE internal measurement quantitiesFor UE internal measurements the following measurement quantities exist:

UE transmission (Tx) power, for TDD measured on a timeslot basis.

UE received signal strength power (RSSI).

UE Rx-Tx time difference (FDD only).

TADV (1.28 Mcps TDD).

14.6.2 UE internal measurement reporting eventsIn the Measurement reporting criteria field in the Measurement Control messages, the UTRAN notifies

the UE of which events should trigger a measurement report. UE internal measurement reportingevents that can trigger a report are given below. The reporting events are marked with vertical arrows

in the figures below. All events can be combined with time-to-trigger.

NOTE: The reporting events are numbered 6A, 6B, 6C, where 6, denotes that the event belongs

to the type UE internal measurements.

When one measurement identity corresponds to multiple internal events with identical event identities,the UE behaviour is not defined.

Reporting event 6A: The UE Tx power becomes larger than an absolutethreshold

Reporting event 6B: The UE Tx power becomes less than an absolutethreshold

Tx power

threshold 6A1

Tx powerthreshold 6B1

Tx power

threshold 6A2

Tx powerthreshold 6B2

Reportingevent 6A

Reportingevent 6B

Reportingevent 6A

Reportingevent 6B

UE Tx power

Time

Figure 14.6.2.2-1: Event-triggered measurement reports when the UE Tx powerbecomes larger or less than absolute thresholds


31/36

Reporting event 6C: The UE Tx power reaches its minimum value

Minimum

UE Tx power

Reporting

event 6C

UE Tx power

Time

Figure 14.6.2.3-1: Event-triggered measurement report when the UE Tx power reachesits minimum value

14.6.2.4 Reporting event 6D: The UE Tx power reaches its maximumvalue

Maximum

UE Tx power

Reporting

event 6D

UE Tx power

Time

Figure 14.6.2.4-1: Event-triggered report when the UE Tx power reaches its maximumvalue

Reporting event 6E: The UE RSSI reaches the UE's dynamic receiverrange

Reporting event 6F (FDD): The UE Rx-Tx time difference for a RLincluded in the active set becomes larger than an absolute

threshold

Reporting event 6F (1.28 Mcps TDD): The time difference indicated byTADV becomes larger than an absolute threshold

Reporting event 6G: The UE Rx-Tx time difference for a RL included inthe active set becomes less than an absolute threshold


32/36

RNCRestriction on number of cells in SIB11/12 due toinconsistency problem in 3GPP TS 25.331Technical Note No. 046

Copyright Nokia Networks TN Version 1.0


33/36

Page 2 Copyright Nokia Networks TN Version 1.0

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This document is intended for the use

of Nokia Networks' customers only for the purposes of the agreement under which the document

is submitted, and no part of it may be reproduced or transmitted in any form or means without

the prior written permission of Nokia Networks. The document has been prepared to be used by

professional and properly trained personnel, and the customer assumes full responsibility when

using it. Nokia Networks welcomes customer comments as part of the process of continuous

development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or

performance of the mentioned hardware or software products cannot be considered binding but

shall be defined in the agreement made between Nokia Networks and the customer. However,

Nokia Networks has made all reasonable efforts to ensure that the instructions contained in the

document are adequate and free of material errors and omissions. Nokia Networks will, if

necessary, explain issues which may not be covered by the document.

Nokia Networks' liability for any errors in the document is limited to the documentary correction

of errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT

OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might

arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according tothe applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respective

companies, and they are mentioned for identification purposes only.

Copyright Nokia Networks Oy 2004. All rights reserved.

TN Version Edited by Approved by1.0 23.12.2004

Jukka Miettinen23.12.2004Jouni Parkkinen


34/36

TN Version 1.0 Copyright Nokia Networks Page 3

TN 046 Restriction on number of cells in SIB11/12 due toinconsistency problem in 3GPP TS 25.331Validity:Software

RN1.5.2X RN1.5.2ED2X RN2.0

Keywords:RNC, Neighbour cell, RRC, SIB11, SIB12

Summary:Limitation in sending neighbour cell information in System Information Block (SIB) type 11 and 12. SIB11

and SIB12 messages can contain information on the maximum of 96 cells, but physical size of SIB data (no

more than 3552 bits) has capacity only for 47 cells.

Description:3GPP TS 25.331 Radio Resource Control (RRC) protocol specification has inconsistent requirements

concerning the maximum number of neighboring cells that can be broadcasted to the UEs in the System

information block 11 and 12 messages. On one hand the SIB type 11 and 12 messages can contain

information on the maximum of 96 cells (32 intra-frequency cells, 32 inter-frequency cells and 32 GSMcells), but on the other hand the physical size of SIB data (no more than 3552 bits) has capacity only for 47

cells.

Maximum numbers of each type of adjacencies that can be defined for one cell in RNC radio network

database are:

31 (ADJS) Intra-frequency Adjacency

48 (ADJI) Inter-frequency Adjacency (max 32 ADJI with in same UARFCN)

32 (ADJG) Inter-system Adjacency

The current RAN1.5.2ED2 and RN2.0 implementation of the Radio network configuration databasepresumes that all 96 cells will fit into the SIB data. However, if the number of neighboring cells exceeds 47

cells, the NBAP interface is not able to pack the neighbor cell information into the SIB data and the

scheduling of the system information blocks fails. The cell is blocked by the system and in RN1.5.2ED2 an

alarm 7761 RNW O/M SCENARIO FAILURE (BCCH scheduling error) is reported for the cell. If RN2.0 is used

then alarm 7771 WCDMA CELL OUT OF USE (BCCH scheduling error) is reported for the cell.

The physical size of SIB data limits the maximum number of neighboring cells, included in the System

Information for the cell selection and re-selection, to 47 cells. The capacity is smaller (35 cells) if HCS

(hierarchical cell structure) is used due to additional cell re-selection parameters.


35/36

Page 4 Copyright Nokia Networks TN Version 1.0

Instructions:If the operator tries to create more than 47 neighboring cells for an UTRAN cell, the scheduling of the

system information blocks fails and the cell is blocked by the system. The operator is not able to link thescheduling failure directly with the excessive number of neighbouring cells, which delays the recovery and

decreases the cell availability.

Note:Nokia guarantees 47 as maximum number of neighbors with any configuration (35 if HCS is used). The

limitation of 47 neighbouring cells is met with the worst possible situation that is 32 Inter-frequency + 15

Intra frequency neighbours (32+3 with HCS). If some other configuration is used then the number of

defined neighbour cells is higher before cell goes to BL(S) and the alarm 7761/7771 is given. This means

an operator can exceed the number but then the alarm 7761/7771 must be observed.

Reference:Technical Note Revision History

Date Version Editor Summary of changes

23.12.04 1.0 Jukka Miettinen The first version


36/36

List of Active SW Technical Notes for RNC

No Title TN Version RN1.5.2 RN1.5.2

ED2

RN2.0

001 LPD Alarm Printer Installation 2.0 X X002 Changing Password for Nemuadmin Username 2.1 X X

003 Copying BOPCCPCA and BOPCCP10 boot package into fallback

directory

2.0 X X

004 Limitation in the amount of the Neighbouring FDD Cell Information 1.0

005 TBU-0 usage with RNBC cabinet 1.0

006 RAQUEL Database Conversion 1.0

007 OSPF not supported 1.0

008 Alarms are not generated when NEMU WDU is removed 2.0 X X

009 The possible inconsistency of the alarm database (BAIDAT) 1.1

010 Resource leak in RNW Object Browser server process 1.0

011 Problem with measurement reports after switchover of N+1

redundant unit

2.0 X X

012 RNC and WCEL parameter modification requires WBTS restart 1.0 X

013 Configuring Network Adapters binding order in NEMU 2.0 X X014 SIB 11 info incorrect when 31 neighbour cells created 1.2 X

015 MSP 1+1 protection in NIS1 and NIS1P 3.0 X X

016 Controlled OMU switchover may cause spare OMU restart and

memory protection error

1.0 X

017 Availability of Nokia RNC RN1.5.1 Release 1.0

018 Wrong cause value in Iu release Request message 2.0 X X

019 The Boot Software for E Interchangeability CDSP-B and AL2S-A Plug-

in Units

1.0 X

020 The possible inconsistency of the alarm database, BAIDAT 1.1 X X

021 The Boot Software for F Interchangeability CDSP-B and AL2S-A Plug-

in Units

1.0 X

022 A2EA modification needs ICSU restart 2.0 X X

023 ICSU N+1 redundancy 2.0 X X

024 SQL Server memory configuration in NEMU and checking the eventrepublication period

2.0 X X

025 Modification of the traffic volume measurement pending time after

trigger parameters

2.0 X X

026 Control of the Dynamic Link Optimization feature 1.0 X

027 Incorrectly equipped plug-in-units 1.0 X X

028 Deletion of Static Routes 1.0 X X

029 IP Addresses under same Subnet 1.1 X X

030 ATM layer O&M problems with transmission network 1.0 X X

031 Inserting plug-in unit for OMU to the subrack 1.0

032 Better performance with recommended parameter modifications 2.0 X X

033 OMU-1 start-up failure caused by incorrect jumper setting 1.0 X X

034 Disabling of HMS transmission line and master switchover before

plug-in unit insertion or removal

1.0 X X

035 Removal of optimized MSP 1+1 protocol 1.0 X036 The State of PET or SET has no effect on traffic 1.0 X X

037 Cold restart needed in ED2 upgrade 1.0 X

038 RNC problem report instructions 1.0 X X

039 Possibly corrupted traffic of the IMA group 1.1 X X

040 RNW plan management compatibility 1.0 X

041 RNC NEMU QRN1.5 SERIES C-DRIVE CLEANUP 1.0 X X

042 User32.dll errors in NEMU 1.0 X X

043 AAL2 connection releasing timer in case of NNI link break 1.0 X X

044 RNC NEMU power down 1.0 X X X

045 Possible corrupted counter value in statistics measurement report 1.0 X X X

046 Restriction on number of cells in SIB11/12 due to inconsistency

problem in 3GPP TS 25.331

1.0 X X

047 Reducing UL power spiking in first radio link setups 2.0 X X

048 Enlarge RNW measurement file size to 20480KB 1.0 X X X

3G Event Description

Documents

Transcript of 3G Event Description