8c Signalling procedures between RIM SAPs

3GPP48.018Base Station System (BSS) - Serving GPRS Support Node (SGSN)BSS GPRS protocol (BSSGP)General Packet Radio Service (GPRS)Release 17TS

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

8c.1 General

8c.1.1 Introduction

The following sub-clauses describe the generic RAN Information Management (RIM) procedures which support the exchange of information, via the core network, between peer application entities located in a GERAN, in a UTRAN, in an E-UTRAN or in an eHRPD evolved access network.

The RIM function is performed through the interaction of the following sub-layers:

– the underlying part of BSSGP used to transport and route the RIM PDUs from a BSS to an SGSN or from an SGSN to a BSS over the Gb interface;

– the RIM protocol allowing the exchange of the information between two BSSs or between a BSS and an RNS or between a BSS and an eNodeB or between an eNodeB and an eHRPD eAN transparently through the core network;

– the application part on the top of the RIM protocol, referred to as the "RIM application" in this specification.

NOTE: The functional split between the RIM application and the RIM protocol is provided for information in the present specification and should allow for various implementations.

The PDUs conveying the RAN information between two RIM entities are including containers that shall not be interpreted by the core network nodes. The exchange of information is triggered by the application in a controlling BSS or, in the case of the Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]), by the originating BSS.

The support of different applications is achieved by the appropriate definition of specific application containers for those applications.

If the RAN Information Management (RIM) feature is supported by both the BSS and the SGSN, the RIM procedures can be used by any RIM application running on this BSS and requiring information transfer between two BSSs via the core network.

NOTE: Specific requirements applicable to RIM between GERAN and UTRAN or between GERAN and E-UTRAN and between E-UTRAN and eHRPD eAN are specified in sub-clause 8c.1.4.

8c.1.2 Definitions

8c.1.2.1 Controlling, serving, originating and receiving nodes

The BSS requesting the information is called the "controlling BSS", the BSS providing the requested information is called the "serving BSS". Considering a pair of BSSs, each may be at the same time both a controlling BSS and a serving BSS. An exception is when an application uses the RIM procedure to transfer information related to the Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]) in which case the BSS receiving the information is called the “receiving BSS” and the BSS autonomously providing the information is called the “originating BSS”.

In the present specification the term "BSS" should be understood as "RNC, eNodeB or eAN" in the relevant situations (e. g. NACC from UTRAN/E-UTRAN to GERAN), unless it is explicitly stated otherwise.

8c.1.2.2 RIM association

A RIM association links unambiguously either a cell in the serving BSS with the controlling BSS that has initiated an information request related to that cell for a given application, or a cell in the controlling BSS with the serving BSS that receives the RAN-INFORMATION-REQUEST PDU for a given application, and is identified by the following pieces of information:

– Controlling BSS identifier, or, for some particular values of the SON Transfer Application Identity for which the Reporting Cell Identifier is a cell in the controlling BSS (see TS 36.413 [36]), the serving BSS identifier.

– Cell Identifier in the serving BSS, or, for some particular values of the SON Transfer Application Identity (see TS 36.413 [36]), Cell Identifier in the controlling BSS.

– RIM Application Identity

– SON Transfer Application Identity (only applicable if the RIM Application Identity indicates "SON Transfer").

8c.1.2.3 RIM variables

In this protocol description, variables are used to represent the status of the relevant entity as a result of an event, such as the reception of an information element in a message. The variables serve the purpose of specifying an abstract model of the protocol entity, and do not therefore impose any particular implementation.

The following variables are defined in the serving BSS:

– MULTIPLE_REPORTING_ONGOING: this variable indicates whether event-based multiple reporting is active or not for a given RIM association. This variable is initialised to FALSE prior to the reception of any request related to the corresponding association from the controlling BSS, then it is updated according to the relevant procedure requirements.

– MULTIPLE_REPORT_SETTING_RSN: this variable stores the RSN of the last request having initiated or re-initiated multiple reporting in the serving BSS and is used as a reference to ascertain whether any further request received for this association is outdated or not. The value of this variable is only significant when multiple reporting is active (i.e. MULTIPLE_REPORTING_ONGOING set to TRUE).

8c.1.3 RIM PDUs description

8c.1.3.1 RAN-INFORMATION-REQUEST PDU

The RAN-INFORMATION-REQUEST PDU is used by the controlling BSS to request or interrupt an information transfer from a serving BSS. The RAN-INFORMATION-REQUEST PDU specifies the requested operation and the expected information when applicable. The following RAN-INFORMATION-REQUEST PDU type extensions are defined:

– RAN-INFORMATION-REQUEST/Single Report is used to request a single report.

– RAN-INFORMATION-REQUEST/Multiple Report is used to request event-driven multiple reports.

– RAN-INFORMATION-REQUEST/Stop is used to stop event-driven multiple reports.

8c.1.3.2 RAN-INFORMATION PDU

The RAN-INFORMATION PDU is used by the serving BSS to transmit the requested information to the controlling BSS or by the originating BSS to autonomously send Multilateration Timing Advance (see 3GPP TS 43.059 [23]) related information to the receiving BSS. The following RAN-INFORMATION PDU type extensions are defined:

– RAN-INFORMATION/Single Report is used to acknowledge the reception of a RAN-INFORMATION-REQUEST/Single Report and to transmit the requested single report information. The RAN-INFORMATION/Single Report is the only RAN-INFORMATION PDU type extension used to transfer information related to the Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]).

– RAN-INFORMATION/Initial Multiple Report is used to acknowledge the reception of a RAN-INFORMATION-REQUEST/Multiple Report and to transmit the initial report of the event-driven multiple reporting.

– RAN-INFORMATION/Multiple Report is used to transmit subsequent reports while event-driven multiple reporting is active.

– RAN-INFORMATION/Stop is used to acknowledge the reception of a RAN-INFORMATION-REQUEST/Stop.

– RAN-INFORMATION/End is used to indicate that the serving BSS will not longer send multiple reports for other reasons than the reception of a RAN-INFORMATION-REQUEST/Stop.

8c.1.3.3 RAN-INFORMATION-ACK PDU

The RAN-INFORMATION-ACK PDU is used by the controlling BSS to acknowledge the reception of a previous RAN-INFORMATION PDU if so requested by the serving BSS and is used by the serving BSS to acknowledge the reception of a previous RAN-INFORMATION-APPLICATION-ERROR PDU if so requested by the controlling BSS. The RAN-INFORMATION-ACK PDU is also used by the receiving BSS to acknowledge the reception of a previous RAN-INFORMATION PDU autonomously send by the originating BSS.

8c.1.3.4 RAN-INFORMATION-ERROR PDU

The RAN-INFORMATION-ERROR PDU is used, by either the controlling, the serving or the receiving BSS, to report an error diagnosed at the RIM protocol level to the peer entity.

8c.1.3.5 RAN-INFORMATION-APPLICATION-ERROR PDU

The RAN-INFORMATION-APPLICATION-ERROR PDU is used by the controlling or the receiving BSS to inform the peer application in the serving BSS about erroneous application information in a previously received RAN-INFORMATION PDU.

8c.1.4 RIM addressing and routing principles

8c.1.4.1 RIM routing address

8c.1.4.1.1 GERAN BSS identification

As there is no BSS address identifier defined as such in the 3GPP specifications, RIM makes use of the cell identifier (RAI + CI – see sub-clause 11.3.9 in the present document and 3GPP TS 23.003) of any cell parented by the BSS:

– the cell identifier of the source cell is used to identify the BSS issuing a RIM PDU;

– the cell identifier of the destination cell is used to identify the BSS towards which a RIM PDU is issued.

The source cell identifying the BSS issuing a RAN-INFORMATION-REQUEST PDU may be chosen arbitrarily within all the cells parented by the controlling BSS. The deletion or the re-parenting of any cell used as a source cell in the controlling BSS shall trigger the actions described in sub-clause 8c.5.2.

8c.1.4.1.2 UTRAN RNS identification

When RIM is used to support the exchange of information with a peer application entity located in UTRAN, the RNC identifier (see sub-clause 11.3.70) shall be used as the RIM Routing Address (Source Cell Identifier or Destination Cell Identifier) to identify the corresponding RNS.

8c.1.4.1.3 E-UTRAN eNodeB identification

When RIM is used to support the exchange of information with a peer application entity located in E-UTRAN, an eNB identifier (see sub-clause 11.3.70) shall be used as the RIM Routing Address (Source Cell Identifier or Destination Cell Identifier) to identify the corresponding eNodeB.

8c.1.4.1.4 eHRPD eAN identification

When RIM is used to support the exchange of information with a peer application entity located in eHRPD, an eHRPD Sector ID IE (see sub-clause 11.3.70) shall be used as the RIM Routing Address (Source Cell Identifier or Destination Cell Identifier) to identify the corresponding eHRPD eAN.

8c.1.4.2 Routing via the core network

The RIM PDUs shall be conveyed transparently by the core network toward the destination BSS, RNS, eNodeB or eHRPD eAN. A SGSN or MME shall use the destination address included in each RIM PDU either to send the PDU to the relevant BSS, RNS, eNodeB or eAN through the Gb, the Iu, the S1 or the S121 interface respectively, or to tunnel the PDU towards the target SGSN or MME parenting the destination node through the Gn or S3 interface respectively.

If a RIM PDU has been tunnelled through the Gn or S3 interface to a destination SGSN or MME that does not support RIM the PDU is discarded without further action.

8c.1.4.3 Address mirroring

The following address mirroring principles shall be applied:

– the serving BSS shall mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the received RAN-INFORMATION-REQUEST PDU into the Destination Cell Identifier IE and the Source Cell Identifier IE, respectively, of the related RAN-INFORMATION PDU(s);

– the controlling BSS shall mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION PDU to be acknowledged into the Destination Cell Identifier IE and the Source Cell Identifier IE, respectively, of the related RAN-INFORMATION-ACK PDU;

– the receiving BSS shall mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION PDU to be acknowledged into the Destination Cell Identifier IE and the Source Cell Identifier IE, respectively, of the related RAN-INFORMATION-ACK PDU;

– the BSS having identified an error at the RIM protocol level in a received RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU shall mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the erroneous PDU into the Destination Cell Identifier IE and the Source Cell Identifier IE, respectively, of the RAN-INFORMATION-ERROR PDU;

– the controlling BSS having identified an error at application level in a received PDU shall mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION PDU which carried the erroneous application information into the Destination Cell Identifier IE and the Source Cell Identifier IE, respectively, of the RAN-INFORMATION-APPLICATION-ERROR PDU.

8c.1.5 In-order delivery and reliable transfer – RSN

8c.1.5.1 General

A BSS shall allocate a RIM Sequence Number (RSN) to any RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION PDU or RAN-INFORMATION-APPLICATION-ERROR PDU sent by this BSS. The purpose of the RSN is twofold:

– to assess whether a RAN-INFORMATION-REQUEST PDU or a RAN-INFORMATION PDU received for a given RIM association is providing up-to-date information or is outdated if having been overtaken by a PDU received previously;

– to identify the PDU acknowledged with a RAN-INFORMATION-ACK PDU or reported in a RAN-INFORMATION-ERROR PDU.

For the purpose of comparing any RSN value to a given RSN X, the RSN numbering space is halved in two equal parts (see figure 8c.1) located on either sides of RSN X, the half part "below" RSN X (modulo RSN MAX+1) defining the RSN values "older" than RSN X, the half part "above" (modulo RSN MAX+1) RSN X defining the RSN values "newer" than RSN X.

Figure 8c.1: Comparing RSN values

8c.1.5.2 Allocating RSN values at the sending BSS

The RSN allocated to a RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION PDU or RAN-INFORMATION-APPLICATION-ERROR PDU shall be greater (modulo 2**32) than the RSN value allocated to the previous PDU of the same type sent for this association. In case a given PDU needs to be resent, this PDU may be re-issued with either the same RSN value or an increased RSN value (modulo 2**32).

NOTE: The RSN values allocated to two different PDUs sent successively for a given RIM association need not be consecutive (e.g. the RSN values could be uniquely allocated for a given application or within the whole BSS). However, in order to avoid RSN values depletion, the sending BSS should allocate the next higher RSN value (modulo 2**32) to the next PDU to be sent.

To allow a receiving entity to assess whether two PDUs are received in the same relative order they have been sent or not, the difference between the RSN values allocated to those two PDUs should not exceed an RSN window size of 2**31 (see sub-clause 8c.1.5.3).

NOTE: In order to cope with RSN values outside the RSN window for a given RIM association, the relevant RIM procedures might be triggered on a timely basis for advancing the RSN window.

8c.1.5.3 Comparing RSN values at the receiving BSS

Let PDU1 and PDU2 be two PDUs received at the BSS and related to the same RIM association, PDU1 is considered as having been sent earlier than PDU2 if the difference between the associated RSNs is less than an RSN window size of 2**31 (see sub-clause 8c.1.5.2), i.e.:

(RSN2 – RSN1) mod (2**32) < 2**31

8c.1.6 RIM Protocol Version Number

The RIM Protocol Version Number Information Element may be included in a RIM PDU. The RIM Protocol Version Number IE indicates which version of the RIM protocol is in use in the BSS having issued the PDU. If this Information Element is omitted, the behaviour of the receiving BSS should be the same as if the value of the RIM Protocol Version Number IE was "Version 1".

Only "Version 1" is defined in the present version of the specification.

In case the protocol version of the receiving BSS is lower than the version of the sending BSS, and unless otherwise specified in the present specification, the general rules of the BSSGP protocol apply and any unknown parameter shall be ignored.

8c.2 RIM procedures

8c.2.1 General

The RAN Information Request procedure is initiated by an application in the controlling BSS when it either requires information or wants to stop the transmission of information from a remote peer entity of the same application in the serving BSS. The application on the controlling side indicates the type of operation (Multiple Reports, Single Report, Stop) to the peer entity.

The RAN Information Send procedure is used to transfer application information between two entities of the same application in two BSSs via the core network.

The RAN Information Application Error procedure is initiated by an application in the controlling or receiving BSS to transfer application error information to the peer application entity of the same application in the serving BSS.

The RAN Information Error procedure is initiated by the RIM entity in the controlling, the serving or the receiving BSS to transfer error information to the RIM entity in the peer BSS.

8c.2.2 RAN Information Request procedure

8c.2.2.1 RAN Information Request/Single Report procedure

Figure 8c.2.2.1: RAN Information Request/Single Report Procedure

8c.2.2.1.1 Initiation by the controlling BSS

Upon initiation of the procedure, the controlling BSS shall:

1> set the content of the RAN-INFORMATION-REQUEST/Single Report PDU as follows:

2> set the PDU type IE, the Destination Cell Identifier IE and the Source Cell Identifier IE;

2> set the content of the RIM Container IE as follows:

3> set the RIM Application Identity IE and the RIM Sequence Number IE;

3> set the PDU Type Extension field in the RIM PDU Indications IE to "RAN-INFORMATION-REQUEST/Single Report";

3> set the RIM Protocol Version Number IE if necessary (see sub-clause 8c.1.6);

3> include the Application Container IE according to the requirements of the application;

1> send the RAN-INFORMATION-REQUEST/Single Report PDU;

1> start T(RIR);

8c.2.2.1.2 Reception of a valid RAN-INFORMATION-REQUEST/Single Report PDU by the serving BSS

Upon reception of a valid RAN-INFORMATION-REQUEST/Single Report PDU as defined in sub-clause 8c.3.2 the serving BSS shall:

1> set the content of the RAN-INFORMATION/Single Report PDU as follows:

2> set the PDU type IE; mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION-REQUEST/Single Report PDU respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION/Single Report PDU;

2> set the content of the RIM Container IE as follows:

3> set the RIM Application Identity IE as required by the application;

3> set the RIM Sequence Number IE and, if necessary, the RIM Protocol Version Number IE (see sub-clause 8c.1.6);

3> set the ACK indicator in the RIM PDU Indications IE to "No ACK requested";

3> set the PDU Type Extension field in the RIM PDU Indications IE to "RAN-INFORMATION/Single Report";

3> include either the RAN-INFORMATION Application Container IE or the Application Error Container IE according to the requirements of the application;

1> send the RAN-INFORMATION/Single Report PDU to the controlling BSS.

8c.2.2.1.3 Reception of a valid RAN-INFORMATION/Single Report PDU by the controlling BSS

Upon reception of a valid RAN-INFORMATION/Single Report PDU as defined in sub-clause 8c.3.2 the controlling BSS shall:

1> stop T(RIR) for this RIM association;

1> deliver the relevant information to the application;

and the procedure ends.

8c.2.2.1.4 Expiration of T(RIR) in the controlling BSS

If T(RIR) expires the controlling BSS shall as an implementation option either inform the application that the procedure has failed or restart the RAN Information Request/Single Report procedure a finite number of times as described in sub-clause 8c.2.2.1.1.

8c.2.2.2 RAN Information Request/Multiple Report procedure

Figure 8c.2.2.2: Successful RAN Information Request/Multiple Report Procedure

8c.2.2.2.1 Initiation by the controlling BSS

Upon initiation of the procedure, the controlling BSS shall:

1> set the content of the RAN-INFORMATION-REQUEST/Multiple Report PDU as follows:

2> set the PDU type IE, the Destination Cell Identifier IE and the Source Cell Identifier IE;

2> set the content of the RIM Container IE as follows:

3> set the RIM Application Identity IE and the RIM Sequence Number IE;

3> set the PDU Type Extension field in the RIM PDU Indications IE to "RAN-INFORMATION-REQUEST/Multiple Report";

3> set the RIM Protocol Version Number IE if necessary (see sub-clause 8c.1.6);

3> include the Application Container IE according to the requirements of the application;

1> send the RAN-INFORMATION-REQUEST/Multiple Report PDU;

1> Start T(RIR);

8c.2.2.2.2 Reception of a valid RAN-INFORMATION-REQUEST/Multiple Report PDU by the serving BSS

Upon reception of a valid RAN-INFORMATION-REQUEST/Multiple Report PDU as defined in sub-clauses 8c.3.2 the serving BSS shall:

1> if MULTIPLE_REPORTING_ONGOING is set to TRUE for this RIM association and if the received RAN-INFORMATION-REQUEST/Multiple Report PDU is considered as having been sent earlier (see sub-clause 8c.1.5) than the PDU whose RSN is stored in MULTIPLE_REPORT_SETTING_RSN, then:

2> discard the PDU without further actions and the procedure ends;

1> otherwise:

2> set the MULTIPLE_REPORTING_ONGOING variable to TRUE for this RIM association;

2> store the RIM Sequence Number IE value of the received PDU in the MULTIPLE_REPORT_SETTING_RSN variable;

2> set the content of the RAN-INFORMATION/Initial Multiple Report PDU as follows:

3> set the PDU type IE; mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION-REQUEST/Multiple Report PDU respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION/Initial Multiple Report PDU;

3> set the content of the RIM Container IE as follows:

4> set the RIM Application Identity IE as required by the application;

4> set the RIM Sequence Number IE and, if necessary, the RIM Protocol Version Number IE (see sub-clause 8c.1.6);

4> set the ACK indicator in the RIM PDU Indications IE to "No ACK requested";

4> set the PDU Type Extension field in the RIM PDU Indications IE to "RAN-INFORMATION/Initial Multiple Report";

4> include either the RAN-INFORMATION Application Container IE or the Application Error Container IE according to the requirements of the application;

2> send the RAN-INFORMATION/Initial Multiple Report PDU.

8c.2.2.2.3 Reception of a valid RAN-INFORMATION PDU/Initial Multiple Report PDU by the controlling BSS

Upon reception of a valid RAN-INFORMATION/Initial Multiple Report PDU as defined in sub-clause 8c.3.2 the controlling BSS shall:

1> stop T(RIR) for this RIM association;

1> deliver the relevant information to the application;

and the procedure ends.

8c.2.2.2.4 Expiration of T(RIR) in the controlling BSS

If T(RIR) expires the controlling BSS shall as an implementation option either inform the application that the procedure has failed or restart the RAN Information Request/Multiple Report procedure a finite number of times as described in sub-clause 8c.2.2.2.1.

8c.2.2.3 RAN Information Request/Stop procedure

Figure 8c.2.2.3: RAN Information Request/Stop Procedure

8c.2.2.3.1 Initiation by the controlling BSS

Upon initiation of the procedure, the controlling BSS shall:

1> set the content of the RAN-INFORMATION-REQUEST/Stop PDU as follows:

2> set the PDU type IE, the Destination Cell Identifier IE and the Source Cell Identifier IE;

2> set the content of the RIM Container IE as follows:

3> set the RIM Application Identity IE and the RIM Sequence Number IE;

3> set the PDU Type Extension field in the RIM PDU Indications IE to "RAN-INFORMATION-REQUEST/Stop";

3> set the RIM Protocol Version Number IE if necessary (see sub-clause 8c.1.6);

3> include the Application Container IE according to the requirements of the application;

1> send the RAN-INFORMATION-REQUEST/Stop PDU;

1> start T(RIR).

8c.2.2.3.2 Reception of a valid RAN-INFORMATION-REQUEST/Stop PDU by the serving BSS

Upon reception of a valid RAN-INFORMATION-REQUEST/Stop PDU as defined in sub-clause 8c.3.2, the serving BSS shall:

1> if MULTIPLE_REPORTING_ONGOING is set to TRUE for this RIM association and if the received RAN-INFORMATION-REQUEST/Stop PDU is considered as having been sent earlier (see sub-clause 8c.1.5) than the PDU whose RSN is stored in MULTIPLE_REPORT_SETTING_RSN, then:

2> discard the PDU without further actions and the procedure ends;

1> otherwise:

2> set the MULTIPLE_REPORTING_ONGOING variable to FALSE for this RIM association;

2> set the content of the RAN-INFORMATION/Stop as follows:

3> set the PDU type IE; mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION-REQUEST/Stop PDU respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION/Stop PDU;

3> set the content of the RIM Container IE as follows:

4> set the RIM Application Identity IE as required by the application;

4> set the RIM Sequence Number IE and, if necessary, the RIM Protocol Version Number IE (see sub-clause 8c.1.6);

4> set the ACK indicator in the RIM PDU Indications IE to "No ACK requested";

4> set the PDU Type Extension field in the RIM PDU Indications IE to "RAN-INFORMATION/Stop";

4> include either the Application Container IE or the Application Error Container IE according to the requirements of the application;

2> send the RAN-INFORMATION/Stop PDU.

8c.2.2.3.3 Reception of a valid RAN-INFORMATION/Stop PDU by the controlling BSS

Upon reception of a valid RAN-INFORMATION/Stop PDU as defined in sub-clause 8c.3.2 the controlling BSS shall:

1> stop T(RIR) for this RIM association;

1> deliver the relevant information to the application;

and the procedure ends.

8c.2.2.3.4 Expiration of T(RIR) in the controlling BSS

If T(RIR) expires the controlling BSS shall as an implementation option either inform the application that the procedure has failed or restart the RAN Information Request/Stop procedure a finite number of times as described in sub-clause 8c.2.2.3.1.

8c.2.3 RAN Information Send procedure

Fig 8c.2.3: Acknowledged RAN Information Send procedure

8c.2.3a Autonomous RAN Information Send procedure

Fig 8c.2.3: Acknowledged Autonomous RAN Information Send procedure

8c.2.3a.1 Initiation by the originating BSS

This RIM procedure is used for sending Multilateration Timing Advance related information from an originating BSS to a receiving BSS.

The autonomous RAN Information Send procedure is initiated by the application in the originating BSS when it realizes there is multilaration related information to be sent (using the RAN-INFORMATION/Single Report PDU) and it has not triggered the Multilateration Timing Advance procedure (see 3GPP TS 43.059 [23]).

Upon initiation of the procedure, the originating BSS shall:

1. set the content of the RAN-INFORMATION PDU as follows:

a. set the PDU type IE, the Source Cell Identifier IE value and the Destination Cell Identifier IE value where the Destination Cell Identifier IE corresponds to the 8 octet Source Identity IE (Cell Identity+Routing Area Identity) received in an uplink RLC data block as part of a Multilateration Timing Advance procedure (see 3GPP TS 44.060 [22];

b. set the content of the RIM Container IE as follows:

i set the RIM Application Identity IE and the RIM Sequence Number IE;

ii set the RIM Protocol Version Number IE if necessary (see sub-clause 8c.1.6)

iii set the PDU Type Extension field in the RIM PDU Indications IE to "RAN-INFORMATION/Single Report";

iv for a RAN-INFORMATION/Single Report PDU, set the ACK indicator to "ACK requested";

v set the Application Container IE according to the requirements of the Multilateration Timing Advance application (see sub-clause 11.3.63.2.6);

2. send the RAN-INFORMATION PDU;

3. if the ACK indicator has been set to "ACK requested", start a T(RI) instance for this RAN-INFORMATION PDU;

4. otherwise the procedure ends.

8c.2.3a.2 Reception of a valid RAN-INFORMATION PDU by the receiving BSS

Upon reception of a valid RAN-INFORMATION/Single Report the receiving BSS shall:

1. deliver the relevant information to the application;

a) if the ACK indicator in the RIM PDU Indications IE included in the RIM container of the RAN-INFORMATION PDU is set to "ACK requested", the receiving BSS shall:

2. set the content of the RAN-INFORMATION-ACK PDU as follows:

i set the PDU type IE; mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION PDU respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION-ACK PDU;

ii set the content of the RIM Container IE as follows:

ii.1 mirror the RIM Sequence Number IE value and the RIM Application Identity IE value included in the RIM container of the RAN-INFORMATION PDU respectively into the RIM Sequence Number IE and the RIM Application Identity IE of the RAN-INFORMATION-ACK PDU;

ii.2 set, if necessary, the RIM Protocol Version Number IE (see sub-clause 8c.1.6);

3. send the RAN-INFORMATION-ACK PDU.

b) otherwise, the procedure ends.

8c.2.3a.3 Reception of a valid RAN-INFORMATION-ACK PDU in the originating BSS

Upon reception of a valid RAN-INFORMATION-ACK PDU as defined in sub-clause 8c.3.2 the originating BSS shall:

1. if the RIM Sequence Number IE value contained in the RAN-INFORMATION-ACK PDU matches the RSN of the RAN-INFORMATION PDU having initiated the procedure then:

a) stop the T(RI) instance corresponding to the acknowledged PDU;

and the procedure ends.

8c.2.3a.4 Expiration of T(RI) in the originating BSS

Upon expiration of the T(RI) instance the originating BSS shall, as an implementation option, either inform the application that the procedure has failed or restart the RAN Information Send procedure a finite number of times as described in sub-clause 8c.2.3.1.

8c.2.3.1 Initiation by the serving BSS

If multiple reporting has been requested for a given RIM association (i.e. the MULTIPLE_REPORTING_ONGOING variable is set to TRUE), the RAN Information Send procedure is initiated by the application in the serving BSS either to send updated information (using the RAN-INFORMATION/Multiple Report PDU) or to indicate that multiple reporting has been deactivated on the serving BSS side (using the RAN-INFORMATION/End PDU).

Upon initiation of the procedure, the serving BSS shall:

1> set the content of the RAN-INFORMATION PDU as follows:

2> set the PDU type IE, mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION-REQUEST/Multiple Report PDU that is identified by the RSN stored in the MULTIPLE_REPORT_SETTING_RSN variable respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION PDU;

2> set the content of the RIM Container IE as follows:

3> mirror the RIM Application Identity IE value of the RAN-INFORMATION-REQUEST/Multiple Report PDU that is identified by the RSN stored in the MULTIPLE_REPORT_SETTING_RSN variable into the RIM Application Identity IE of the RAN-INFORMATION PDU;

3> set the RIM Sequence Number IE and, if necessary, the RIM Protocol Version Number IE (see sub-clause 8c.1.6);

3> set the PDU Type Extension field in the RIM PDU Indications IE to "RAN-INFORMATION/Multiple Report" or "RAN-INFORMATION/End" as required by the application;

3> for a RAN-INFORMATION/Multiple Report PDU, set the ACK indicator to the value required by the application; for a RAN-INFORMATION/End PDU, set the ACK indicator to "ACK requested";

3> set the Application Container IE according to the requirements of the application;

1> if the RAN-INFORMATION PDU is a RAN-INFORMATION/End (multiple reporting deactivated), set the MULTIPLE_REPORTING_ONGOING variable to FALSE;

1> send the RAN-INFORMATION PDU;

1> if the ACK indicator has been set to "ACK requested", start a T(RI) instance for this RAN-INFORMATION PDU;

1> otherwise the procedure ends.

8c.2.3.2 Reception of a valid RAN-INFORMATION PDU by the controlling BSS

Upon reception of a valid RAN-INFORMATION/Multiple Report or RAN-INFORMATION/End PDU as defined in sub-clause 8c.3.2 the controlling BSS shall:

1> deliver the relevant information to the application;

1> if the ACK indicator in the RIM PDU Indications IE included in the RIM container of the RAN-INFORMATION PDU is set to "ACK requested", the controlling BSS shall:

2> set the content of the RAN-INFORMATION-ACK PDU as follows:

3> set the PDU type IE; mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION PDU respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION-ACK PDU;

3> set the content of the RIM Container IE as follows:

4> mirror the RIM Sequence Number IE value and the RIM Application Identity IE value included in the RIM container of the RAN-INFORMATION PDU respectively into the RIM Sequence Number IE and the RIM Application Identity IE of the RAN-INFORMATION-ACK PDU;

4> set, if necessary, the RIM Protocol Version Number IE (see sub-clause 8c.1.6);

NOTE: If the RAN-INFORMATION PDU is a RAN-INFORMATION/End, the controlling BSS shall consider that multiple reporting is deactivated for this RIM association in the serving BSS.

2> send the RAN-INFORMATION-ACK PDU.

1> otherwise, the procedure ends.

8c.2.3.3 Reception of a valid RAN-INFORMATION-ACK PDU in the serving BSS

Upon reception of a valid RAN-INFORMATION-ACK PDU as defined in sub-clause 8c.3.2 the serving BSS shall:

1> if the RIM Sequence Number IE value contained in the RAN-INFORMATION-ACK PDU matches the RSN of the RAN-INFORMATION PDU having initiated the procedure then:

2> stop the T(RI) instance corresponding to the acknowledged PDU;

and the procedure ends.

8c.2.3.4 Expiration of T(RI) in the serving BSS

Upon expiration of the T(RI) instance the serving BSS shall, as an implementation option, either inform the application that the procedure has failed or restart the RAN Information Send procedure a finite number of times as described in sub-clause 8c.2.3.1.

8c.2.4 RAN Information Application Error procedure

Fig 8c.2.4: RAN Information Application Error procedure

8c.2.4.1 Initiation by the controlling or receiving BSS

Upon initiation of the procedure, the controlling/receiving BSS shall:

1. set the content of the RAN-INFORMATION-APPLICATION-ERROR PDU as follows:

a) set the PDU type IE, mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION PDU with the erroneous application container respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION-APPLICATION-ERROR PDU;

b) set the content of the RIM Container IE as follows:

i set the RIM Application Identity IE and the RIM Sequence Number IE;

ii set the RIM Protocol Version Number IE if necessary (see sub-clause 8c.1.6);

iii set the ACK indicator in the RIM PDU Indications IE according to the requirements of the application;

iv include the Application Error Container IE according to the requirements of the application

2. send the RAN-INFORMATION-APPLICATION-ERROR PDU to the serving/originating BSS;

3. if the ACK indicator has been set to "ACK requested", start a T(RIAE) instance for this RAN-INFORMATION-APPLICATION-ERROR PDU;

4. otherwise the procedure ends.

8c.2.4.2 Reception of a valid RAN-INFORMATION-APPLICATION-ERROR PDU by the serving BSS

Upon reception of a valid RAN-INFORMATION-APPLICATION-ERROR PDU as defined in sub-clause 8c.3.2 the serving BSS shall:

1> deliver the relevant information to the application;

1> if the ACK indicator in the RIM PDU Indications IE included in the RIM container of the RAN-INFORMATION-APPLICATION-ERROR PDU is set to "ACK requested", then the serving BSS shall:

2> set the content of the RAN-INFORMATION-ACK PDU as follows:

3> set the PDU type IE, mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the RAN-INFORMATION-APPLICATION-ERROR PDU respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION-ACK PDU;

3> set the content of the RIM Container IE as follows:

4> mirror the RIM Sequence Number IE value and the RIM Application Identity IE value included in the RIM container of the RAN-INFORMATION-APPLICATION-ERROR PDU respectively into the RIM Sequence Number IE and the RIM Application Identity IE of the RAN-INFORMATION-ACK PDU;

4> set the RIM Protocol Version Number IE if necessary (see sub-clause 8c.1.6);

2> send the RAN-INFORMATION-ACK PDU.

1> otherwise, the procedure ends.

8c.2.4.3 Reception of a valid RAN-INFORMATION-ACK PDU by the controlling or receiving BSS

Upon reception of a valid RAN-INFORMATION-ACK PDU as defined in sub-clause 8c.3.2, the controlling or receiving BSS shall:

1> if the RIM Sequence Number IE value contained in the RAN-INFORMATION-ACK PDU matches the RSN of the RAN-INFORMATION-APPLICATION-ERROR PDU having initiated the procedure

2> then stop the T(RIAE) instance corresponding to the acknowledged PDU;

1> else discard the PDU without further action;

and the procedure ends.

8c.2.4.4 Expiration of T(RIAE) in the controlling or receiving BSS

At the expiration of the T(RIAE) instance corresponding to the RAN-INFORMATION-APPLICATION-ERROR PDU sent previously by the controlling or receiving BSS, the controlling or receiving BSS shall, as an implementation option, either inform the application that the procedure has failed or restart the RAN Information Application Error procedure a finite number of times as described in sub-clause 8c.2.4.1.

8c.2.5 RAN Information Error procedure

Fig 8c.2.5: RAN Information Error procedure

The RAN Information Error procedure is initiated by the RIM in the source BSS (controlling originating, receiving or serving) to transfer error information to the RIM entity in the associated BSS.

The procedure is described in sub-clause 8c.3.4.

8c.3 Abnormal conditions

8c.3.0 General

Two levels of abnormal conditions are defined for the RIM function:

– the abnormal conditions encountered at the BSSGP level as described in sub-clause 8c.3.1, affecting the routing mechanisms and the related IEs in the RIM PDUs;

– the abnormal conditions encountered in the RIM container as described in sub-clauses 8c.3.2 and 8c.3.3.

The errors encountered in the application container are handled by the application and are made known to the peer application entity by including the Application Error container IE.

8c.3.1 Abnormal conditions at the BSSGP level

8c.3.1.1 General

The general protocol error handling as defined in section 9 applies.

However, the RIM containers being defined as general containers for passing field elements transparently between BSSs via the core network are not subject to error handling at the BSSGP level but only at the RIM protocol level (see sub-clause 8c.3.2).

Additionally the abnormal conditions defined in the following sub-clauses apply.

8c.3.1.2 RIM addressing error in BSS

If a BSS receives from an SGSN a RIM PDU with a Destination Cell Identifier IE value which does not match the cell identifier of any of its parented cells, the PDU shall be discarded and a STATUS PDU with the cause value set to "Unknown Destination address" shall be sent back to the SGSN.

8c.3.1.3 RIM addressing error in the CN

If an SGSN receives from a BSS a RIM PDU with an invalid destination address, the PDU shall be discarded and a STATUS PDU with the cause value set to "Unknown Destination address" shall be sent back to the BSS.

8c.3.1.4 RIM PDU addressed to a BSS not supporting RIM

If an SGSN receives a RIM PDU addressed to a parented BSS that does not support the RIM procedures, the PDU shall be discarded without further action.

8c.3.2 Abnormal conditions encountered in the RIM container

8c.3.2.1 Unknown RIM Application Identity

If the RIM container included in a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU contains an unknown value in the RIM Application Identity IE, or if the RIM container contains an unknown value in the SON Transfer Application Identity IE in case the RIM Application Identity IE is set to "SON Transfer", or if the RIM application is disabled when receiving a RAN-INFORMATION-REQUEST PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU with the RIM Cause IE set to "Unknown RIM Application Identity or RIM application disabled" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU.

If the RIM container included in a RAN-INFORMATION-ERROR PDU contains an unknown value in the RIM Application Identity IE, or if the RIM container contains an unknown value in the SON Transfer Application Identity IE in case the RIM Application Identity IE is set to "SON Transfer", the BSS shall discard the RIM PDU without further action.

8c.3.2.2 Erroneous PDU Type Extension field

If the PDU Type Extension field in the RIM PDU Indications IE included in the RIM container of a RAN-INFORMATION-REQUEST PDU does not indicate "RAN-INFORMATION-REQUEST/Multiple Report", "RAN-INFORMATION-REQUEST/Stop" or "RAN-INFORMATION-REQUEST/Single Report", the serving BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the RIM Cause IE set to "PDU not compatible with the feature set" back to the originating BSS (see sub-clause 8c.3.4.2) and shall discard the received PDU.

If the PDU Type Extension field in the RIM PDU Indications IE included in the RIM container of a RAN-INFORMATION PDU does not indicate "RAN-INFORMATION/Single Report", "RAN-INFORMATION/Multiple Report", "RAN-INFORMATION/Initial Multiple Report", "RAN-INFORMATION/Stop" or "RAN-INFORMATION/End", the serving BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the RIM Cause IE set to "PDU not compatible with the feature set" back to the originating BSS (see sub-clause 8c.3.4.2) and shall discard the received PDU.

8c.3.2.3 Missing conditional IE

If an expected conditional Information Element is not included in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the RIM Cause IE set to "Missing Conditional IE" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU.

If an expected conditional Information Element is not included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action.

8c.3.2.4 Missing mandatory IE

If a mandatory Information Element is not included in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the RIM Cause IE set to "Missing Mandatory IE" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU.

If a mandatory Information Element is not included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action.

8c.3.2.5 Syntactical error in an expected conditional IE

If a syntactical error is detected in an expected conditional Information Element included in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the RIM Cause IE set to "Conditional IE error" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU.

If a syntactical error is detected in an expected conditional Information Element included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action.

8c.3.2.6 Syntactical error in a mandatory IE

If a syntactical error is detected in a mandatory IE included in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the RIM Cause IE set to "Invalid mandatory information" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU.

For this rule the following exceptions apply:

– unknown RIM Application Identity IE (see sub-clause 8c.3.2.1); or

– erroneous PDU Type Extension field (see sub-clause 8c.3.2.2)

If a syntactical error is detected in a mandatory IE included in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action.

8c.3.2.7 Unexpected conditional IE

If an unexpected conditional Information Element is received in the RIM container of a RAN-INFORMATION PDU, RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION-ACK PDU or RAN-INFORMATION-APPLICATION-ERROR PDU, the BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the RIM Cause IE set to "Unexpected Conditional IE" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU.

If an unexpected conditional Information Element is received in the RIM container of a RAN-INFORMATION-ERROR PDU, the BSS shall discard the received PDU without further action.

8c.3.2.8 Containers with out-of-sequence information elements

The receiving BSS may accept RIM containers that include information elements that do not appear to be in the correct sequence. Elements that occur more than once in a RIM container shall be assumed to have been transmitted in the correct order. Recipients that do not accept out of sequence information elements shall regard the RIM container as containing unexpected and/or missing information elements and follow the procedures defined in the rest of this sub-clause 8c.3.2.

8c.3.2.9 Container with semantically incorrect content

When any IE with semantically incorrect contents is received within a RIM container, the receiving BSS shall react according to the relevant protocol specification. If however no such reactions are specified, the receiving BSS shall ignore that IE and treat the rest of the RIM container. If the rest of the RIM container can no longer be handled because this IE was ignored then the receiving BSS shall send a RAN-INFORMATION-ERROR PDU containing the complete received PDU and with the RIM Cause IE set to "Semantically incorrect PDU" back to the originating BSS (see sub-clause 8c.3.4.2) and discard the received PDU.

8c.3.3 Unexpected RIM PDU

If a BSS receives a RIM PDU in a case not covered by the RIM procedures specified in sub-clause 8c.2, it shall discard the RIM PDU without further action.

8c.3.4 RIM error reporting

8c.3.4.1 General

A BSS diagnosing any of the abnormal cases identified in sub-clause 8c.3.2 in a received RIM PDU shall inform the originating BSS by sending in return a RAN-INFORMATION-ERROR PDU as described in sub-clause 8c.3.4.2.

The tasks to be performed upon reception of the RAN-INFORMATION-ERROR PDU are described in sub-clause 8c.3.4.3.

8c.3.4.2 Sending of a RAN-INFORMATION-ERROR PDU

A BSS receiving an erroneous RIM PDU according to sub-clause 8c.3.2 shall:

1> set the PDU type IE, mirror the Source Cell Identifier IE value and the Destination Cell Identifier IE value of the erroneous RIM PDU respectively into the Destination Cell Identifier IE and the Source Cell Identifier IE of the RAN-INFORMATION-ERROR PDU

1> set the content of RIM Container IE as follows:

2> mirror the RIM Application Identity IE value of the erroneous RIM PDU into the RIM Application Identity IE in the RIM Container IE of the RAN-INFORMATION-ERROR PDU;

2> set the RIM Cause IE and, if necessary, the RIM Protocol Version Number IE (see sub-clause 8c.1.6);

2> include the complete erroneous RIM PDU in to the PDU in Error IE;

1> send the RAN-INFORMATION-ERROR PDU.

8c.3.4.3 Reception of a RAN-INFORMATION-ERROR PDU in the BSS

Upon reception of an erroneous RAN-INFORMATION-ERROR PDU according to sub-clause 8c.3.2 the BSS shall discard the received PDU without further action.

The actions to be taken upon reception of a valid RAN-INFORMATION-ERROR PDU are an implementation-dependent option.

8c.4 RIM timers

The following RIM timers are defined:

T(RIR) is used in the controlling BSS to control the reception of the response to a previously transmitted RAN-INFORMATION-REQUEST PDU.

T(RI) is used in the serving BSS used to control the reception of the acknowledgement of a previously transmitted RAN-INFORMATION PDU.

T(RIAE) is used in the controlling BSS used to control the reception of the acknowledgement of a previously transmitted RAN-INFORMATION-APPLICATION-ERROR PDU.

Table 8c.4: RIM timers

Timer	Start	Stop	Action at expiry
T(RIR)	Transmission of a RAN-INFORMATION-REQUEST/Multiple Report PDU	Reception of the answering RAN-INFORMATION/Initial Multiple Report	Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times
	Transmission of a RAN-INFORMATION-REQUEST/Single Report PDU	Reception of the answering RAN-INFORMATION/Single Report	Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times
	Transmission of a RAN-INFORMATION-REQUEST/Stop PDU	Reception of the answering RAN-INFORMATION/Stop	Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times
T(RI)	Transmission of a RAN-INFORMATION/Multiple Report, RAN-INFORMATION/Single Report or RAN-INFORMATION/End PDU	Reception of the answering RAN-INFORMATION-ACK	Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times
T(RIAE)	Transmission of a RAN-INFORMATION-APPLICATION-ERROR PDU	Reception of the answering RAN-INFORMATION-ACK	Either (implementation option) inform the application that the procedure has failed or restart the procedure a finite number of times

8c.5 Action upon deletion of a cell in a BSS

8c.5.0 General

The deletion of a cell in a BSS should trigger the actions described in this sub-clause to ensure the proper operation of the RIM procedures for RIM associations related to this cell.

8c.5.1 Actions due to the deletion of the cell

If the deleted cell has to report to one or more controlling BSS(s), the serving BSS parenting the deleted cell shall trigger a RAN Information Send procedure to inform each of the corresponding controlling BSS(s) that multiple reporting has been deactivated by the sending of a RAN-INFORMATION/End PDU.

The controlling BSS parenting the deleted cell may also decide that, as a consequence of the deletion of this cell, some multiple reports previously requested from some cells parented by other BSS(s) are no longer needed and shall trigger the relevant RAN Information Request/Stop procedure.

8c.5.2 Additional actions in the case the deleted cell is used as a source cell by RIM

If the cell identifier of the cell being deleted has been used as the Source Cell Identifier IE value in a previous RAN-INFORMATION-REQUEST/Multiple report PDU, the deletion of this cell shall trigger the following additional actions to update this information in the serving BSS, as the Source Cell Identifier IE is used by the serving BSS to address the controlling BSS (address mirroring – see sub-clause 8c.1.4.3):

– The controlling BSS parenting this cell shall trigger a RAN Information Request/Stop procedure for each of the involved cells in the serving BSS;

– After the completion of this procedure the parenting BSS shall, if event-based multiple reporting is still needed from the involved cells, trigger further RAN Information Request/Multiple Report procedure(s) with a different cell identifier as Source Cell Identifier IE value.

8c.6 Specific requirements related to RIM applications

8c.6.0 General requirements

Any error condition detected in the Application Error Container IE included in the RIM Container IE of a valid RIM PDU shall not be reported to the peer application entity.

Any error condition detected in the Application Container IE included in the RIM Container IE of an erroneous RIM PDU shall not trigger a RAN Information Application Error procedure.

A controlling BSS shall not send another RAN-INFORMATION-REQUEST PDU for the same association before the first RAN-INFORMATION-REQUEST PDU has been acknowledged or before T(RIR) associated to this request has expired.

8c.6.1 Requirements related to the NACC RIM application

The rules specified in this sub-clause apply when the RIM Application Identity IE is set to "Network Assisted Cell Change (NACC)":

– The RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to request the system information required for NACC operation in the controlling BSS and related to a single cell parented by a serving BSS. The Destination Cell Identifier IE of the RAN-INFORMATION-REQUEST PDU shall be set to the value of the Reporting Cell Identifier field contained in the application container of the PDU.

– The presence of the Application Container IE is mandatory in the RIM Container IE of the RAN-INFORMATION-REQUEST PDU.

– The RAN-INFORMATION PDU is used by a serving BSS to send the system information required for NACC operation (i.e. if a PBCCH is allocated in the cell, PSI1, a consistent set of PSI2 and PSI14 messages; if no PBCCH is allocated in the cell, SI3, SI13 and, if available, SI1 messages – see 3GPP TS 4.060) related to a single reporting cell, to a controlling BSS.

– In the present specification, NACC between UTRAN and GERAN is restricted to the case of a controlling RNS and a serving BSS (i.e. assistance is provided for MSs moving from UTRAN to GERAN) and NACC between E-UTRAN and GERAN is restricted to the case of a controlling eNodeB and a serving BSS (i.e. assistance is provided for MSs moving from E-UTRAN to GERAN). The reporting cell located in the serving BSS is therefore always a GERAN cell and shall be addressed as such (RAI + CI) in the NACC application containers.

– The presence of the Application Container IE is mandatory in the RIM Container IE of the RAN-INFORMATION PDU, except in the case of a RAN-INFORMATION/Initial Multiple Report PDU and of a RAN-INFORMATION/Single Report PDU, where the Application Error Container IE may be included instead.

– When multiple reports from a certain cell have been requested, the RAN-Information Send procedure shall be triggered every time the set of NACC related (packet) system information for this cell is changed; the NACC application shall request acknowledgements.

– The Application Container IE included in the RIM container IE of a RAN-INFORMATION/End PDU or of a RAN-INFORMATION/Stop PDU shall contain only the identity of the reporting cell.

8c.6.2 SI3 application

The rules specified in this sub-clause apply when the RIM Application Identity IE is set to "SI3":

– the RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to request system information type 3 related to a single cell parented by a serving BSS. The Destination Cell Identifier IE of the RAN-INFORMATION-REQUEST PDU shall be set to the value of the Reporting Cell Identifier field contained in the application container of the PDU.

– The presence of the Application Container IE is mandatory in the RIM Container IE of the RAN-INFORMATION-REQUEST PDU.

– The RAN-INFORMATION PDU is used by a serving BSS to send system information type 3 related to a single reporting cell, to a controlling BSS.

– When multiple reports from a certain cell have been requested, the RAN-Information Send procedure shall be triggered every time the system information type 3 for this cell is changed; the SI3 application shall request acknowledgements.

– The Application Container IE included in the RIM container IE of a RAN-INFORMATION/End PDU or of a RAN-INFORMATION/Stop PDU shall contain only the identity of the reporting cell.

8c.6.3 MBMS data channel application

The rules specified in this sub-clause apply when the RIM Application Identity IE is set to "MBMS data channel":

– The RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to request the information about the MBMS data channels established in a single cell controlled by a serving BSS. The Destination Cell Identifier IE of the RAN-INFORMATION-REQUEST PDU shall be set to the value of the Reporting Cell Identifier field contained in the application container of the PDU.

– The presence of the Application Container IE is mandatory in the RIM Container IE of the RAN-INFORMATION-REQUEST PDU.

– The RAN-INFORMATION PDU is used by a serving BSS to send the information about the MBMS data channels established in a single reporting cell, to a controlling BSS.

– When multiple reports from a certain cell have been requested, the RAN-Information Send procedure shall be triggered every time the allocation of the MBMS data channel is changed (i.e. established, reconfigured, abnormally released) for any MBMS session ongoing in the reporting cell. The MBMS data channel application shall request acknowledgements. However the normal release (i.e. resulting from a MBMS-SESSION-STOP-REQUEST PDU received from the SGSN) of the MBMS data channel at the end of a session shall not trigger the RAN-Information Send procedure, but assumed implicitly as done at the end of the session by the the controlling BSS.

– The Application Container IE included in the RIM container IE of a RAN-INFORMATION/End PDU or of a RAN-INFORMATION/Stop PDU shall contain only the identity of the reporting cell.

8c.6.4 Requirements related to the SON Transfer RIM application

The introduction of generic SON Transfer containers in TS 36.413 [36] means that the RIM procedure itself has to be understood in a more generic way for the SON Transfer RIM application: the RIM procedure triggered by the Controlling BSS is used to exchange between BSSs SON Transfer Request container (controlling —> serving) and SON Transfer Response container (serving —> controlling), the precise content of these containers (possibly NULL) being linked with the SON Transfer Application in use.The Reporting Cell Identifier may either identify a cell in the serving BSS or in the controlling BSS, depending on the value of the SON Transfer Application Identity as specified in TS 36.413 [36].

The rules specified in this sub-clause apply when the RIM Application Identity IE is set to "SON Transfer":

– The RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to send the SON Transfer Request container to the serving BSS as specified in TS 36.413 [36].

– The procedure shall be triggered using single report or multiple reports.

– The RAN-INFORMATION PDU is used by a serving BSS to send the SON Transfer Response Container to a controlling BSS as specified in TS 36.413 [36].

– When multiple reports have been requested, the RAN-Information Send procedure shall be triggered every time a SON Transfer Response Container must be sent. The RAN-Information Send procedure shall be used with lower priority with respect to the MS/UE dedicated signalling.

8c.6.5 Requirements related to the UTRA SI RIM application

The rules specified in this sub-clause apply when the RIM Application Identity IE is set to "UTRA System Information (UTRA SI)":

– The RAN-INFORMATION-REQUEST PDU is used by a controlling BSS to request the UTRA system information in the controlling BSS and related to a cell parented by a serving BSS.

– The presence of the Application Container IE is mandatory in the RIM Container IE of the RAN-INFORMATION-REQUEST PDU.

– The RAN-INFORMATION PDU is used by a serving BSS to send the UTRA system information related to a cell, to a controlling BSS.

– In the present specification, UTRA SI is transferred only to E-UTRAN. The reporting cell located in the serving BSS is always a cell and shall be addressed by the UTRAN Source Cell ID in the UTRA SI application containers.

– When multiple reports from a certain cell have been requested, the RAN-Information Send procedure shall be triggered every time the set of UTRA system information managed by the UTRA SI RIM application for this cell is changed; the UTRA SI application shall request acknowledgements.

– The Application Container IE included in the RIM container IE of a RAN-INFORMATION/End PDU or of a RAN-INFORMATION/Stop PDU shall contain only the identity of the reporting cell.

8c.6.6 Multilateration Timing Advance application

The rules specified in this sub-clause apply when the RIM Application Identity IE is set to "Multilateration Timing Advance":

– The RAN-INFORMATION PDU is used by an originating BSS to send information related to an ongoing Multilaration Timing Advance procedure (see 3GPP TS 43.059 [23]), to a receiving BSS.

– The presence of the Application Container IE is mandatory in the RIM Container IE of the RAN-INFORMATION PDU, except in the case of a RAN-INFORMATION/Single Report PDU, where the Application Error Container IE applicable to the Multilateration Timing Advance Application (see sub-clause 11.3.64.6) may be included instead.

– When included, the contents of the Application Container IE is set according to the requirements of the Multilateration Timing Advance application as described in sub-clause 11.3.63.2.6.