1、 ETSI TS 136 360 V14.0.0 (2017-04) LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-WLAN Aggregation Adaptation Protocol (LWAAP) specification (3GPP TS 36.360 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 136 360 V14.0.0 (2017-04)13GPP TS 36.360 version 14.0.0 Release
2、14Reference RTS/TSGR-0236360ve00 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following serv
6、ices: 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 sh
7、all 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 are Trade Marks of ETSI registered f
8、or 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 by the GSM Association. ETSI ETSI
9、 TS 136 360 V14.0.0 (2017-04)23GPP TS 36.360 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 available for ETSI members and no
10、n-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 server (https:/ipr.etsi.org/). Pu
11、rsuant 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 become, essential to the present d
12、ocument. 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 should be interpreted as being referenc
13、es 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“, “need not“, “will“, “will not“,
14、“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 360 V14.0.0 (2017-04)33GPP TS 36.360 versio
15、n 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.2 LWAAP architecture 6g34.2.1 LWA
16、AP 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 7g35.1 Data transfer procedures . 7g35.1.1 DL data transfer procedures 7g35.1.2 UL data transfer procedures 7g35.2 Handling of unknown, unforeseen an
17、d erroneous protocol data 8g36 Protocol data units, formats and parameters . 8g36.1 Protocol data units 8g36.1.1 General 8g36.1.2 LWAAP data PDU 8g36.2 Formats and parameters 8g36.2.1 LWAAP header 8g3Annex A (informative): Change history . 10g3History 11g3ETSI ETSI TS 136 360 V14.0.0 (2017-04)43GPP
18、TS 36.360 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 approval. Should the TSG modify the conte
19、nts 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 approval; 3 or greater indicates TSG approved doc
20、ument 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 TS 136 360 V14.0.0 (2017-04)53GPP TS 36.3
21、60 version 14.0.0 Release 141 Scope The present document specifies the E-UTRA LTE-WLAN Aggregation Adaptation Protocol (LWAAP). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specif
22、ic (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 document), a non-spe
23、cific 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.323: “E-UTRA PDCP specification“. 4 3GPP TS
24、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 precedence over the definition of the s
25、ame term, if any, in TR 21.905 1. LWA bearer: a bearer used in LTE-WLAN Aggregation, as defined in TS 36.300 2. 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 Radio Ac
26、cess E-UTRAN Evolved UMTS Terrestrial Radio Access Network LWAAP LTE-WLAN Aggregation Adaptation Protocol PDCP Packet Data Convergence Protocol PDU Protocol Data Unit RRC Radio Resource Control SAP Service Access Point SDU Service Data Unit UE User EquipmentUL UpLink ETSI ETSI TS 136 360 V14.0.0 (20
27、17-04)63GPP TS 36.360 version 14.0.0 Release 144 General 4.1 Introduction The objective is to describe the LWAAP architecture and the LWAAP entities from a functional point of view. 4.2 LWAAP architecture 4.2.1 LWAAP entities The description in this sub clause is a model and does not specify or rest
28、rict implementations. RRC is generally in control of the LWAAP configuration. Functions of the LWAAP sublayer are performed by LWAAP entities. For an LWAAP entity configured at the eNB, there is a peer LWAAP entity configured at the UE and vice versa. For all LWA bearers, there is one LWAAP entity i
29、n the eNB and one LWAAP entity in the UE. An LWAAP entity receives/delivers LWAAP SDUs from/to upper layers (i.e. PDCP) and sends/receives LWAAP PDUs to/from its peer LWAAP entity via WLAN: - At the transmitting side, when an LWAAP entity receives an LWAAP SDU from upper layers, it constructs the co
30、rresponding LWAAP PDU and delivers it to lower layers; - At the receiving side, when an LWAAP entity receives an LWAAP PDU from lower layers, it reassembles the corresponding LWAAP SDU and delivers it to upper layers. Figure 4.2.1-1 illustrates the overview model of the LWAAP sublayer. Figure 4.2.1-
31、1: Overview model of the LWAAP sublayer ETSI ETSI TS 136 360 V14.0.0 (2017-04)73GPP TS 36.360 version 14.0.0 Release 14An LWAAP entity delivers/receives the following LWAAP PDU to/from a lower layer entity: - LWAAP data PDU. 4.3 Services 4.3.1 Services provided to upper layers The following services
32、 are provided by LWAAP to upper layers (i.e. PDCP): - transfer of user plane data; 4.3.2 Services expected from lower layers The following services are expected by LWAAP from lower layers: - transfer of user plane data; 4.4 Functions The following functions are supported by the LWAAP sublayer: - tra
33、nsfer of user plane data; - identification of the LWA bearer to which the LWAAP SDU belongs; - enabling or disabling data handling for LWA bearer. 5 Procedures 5.1 Data transfer procedures 5.1.1 DL data transfer procedures When receiving an LWAAP data PDU from lower layers, the LWAAP entity in the U
34、E shall: - identify the upper layer entity to which the LWAAP SDU is destined based on the DRB ID included in the LWAAP header; - if the DRB ID belongs to LWA bearer for which DL data transfer procedures are enabled: - reassemble the LWAAP SDU from the LWAAP data PDU by removing the LWAAP header fro
35、m the LWAAP data PDU; - deliver the reassembled LWAAP SDU to the upper layer entity identified by the DRB ID. - else: - discard the LWAAP data PDU. 5.1.2 UL data transfer procedures When receiving an LWAAP data SDU from upper layers, the LWAAP entity in the UE shall: - identify the DRB ID of the upp
36、er layer entity from which the LWAAP SDU is received; - assemble the LWAAP data PDU from the LWAAP SDU by adding the LWAAP header to the LWAAP SDU; ETSI ETSI TS 136 360 V14.0.0 (2017-04)83GPP TS 36.360 version 14.0.0 Release 14- deliver the assembled LWAAP data PDU to the lower layers. 5.2 Handling
37、of unknown, unforeseen and erroneous protocol data When an LWAAP entity receives an LWAAP PDU that contains reserved or invalid values, the LWAAP entity shall: - discard the received PDU. 6 Protocol data units, formats and parameters 6.1 Protocol data units 6.1.1 General An LWAAP PDU is a bit string
38、 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 which 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 mo
39、re 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 field within an LWAAP 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. A
40、n LWAAP SDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. An LWAAP SDU is included into an LWAAP PDU from the first bit onward. The LWAAP entity shall ignore the value of Reserved bits in downlink LWAAP PDUs. Only one type of LWAAP PDU is defined, i.e. LWAAP data PDU. 6.1
41、.2 LWAAP data PDU An LWAAP PDU consists of an LWAAP header and a Data field, as described in Figure 6.1.2-1. An LWAAP header is one byte, and consists of the four header fields R/R/R/DRBID. A Data field is of variable size, and consists of an LWAAP SDU. Figure 6.1.2-1: LWAAP data PDU 6.2 Formats and
42、 parameters 6.2.1 LWAAP header The LWAAP header consists of the following fields: - R: Reserved bit, set to “0“. The R field size is 1 bit; ETSI ETSI TS 136 360 V14.0.0 (2017-04)93GPP TS 36.360 version 14.0.0 Release 14- DRBID: The Data Radio Bearer ID field indicates the RRC configured DRB identity
43、 to which the corresponding LWAAP SDU belongs. The DRBID field size is 5 bits. ETSI ETSI TS 136 360 V14.0.0 (2017-04)103GPP TS 36.360 version 14.0.0 Release 14Annex A (informative): Change history Change history Date TSG # TSG Doc. CR Rev Cat Subject/Comment New version 2016-02 RAN2#93 R2-161087 - -
44、 draft TS 36.360 v0.0.0 on LTE-WLAN Aggregation Adaptation Protocol (LWAAP) specification after e-mail discussion “92#42LTE/WLAN New specification (LG)” 0.0.0 2016-02 RAN2#93 R2-161787 - - draft TS 36.360 v0.0.1 on LTE-WLAN Aggregation Adaptation Protocol (LWAAP) specification 0.0.1 2016-02 RAN2#93
45、R2-161986 - - draft TS 36.360 v0.0.2 on LTE-WLAN Aggregation Adaptation Protocol (LWAAP) specification 0.0.2 2016-02 RAN2#93 R2-162023 - - draft TS 36.360 v0.1.0 on LTE-WLAN Aggregation Adaptation Protocol (LWAAP) specification 0.1.0 2016-02 RAN2#93 R2-162024 - - draft TS 36.360 v1.0.0 on LTE-WLAN A
46、ggregation Adaptation Protocol (LWAAP) specification 1.0.0 2016-03 RP-71 RP-160496 - - Approved at TSG RAN#71 and put under Change Control 13.0.0 2017-03 RP-75 RP-170651 0005 2 F Clarification on data handling for LWA bearer 13.1.0 RP-75 RP-170628 0006 2 B Introduction of Enhanced LTE-WLAN Aggregation (eLWA) 14.0.0 ETSI ETSI TS 136 360 V14.0.0 (2017-04)113GPP TS 36.360 version 14.0.0 Release 14History Document history V14.0.0 April 2017 Publication
