TSG-RAN Working Group 3 meeting #3 TSGR3#3(99)359

Kawasaki 26th to 30th April 1999

Agenda Item: 10.2 Iu Signalling (RANAP) (S3.13)

Source: NEC

Title: Parameters with regard to the RANAP SRNS Relocation

Document for: Decision

___________________________________________________________________________
[1] I3.01 v0.1.0 UTRAN Functions, Examples on Signalling Procedures
[2] S3.13 v0.1.0 RANAP Specification

1.Abstract
This contribution is to propose the RANAP message parameters with regard to the SRNS Relocation
procedure.
The explanation of each parameter is shown below.
2.Discussion
The ANNEX shows the RANAP messages and parameters related to SRNS RELOCATION procedure.

2.1 contents in the RANAP message related to the SRNS Relocation procedure

RELOCATION REQUIRE message:

>Common ID: This parameter is used as a common ID (e.g. IMSI). The CN transfer the Common ID to
the target RNC in the Relocation Request message.
>C-RNTI: This parameter is the information that has been informed from target RNC to the serving RNC
in the RNSAP Uplink Transfer message. The CN transfer the C-RNTI in the Relocation Request message
to the target RNC.
>Target RNC Signalling Address: This parameter shows the target RNC signalling address to enable
the CN to route to the target RNC.
>RRC Information: This parameter is transparent field. The CN transfer this parameter in the Relocation
Request message. This parameter includes Cipher key, Cipher Algorithm, UE Capability for RAN.
>SGSN Signalling Address: This parameter shows the target SGSN Signalling Address. If the target
SGSN Signalling Address is same as the current SGSN signalling address, this parameter can be ignored
in the CN.

RELOCATION REQUEST message:

>Common ID: This parameter is received at the CN in RELOCATION REQUIRE message. The CN
transfer the Common ID to the target RNC.
>C-RNTI: This parameter is received at the CN in RELOCATION REQUIRE message. The CN transfer
the C-RNTI to the target RNC.
>RRC Information: This parameter is received at the CN in RELOCATION REQUIRE message. The CN
transfer the RRC Information to the target RNC.
>Number of Bearer: This parameter shows the number of the Bearer that should be established across
the new Iu interface.

1/4
>Bearer ID(s): This parameter shows the Bearer ID(s) of the bearer(s) that should be established across
the new Iu interface
>Information Transfer Capability: This parameter shows the transfer capability for the CS call. The
necessity of this information is FFS.
>Quality of Service: This parameters shows the capability for the PS call. This information can be used
as mapping to data transport bearer.
>ATM Address: This parameter shows the ATM address of the sending node i.e. the CN.
>ATM Binding ID(s): This parameter shows the Binding ID in order to associate to the ALCAP protocol.

RELOCATION PROCEEDING 1 message:

This message has no parameters except message header information (message type etc.).

RELOCATION PROCEEDING 2 message:

This message has no parameters except message header information (message type etc.).

3. Proposal
It is proposed to incorporate the chapter 2.1 of this contribution in the chapter 8.1 of the RANAP
Specification (S3.13), and also incorporate the ANNEX of this contribution into appropriate chapter of the
RANAP Specification (S3.13).

2/4
ANNEX

9.1.1.19 RELOCATION REQUIRED

The RELOCATION REQUIRED message is sent from the RNC to the CN to inform that the RNC requires
relocating the serving RNC functionality to other RNC.
The message is sent via the SCCP connection associated with the dedicated resource(s).
INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN
Message Identifier RNC-CN M
Length RNC-CN M
Message Compatibility Information RNC-CN M
User IdCommon ID RNC-CN M (1)
CRNTI RNC-CN M
Target RNC Signaling Address RNC-CN M(2)
RRC Information RNC-CN M(3)
SGSN Signalling address RNC-CN M

1. This element includes TMUI The Common ID is transferred to the Target RNC in CN
2. This parameter shows target RNC Signaling Address.
3. This parameter is transparent field, and it includes Cipher key, Cipher Algorithm, UE Capability
for RAN.

9.1.1.20 RELOCATION REQUEST

The RELOCATION REQUEST message is sent from the RNC to the CN to inform that the RNC requires
relocating the serving RNC functionality to other RNC.
The message is sent via the SCCP connection associated with the dedicated resource(s).
INFORMATION ELEMENT REFERENCE DIRECTION TYPE LEN
Message Identifier CN-RNC M
Length CN-RNC M
Message Compatibility Information CN-RNC M
User IDCommon ID CN-RNC M (1)
C-RNTI CN-RNC M (2)
RRC Information CN-RNC M (3)
Number of Bearer ID CN-RNC M
Bearer ID(s). CN-RNC M
User Information Rate CN-RNC M
Information Transfer Capability CN-RNC M (4)
Quality of Service CN-RNC M (5)
ATM address CN-RNC M (26)
ATM Binding ID(s) CN-RNC M

1.This element includes TMUI. Formatados: Marcadores e numerao

2.This element is used for ATM address, may be included the AAL2 address or If Iu interface use
AAL type1 or type5, it should be included ATM address.

3/4
 1. The Common ID is transferred to the Target RNC in CN
2. This parameter shows C-RNTI
3. This element is transparent field, and it includes Cipher key, Cipher Algorithm, UE Capability for
RAN.
4. Information Transfer Capability shows the capability for CS call The necessity of this parameter is
FFS.
5. Quality of Service shows the capability of for PS call. This information can be used as mapping to
the data transport bearer
6. This element is used for ATM address, may be included the AAL2 address or If Iu interface use
AAL type1 or type5, it should be included ATM address.

9.1.1.xx RELOCATION PROCEEDING1

The RELOCATION PROCEEDING1 is sent from the RNC to the CN to inform the target RNC has
prepared for the relocation.
The message is sent via the SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT REFERENC DIRECTION TYPE LEN

E
Message Identifier CN-RNC M
Length CN-RNC M
Compatibility Information CN-RNC M

9.1.1.xx RELOCATION PROCEEDING2

The RELOCATION PROCEEDING2 is sent from the CN to the RNC to inform the Serving RNC
indicates that the completion of the preparation at the CN side for the SRNS relocation.
The message is sent via the SCCP connection associated with the dedicated resource(s).

INFORMATION ELEMENT REFERENC DIRECTION TYPE LEN

E
Message Identifier CN-RNC M
Length CN-RNC M
Compatibility Information CN-RNC M

4/4