ETSI TS 136 422-2016 LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) X2 signalling transport (V13 0 0 3GPP TS 36 422 version 13 0 0 Release 13)《长期演进技术(LTE) 演进型通用陆地.pdf

1、 ETSI TS 1Evolved Universal TerresX2 s(3GPP TS 36.4TECHNICAL SPECIFICATION136 422 V13.0.0 (2016LTE; restrial Radio Access Network (2 signalling transport 6.422 version 13.0.0 Release 1316-01) k (E-UTRAN); ) ETSI ETSI TS 136 422 V13.0.0 (2016-01)13GPP TS 36.422 version 13.0.0 Release 13Reference RTS/

2、TSGR-0336422vd00 Keywords LTE 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 docum

3、ent 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 cas

4、e 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 docume

5、nt may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.o

6、rg/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 modified withou

7、t the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Memb

8、ers. 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 136 422 V13.0.0 (2016-01)23GPP TS 36.422 version 13.0.0 Release 13Intellectual

9、 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 Property Rights (IPR

10、s); 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 searches, has been

11、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 by ETSI 3rd

12、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 between GSM, UMTS,

13、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 of the ETSI Dr

14、afting 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 136 422 V13.0.0 (2016-01)33GPP TS 36.422 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal ve

15、rbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.3 Abbreviations . 5g34. X2 signalling bearer . 6g34.1 Function and protocol stack 6g35 Data link layer 6g36 IP layer . 6g37 Transport layer . 6g3Annex A (informative): Chang

16、e History 8g3History 9g3ETSI ETSI TS 136 422 V13.0.0 (2016-01)43GPP TS 36.422 version 13.0.0 Release 13Foreword 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 c

17、hange 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 the first digit: 1 presented to TSG for information; 2 pr

18、esented 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 incremented when editorial only changes have been incorporated

19、in the document. ETSI ETSI TS 136 422 V13.0.0 (2016-01)53GPP TS 36.422 version 13.0.0 Release 131 Scope The present document specifies the standards for Signalling Transport to be used across X2 interface. X2 interface is a logical interface between eNBs. The present document describes how the X2-AP

20、 signalling messages are transported over X2. 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-

21、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 same Rel

22、ease as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 IETF RFC 2460 (1998-12): “Internet Protocol, Version 6 (IPv6) Specification“. 3 IETF RFC 791(1981-09): “Internet Protocol“. 4 IETF RFC 2474 (1998-12): “Definition of the Differentiated Services Field (DS Field) i

23、n the IPv4 and IPv6 Headers“. 5 IETF RFC 4960 (2007-09): “Stream Control Transmission Protocol“. 3 Definitions, symbols 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 do

24、cument takes precedence over the definition of the same term, if any, in TR 21.905 1. X2: logical interface between two eNBs. 3.3 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 ta

25、kes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. eNB E-UTRAN Node B DiffServ Differentiated ServiceIANA Internet Assigned Number Authority IP Internet Protocol PPP Point to Point Protocol SCTP Stream Control Transmission Protocol ETSI ETSI TS 136 422 V13.0.0 (2016

26、-01)63GPP TS 36.422 version 13.0.0 Release 134. X2 signalling bearer 4.1 Function and protocol stack X2 signalling bearer provides the following functions: - Provision of reliable transfer of X2-AP message over X2 interface. - Provision of networking and routeing function - Provision of redundancy i

27、n the signalling network - Support for flow control and congestion control The protocol stack for X2 Signalling Bearer is shown in figure 4.1 and details on each protocol are described in the following sections. SCTP IP Data link layer X2-AP Physical layer Radio Network Layer TransportNetworkLayer F

28、igure 4.1: X2 signalling bearer protocol stack The Transport Network Layer is based on IP transport, comprising SCTP on top of IP. 5 Data link layer The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc. , shall not be prevented. 6 IP layer The eNB shall support IPv6 (IETF RF

29、C 2460 2) and/or IPv4 (IETF RFC 791 3). The IP layer of X2 only supports point-to-point transmission for delivering X2-AP message. The eNB shall support the Diffserv Code Point marking as described in IETF RFC 2474 4. 7 Transport layer SCTP (IETF RFC 4960 5) shall be supported as the transport layer

30、 of X2 signalling bearer. The Payload Protocol Identifier assigned by IANA to be used by SCTP for the application layer protocol X2AP is 27. SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling p

31、rotocols over IP network. ETSI ETSI TS 136 422 V13.0.0 (2016-01)73GPP TS 36.422 version 13.0.0 Release 13There shall be only one SCTP association established between one eNB pair. An eNB shall use the Destination Port Number value 36422 assigned by IANA to be used for X2AP and this value shall also

32、be used in Source Port Number by all eNBs within a network. NOTE: A multi-homed eNB implementation should provide the correspondent eNB with the set of IP addresses supported during SCTP association establishment unless the correspondent eNB already has this information e.g. through IP address manag

33、ement. An arbitrary eNB shall be able to initiate the INIT procedure towards another eNB for establishing the SCTP association. Within the SCTP association established between one eNB pair; - A single pair of stream identifiers shall be reserved for the sole use of X2AP elementary procedures that ut

34、ilize non UE-associated signalling. - At least one pair of stream identifiers shall be reserved for the sole use of X2AP elementary procedures that utilize UE-associated signalling. However a few pairs (i.e. more than one) should be reserved. - A single UE-associated signalling shall use one SCTP st

35、ream and the stream should not be changed during the communication of the UE-associated signalling. Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remot

36、e SCTP end-point. For SCTP endpoint redundancy an INIT may be sent from either of the eNBs, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960 5 in subclause 5.2. The SCTP congestion control may, using an implementation specific mechanism, ini

37、tiate higher layer protocols to reduce the signalling traffic at the source and prioritise certain messages. ETSI ETSI TS 136 422 V13.0.0 (2016-01)83GPP TS 36.422 version 13.0.0 Release 13Annex A (informative): Change History TSG # TSG Doc. CR Rev Subject/Comment New 38 Apecification approved at TSG

38、-RAN and placed under change control 8.0.0 39 RP-080077 0001 - Dedication of common streams over X2 8.1.0 40 RP-080301 0003 - SCTP flow control and overload protection 8.2.0 41 RP-080583 0005 1 Correct the wording of common and dedicated procedures 8.3.0 41 RP-080583 0006 2 SCTP restart function for

39、 X2 interface 8.3.0 41 RP-080583 0007 - Clarification of SCTP Congestion Indication over X2 8.3.0 42 RP-080855 0008 1 Further clarification of SCTP Association handling 8.4.0 42 RP-080855 0009 Removal of chapter 8 8.4.0 43 RP-090090 0010 1 The use of the number of stream ID for a UE-associated signa

40、lling 8.5.0 43 RP-090085 0011 1 Clarification of SCTP streams 8.5.0 43 RP-090085 0012 1 Clarification the overload protection function support in SCTP 8.5.0 46 RP-091183 0014 1 Specification of SCTP destination port number 8.6.0 - - - - Created Rel-9 version based on v8.6.0 9.0.0 47 RP-100213 0016 S

41、pecification of Payload Identifier 9.1.0 50 Created Rel-10 version based on v. 9.1.0 10.0.0 SP-49 SP-100629 Clarification on the use of References (TS 21.801 CR#0030) 10.0.1 52 RP-110685 0018 Correction to the References in 36.422 10.1.0 09/2012 Update to Rel-11 version (MCC) 11.0.0 09/2014 Update to Rel-12 version (MCC) 12.0.0 12/2015 Update to Rel-13 version (MCC) 13.0.0 ETSI ETSI TS 136 422 V13.0.0 (2016-01)93GPP TS 36.422 version 13.0.0 Release 13History Document history V13.0.0 January 2016 Publication