|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
UTRAN Iurh interface Radio Network Subsystem Application
Part (RNSAP) User Adaption (RNA) signalling
(3GPP TS 25.471 version 16.0.0 Release 16)
---------------------- Page: 1 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 1 ETSI TS 125 471 V16.0.0 (2020-08)
Reference
RTS/TSGR-0325471vg00
Keywords
UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 2 ETSI TS 125 471 V16.0.0 (2020-08)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under .
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 3 ETSI TS 125 471 V16.0.0 (2020-08)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 8
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 9
4 General . 9
4.1 Procedure Specification Principles . 9
4.2 Forwards and Backwards Compatibility . 10
4.3 Specification Notations . 10
5 RNA Services . 10
5.1 General . 10
5.2 Parallel Transactions . 10
6 Services expected from the Transport layer . 10
7 Functions of RNA . 10
8 RNA Procedures . 11
8.1 Elementary Procedures . 11
8.2 Iurh Setup . 11
8.2.1 General . 11
8.2.2 Direct Iurh connection . 11
8.2.2.1 Successful operation. 11
8.2.2.2 Unsuccessful operation . 11
8.2.2.3 Abnormal Conditions . 12
8.2.3 Iurh connection via the HNB-GW . 12
8.2.3.1 Successful Operation HNB Originated . 12
8.2.3.2 Unsuccessful Operation HNB Originated . 13
8.2.3.3 Abnormal Conditions – HNB originated. 13
8.2.3.4 Successful Operation HNB-GW Originated . 13
8.2.3.5 Unsuccessful Operation HNB-GW Originated . 13
8.3 Connect . 14
8.3.1 General . 14
8.3.2 Successful Operation . 14
8.3.2.1 HNB Originated – Direct Iurh connection . 14
8.3.2.2 HNB Originated – Iurh connection via the HNB-GW . 14
8.3.2.3 HNB-GW Originated – Iurh connection via the HNB-GW . 15
8.4 Direct Transfer . 15
8.4.1 General . 15
8.4.2 Successful Operation . 15
8.4.2.1 HNB Originated – Direct Iurh connection . 15
8.4.2.2 HNB Originated – Iurh connection via the HNB-GW . 15
8.4.2.3 HNB-GW Originated – Iurh connection via the HNB-GW . 16
8.5 Disconnect . 16
8.5.1 General . 16
8.5.2 Successful Operation . 16
8.5.2.1 HNB Originated – Direct Iurh connection . 16
8.5.2.2 HNB Originated – Iurh connection via the HNB-GW . 16
8.5.2.3 HNB-GW Originated – Iurh connection via the HNB-GW . 17
8.6 Connectionless Transfer . 17
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 4 ETSI TS 125 471 V16.0.0 (2020-08)
8.6.1 General . 17
8.6.2 Successful Operation . 17
8.6.2.1 HNB Originated – Direct Iurh connection . 17
8.6.2.2 HNB Originated – Iurh connection via the HNB-GW . 18
8.6.2.3 HNB-GW Originated – Iurh connection via the HNB-GW . 18
8.7 Error Indication . 18
8.7.1 General . 18
8.7.2 Successful Operation . 19
8.7.2.1 Direct Iurh Connection . 19
8.7.2.2 Iurh Connection via the HNB-GW . 19
9 Elements for RNA Communication . 20
9.1 Message Functional Definition and Content . 20
9.1.1 General . 20
9.1.2 Message Contents . 20
9.1.2.1 Presence . 20
9.1.2.2 Criticality . 20
9.1.2.3 Range . 20
9.1.2.4 Assigned Criticality . 20
9.1.3 IURH SETUP REQUEST . 21
9.1.4 IURH SETUP RESPONSE . 21
9.1.5 IURH SETUP FAILURE . 21
9.1.6 CONNECT . 22
9.1.7 DIRECT TRANSFER. 22
9.1.8 DISCONNECT . 22
9.1.9 CONNECTIONLESS TRANSFER . 23
9.1.10 ERROR INDICATION . 23
9.2 Information Element Definitions . 23
9.2.0 General . 23
9.2.1 Message Type . 24
9.2.2 Cause . 24
9.2.3 Criticality Diagnostics . 25
9.2.4 RNSAP Message . 26
9.2.5 Iurh Signalling Context ID . 26
9.2.6 PLMN-ID . 27
9.2.7 Cell-ID . 27
9.2.8 Backoff Timer . 27
9.2.9 HNB RNL Identity . 27
9.2.10 HNB Cell Identifier . 27
9.2.11 Global RNC ID . 28
9.3 Message and Information Element Abstract Syntax (with ASN.1) . 28
9.3.0 General . 28
9.3.1 Usage of protocol extension mechanism for non-standard use . 28
9.3.2 Elementary Procedure Definitions . 29
9.3.3 PDU Definitions . 32
9.3.4 Information Element Definitions . 37
9.3.5 Common Definitions. 41
9.3.6 Constant Definitions . 42
9.3.7 Container Definitions . 43
9.4 Message Transfer Syntax . 47
10 Handling of Unknown, Unforeseen or Erroneous Protocol Data . 47
10.1 General . 47
10.2 Transfer Syntax Error . 47
10.3 Abstract Syntax Error . 47
10.3.1 General . 47
10.3.2 Criticality Information . 48
10.3.3 Presence Information . 48
10.3.4 Not comprehended IE/IE group . 49
10.3.4.1 Procedure Code . 49
10.3.4.1A Type of Message . 49
10.3.4.2 IEs other than the Procedure Code and Type of Message . 49
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 5 ETSI TS 125 471 V16.0.0 (2020-08)
10.3.5 Missing IE or IE group . 50
10.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present . 51
10.4 Logical Error . 52
10.5 Exceptions . 52
Annex A (informative): Change history . 53
History . 54
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 6 ETSI TS 125 471 V16.0.0 (2020-08)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 7 ETSI TS 125 471 V16.0.0 (2020-08)
1 Scope
The present document specifies the RNSAP User Adaption (RNA) supporting Iurh-connectivity between HNBs as
specified in TS 25.467 [3] by adapting the services made available by the Iurh signalling transport layer to the needs of
RNSAP. It provides transparent transport for RNSAP messages in connection-oriented and connectionless mode and an
Iurh setup function.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 8 ETSI TS 125 471 V16.0.0 (2020-08)
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] Void
[3] 3GPP TS 25.467: "UTRAN architecture for 3G Home NodeB"
[4] 3GPP TS 25.423: "UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP)
signalling"
[5] 3GPP TR 25.921 (version.7.0.0): "Guidelines and Principles for Protocol Description and Error
Handling".
[6] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[7] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules:
Specification of Packed Encoding Rules (PER)".
[8] ITU-T Recommendation X.680 (2002-07): "Information technology - Abstract Syntax Notation
One (ASN.1): Specification of basic notation".
[9] ITU-T Recommendation X.681 (2002-07): "Information technology - Abstract Syntax Notation
One (ASN.1): Information object specification".
[10] Void
[11] Void
[12] 3GPP TS 25.331: "Radio Resource Control (RRC) Protocol Specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [6] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [6].
Elementary Procedure: RNA consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of
interaction between HNBs. 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.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 25.471 version 16.0.0 Release 16 9 ETSI TS 125 471 V16.0.0 (2020-08)
For Class 1 EPs, the types of responses can be as follows:
Successful
- A signalling message explicitly indicates that the elementary procedure successfully completed with the
receipt of the response.
Unsuccessful
- 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.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [6] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [6].
EP Elementary Procedure
HNB Home Node B
PDU Protocol Data Unit
RNA RNSAP User Adaption
RNS Radio Network Subsystem
RNSAP Radio Network Subsystem Application Part
SCTP Stream Control Transmission Protocol
4 General
The protocol described in the present document is the protocol between Iurh-connected HNBs providing adaptation of
services of the Iurh signalling transport layer to the needs of RNSAP and an Iurh setup function.
4.1 Procedure Specification Principles
The principle for specifying the procedure logic is to specify the functional behaviour of the HNBs 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
...