1、 ETSI TS 125 471 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); UTRAN Iurh interface Radio Network Subsystem Application Part (RNSAP) User Adaption (RNA) signalling (3GPP TS 25.471 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 125 471 V15.0.0 (2018-07)13GPP TS
2、 25.471 version 15.0.0 Release 15Reference RTS/TSGR-0325471vf00 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benef
8、it of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 125 471 V
9、15.0.0 (2018-07)23GPP TS 25.471 version 15.0.0 Release 15Intellectual 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
10、 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.or
11、g/). 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 pr
12、esent 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 an
13、d/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. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The
14、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 ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
15、 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 to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expressi
16、on of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 125 471 V15.0.0 (2018-07)33GPP TS 25.471 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g
17、32 References 8g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 9g34 General . 9g34.1 Procedure Specification Principles . 9g34.2 Forwards and Backwards Compatibility 10g34.3 Specification Notations 10g35 RNA Services . 10g35.1 General . 10g35.2 Parallel Transactions 10g
18、36 Services expected from the Transport layer . 10g37 Functions of RNA 10g38 RNA Procedures . 11g38.1 Elementary Procedures . 11g38.2 Iurh Setup . 11g38.2.1 General 11g38.2.2 Direct Iurh connection 11g38.2.2.1 Successful operation 11g38.2.2.2 Unsuccessful operation . 11g38.2.2.3 Abnormal Conditions
19、12g38.2.3 Iurh connection via the HNB-GW 12g38.2.3.1 Successful Operation HNB Originated . 12g38.2.3.2 Unsuccessful Operation HNB Originated . 12g38.2.3.3 Abnormal Conditions HNB originated. 13g38.2.3.4 Successful Operation HNB-GW Originated . 13g38.2.3.5 Unsuccessful Operation HNB-GW Originated . 1
20、3g38.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 14g38.3.2.3 HNB-GW Originated Iurh connection via the HNB-GW 14g38.4 Direct Transfer . 14g38.4.1 General 14g38.4.2 Successful Op
21、eration 15g38.4.2.1 HNB Originated Direct Iurh connection 15g38.4.2.2 HNB Originated Iurh connection via the HNB-GW 15g38.4.2.3 HNB-GW Originated Iurh connection via the HNB-GW 15g38.5 Disconnect 15g38.5.1 General 15g38.5.2 Successful Operation 16g38.5.2.1 HNB Originated Direct Iurh connection 16g38
22、.5.2.2 HNB Originated Iurh connection via the HNB-GW 16g38.5.2.3 HNB-GW Originated Iurh connection via the HNB-GW 16g38.6 Connectionless Transfer . 16g38.6.1 General 16g3ETSI ETSI TS 125 471 V15.0.0 (2018-07)43GPP TS 25.471 version 15.0.0 Release 158.6.2 Successful Operation 17g38.6.2.1 HNB Originat
23、ed Direct Iurh connection 17g38.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 Successful Operation 18g38.7.2.1 Direct Iurh Connection 18g38.7.2.2 Iurh Connection via the HNB-GW 18g
24、39 Elements for RNA Communication . 18g39.1 Message Functional Definition and Content 18g39.1.1 General 18g39.1.2 Message Contents . 19g39.1.2.1 Presence 19g39.1.2.2 Criticality 19g39.1.2.3 Range 19g39.1.2.4 Assigned Criticality . 19g39.1.3 IURH SETUP REQUEST 20g39.1.4 IURH SETUP RESPONSE 20g39.1.5
25、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 General 22g39.2.1 Message Type . 23g39.2.2 Cause 23g39.2.3 Criticality Diagnostics 24g39.2.4 RNSA
26、P Message 25g39.2.5 Iurh Signalling Context ID . 25g39.2.6 PLMN-ID 25g39.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 Message and Information Element Abstract Syntax (with ASN.1) 27g39.3.0 General 27g39.3.1 Usage
27、 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.6 Constant Definitions . 41g39.3.7 Container Definitions 42g39.4 Message Transfer Syntax . 46
28、g310 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 47g310.3.3 Presence Information 47g310.3.4 Not comprehended IE/IE group 48g310.3.4.1 Procedure
29、Code . 48g310.3.4.1A Type of Message . 48g310.3.4.2 IEs other than the Procedure Code and Type of Message . 48g310.3.5 Missing IE or IE group . 49g3ETSI ETSI TS 125 471 V15.0.0 (2018-07)53GPP TS 25.471 version 15.0.0 Release 1510.3.6 IEs or IE groups received in wrong order or with too many occurren
30、ces or erroneously present 50g310.4 Logical Error 51g310.5 Exceptions 51g3Annex A (informative): Change history . 52g3History 53g3ETSI ETSI TS 125 471 V15.0.0 (2018-07)63GPP TS 25.471 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Pr
31、oject (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 v
32、ersion 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, corre
33、ctions, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 471 V15.0.0 (2018-07)73GPP TS 25.471 version 15.0.0 Release 151 Scope The present document specifies the RNSAP User Adaption (RNA) supporting Iurh-connectivity
34、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 ETSI TS 125 471 V15.0.0
35、(2018-07)83GPP TS 25.471 version 15.0.0 Release 152 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.) o
36、r 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 th
37、e 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
38、 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
39、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 abbrev
40、iations 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 Elemen
41、tary 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 descriptio
42、n. 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 res
43、ponse (success or failure). - Class 2: Elementary Procedures without response. For Class 1 EPs, the types of responses can be as follows: ETSI ETSI TS 125 471 V15.0.0 (2018-07)93GPP TS 25.471 version 15.0.0 Release 15Successful - A signalling message explicitly indicates that the elementary procedur
44、e 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 do
45、cument, 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 Ra
46、dio 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
47、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 proc
48、edure 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
49、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 informi
