8.5 Global Procedures

25.4233GPPRelease 17TSUTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling

8.5.1 Error Indication

8.5.1.1 General

The Error Indication procedure is initiated by a node to report detected errors in a received message, provided they cannot be reported by an appropriate response message.

This procedure shall use the signalling bearer mode specified below.

8.5.1.2 Successful Operation

Figure 30: Error Indication procedure, Successful Operation

When the conditions defined in clause 10 are fulfilled, the Error Indication procedure is initiated by an ERROR INDICATION message sent from the receiving node. This message shall use the same mode of the signalling bearer and the same signalling bearer connection (if connection oriented) as the message that triggers the procedure.

When the ERROR INDICATION message is sent from a DRNC to an SRNC using connectionless mode of the signalling bearer, the S-RNTI IE shall be included in the message if the UE Context addressed by the D-RNTI IE which was received in the message triggering the Error Indication procedure exists. When the ERROR INDICATION message is sent from an SRNC to a DRNC using connectionless mode of the signalling bearer, the D-RNTI IE shall be included in the message if available.

When a message using connectionless mode of the signalling bearer is received in the DRNC and there is no UE Context in the DRNC as indicated by the D-RNTI IE, the DRNC shall include the D-RNTI from the received message in the D-RNTI IE and set the Cause IE to “Unknown RNTI” in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure.

When a message using connectionless mode of the signalling bearer is received in the SRNC and there is no UE in the SRNC as indicated by the S-RNTI IE, the SRNC shall include the S-RNTI from the received message in the S-RNTI IE and set the Cause IE to “Unknown RNTI” in the ERROR INDICATION message, unless another handling is specified in the procedure text for the affected procedure.

The ERROR INDICATION message shall include either the Cause IE, or the Criticality Diagnostics IE, or both the Cause IE and the Criticality Diagnostics IE to indicate the reason for the error indication.

Typical cause values for the ERROR INDICATION message are:

Protocol Causes:

– Transfer Syntax Error;

– Abstract Syntax Error (Reject);

– Abstract Syntax Error (Ignore and Notify);

– Message not Compatible with Receiver State;

– Unspecified.

8.5.1.2.1 Successful Operation for Iur-g

The RNC₁/BSS₁ and RNC₂/BSS₂ shall use the error indication procedure as specified in section 8.5.1.2.

8.5.1.3 Abnormal Conditions

–

8.5.2 Common Measurement Initiation

8.5.2.1 General

This procedure is used by an RNC to request the initiation of measurements of common resources to another RNC. The requesting RNC is referred to as RNC₁ and the RNC to which the request is sent is referred to as RNC₂.

This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.2.2 Successful Operation

Figure 30A: Common Measurement Initiation procedure, Successful Operation

The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the RNC₁ to the RNC₂.

Upon receipt, the RNC₂ shall initiate the requested measurement according to the parameters given in the request.

Unless specified below, the meaning of the parameters are given in other specifications.

[TDD – If the [3.84 Mcps TDD and 7.68 Mcps TDD – Time Slot IE] [1.28 Mcps – Time Slot LCR IE] is present in the COMMON MEASUREMENT INITIATION REQUEST message, the measurement request shall apply to the requested time slot individually.]

Common measurement type

If the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference”, then:

– The RNC₂ shall initiate the SFN-SFN Observed Time Difference measurements between the reference cell identified by the Reference Cell Identifier IE and the neighbouring cells identified by the UTRAN Cell Identifier IE (UC-ID) in the Neighbouring Cell Measurement Information IE.

– [3.84 Mcps TDD – The RNC₂ shall perform the measurement using the time slot specified in the Time Slot IE in the Neighbouring TDD Cell Measurement Information IE and using the midamble shift and burst type specified in the Midamble Shift And Burst Type IE in the Neighbouring TDD Cell Measurement Information IE. If Time Slot IE and Midamble Shift And Burst Type IE are not available in the Neighbouring TDD Cell Measurement Information IE, the RNC₂ may use any appropriate time slots, midamble shifts and burst types to make the measurement.]

– [7.68 Mcps TDD – The RNC₂ shall perform the measurement using the time slot specified in the Time Slot IE in the Neighbouring TDD Cell Measurement Information 7.68 Mcps IE and using the midamble shift and burst type specified in the Midamble Shift And Burst Type 7.68 Mcps IE in the Neighbouring TDD Cell Measurement Information 7.68 Mcps IE. If Time Slot IE and Midamble Shift And Burst Type 7.68 Mcps IE are not available in the Neighbouring TDD Cell Measurement Information 7.68 Mcps IE, the RNC₂ may use any appropriate time slots, midamble shifts and burst types to make the measurement.]

If the Common Measurement Type IE is set to “load”, the RNC₂ shall initiate measurements of uplink and downlink load on the measured object identified by the Reference Cell Identifier IE. If either uplink or downlink load satisfies the requested report characteristics, the RNC₂ shall report the result of both uplink and downlink measurements.

If the Common Measurement Type IE is set to “UTRAN GPS Timing of Cell Frames for UE Positioning”, “UTRAN GANSS Timing of Cell Frames for UE Positioning”, “transmitted carrier power”, “received total wide band power”, or “UL timeslot ISCP” the RNC₂ shall initiate measurements on the measured object identified by the Reference Cell Identifier IE.

If the Common Measurement Type IE is set to “UTRAN GANSS Timing of Cell Frames for UE Positioning”, then the RNC₂ shall initiate the UTRAN GANSS Timing of Cell Frames measurements using the GNSS system time identified by GANSS Time ID IE included in the COMMON MEASUREMENT INITIATION REQUEST message.

– If the Common Measurement Type IE is set to “UTRAN GANSS Timing of Cell Frames for UE Positioning” and the GANSS Time ID IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC₂ shall assume that the corresponding GANSS time is “Galileo” system time.

If the Common Measurement Type IE is set to “RT load”, the RNC₂ shall initiate measurements of uplink and downlink estimated share of RT (Real Time) traffic of the load of the measured object. If either uplink or downlink RT load satisfies the requested report characteristics, the RNC₂ shall report the result of both uplink and downlink measurements.

If the Common Measurement Type IE is set to “NRT load Information”, the RNC₂ shall initiate measurements of uplink and downlink NRT (Non Real Time) load situation on the measured object. If either uplink or downlink NRT load satisfies the requested report characteristics, the RNC₂ shall report the result of both uplink and downlink measurements.

Report characteristics

The Report Characteristics IE indicates how the reporting of the measurement shall be performed. See also Annex B.

If the Report Characteristics IE is set to “On Demand” and if the SFN IE is not provided, the RNC₂ shall report the result of the requested measurement immediately in the COMMON MEASUREMENT INITIATION RESPONSE message. If the SFN IE is provided, it indicates the frame for which the measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the SFN IE is present and if the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference “, then the SFN IE relates to the Radio Frames of the Reference Cell identified by the Reference Cell Identifier IE.

If the Report Characteristics IE is set to “Periodic” and if the SFN IE is not provided, the RNC₂ shall immediately and periodically initiate a Common Measurement Reporting procedure for this measurement, with a frequency as specified by the Report Periodicity IE. If the SFN IE is provided, the RNC₂ shall initiate a Common Measurement Reporting procedure for this measurement at the SFN indicated in the SFN IE, and shall repeat this initiation periodically thereafter with a frequency as specified by the Report Periodicity IE. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the SFN IE is present and if the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference “, then the SFN IE relates to the Radio Frames of the Reference Cell identified by the Reference Cell Identifier IE.

If the Report Characteristics IE is set to “Event A”, the RNC₂ shall initiate the Common Measurement Reporting procedure when the measured entity rises above the requested threshold, as specified by the Measurement Threshold IE, and then stays above the threshold for the requested hysteresis time, as specified by the Measurement Hysteresis Time IE. If the Measurement Hysteresis Time IE is not included, the RNC₂ shall use the value zero for the hysteresis time.

If the Report Characteristics IE is set to “Event B”, the RNC₂ shall initiate the Common Measurement Reporting procedure when the measured entity falls below the requested threshold, as specified by the Measurement Threshold IE, and then stays below the threshold for the requested hysteresis time, as specified by the Measurement Hysteresis Time IE. If the Measurement Hysteresis Time IE is not included, the RNC₂ shall use the value zero for the hysteresis time.

If the Report Characteristics IE is set to “Event C”, the RNC₂ shall initiate the Common Measurement Reporting procedure when the measured entity rises more than the requested threshold specified by the Measurement Increase/Decrease Threshold IE, and only when this rise occurs within the requested rising time specified by the Measurement Change Time IE. After reporting this type of event, the RNC₂ shall not initiate the next C event reporting for the same measurement during the subsequent time specified by the Measurement Change Time IE.

If the Report Characteristics IE is set to “Event D”, the RNC₂ shall initiate the Common Measurement Reporting procedure when the measured entity falls more than the requested threshold specified by the Measurement Increase/Decrease Threshold IE, and only when this fall occurs within the requested falling time specified by the Measurement Change Time IE. After reporting this type of event,, the RNC₂ shall not initiate the next D event reporting for the same measurement during the subsequent time specified by the Measurement Change Time IE.

If the Report Characteristics IE is set to “Event E”, the RNC₂shall initiate the Common Measurement Reporting procedure when the measured entity rises above the Measurement Threshold 1 IE and stays above the threshold for the Measurement Hysteresis Time IE (Report A). When the conditions for Report A are met and if the Report Periodicity IE is provided, the RNC₂ shall initiate the Common Measurement Reporting procedure periodically with the requested report frequency specified by the Report Periodicity IE. If the conditions for Report A have been met and the measured entity falls below the Measurement Threshold 2 IE and stays below the threshold for the Measurement Hysteresis Time IE, the RNC₂ shall initiate the Common Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the RNC₂ shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the RNC₂ shall use the value zero as hysteresis times for both Report A and Report B.

If the Report Characteristics IE is set to “Event F”, the RNC₂ shall initiate the Common Measurement Reporting procedure when the measured entity falls below the Measurement Threshold 1 IE and stays below the threshold for the Measurement Hysteresis Time IE (Report A). When the conditions for Report A are met and if the Report Periodicity IE is provided, the RNC₂ shall initiate the Measurement Reporting procedure periodically with the requested report frequency specified by the Report Periodicity IE. If the conditions for Report A have been met and the measured entity rises above the Measurement Threshold 2 IE and stays above the threshold for the Measurement Hysteresis Time IE, the RNC₂ shall initiate the Common Measurement Reporting procedure (Report B) and shall terminate any corresponding periodic reporting. If the Measurement Threshold 2 IE is not present, the RNC₂ shall use the value of the Measurement Threshold 1 IE instead. If the Measurement Hysteresis Time IE is not included, the RNC₂ shall use the value zero as hysteresis times for both Report A and Report B.

[1.28Mcps TDD-If the Report Characteristics IE is set to “Event H” (figure B.7), the Measurement Reporting procedure (Report A) is initiated when the measurement value of measured entity rises above the Measurement Threshold 1 and stays above the threshold for the Measurement Hysteresis Time (T₁ in figure B.7).] The measurement value of measured entity in Report A substitutes the Measurement Base value for the consequent measurement reporting.

When the Report A conditions has been met and the measurement value of measured entity rises above or falls below the Measurement Base Value by Measurement Fluctuation Range (H₁ in figure B.7), and stays there for the Measurement Hysteresis Time (T_h in figure B.7) counting from the beginning of every Report Periodicity, the Measurement Reporting procedure (Report B or Report C) is initiated. The the measurement value of measured entity in (Report B or Report C) substitutes the Measurement Base value for the consequent measurement reporting.

When the Report A conditions have been met and the measurement value of measured entity falls below the Measurement Threshold 2 and stays there for the Measurement Hysteresis Time (T_h in figure B.7), the Measurement Reporting procedure (Report D) is initiated and the reporting is terminated.]

If the Report Characteristics IE is set to “On Modification” and if the SFN IE is not provided, the RNC₂ shall report the result of the requested measurement immediately. If the SFN IE is provided, it indicates the frame for which the first measurement value shall be provided. The provided measurement value shall be the one reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). Furthermore, if the SFN IE is present and if the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference”, then the SFN IE relates to the Radio Frames of the Reference Cell identified by the Reference Cell Identifier IE. Following the first measurement report, the RNC₂ shall initiate the Common Measurement Reporting procedure in accordance to the following conditions:

1. If the Common Measurement Type IE is set to “UTRAN GPS Timing of Cell Frames for UE Positioning”:

– If the T_UTRAN-GPS Change Limit IE is included in the T_UTRAN-GPS Measurement Threshold Information IE, the RNC₂ shall calculate the change of T_UTRAN-GPS value (F_n) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC₂ shall initiate the Common Measurement Reporting procedure and set n equal to zero when the absolute value of F_n rises above the threshold indicated by the T_UTRAN-GPS Change Limit IE. The change of T_UTRAN-GPS value (F_n) is calculated according to the following:

F_n=0 for n=0

F_n = (M_n – M_n-1) mod 37158912000000 – ((SFN_n – SFN_n-1) mod 4096) *10*3.84*10^3*16 + F_n-1 for n>0

F_n is the change of the T_UTRAN-GPS value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.

M_n is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFN_n.

M_n-1 is the previous measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFN_n-1.

M₁ is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered.

M₀ is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered.

– If the Predicted T_UTRAN-GPS Deviation Limit IE is included in the T_UTRAN-GPS Measurement Threshold Information IE, the RNC₂ shall update the P_n and F each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC₂ shall initiate the Common Measurement Reporting procedure and set n equal to zero when F_n rises above the threshold indicated by the Predicted T_UTRAN-GPS Deviation Limit IE. The P_n and F_n are calculated according to the following:

P_n=b for n=0

P_n = ((a/16) * ((SFN_n – SFN_n-1) mod 4096) /100 +((SFN_n – SFN_n-1) mod 4096)*10*3.84*10^3*16 + P_n-1 ) mod 37158912000000 for n>0

F_n = min((M_n – P_n) mod 37158912000000, (P_n – M_n) mod 37158912000000) for n>0

P_n is the predicted T_UTRAN-GPS value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.

A is the last reported T_UTRAN-GPS Drift Rate value.

B is the last reported T_UTRAN-GPS value.

F_n is the deviation of the last measurement result from the predicted T_UTRAN-GPS value (P_n ) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.

M_n is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFN_n .

M₁ is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered.

The T_UTRAN-GPS Drift Rate is determined by the RNS₂ in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])).

2. If the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference”:

– If the SFN-SFN Change Limit IE is included in the SFN-SFN Measurement Threshold Information IE, the RNC₂ shall calculate the change of SFN-SFN value (F_n) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC₂ shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set n equal to zero when the absolute value of F_n rises above the threshold indicated by the SFN-SFN Change Limit IE. The change of the SFN-SFN value is calculated according to the following:

F_n=0 for n=0

[FDD – F_n = (M_n – a) mod 614400 for n>0]

[TDD – F_n = (M_n – a) mod 40960 for n>0]

F_n is the change of the SFN-SFN value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.

A is the last reported SFN-SFN.

M_n is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at SFN_n.

M₁ is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after the first Common Measurement Reporting at initiation or after the last event was triggered.

– If the Predicted SFN-SFN Deviation Limit IE is included in the SFN-SFN Measurement Threshold Information IE, the RNC₂ shall each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]), update the P_n and F_n. The RNC₂ shall initiate the Common Measurement Reporting procedure in order to report the particular SFN-SFN measurement which has triggered the event and set n equal to zero when F_n rises above the threshold indicated by the Predicted SFN-SFN Deviation Limit IE. The P_n and F_n are calculated according to the following:

P_n=b for n=0

[FDD – P_n = ((a/16) * ((SFN_n – SFN_n-1) mod 4096)/100 + P_n-1 ) mod 614400 for n>0]

[FDD – F_n = min((M_n – P_n) mod 614400, (P_n – M_n) mod 614400) for n>0]

[TDD – P_n =((a/16) * (15*(SFN_n – SFN_n-1)mod 4096 + (TS_n – TS_n-1))/1500 + P_n-1 ) mod 40960 for n>0]

[TDD – F_n = min((M_n – P_n) mod 40960, (P_n – M_n) mod 40960) for n>0]

P_n is the predicted SFN-SFN value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.

A is the last reported SFN-SFN Drift Rate value.

B is the last reported SFN-SFN value.

F_n is the deviation of the last measurement result from the predicted SFN-SFN value (P_n ) when n measurements have been received after first Common Measurement Reporting at initiation or after the last event was triggered.

M_n is the latest measurement result received after point C in the measurement model (TS 25.302 [26]), measured at the [TDD – the Time Slot TS_n of] the Frame SFN_n.

M₁ is the first measurement result received after point C in the measurement model (TS 25.302 [26]), after first Common Measurement Reporting at initiation or after the last event was triggered.

The SFN-SFN Drift Rate is determined by the RNS₂ in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])).

3. If the Common Measurement Type IE is set to “UTRAN GANSS Timing of Cell Frames for UE Positioning”:

– If the T_UTRAN-GANSS Change Limit IE is included in the T_UTRAN-GANSS Measurement Threshold Information IE, the RNC₂ shall calculate the change of T_UTRAN-GANSS value (F_n) each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC₂ shall initiate the Common Measurement Reporting procedure and set n equal to zero when the absolute value of F_n rises above the threshold indicated by the T_UTRAN-GANSS Change Limit IE. The change of T_UTRAN-GANSS value (F_n) is calculated according to the following:

Fn=0 for n=0

Fn = (GAMn – GAMn-1) mod 5308416000000 – ((SFNn – SFNn-1) mod 4096) *10*3.84*10^3*16 + Fn-1

for n>0

Fn is the change of the TUTRAN-GANSS value expressed in unit [1/16 chip] when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.

GAMn is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at SFNn.

GAMn-1 is the previous GANSS measurement result received after point C in the GANSS measurement model, measured at SFNn-1.

GAM1 is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered.

GAM0 is equal to the value reported in the first Common Measurement Reporting at initiation or in the Common Measurement Reporting when the event was triggered.

GANSS measurement model is the timing between cell j and GANSS Time Of Day. T_UE-GANSSj is defined as the time of occurrence of a specified UTRAN event according to GANSS time. The specified UTRAN event is the beginning of a particular frame (identified through its SFN) in the first detected path (in time) of the cell j CPICH, where cell j is a cell chosen by the UE. The reference point for T_UE-GANSSj shall be the antenna connector of the UE.

– If the Predicted T_UTRAN-GANSS Deviation Limit IE is included in the T_UTRAN-GANSS Measurement Threshold Information IE, the RNC₂ shall update the P_n and F each time a new measurement result is received after point C in the measurement model (TS 25.302 [26]). The RNC₂ shall initiate the Common Measurement Reporting procedure and set n equal to zero when F_n rises above the threshold indicated by the Predicted T_UTRAN-GANSS Deviation Limit IE. The P_n and F_n are calculated according to the following:

P_n=b for n=0

P_n = ((a/16) * ((SFN_n – SFN_n-1) mod 4096)/100 +((SFN_n – SFN_n-1) mod 4096)*10*3.84*10^3*16 + P_n-1 ) mod 5308416000000 for n>0

F_n = min((GAM_n – P_n) mod 5308416000000, (P_n – GAM_n) mod 5308416000000) for n>0

P_n is the predicted T_UTRAN-GANSS value when n measurement results have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.

A is the last reported T_UTRAN-GANSS Drift Rate value.

B is the last reported T_UTRAN-GANSS value.

F_n is the deviation of the last measurement result from the predicted T_UTRAN-GANSS value (P_n ) when n measurements have been received after the first Common Measurement Reporting at initiation or after the last event was triggered.

GAM_n is the latest GANSS measurement result received after point C in the GANSS measurement model, measured at SFN_n.

GAM₁ is the first GANSS measurement result received after point C in the GANSS measurement model, after the first Common Measurement Reporting at initiation or after the last event was triggered.

The T_UTRAN-GANSSS Drift Rate is determined by the RNS₂ in an implementation-dependent way after point B (see model of physical layer measurements in (TS 25.302 [26])).

If the Report Characteristics IE is not set to “On Demand”, the RNC₂ is required to perform reporting for a common measurement object, in accordance with the conditions provided in the COMMON MEASUREMENT INITIATION REQUEST message, as long as the object exists. If no common measurement object(s) for which a measurement is defined exists any more, the RNC₂ shall terminate the measurement locally without reporting this to RNC₁.

If at the start of the measurement, the reporting criteria are fulfilled for any of Event A, Event B, Event E or Event F, the RNC₂ shall initiate a Measurement Reporting procedure immediately, and then continue with the measurements as specified in the COMMON MEASUREMENT INITIATION REQUEST message.

Common measurement accuracy

If the Common Measurement Type IE is set to “UTRAN GPS Timing of Cell Frames for UE Positioning”, then the RNC₂ shall use the T_UTRAN-GPS Measurement Accuracy Class IE included in the Common Measurement Accuracy IE according to the following:

– If the T_UTRAN-GPS Measurement Accuracy Class IE indicates “Class A”, then the concerned RNC₂ shall perform the measurement with the highest supported accuracy within the accuracy classes A, B or C.

– If the T_UTRAN-GPS Measurement Accuracy Class IE indicates the “Class B”, then the concerned RNC₂ shall perform the measurements with the highest supported accuracy within the accuracy classes B and C.

– If the T_UTRAN-GPS Measurement Accuracy Class IE indicates “Class C”, then the concerned RNC₂ shall perform the measurements with the highest supported accuracy according to class C.

If the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference”, then the concerned RNC₂ shall initiate the SFN-SFN observed Time Difference measurements between the reference cell identified by UC-ID IE and the neighbouring cells identified by their UC-ID. The Report Characteristics IE applies to each of these measurements.

If the Common Measurement Type IE is set to “UTRAN GANSS Timing of Cell Frames for UE positioning”, then the RNC₂ shall use the T_UTRAN-GANSS Measurement Accuracy Class IE included in the Common Measurement Accuracy IE according to the following:

– If the T_UTRAN-GANSS Measurement Accuracy Class IE indicates “Class A”, then the concerned RNC₂ shall perform the measurement with the highest supported accuracy within the accuracy classes A, B or C.

– If the T_UTRAN-GANSS Measurement Accuracy Class IE indicates the “Class B”, then the concerned RNC₂ shall perform the measurements with the highest supported accuracy within the accuracy classes B and C.

– If the T_UTRAN-GANSS Measurement Accuracy Class IE indicates “Class C”, then the concerned RNC₂ shall perform the measurements with the highest supported accuracy according to class C.

Higher layer filtering

The Measurement Filter Coefficient IE indicates how filtering of the measurement values shall be performed before measurement event evaluation and reporting.

The averaging shall be performed according to the following formula.

The variables in the formula are defined as follows

F_n is the updated filtered measurement result

F_n-1 is the old filtered measurement result

M_n is the latest received measurement result from physical layer measurements, the unit used for M_n is the same unit as the reported unit in the COMMON MEASUREMENT INITIATION RESPONSE, COMMON MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for Fn).

A = ½^(k/2) -, where k is the parameter received in the Measurement Filter Coefficient IE. If the Measurement Filter Coefficient IE is not present, a shall be set to 1 (no filtering).

In order to initialise the averaging filter, F₀ is set to M₁ when the first measurement result from the physical layer measurement is received.

Measurement Recovery Behavior:

If the Measurement Recovery Behavior IE is included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC₂ shall, if Measurement Recovery Behavior is supported, include the Measurement Recovery Support Indicator IE in the COMMON MEASUREMENT INITIATION RESPONSE message and perform the Measurement Recovery Behavior as described in subclause 8.5.3.2.

Response message

If the RNC₂ was able to initiate the measurement requested by RNC, it shall respond with the COMMON MEASUREMENT INITIATION RESPONSE message. The message shall include the same Measurement ID that was used in the COMMON MEASUREMENT INITIATION REQUEST message.

In the case in which the Report Characteristics IE is set to “On Demand” or “On Modification”:

– The COMMON MEASUREMENT INITIATION RESPONSE message shall include the Common Measurement Object Type IE containing the measurement result. It shall also include the Common Measurement Achieved Accuracy IE if the Common Measurement Type IE is set to “UTRAN GPS Timing of Cell Frames for UE positioning” or “UTRAN GANSS Timing of Cell Frames for UE positioning”.

– If the Common Measurement Type IE is not set to “SFN-SFN Observed Time Difference” and if the SFN Reporting Indicator IE is set to “FN Reporting Required”, then the RNC₂ shall include the SFN IE in the COMMON MEASUREMENT INITIATION RESPONSE message,. The reported SFN shall be the SFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). If the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference”, then the SFN Reporting Indicator IE is ignored.

– If the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference”, then the RNC₂ shall report all the available measurements in the Successful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information IE, and the RNC₂ shall report the neighbouring cells with no measurement result available in the Unsuccessful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information IE. For all available measurement results, the RNC₂ shall include in the Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE the SFN-SFN Quality IE and the SFN-SFN Drift Rate Quality IE, if available.

If the Common Measurement Type IE is set to “UTRAN GPS Timing of Cell Frames for UE Positioning” and the Report Characteristics IE is set to “On Demand” or “On Modification”, the RNC₂ shall include in the T_UTRAN-GPS Measurement Value Information IE the T_UTRAN-GPS Quality IE and the T_UTRAN-GPS Drift Rate Quality IE, if available.

If the Common Measurement Type IE is set to “UTRAN GANSS Timing of Cell Frames for UE Positioning” and the Report Characteristics IE is set to “On Demand” or “On Modification”, the RNC₂ shall include in the T_UTRAN-GANSS Measurement Value Information IE, the T_UTRAN-GANSS Quality IE and the T_UTRAN-GANSS Drift Rate Quality IE, if available.

8.5.2.2.1 Successful Operation for Iur-g

The procedure is initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the RNC₁ to the BSS₂ or from the BSS₁ to the RNC₂/BSS₂.

Upon receipt, the RNC₂ /BSS₂ shall initiate the requested measurement according to the parameters given in the request.

[1.28Mcps TDD-The procedure is also initiated with a COMMON MEASUREMENT INITIATION REQUEST message sent from the TDD RNC₁ to the BSS₂ for multiple GERAN cells’ measurements by allocating unique Measurement ID for each GERAN cell. Upon receipt, the BSS₂ shall initiate the requeted measurement according to the parameters given in the request.]

Common measurement type on Iur-g

If the Common Measurement Type IE is set to “load”, the RNC₂/BSS₂ shall initiate measurements and report results as described in section 8.5.2.2.

If the Common Measurement Type IE is set to “RT load”, the RNC₂/BSS₂ shall initiate measurements and report results as described in section 8.5.2.2.

If the Common Measurement Type IE is set to “NRT load Information”, the RNC₂/BSS₂ shall initiate measurements and report results as described in section 8.5.2.2.

Report characteristics on Iur-g

The Report Characteristics IE indicates how the reporting of the measurement shall be performed. This IE is used as described in section 8.5.2.2.

Response message for Iur-g

If the RNC₂/BSS₂ was able to initiate the measurement requested by RNC₁/BSS₁ it shall respond with the COMMON MEASUREMENT INITIATION RESPONSE message sent. The message shall include the same Measurement ID that was used in the measurement request. Only in the case when the Report Characteristics IE is set to “On Demand”, the COMMON MEASUREMENT INITIATION RESPONSE message shall contain the measurement result.

[1.28Mcps TDD- If the BSS₂ was able to initiate the measurement requested by RNC₁, it shall respond with one or more COMMON MEASUREMENT INITIATION RESPONSE messages sent. The message(s) should include the same Measurement ID that was used in the mesasurement request.]

8.5.2.3 Unsuccessful Operation

Figure 30B: Common Measurement Initiation procedure, Unsuccessful Operation

If the requested measurement cannot be initiated, the RNC₂ shall send a COMMON MEASUREMENT INITIATION FAILURE message. The message shall include the same Measurement ID IE that was used in the COMMON MEASUREMENT INITIATION REQUEST message and shall include the Cause IE set to an appropriate value.

Typical cause values are as follows:

Radio Network Layer Cause

– Measurement not supported for the object;

– Measurement Temporarily not Available.

8.5.2.4 Abnormal Conditions

If the COMMON MEASUREMENT INITIATION REQUEST message contains the SFN-SFN Measurement Threshold Information IE (in the Measurement Threshold IE contained in the Report Characteristics IE) and it does not contain at least one IE, the RNC₂ shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

If the COMMON MEASUREMENT INITIATION REQUEST message contains the T_UTRAN-GPS Measurement Threshold Information IE (in the Measurement Threshold IE contained in the Report Characteristics IE) and it does not contain at least one IE, the RNC₂ shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

If the COMMON MEASUREMENT INITIATION REQUEST message contains the T_UTRAN-GANSS Measurement Threshold Information IE (in the Measurement Threshold IE contained in the Report Characteristics IE) and it does not contain at least one IE, the RNC₂ shall reject the procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

If the Common Measurement Type IE is set to “UTRAN GPS Timing of Cell Frames for UE positioning”, but the T_UTRAN-GPS Measurement Accuracy Class IE in the Common Measurement Accuracy IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC₂ shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

If the Common Measurement Type IE is set to “UTRAN GANSS Timing of Cell Frames for UE positioning”, but the T_UTRAN-GANSS Measurement Accuracy Class IE in the Common Measurement Accuracy IE is not included in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC₂ shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

If the Common Measurement Type received in the Common Measurement Type IE is not “load”, “RT load” or “NRT load Information”, and if the Common Measurement Type received in the Common Measurement Type IE is not defined in TS 25.215 [11] or TS 25.225 [14] to be measured on the Common Measurement Object Type indicated in the COMMON MEASUREMENT INITIATION REQUEST message the RNC₂ shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

If the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference”, but the Neighbouring Cell Measurement Information IE is not received in the COMMON MEASUREMENT INITIATION REQUEST message, the RNC₂ shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

The allowed combinations of the Common Measurement Type and Report Characteristics Type are shown in the table below marked with “X”. For not allowed combinations, the RNC₂ shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

Table 5: Allowed Common Measurement Type and Report Characteristics Type Combinations

Common measurement type	Report characteristics type
	On Demand	Periodic	Event A	Event B	Event C	Event D	Event E	Event F	Event-H	On Modification
Received total wide band power	X	X	X	X	X	X	X	X
Transmitted Carrier Power	X	X	X	X	X	X	X	X
UL Timeslot ISCP	X	X	X	X	X	X	X	X
Load	X	X	X	X	X	X	X	X	X
UTRAN GPS Timing of Cell Frames for UE Positioning	X	X								X
SFN-SFN Observed Time Difference	X	X								X
RT load	X	X	X	X	X	X	X	X
NRT load Information	X	X	X	X	X	X	X	X
UpPTS interference	X	X	X	X	X	X	X	X
UTRAN GANSS Timing of Cell Frames for UE Positioning	X	X								X

[TDD – If the Common Measurement Type requires the Time Slot Information but the [3.84Mcps TDD and 7.68 Mcps TDD – Time Slot IE] [1.28Mcps TDD – Time Slot LCR IE] is not provided in the COMMON MEASUREMENT INITIATION REQUEST message the RNS₂ shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.]

If the SFN IE is included in the COMMON MEASUREMENT INITIATION REQUEST message and the Report Characteristics IE is other than “Periodic”, “On Demand” or “On Modification”, the RNS₂ shall reject the Common Measurement Initiation procedure using the COMMON MEASUREMENT INITIATION FAILURE message.

8.5.2.4.1 Abnormal Conditions for Iur-g

The measurements which can be requested on the Iur and Iur-g interfaces are shown in the table below marked with “X”.

Table 6: Allowed Common measurement type on Iur and Iur-g interfaces

Common Measurement Type	Interface
	Iur	Iur-g
Received total wide band power	X
Transmitted Carrier Power	X
UL Timeslot ISCP	X
Load	X	X
UTRAN GPS Timing of Cell Frames for LCS	X
SFN-SFN Observed Time Difference	X
RT load	X	X
NRT load Information	X	X
UTRAN GANSS Timing of Cell Frames for UE Positioning	X

If the RNC₂ receives from the BSS₁ a COMMON MEASUREMENT INITIATION REQUEST message in which a measurement, which is not applicable on the Iur-g interface, is requested, the RNC₂ shall reject the Common Measurement Initiation procedure.

If the BSS₂ receives from the BSS₁ / RNC₁ a COMMON MEASUREMENT INITIATION REQUEST message in which a measurement, which is not applicable on the Iur-g interface, is requested, the BSS₂ shall reject the Common Measurement Initiation procedure.

If the RNC₂ receives from the BSS₁ a COMMON MEASUREMENT INITIATION REQUEST message in which the SFN reporting indicator IE is set to “FN Reporting Required”, the RNC₂ shall ignore that IE.

If the BSS₂ receives from the BSS₁ / RNC₁ a COMMON MEASUREMENT INITIATION REQUEST message in which the SFN reporting indicator IE is set to “FN Reporting Required”, the BSS₂ shall ignore that IE.

The allowed combinations of the Common measurement type and Report characteristics type are shown in the table in section 8.5.2.4 marked with “X”. For not allowed combinations, the RNC₂/BSS₂ shall reject the Common Measurement Initiation procedure.

8.5.3 Common Measurement Reporting

8.5.3.1 General

This procedure is used by an RNC to report the result of measurements requested by another RNC using the Common Measurement Initiation.

This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.3.2 Successful Operation

Figure 30C: Common Measurement Reporting procedure, Successful Operation

If the requested measurement reporting criteria are met, the RNC₂ shall initiate the Common Measurement Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications.

The Measurement ID IE shall be set to the Measurement ID provided by RNC₁ when initiating the measurement with the Common Measurement Initiation procedure.

If the achieved measurement accuracy does not fulfil the given accuracy requirement (see TS 25.133 [23] and TS 25.123 [24]) or the measurement is temporarily not available in case Measurement Recovery Behavior is supported, the Common Measurement Value Information IE shall indicate Measurement not Available. If the RNC₂ was configured to perform the Measurement Recovery Behavior, the RNC₂ shall indicate Measurement Available to the RNC₁ when the achieved measurement accuracy again fulfils the given accuracy requirement (see TS 25.133 [23] and TS 25.123 [24]) and include the Measurement Recovery Report Indicator IE in the COMMON MEASUREMENT REPORT message if the requested measurement reporting criteria are not met.

For measurements included in the Successful Neighbouring Cell SFN-SFN Observed Time Difference Measurement Information IE, the RNC₂ shall include the SFN-SFN Quality IE and the SFN-SFN Drift Rate Quality IE if available.

If the Common Measurement Type provided by RNC₁ when initiating the measurement with the Common Measurement Initiation procedure was “UTRAN GPS Timing of Cell Frames for UE Positioning”, then the RNC₂ shall include in the T_UTRAN-GPS Measurement Value Information IE the T_UTRAN-GPS Quality IE and the T_UTRAN-GPS Drift Rate Quality IE, if available.

If the Common Measurement Type provided by RNC₁ when initiating the measurement with the Common Measurement Initiation procedure was “UTRAN GANSS Timing of Cell Frames for UE Positioning”, then the RNC₂ shall include in the T_UTRAN-GANSS Measurement Value Information IE the T_UTRAN-GANSS Quality IE and the T_UTRAN-GANSS Drift Rate Quality IE, if available.

8.5.3.2.1 Successful Operation for Iur-g

If the requested measurement reporting criteria are met, the RNC₂/BSS₂ shall initiate a Measurement Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications.

The Measurement ID IE shall be set to the Common Measurement ID provided by RNC₁/BSS₁ when initiating the measurement with the Common Measurement Initiation procedure.

If the Common measurement type provided by RNC₁ when initiating the measurement with the Common Measurement Initiation procedure was “SFN-SFN Observed Time Difference”, then RNC₂ shall include in the COMMON MEASUREMENT REPORT all the available measurements in the Successful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information IE and shall include the neighbouring cells with no measurement result available in the Unsuccessful Neighbouring cell SFN-SFN Observed Time Difference Measurement Information IE.

If the Common measurement type provided by RNC₁ when initiating the measurement with the Common Measurement Initiation procedure was not set to “SFN-SFN Observed Time Difference” and the SFN Reporting Indicator when initiating the measurement was set to “FN Reporting Required”, the RNC₂ shall include the SFN IE in the COMMON MEASUREMENT REPORT message. The reported SFN shall be the SFN at the time when the measurement value was reported by the layer 3 filter, referred to as point C in the measurement model (TS 25.302 [26]). If the Common Measurement Type IE is set to “SFN-SFN Observed Time Difference”, then the SFN Reporting Indicator IE is ignored.

8.5.3.3 Abnormal Conditions

–

8.5.4 Common Measurement Termination

8.5.4.1 General

This procedure is used by an RNC to terminate a measurement previously requested by the Common Measurement Initiation procedure.

This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.4.2 Successful Operation

Figure 30D: Common Measurement Termination procedure, Successful Operation

This procedure is initiated with a COMMON MEASUREMENT TERMINATION REQUEST message.

Upon receipt, RNC₂ shall terminate reporting of common measurements corresponding to the received Measurement ID IE.

8.5.4.2.1 Successful Operation for Iur-g

The RNC₁/BSS₁ and RNC₂/BSS₂ shall use the Common Measurement Termination procedure as specified in section 8.5.4.2.

8.5.4.3 Abnormal Conditions

–

8.5.5 Common Measurement Failure

8.5.5.1 General

This procedure is used by an RNC to notify another RNC that a measurement previously requested by the Common Measurement Initiation procedure can no longer be reported.

This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.5.2 Successful Operation

Figure 30E: Common Measurement Failure procedure, Successful Operation

This procedure is initiated with a COMMON MEASUREMENT FAILURE INDICATION message, sent from RNC₂ to RNC₁ to inform the RNC₁ that a previously requested measurement can no longer be reported. RNC₂ has locally terminated the indicated measurement. The RNC₂ shall include in the COMMON MEASUREMENT FAILURE INDICATION message the reason for the failure in the Cause IE.

8.5.5.2.1 Successful Operation for Iur-g

The RNC₁/BSS₁ and RNC₂/BSS₂ shall use the Common Measurement Failure procedure as specified in section 8.5.5.2.

8.5.5.3 Abnormal Conditions

–

8.5.6 Information Exchange Initiation

8.5.6.1 General

This procedure is used by an RNC to request the initiation of an information exchange with another RNC.

This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.6.2 Successful Operation

Figure 30F: Information Exchange Initiation procedure, Successful Operation

The procedure is initiated with an INFORMATION EXCHANGE INITIATION REQUEST message sent from RNC₁ to RNC₂.

Upon receipt, the RNC₂ shall provide the requested information according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications.

If the Information Exchange Object Type IE is set to “MBMS Bearer Service” and the Information Type Item IE is set to “MBMS Bearer Service Full Address”, the RNC₂ shall report for each TMGI included in the received MBMS Bearer Service Identifiers List IE, the Access Point Name and the IP Multicast Address corresponding to this TMGI in the MBMS Bearer Service Identifiers List IE in the INFORMATION EXCHANGE INITIATION RESPONSE message.

[FDD – If the Information Exchange Object Type IE is set to “MBMS Bearer Service in MBMS Cell” and the Information Type Item IE is set to “MBMS Counting Information”, the RNC₂ shall perform counting in cells as defined in TS 25.346 [50] and report in the Counting Result IE for each TMGI included in the received MBMS Bearer Service Identifiers List IE for each cell included in the received MBMS Cell List IE either the counting information or, if relevant counting information is not available in RNC₂ (TS 25.346 [50]), the value “0” in the INFORMATION EXCHANGE INITIATION RESPONSE message.]

[FDD – If the Information Exchange Object Type IE is set to “MBMS Bearer Service in MBMS Cell” and the Information Type Item IE is set to “MBMS Transmission Mode”, the RNC₂ shall report for each TMGI included in the received MBMS Bearer Service Identifiers List IE for each cell included in the received MBMS Cell List IE, the transmission mode for each TMGI in the cells of RNC₂ that have a neighbour relation to the cells received in MBMS Cell List IE as defined in TS 25.346 [50] in the INFORMATION EXCHANGE INITIATION RESPONSE message. If no cells of RNC₂ have a neighbour relation to a cell received in MBMS Cell List IE for a TMGI the value “Not Provided” shall be used.]

[FDD – If the Information Exchange Object Type IE is set to “MBMS Cell” and the Information Type Item IE is set to “MBMS Neighbouring Cell Information”, the RNC₂ shall report for each cell included in the received MBMS Cell List IE, the MBMS radio bearer information for each cells in the INFORMATION EXCHANGE INITIATION RESPONSE message.]

[FDD – If the Information Exchange Object Type IE is set to “MBMS Bearer Service in MBMS Cell” and the Information Type Item IE is set to “MBMS RLC Sequence Number”, the RNC₂ shall report for each TMGI included in the received MBMS Bearer Service Identifiers List IE for each cell included in the received MBMS Cell List IE, the RLC sequence number for each TMGI for the indicated cells in the INFORMATION EXCHANGE INITIATION RESPONSE message.]

If the Information Exchange Object Type IE is set to “ANR Cell” and the Information Type Item IE is set to “ANR Cell Information”, the RNC₂ shall, if supported, for each cell in the ANR Cell List IE that is controlled by RNC₂, report the ANR Cell Information in the INFORMATION EXCHANGE INITIATION RESPONSE message.

If the Information Type IE contains a GANSS Generic Data IE, at least one of the GANSS Navigation Model And Time Recovery, GANSS Time Model GNSS-GNSS, GANSS UTC Model, GANSS Almanac, GANSS Real Time Integrity, GANSS Data Bit Assistance, GANSS Additional Navigation Models And Time Recovery, GANSS Additional UTC Models, GANSS Auxiliary Information, DBDS Corrections Request, BDS Ionospheric Grid Model Request IEs shall be present in the GANSS Generic Data IE.

– If the GANSS Generic Data IE does not contain the GANSS ID IE, the RNC₂ shall assume that the corresponding GANSS is “Galileo”.

If the Information Exchange Object Type IE is set to “Common E-RGCH Cell” and the Information Type Item IE is set to “Common E-RGCH Cell Information”, the RNC₂ shall, for each Common E-RGCH capable cell in the Common E-RGCH Cell List IE that is controlled by RNC₂, report the Common E-RGCH Cell Information in the INFORMATION EXCHANGE INITIATION RESPONSE message.

Information Report Characteristics:

The Information Report Characteristics IE indicates how the reporting of the information shall be performed.

If the Information Report Characteristics IE is set to “On Demand”, the RNC₂ shall report the requested information immediately.

If the Information Report Characteristics IE is set to “Periodic”, the RNC₂ shall report the requested information immediately and then shall periodically initiate the Information Reporting procedure for all the requested information, with the report frequency indicated by the Information Report Periodicity IE.

If the Information Report Characteristics IE is set to “On Modification”, the RNC₂ shall report the requested information immediately if available. If the requested information is not available at the moment of receiving the INFORMATION EXCHANGE INITIATION REQUEST message, but expected to become available after some acquisition time, the RNC₂ shall initiate the Information Reporting procedure when the requested information becomes available. The RNC₂ shall then initiate the Information Reporting procedure in accordance to the following conditions:

– If the Information Type Item IE is set to “IPDL Parameters”, the RNC₂ shall initiate the Information Reporting procedure when any change in the parameters occurs.

– If the Information Type Item IE is set to “DGPS Corrections”, the RNC₂ shall initiate the Information Reporting procedure for this specific Information Type when either the PRC has drifted from the previously reported value more than the threshold indicated in the PRC Deviation IE in the Information Threshold IE or a change has occurred in the IODE.

– If the Information Type Item IE is set to “GPS Information” and the GPS Information Item IE includes “GPS Navigation Model & Recovery Assistance”, the RNC₂ shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred regarding either the IODC or the list of visible satellites, identified by the Sat ID IEs.

– If the Information Type Item IE is set to “GPS Information” and the GPS Information Item IE includes “GPS Ionospheric Model”, the RNC₂ shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred.

– If the Information Type Item IE is set to “GPS Information” and the GPS Information Item IE includes “GPS UTC Model”, the RNC₂ shall initiate the Information Reporting procedure for this specific GPS Information Item when a change has occurred in the t_ot or WN_t parameter.

– If the Information Type Item IE is set to “GPS Information” and the GPS Information Item IE includes “GPS Almanac”, the RNC₂ shall initiate the Information Reporting procedure for this specific GPS Information Item when a change in the t_oa or WN_a parameter has occurred.

– If the Information Type Item IE is set to “GPS Information” and the GPS Information Item IE includes “GPS Real-Time Integrity”, the RNC₂ shall initiate the Information Reporting procedure for this specific GPS Information Item when any change has occurred.

– If the Information Type IE is set to “Cell Capacity Class”, the RNC₂ shall initiate the Information Reporting procedure for uplink and downlink cell capacity class when any change has occurred. If either uplink or downlink cell capacity class satisfies the requested report characteristics, the RNC₂ shall report the result of both uplink and downlink cell capacity information.

– If any of the above Information Type IEs becomes temporarily unavailable, the RNC₂ shall initiate the Information Reporting procedure for this specific Information Item by indicating “Information Not Available” in the Requested Data Value Information IE. If the Information becomes available again, the RNC₂ shall initiate the Information Reporting procedure for this specific Information.

– If the Information Type IE is set to “NACC related data”, the RNC₂ shall initiate the Information Reporting procedure for NACC related data if any change has occurred.

– If the Information Type IE is set to “Inter-frequency Cell Information”, the RNC₂ shall initiate the Information Reporting procedure for this specific Information Item when any change has occurred to the inter-frequency cell information broadcasted in the SIB11, SIB11ter or SIB12.

– If the Information Type Item IE is set to “DGANSS Corrections”, the RNC₂ shall initiate the Information Reporting procedure for this specific Information Type when either the PRC has drifted from the previously reported value more than the threshold indicated in the PRC Deviation IE in the Information Threshold IE or a change has occurred in the IODE.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Navigation Model And Time Recovery IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the Sat ID IEs.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Ionospheric Model IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS UTC Model IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change has occurred in the t_ot or WN_t parameter.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Almanac IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information Item when a change in the T_oa, IOD_a, or Week Number parameter has occurred.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Real Time Integrity IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Data Bit Assistance IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information Item when any change has occurred.

– If the Information Type Item IE is set to “MBMS Transmission Mode”, the RNC₂ shall initiate the Information Reporting procedure when any change in the parameter occurs.

– If the Information Type Item IE is set to “MBMS Neighbouring Cell Information”, the RNC₂ shall initiate the Information Reporting procedure when any change in the parameters occurs.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Additional Navigation Models And Time Recovery IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred regarding either the IOD or the list of visible satellites, identified by the Sat ID IEs.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Additional Ionospheric Model IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Additional UTC Models IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the t_ot,WN_ot, WN_t, or N^A parameter.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Earth Orientation Parameters IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the t_EOP parameter.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Auxiliary Information IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information item when a change has occurred in the Signals Available or Channel Number IE parameter.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the DBDS Corrections Request IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.

– If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the BDS Ionospheric Grid Model Request IE, the RNC₂ shall initiate the Information Reporting procedure for this specific GANSS Information item when any change has occurred.

– If the Information Type Item IE is set to “Common E-RGCH Cell Information”, the RNC₂ shall initiate the Information Reporting procedure for this Common E-RGCH Information item when a change has occurred in the Common E-RGCH Cell Information IE parameter for the specific cell.

Response message:

If the RNC₂ is able to determine the information requested by the RNC₁, it shall respond with the INFORMATION EXCHANGE INITIATION RESPONSE message. The message shall include the Information Exchange ID IE set to the same value that was included in the INFORMATION EXCHANGE INITIATION REQUEST message. When the Report Characteristics IE is set to or “On Modification” or “Periodic”, the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the Requested Data Value IE if the data are available. When the Report Characteristics IE is set to “On Demand”, the INFORMATION EXCHANGE INITIATION RESPONSE message shall contain the Requested Data Value IE.

If the Requested Data Value IE contains the GANSS Common Data IE, at least one of the GANSS Ionospheric Model, GANSS RX Pos, GANSS Additional Ionospheric Model, or GANSS Earth Orientation Parameters IEs shall be present.

Any GANSS Generic Data IE associated with a given GANSS included in the Requested Data Value IE shall contain at least one of the DGANSS Corrections, GANSS Navigation Model And Time Recovery, GANSS Time Model, GANSS UTC Model, GANSS Almanac, GANSS Real Time Integrity, GANSS Data Bit Assistance, GANSS Additional Time Models, GANSS Additional Navigation Models And Time Recovery, GANSS Additional UTC Models, GANSS Auxiliary Information, DBDS Corrections, or BDS Ionospheric Grid Model IEs.

– If the GANSS Generic Data IE does not contain the GANSS ID IE, the corresponding GANSS is “Galileo”.

– The DGANSS Corrections IE contains one or several DGANSS Information IE(s), each of them associated with a GANSS Signal. A DGANSS Information IE for a particular GANSS that does not contain the GANSS Signal ID IE is by default associated with the default signal defined in TS 25.331 [16], clause 10.3.3.45a.

– The DBDS Corrections IE contains one or several DBDS information IE(s), each of them associated with a GANSS Signal. A DBDS Information IE for a particular GANSS that does not contain the GANSS Signal ID IE is by default associated with the default signal defined in TS 25.331 [16], clause 10.3.3.45a.

– The GANSS Real Time Integrity IE contains one or several Satellite Information IEs, each of them associated with a satellite and a GANSS Signal. A Satellite Information IE for a particular GANSS that does not contain the Bad GANSS Signal ID IE is by default associated with all the signals of the corresponding satellite (see [53], IS-GPS-200 [55], IS-GPS-705 [56], IS-GPS-800 [57], DTFA01-96-C-00025 [58], IS-QZSS [59], [60]).

If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Time Model GNSS-GNSS IE with exactly one bit set to value “1”, the RNC₂ shall include the GANSS Time Model IE in the Requested Data Value IE with the requested time information.

If the Information Type Item IE is set to “GANSS Information” and the GANSS Information IE includes the GANSS Time Model GNSS-GNSS IE with more than one bit set to value “1”, the RNC₂ shall include the GANSS Additional Time Models IE in Requested Data Value IE with the requested time information for each GANSS.

If the Information Type Item IE is set to “DGPS Corrections”, the RNC₂ shall include the DGPS Corrections IE in Requested Data Value IE with the DGNSS Validity Period IE included, if available.

If the Information Type Item IE is set to “DGANSS Corrections”, the RNC₂ shall include the DGANSS Corrections IE in Requested Data Value IE with the DGNSS Validity Period IE included, if available.

If the Information Type Item IE is set to "GPS Almanac", the RNC₂ shall include the GPS Almanac IE in Requested Data Value IE with the Complete Almanac Provided IE included, if available.

If the Information Type Item IE is set to "GANSS Almanac", the RNC₂ shall include the GANSS Almanac IE in Requested Data Value IE with the Complete Almanac Provided IE included, if available.

If the Information Type Item IE is set to "GANSS Time Model GNSS-GNSS", the RNC₂ shall include the GANSS Time Model IE in Requested Data Value IE with the Delta_T IE included, if available.

8.5.6.2.1 Successful Operation for Iur-g

The procedure is initiated with an INFORMATION EXCHANGE INITIATION REQUEST message sent from BSS₁ to BSS₂/RNC₂ or by RNC₁ to BSS₂.

Upon receipt, the BSS₂/RNC₂ shall provide the requested information according to the parameters given in the request. Unless specified below, the meaning of the parameters are given in other specifications.

Information Report Characteristics on Iur-g:

If the Information Type Item IE is set to “Cell Capacity Class”, the RNC₂/BSS₂ shall initiate measurements and report results as described in section 8.5.6.2.

The Information Report Characteristics IE indicates how the reporting of the information shall be performed. This IE is used as described in section 8.5.6.2.

8.5.6.3 Unsuccessful Operation

Figure 30G: Information Exchange Initiation procedure, Unsuccessful Operation

If the requested Information Type received in the Information Type IE indicates a type of information that RNC₂ cannot provide, the RNC₂ shall reject the Information Exchange Initiation procedure.

If the requested information provision cannot be accessed, the RNC₂ shall reject the procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.

The message shall include the Information Exchange ID IE set to the same value that was used in the INFORMATION EXCHANGE INITIATION REQUEST message and the Cause IE set to an appropriate value.

Typical cause values are as follows:

Radio Network Layer Cause:

– Information temporarily not available;

– Information Provision not supported for the object.

8.5.6.4 Abnormal Conditions

If the Information Report Characteristics IE is set to “On Modification”, and the Information Type Item IE is set to “DGPS Corrections”, but the Information Threshold IE is not received in the INFORMATION EXCHANGE INITIATION REQUEST message, the RNC₂ shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.

If the Information Exchange Object Type IE is set to a value other than “GSM Cell” and the Information Type Item IE set to “NACC related data” the RNC₂ shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.

If the Information Type Item IE is set to the value “MBMS Bearer Service Full Address” and the Information Exchange Object Type IE is not set to “MBMS Bearer Service”, the RNC₂ shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.

If the Information Type Item IE is set to the value “ANR Cell Information” and the Information Exchange Object Type IE is not set to “ANR Cell”, the RNC₂ shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.

If the Information Type Item IE is set to the value “ANR Cell Information” and the Information Exchange Object Type IE is set to “ANR Cell”, but the RNC₂ can only collect the “Requested Data Value” for the subset of the cells requested, RNC₂ shall not reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION RESPONSE message with the information it could obtain.

If the Information Type Item IE is set to the value “Common E-RGCH Cell Information” and the Information Exchange Object Type IE is not set to “Common E-RGCH Cell”, the RNC₂ shall reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION FAILURE message.

If the Information Type Item IE is set to the value “Common E-RGCH Cell Information” and the Information Exchange Object Type IE is set to “Common E-RGCH Cell”, but only the subset of the cells requested are Common E-RGCH capable, the RNC₂ shall not reject the Information Exchange Initiation procedure and shall send the INFORMATION EXCHANGE INITIATION RESPONSE message with the information it could obtain.

The allowed combinations of the Information type and Information Report Characteristics type are shown in the table below marked with “X”. For not allowed combinations, the RNC₂ shall reject the Information Exchange Initiation procedure using the INFORMATION EXCHANGE INITIATION FAILURE message.

Table 6a: Allowed Information Type and Information Report Characteristics type combinations

Type	Information Report Characteristics Type
	On Demand	Periodic	On Modification
UTRAN Access Point Position with Altitude Information	X
UTRAN Access Point Position	X
IPDL Parameters	X	X	X
GPS Information	X	X	X
DGPS Corrections	X	X	X
GPS RX Pos	X
SFN-SFN Measurement Reference Point Position	X
Cell Capacity Class	X		X
NACC related data	X		X
MBMS Bearer Service Full Address	X
Inter-frequency Cell Information	X		X
GANSS Information	X	X	X
DGANSS Corrections	X	X	X
GANSS RX Pos	X
MBMS Counting Information [FDD only]	X
MBMS Transmission Mode [FDD only]			X
MBMS Neighbouring Cell Information [FDD only]	X		X
MBMS RLC Sequence Number [FDD only]	X
ANR Cell Information	X
Common E-RGCH Cell Information	X		X

8.5.6.4.1 Abnormal Conditions for Iur-g

The information types that can be requested on the Iur and Iur-g interfaces are shown in the table below marked with “X”. For information types that are not applicable on the Iur-g interface, the BSS shall reject the Information Exchange Initiation procedure.

Table 7: Allowed Information types on Iur and Iur-g interfaces

Information Type	Interface
	Iur	Iur-g
UTRAN Access Point Position with Altitude Information	X
UTRAN Access Point Position	X
IPDL Parameters	X
DGPS Corrections	X
GPS Information	X
GPS RX Pos	X
SFN-SFN Measurement Reference Point Position	X
Cell Capacity Class	X	X
NACC related data	X
MBMS Bearer Service Full Address	X
Inter-frequency Cell Information	X
DGANSS Corrections	X
GANSS Information	X
GANSS RX Pos	X
MBMS Counting Information [FDD only]	X
MBMS Transmission Mode [FDD only]	X
MBMS Neighbouring Cell Information [FDD only]	X
MBMS RLC Sequence Number [FDD only]	X

8.5.7 Information Reporting

8.5.7.1 General

This procedure is used by a RNC to report the result of information requested by another RNC using the Information Exchange Initiation.

This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.7.2 Successful Operation

Figure 30H: Information Reporting procedure, Successful Operation

If the requested information reporting criteria are met, the RNC₂ shall initiate an Information Reporting procedure. Unless specified below, the meaning of the parameters are given in other specifications.

The Information Exchange ID IE shall be set to the Information Exchange ID provided by the RNC₁ when initiating the information exchange with the Information Exchange Initiation procedure.

The Requested Data Value IE shall include at least one IE containing the data to be reported.

8.5.7.2.1 Successful Operation for Iur-g

The RNC₁/BSS₁ and RNC₂/BSS₂ shall use the Information Reporting procedure as specified in section 8.5.7.2.

8.5.7.3 Abnormal Conditions

–

8.5.8 Information Exchange Termination

8.5.8.1 General

This procedure is used by a RNC to terminate the information exchange requested using the Information Exchange Initiation.

This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.8.2 Successful Operation

Figure 30I: Information Exchange Termination procedure, Successful Operation

This procedure is initiated with a INFORMATION EXCHANGE TERMINATION REQUEST message.

Upon receipt, the RNC₂ shall terminate the information exchange corresponding to the Information Exchange ID IE provided by the RNC₁ when initiating the information exchange with the Information Exchange Initiation procedure.

8.5.8.2.1 Successful Operation for Iur-g

The RNC₁/BSS₁ and RNC₂/BSS₂ shall use the Information Exchange Termination procedure as specified in section 8.5.8.2.

8.5.8.3 Abnormal Conditions

–

8.5.9 Information Exchange Failure

8.5.9.1 General

This procedure is used by a RNC to notify another that the information exchange it previously requested using the Information Exchange Initiation can no longer be reported.

This procedure uses the signalling bearer connection for the relevant Distant RNC Context.

8.5.9.2 Successful Operation

Figure 30J: Information Exchange Failure procedure, Successful Operation

This procedure is initiated with a INFORMATION EXCHANGE FAILURE INDICATION message, sent from the RNC₂ to the RNC₁, to inform the RNC₁ that information previously requested by the Information Exchange Initiation procedure can no longer be reported. The RNC₂ shall include in the INFORMATION EXCHANGE FAILURE INDICATION message the Information Exchange ID IE set to the same value provided by the RNC₁ when initiating the information exchange with the Information Exchange Initiation procedure, and the RNC₂ shall include the Cause IE set to an appropriate value.

Typical cause values are as follows:

Radio Network Layer Cause:

Information temporarily not available.

8.5.9.2.1 Successful Operation for Iur-g

The RNC₁/BSS₁ and RNC₂/BSS₂ shall use the Information Exchange Failure procedure as specified in section 8.5.9.2.

8.5.10 Reset

8.5.10.1 General

The purpose of the reset procedure is to align the resources in RNC₁ and RNC₂ in the event of an abnormal failure.

The procedure uses connectionless signalling.

8.5.10.2 Successful Operation

Figure 30K: Reset procedure, Successful Operation

The procedure is initiated with a RESET REQUEST message sent from the RNC₁ to the RNC₂.

If the Reset Indicator IE is set to “Context”, then:

– For all indicated UE Contexts identified by the S-RNTI IE, the RNC₂ in the role of DRNC, shall remove all the indicated UE Contexts and all the radio resources allocated for these UE Contexts. In addition, the RNC₂ shall take actions according to Annex D.2.

– For all indicated UE Contexts identified by the D-RNTI IE, the RNC₂ in the role of SRNC, shall remove the information related to the RNC₁ for all indicated UE Contexts and the radio resources allocated for these UE Contexts.

If the Reset Indicator IE is set to “Context Group”, then:

– For all indicated UE Context Groups identified by the S-RNTI Group IE, the RNC₂ in the role of DRNC, shall remove all the indicated UE Contexts and all the radio resources allocated for these UE Contexts. In addition, the RNC₂ shall take actions according to Annex D.2.

If the Reset Indicator IE is set to “All Contexts”, then the RNC₂ shall:

– In the role of DRNC, remove all the UE Contexts for which the RNC₁ is the SRNC and all the radio resources allocated for these UE Contexts. In addition, the RNC₂ shall take actions according to Annex D.2.

– In the role of SRNC, remove the information related to the RNC₁ for all the UE Contexts and all the radio resources allocated for these UE Contexts.

For all the removed UE Contexts and for all the UE Contexts for which the RNC₂ has removed information related to the RNC₁, the RNC₂ shall also initiate release of the dedicated or common user plane resources that were involved in these UE Contexts. After clearing all related resources, the RNC₂ shall return the RESET RESPONSE message to the RNC₁.

8.5.10.3 Abnormal Conditions

If the RESET message is received, any other ongoing procedure (except another Reset procedure) on same Iur interface related to a context indicated explicitly or implicitly in the message shall be aborted.

8.5.11 Direct Information Transfer

8.5.11.1 General

This procedure is used by an RNC to transfer information to another RNC spontaneously.

This procedure shall use the connectionless mode of signalling bearer.

8.5.11.2 Successful Operation

Figure 30L: Direct Information Transfer procedure, Successful Operation

The procedure is initiated with an DIRECT INFORMATION TRANSFER message sent from RNC₁ to RNC₂.

If the initiating RNC of this procedure is RNC₁, RNC₁ shall provide appropriate information in the Provided Information IE.

MBMS Channel Type Indication:

At the start time of a session for an MBMS bearer service, if the RNC₁ is in the DRNC role for some Ues whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC₂ and if the channel type is determined by the RNC₁ for certain cells in the DRNS, the procedure shall be initiated by the RNC₁ to the RNC₂. In this case, the RNC₁ shall include in the Provided Information IE the Channel Type Information IE in the DIRECT INFORMATION TRANSFER message.

During a session of an MBMS bearer service, if the RNC₁ is in the DRNC role for some Ues whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC₂, then the RNC₁ may initiate this procedure to indicate channel type change for the MBMS bearer service in certain cells. In this case, the RNC₁ shall include in the Provided Information IE the Channel Type Information IE in the DIRECT INFORMATION TRANSFER message.

The RNC₁ shall include the available information within the PTM Cell List IE, the PTP Cell List IE and/or the Not Provided Cell List IE in the Channel Type Information IE.

MBMS Preferred Frequency Layer Indication:

At the start time of a session for an MBMS bearer service, if the RNC₁ is in the DRNC role for at least one CELL_DCH UE whose UE Link contains the concerned MBMS bearer service and whose SRNC is RNC₂ and if the preferred frequency layer is determined by the RNC₁ for certain cells that host at least one of these CELL_DCH Ues whose SRNC is RNC₂, the procedure shall be initiated by the RNC₁ to the RNC₂. In this case, the RNC₁ shall include in the Provided Information IE the Preferred Frequency Layer Information IE in the DIRECT INFORMATION TRANSFER message.

If some of the cells controlled by RNC₁ that host at least one of these CELL_DCH Ues whose SRNC is RNC₂ are configured with different preferred frequencies, the Additional Preferred Frequency IE as well as Default Preferred Frequency IE shall be included in the Preferred Frequency Layer Information IE. In this case, for each preferred frequency different from the Default Preferred Frequency IE, one Additional Preferred Frequency IE shall be included containing at least one Corresponding Cells IE.

ANR Report Indication:

The message contains ANR Report Indication IE if the initiating RNC (RNC₁) has decided to forward a logged ANR report received over Uu to RNC₂. On reception of the ANR Report Indication IE, RNC2 may use the information to configure neighbour relations.

8.5.12 Information Transfer Control

8.5.12.1 General

This procedure is used by an RNC to control transfer of information (e.g. log information related to ANR) from an RNC to any other RNC. This procedure is initiated by an RNC to suspend or resume transfer of information.

This procedure shall use the connectionless mode of signalling bearer.

8.5.12.2 Successful Operation

Figure 30M: Information Transfer Control procedure, Successful Operation

The RNC₁ initiates the procedure by sending the INFORMATION TRANSFER CONTROL REQUEST message to the RNC₂.

The Control Type IE within the INFORMATION TRANSFER CONTROL REQUEST message shall be used to either suspend or to resume (respectively indicated by Suspension IE or Resume IE in Control Type IE) the transfer of information for the specified scope of objects indicated by Controlled Object Scope IE.

If the control of information transfer is intended for individual cells, those cells shall be indicated in the UMTS Cell Information IE within the Controlled Object Scope IE. If the UMTS Cell Information IE is not included, the procedure is intended for the whole entity indicated in RNC-ID IE or Extended RNC-ID IE. In shared network configurations, PLMN identities shall be indicated with Multiple PLMN List IE.

8.5.12.3 Abnormal Conditions

–