1、 ETSI TS 125 471 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); UTRAN Iurh interface Radio Network Subsystem Application Part (RNSAP) User Adaption (RNA) signalling (3GPP TS 25.471 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 125 471 V14.0.0 (2017-04)13GPP TS
2、 25.471 version 14.0.0 Release 14Reference RTS/TSGR-0325471ve00 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 enregistre la Sous-Prfecture de Grasse (
3、06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search 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
4、 the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the
5、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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comm
6、ent to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx 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. T
7、he 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. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are
8、Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 125 471 V14.0.0 (201
9、7-04)23GPP TS 25.471 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document 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 fo
10、und 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 P
11、olicy, 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. Foreword This T
12、echnical 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, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding
13、ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are t
14、o 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 ETSI TS 125 471 V14.0.0 (2017-04)33GPP TS 25.471 version 14.0.0 Release 14Conte
15、nts Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 General . 8g34.1 Procedure Specification Principles . 8g34.2 Forwards and Backwards Compatibility 9g3
16、4.3 Specification Notations 9g35 RNA Services . 9g35.1 General . 9g35.2 Parallel Transactions 9g36 Services expected from the Transport layer . 9g37 Functions of RNA 9g38 RNA Procedures . 10g38.1 Elementary Procedures . 10g38.2 Iurh Setup . 10g38.2.1 General 10g38.2.2 Direct Iurh connection 10g38.2.
17、2.1 Successful operation 10g38.2.2.2 Unsuccessful operation . 11g38.2.2.3 Abnormal Conditions 11g38.2.3 Iurh connection via the HNB-GW 11g38.2.3.1 Successful Operation HNB Originated . 11g38.2.3.2 Unsuccessful Operation HNB Originated . 12g38.2.3.3 Abnormal Conditions HNB originated. 12g38.2.3.4 Suc
18、cessful Operation HNB-GW Originated . 12g38.2.3.5 Unsuccessful Operation HNB-GW Originated . 12g38.3 Connect 13g38.3.1 General 13g38.3.2 Successful Operation 13g38.3.2.1 HNB Originated Direct Iurh connection 13g38.3.2.2 HNB Originated Iurh connection via the HNB-GW 13g38.3.2.3 HNB-GW Originated Iurh
19、 connection via the HNB-GW 14g38.4 Direct Transfer . 14g38.4.1 General 14g38.4.2 Successful Operation 14g38.4.2.1 HNB Originated Direct Iurh connection 14g38.4.2.2 HNB Originated Iurh connection via the HNB-GW 14g38.4.2.3 HNB-GW Originated Iurh connection via the HNB-GW 15g38.5 Disconnect 15g38.5.1
20、General 15g38.5.2 Successful Operation 15g38.5.2.1 HNB Originated Direct Iurh connection 15g38.5.2.2 HNB Originated Iurh connection via the HNB-GW 15g38.5.2.3 HNB-GW Originated Iurh connection via the HNB-GW 16g38.6 Connectionless Transfer . 16g3ETSI ETSI TS 125 471 V14.0.0 (2017-04)43GPP TS 25.471
21、version 14.0.0 Release 148.6.1 General 16g38.6.2 Successful Operation 16g38.6.2.1 HNB Originated Direct Iurh connection 16g38.6.2.2 HNB Originated Iurh connection via the HNB-GW 17g38.6.2.3 HNB-GW Originated Iurh connection via the HNB-GW 17g38.7 Error Indication 17g38.7.1 General 17g38.7.2 Successf
22、ul Operation 18g38.7.2.1 Direct Iurh Connection 18g38.7.2.2 Iurh Connection via the HNB-GW 18g39 Elements for RNA Communication . 19g39.1 Message Functional Definition and Content 19g39.1.1 General 19g39.1.2 Message Contents . 19g39.1.2.1 Presence 19g39.1.2.2 Criticality 19g39.1.2.3 Range 19g39.1.2.
23、4 Assigned Criticality . 19g39.1.3 IURH SETUP REQUEST 20g39.1.4 IURH SETUP RESPONSE 20g39.1.5 IURH SETUP FAILURE 20g39.1.6 CONNECT . 21g39.1.7 DIRECT TRANSFER. 21g39.1.8 DISCONNECT . 21g39.1.9 CONNECTIONLESS TRANSFER 22g39.1.10 ERROR INDICATION . 22g39.2 Information Element Definitions 22g39.2.0 Gen
24、eral 22g39.2.1 Message Type . 23g39.2.2 Cause 23g39.2.3 Criticality Diagnostics 24g39.2.4 RNSAP Message 25g39.2.5 Iurh Signalling Context ID . 25g39.2.6 PLMN-ID 26g39.2.7 Cell-ID 26g39.2.8 Backoff Timer . 26g39.2.9 HNB RNL Identity . 26g39.2.10 HNB Cell Identifier 26g39.2.11 Global RNC ID . 27g39.3
25、Message and Information Element Abstract Syntax (with ASN.1) 27g39.3.0 General 27g39.3.1 Usage of protocol extension mechanism for non-standard use . 27g39.3.2 Elementary Procedure Definitions 28g39.3.3 PDU Definitions . 31g39.3.4 Information Element Definitions 36g39.3.5 Common Definitions. 40g39.3
26、.6 Constant Definitions . 41g39.3.7 Container Definitions 42g39.4 Message Transfer Syntax . 46g310 Handling of Unknown, Unforeseen or Erroneous Protocol Data . 46g310.1 General . 46g310.2 Transfer Syntax Error . 46g310.3 Abstract Syntax Error . 46g310.3.1 General 46g310.3.2 Criticality Information 4
27、7g310.3.3 Presence Information 47g310.3.4 Not comprehended IE/IE group 48g310.3.4.1 Procedure Code . 48g310.3.4.1A Type of Message . 48g310.3.4.2 IEs other than the Procedure Code and Type of Message . 48g3ETSI ETSI TS 125 471 V14.0.0 (2017-04)53GPP TS 25.471 version 14.0.0 Release 1410.3.5 Missing
28、IE or IE group . 49g310.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present 50g310.4 Logical Error 51g310.5 Exceptions 51g3Annex A (informative): Change history . 52g3History 53g3ETSI ETSI TS 125 471 V14.0.0 (2017-04)63GPP TS 25.471 version 14.0.0 Release
29、 14Foreword This Technical Specification has been produced by the 3rdGeneration 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
30、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 th
31、e 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 ETSI TS 125 471 V14.0.0 (2017-04)73GPP TS 25.471 version 14.0.0 Release 141 Sc
32、ope 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 connect
33、ion-oriented and connectionless mode and an Iurh setup function. 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
34、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
35、 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
36、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 S
37、yntax 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 Definit
38、ions 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 con
39、sists 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 ETSI ETSI TS 125 471 V14.0.0 (2017-04)83GPP TS 25.471 version 14.0.0 Release 14sequences in a flexible manner. If the
40、 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 pos
41、sibly 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: Successful - A signalling message explicitly indicates that the elem
42、entary 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
43、 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
44、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 t
45、o 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 claus
46、e 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
47、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. ETSI ETSI TS 125 471 V14.0.0 (2017-04)93GPP TS 25.471 version 14.0.0 Release 142) Functionality which “shall, if su
48、pported“ 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,
49、 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 o
