1、 ETSI TS 125 468 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); UTRAN Iuh Interface RANAP User Adaption (RUA) signalling (3GPP TS 25.468 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 125 468 V14.0.0 (2017-04)13GPP TS 25.468 version 14.0.0 Release 14Reference R
2、TS/TSGR-0325468ve00 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 (06) N 7803/88 Important notice The present d
3、ocument 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 the prior written authorization of ETSI. In
4、 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 present document should be aware that the do
5、cument 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 comment to one of the following services: https:
6、/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. The content of the PDF version shall not be m
7、odified 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 Trade Marks of ETSI registered for the benef
8、it 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 468 V14.0.0 (2017-04)23GPP TS 25.468 version 14.0.0 Release
9、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 found in ETSI SR 000 314: “Intellectual Proper
10、ty 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 searc
11、hes, 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 Technical Specification (TS) has been produce
12、d 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 ETSI deliverables. The cross reference betwe
13、en 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 to be interpreted as described in clause 3.2
14、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 468 V14.0.0 (2017-04)33GPP TS 25.468 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword
15、 . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 General . 7g34.1 Procedure specification principles 7g34.2 Forwards and backwards compatibility 7g34.3 Specification notations . 7g35 RUA service
16、s 8g36 Services expected from the transport layer 8g37 Functions of RUA 8g38 RUA procedures . 8g38.1 Elementary Procedures . 8g38.2 Connect 8g38.2.1 General 8g38.2.2 Successful Operation 9g38.2.2.1 HNB Originated 9g38.2.2.2 HNB-GW Originated 9g38.3 Direct Transfer . 10g38.3.1 General 10g38.3.2 Succe
17、ssful Operation (HNB-GW Originated) 10g38.3.3 Successful Operation (HNB Originated) 10g38.3.4 Abnormal Conditions 10g38.4 Disconnect 10g38.4.1 General 10g38.4.2 Successful Operation (HNB Originated) 11g38.4.3 Successful Operation (HNB-GW Originated) 11g38.4.4 Abnormal Conditions 11g38.5 Connectionle
18、ss Transfer . 11g38.5.1 General 11g38.5.2 Successful Operation (HNB-GW Originated) 11g38.5.3 Successful Operation (HNB Originated) 12g38.5.4 Abnormal Conditions 12g38.6 Error Indication 12g38.6.1 General 12g38.6.2 Successful Operation 12g39 Elements for RUA communication 13g39.1 Message functional d
19、efinition and content . 13g39.1.1 General 13g39.1.2 Message contents 13g39.1.2.1 Presence 13g39.1.2.2 Criticality 13g39.1.2.3 Range 13g39.1.2.4 Assigned Criticality . 13g39.1.3 CONNECT . 14g39.1.4 DIRECT TRANSFER. 14g3ETSI ETSI TS 125 468 V14.0.0 (2017-04)43GPP TS 25.468 version 14.0.0 Release 149.1
20、.5 DISCONNECT . 14g39.1.6 CONNECTIONLESS TRANSFER 14g39.1.7 ERROR INDICATION . 15g39.2 Information Element Definitions 15g39.2.0 General 15g39.2.1 Message Type . 15g39.2.2 Context ID 15g39.2.3 Establishment Cause . 16g39.2.4 Intra Domain NAS Node Selector 16g39.2.5 RANAP Message 18g39.2.6 CN Domain
21、Indicator 18g39.2.7 Cause 18g39.2.8 Criticality Diagnostics 20g39.2.9 CSG Membership Status . 21g39.3 Message and Information Element Abstract Syntax (with ASN.1) 22g39.3.0 General 22g39.3.1 Usage of private message mechanism for non-standard use . 22g39.3.2 Elementary Procedure Definitions 22g39.3.
22、3 PDU definitions 26g39.3.4 Information Element definitions . 29g39.3.5 Common definitions . 33g39.3.6 Constant definitions 34g39.3.7 Container definitions. 35g39.4 Message transfer syntax . 39g310 Handling of unknown, unforeseen, and erroneous protocol data . 40g310.1 General . 40g310.2 Transfer Sy
23、ntax Error . 40g310.3 Abstract Syntax Error . 40g310.3.1 General 40g310.3.2 Criticality Information 41g310.3.3 Presence Information 41g310.3.4 Not comprehended IE/IE group 42g310.3.4.1 Procedure Code . 42g310.3.4.1A Type of Message . 42g310.3.4.2 IEs other than the Procedure Code and Type of Message
24、 . 42g310.3.5 Missing IE or IE group . 43g310.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present 44g310.4 Logical Error 45g310.5 Exceptions 45g3Annex A (informative): Change History 46g3History 47g3ETSI ETSI TS 125 468 V14.0.0 (2017-04)53GPP TS 25.468 ve
25、rsion 14.0.0 Release 14Foreword This Technical Specification (TS) 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
26、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 u
27、nder 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 ETSI TS 125 468 V14.0.0 (2017-04)63GPP TS 25.468 vers
28、ion 14.0.0 Release 141 Scope 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 3 and is defined over the Iuh reference point. It provides transp
29、arent 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.
30、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 th
31、e present document. 1 Void 2 3GPP TS 25.413: “UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling“. 3 3GPP TS 25.467: “UTRAN architecture for 3G Home NodeB; Stage 2“. 4 3GPP TR 25.921 (version.7.0.0): “Guidelines and principles for protocol description and error handling“. 5
32、3GPP 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): Specifi
33、cation of basic notation“. 8 ITU-T Recommendation X.681 (2002-07): “Information technology - Abstract Syntax Notation One (ASN.1): Information object specification“. 9 IETF RFC 4960 (2007-09): “Stream Control Transmission Protocol“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of
34、 the present document, the following terms and definitions below apply. Terms and definitions not defined below can be found in TR 21.905 5. UE-associated Signalling Connection: UE-associated Signalling Connection is a logical connection between HNB and HNB-GW associated to an Iu signalling connecti
35、on 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: ETSI ETSI TS 125 468 V14.0.0 (2017-04)73GPP TS 25.468 vers
36、ion 14.0.0 Release 14CN Core Network EP 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 The protocol described in the present document is the protocol between HNB-GW and HNB. 4.1 Proced
37、ure specification principles The principle for specifying the procedure logic is to specify the functional behaviour of the HNB Elementary procedures Elementary Procedure Message Connect CONNECTDirect Transfer DIRECT TRANSFER Disconnect DISCONNECTConnectionless Transfer CONNECTIONLESS TRANSFER Error
38、 Indication ERROR INDICATION 8.2 Connect 8.2.1 General The HNB or HNB-GW can initiate this procedure to establish an UE-associated Signalling Connection and carry a RANAP message. ETSI ETSI TS 125 468 V14.0.0 (2017-04)93GPP TS 25.468 version 14.0.0 Release 148.2.2 Successful Operation 8.2.2.1 HNB Or
39、iginated HNB-GW HNB CONNECT Figure 1: Connect to HNB-GW procedure This procedure is used to carry the first RANAP message from the HNB to the HNB-GW. Additional information is provided to enable the HNB-GW to handle the RANAP message without it being necessary to inspect the contents and trigger the
40、 establishment of a new UE-associated Signalling Connection between HNB and HNB-GW, which is directly mapped to the Iu Signalling Connection the RANAP message refers to. If HNB receives the Intra Domain NAS Node Selector IE in the RRC message, the HNB shall, if supported, include the Intra Domain NA
41、S Node Selector IE in the CONNECT message. NOTE: The Context ID is used as the Iu Signalling Connection identifier in the corresponding RANAP messages. 8.2.2.2 HNB-GW Originated HNB-GW CONNECT HNB Figure 1A: Connect to HNB procedure This procedure is used to carry the first RANAP message from the HN
42、B-GW to an HNB for a particular UE, e.g. RANAP RELOCATION REQUEST. This shall trigger the establishment of a new UE-associated Signalling Connection between HNB-GW and HNB, which is directly mapped to the Iu Signalling Connection the RANAP message refers to. The HNB-GW allocates the context id. If t
43、he first RANAP message received by the HNB GW is a RELOCATION REQUEST message and the RELOCATION REQUEST does not contain the CSG ID of the target cell the RUA CONNECT message may contain the CSG Membership Status IE. Additional information is provided by the HNB-GW to the HNB to assist the HNB in h
44、andling the RANAP message. ETSI ETSI TS 125 468 V14.0.0 (2017-04)103GPP TS 25.468 version 14.0.0 Release 148.3 Direct Transfer 8.3.1 General This procedure is initiated by either the HNB or HNB-GW to transport a RANAP message between the two nodes. The HNB-GW can initiate this procedure to establish
45、 an UE-associated Signalling Connection when carrying the second RANAP RELOCATION REQUEST message. 8.3.2 Successful Operation (HNB-GW Originated) HNB-GW DIRECT TRANSFER HNB Figure 2: Direct Transfer to HNB This procedure is used to carry any DL connection-oriented RANAP message defined in TS 25.413
46、2 from the HNB-GW to the HNB. This procedure can be used to carry the second RANAP RELOCATION REQUEST message from the HNB-GW to an HNB for a particular UE. This shall trigger the establishment of a second UE-associated Signalling Connection between HNB-GW and HNB, which is directly mapped to the Iu
47、 Signalling Connection the RANAP message refers to. 8.3.3 Successful Operation (HNB Originated) HNB-GW DIRECT TRANSFER HNB Figure 3: Direct Transfer to HNB-GW This procedure is used to carry any UL connection-oriented RANAP message defined in TS 25.413 2, except those carried in CONNECT or DISCONNEC
48、T messages, from the HNB to the HNB-GW. 8.3.4 Abnormal Conditions - 8.4 Disconnect 8.4.1 General This procedure is initiated by either the HNB or the HNB-GW to terminate an UE-associated Signalling Connection between these nodes. ETSI ETSI TS 125 468 V14.0.0 (2017-04)113GPP TS 25.468 version 14.0.0
49、Release 148.4.2 Successful Operation (HNB Originated) HNB-GW DISCONNECT HNB Figure 4: Disconnect to HNB-GW This procedure is used to carry the last RANAP (TS 25.413 2) UL connection-oriented message of a given Iu Signalling Connection to the HNB-GW over the Iuh interface. This procedure may also be used to indicate error conditions at the HNB. 8.4.3 Successful Operation (HNB-GW Originated) HNB-GW DISCONNECT HNB Figure 5: Disconnect to HNB This procedure is initiated by the HNB-GW to close a given Iu Signalling Connection either in case of e
