ETSI TS 125 470-2018 Universal Mobile Telecommunications System (UMTS) UTRAN Iuh Interface PCAP User Adaption (PUA) signalling (V15 0 0 3GPP TS 25 470 version 15 0 0 Release 15).pdf

《ETSI TS 125 470-2018 Universal Mobile Telecommunications System (UMTS) UTRAN Iuh Interface PCAP User Adaption (PUA) signalling (V15 0 0 3GPP TS 25 470 version 15 0 0 Release 15).pdf》由会员分享，可在线阅读，更多相关《ETSI TS 125 470-2018 Universal Mobile Telecommunications System (UMTS) UTRAN Iuh Interface PCAP User Adaption (PUA) signalling (V15 0 0 3GPP TS 25 470 version 15 0 0 Release 15).pdf（43页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 125 470 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); UTRAN Iuh Interface PCAP User Adaption (PUA) signalling (3GPP TS 25.470 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 125 470 V15.0.0 (2018-07)13GPP TS 25.470 version 15.0.0 Release 15Reference RT

2、S/TSGR-0325470vf00 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. 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 tradem

8、arks 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 470 V15.0.0 (2018-07)23GPP TS 25.470 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 SR

10、 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 inve

11、stigation, 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 docume

12、nt 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 i

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

14、fications 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. Mod

15、al 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 470 V15.0.0 (2018-07)33GPP TS 25.470 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviati

17、ons . 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 7g36 Services expected from the transport layer 8g37 Functions of PUA . 8g38 PUA procedures . 8g38.1

18、 Elementary Procedures . 8g38.2 Connect 8g38.2.1 General 8g38.2.2 Successful Operation 8g38.3 Direct Transfer . 9g38.3.1 General 9g38.3.2 Successful Operation (HNB-GW Originated) 9g38.3.3 Successful Operation (HNB Originated) 9g38.3.4 Abnormal Conditions 9g38.4 Disconnect 9g38.4.1 General 9g38.4.2 S

19、uccessful 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) 10g38.5.3 Successful Operation (HNB Originated) 11g38.5.4 Abnormal Conditions 11g38.6 Error Indication 11g38.

20、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 Presence 12g39.1.2.2 Criticality 12g39.1.2.3 Range 12g39.1.2.4 Assigned Criticality . 12g39.1.3 CONNECT . 13g

21、39.1.4 DIRECT TRANSFER. 13g39.1.5 DISCONNECT . 13g39.1.6 CONNECTIONLESS TRANSFER 13g39.1.7 ERROR INDICATION . 14g3ETSI ETSI TS 125 470 V15.0.0 (2018-07)43GPP TS 25.470 version 15.0.0 Release 159.2 Information Element Definitions 14g39.2.0 General 14g39.2.1 Message Type . 14g39.2.2 PCAP Context ID .

22、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) 19g39.3.0 General 19g39.3.1 Usage of private message mechanism for non-standard use . 19g39.3.2 Elementary

23、Procedure Definitions 19g39.3.3 PDU definitions 22g39.3.4 Information Element definitions . 26g39.3.5 Common definitions . 28g39.3.6 Constant definitions 29g39.3.7 Container definitions. 31g39.4 Message transfer syntax . 34g310 Handling of unknown, unforeseen, and erroneous protocol data . 35g310.1

24、General . 35g310.2 Transfer Syntax Error . 35g310.3 Abstract Syntax Error . 35g310.3.1 General 35g310.3.2 Criticality Information 36g310.3.3 Presence Information 36g310.3.4 Not comprehended IE/IE group 37g310.3.4.1 Procedure Code . 37g310.3.4.1A Type of Message . 37g310.3.4.2 IEs other than the Proc

25、edure Code and Type of Message . 37g310.3.5 Missing IE or IE group . 38g310.3.6 IEs or IE groups received in wrong order or with too many occurrences or erroneously present 39g310.4 Logical Error 40g310.5 Exceptions 40g3Annex A (informative): Change history . 41g3History 42g3ETSI ETSI TS 125 470 V15

26、.0.0 (2018-07)53GPP TS 25.470 version 15.0.0 Release 15Foreword 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

27、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 the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indica

28、tes 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 incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 125 470 V15.0.0 (2

29、018-07)63GPP TS 25.470 version 15.0.0 Release 151 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 the HNB- HNB-GW communication requirements specified in TS 25.467 5 and is defined over the Iuh reference

30、 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. - References are either specific (identified by date of publication, edition number, version number, etc.) or

31、 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 the

32、 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“. 3 IETF RFC 4960 (2007-09): “Stream Control Transmission Protocol“. 4 3GPP TR 25.921 (Version 7.0.0): “Gu

33、idelines 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 technology - ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)“. 7 ITU-T Recommendation X.68

34、0 (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 Notation One (ASN.1): Information object specification“. 3 Definitions and abbreviations 3.1 Definitions Fo

35、r 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 same term, if any, in TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the abbrev

36、iations 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 Network EP Elementary Procedure HNB Home Node B HNB-GW Home Node B Gateway PDU Protocol Data Unit PUA P

37、CAP User AdaptionSCTP Stream Control Transmission Protocol ETSI ETSI TS 125 470 V15.0.0 (2018-07)73GPP TS 25.470 version 15.0.0 Release 154 General The protocol described in the present document is the protocol between HNB-GW and HNB. 4.1 Procedure specification principles The principle for specifyi

38、ng 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 Indication ERROR INDICATION 8.2 Connect 8.2.1 General

39、The HNB can initiate this procedure to establish a Signalling Connection and carry a PCAP message. 8.2.2 Successful Operation 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 Indica

40、tor IE is included the HNB-GW may use to select a SAS for connection. Additional information is provided to enable the 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. ETS

41、I ETSI TS 125 470 V15.0.0 (2018-07)93GPP TS 25.470 version 15.0.0 Release 15NOTE: The Context ID is used as the Iupc Signalling Connection identifier in the corresponding PCAP messages. 8.3 Direct Transfer 8.3.1 General This procedure is initiated by either the HNB or HNB-GW to transport a PCAP mess

42、age 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 any downlink connection-oriented PCAP message defined in TS 25.453 2 from the HNB-GW to the HNB. 8.3.3 S

43、uccessful Operation (HNB Originated) HNB-GW DIRECT TRANSFER HNB Figure 8.3.3-1: Direct Transfer procedure successful operation This 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 t

44、he HNB-GW. 8.3.4 Abnormal Conditions - 8.4 Disconnect 8.4.1 General This procedure is normally initiated by the HNB 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 err

45、or reasons) by the SAS or HNB-GW. ETSI ETSI TS 125 470 V15.0.0 (2018-07)103GPP TS 25.470 version 15.0.0 Release 158.4.2 Successful Operation (HNB Originated) HNB-GW DISCONNECT HNB Figure 8.4.2-1: Disconnect procedure This procedure is used to release a signalling connection between the HNB and HNB-G

46、W 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 error conditions at the HNB. This procedure will indicate the cause of the termination in the Cause IE. 8.

47、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 over the Iuh interface. This procedure will indicate the cause of the termination in the Cause IE. 8.5

48、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. 8.5.2 Successful Operation (HNB-GW Originated) HNB-GW CONNECTIONLESS TRANSFER HNB Figure 8.5.2-1: Connectionless Transfer procedure t

49、o HNB This procedure is used to carry any downlink connectionless PCAP message defined in TS 25.453 2 from the HNB-GW to the HNB. ETSI ETSI TS 125 470 V15.0.0 (2018-07)113GPP TS 25.470 version 15.0.0 Release 158.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 is included the HNB-GW may use to select a S