ETSI TS 136 425-2016 Universal Mobile Telecommunications System (UMTS) LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) X2 interface user plane protocol (V13 1 1 3G.pdf

《ETSI TS 136 425-2016 Universal Mobile Telecommunications System (UMTS) LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) X2 interface user plane protocol (V13 1 1 3G.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 136 425-2016 Universal Mobile Telecommunications System (UMTS) LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) X2 interface user plane protocol (V13 1 1 3G.pdf（19页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1Universal Mobile TelEvolvedRadio AccX2 interfa(3GPP TS 36.4TECHNICAL SPECIFICATION136 425 V13.0.0 (2016elecommunications System (LTE; ed Universal Terrestrial ccess Network (E-UTRAN); rface user plane protocol .425 version 13.0.0 Release 1316-01) (UMTS); 13) ETSI ETSI TS 136 425 V13.0.0 (2

2、016-01)13GPP TS 36.425 version 13.0.0 Release 13Reference RTS/TSGR-0336425vd00 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-Prfectu

3、re de Grasse (06) N 7803/88 Important notice The present document 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 mo

4、dified without the prior written authorization of ETSI. In 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.

5、 Users of the present document should be aware that the document 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

6、comment to one of the following services: https:/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 ETS

7、I. The content of the PDF version shall not be modified without 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

8、are Trade Marks of ETSI registered for the benefit 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 136 425 V13.0.0

9、(2016-01)23GPP TS 36.425 version 13.0.0 Release 13Intellectual 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 b

10、e found in ETSI SR 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 I

11、PR Policy, no investigation, 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. Foreword Th

12、is Technical Specification (TS) has been produced 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 correspond

13、ing ETSI deliverables. The cross reference between 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“ a

14、re 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 NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 136 425 V13.0.0 (2016-01)33GPP TS 36.425 version 13.0.0 Release 13C

15、ontents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 General . 6g34.1 General aspects . 6g35 X2 user plane protocol . 7g35.1 General . 7g35.2

16、 X2 user plane protocol layer services . 7g35.3 Services expected from the X2 Transport Network Layer . 7g35.4 Elementary procedures . 8g35.4.1 Transfer of Downlink User Data . 8g35.4.1.1 Successful operation 8g35.4.1.2 Unsuccessful operation . 8g35.4.2 Downlink Data Delivery Status 8g35.4.2.1 Succe

17、ssful operation 8g35.4.2.2 Unsuccessful operation . 9g35.5 Elements for the X2 user plane protocol 10g35.5.1 General 10g35.5.2 Frame format for the X2 user plane protocol 11g35.5.2.1 DL USER DATA (PDU Type 0) 11g35.5.2.2 DL DATA DELIVERY STATUS (PDU Type 1) . 12g35.5.2.3 DL DATA DELIVERY STATUS EXTE

18、NDED (PDU Type 2). 12g35.5.3 Coding of information elements in frames . 14g35.5.3.1 PDU Type . 14g35.5.3.2 Spare . 14g35.5.3.3 X2-U Sequence Number . 14g35.5.3.4 Lost Packet Report 14g35.5.3.5 Final Frame Indication 14g35.5.3.6 Highest successfully delivered PDCP Sequence Number . 14g35.5.3.7 Desire

19、d buffer size for the E-RAB 14g35.5.3.8 Minimum desired buffer size for the UE . 15g35.5.3.9 Number of lost X2-U Sequence Number ranges reported . 15g35.5.3.10 Start of lost X2-U Sequence Number range 15g35.5.3.11 End of lost X2-U Sequence Number range . 15g35.5.3.12 Spare extension . 15g35.5.3.13 H

20、ighest successfully delivered PDCP Sequence Number Extended . 15g35.5.3.14 Start of lost X2-U Sequence Number range Extended 15g35.5.3.15 End of lost X2-U Sequence Number range Extended . 16g35.5.4 Timers . 16g35.6 Handling of unknown, unforeseen and erroneous protocol data 16g3Annex A (informative)

21、: Change history . 17g3History 18g3ETSI ETSI TS 136 425 V13.0.0 (2016-01)43GPP TS 36.425 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 TS

22、G 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 the first digit: 1 presented to TSG for inform

23、ation; 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 incremented when editorial only changes have been in

24、corporated in the document. ETSI ETSI TS 136 425 V13.0.0 (2016-01)53GPP TS 36.425 version 13.0.0 Release 131 Scope The present document specifies the X2 user plane protocol being used over the X2 interface. 2 References The following documents contain provisions which, through reference in this text

25、, 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 version applies. In t

26、he 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 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 36.300: “Evolved Universal Terrestria

27、l Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2“. 3 3GPP TS 29.281: “General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the p

28、resent 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. Master eNB: as defined in TS 36.300 2. Secondary eNB: as defined in TS 36.300 2. Split bearer

29、: as defined in TS 36.300 2. 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. DC Dual Conn

30、ectivity DL Downlink E-RAB E-UTRAN Radio Access Bearer MeNB Master eNB SeNB Secondary eNBUL Uplink UP User Plane X2 UP X2 User Plane ETSI ETSI TS 136 425 V13.0.0 (2016-01)63GPP TS 36.425 version 13.0.0 Release 134 General 4.1 General aspects The X2 user plane (X2 UP) protocol is located in the User

31、Plane of the Radio Network layer over the X2 interface. The X2 UP protocol is used to convey control information related to the user data flow management of E-RABs. Each X2 UP protocol instance is associated to one E-RAB only. This version of the present document defines the X2 UP protocol in the co

32、ntext of dual connectivity only, more specifically, only for X2 user data bearers setup for E-RABs configured with the split bearer option. If configured, X2 UP protocol instances exist at the eNBs between which the X2 user data bearers are setup, specifically for dual connectivity between the MeNB

33、and the SeNB. NOTE: X2 user data bearers may be setup for data forwarding purposes during X2 HO or during DC related mobility, however, these X2 user data bearers do not require the execution of any additional E-RAB related UP protocol functions related to an X2 UP protocol instance. In this version

34、 of the present document, X2 UP protocol data is conveyed by GTP-U protocol means, more specifically, by means of the “RAN Container“ GTP-U extension header as defined in TS 29.281 3. ETSI ETSI TS 136 425 V13.0.0 (2016-01)73GPP TS 36.425 version 13.0.0 Release 135 X2 user plane protocol 5.1 General

35、The X2 UP protocol layer is using services of the transport network layer in order to allow flow control of user data packets transferred over the X2 interface. 5.2 X2 user plane protocol layer services The following functions are provided by the X2 UP protocol: - Provision of X2 UP specific sequenc

36、e number information for user data transferred from the MeNB to the SeNB for a specific E-RAB configured with the split bearer option; - Information of successful in sequence delivery of PDCP PDUs to the UE from SeNB for user data associated with a specific E-RAB configured with the split bearer opt

37、ion; - Information of PDCP PDUs that were not delivered to the UE; - Information of the currently desired buffer size at the SeNB for transmitting to the UE user data associated with a specific E-RAB configured with the split bearer option; - Information of the currently minimum desired buffer size

38、at the SeNB for transmitting to the UE user data associated with all E-RABs configured with the split bearer option. 5.3 Services expected from the X2 Transport Network Layer The X2 user plane protocol layer expects the following services from the Transport Network Layer: - Transfer of user data. ET

39、SI ETSI TS 136 425 V13.0.0 (2016-01)83GPP TS 36.425 version 13.0.0 Release 135.4 Elementary procedures 5.4.1 Transfer of Downlink User Data 5.4.1.1 Successful operation The purpose of the Transfer of Downlink User Data procedure is to provide X2-U specific sequence number information at the transfer

40、 of user data carrying a DL PDCP PDU from the MeNB to the SeNB via the X2-U interface. An X2 user plane instance making use of the Transfer of Downlink User Data procedure is associated to a single E-RAB only. The Transfer of Downlink User Data procedure is invoked whenever user data for that partic

41、ular E-RAB needs to be sent across the X2-U interface. The MeNB shall assign consecutive X2-U sequence numbers to each transferred X2-U packet. The SeNB shall detect whether an X2-U packet was lost and memorise the respective sequence number after it has declared the respective X2-U packet as being

42、“lost“. The SeNB shall transfer the remaining PDCP PDUs towards the UE and memorise the highest PDCP PDU sequence number of the PDCP PDU that was successfully delivered in sequence towards the UE. NOTE: The Transfer of Downlink User Data procedure and the associated feedback of lost X2-U packets ass

43、ist the MeNB in avoiding PDCP HFN de-synchronisation. If an E-UTRAN deployment decides to not use the Transfer of Downlink User Data procedure, PDCP HFN synchronization should be ensured by other means. Figure 5.4.1.1-1: Successful Transfer of Downlink User Data 5.4.1.2 Unsuccessful operation Void.

44、5.4.2 Downlink Data Delivery Status 5.4.2.1 Successful operation The purpose of the Downlink Data Delivery Status procedure is to provide feedback from the SeNB to the MeNB to allow the MeNB to control the downlink user data flow via the SeNB for the respective E-RAB. The SeNB may also transfer upli

45、nk user data for the concerned E-RAB to the MeNB together with a DL DATA DELIVERY STATUS frame within the same GTP-U PDU. When the SeNB decides to trigger the Feedback for Downlink Data Delivery procedure it shall report: a) the highest PDCP PDU sequence number successfully delivered in sequence to

46、the UE among those PDCP PDUs received from the MeNB; b) the desired buffer size in bytes for the concerned E-RAB; c) the minimum desired buffer size in bytes for the UE; d) the X2-U packets that were declared as being “lost“ by the SeNB and have not yet been reported to the MeNB within the DL DATA D

47、ELIVERY STATUS frame. ETSI ETSI TS 136 425 V13.0.0 (2016-01)93GPP TS 36.425 version 13.0.0 Release 13NOTE: If an E-UTRAN deployment has decided not to use the Transfer of Downlink User Data procedure, d) above is not applicable. The DL DATA DELIVERY STATUS frame shall also include an indication whet

48、her the frame is the last DL status report received in the course of releasing a bearer from the SeNB. When receiving such indication, if applicable, the MeNB considers that no more UL data is to be expected from the SeNB. The MeNB, when receiving the DL DATA DELIVERY STATUS frame: - regards the des

49、ired buffer size under b) and c) above as the amount of data desired from the SeNB being declared - from the PDCP sequence number reported under a) above within the same frame, as well as from the most recently reported PDCP sequence number(s) of all other E-RABs established for the UE; - as the momentary desired buffer sizes, independent of buffer sizes indicated in the past. - is allowed to remove the buffered PDCP PDUs according to the feedback of successfully delivered PDCP PDUs; - decides upon the actions necessary to take for PDCP PDUs reported oth