Content for TS 25.468 Word version: 16.0.0

3.1 Definitions 3.2 Abbreviations 4.1 Procedure specification principles 4.2 Forwards and backwards compatibility 4.3 Specification notations
...

1 Scope Word‑p. 6

The present document specifies the RANAP User Adaption (RUA) between the Home Node B (HNB) and the Home Node B Gateway (HNB-GW). It fulfils the HNB- HNB-GW communication requirements specified in TS 25.467 and is defined over the Iuh - reference point. It provides transparent transport for RANAP messages.

2 References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1] Void

[2]

TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".

[3]

TS 25.467: "UTRAN architecture for 3G Home NodeB; Stage 2".

[4]

TR 25.921: (version.7.0.0) "Guidelines and principles for protocol description and error handling".

[5]

TR 21.905: "Vocabulary for 3GPP Specifications".

[6]

ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".

[7]

ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".

[8]

ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification".

[9]

RFC 4960 (2007-09): "Stream Control Transmission Protocol".

3 Definitions and abbreviations

3.1 Definitions

For the purposes of the present document, the following terms and definitions below apply. Terms and definitions not defined below can be found in TR 21.905.

UE-associated Signalling Connection:

UE-associated Signalling Connection is a logical connection between HNB and HNB-GW associated to an Iu signalling connection for a particular UE over the single signalling connection between the HNB and HNB-GW, identified by the identities Context ID and CN Domain ID.

3.2 Abbreviations

For the purposes of the present document, the following abbreviations apply:

Core Network

Elementary Procedure

HNB

Home Node B

HNB-GW

Home Node B Gateway

PDU

Protocol Data Unit

RUA

RANAP User Adaption

SCTP

Stream Control Transmission Protocol

4 General Word‑p. 7

The protocol described in the present document is the protocol between HNB-GW and HNB.

4.1 Procedure specification principles

The principle for specifying the procedure logic is to specify the functional behaviour of the HNB & HNB-GW exactly and completely..

The following specification principles have been applied for the procedure text in clause 8:

The procedure text discriminates between:
1. Functionality which "shall" be executed:
  - The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
2. Functionality which "shall, if supported" be executed:
  - The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included.

4.2 Forwards and backwards compatibility

The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.

4.3 Specification notations

For the purposes of the present document, the following notations apply:

Procedure

When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. HNB Registration procedure.

Message

When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. CONNECT message.

When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. HNB Identity IE.

Value of an IE

When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)" or "Background ".

5 RUA services Word‑p. 8

RUA provides the signalling service between the HNB and the HNB-GW that is required to fulfil the RUA functions described in Clause 7.

6 Services expected from the transport layer

Following service is expected from the transport layer:

reliable and in sequence delivery of Signalling data using SCTP (IETF RFC 4960 [9])

7 Functions of RUA

The RUA has the following functions:

Transparent transfer of RANAP messages
Error Handling. This function allows the reporting of general error situations, for which function specific error messages have not been defined.

These functions are implemented by one or several RUA elementary procedures described in the following clauses.