ETSI TS 136 323-2016 LTE Evolved Universal Terrestrial Radio Access (E-UTRA) Packet Data Convergence Protocol (PDCP) specification (V13 3 1 3GPP TS 36 323 version 13 3 1 Release 13.pdf

1、 ETSI TS 1Evolved Universal TPacket Data Converg(3GPP TS 36.3TECHNICAL SPECIFICATION136 323 V13.1.0 (2016LTE; l Terrestrial Radio Access (E-rgence Protocol (PDCP) spec.323 version 13.1.0 Release 1316-04) UTRA); ecification 13) ETSI ETSI TS 136 323 V13.1.0 (2016-04)13GPP TS 36.323 version 13.1.0 Rele

2、ase 13Reference RTS/TSGR-0236323vd10 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 noti

3、ce 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 modified without the prior written authoriza

4、tion 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 a

5、ware 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 comment to one of the following services:

6、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 ETSI. The content of the PDF version shall no

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

8、 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 323 V13.1.0 (2016-04)23GPP TS 36.323 version 13.1.0 Re

9、lease 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

10、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 investigation, including IPR

11、 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 This Technical Specification (TS) has been p

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

13、 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“ are to be interpreted as described in claus

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

15、reword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 General . 8g34.1 Introduction 8g34.2 PDCP architecture 8g34.2.1 PDCP structure . 8g34.2.2 PDCP entities 9g34.3 Services 10g34.3.1 Services

16、provided to upper layers . 10g34.3.2 Services expected from lower layers 10g34.4 Functions 11g34.5 Data available for transmission 11g35 PDCP procedures . 12g35.1 PDCP Data Transfer Procedures 12g35.1.1 UL Data Transfer Procedures . 12g35.1.2 DL Data Transfer Procedures . 13g35.1.2.1 Procedures for

17、DRBs. 13g35.1.2.1.1 Void . 13g35.1.2.1.2 Procedures for DRBs mapped on RLC AM when the reordering function is not used . 13g35.1.2.1.2a RN procedures for DRBs mapped on RLC AM 14g35.1.2.1.3 Procedures for DRBs mapped on RLC UM 14g35.1.2.1.3a RN procedures for DRBs mapped on RLC UM 15g35.1.2.1.4 Proc

18、edures for DRBs mapped on RLC AM and for LWA bearers when the reordering function is used 15g35.1.2.1.4.1 Procedures when a PDCP PDU is received from the lower layers 15g35.1.2.1.4.2 Procedures when t-Reordering expires 16g35.1.2.1.4.3 Procedures when the value of t-Reordering is reconfigured 16g35.

19、1.2.2 Procedures for SRBs . 16g35.1.3 SL Data Transmission Procedures 17g35.1.4 SL Data Reception Procedures . 17g35.2 Re-establishment procedure . 17g35.2.1 UL Data Transfer Procedures . 18g35.2.1.1 Procedures for DRBs mapped on RLC AM 18g35.2.1.2 Procedures for DRBs mapped on RLC UM 18g35.2.1.3 Pr

20、ocedures for SRBs . 18g35.2.2 DL Data Transfer Procedures . 19g35.2.2.1 Procedures for DRBs mapped on RLC AM while the reordering function is not used . 19g35.2.2.1a Procedures for DRBs mapped on RLC AM while the reordering function is used . 19g35.2.2.2 Procedures for DRBs mapped on RLC UM 19g35.2.

21、2.3 Procedures for SRBs . 19g35.3 PDCP Status Report . 20g35.3.1 Transmit operation 20g35.3.2 Receive operation . 20g35.4 PDCP discard . 20g35.5 Header Compression and Decompression 20g3ETSI ETSI TS 136 323 V13.1.0 (2016-04)43GPP TS 36.323 version 13.1.0 Release 135.5.1 Supported header compression

22、protocols and profiles 20g35.5.2 Configuration of header compression . 21g35.5.3 Protocol parameters 21g35.5.4 Header compression 22g35.5.5 Header decompression 22g35.5.6 PDCP Control PDU for interspersed ROHC feedback packet 22g35.5.6.1 Transmit Operation . 22g35.5.6.2 Receive Operation . 22g35.6 C

23、iphering and Deciphering. 22g35.6.1 SL Ciphering and Deciphering for one-to-many communication . 23g35.6.2 SL Ciphering and Deciphering for one-to-one communication 23g35.7 Integrity Protection and Verification 23g35.8 Handling of unknown, unforeseen and erroneous protocol data 24g35.9 PDCP Data Rec

24、overy procedure 24g35.10 Status report for LWA 24g35.10.1 Transmit operation 24g35.10.2 LWA status report . 25g36 Protocol data units, formats and parameters . 25g36.1 Protocol data units 25g36.1.1 PDCP Data PDU . 25g36.1.2 PDCP Control PDU 26g36.2 Formats . 26g36.2.1 General 26g36.2.2 Control plane

25、 PDCP Data PDU 26g36.2.3 User plane PDCP Data PDU with long PDCP SN (12 bits) . 26g36.2.4 User plane PDCP Data PDU with short PDCP SN (7 bits) 27g36.2.5 PDCP Control PDU for interspersed ROHC feedback packet 27g36.2.6 PDCP Control PDU for PDCP status report . 27g36.2.7 Void 28g36.2.8 RN user plane P

26、DCP Data PDU with integrity protection 29g36.2.9 User plane PDCP Data PDU with extended PDCP SN (15 bits) 29g36.2.10 User plane PDCP Data PDU for SLRB 29g36.2.11 User plane PDCP Data PDU with further extended PDCP SN (18 bits) 30g36.2.12 PDCP Control PDU for LWA status report 31g36.3 Parameters 32g3

27、6.3.1 General 32g36.3.2 PDCP SN 32g36.3.3 Data . 32g36.3.4 MAC-I 33g36.3.5 COUNT 33g36.3.6 R . 33g36.3.7 D/C 33g36.3.8 PDU type 33g36.3.9 FMS 34g36.3.10 Bitmap 34g36.3.11 Interspersed ROHC feedback packet 34g36.3.12 PGK Index 34g36.3.13 PTK Identity . 34g36.3.14 SDU Type . 34g36.3.15 KD-sessID . 35g

28、36.3.16 NMP 35g36.3.17 HRW . 35g36.3.18 P 35g37 Variables, constants and timers 35g37.1 State variables 35g37.2 Timers 36g37.3 Constants 36g3Annex A (informative): Change history . 38g3History 40 ETSI ETSI TS 136 323 V13.1.0 (2016-04)53GPP TS 36.323 version 13.1.0 Release 13Foreword This Technical S

29、pecification 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 TSG modify the contents of the present document, it will be re-released by the T

30、SG 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 indicates TSG approved document under change control. y the second digit is incremente

31、d 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 136 323 V13.1.0 (2016-04)63GPP TS 36.323 version 13.1.0 Release 131 Scope The present document pro

32、vides the description of the Packet Data Convergence Protocol (PDCP). 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, versi

33、on 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 implicitly refers to the latest version of that

34、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 Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description“. 3 3GPP TS 36.331: “Evolved Univ

35、ersal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification“. 4 3GPP TS 36.321: “Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) protocol specification“. 5 3GPP TS 36.322: “Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Link

36、 Control (RLC) protocol specification“. 6 3GPP TS 33.401: “3GPP System Architecture Evolution: Security Architecture“. 7 IETF RFC 4995: “The RObust Header Compression (ROHC) Framework“. 8 IETF RFC 4996: “RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)“. 9 IETF RFC 3095: “RObust Hea

37、der Compression (ROHC): Framework and four profiles: RTP, UDP, ESP and uncompressed“. 10 IETF RFC 3843: “RObust Header Compression (ROHC): A Compression Profile for IP“. 11 IETF RFC 4815: “RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095“. 12 IETF RFC 5225: “RObust Header

38、 Compression (ROHC) Version 2: Profiles for RTP, UDP, IP, ESP and UDP Lite. 13 3GPP TS 33.303: Proximity-based Services; Security Aspects. 14 3GPP TS 23.303: Proximity-based Services; Stage 2. ETSI ETSI TS 136 323 V13.1.0 (2016-04)73GPP TS 36.323 version 13.1.0 Release 133 Definitions and abbreviati

39、ons 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 same term, if any, in TR 21.905 1. Split bearer: in dual connectivity, a bearer who

40、se radio protocols are located in both the MeNB and the SeNB to use both MeNB and SeNB resources. LWA bearer: in LTE-WLAN Aggregation, a bearer whose radio protocols are located in both the eNB and the WLAN to use both eNB and WLAN resources. 3.2 Abbreviations For the purposes of the present documen

41、t, 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. AM Acknowledged Mode ARP Address Resolution Protocol CID Context IdentifierDRB Data Radio Bearer c

42、arrying user plane data EPS Evolved Packet System E-UTRA Evolved UMTS Terrestrial Radio Access E-UTRAN Evolved UMTS Terrestrial Radio Access Network eNB E-UTRAN Node B FMS First missing PDCP SN HFN Hyper Frame Number HRW Highest Received PDCP SN on WLAN IETF Internet Engineering Task Force IP Intern

43、et Protocol L2 Layer 2 (data link layer) L3 Layer 3 (network layer) LWA LTE-WLAN AggregationMAC Medium Access Control MAC-I Message Authentication Code for Integrity MCG Master Cell Group NMP Number of Missing PDUs PDCP Packet Data Convergence Protocol PDU Protocol Data Unit PEK ProSe Encryption Key

44、 PGK ProSe Group Key ProSe Proximity-based Services PTK ProSe Traffic Key R Reserved RB Radio BearerRFC Request For Comments RLC Radio Link ControlRN Relay Node ROHC RObust Header Compression RRC Radio Resource Control RTP Real Time Protocol SAP Service Access PointSCG Secondary Cell Group SDU Servi

45、ce Data Unit SLRB Sidelink Radio Bearer carrying Sidelink Communication data SN Sequence Number SRB Signalling Radio Bearer carrying control plane data ETSI ETSI TS 136 323 V13.1.0 (2016-04)83GPP TS 36.323 version 13.1.0 Release 13TCP Transmission Control Protocol UDP User Datagram Protocol UE User

46、Equipment UM Unacknowledged Mode X-MAC Computed MAC-I 4 General 4.1 Introduction The present document describes the functionality of the PDCP. Functionality specified for the UE equally applies to the RN for functionality necessary for the RN. There is also functionality which is only applicable to

47、the RN in its communication with the E-UTRAN, in which case the specification denotes the RN instead of the UE. RN-specific behaviour is not applicable to the UE. The functionality specified for the UE applies to communication on Uu interface and PC5 interface 14. 4.2 PDCP architecture 4.2.1 PDCP st

48、ructure Figure 4.2.1.1 represents one possible structure for the PDCP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in 2. Figure 4.2.1.1 - PDCP layer, structure view Each RB (i.e. DRB, SLRB and SRB, except for SRB0) is assoc

49、iated with one PDCP entity. Each PDCP entity is associated with one or two (one for each direction) RLC entities depending on the RB characteristic (i.e. uni-directional or bi-directional) and RLC mode. For split bearers, each PDCP entity is associated with two AM RLC entities. The PDCP entities are located in the PDCP sublayer. The PDCP sublayer is configured by upper layers 3. ETSI ETSI TS 136 323 V13.1.0 (2016-04)93GPP TS 36.323 version 13.1.0 Release 134.2.2 PDCP entities The PDCP entities are located in the PDCP sublay