1、 ETSI TS 136 361 V14.0.0 (2017-05) LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); LTE/WLAN Radio Level Integration Using IPsec Tunnel (LWIP) encapsulation; Protocol specification (3GPP TS 36.361 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 136 361 V14.0.0 (2017-05)13GPP
2、 TS 36.361 version 14.0.0 Release 14Reference RTS/TSGR-0236361ve00 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
3、 (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 modified witho
4、ut 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. Users of th
5、e 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your co
6、mment 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 ETSI.
7、 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 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo ar
8、e 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. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned
9、 by the GSM Association. ETSI ETSI TS 136 361 V14.0.0 (2017-05)23GPP TS 36.361 version 14.0.0 Release 14Intellectual 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
10、 available for ETSI members and non-members, and can be 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
11、 server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR 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
12、become, essential to the present document. Foreword This 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 shoul
13、d 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. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“
14、, “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 NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 136 361 V14.0
15、.0 (2017-05)33GPP TS 36.361 version 14.0.0 Release 14Contents 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 Introduction 6g34
16、.2 LWIPEP architecture 6g34.2.1 LWIPEP entities . 6g34.3 Services 7g34.3.1 Services provided to upper layers . 7g34.3.2 Services expected from lower layers 7g34.4 Functions 7g35 Procedures 8g35.1 Data transfer procedures . 8g35.1.1 UL data transfer procedures 8g35.1.2 DL data transfer procedures 8g3
17、5.2 Handling of unknown, unforeseen and erroneous protocol data 8g36 Protocol data units, formats and parameters . 8g36.1 Protocol data units 8g36.1.1 General 8g36.1.2 LWIPEP data PDU . 8g36.2 Formats and parameters 9g36.2.1 LWIPEP header 9g3Annex A (informative): Change history . 10g3History 11g3ET
18、SI ETSI TS 136 361 V14.0.0 (2017-05)43GPP TS 36.361 version 14.0.0 Release 14Foreword 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
19、 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 presented to TSG for approva
20、l; 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 in the document. ETSI ETSI
21、 TS 136 361 V14.0.0 (2017-05)53GPP TS 36.361 version 14.0.0 Release 141 Scope The present document specifies the LWIP Encapsulation Protocol. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are
22、 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 the case of a reference to a 3GPP document (including a GSM docume
23、nt), 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: “E-UTRA and E-UTRAN Overall Description; Stage 2“. 3 3GPP TS 36.331: “E-UTRA RRC Protocol spec
24、ification“. 4 IETF RFC 2784: “Generic Routing Encapsulation (GRE)“. 5 IETF RFC 2890: “Key and Sequence Number Extensions to GRE“. 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.
25、 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 following abbreviations apply: DL DownLink DRB Data Radio Bearer eNB E-UTRAN Node B E-UTRA Evolved UMTS Terrestrial R
26、adio Access E-UTRAN Evolved UMTS Terrestrial Radio Access Network IP Internet Protocol LWIP LTE/WLAN Radio Level Integration Using IPsec Tunnel LWIPEP LWIP Encapsulation Protocol GRE Generic Routing and Encapsulation PDCP Packet Data Convergence Protocol PDU Protocol Data Unit RRC Radio Resource Con
27、trol SAP Service Access Point SDU Service Data Unit UE User EquipmentETSI ETSI TS 136 361 V14.0.0 (2017-05)63GPP TS 36.361 version 14.0.0 Release 144 General 4.1 Introduction The objective is to describe the use of encapsulation for IP packets over the LWIP Tunnel as defined in TS 36.300 2 and TS 36
28、.331 3. 4.2 LWIPEP architecture 4.2.1 LWIPEP entities The description in this sub clause is a model and does not specify or restrict implementations. RRC is in control of the LWIPEP configuration. Functions of the LWIPEP sublayer are performed by LWIPEP entities. For an LWIPEP entity configured at t
29、he eNB, there is a peer LWIPEP entity configured at the UE and vice versa. The LWIPEP entity responsible for encapsulating LWIPEP SDUs is referred to as the transmitter. The LWIPEP entity responsible for decapsulating LWIPEP PDUs is referred to as the receiver. An LWIPEP entity receives/delivers LWI
30、PEP SDUs from/to upper layers (i.e. IP) and sends/receives LWIPEP PDUs to/from its peer LWIPEP entity via an LWIP Tunnel. - At the transmitting side, when an LWIPEP entity receives an LWIPEP SDU from upper layers, it constructs the corresponding LWIPEP PDU and delivers it to lower layers; - At the r
31、eceiving side, when an LWIPEP entity receives an LWIPEP PDU from lower layers, it reassembles the corresponding LWIPEP SDU and delivers it to upper layers. Figure 4.2.1-1 illustrates the overview model of the LWIPEP sublayer. ETSI ETSI TS 136 361 V14.0.0 (2017-05)73GPP TS 36.361 version 14.0.0 Relea
32、se 14Figure 4.2.1-1: Overview model of the LWIPEP sublayer An LWIPEP entity delivers/receives the following LWIPEP PDU to/from a lower layer entity: - LWIPEP data PDU. 4.3 Services 4.3.1 Services provided to upper layers The following services are provided by LWIPEP to upper layers (i.e. IP): - tran
33、sfer of user plane data; 4.3.2 Services expected from lower layers The following services are expected by LWIPEP from lower layers (i.e. LWIP Tunnel): - transfer of user plane data; 4.4 Functions The following functions are supported by the LWIPEP sublayer: - transfer of user plane data; - identific
34、ation of the DRB identity to which the LWIPEP SDU belongs. ETSI ETSI TS 136 361 V14.0.0 (2017-05)83GPP TS 36.361 version 14.0.0 Release 145 Procedures 5.1 Data transfer procedures 5.1.1 UL data transfer procedures When receiving an LWIPEP SDU from upper layers, the LWIPEP entity shall form the LWIPE
35、P PDU as described in Section 6.1. 5.1.2 DL data transfer procedures When receiving an LWIPEP SDU from lower layers, the LWIPEP entity shall: - if configured by upper layers to enable aggregation in DL: - interpret the LWIPEP PDU as having both Key and Sequence Number fields included as described in
36、 Section 6.1 - reorder received packets according to the Sequence Number field before delivering them to higher layers as specified in RFC 2890 5; 5.2 Handling of unknown, unforeseen and erroneous protocol data When an LWIPEP entity receives an LWIPEP PDU that contains reserved or invalid values, th
37、e LWIPEP entity shall: - discard the received PDU. 6 Protocol data units, formats and parameters 6.1 Protocol data units 6.1.1 General An LWIPEP PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. In the figures in subclause 6.1, bit strings are represented by tables in whi
38、ch the most significant bit is the leftmost bit of the first line of the table, the least significant bit is the rightmost bit on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. The bit order of each parameter
39、 field within an LWIPEP PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit. An LWIPEP SDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. An LWIPEP SDU is included into an LWIPEP PDU fro
40、m the first bit onward. Only one type of LWIPEP PDU is defined, i.e. LWIPEP data PDU. 6.1.2 LWIPEP data PDU An LWIPEP data PDU consists of the LWIPEP header and the LWIPEP SDU, as described in Figure 6.1.2-1. The LWIPEP header is populated as described in 6.2.1. ETSI ETSI TS 136 361 V14.0.0 (2017-05
41、)93GPP TS 36.361 version 14.0.0 Release 14Figure 6.1.2-1: LWIPEP data PDU 6.2 Formats and parameters 6.2.1 LWIPEP header The LWIPEP Header is a GRE header as specified in RFC 2890 5 and has a fixed size of eight bytes (if only the Key field is included) or twelve bytes (if both the Key and Sequence
42、Number fields are included). The transmitter shall set the 5 LSBs of the Key field in the GRE header to the DRB Identity associated with the LWIPEP SDU and set the remaining MSBs to 0. If instructed by RRC to enable aggregation in UL or DL, the transmitter shall in addition include the Sequence Numb
43、er field as specified by RFC 2890 5 in the LWIP header. All other optional fields are unused, and the values of other fields shall be set as specified in RFC 2784 4 and RFC 2890 5. ETSI ETSI TS 136 361 V14.0.0 (2017-05)103GPP TS 36.361 version 14.0.0 Release 14Annex A (informative): Change history C
44、hange history Date TSG # TSG Doc. CR Rev Subject/Comment Old New 02-2016 RAN#71 RP-160238 - - TS 00.001 v1.0.0 on LTE/WLAN Radio Level Integration Using IPsec Tunnel (LWIP) encapsulation; Protocol specification - This new spec is based on RAN2 agreed Tdoc R2-161974in RAN2#93 - spec number 00.001 wil
45、l be changed properly after RAN#71 approval 0.0.0 1.0.0 03-2016 RAN#71 RP-160607 - - Spec number added 1.0.0 1.0.1 03-2016 RAN#71 RP-160607 - - Approved at TSG RAN#71 and put under Change Control 1.0.1 13.0.0 06-2016 RP-72 RP-161080 0001 1 Corrections to LWIPEP specification 13.0.0 13.1.0 09-2016 RP
46、-73 RP-161757 0002 1 Clarification on LWIPEP 13.1.0 13.2.0 RP-73 RP-161757 0003 - Correction on GRE header size 13.1.0 13.2.0 12-2016 RP-74 RP-162327 0004 1 Modifications to LWIPEP due to LWIP aggregation 13.2.0 14.0.0 ETSI ETSI TS 136 361 V14.0.0 (2017-05)113GPP TS 36.361 version 14.0.0 Release 14History Document history V14.0.0 May 2017 Publication
