ETSI TS 125 470-2017 Universal Mobile Telecommunications System (UMTS) UTRAN Iuh Interface PCAP User Adaption (PUA) signalling (V14 0 0 3GPP TS 25 470 version 14 0 0 Release 14)《通用.pdf

1、 ETSI TS 125 470 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); UTRAN Iuh Interface PCAP User Adaption (PUA) signalling (3GPP TS 25.470 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 125 470 V14.0.0 (2017-04)13GPP TS 25.470 version 14.0.0 Release 14Reference RT

2、S/TSGR-0325470ve00 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 do

3、cument 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 doc

5、ument 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 mo

7、dified 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 benefi

8、t 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 470 V14.0.0 (2017-04)23GPP TS 25.470 version 14.0.0 Release 1

9、4Intellectual 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 Propert

10、y 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 search

11、es, 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 produced

12、 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 betwee

13、n 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 o

14、f 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 470 V14.0.0 (2017-04)33GPP TS 25.470 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 PUA services

16、 8g36 Services expected from the transport layer 8g37 Functions of PUA . 8g38 PUA procedures . 8g38.1 Elementary Procedures . 8g38.2 Connect 8g38.2.1 General 8g38.2.2 Successful Operation 9g38.3 Direct Transfer . 9g38.3.1 General 9g38.3.2 Successful Operation (HNB-GW Originated) 9g38.3.3 Successful

17、Operation (HNB Originated) 9g38.3.4 Abnormal Conditions 10g38.4 Disconnect 10g38.4.1 General 10g38.4.2 Successful Operation (HNB Originated) 10g38.4.3 Successful Operation (HNB-GW Originated) 10g38.5 Connectionless Transfer . 10g38.5.1 General 10g38.5.2 Successful Operation (HNB-GW Originated) 11g38

18、.5.3 Successful Operation (HNB Originated) 11g38.5.4 Abnormal Conditions 11g38.6 Error Indication 11g38.6.1 General 11g38.6.2 Successful Operation 11g39 Elements for PUA communication . 12g39.1 Message functional definition and content . 12g39.1.1 General 12g39.1.2 Message contents 12g39.1.2.1 Prese

19、nce 12g39.1.2.2 Criticality 12g39.1.2.3 Range 13g39.1.2.4 Assigned Criticality . 13g39.1.3 CONNECT . 13g39.1.4 DIRECT TRANSFER. 13g39.1.5 DISCONNECT . 13g39.1.6 CONNECTIONLESS TRANSFER 14g39.1.7 ERROR INDICATION . 14g3ETSI ETSI TS 125 470 V14.0.0 (2017-04)43GPP TS 25.470 version 14.0.0 Release 149.2

20、 Information Element Definitions 14g39.2.0 General 14g39.2.1 Message Type . 15g39.2.2 PCAP Context ID . 15g39.2.3 PCAP Message . 15g39.2.4 SAS Indicator 15g39.2.5 Transaction ID 15g39.2.6 Cause 15g39.2.7 Criticality Diagnostics 17g39.3 Message and Information Element Abstract Syntax (with ASN.1) 19g

21、39.3.0 General 19g39.3.1 Usage of private message mechanism for non-standard use . 19g39.3.2 Elementary Procedure Definitions 19g39.3.3 PDU definitions 23g39.3.4 Information Element definitions . 26g39.3.5 Common definitions . 29g39.3.6 Constant definitions 30g39.3.7 Container definitions. 31g39.4 M

22、essage transfer syntax . 35g310 Handling of unknown, unforeseen, and erroneous protocol data . 36g310.1 General . 36g310.2 Transfer Syntax Error . 36g310.3 Abstract Syntax Error . 36g310.3.1 General 36g310.3.2 Criticality Information 37g310.3.3 Presence Information 37g310.3.4 Not comprehended IE/IE

23、group 38g310.3.4.1 Procedure Code . 38g310.3.4.1A Type of Message . 38g310.3.4.2 IEs other than the Procedure Code and Type of Message . 38g310.3.5 Missing IE or IE group . 39g310.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present 40g310.4 Logical Error

24、41g310.5 Exceptions 41g3Annex A (informative): Change history . 42g3History 43g3ETSI ETSI TS 125 470 V14.0.0 (2017-04)53GPP TS 25.470 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document

25、 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 t

26、he 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 increme

27、nted when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 470 V14.0.0 (2017-04)63GPP TS 25.470 version 14.0.0 Release 141 Scope The present document specifies the PCAP User Adaption (PUA) between the Home Node B (HNB) and the Home Node B Gateway (HNB-GW). It fulfils t

28、he HNB- HNB-GW communication requirements specified in TS 25.467 5 and is defined over the Iuh reference point. It provides transport for PCAP messages. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - Ref

29、erences 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

30、 GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 25.453: “UTRAN Iupc interface Positioning Calculation Application Part (PCAP) signalling“.

31、3 IETF RFC 4960 (2007-09): “Stream Control Transmission Protocol“. 4 3GPP TR 25.921 (Version 7.0.0): “Guidelines and principles for protocol description and error handling“. 5 3GPP TS 25.467: “UTRAN architecture for 3G Home Node B; Stage 2“. 6 ITU-T Recommendation X.691 (2002-07): “Information techn

32、ology - 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 Syntax Not

33、ation One (ASN.1): Information object specification“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the s

34、ame term, if any, in TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 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 1. CN Core

35、 Network EP Elementary Procedure HNB Home Node B HNB-GW Home Node B Gateway ETSI ETSI TS 125 470 V14.0.0 (2017-04)73GPP TS 25.470 version 14.0.0 Release 14PDU Protocol Data Unit PUA PCAP User AdaptionSCTP Stream Control Transmission Protocol 4 General The protocol described in the present document i

36、s the protocol between HNB-GW and HNB. 4.1 Procedure 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 DISCONNECTConn

37、ectionless Transfer CONNECTIONLESS TRANSFER Error Indication ERROR INDICATION 8.2 Connect 8.2.1 General The HNB can initiate this procedure to establish a Signalling Connection and carry a PCAP message. ETSI ETSI TS 125 470 V14.0.0 (2017-04)93GPP TS 25.470 version 14.0.0 Release 148.2.2 Successful O

38、peration HNB-GW HNB CONNECT Figure 8.2.2-1: Connect procedure successful operation This procedure is used to carry the first PCAP message from the HNB to the HNB-GW. If the SAS Indicator IE is included the HNB-GW may use to select a SAS for connection. Additional information is provided to enable th

39、e HNB-GW to trigger the establishment of a new Signalling Connection between HNB and HNB-GW, which is directly mapped to the Iupc Signalling Connection the PCAP message refers to. NOTE: The Context ID is used as the Iupc Signalling Connection identifier in the corresponding PCAP messages. 8.3 Direct

40、 Transfer 8.3.1 General This procedure is initiated by either the HNB or HNB-GW to transport a PCAP message between the two nodes. 8.3.2 Successful Operation (HNB-GW Originated) HNB-GW DIRECT TRANSFER HNB Figure 8.3.2-1: Direct Transfer procedure successful operation This procedure is used to carry

41、any downlink connection-oriented PCAP message defined in TS 25.453 2 from the HNB-GW to the HNB. 8.3.3 Successful Operation (HNB Originated) HNB-GW DIRECT TRANSFER HNB Figure 8.3.3-1: Direct Transfer procedure successful operation ETSI ETSI TS 125 470 V14.0.0 (2017-04)103GPP TS 25.470 version 14.0.0

42、 Release 14This procedure is used to carry any uplink connection-oriented PCAP message defined in TS 25.453 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 normally initiated by the HNB

43、to terminate a Signalling Connection between the HNB and HNB-GW, but may be initiated by the HNB-GW to close a refused connection or if an existing connection is released (e.g. for error reasons) by the SAS or HNB-GW. 8.4.2 Successful Operation (HNB Originated) HNB-GW DISCONNECT HNB Figure 8.4.2-1:

44、Disconnect procedure This procedure is used to release a signalling connection between the HNB and HNB-GW and may carry the last PCAP (TS 25.453 2) uplink connection-oriented message of a given Signalling Connection to the HNB-GW over the Iuh interface. This procedure may also be used to indicate er

45、ror conditions at the HNB. This procedure will indicate the cause of the termination in the Cause IE. 8.4.3 Successful Operation (HNB-GW Originated) HNB-GW DISCONNECT HNB Figure 8.4.3-1: Disconnect procedure This procedure is used to close a given Signalling Connection between the HNB and the HNB-GW

46、 over the Iuh interface. This procedure will indicate the cause of the termination in the Cause IE. 8.5 Connectionless Transfer 8.5.1 General This procedure is initiated by either the HNB or the HNB-GW to transfer connectionless PCAP messages between the HNB and HNB-GW. ETSI ETSI TS 125 470 V14.0.0

47、(2017-04)113GPP TS 25.470 version 14.0.0 Release 148.5.2 Successful Operation (HNB-GW Originated) HNB-GW CONNECTIONLESS TRANSFER HNB Figure 8.5.2-1: Connectionless Transfer procedure to HNB This procedure is used to carry any downlink connectionless PCAP message defined in TS 25.453 2 from the HNB-G

48、W to the HNB. 8.5.3 Successful Operation (HNB Originated) HNB-GW CONNECTIONLESS TRANSFER HNB Figure 8.5.3-1: Connectionless Transfer procedure to HNB-GW This procedure is used to carry any uplink connectionless PCAP message defined in TS 25.453 2 from the HNB to the HNB-GW. If the SAS Indicator IE i

49、s included the HNB-GW may use to select a SAS as the destination of the message. 8.5.4 Abnormal Conditions - 8.6 Error Indication 8.6.1 General The Error Indication procedure is initiated by either HNB or HNB-GW to report detected errors in one incoming message. 8.6.2 Successful Operation ERROR INDICATION HNB HNB-GW Figure 8.6.2-1 Error Indication HNB Originated, Successful Operation ETSI ETSI TS 125 470 V14.0.0 (2017-04)123GPP TS 25.470 version 14.0.0 Release 14ERROR INDICATION HNB HNB-GW Figure 8.6.2-2 Error Indication HNB-GW Orig