Content for  TS 25.469  Word version:  18.0.0

Top   Top   None   None   Next
1…   8…


1  Scopep. 7

The present document specifies the Home Node B Application Part (HNBAP) 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 control and management procedures between HNB and HNB-GW.

2  Referencesp. 7

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]  Void
TS 25.467: "UTRAN architecture for 3G Home Node B"
TS 23.032: "Universal Geographical Area Description (GAD)".
TR 25.921: (Version 7.0.0) "Guidelines and Principles for Protocol Description and Error Handling".
TR 21.905: "Vocabulary for 3GPP Specifications".
ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".
ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation".
ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation One (ASN.1): Information object specification".
TS 25.331: "Radio Resource Control (RRC) Protocol Specification"
RFC 4960  (2007-09): "Stream Control Transmission Protocol".
TS 23.003: "Numbering, addressing and identification".
RFC 4282  (2005-12): "The Network Access Identifier".
Broadband Forum TR-069 Amendment 2, CPE WAN Management Protocol, Broadband Forum Technical Report, 2007.
TS 22.220: "Service requirements for Home Node Bs and Home eNode Bs".

3  Definitions and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following terms and definitions apply:
Elementary Procedure:
HNBAP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the HNB and HNB-GW. These EPs are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand-alone procedures, which can be active in parallel.
An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used:
  • Class 1: Elementary Procedures with response (success or failure).
  • Class 2: Elementary Procedures without response.
For Class 1 EPs, the types of responses can be as follows:
  • A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response.
  • A signalling message explicitly indicates that the EP failed.
  • On time supervision expiry (i.e. absence of expected response).
Class 2 EPs are considered always successful.
RNSAP Relocation:
see definition in TS 25.467.

3.2  Abbreviationsp. 8

For the purposes of the present document, the abbreviations given in TR 21.905 and the following abbreviations apply:
Elementary Procedure
Electronic Serial Number
Home Node B
Home Node B Gateway
HNB Application Part
Protocol Data Unit
Packed Encoding Rules
Service Area Code

4  Generalp. 8

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

4.1  Procedure Specification Principlesp. 8

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 Compatibilityp. 9

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 Notationsp. 9

For the purposes of the present document, the following notations apply:
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.
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. HNB REGISTRATION REQUEST 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  HNBAP Servicesp. 9

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

6  Services expected from the Transport layerp. 9

Following service is expected from the transport layer:
  • reliable and in sequence delivery of HNBAP messages. HNBAP shall be notified if the signalling connection breaks.

7  Functions of HNBAPp. 10

The HNBAP has the following functions:
  • HNB Registration
  • UE Registration
  • Support RNSAP relocation (TS 25.467)
  • 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 HNBAP elementary procedures described in the following clauses.

Up   Top   ToC