1、 ETSI TS 125 468 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); UTRAN Iuh Interface RANAP User Adaption (RUA) signalling (3GPP TS 25.468 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 125 468 V15.0.0 (2018-07)13GPP TS 25.468 version 15.0.0 Release 15Reference R
2、TS/TSGR-0325468vf00 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trade
8、marks 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 468 V15.0.0 (2018-07)23GPP TS 25.468 version 15.0
9、.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 and non-members, and can be found in ETSI S
10、R 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 inv
11、estigation, 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 docum
12、ent 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
13、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 present document may refer to technical spec
14、ifications 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 http:/webapp.etsi.org/key/queryform.asp. Mo
15、dal 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
16、 NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 125 468 V15.0.0 (2018-07)33GPP TS 25.468 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviat
17、ions . 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 services 8g36 Services expected from the transport layer 8g37 Functions of RUA 8g38 RUA procedures . 8g38.1
18、Elementary Procedures . 8g38.2 Connect 8g38.2.1 General 8g38.2.2 Successful Operation 8g38.2.2.1 HNB Originated 8g38.2.2.2 HNB-GW Originated 9g38.3 Direct Transfer . 9g38.3.1 General 9g38.3.2 Successful Operation (HNB-GW Originated) 10g38.3.3 Successful Operation (HNB Originated) 10g38.3.4 Abnormal
19、Conditions 10g38.4 Disconnect 10g38.4.1 General 10g38.4.2 Successful Operation (HNB Originated) 10g38.4.3 Successful Operation (HNB-GW Originated) 11g38.4.4 Abnormal Conditions 11g38.5 Connectionless Transfer . 11g38.5.1 General 11g38.5.2 Successful Operation (HNB-GW Originated) 11g38.5.3 Successful
20、 Operation (HNB Originated) 11g38.5.4 Abnormal Conditions 12g38.6 Error Indication 12g38.6.1 General 12g38.6.2 Successful Operation 12g39 Elements for RUA communication 12g39.1 Message functional definition and content . 12g39.1.1 General 12g39.1.2 Message contents 13g39.1.2.1 Presence 13g39.1.2.2 C
21、riticality 13g39.1.2.3 Range 13g39.1.2.4 Assigned Criticality . 13g39.1.3 CONNECT . 13g39.1.4 DIRECT TRANSFER. 14g3ETSI ETSI TS 125 468 V15.0.0 (2018-07)43GPP TS 25.468 version 15.0.0 Release 159.1.5 DISCONNECT . 14g39.1.6 CONNECTIONLESS TRANSFER 14g39.1.7 ERROR INDICATION . 14g39.2 Information Elem
22、ent Definitions 15g39.2.0 General 15g39.2.1 Message Type . 15g39.2.2 Context ID 15g39.2.3 Establishment Cause . 15g39.2.4 Intra Domain NAS Node Selector 15g39.2.5 RANAP Message 18g39.2.6 CN Domain Indicator 18g39.2.7 Cause 18g39.2.8 Criticality Diagnostics 19g39.2.9 CSG Membership Status . 20g39.3 M
23、essage and Information Element Abstract Syntax (with ASN.1) 21g39.3.0 General 21g39.3.1 Usage of private message mechanism for non-standard use . 21g39.3.2 Elementary Procedure Definitions 21g39.3.3 PDU definitions 24g39.3.4 Information Element definitions . 28g39.3.5 Common definitions . 32g39.3.6
24、Constant definitions 33g39.3.7 Container definitions. 34g39.4 Message transfer syntax . 38g310 Handling of unknown, unforeseen, and erroneous protocol data . 39g310.1 General . 39g310.2 Transfer Syntax Error . 39g310.3 Abstract Syntax Error . 39g310.3.1 General 39g310.3.2 Criticality Information 40g
25、310.3.3 Presence Information 40g310.3.4 Not comprehended IE/IE group 41g310.3.4.1 Procedure Code . 41g310.3.4.1A Type of Message . 41g310.3.4.2 IEs other than the Procedure Code and Type of Message . 41g310.3.5 Missing IE or IE group . 42g310.3.6 IEs or IE groups received in wrong order or with too
26、many occurrences or erroneously present 43g310.4 Logical Error 44g310.5 Exceptions 44g3Annex A (informative): Change History 45g3History 46g3ETSI ETSI TS 125 468 V15.0.0 (2018-07)53GPP TS 25.468 version 15.0.0 Release 15Foreword This Technical Specification (TS) has been produced by the 3rdGeneratio
27、n 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
28、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 enh
29、ancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 468 V15.0.0 (2018-07)63GPP TS 25.468 version 15.0.0 Release 151 Scope The present document specifies the RANAP User Adaption (RUA) between the H
30、ome 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 transparent transport for RANAP messages. 2 References The following documents contain provisions which, thro
31、ugh 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 v
32、ersion 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 3GPP TS 25.413: “UTRAN Iu interface Radio Access Network Application Part
33、(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 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 6 ITU-T Recommendation X.691 (2002-07): “Informat
34、ion 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): Specification of basic notation“. 8 ITU-T Recommendation X.681 (2002-07): “Information technology - Abstract S
35、yntax 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 the present document, the following terms and definitions below apply. Terms and definitions not defin
36、ed 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 connection for a particular UE over the single signalling connection between the HNB and HNB-GW, identified by
37、the identities Context ID and CN Domain ID. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CN Core Network EP Elementary Procedure HNB Home Node B ETSI ETSI TS 125 468 V15.0.0 (2018-07)73GPP TS 25.468 version 15.0.0 Release 15HNB-GW Home Node B Gateway
38、 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 Procedure specification principles The principle for specifying the procedure logic is to specify the functio
39、nal behaviour of the HNB Elementary procedures Elementary Procedure Message Connect CONNECTDirect Transfer DIRECT TRANSFER Disconnect DISCONNECTConnectionless Transfer CONNECTIONLESS TRANSFER Error Indication ERROR INDICATION 8.2 Connect 8.2.1 General The HNB or HNB-GW can initiate this procedure to
40、 establish an UE-associated Signalling Connection and carry a RANAP message. 8.2.2 Successful Operation 8.2.2.1 HNB Originated ETSI ETSI TS 125 468 V15.0.0 (2018-07)93GPP TS 25.468 version 15.0.0 Release 15HNB-GW HNB CONNECT Figure 1: Connect to HNB-GW procedure This procedure is used to carry the f
41、irst 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 establishment of a new UE-associated Signalling Connection between HNB and HNB-GW, which is directly m
42、apped 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 NAS Node Selector IE in the CONNECT message. NOTE: The Context ID is used as the Iu Signalling Connection
43、 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 HNB-GW to an HNB for a particular UE, e.g. RANAP RELOCATION REQUEST. This shall trigger the establishment
44、 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 the first RANAP message received by the HNB GW is a RELOCATION REQUEST message and the RELOCATION REQUES
45、T 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 handling the RANAP message. 8.3 Direct Transfer 8.3.1 General This procedure is initiated by either the
46、HNB or HNB-GW to transport a RANAP message between the two nodes. The HNB-GW can initiate this procedure to establish an UE-associated Signalling Connection when carrying the second RANAP RELOCATION REQUEST message. ETSI ETSI TS 125 468 V15.0.0 (2018-07)103GPP TS 25.468 version 15.0.0 Release 158.3.
47、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 2 from the HNB-GW to the HNB. This procedure can be used to carry the second RANAP RELOCATION REQUEST m
48、essage 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 Signalling Connection the RANAP message refers to. 8.3.3 Successful Operation (HNB Originated) HNB-GW
49、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 DISCONNECT 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. 8.4.2 Successful Operation (HNB Originated) HNB-GW DISCONNECT HNB Figure 4: Disconnect to HNB-GW ETSI ETSI TS 125 468 V15.
