KR20170113767A - Methods for operating PDCP in LWA environment and apparatus thereof - Google Patents

Abstract

The present invention relates to an LWA configuration method and apparatus for supporting high-speed WLAN technology in an LTE-WLAN aggregation framework using base station radio resources and / or WLAN radio resources, thereby improving user throughput. In particular, the present invention provides a method for processing data by a terminal, comprising: constructing a LWA bearer capable of efficiently supporting high-speed WLAN technology such as 802.11ax, 802.11ad, and 802.11ay to provide user throughput; And processing the data.

Description

[0001] The present invention relates to a method and apparatus for operating PDCP in an LWA environment,

The present invention relates to an LWA configuration method and apparatus for supporting high-speed WLAN technology in an LTE-WLAN aggregation framework using base station radio resources and / or WLAN radio resources, thereby improving user throughput.

The present invention provides a method of processing data by a terminal, comprising the steps of: constructing a LWA bearer capable of efficiently supporting high-speed WLAN technology such as 802.11ax, 802.11ad and 802.11ay to provide user throughput; The method comprising the steps of:

Figure 1 shows a LWA radio protocol architecture diagram for a collocated scenario.
FIG. 2 shows a structure of a LWA radio protocol for a non-collocated scenario.
FIG. 3 shows LWA UE-EUTRA-Capability information elements and fields.
4 shows the REL-13 LWA UL Layer 2 structure.
5 shows an example of a LWA radio protocol structure for uplink transmission.
6 shows a functional diagram of the PDCP layer.
7 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
FIG. 8 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

Herein, the MTC terminal may mean a terminal supporting low cost (or low complexity) or a terminal supporting coverage enhancement. In this specification, the MTC terminal may mean a terminal supporting low cost (or low complexity) and coverage enhancement. Alternatively, the MTC terminal may refer to a terminal defined in a specific category for supporting low cost (or low complexity) and / or coverage enhancement.

In other words, the MTC terminal in this specification may mean a newly defined 3GPP Release-13 low cost (or low complexity) UE category / type for performing LTE-based MTC-related operations. Alternatively, the MTC terminal may support enhanced coverage over the existing LTE coverage or a UE category / type defined in the existing 3GPP Release-12 or lower that supports low power consumption, or a newly defined Release-13 low cost low complexity UE category / type.

The wireless communication system in the present invention is widely deployed to provide various communication services such as voice, packet data and the like. A wireless communication system includes a user equipment (UE) and a base station (BS, or eNB). The user terminal in this specification is a comprehensive concept of a terminal in wireless communication. It is a comprehensive concept which means a mobile station (MS), a user terminal (UT), an SS (User Equipment) (Subscriber Station), a wireless device, and the like.

A base station or a cell generally refers to a station that communicates with a user terminal and includes a Node-B, an evolved Node-B (eNB), a sector, a Site, a BTS A base transceiver system, an access point, a relay node, a remote radio head (RRH), a radio unit (RU), and a small cell.

That is, the base station or the cell in this specification is interpreted as a comprehensive meaning indicating a partial region or function covered by BSC (Base Station Controller) in CDMA, NodeB in WCDMA, eNB in LTE or sector (site) And covers various coverage areas such as megacell, macrocell, microcell, picocell, femtocell and relay node, RRH, RU, and small cell communication range.

Since the various cells listed above exist in the base station controlling each cell, the base station can be interpreted into two meanings. i) the device itself providing a megacell, macrocell, microcell, picocell, femtocell, small cell in relation to the wireless region, or ii) indicating the wireless region itself. i indicate to the base station all devices that are controlled by the same entity or that interact to configure the wireless region as a collaboration. An eNB, an RRH, an antenna, an RU, an LPN, a point, a transmission / reception point, a transmission point, a reception point, and the like are exemplary embodiments of a base station according to a configuration method of a radio area. ii) may indicate to the base station the wireless region itself that is to receive or transmit signals from the perspective of the user terminal or from a neighboring base station.

Therefore, a base station is collectively referred to as a base station, collectively referred to as a megacell, macrocell, microcell, picocell, femtocell, small cell, RRH, antenna, RU, low power node do.

Herein, the user terminal and the base station are used in a broad sense as the two transmitting and receiving subjects used to implement the technical or technical idea described in this specification, and are not limited by a specific term or word. The user terminal and the base station are used in a broad sense as two (uplink or downlink) transmitting and receiving subjects used to implement the technology or technical idea described in the present invention, and are not limited by a specific term or word. Here, an uplink (UL, or uplink) means a method of transmitting / receiving data to / from a base station by a user terminal, and a downlink (DL or downlink) .

There are no restrictions on multiple access schemes applied to wireless communication systems. Various multiple access schemes such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), OFDM-FDMA, OFDM- Can be used. An embodiment of the present invention can be applied to asynchronous wireless communication that evolves into LTE and LTE-advanced via GSM, WCDMA, and HSPA, and synchronous wireless communication that evolves into CDMA, CDMA-2000, and UMB. The present invention should not be construed as limited to or limited to a specific wireless communication field and should be construed as including all technical fields to which the idea of the present invention can be applied.

A TDD (Time Division Duplex) scheme in which uplink and downlink transmissions are transmitted using different time periods, or an FDD (Frequency Division Duplex) scheme in which they are transmitted using different frequencies can be used.

In systems such as LTE and LTE-advanced, a standard is constructed by configuring uplink and downlink based on a single carrier or carrier pair. The uplink and the downlink are divided into a Physical Downlink Control Channel (PDCCH), a Physical Control Format Indicator CHannel (PCFICH), a Physical Hybrid ARQ Indicator CHannel, a Physical Uplink Control CHannel (PUCCH), an Enhanced Physical Downlink Control Channel (EPDCCH) Transmits control information through the same control channel, and is configured with data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel), and transmits data.

On the other hand, control information can also be transmitted using EPDCCH (enhanced PDCCH or extended PDCCH).

In this specification, a cell refers to a component carrier having a coverage of a signal transmitted from a transmission point or a transmission point or transmission / reception point of a signal transmitted from a transmission / reception point, and a transmission / reception point itself .

The wireless communication system to which the embodiments are applied may be a coordinated multi-point transmission / reception system (CoMP system) or a coordinated multi-point transmission / reception system in which two or more transmission / reception points cooperatively transmit signals. antenna transmission system, or a cooperative multi-cell communication system. A CoMP system may include at least two multipoint transmit and receive points and terminals.

The multi-point transmission / reception point includes a base station or a macro cell (hereinafter referred to as 'eNB'), and at least one mobile station having a high transmission power or a low transmission power in a macro cell area, Lt; / RTI >

Hereinafter, a downlink refers to a communication or communication path from a multipoint transmission / reception point to a terminal, and an uplink refers to a communication or communication path from a terminal to a multiple transmission / reception point. In the downlink, a transmitter may be a part of a multipoint transmission / reception point, and a receiver may be a part of a terminal. In the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of multiple transmission / reception points.

Hereinafter, a situation in which a signal is transmitted / received through a channel such as PUCCH, PUSCH, PDCCH, EPDCCH, and PDSCH is expressed as 'PUCCH, PUSCH, PDCCH, EPDCCH and PDSCH are transmitted and received'.

In the following description, an indication that a PDCCH is transmitted or received or a signal is transmitted or received via a PDCCH may be used to mean transmitting or receiving an EPDCCH or transmitting or receiving a signal through an EPDCCH.

That is, the physical downlink control channel described below may mean a PDCCH, an EPDCCH, or a PDCCH and an EPDCCH.

Also, for convenience of description, EPDCCH, which is an embodiment of the present invention, may be applied to the portion described with PDCCH, and EPDCCH may be applied to the portion described with EPDCCH according to an embodiment of the present invention.

Meanwhile, the High Layer Signaling described below includes RRC signaling for transmitting RRC information including RRC parameters.

The eNB performs downlink transmission to the UEs. The eNB includes a physical downlink shared channel (PDSCH) as a main physical channel for unicast transmission, downlink control information such as scheduling required for reception of a PDSCH, A physical downlink control channel (PDCCH) for transmitting scheduling grant information for transmission in a Physical Uplink Shared Channel (PUSCH). Hereinafter, the transmission / reception of a signal through each channel will be described in a form in which the corresponding channel is transmitted / received.

high speed WLAN  Technology

The IEEE 802.11 specification, which provides WLAN technology, is also evolving continuously with the user's high-speed throughput requirements.

802.11ax increases frequency efficiency over the existing 802.11 technology in the 2.4GHz and 5GHz bands. To do this, we concentrate on dense deployment to provide scheduled uplinks and theoretically provide up to 9.6Gbps of throughput. In practical terms, it provides 1.6 Gbps.

802.11ad adds support for the 60 GHz millimeter waveband and delivers up to 7 Gbps.

802.11ay is in the process of improving 802.11ad and provides 20 Gbps speed.

Rel -13 LWA ( LTE - WLAN  Aggregation)

In 3GPP Release 13, LWA for downlink data transmission using both base station and WLAN radio resources was standardized. The LWA has a different wireless protocol architecture depending on the LWA backhaul scenario and how the bearer is set up.

There are two bearer types for LWA as shown in FIG. 1 and FIG.

A separate LWA bearer represents a bearer where the radio protocol is present in both the base station and the WLAN in order to use both the base station radio resource and the WLAN radio resource.

- Switched LWA bearer represents a bearer where the wireless protocol is present in both the base station and the WLAN but uses only WLAN radio resources.

Figure 1 shows a LWA radio protocol architecture diagram for a collocated scenario. FIG. 2 shows a structure of a LWA radio protocol for a non-collocated scenario.

In the LWA operation, the LWAAP (LTE-WLAN Aggregation Adaptation Protocol) generates a LWA PDU containing the DRB identifier for the PDUs transmitted via the WLAN. The WT uses the LWA EtherType to forward data to the terminal via the WLAN. The terminal uses the LWA EtherType to determine whether the received PDU belongs to the LWA bearer. And uses the DRB identifier to determine which LWA bearer the PDU belongs to.

On the downlink, the LWA supports a split bearer operation in which the UE's PDCP sublayer supports in-sequence delivery of upper layer PDUs based on the reordering procedure introduced in dual connectivity. PDCP PDUs in the uplink are sent only through LTE.

Thus, in the Rel-13 LWA bearer, the split LWA bearer and the Switched LWA bearer constitute an LTE Layer 2 entity for uplink transmission to the UE in order to transmit PDCP PDUs on the uplink on the LTE. Therefore, when the terminal is configured with a switched LWA bearer as well as when the split LWA bearer is configured, the UE shall perform the reordering function (refer to 5.1.2.1.4 of TS 36.323) applied to the dual-connectivity split bearer specified in the PDCP standard (TS 36.323) ) Were used. When the reconfiguration of the Switched LWA (reconfiguration from the LTE bearer to the Switched LWA bearer or reconfiguration from the Switched LWA bearer to the LTE bearer) occurs, the UE reorders the PDUs transmitted out of order through the two paths, Could.

Rel -13 LWA  Terminal Capability ( UE  capability)

The LWA parameter UE capability is defined in FIG. 3 as a UE-EUTRA-Capability information element for Rel-13 LWA support.

For example, if the UE is instructed to support both lwa-r13 and lwa-splitbearer on the terminal capability parameter and the base station instructs the BS to support the split LWA bearer (FIG. 1 and FIG. 2) have.

For example, if the base station instructs the base station to support lwa-r13 on the terminal capability parameter (or supports lwa-r13 but sets lwa-splitbearer to be unsupported), the base station It can be seen that the terminal supports switched LWA bearers (in FIG. 1 and FIG. 2).

In another example, when the UE is set to support lwa-BufferSize on the terminal capability parameter, the BS can know that the UE supports the increased L2 buffer size for the LWA and supports the dual-connectivity split bearer.

Thus, even if the terminal supports the increased L2 buffer size for LWA, it only supports buffer size for dual connectivity support based on LTE transmission rate. Accordingly, when using the above-described super-high-speed IEEE 802.11 technologies, a buffer size capable of supporting the corresponding transmission speed is not supported, thereby providing a speed that does not reach the maximum transmission speed.

As described above, in the conventional LWA technology, the UE can transmit data through the LWA irrespective of the IEEE 802.11 technology. However, there is a problem that sufficient high-speed throughput can not be provided for some high-speed 802.11 technologies due to buffer size limitation of the UE.

It is an object of the present invention to provide a LWA bearer configuration method and apparatus capable of efficiently supporting high-speed WLAN technology such as 802.11ax, 802.11ad, and 802.11ay to provide user throughput .

For the RRC Connected terminal, the base station must accurately recognize the terminal capability to provide a suitable configuration for the terminal. Normally, the MME stores UE capability, which consists of UE Radio Access Capability and UE Core Network Capability.

For example, the UE Core Network Capability can be indicated by the UE through NAS signaling (attach procedure, etc.). As another example, the UE Radio Access Capability can be transferred from the UE to the BS using the UE capability transfer procedure and transferred to the MME through the S1 interface. As another example, the UE Radio Access Capability can be indicated to the MME through the NAS signaling (attach procedure, etc.) by the UE and transmitted to the base station via the S1 interface.

If available, the MME transmits UE Radio Access Capability to the base station whenever the UE enters RRC Connected.

As described above, the split LWA bearer and the switched LWA bearer in Rel-13 transmitted the uplink only through the base station radio link.

The base station must be able to recognize that the UE is capable of uplink transmission through the WLAN differently from the Rel-13 LWA, so that the uplink transmission through the WLAN can be configured only for the UE supporting this function. Or an operation related to uplink transmission over the WLAN.

To this end, the base station may define a new information element (field) on the terminal capability parameter to indicate that the terminal supports uplink transmission over the WLAN.

For example, it can be expressed in various ways such as uplink bearer split (or LWA uplink bearer split, uplink split bearer, uplink split, LWA uplink split, uplink bearer split, uplink split bearer). Hereinafter, for convenience of description, the uplink transmission using both the base station radio resource and the WLAN radio resource is referred to as " uplink bearer split ", but it is also within the scope of the present invention to use another term indicating the same concept) You can define information elements to indicate support.

For another example, an information element may be defined to indicate that the WLAN supports uplink transmission. Uplink bearer switch (or LWA uplink bearer switch, uplink switch bearer, uplink switch, LWA uplink switch, uplink bearer switch, uplink switched bearer, etc.) Link bearer switch, but using another term to represent the same concept is also included in the scope of the present invention), it is possible to indicate that uplink transmission through WLAN radio resources is possible.

An information element for instructing to support an uplink transmission using both base station radio resource and WLAN radio resource via an uplink bearer split (in PDCP) and an information element for indicating to support another uplink transmission via WLAN Can be defined.

LWA Uplink  Protocol structure

FIG. 4 shows a UL Layer 2 structure for the LWA bearer of the conventional Release-13. As described above, existing LWA bearers used LTE in both uplinks. Therefore, the existing LTE UL Layer 2 structure can be used as it is.

5 shows an example of the LWA L2 protocol structure for supporting uplink transmission over the WLAN.

5 shows an example of the LWA L2 protocol structure for supporting uplink transmission over the WLAN.

For example, the LWA bearer consisting of an uplink bearer split (described below) may comprise an associated AM RLC entity and a MAC entity configured for uplink BS / base station CG / CG / MCG (denoted as MCG hereinafter for convenience of description) . ≪ / RTI >

As another example, an LWA bearer configured with an uplink bearer switch (described below) may be configured to have an associated AM RLC entity and a MAC entity configured for uplink BS / base station CG / CG / MCG (denoted as MCG below for convenience of description) . ≪ / RTI >

As another example, an LWA bearer configured with an uplink bearer switch (described below) may be configured to have an associated AM RLC entity and a MAC entity configured for uplink BS / base station CG / CG / MCG (denoted as MCG below for convenience of description) As shown in FIG.

For PDUs transmitted over the WLAN, the LWA Adaptation Protocol (LWAAP) entity generates an LWA PDU containing DRB identity and the base station uses the LWA Ethertype to determine that the received PDU belongs to the LWA bearer And can use the DRB identification information to determine which LWA bearer the PDU belongs to. In FIG. 5, the LWAAP entity indicates that it is configured to be UE-specific, but this may be configured for each bearer. It is also within the scope of the present invention that LWAAP entities may be used in place of entities of other terms or terms having similar functions.

Data transmission path indication information

The base station can indicate to the terminal through the RRC message the uplink data transmission path (or uplink bearer split) to the LWA bearer.

For example, the base station may include information for instructing DRB configuration information (or PDCP configuration information) included in the RRC reconfiguration message to use both the base station radio resource and the WLAN radio resource through the uplink bearer split.

As another example, the base station may select one of the base station radio resource and the WLAN radio resource (or the base station radio link and the WLAN radio link) to use the uplink transmission path in the DRB configuration information (or PDCP configuration information) included in the RRC reconfiguration message May contain information for directing

As another example, the uplink bearer split can be transmitted to the DRB configuration information (or the PDCP configuration information) included in the RRC reconfiguration message. However, the transmission path to be transmitted by default may be either the base station radio resource and the WLAN radio resource Link) to select one to use.

In another example, the base station may instruct the split LWA bearer to indicate an uplink bearer split. In another example, the base station may direct only the uplink bearer switch to the Switched LWA bearer. That is, the base station may not configure the uplink bearer split for the Switched LWA bearer.

As described above, the LWA parameter UE capability is defined as a UE-EUTRA-Capability information element for Rel-13 LWA support as shown in FIG. Accordingly, it has been difficult to support the increased data rate of the high-speed WLAN when the LWA is configured using the high-speed WLAN technologies for the LWA-enabled terminal.

To solve this problem, the following methods can be used independently or in combination.

1) High speed WLAN  To support On the LWA bearer  About PDCP  Simplify operation

6 shows a functional diagram of the PDCP layer. As shown in FIG. 6, the PDCP (entity) provides the following functions. Specific details are described in 3GPP TS 36.323.

The transmitting PDCP entity (entity) associates the PDCP SN with the PDCP SDU received from the upper layer (IP) through sequence numbering.

The transmitting PDCP (entity) performs header compression of the PDCP SDU (if configured) through header compression.

The transmitting PDCP (entity) performs integrity protection (if applicable) and ciphering (if applicable).

The transmitting PDCP (entity) adds the PDCP header.

Routing is performed at the transmitting PDCP (entity) for the split bearer and the LWA bearer, and reordering is performed at the receiving PDCP (entity).

The receiving PDCP entity (entity) removes the PDCP header.

The receiving PDCP (entity) performs deciphering (if configured). And performs integrity verification (if configured).

The receiving PDCP (entity) performs header decompression of the PDCP SDU (if configured) through header decompression.

The receiving PDCP (entity) performs In order delivery and duplicate detection for in-sequence transmission.

In order to support high-speed WLAN (or LWA bearer supporting high-speed WLAN, or LWA bearer supporting high-speed WLAN), for convenience of description, the terminal will be referred to as " ) It is possible to transmit / receive data through the LWAAP without using one or more of the PDCP functions described above. Information for indicating this can be configured through the RRC.

For example, in order to support a high-speed WLAN, the PDCP entity may be able to forward PDCP SDUs directly to the LWAAP entity when receiving PDCP SDUs from the IP layer. The LWAAP entity may receive LWAAP SDUs from the PDCP layer and send them over the WLAN (or via the WT) to its peer LWAAP entities.

The LWAAP entity may receive LWAAP PDUs from the peer LWAAP entity via the WLAN (or via the WT) and forward the LWAAP SDUs to the PDCP layer.

The PDCP entity may forward it to the IP layer.

For another example, in order to support high-speed WLAN, the PDCP entity receives a PDCP SDU from the IP layer and associates the PDCP SN with a PDCP SDU received from an upper layer (IP) through sequence numbering. And then forward it (or add the PDCP header) to the LWAAP entity. The LWAAP entity may receive LWAAP SDUs from the PDCP layer and send them over the WLAN (or via the WT) to its peer LWAAP entities.

The LWAAP entity may receive LWAAP PDUs from the peer LWAAP entity via the WLAN (or via the WT) and forward the LWAAP SDUs to the PDCP layer.

The PDCP entity may forward this (or remove the PDCP header) to the IP layer

For another example, in order to support high-speed WLAN, the PDCP entity receives a PDCP SDU from the IP layer and associates the PDCP SN with a PDCP SDU received from an upper layer (IP) through sequence numbering. (If configured) performs header compression of the PDCP SDU.

 Integrity protection (if applicable), and ciphering (if applicable). And then forward it (or add the PDCP header) to the LWAAP entity. The LWAAP entity may receive LWAAP SDUs from the PDCP layer and send them over the WLAN (or via the WT) to its peer LWAAP entities.

The LWAAP entity may receive LWAAP PDUs from the peer LWAAP entity via the WLAN (or via the WT) and forward the LWAAP SDUs to the PDCP layer.

The PDCP entity removes the PDCP header. (If configured) deciphering. And performs integrity verification (if configured). (If configured) performs header decompression of the PDCP SDU. Then, the PDCP SDU can be transmitted to the IP layer.

For another example, in order to support high-speed WLAN, the PDCP entity receives a PDCP SDU from the IP layer and associates the PDCP SN with a PDCP SDU received from an upper layer (IP) through sequence numbering.

(If applicable) ciphering. And then forward it (or add the PDCP header) to the LWAAP entity. The LWAAP entity may receive LWAAP SDUs from the PDCP layer and send them over the WLAN (or via the WT) to its peer LWAAP entities.

The LWAAP entity may receive LWAAP PDUs from the peer LWAAP entity via the WLAN (or via the WT) and forward the LWAAP SDUs to the PDCP layer.

The PDCP entity removes the PDCP header. (If configured) deciphering. Then, the PDCP SDU can be transmitted to the IP layer.

That is, it is possible to perform the forwarding to the LWAAP without performing a separate PDCP processing operation or performing only a part or at least the PDCP processing operation. Or it may be sent in the sending PDCP entity without performing the routing function. Or without performing the reordering function described above (the reordering function that was conventionally performed on a separate bearer or LWA bearer) on the LWA bearer in the receiving PDCP entity. Alternatively, PDCP SDUs can be delivered to the IP layer without in-order delivery and duplicate detection for in-sequence transmission at the receiving PDCP entity.

The base station can transmit information for instructing the terminal to the terminal. Or information for instructing the configuration information associated with such operation to the terminal.

Alternatively, when the cipher / decipher function is removed from the PDCP between the BS and the MS, the BS can instruct the WT to configure the cipher between the MS and the WT through the WLAN when performing the WT addition. And / or establish WLAN encryption (bi-directional / per direction / downlink / uplink) between the terminal and the WLAN node WT.

2) Riordering  Configuring Information to Disable Features

As described above, the conventional LWA bearer has used the reordering function applied to the dual connectivity split bearer when the split LWA bearer is configured as well as when the Switched LWA bearer is configured in the terminal. The wireless transmission characteristics of the base station and the WLAN are very different, and the speed difference is large. In the case of transmitting user data using radio technologies / links / resources having different characteristics, sufficient buffering is necessary to re-order user data transmitted using each radio technology / link / resource, Delay is also added. In some cases, performance may be degraded compared to transmitting data only over a high-speed WLAN.

Therefore, when high-speed WLAN technology that provides speeds of Gbps or higher is applied, it is possible to obtain a sufficient amount of throughput by simply transmitting user data using only WLAN radio resources.

For example, in order to support high-speed WLAN, a base station may configure a Switched LWA bearer in a terminal to transmit downlink data only through WT. It is possible to prevent the downlink receiving PDCP entity from performing the above-described reordering. (For example, the DL data transfer procedures for DRBs mapped on RLC AM in section 5.1.2.1.2 of TS 36.323 can be used, or the procedure in 5.1.2.1.2 can be simplified Simplify the discard operation of the PDCP reception process due to layer re-establishment, or not perform in-order delivery and duplicate detection for in-sequence transmission).

And / or for the uplink, uplink data can be transmitted only through the WT by configuring an uplink bearer switch in the terminal. The uplink receiving PDCP entity may also be prevented from performing reordering.

The base station can transmit information for instructing the terminal to the terminal. Or information for instructing the configuration information associated with such operation to the terminal.

As another example, in order to support high-speed WLAN, a base station can configure a split LWA bearer in a terminal and transmit downlink data only through the WT. It is possible to prevent the downlink receiving PDCP entity from performing the above-described reordering.

And / or for the uplink, uplink data can be transmitted only through the WT by configuring an uplink bearer switch in the terminal. The uplink receiving PDCP entity may also be prevented from performing reordering.

The base station can transmit information for instructing the terminal to the terminal. Or information for instructing the configuration information associated with such operation to the terminal.

3) LWAAP  Direct data processing from the entity layer to the IP layer

The LWAAP entity can receive LWAAP SDUs from the IP layer and send them over the WLAN (or via the WT) to its peer LWAAP entities.

The LWAAP entity may receive LWAAP PDUs from the peer LWAAP entity via the WLAN (or via the WT) and forward the LWAAP SDUs to the IP layer.

For downlink transmission, when the LWAAP entity at the base station receives the LWAAP SDU from the IP layer, the base station constructs the corresponding LWAAP PDU and delivers it to the lower layer.

For downlink transmission, the LWAAP entity in the terminal receives the LWAAP PDU from the lower layer, and the terminal reassembles the corresponding LWAAP SDU and delivers it to the upper layer.

For uplink transmission, when the LWAAP entity at the terminal receives the LWAAP SDU from the IP layer, the terminal constructs the corresponding LWAAP PDU and delivers it to the lower layer.

For uplink transmission, the LWAAP entity in the base station receives the LWAAP PDU from the lower layer, and the base station reassembles the corresponding LWAAP SDU and delivers it to the upper layer.

Alternatively, the operations may be provided by defining new entities that are not LWAAP entities.

The base station can transmit information for instructing the terminal to the terminal. Or information for instructing the configuration information associated with such operation to the terminal.

Alternatively, the base station may instruct the WT to configure ciphering between the terminal and the WT over the WLAN when performing the WT addition.

Alternatively, in the case described above, it may be possible to establish WLAN encryption (bi-directional / downlink / downlink / uplink) between the terminal and the WLAN node WT.

In another method, when performing the above operation, a tunnel between a base station and an end station (for example, an arbitrary tunnel that provides a security function based on IPSEC or encapsulation) in a connection between LWAAP entities is referred to as a security tunnel As shown in FIG.

Alternatively, the LWAAP entity may perform the PDCP cipher function and the decipher function when performing the above operation. To this end, the LWAAP entity may be configured to be UE-specific or bearer-specific.

The base station can transmit information for instructing the terminal to the terminal. Or information for instructing the configuration information associated with such operation to the terminal.

4) PDCP  Receive data through higher layers

To support high-speed WLAN, a base station may configure a terminal and a security tunnel (for example, an arbitrary tunnel providing security functions based on IPSEC or encapsulation, hereinafter referred to as a security tunnel for convenience of explanation) . For example, a security tunnel can be constructed directly between the base station and the terminal. In another example, a security tunnel may be formed between a terminal and a base station through a security gateway with a security gateway in between to secure the base station.

The LWAAP entity may receive LWAAP SDUs from the IP layer and send them to the peer LWAAP entity via the WLAN (or via the WT or through the security tunnel).

The LWAAP entity may receive LWAAP PDUs from the peer LWAAP entity via the WLAN (or via the WT or through the security tunnel) and forward the LWAAP SDUs to the IP layer.

For downlink transmission, when the LWAAP entity at the base station receives the LWAAP SDU from the IP layer, the base station constructs the corresponding LWAAP PDU and delivers it to the lower layer.

For downlink transmission, the LWAAP entity in the terminal receives the LWAAP PDU from the lower layer, and the terminal reassembles the corresponding LWAAP SDU and delivers it to the upper layer.

For uplink transmission, when the LWAAP entity at the terminal receives the LWAAP SDU from the IP layer, the terminal constructs the corresponding LWAAP PDU and delivers it to the lower layer.

For uplink transmission, the LWAAP entity in the base station receives the LWAAP PDU from the lower layer, and the base station reassembles the corresponding LWAAP SDU and delivers it to the upper layer.

Alternatively, the operations may be provided by defining new entities that are not LWAAP entities.

The base station can transmit information for instructing the terminal to the terminal. Or information for instructing the configuration information associated with such operation to the terminal.

5) High speed WLAN  Support new LWA Bearer  Type Definition

In order to support high-speed WLAN, an LWA bearer type having information different from a conventional Rel-13 LWA bearer type can be configured in the UE.

Whereby the base station can direct the terminal to perform one or more of the methods described above for high speed WLAN support.

6) When the timer expires or Riordering  If the function is interrupted / Suspend / To be released  time Riordering  How to disable the function

When the timer expires or Riordering  If the function is interrupted / Suspend / To be released  time Riordering  How to disable the function

When the LWA bearer is configured in the Rel-13 LWA technique, the above-mentioned reordering function is always applied.

If the downlink data is transmitted only through the WLAN to the LWA switched bearer for high-speed WLAN support, it is not necessary to perform the above-mentioned ordinary reordering function, so that a larger L2 buffer size is not required or a sufficient WLAN speed can be provided .

In this case, however, data is received via LTE until the LWAAP entity is enabled and can receive data over the WLAN. Or in the course of changing from LTE bearer to LWA Switched bearer, data transmission may be interrupted or (temporary) reordering may be required at the terminal.

The base station can configure the terminal with the indication information. Alternatively, the base station may configure the terminal with information for instructing the terminal to perform such an operation. At this time, the reordering timer can use the existing reordering timer as it is, or an additional new timer can be configured.

From the time when the LWAAP entity is enabled to receive data (continuously) through the WLAN (or continuously) or from the LTE bearer to the LWA Switched bearer and can receive data (continuously) via the WLAN, You can suspend / suspend / release the function.

When the timer expires or when suspending / suspending / releasing the reordering function, the terminal transmits next to the upper layer in ascending order of the associated COUNT value.

- All stored PDCP SDUs (s) with associated COUNT value (s) less than Reordering_PDCP_RX_COUNT with associated COUNT value less than reordering PDCP_RX_COUNT

All stored PDCP SDUs (s) with consecutively associated COUNT values starting from PDCP_RX_COUNT (consecutively associated COUNT value (s) starting from Reordering_PDCP_RX_COUNT;

The terminal sets Last_Submitted_PDCP_RX_SN to the PDCP SN of the PDCP SDU finally delivered to the upper layer.

7) How to direct data transmission or reception via WLAN

The base station may instruct the terminal to perform a processing operation on the PDCP data when configuring the LWA bearer or configuring the LWA uplink bearer split or the LWA uplink bearer switch. The base station can indicate this through the PDCP Control PDU. Or the base station can indicate this through the RRC message.

In one example, the base station sends an RRC reconfiguration message including a WLAN mobility set to the terminal. The RRC reconfiguration message may further include DRB configuration information for transmitting / receiving data using a base station radio resource and / or a WLAN radio resource for a specific DRB.

The UE applies the new configuration and responds with the RRC Connection Reconfiguration Complete message.

If the terminal is not already associated, it associates with the WLAN considering the mobility set.

The terminal sends a WLAN association acknowledgment to the base station. And / or the WT sends a WT association confirmation message to the base station.

The terminal constructs / considers the LWAAP entity in the inactive / disabled state for the DRB.

In another example, the base station sends an RRC reconfiguration message including a WLAN mobility set to the terminal. The UE applies the new configuration and responds with the RRC Connection Reconfiguration Complete message.

If the terminal is not already associated, it associates with the WLAN considering the mobility set.

The terminal sends a WLAN association acknowledgment to the base station. And / or the WT sends a WT association confirmation message to the base station.

The base station may transmit the DRB configuration information including the DRB configuration information that can transmit / receive data using the base station radio resource and / or the WLAN radio resource to the specific DRB in another RRC reconfiguration message.

The terminal constructs / considers the LWAAP entity in the inactive / disabled state for the DRB.

Upon receiving information instructing the base station to activate / enable the LWAAP entity for the DRB,

For example, the UE applies a new configuration and responds with an acknowledgment message (RRC Connection Reconfiguration Complete message or response PDCP Control PDU).

As another example, the transmitting PDCP entity may submit the PDCP PDU (s) to the LWAAP entity. Alternatively, the terminal (PDCP entity) may indicate the amount of data available for transmission to the MAC entity configured for the MCG by zero (or the terminal may use the PDCP entity for transmission to the MAC entity configured for MCG). Or the sending PDCP entity may suspend / suspend / release the submission of the PDCP PDU (s) to the associated AM RLC entity configured for the MCG.

At this time, the base station may perform reordering on the uplink data temporarily received through the two paths to transmit data to the upper layer in order.

Upon receiving information indicating to disable / disable the LWAAP entity for the DRB from the base station,

For example, the UE applies a new configuration and responds with an acknowledgment message (RRC Connection Reconfiguration Complete message or response PDCP Control PDU).

As another example, the transmitting PDCP entity may submit the PDCP PDU (s) to the associated AM RLC entity configured for the MCG. Or the terminal (PDCP entity) may indicate the amount of data available for transmission to the MAC entity configured for the MCG. Or the sending PDCP entity may suspend submitting the PDCP PDU (s) to the LWAAP entity.

At this time, the base station may perform reordering on the uplink data temporarily received through the two paths to transmit data to the upper layer in order.

8) Other considerations

As described above, in order to sufficiently support high-speed WLAN transmission, it is necessary to support a larger buffer size than the conventional Rel-13 LWA buffer size. In this case, in order to calculate the L2 buffer size of the high-speed WLAN supporting terminal, it may be calculated based on the LWA bearer type, the uplink transmission path, and the uplink split, or the maximum value of the calculated value may be used.

In order to use a buffer size for a conventional Rel-13 LWA terminal for a high speed WLAN supporting terminal or to provide a relatively small additional buffer size for a high speed WLAN supporting terminal, the LWA bearer for the LWA bearer or the current LWA bearer And LWA bearers that provide other specific functionality. Define a new bearer to support high-speed WLAN with a small buffer size without using split bearer reordering, for example, by limiting to a switched LWA bearer or by processing data directly with the IP layer in another example, LWAAP entity To a bearer capable of delivering user data through PDCP processing that does not provide the split / routing / detach function and reordering function in the PDCP for the switched LWA bearer, or removes some of the PDCP functions for the LWA bearer Can be limited. As another example, if a buffer size for a conventional Rel-13 LWA terminal is used for a high-speed WLAN supporting terminal, it may be necessary to limit the LWA bearer for this.

In order to construct the LWA bearer by effectively utilizing the throughput of the terminal supporting the high-speed WLAN technology, the base station can recognize whether the terminal supports the high-speed WLAN technology, the wireless state information of the high-speed WLAN and the L2 buffer size .

For example, a new field that is distinguished from the lwa-BufferSize field described above may be defined as a terminal capability field, thereby indicating to the base station that the terminal supports a larger buffer size that supports high-speed WLAN technology.

In another example, the update field (lwa-SplitBearer-r14) in the above-described lwa-SplitBearer-r13 may indicate to the base station that the terminal supports a larger buffer size supporting high-speed WLAN technology.

Another example is the LWA Switched Bearer that does not support the new LWA bearer / reordering that supports high-speed WLAN (Switched LWA without the new WLAN bearer / split bearer reordering feature that distinguishes it from the Rel-13 LWA bearer type that supports high- Bearer / LWA bearer configured to not use some of the PDCP functions for high-speed WLAN data transmission / LWA bearer / LWAAP entity that only transmits data over the WLAN at a time Do not use split bearer reordering by processing data directly with the IP layer LWA bearer (for convenience of description, hereinafter referred to as Switched LWA bearer which does not use the reordering function, this is for convenience of explanation only, and other terms can be used). And defines a terminal capability field indicating whether or not to support the size, The base station can be instructed to support a switched bearer / larger buffer size that does not support the new LWA bearer / reordering supporting high-speed WLAN technology.

In another example, a split LWA bearer or a switched LWA bearer may define additional information elements (fields) on the terminal capability parameters to indicate that the terminal supports uplink transmissions over the WLAN. For example, it is possible to define an information element for indicating uplink transmission using both an LTE radio resource and a WLAN radio resource through an uplink split (at the PDCP). An information element for instructing to support an uplink transmission using both an LTE radio resource and a WLAN radio resource through an uplink split (in PDCP) and an information element for instructing another example to support uplink transmission through a WLAN Can be defined. For another example (at PDCP), an information element may be defined to indicate that it supports uplink transmissions using WLAN radio resources. For a terminal that does not support uplink transmission using both LTE radio resources and WLAN radio resources through the uplink split, the BS selects one of uplink transmission through WLAN and uplink transmission through LTE, As shown in FIG.

For another example, for a Switched LWA bearer, the base station may instruct the terminal to select one of uplink transmission over the WLAN and uplink transmission over the LTE to configure the terminal. For example, the uplink split may not be configured for the Switched LWA bearer.

For another example, for a Switched LWA bearer that does not use the reordering function, the base station may instruct the terminal to select one of the uplink transmission through the WLAN and the uplink transmission via the LTE to configure the terminal. For example, the uplink split may not be configured for the Switched LWA bearer.

As another example, it is possible to support uplink transmission using both LTE radio resources and WLAN radio resources only for a terminal supporting lwa-SplitBearer (conventionally). Accordingly, the base station can instruct the terminal using the high-speed WLAN to select one of the uplink transmission through the WLAN and the uplink transmission through the LTE to configure the terminal.

 As another example, a buffer size for a switched bearer supporting a high-speed WLAN may be newly defined, and a terminal capability field for indicating the buffer size may be defined to indicate to the base station that the terminal supports a buffer size that supports high-speed WLAN technology.

The BS can transmit the LWA configuration including the corresponding indication information to the UE based on the indication information received from the UE according to the embodiments described above, and the UE can apply the new configuration according to the wireless configuration.

If the buffer size to support high-speed WLAN is extended, it may be increased by n bits (n is a natural number) in addition to the PDCP SN of 18 bits. Or the PDCP SN to have a specific bit value. In this case, the base station can instruct bearer configuration information to support high-speed WLAN.

Values for a larger buffer size supporting high speed WLAN technology can be calculated by considering the various information described above. For example, it can be calculated by further considering whether or not the uplink is split. For another example, if the high-speed WLAN rate is supported, there is a possibility that the buffer size for buffering LTO link transmission PDUs has a larger buffer size for buffering WLAN link transmission PDUs for reordering. Accordingly, in case of supporting a high-speed WLAN speed, a method of obtaining an L2 buffer size using a method of buffering high-speed WLAN link transmission PDUs and reordering can be used. In the conventional dual connectivity, buffer size is calculated by buffering MeNB link transmission PDUs while waiting for PDUs delayed through SeNB since they are merged among the same base stations. However, since the WLAN transmission speed may be higher in LWA, high-speed WLAN speed is supported , It may be necessary to calculate the buffer size in such a manner as to buffer the WLAN link transmission PDUs.

Another example is a Switched LWA bearer that supports high-speed WLAN and / or a Switched LWA bearer that does not support reordering, and / or a terminal LWA bearer that supports high-speed WLAN technology Whether or not the buffer size of the corresponding Switched LWA bearer is supported). In this case, a value for a larger buffer size supporting high speed WLAN technology can be calculated using one of the methods described above.

As described above, the present invention can effectively support high-speed WLAN technology such as 802.11ax, 802.11ad, and 802.11ay to provide user throughput.

7 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.

Referring to FIG. 7, a base station 1000 according to another embodiment includes a control unit 1010, a transmission unit 1020, and a reception unit 1030.

The controller 1010 provides a method and apparatus for configuring a LWA bearer capable of efficiently supporting high-speed WLAN technologies such as 802.11ax, 802.11ad, and 802.11ay, which are necessary for carrying out the present invention, to provide user throughput Thereby controlling the overall operation of the base station.

The transmitting unit 1020 and the receiving unit 1030 are used to transmit and receive signals, messages, and data necessary for carrying out the present invention to and from the terminal.

FIG. 8 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.

Referring to FIG. 8, a user terminal 1100 according to another embodiment includes a receiving unit 1110, a control unit 1120, and a transmitting unit 1130.

The receiving unit 1110 receives downlink control information, data, and messages from the base station through the corresponding channel.

The controller 1120 also provides a method and apparatus for configuring an LWA bearer capable of efficiently supporting high-speed WLAN technologies such as 802.11ax, 802.11ad, and 802.11ay, which are necessary for performing the above-described present invention, to provide user throughput Thereby controlling the overall operation of the terminal.

The transmitter 1130 transmits uplink control information, data, and a message to the base station through the corresponding channel.

The standard content or standard documents referred to in the above-mentioned embodiments constitute a part of this specification, for the sake of simplicity of description of the specification. Therefore, it is to be understood that the content of the above standard content and portions of the standard documents are added to or contained in the scope of the present invention.

The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

Claims (1)

In a method for a terminal to process data,
Configuring a LWA bearer to efficiently support high speed WLAN technologies such as 802.11ax, 802.11ad and 802.11ay to provide user throughput; And
And processing the data using the LWA bearer.

Images