ETSI TS 136 322-2016 LTE Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Link Control (RLC) protocol specification (V13 2 0 3GPP TS 36 322 version 13 2 0 Release 13)《长期演进.pdf

1、 ETSI TS 1Evolved Universal TRadio Link Contr(3GPP TS 36.3TECHNICAL SPECIFICATION136 322 V13.1.0 (2016LTE; l Terrestrial Radio Access (E-ntrol (RLC) protocol specificat.322 version 13.1.0 Release 1316-04) UTRA); cation 13) ETSI ETSI TS 136 322 V13.1.0 (2016-04)13GPP TS 36.322 version 13.1.0 Release

2、13Reference RTS/TSGR-0236322vd10 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 T

3、he 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 modified without the prior written authorization

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

5、 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.aspIf 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

7、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 are Trade Marks of ETSI registered for the bene

8、fit 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 322 V13.1.0 (2016-04)23GPP TS 36.322 version 13.1.0 Release

9、 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 be found in ETSI SR 000 314: “Intellectual Prope

10、rty 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 sear

11、ches, 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 produc

12、ed 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 betw

13、een 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

14、 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 322 V13.1.0 (2016-04)33GPP TS 36.322 version 13.1.0 Release 13Contents Intellectual Property Rights 2g3Forewor

15、d . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 General . 7g34.1 Introduction 7g34.2 RLC architecture 7g34.2.1 RLC entities 7g34.2.1.1 TM RLC entity 9g34.2.1.1.1 General 9g34.2.1.1.2

16、Transmitting TM RLC entity . 9g34.2.1.1.3 Receiving TM RLC entity . 9g34.2.1.2 UM RLC entity . 10g34.2.1.2.1 General 10g34.2.1.2.2 Transmitting UM RLC entity 10g34.2.1.2.3 Receiving UM RLC entity . 10g34.2.1.3 AM RLC entity . 11g34.2.1.3.1 General 11g34.2.1.3.2 Transmitting side . 12g34.2.1.3.3 Rece

17、iving side . 12g34.3 Services 12g34.3.1 Services provided to upper layers . 12g34.3.2 Services expected from lower layers 12g34.4 Functions 13g34.5 Data available for transmission 13g35 Procedures 13g35.1 Data transfer procedures . 13g35.1.1 TM data transfer . 13g35.1.1.1 Transmit operations . 13g35

18、.1.1.1.1 General 13g35.1.1.2 Receive operations 13g35.1.1.2.1 General 13g35.1.2 UM data transfer . 14g35.1.2.1 Transmit operations . 14g35.1.2.1.1 General 14g35.1.2.2 Receive operations 14g35.1.2.2.1 General 14g35.1.2.2.2 Actions when an UMD PDU is received from lower layer . 14g35.1.2.2.3 Actions w

19、hen an UMD PDU is placed in the reception buffer 14g35.1.2.2.4 Actions when t-Reordering expires . 15g35.1.3 AM data transfer . 15g35.1.3.1 Transmit operations . 15g35.1.3.1.1 General 15g35.1.3.2 Receive operations 16g35.1.3.2.1 General 16g35.1.3.2.2 Actions when a RLC data PDU is received from lowe

20、r layer . 16g35.1.3.2.3 Actions when a RLC data PDU is placed in the reception buffer 16g3ETSI ETSI TS 136 322 V13.1.0 (2016-04)43GPP TS 36.322 version 13.1.0 Release 135.1.3.2.4 Actions when t-Reordering expires . 17g35.2 ARQ procedures . 17g35.2.1 Retransmission 17g35.2.2 Polling . 18g35.2.2.1 Tra

21、nsmission of a AMD PDU or AMD PDU segment . 18g35.2.2.2 Reception of a STATUS report . 19g35.2.2.3 Expiry of t-PollRetransmit 19g35.2.3 Status reporting . 19g35.3 SDU discard procedures . 20g35.4 Re-establishment procedure . 21g35.5 Handling of unknown, unforeseen and erroneous protocol data 21g35.5

22、.1 Reception of PDU with reserved or invalid values . 21g36 Protocol data units, formats and parameters . 21g36.1 Protocol data units 21g36.1.1 RLC data PDU 21g36.1.2 RLC control PDU . 22g36.2 Formats and parameters 22g36.2.1 Formats . 22g36.2.1.1 General 22g36.2.1.2 TMD PDU . 22g36.2.1.3 UMD PDU 22

23、g36.2.1.4 AMD PDU 25g36.2.1.5 AMD PDU segment 28g36.2.1.6 STATUS PDU . 32g36.2.2 Parameters. 33g36.2.2.1 General 33g36.2.2.2 Data field. 33g36.2.2.3 Sequence Number (SN) field 34g36.2.2.4 Extension bit (E) field . 34g36.2.2.5 Length Indicator (LI) field 34g36.2.2.6 Framing Info (FI) field 34g36.2.2.

24、7 Segment Offset (SO) field . 35g36.2.2.8 Last Segment Flag (LSF) field 35g36.2.2.9 Data/Control (D/C) field . 35g36.2.2.10 Re-segmentation Flag (RF) field . 35g36.2.2.11 Polling bit (P) field 35g36.2.2.12 Reserved 1 (R1) field 36g36.2.2.13 Control PDU Type (CPT) field . 36g36.2.2.14 Acknowledgement

25、 SN (ACK_SN) field . 36g36.2.2.15 Extension bit 1 (E1) field 36g36.2.2.16 Negative Acknowledgement SN (NACK_SN) field . 36g36.2.2.17 Extension bit 2 (E2) field 37g36.2.2.18 SO start (SOstart) field 37g36.2.2.19 SO end (SOend) field 37g37 Variables, constants and timers 37g37.1 State variables 37g37.

26、2 Constants 39g37.3 Timers 39g37.4 Configurable parameters 40g3Annex A (informative): Change history . 41g3History 46g3ETSI ETSI TS 136 322 V13.1.0 (2016-04)53GPP TS 36.322 version 13.1.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP

27、). 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 an increase in version numb

28、er 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 enhancements, corrections, upd

29、ates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 136 322 V13.1.0 (2016-04)63GPP TS 36.322 version 13.1.0 Release 131 Scope The present document specifies the E-UTRA Radio Link Control (RLC) protocol for the UE E-UTRAN radio

30、interface. The specification describes: - E-UTRA RLC sublayer architecture; - E-UTRA RLC entities; - services expected from lower layers by E-UTRA RLC; - services provided to upper layers by E-UTRA RLC; - E-UTRA RLC functions; - elements for peer-to-peer E-UTRA RLC communication including protocol d

31、ata units, formats and parameters; - handling of unknown, unforeseen and erroneous protocol data at E-UTRA RLC. 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

32、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 GSM document), a non-specific reference implic

33、itly 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: “E-UTRA and E-UTRAN Overall Description; Stage 2“. 3 3GPP TS 36.321: “E-UTRA MAC protocol specification“. 4 3GPP TS 36.323: “E-UTR

34、A PDCP specification“. 5 3GPP TS 36.331: “E-UTRA RRC Protocol specification“. 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 document takes preced

35、ence over the definition of the same term, if any, in TR 21.905 1. byte segment: A byte of the Data field of an AMD PDU. Specifically, byte segment number 0 corresponds to the first byte of the Data field of an AMD PDU. Data field element: An RLC SDU or an RLC SDU segment that is mapped to the Data

36、field. RLC SDU segment: A segment of an RLC SDU. ETSI ETSI TS 136 322 V13.1.0 (2016-04)73GPP TS 36.322 version 13.1.0 Release 133.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AM Acknowledged Mode AMD AM Data ARQ Automatic Repeat reQuest BCCH Broadcast

37、Control CHannel BCH Broadcast CHannel CCCH Common Control CHannel DCCH Dedicated Control CHannel DL DownLink DL-SCH DL-Shared CHannel DTCH Dedicated Traffic CHannel E Extension biteNB E-UTRAN Node B E-UTRA Evolved UMTS Terrestrial Radio Access E-UTRAN Evolved UMTS Terrestrial Radio Access Network FI

38、 Framing Info HARQ Hybrid ARQ LI Length Indicator LSF Last Segment FlagMAC Medium Access Control MCCH Multicast Control Channel MTCH Multicast Traffic Channel PCCH Paging Control CHannel PDU Protocol Data Unit RLC Radio Link ControlRRC Radio Resource Control SAP Service Access Point SBCCH Sidelink B

39、roadcast Control Channel SC-MCCH Single Cell Multicast Control Channel SC-MTCH Single Cell Multicast Transport Channel SDU Service Data Unit SN Sequence Number SO Segment Offset STCH Sidelink Traffic Channel TB Transport Block TM Transparent ModeTMD TM Data UE User Equipment UL UpLink UM Unacknowled

40、ged Mode UMD UM Data 4 General 4.1 Introduction The objective is to describe the RLC architecture and the RLC entities from a functional point of view. 4.2 RLC architecture 4.2.1 RLC entities The description in this sub clause is a model and does not specify or restrict implementations. RRC is gener

41、ally in control of the RLC configuration. ETSI ETSI TS 136 322 V13.1.0 (2016-04)83GPP TS 36.322 version 13.1.0 Release 13Functions of the RLC sub layer are performed by RLC entities. For a RLC entity configured at the eNB, there is a peer RLC entity configured at the UE and vice versa. For an RLC en

42、tity configured at the transmitting UE for STCH or SBCCH there is a peer RLC entity configured at each receiving UE for STCH or SBCCH. An RLC entity receives/delivers RLC SDUs from/to upper layer and sends/receives RLC PDUs to/from its peer RLC entity via lower layers. An RLC PDU can either be a RLC

43、 data PDU (see sub clause 6.1.1) or a RLC control PDU (see sub clause 6.1.2). If an RLC entity receives RLC SDUs from upper layer, it receives them through a single SAP between RLC and upper layer, and after forming RLC data PDUs from the received RLC SDUs, the RLC entity delivers the RLC data PDUs

44、to lower layer through a single logical channel. If an RLC entity receives RLC data PDUs from lower layer, it receives them through a single logical channel, and after forming RLC SDUs from the received RLC data PDUs, the RLC entity delivers the RLC SDUs to upper layer through a single SAP between R

45、LC and upper layer. If an RLC entity delivers/receives RLC control PDUs to/from lower layer, it delivers/receives them through the same logical channel it delivers/receives the RLC data PDUs through. An RLC entity can be configured to perform data transfer in one of the following three modes: Transp

46、arent Mode (TM), Unacknowledged Mode (UM) or Acknowledged Mode (AM). Consequently, an RLC entity is categorized as a TM RLC entity, an UM RLC entity or an AM RLC entity depending on the mode of data transfer that the RLC entity is configured to provide. A TM RLC entity is configured either as a tran

47、smitting TM RLC entity or a receiving TM RLC entity. The transmitting TM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer receiving TM RLC entity via lower layers. The receiving TM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer transmittin

48、g TM RLC entity via lower layers. An UM RLC entity is configured either as a transmitting UM RLC entity or a receiving UM RLC entity. The transmitting UM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer receiving UM RLC entity via lower layers. The receiving UM RLC entity

49、 delivers RLC SDUs to upper layer and receives RLC PDUs from its peer transmitting UM RLC entity via lower layers. An AM RLC entity consists of a transmitting side and a receiving side. The transmitting side of an AM RLC entity receives RLC SDUs from upper layer and sends RLC PDUs to its peer AM RLC entity via lower layers. The receiving side of an AM RLC entity delivers RLC SDUs to upper layer and receives RLC PDUs from its peer AM RLC entity via lower layers. Figure 1 illustrates the overview model of the RLC sub layer. Figure 4.2.1-1: Overview model o