7.3.2 Usage of the services provided by RNSAP User Adaptation Layer (RNA)

25.4673GPPRelease 17Stage 2TSUTRAN architecture for 3G Home Node B (HNB)

7.3.2.1 General

This section describes usage of RNA for Iurh connectivity between HNBs.

RNA supports the transport of any RNSAP signalling messages between HNBs.

RNA provides a connection-oriented data transfer service and a connectionless data transfer service.

A signalling connection established by means of RNA is denoted by a single Context Id, which is unique within both involved nodes (see TS 25.471 [19] for further details).

RNA supports direct Iurh-connectivity and Iurh-connectivity via the HNB-GW.

7.3.2.2 Iurh Signalling Connection Establishment

7.3.2.2.1 Direct Iurh connectivity

Figure 7.3.2.2.1-1: Signalling Connection Establishment – Direct Iurh-connectivity.

If the Sending HNB wants to send an RNSAP message to the Receiving HNB for which a dedicated Iurh signalling connection has to be established, it issues an RNA:CONNECT message containing the Iurh Context Id, the RNSAP PDU, the Senders HNB RNL Identity and the Receivers HNB RNL Identity. The Reception of the RNA:CONNECT message at the Receiving HNB completes the signalling connection establishment.

7.3.2.2.2 Iurh signalling connection establishment via the HNB-GW

Figure 7.3.2.2.2-1: Signalling Connection Establishment – Iurh connection via HNB-GW.

1. If the Sending HNB is configured for Iurh-connectivity via the HNB-GW, and wants to send an RNSAP message to the Receiving HNB for which a signalling connection has to be established, it issues an RNA:CONNECT message containing the Iurh Context Id, the RNSAP PDU, the Senders HNB RNL Identity and the Receivers HNB RNL Identity.

2. The HNB-GW identifies the signalling interface to which the RNA message shall be routed by Receivers HNB RNL Identity as received from the Sending HNB.

3. The HNB-GW issues an RNA:CONNECT message with identical content as received from the Sending HNB to the Receiving HNB.

4. Reception of the RNA:CONNECT message by the Receiving HNB completes the signalling connection establishment for the Receiving HNB.

7.3.2.3 Transport of RNSAP signalling messages via an established Iurh signalling connection

7.3.2.3.1 Direct Iurh connectivity

Figure 7.3.2.3.1-1: Transport of RNSAP messages via an established Iurh signalling connection – Direct Iurh connectivity.

If Sending HNB, directly Iurh connected to the Receiving HNB, wants to send an RNSAP message to Receiving HNB for which a connection oriented data transfer service is already established, it issues an RNA:DIRECT TRANSFER message to the Receiving HNB which contains the Iurh Context Id, the RNSAP PDU and the Receivers HNB RNL Identity.

7.3.2.3.2 Iurh connectivity via the HNB-GW

Figure 7.3.2.3.2-1: Transport of RNSAP messages via an established Iurh signalling connection – Iurh connectivity via the HNB-GW.

If the Sending HNB, Iurh connected to the Receiving HNB via the HNB-GW, wants to send an RNSAP messages via the established signalling connection, it issues an RNA:DIRECT TRANSFER message to the HNB-GW, providing the Receivers HNB RNL Identity which enables the HNB-GW to route the RNSAP message to the Receiving HNB.

7.3.2.4 Release of a Signalling Connection

7.3.2.4.1 Direct Iurh connectivity

Figure 7.3.2.4.1-1: Release of an Iurh signalling connection – Direct Iurh-connectivity.

If the Sending HNB, directly Iurh-connected to the Receiving HNB, wants to release an established signalling connection towards the Receiving HNB, it sends an RNA:DISCONNECT message, which includes the Iurh Context Id and the Receivers HNB RNL Identity and may include an RNSAP PDU. Reception of the DISCONNECT message by the Receiving HNB completes the release of the Iurh signalling connection.

7.3.2.4.2 Iurh connectivity via the HNB-GW

Figure 7.3.2.4.2-1: Release of an Iurh signalling connection – Iurh connectivity via the HNB-GW.

If the Sending HNB, Iurh connected to the Receiving HNB via the HNB-GW, wants to release the signalling connection towards Receiving HNB, it sends an RNA:DISCONNECT message, which includes the Iurh Context Id and the Receivers HNB RNL Identity and may include an RNSAP PDU. The HNB-GW routes the DISCONNECT message based on the Receivers HNB RNL Identity. Reception of the DISCONNECT message by Receiving HNB completes the release of the signalling connection.

7.3.2.5 Transport of RNSAP signalling messages via the connectionless data transfer service

7.3.2.5.1 Direct Iurh connectivity

Figure 7.3.2.5.1-1: Connectionless data transfer – Direct Iurh-connectivity.

If the Sending HNB wants to send an RNSAP PDU to the Receiving HNB, for which no Iurh signalling connection is necessary, it issues an RNA:CONNECTIONLESS TRANSFER message containing the RNSAP PDU, the Senders HNB RNL Identity and the Receivers HNB RNL Identity.

7.3.2.5.2 Iurh connectivity via the HNB-GW

Figure 7.3.2.5.2-1: Connectionless data transfer – Iurh connectivity via the HNB-GW.

If the Sending HNB wants to send an RNSAP PDU to the Receiving HNB, for which an Iurh signalling connection is not necessary, it issues an RNA:CONNECTIONLESS TRANSFER message containing the RNSAP PDU, the Senders and the Receivers HNB RNL Identities to the HNB-GW, which routes the RNA message based on the Receivers HNB RNL Identity. The Receiving HNB is able to identify the sending HNB by the Senders HNB RNL Identity.