WO2016036180A1

WO2016036180A1 - Method and apparatus for transmitting data by using wireless lan carrier

Info

Publication number: WO2016036180A1
Application number: PCT/KR2015/009333
Authority: WO
Inventors: 홍성표; 최우진
Original assignee: 주식회사 케이티
Priority date: 2014-09-05
Filing date: 2015-09-04
Publication date: 2016-03-10

Abstract

The present invention relates to a technique by which a terminal and a base station transmit and receive data by using a wireless local area network (WLAN) carrier. Particularly, the present invention relates to a method and an apparatus for transmitting and receiving LTE-WLAN aggregation data, which is for aggregating the WLAN with an E-UTRAN carrier at a radio access network (RAN) level and using the same. Particularly, the present invention provides a method by which a terminal receives data by aggregating a WLAN carrier, comprising: a step for transmitting WLAN MAC address information or IP address information which are configured in the terminal; a step for receiving configuration information so as to configure a specific bearer through the WLAN carrier; a step for receiving the data through the base station and the WLAN carrier, respectively; and a step for transferring the specific bearer data received through the WLAN carrier to a PDCP entity of the specific bearer within the terminal.

Description

Method and apparatus for data transmission using WLAN carrier

The present invention relates to a technology for transmitting and receiving data between a terminal and a base station using a wireless local area network (WLAN) carrier. In particular, the present invention relates to an LTE-WLAN aggregation data transmission and reception method and apparatus for merging and using a WLAN as an E-UTRAN carrier at a Radio Access Network (RAN) level.

As communication systems have evolved, consumers, such as businesses and individuals, have used a wide variety of wireless terminals. Mobile communication systems such as LTE (Long Term Evolution) and LTE-Advanced of the current 3GPP series are high-speed, high-capacity communication systems that can transmit and receive various data such as video and wireless data, beyond voice-oriented services. The development of technology capable of transferring large amounts of data is required. As a method for transmitting a large amount of data, data can be efficiently transmitted using a plurality of cells.

However, there is a limitation in providing a base station to a plurality of terminals that transmit a large amount of data using limited frequency resources. In other words, securing a frequency resource that can be used exclusively by a specific operator has a problem of high cost.

On the other hand, the unlicensed frequency band that can not be used exclusively by a specific operator or a specific communication system can be shared by multiple operators or communication systems. For example, WLAN technology represented by Wi-Fi provides data transmission / reception services using frequency resources of the unlicensed band.

Therefore, the mobile communication system also requires a study on the technology for transmitting and receiving data with the terminal using a corresponding Wi-Fi access point (AP).

The present invention devised to solve this problem proposes a specific method and apparatus for the E-UTRAN to add a WLAN as a carrier in the E-UTRAN at the RAN level in the UE transmits specific user plane data. I would like to.

In addition, the present invention is to propose a method and apparatus for the user equipment to transmit the user plane data using the E-UTRAN carrier and the WLAN carrier at the same time.

According to an aspect of the present invention, a method for receiving data by merging WLAN carriers, the method comprising: transmitting WLAN MAC address information or IP address information configured in a terminal and configuring a specific bearer through the WLAN carrier; It provides a method comprising the step of receiving the configuration information for receiving the data through the base station and the WLAN carrier, and the specific bearer received via the WLAN carrier to the PDCP entity of the specific bearer in the terminal .

In addition, the present invention provides a method for transmitting a data using a WLAN carrier in the base station, generating the configuration information for configuring a specific bearer via the WLAN carrier, transmitting the configuration information to the terminal and through the WLAN carrier A method is provided that includes passing data for transmission to a WLAN end point.

In addition, the present invention is a terminal for receiving data by merging WLAN carriers, receiving configuration information for configuring a transmitter and a specific bearer for transmitting WLAN MAC address information or IP address information configured in the terminal through the WLAN carrier, Provided is a terminal device including a receiver for receiving data through a base station and a WLAN carrier, and a controller for transmitting data of a specific bearer received through a WLAN carrier to a PDCP entity of a specific bearer in the terminal.

In addition, the present invention provides a base station for transmitting data using a WLAN carrier, for transmitting a control unit and configuration information for generating a configuration information for configuring a specific bearer via the WLAN carrier, and for transmitting through the WLAN carrier Provided is a base station apparatus including a transmitter for transmitting data to a WLAN end point.

According to the present invention, when a terminal transmits specific user plane data, there is an effect that the E-UTRAN provides a specific method and apparatus for adding a WLAN as one carrier in the E-UTRAN to the terminal at the RAN level.

In addition, the present invention has the effect of providing a method and apparatus for the user equipment to transmit the user plane data using the E-UTRAN carrier and the WLAN carrier at the same time.

1 is a diagram illustrating an example of a Layer2 configuration diagram for downlink according to the present invention.

2 is a diagram illustrating another example of a Layer2 configuration diagram for the downlink according to the present invention.

3 is a view for explaining the operation of the terminal according to an embodiment of the present invention.

4 is a view for explaining the operation of the base station according to another embodiment of the present invention.

5 is a view for explaining the configuration of a terminal according to another embodiment of the present invention.

6 is a view for explaining the configuration of a base station according to another embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail through exemplary drawings. In adding reference numerals to the components of each drawing, it should be noted that the same reference numerals are assigned to the same components as much as possible even though they are shown in different drawings. In addition, in describing the present invention, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

The wireless communication system in the present invention is widely deployed to provide various communication services such as voice, packet data, and the like. The wireless communication system includes a user equipment (UE) and a base station (base station, BS, or eNB). In the present specification, a user terminal is a generic concept meaning a terminal in wireless communication. In addition, user equipment (UE) in WCDMA, LTE, and HSPA, as well as mobile station (MS) in GSM, user terminal (UT), and SS It should be interpreted as a concept that includes a 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, an Sector, a Site, and a BTS. Other terms such as a base transceiver system, an access point, a relay node, a remote radio head (RRH), a radio unit (RU), and a small cell may be called.

In other words, in the present specification, a base station or a cell is a generic meaning indicating some areas or functions covered by a base station controller (BSC) in CDMA, a Node-B in WCDMA, an eNB or a sector (site) in LTE, and the like. It should be interpreted as, and it is meant to cover all the various coverage areas such as megacell, macrocell, microcell, picocell, femtocell and relay node, RRH, RU, small cell communication range.

Since the various cells listed above have a base station for controlling each cell, the base station may be interpreted in two senses. i) the device providing the megacell, the macrocell, the microcell, the picocell, the femtocell, the small cell in relation to the wireless area, or ii) the wireless area itself. In i) all devices which provide a given wireless area are controlled by the same entity or interact with each other to cooperatively configure the wireless area to direct the base station. The eNB, RRH, antenna, RU, LPN, point, transmit / receive point, transmit point, receive point, and the like, according to the configuration of the radio region, become an embodiment of the base station. In ii), the base station may indicate the radio area itself to receive or transmit a signal from a viewpoint of a user terminal or a neighboring base station.

Therefore, megacells, macrocells, microcells, picocells, femtocells, small cells, RRHs, antennas, RUs, low power nodes (LPNs), points, eNBs, transmit / receive points, transmit points, and receive points are collectively referred to as base stations. do.

In the present specification, the user terminal and the base station are two transmitting and receiving entities used to implement the technology or technical idea described in this specification in a comprehensive sense and are not limited by the terms or words specifically referred to. The user terminal and the base station are two types of uplink or downlink transmitting / receiving subjects used to implement the technology or the technical idea described in the present invention, and are used in a generic sense and are not limited by the terms or words specifically referred to. Here, the uplink (Uplink, UL, or uplink) refers to a method for transmitting and receiving data to the base station by the user terminal, the downlink (Downlink, DL, or downlink) means to transmit and receive data to the user terminal by the base station It means the way.

There is no limitation on the multiple access scheme applied to the wireless communication system. Various multiple access techniques 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-TDMA, OFDM-CDMA Can be used. One embodiment of the present invention can be applied to resource allocation in the fields of asynchronous wireless communication evolving to LTE and LTE-Advanced through GSM, WCDMA, HSPA, and synchronous wireless communication evolving to CDMA, CDMA-2000 and UMB. The present invention should not be construed as being limited or limited to a specific wireless communication field, but should be construed as including all technical fields to which the spirit of the present invention can be applied.

The uplink transmission and the downlink transmission may use a time division duplex (TDD) scheme that is transmitted using different times, or may use a frequency division duplex (FDD) scheme that is transmitted using different frequencies.

In addition, in systems such as LTE and LTE-Advanced, a standard is configured by configuring uplink and downlink based on one carrier or a pair of carriers. The uplink and the downlink include a Physical Downlink Control CHannel (PDCCH), a Physical Control Format Indicator CHannel (PCFICH), a Physical Hybrid ARQ Indicator CHannel (PHICH), a Physical Uplink Control CHannel (PUCCH), an Enhanced Physical Downlink Control CHannel (EPDCCH), and the like. Control information is transmitted through the same control channel, and data is configured by a data channel such as a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH).

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

In the present specification, a cell means a component carrier having a coverage of a signal transmitted from a transmission / reception point or a signal transmitted from a transmission point or a transmission / reception point, and the transmission / reception point itself. Can be.

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

The multiple transmit / receive point is at least one having a base station or a macro cell (hereinafter referred to as an eNB) and a high transmission power or a low transmission power in a macro cell region, which is wired controlled by an optical cable or an optical fiber to the eNB. May be RRH.

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

Hereinafter, a situation in which a signal is transmitted and received through a channel such as a PUCCH, a PUSCH, a PDCCH, an EPDCCH, and a PDSCH may be described as "transmit and receive a PUCCH, PUSCH, PDCCH, EPDCCH, and PDSCH."

In addition, hereinafter, a description of transmitting or receiving a PDCCH or transmitting or receiving a signal through the PDCCH may be used as a meaning including transmitting or receiving an EPDCCH or transmitting or receiving a signal through the EPDCCH.

That is, the physical downlink control channel described below may mean PDCCH or EPDCCH, and may also be used to include both PDCCH and EPDCCH.

In addition, for convenience of description, the EPDCCH, which is an embodiment of the present invention, may be applied to the portion described as the PDCCH, and the EPDCCH may be applied to the portion described as the EPDCCH as an embodiment of the present invention.

Meanwhile, high layer signaling described below includes RRC signaling for transmitting RRC information including an RRC parameter.

The eNB performs downlink transmission to the terminals. The eNB includes downlink control information and an uplink data channel (eg, a physical downlink shared channel (PDSCH), which is a primary physical channel for unicast transmission, and scheduling required to receive the PDSCH. For example, a physical downlink control channel (PDCCH) for transmitting scheduling grant information for transmission on a physical uplink shared channel (PUSCH) may be transmitted. Hereinafter, the transmission and reception of signals through each channel will be described in the form of transmission and reception of the corresponding channel.

Due to the explosion of data traffic and the rapid increase in the number of wireless terminals, various techniques for processing a large amount of data at high speed are being discussed. For example, 3GPP discusses interworking technology using E-UTRAN and WLAN. That is, 3GPP Release 12 discusses 3GPP / WLAN interworking items. The aforementioned 3GPP / WLAN interworking item provides a Radio Access Network (RAN) assisted WLAN interworking function. The E-UTRAN may help terminal-based two-way traffic steering between the E-UTRAN and the WLAN for terminals in the RRC_IDLE and RRC_CONNECTED states.

The E-UTRAN provides the assistance parameter through broadcast or dedicated RRC signaling to the terminal. For example, the RAN assistance parameters may include information of at least one of an E-UTRAN signal strength threshold, a WLAN channel usage threshold, a WLAN backhaul data rate threshold, a WLAN signal strength, and an offload preference indicator. In addition, the E-UTRAN may provide a list of WLAN identifiers to the terminal through broadcast signaling.

The terminal uses the aforementioned RAN assistance parameters to evaluate access network selection and traffic steering rules.

The terminal indicates this to the access stratum (AS) upper layer when the access network selection and traffic steering rules are satisfied (fulfilled).

When applying the above-described access network selection and traffic steering rules, the terminal performs traffic steering in APN granularity between the E-UTRAN and the WLAN.

As described above, the RAN assisted WLAN interworking function provides only a method in which the E-UTRAN and the WLAN are built and standalone.

However, there is a growing need for LTE and WLAN aggregation, which considers tighter integration at the RAN level than the RAN assisted WLAN interworking, for high-capacity high-speed data processing. As described above, RAN assisted WLAN interworking could only operate according to the independent operation of the E-UTRAN and the WLAN on an APN basis. Accordingly, when the UE transmits specific user plane data, the E-UTRAN may not use the E-UTRAN carrier and the WLAN carrier at the same time by adding the WLAN carrier as one carrier in the E-UTRAN at the RAN level. In the following description, a WLAN carrier is referred to collectively as a WLAN radio link, a WLAN radio, a WLAN radio resource, or a WLAN radio network. Thus, depending on the need or situation, the WLAN carrier may be understood as the WLAN radio link, WLAN radio, WLAN radio resource or WLAN radio network described above. In addition, in the present specification, a carrier using E-UTRAN technology will be described as an LTE carrier, and a carrier using WLAN technology will be described as a WLAN carrier. This is for convenience of understanding, LTE carrier may include all carriers using a mobile communication system, including LTE. In addition, the WLAN carrier may be used to mean all carriers of the wireless communication system.

On the other hand, as an example for the terminal to utilize the LTE carrier and WLAN carrier at the same time, the terminal separates (or split or routing) / user plane data unit to be transmitted in the application or session layer or transmission layer or core network in performing data communication There is a method of combining (or aggregation or merging) to use an LTE carrier and a WLAN carrier. However, this method has a problem in that there is no standardized procedure or the WLAN carrier cannot be added / released quickly in consideration of the RAN-level radio environment and the mobility of the terminal effectively.

In addition, in the conventional E-UTRAN, when the terminal transmits specific user plane data, the E-UTRAN carrier and the WLAN carrier cannot be used simultaneously by adding the WLAN as one carrier in the E-UTRAN at the RAN level. In addition, a method of using an LTE carrier and a WLAN carrier by separating / integrating data units on a conventional application or a session layer or a transport layer or a core network may have no standardized procedure or effectively consider a RAN-level wireless environment and mobility of a terminal. There was no such problem.

In order to solve this problem, the present invention provides a UE to transmit specific user plane data, in which the E-UTRAN adds WLAN to the UE at the RAN level as one carrier in the E-UTRAN, and the UE is an E-UTRAN carrier. It is an object of the present invention to provide a method and apparatus for transmitting user plane data using a WLAN carrier and a WLAN.

This invention may be provided in a scenario where the base station and WLAN termination are co-located. In addition, the present invention may be provided in a scenario where the base station and the WLAN termination are non-co-located. In scenarios where the base station and WLAN terminations are non-co-located, the base station and WLAN terminations may be connected or established through non-ideal backhaul or near-ideal backhaul or ideal backhaul.

The WLAN termination herein refers to a logical WLAN network node. For example, it may be a WLAN AP or a WLAN AC. The WLAN termination may be a WLAN network node, such as an existing WLAN AP or an existing WLAN AC, or may be a WLAN network node with additional functionality for WLAN merge transmission to an existing WLAN AP or an existing WLAN AC. The WLAN termination may be implemented as an independent entity or as a functional entity included in another entity.

In order for the E-UTRAN to add a WLAN carrier to one terminal in the E-UTRAN at the RAN level, and to simultaneously use the E-UTRAN carrier and the WLAN carrier, a control plane procedure for this should be provided. In addition, in order for the E-UTRAN to add a WLAN carrier to one terminal in the E-UTRAN at the RAN level, and to transmit user plane data using the E-UTRAN carrier and the WLAN carrier at the same time, a protocol structure for this and each layer Should be provided. In addition, the addition of the WLAN or WLAN carrier as one carrier by the E-UTRAN logically or conceptually indicates that the terminal and the base station add the WLAN carrier PHY / MAC transmission function in addition to the existing E-UTRAN cell.

In order to apply the present invention, a method of separating or merging data at the RAN level between a base station and a WLAN end is required. Hereinafter, a specific embodiment for separating or merging user plane data between a base station and a WLAN terminal at the RAN level will be described with reference to the drawings.

Configuring user plane data split or aggregation sublayers

The E-UTRAN may implement a method of separating or merging user plane data through each sublayer by adding WLAN as a carrier in the E-UTRAN to the terminal at the RAN level.

Split or merge E-UTRAN MAC layers

For example, like a single base station-based carrier aggregation (CA) technology, the E-UTRAN adds WLAN as one carrier to transmit user plane data, and may separate or merge user plane data at the MAC layer. Can be. The MAC layer of the E-UTRAN processes operations such as dynamic scheduling or priority according to a radio state. Therefore, separation or merging at the MAC layer of the E-UTRAN may seriously affect the E-UTRAN existing standard. In addition, it may be practically difficult to directly interwork with the PHY or MAC layer of another standard or to receive information of the PHY or MAC layer of the WLAN.

Split or merge E-UTRAN RLC layers

As another example, the E-UTRAN may separate or merge user plane data in the RLC layer in transmitting user plane data by adding a WLAN as one carrier. The RLC layer segments or concatenates RLC SDUs in order to fit within the total size of the RLC PDU indicated by the lower layer to a particular transmission opportunity notified by the lower layer. The RLC layer performs error correction through ARQ for acknowledgment mode (AM) data transmission. Since the WLAN MAC layer may also transmit or retransmit data through the WLAN carrier, it may not be necessary for the RLC layer to perform segmentation or concatenation in conjunction with another standard, the WLAN MAC layer. However, the RLC layer may provide HARQ reordering functionality. Accordingly, when the E-UTRAN intends to use WLAN as one carrier in the RLC layer, data may be sequentially transmitted by receiving and reordering data received through the WLAN radio link different from the E-UTRAN. To this end, when the transmitting side of the AM RLC entity forms AMD Data PDUs (AM PDUs) from the RLC SDUs, the RLC SDUs may be segmented or concatenated to be delivered on demand or separately from the WLAN end. may not be concatenate).

The transmitting side of the AM RLC entity may perform retransmission of the RLC data PDUs. In addition, the transmitting side of the AM RLC entity may not segment or concatenate RLC PDUs to be delivered on demand or separately from the WLAN end when retransmitting the RLC data PDUs.

The transmitting side of the AM RLC entity may include the associated RLC header in the RLC data PDU when forming AMD PDUs from the RLC SDUs, or when retransmitting the RLC data PDUs.

E-UTRAN PDCP Layer Separation / Merge

As another example, the E-UTRAN may separate or merge user plane data in the PDCP layer in transmitting user plane data by adding a WLAN carrier as one carrier.

Referring to FIG. 1, the E-UTRAN of the present invention may separate or merge user plane data in the PDCP layer. To this end, the base station may be connected to a merging entity 100 that may be configured within the WLAN end 120. That is, the PDCP entity 110 of the base station may establish an interworking with the merge entity 100 of the WLAN terminal 120.

Referring to FIG. 2, the E-UTRAN of the present invention may separate or merge user plane data in the PDCP layer. To this end, the PDCP entity 210 of the base station may include a merge entity 200. The base station may establish a connection with the WLAN end 220 using the merge entity 200.

1 and 2 illustrate a diagram of separating or merging PDCP PDUs to which a PDCP header is added in the PDCP layer, but also to separate or merge PDCP SDUs or PDCP SDUs associated with a sequence number in the PDCP layer. It is included in the scope of the present invention.

In the following, the E-UTRAN adds WLAN carriers as one carrier, and details the procedure and detailed method for separating or merging user plane data in the PDCP layer.

PDCP 계층 분리 또는 병합(Split or Aggregation) 절차PDCP Hierarchy Split or Aggregation Procedure

The following description focuses on the procedures and detailed methods for separating or merging user plane data in the PDCP layer / object for understanding, but the procedures and detailed methods included in the following description are the user plane data in the RLC layer / object. The same can be applied to a method of separating or merging the same. That is, the PDCP layer / object / SDUs / PDUs included in each description can be applied to the same by changing the RLC layer / object / SDUs / PDUs.

The E-UTRAN may add a WLAN carrier as one carrier at the PDCP layer and transmit user data traffic using the LTE carrier and the WLAN carrier simultaneously. In this case, the WLAN carrier may be used as a downlink dedicated carrier. That is, the uplink transmission may be transmitted only through the carrier (s) between the terminal and the base station for a specific bearer using the LTE carrier and the WLAN carrier at the same time. In this case, the layer2 structure for uplink transmission of the terminal may be used in the same manner as in the prior art.

Alternatively, the WLAN carrier may be used for both uplink and downlink in the E-UTRAN adding the WLAN carrier as one carrier in the PDCP layer and transmitting user data traffic using the LTE carrier and the WLAN carrier simultaneously. have. That is, both uplink transmission and downlink transmission may be used for a specific bearer using the LTE carrier and the WLAN carrier at the same time.

Aggregation entity for merging or interworking between base station and WLAN end points

Aggregation for base station and WLAN end-to-end aggregation or interworking, in order for E-UTRAN to add WLAN carriers as one carrier at the PDCP layer and to transmit downlink user data traffic using both LTE and WLAN carriers simultaneously. entity may be required. Merging entity herein is a name for convenience of understanding only, but is not limited thereto. Accordingly, the merging entity may be variously referred to as an interworking entity, an interworking function, a logical entity for LTE-WLAN merging, an LTE-WLAN merging entity, and the like, and hereinafter referred to as a merging entity. do.

The aforementioned merge entity may be an independent entity or may be a functional entity of another network entity. For example, when the base station and the WLAN termination are co-located and provided as an integrated device, the aforementioned merging entity may be a functional entity included in the integrated device. In another example, the merging entity in a scenario where the base station and WLAN end point are non-co-located may be a functional entity included within the WLAN end point. As another example, the merging entity in a scenario where the base station and WLAN end point are non-co-located may be a functional entity included in the base station.

The merge entity may be implemented as a layer entity higher than L1 / L2. For example, when the merge entity is configured as a functional entity included in the WLAN termination, the merge entity may operate as a higher layer entity than WLAN L1 / L2 to transmit terminal and user plane data through WLAN L1 / L2. In another example, when a merged entity consists of functional entities contained within a base station, it acts as a higher layer entity (e.g., IP layer or session layer or application layer) to transmit terminal and user plane data over the WLAN end. It may be. For another example, when a merge entity consists of a functional entity contained within a base station, it operates as a protocol translation function entity that receives PDCP PDUs and performs the function for delivering PDCP PDUs through the WLAN end. Through the terminal and the user plane data can be transmitted.

Alternatively, the merge entity may be configured as a function in WLAN L2 so that the WLAN L2 entity may implement an operation for this.

Alternatively, the merging entity may be configured as a PDCP lower layer in the terminal to separate data of a specific radio bearer received through a WLAN carrier and transmit the data to the associated PDCP entity.

Meanwhile, the merge entity of the present invention configured according to the above-described embodiments may receive PDCP PDUs from the PDCP entity of the base station. Alternatively, PDCP PDUs may be requested to the PDCP entity of the base station to receive PDCP PDUs.

The merging entity may transmit the received PDCP PDUs to the terminal through the WLAN wireless link. Alternatively, the merging entity may transmit the received PDCP PDUs to the terminal using the WLAN L1 / L2 protocol. Alternatively, the merging entity may transmit the received PDCP PDUs to the terminal through WLAN end point (or WLAN radio link) using IP communication (or IP packet forwarding). Alternatively, the merging entity may transmit the received PDCP PDUs to the terminal through WLAN end point (or WLAN radio link) using WLAN communication (or WLAN MAC forwarding).

The terminal of the present invention may deliver the PDCP PDUs received through the WLAN radio link to the PDCP entity in the corresponding terminal. Alternatively, the terminal may deliver the received PDCP PDUs to the corresponding PDCP entity in the terminal using the WLAN L1 / L2 protocol in the terminal.

Meanwhile, the base station of the present invention may separate and transmit data traffic belonging to a specific bearer in the PDCP layer through the base station and the WLAN terminal. That is, the PDCP entity of the base station may separately submit PDCP PDUs into an associated RLC entity or an associated merge entity in order to transmit user plane data through an E-UTRAN carrier and a WLAN carrier on a radio bearer basis.

In order to transmit user plane data on the E-UTRAN carrier and / or WLAN carrier on a radio bearer basis in the PDCP entity, the base station selects the corresponding PDCP PDUs in the terminal corresponding to the PDCP PDUs received on the WLAN radio link for the specific bearer. It can be configured to forward to the bearer's PDCP entity. Or, in order to transmit user plane data on the E-UTRAN carrier and / or WLAN carrier in the radio bearer unit in the PDCP entity, the base station corresponds to the PDCP PDUs received by the terminal through the WLAN radio link for the specific bearer in the terminal. It may be transmitted including information for delivery to the PDCP entity of a specific bearer.

Meanwhile, in a scenario where the base station and the WLAN end are non-co-located, user plane data (PDCP PDUs) may be carried through the GTP-U protocol on an interface between the base station and the WLAN end. In scenarios where the base station (eNB) and WLAN terminations are non-co-located, if the interface between the base station and the WLAN termination is associated with an E-RAB for a bearer provided through the base station and the WLAN termination, the GTP-U will carry PDCP PDUs. Can be.

When the E-UTRAN adds the WLAN carrier as one carrier and configures a merge entity for transmitting downlink user data traffic using the LTE carrier and the WLAN carrier simultaneously, the user data bearer is placed on the interface between the base station and the WLAN end point. The user plane protocol instance is set up at the base station and the WLAN end.

Each user plane protocol instance on the interface between the base station and the WLAN end is associated with one E-RAB. Thus, each E-RAB is either an endpoint of the user plane data bearer on the base station and the WALN end-to-end interface, or the endpoint of the user plane data bearer of the base station associated with that bearer, or the endpoint of the WLAN end associated with that bearer. Each can be identified using the GTP Tunnel endpoint Information Element (IE).

The merging entity configured within the aforementioned WLAN end may comprise a user plane instance within the aforementioned WLAN end. Alternatively, the merging entity may operate in association with the user plane instance in the aforementioned WLAN end. Alternatively, the merging entity may operate as a user plane instance within the aforementioned WLAN end.

Alternatively, in a scenario where the base station and the WLAN end are non-co-located, user plane data (PDCP PDUs) may be transmitted in the payload of the IP protocol on an interface between the base station and the WLAN end. The base station may include PDCP PDUs to be transmitted to the terminal through the WLAN end in the data field of the IP packet, and may send the terminal through the WLAN end with the IP address of the terminal as the destination address.

Alternatively, in a scenario where the base station and WLAN end points are non-co-located, user plane data (PDCP PDUs or PDCP SDUs or PDCP SDUs associated with a Sequence Number) on the interface between the base station and the WLAN end is WLAN L2 (or WLAN MAC). It may be transmitted in the payload of the protocol. The base station includes PDCP PDUs (or PDCP SDUs associated with PDCP SDUs or Sequence Numbers) to be transmitted to the terminal through WLAN termination in a data field of a WLAN L2 (or WLAN MAC) frame, and uses the WLAN MAC address of the terminal as a destination address. It may be sent to the terminal through the WLAN end.

Meanwhile, the data received by the terminal through the WLAN termination in the present specification means PDCP SDUs or PDCP PDUs or user plane data or user plane packets associated with PDCP SDUs or sequence numbers, respectively, as necessary. It may be described as a user plane packet, PDCP SDUs, PDCP SDUs associated with a sequence number, PDCP PDUs, and the like.

Hereinafter, the data transmission method of the present invention described above will be described with reference to the drawings based on the operation of the terminal and the base station.

A method for receiving data by merging WLAN carriers according to an embodiment of the present invention, the method comprising: transmitting WLAN MAC address information or IP address information configured in the terminal and configuring a specific bearer through the WLAN carrier The method may include receiving information, receiving data through the base station and the WLAN carrier, and transmitting data of a specific bearer received through the WLAN carrier to the PDCP entity of the specific bearer in the terminal.

Referring to FIG. 3, the terminal may include transmitting WLAN MAC address information or IP address information configured in the terminal (S310). For example, the terminal may transmit WLAN MAC address information or IP address information configured in the terminal to the base station or the WLAN end. This is because, when the PDCP PDUs are transmitted through the LTE carrier and the WLAN carrier, the WLAN termination or merging entity needs the WLAN MAC address or IP address information of the terminal in order to transmit the PDCP PDUs or PDCP SDUs to the terminal. That is, the WLAN termination or merging entity may need the WLAN MAC address and / or IP address of the terminal to transmit the received PDCP PDUs (or PDCP SDUs) to the terminal via the WLAN wireless link. To this end, the terminal may transmit WLAN MAC address and / or IP address information to the base station or WLAN end configured with the merge entity. If the base station receives the WLAN MAC address information or IP address information of the terminal and the merge entity is configured at the WLAN end, the base station may transmit the WLAN MAC address information or IP address information of the terminal to the merge entity.

The terminal may include receiving configuration information for configuring a specific bearer through a WLAN carrier (S320). For example, the base station may transmit configuration information necessary for transmitting data by adding a WLAN carrier to the terminal. The terminal may receive the corresponding configuration information from the base station to obtain information about a specific bearer configured through the LTE carrier and the WLAN carrier. In addition, the terminal may be configured to receive user plane data belonging to the specific bearer through the WLAN carrier using the configuration information to deliver to the associated PDCP entity. Through this, the terminal may receive data of a specific bearer through the WLAN carrier.

In addition, the terminal may include receiving data through each of the base station and the WLAN carrier (S330). As described above, the terminal may receive data through the base station and the WLAN end. For example, the terminal may be configured to receive a specific bearer separated through a merge entity through a WLAN carrier, and may receive data of the specific bearer. In addition, the terminal may also receive data through the base station.

In addition, the terminal may include transmitting the data of the specific bearer received through the WLAN carrier to the PDCP entity of the specific bearer in the terminal (S340). The terminal may transmit data of a specific bearer received through the WLAN carrier to a corresponding PDCP entity in the terminal. For example, a specific bearer may be configured to be received through a WLAN carrier based on the above-described configuration information, and when data is received through the WLAN carrier, the specific bearer may be delivered to a PDCP entity in the terminal. In this case, the specific bearer delivered to the PDCP entity of the specific bearer may be determined based on the above configuration information.

Hereinafter, the detailed operation of the above-described terminal operation will be described in more detail.

User Plane Data Transmission over WLAN Carrier

The aforementioned merging entity may transmit the received PDCP PDUs (or PDCP SDUs associated with user plane data or data, or PDCP SDUs or Sequence Number) to the terminal through a WLAN wireless link. Alternatively, the merging entity may transmit the received PDCP PDUs (or PDCP SDUs associated with user plane data or data, or PDCP SDUs or Sequence Number) to the terminal using the WLAN L1 / L2 protocol. To this end, the merging entity may determine the WLAN MAC address of the terminal and / or transmit the received PDCP PDUs (or user plane data or data or PDCP SDUs associated with PDCP SDUs or Sequence Numbers) to the terminal via the WLAN radio link. Or an IP address may be required.

The terminal may transmit the MAC address information to the base station or WLAN end.

For example, the merging entity may obtain WLAN MAC address information of the terminal and transmit PDCP PDUs (or PDCP SDUs associated with user plane data or data, or PDCP SDUs or Sequence Numbers) to the terminal. To this end, the terminal may transmit the WLAN MAC address information of the terminal to the base station. If, in the scenario where the base station and the WLAN end are non-co-located, the aforementioned merging entity is a functional entity included in the WLAN end, when the base station configures LTE-WALN merging, the base station is connected to the WLAN end of the WLAN MAC of the terminal. You can send address information. Alternatively, the base station may transmit the WLAN MAC address information of the terminal described above when the WLAN is to be added as one carrier or when the base station requests to add the WLAN to the WLAN end.

As another example, when a base station and a WLAN end are co-located and provided as an integrated device, or in a scenario where the base station and WLAN end are non-co-located, the terminal may be a functional entity included in the base station. The WLAN MAC address information of the terminal may be transmitted to the base station. Through this, the merge entity may obtain the WLAN MAC address information of the terminal and transmit PDCP PDUs (or user plane data or data, or PDCP SDUs associated with PDCP SDUs or Sequence Numbers) to the terminal through the WLAN terminal.

As another example, the terminal may transmit the WLAN MAC address information of the terminal to the WLAN end according to the configuration of the base station. For example, in the scenario where the base station and the WLAN end are non-co-located, the aforementioned merging entity may be a functional entity included within the WLAN end. In this case, in order to configure the LTE-WLAN merging, the base station may transmit configuration information necessary for configuring the LTE-WLAN merging to the terminal through an RRC connection reconfiguration message. The terminal receiving the RRC reconfiguration message may attempt to connect to the WLAN end to inform the merging entity of the WLAN MAC address information of the terminal.

In the methods described above, the terminal may transmit WLAN MAC address information to the base station through the RRC message. As an example, the terminal may transmit WLAN MAC address information through the UE assistance message. As another example, the terminal may transmit WLAN MAC address information through a measurement report. As another example, the terminal may transmit WLAN MAC address information through a UL information transfer message. As another example, the terminal may transmit WLAN MAC address information through the UE information procedure. To this end, when the base station requests WLAN MAC address information through a UE information request message, the terminal may transmit WLAN MAC address information through a UE information response message.

Alternatively, the terminal may transmit the IP address information to the base station or WLAN end.

For example, the merge entity may transmit PDCP PDUs to the terminal by obtaining the IP address information of the terminal. The IP address of the UE may be an IP address for PDN connection (connection) allocated by the UE requested PDN connectivity procedure or UE requested PDN connectivity procedure in the Attach procedure. Alternatively, the IP address of the terminal may be an IP address assigned through the WLAN termination.

To this end, the terminal may transmit the IP address information of the terminal to the base station. If the base station and the WLAN termination are in a non-co-located scenario, the aforementioned merging entity may be a functional entity included in the WLAN termination. Thus, the base station can send this information to the WLAN end when the base station wants to add the WLAN carrier as one carrier or when the base station requests to add the WLAN to the WLAN end.

As another example, when a base station and a WLAN end are co-located to provide an integrated device, or in the scenario where the base station and the WLAN end are non-co-located, the terminal may be a functional entity included in the base station. The base station or the base station and the WLAN terminal is co-located to transmit the IP address information of the terminal to the integrated device. Through this, the merge entity may obtain the IP address information of the terminal and transmit PDCP PDUs to the terminal through the WLAN end.

As another example, if the base station and the WLAN termination is a non-co-located scenario, the aforementioned merging entity may be a functional entity included in the WLAN termination. In this case, the base station may receive the IP address information of the terminal through the MME. The base station may transmit the IP address information of the terminal to the WLAN end when the base station wants to add the WLAN as one carrier.

As another example, when the WLAN end is composed of co-located and integrated devices, or in the scenario where the base station and the WLAN end are non-co-located, the merge entity described above is a functional entity included in the base station. IP address information may be transmitted to the base station or the integrated device. The merge entity may obtain PD address information of the terminal and transmit PDCP PDUs to the terminal.

As another example, if the base station and the WLAN termination is a non-co-located scenario, the aforementioned merging entity may be a functional entity included in the WLAN termination. Therefore, when the base station wants to add the WLAN as one carrier, the base station may transmit an RRC connection reconfiguration message including configuration information for LTE-WLAN merging to the terminal. Upon receiving the RRC reconfiguration message, the UE may attempt to connect to the WLAN end to transmit the IP address of the UE to the merge entity.

In the methods of transmitting the above-described IP address information, the terminal may transmit the IP address information to the base station through the RRC message. For example, the terminal may transmit IP address information through the UE assistance message. As another example, the terminal may transmit IP address information through a measurement report. As another example, the terminal may transmit IP address information through a UL information transfer message. As another example, IP address information may be transmitted through a UE information procedure. To this end, when the base station requests IP address information through a UE information request message, the terminal may transmit IP address information through a UE information response message.

Alternatively, the WLAN termination or merging entity may obtain WLAN MAC address information of the terminal using an address resolution protocol (ARP).

The merging entity may transmit PDCP PDUs through the WLAN radio link using WLAN MAC address information and / or IP address information of the terminal.

Forward PDCP PDUs received over WLAN radio link to the corresponding in-device PDCP entity

Hereinafter, the reception of the terminal through the WLAN radio link will be described using PDCP PDUs as an example. However, the PDCP PDUs are just examples, and the same may be applied to the PDCP SDUs associated with user plane data or data, or PDCP SDUs or a sequence number. That is, hereinafter, even if PDCP SDUs associated with user plane data or data or PDCP SDUs or a sequence number are used instead of PDCP PDUs, the present invention is included in the embodiment of the present invention.

The terminal may deliver the PDCP PDUs received through the WLAN radio link to the PDCP entity in the corresponding terminal. Alternatively, the terminal may deliver the received PDCP PDUs to the corresponding PDCP entity in the terminal using the WLAN L1 / L2 protocol in the terminal.

First, a specific method of delivering the PDCP PDUs received through the WLAN radio link to the corresponding PDCP entity in the terminal will be described.

For example, the terminal may receive information for mapping the PDCP PDUs to the PDCP entity in the terminal together with the PDCP PDUs. As another example, the terminal may receive information for mapping the PDCP PDUs to the PDCP entity in the terminal as header information of the PDCP PDUs. As another example, the terminal may receive information for mapping PDCP PDUs to PDCP entities in the terminal as added new header information. As another example, the terminal may receive information for mapping the PDCP PDUs to the PDCP entity within the terminal in a WLAN MAC header or LLC header or an IP header or UDP header between the WLAN terminal and the terminal including the PDCP PDUs.

More specifically, when a PDCP entity (or base station) of a base station delivers PDCP PDUs to a terminal over a WLAN radio link (or WLAN L1 / L2 protocol), it is either in conjunction with, in addition to, or in addition to PDCP PDUs. As a method of adding a header to the PDUs, information for mapping PDCP PDUs to PDCP entities in the terminal may be transmitted to the terminal.

Or, if the PDCP entity of the base station transmits PDCP PDUs to the merging entity and the merging entity transmits the received PDCP PDUs to the terminal through the WLAN radio link, the PDCP PDUs together with or in addition to the PDCP PDUs or the PDCP PDUs with a header As an additional method, information for mapping PDCP PDUs to PDCP entities in the terminal may be pasted and transmitted to the terminal. To this end, in the scenario where the base station and WLAN end point are non-co-located, the merge entity described above is a functional entity included in the WLAN end point, when the base station attempts to add the WLAN as a carrier, Information for mapping PDCP PDUs to PDCP entities in the terminal may be transmitted.

Alternatively, the merging entity may identify PDCP PDUs belonging to a specific bearer through the aforementioned user plane protocol instance. The merging entity may transmit information for mapping PDCP PDUs belonging to a specific bearer to PDCP entities in the terminal together with the PDCP PDUs, in addition to the PDCP PDUs, or by adding a header to the PDCP PDUs to the terminal.

Alternatively, the PDCP entity of the base station transmits PDCP PDUs to a merge entity contained within the WLAN end, and the merge entity contained within the WLAN end peers the received PDCP PDUs to the merge entity within the WLAN end via the WLAN radio link. It can be transmitted to the merge entity in the terminal.

Alternatively, the PDCP entity of the base station transmits PDCP PDUs to the merge entity contained in the base station, and the merge entity included in the base station peers the received PDCP PDUs to the merge entity contained in the base station via a WLAN end (or WLAN radio link). It can be transmitted to the merged entity in the peered terminal.

The merge entity in the terminal may deliver the received PDCP PDUs to the corresponding PDCP entity in the terminal.

To support this, the merge entity in the WLAN end and the merge entity in the terminal may be configured such that only one radio bearer is associated.

Alternatively, the merge entity included in the WLAN termination may transmit information including mapping PDCP PDUs to the PDCP entity in the terminal. That is, the merge entity included in the WLAN end includes information for mapping the PDCP PDUs to the PDCP entity in the terminal, and the merge entity in the terminal may transmit the PDCP PDUs to the corresponding PDCP entity using this information.

Alternatively, the merge entity included in the base station may transmit the PDCP PDUs including information for mapping the PDCP PDUs with the PDCP entity in the terminal. That is, the merge entity included in the base station transmits the PDCP PDUs including information for mapping the PDCP entities with the terminal in the terminal, and the merge entity in the terminal may transmit the PDCP PDUs to the corresponding PDCP entity using this information.

Meanwhile, information for mapping the PDCP PDUs described above with the PDCP entity in the terminal may be included in the corresponding PDCP PDUs. That is, the data received through the WLAN carrier may include identification information for transferring the data received through the WLAN carrier to the PDCP entity of a specific bearer in the terminal.

The information for mapping the above-described PDCP PDUs with the PDCP entity in the terminal may preferably use the corresponding radio bearer identification information.

For example, a logical channel identifier having a value between 3 and 10 may be used as information for mapping the above-described PDCP PDUs to a PDCP entity in a terminal. As another example, eps-BearerIdentity may be used as information for mapping the aforementioned PDCP PDUs to PDCP entities in the terminal. As another example, dRB-Identity may be used as information for mapping the aforementioned PDCP PDUs to PDCP entities in the terminal. As another example, newly defined index information for identifying the radio bearer may be used as information for mapping the above-described PDCP PDUs to PDCP entities in the terminal, and the above-mentioned radio in the DRB configuration information (DRB-ToAddMod) in the terminal may be used. It may be configured by adding index information for identifying a bearer.

The terminal may establish a merge entity in the terminal that is peered to the aforementioned merge entity. Alternatively, the terminal may set a merge entity in the terminal peered to the aforementioned merge entity in the PDCP entity. Alternatively, the terminal may provide a function of mapping PDCP PDUs received through WLAN termination (or WLAN radio link) in the PDCP layer to corresponding PDCP PDUs. Alternatively, the terminal may provide a function of mapping PDCP PDUs received through a WLAN end (or WLAN radio link) to corresponding PDCP PDUs.

The PDCP PDDUs for PDCP PDUs received from the PDCP entity on the WLAN end (or WLAN radio link) and delivered to the corresponding PDCP entity in the UE and on PDCP PDUs received on the base station radio link and delivered to the PDCP entity through the RLC entity. Reordering may be performed according to a PDCP sequence number. Through this, the user plane data may be transmitted in-sequence in the PDCP entity.

The information for setting an entity that provides an operation for distinguishing data received through the WLAN carrier for each specific bearer described above may be included in configuration information for configuring the aforementioned bearer through the WLAN carrier.

In a method for transmitting data using a WLAN carrier, a base station according to another embodiment of the present invention, generating configuration information for configuring a specific bearer through a WLAN carrier, transmitting configuration information to a terminal, and WLAN And forwarding data to the WLAN end for transmission over the carrier.

Referring to FIG. 4, the base station may include generating configuration information for configuring a specific bearer through a WLAN carrier (S410). The configuration information may include information for setting an entity in the terminal that provides an operation for distinguishing data transmitted through a WLAN carrier for each specific bearer. As described above, the terminal may transmit the data received through the WLAN carrier to the corresponding PDCP entity in the terminal. To this end, the base station may generate configuration information for setting an entity that provides an operation for the terminal to distinguish the data received through the WLAN carrier for each specific bearer. For example, an entity providing an operation for distinguishing by a specific bearer may be an entity in a terminal peered with the aforementioned merge entity. Alternatively, the entity providing an operation of dividing by specific bearers may be an entity performing a function of dividing received data by specific bearers.

The base station may include transmitting the configuration information to the terminal (S420). The base station may transmit the above-described configuration information to the terminal. The configuration information may be transmitted through higher layer signaling.

The base station may include transmitting data for transmission through the WLAN carrier to the WLAN end point (S430). As discussed above, data delivered to a WLAN end may be delivered via a GTP-U protocol between the base station and the WLAN end providing the WLAN carrier. For example, the base station may deliver PDCP PDUs transmitted to the terminal through a WLAN carrier to a merge entity configured in the WLAN end. Alternatively, the PDCP entity of the base station may deliver PDCP PDUs transmitted to the terminal through the WLAN carrier to a merge entity configured in the WLAN end.

Meanwhile, the data transmitted through the WLAN carrier may include identification information for transmitting the data received through the WLAN carrier to the PDCP entity of a specific bearer in the terminal. The identification information may also include any one of logical channel identifier information, bearer identification information, and radio bearer index information.

In addition, the base station can perform all the operations required to perform the above-described operation of the present invention according to each embodiment.

As described above, in the present invention, in order for the UE to transmit user plane data using the E-UTRAN carrier and the WLAN carrier simultaneously, the E-UTRAN separates the user plane data from the PDCP entity in units of radio bearers and uses the WLAN radio link. The user plane data is transmitted through the UE, and the UE transmits the PDCP PDUs received through the WLAN radio link to the corresponding PDCP entity in the UE so that the WLAN carrier can be added in the E-UTRAN to transmit the user plane data in units of radio bearers. It is effective.

Referring to FIG. 5, the user terminal 500 according to another embodiment of the present invention is configured to configure a specific bearer and a transmitter 520 for transmitting WLAN MAC address information or IP address information configured in the terminal through a WLAN carrier. Receiving configuration information, receiving unit 530 for receiving data through the base station and the WLAN carrier and the control unit 510 for transmitting the data of a specific bearer received through the WLAN carrier to the PDCP entity of a specific bearer in the terminal; Can be.

In addition, the control unit 510 controls the overall operation of the terminal 500 according to the terminal required to carry out the present invention to receive the data through the WLAN carrier and transfer to the PDCP entity.

The transmitter 520 may transmit the WLAN MAC address or the IP address information to the base station or the WLAN terminal, or may transmit the WLAN MAC address or IP address information to the aforementioned merge entity. In addition, the transmitter 520 transmits uplink control information, data, and messages to the base station through a corresponding channel.

The receiver 530 may receive configuration information for configuring a specific bearer through a WLAN carrier. The configuration information may include information for setting an entity that provides an operation of dividing data received through a WLAN carrier for each specific bearer. In addition, the receiver 530 may receive data including identification information for transferring data received through the WLAN carrier to the PDCP entity of a specific bearer in the terminal. The identification information may include any one of logical channel identifier information, bearer identification information, and radio bearer index information.

In addition, the receiver 530 receives downlink control information, data, and a message from a base station through a corresponding channel.

Referring to FIG. 6, the base station 600 according to another embodiment of the present invention transmits configuration information and a control unit 610 for generating configuration information for configuring a specific bearer through a WLAN carrier, and transmits the configuration information to the terminal. It may include a transmitter 620 for transmitting data for transmission through the WLAN terminal. The configuration information may include information for setting an entity in the terminal that provides an operation of dividing data received through the WLAN carrier for each specific bearer.

The transmitter 620 may transmit data to be transmitted to the terminal through the WLAN carrier or WLAN MAC address information or IP address information of the terminal to the WLAN terminal. Data delivered to the WLAN end may be carried over the GTP-U protocol between the base station and the WLAN end providing the WLAN carrier. In addition, the data transmitted through the WLAN carrier may include identification information for transmitting the data received via the WLAN carrier to the PDCP entity of a specific bearer in the terminal. The identification information may include information of any one of logical channel identifier information, bearer identification information, and radio bearer index information.

On the other hand, the base station may further include a receiver 630 for receiving the uplink signal and data from the terminal.

The transmitter 620 and the receiver 630 are used to transmit and receive signals, messages, and data necessary for carrying out the present invention.

The control unit 610 controls the overall operation of the base station 600 according to the terminal required to carry out the present invention to receive the data through the WLAN carrier and transfer to the corresponding PDCP entity.

In addition to this, the controller 610 controls the overall operation of the base station required to perform the above-described embodiments of the present invention.

The above description is merely illustrative of the technical idea of the present invention, and those skilled in the art to which the present invention pertains may make various modifications and changes without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical spirit of the present invention but to describe the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the equivalent scope should be interpreted as being included in the scope of the present invention.

CROSS-REFERENCE TO RELATED APPLICATIONCROSS-REFERENCE TO RELATED APPLICATION

This patent application is related to the patent application No. 10-2014-0119263 filed with Korea on September 05, 2014 and the patent application No. 10-2015-0094021 filed with Korea on July 01, 2015. Priority is claimed under section (a) (35 USC § 119 (a)), all of which is incorporated by reference in this patent application. In addition, if this patent application claims priority for the same reason for countries other than the United States, all its contents are incorporated into this patent application by reference.

Claims

In the method for the terminal to merge the WLAN carriers to receive data,

Transmitting WLAN MAC address information or IP address information configured in the terminal;

Receiving configuration information for configuring a specific bearer via a WLAN carrier;

Receiving data on each of a base station and the WLAN carrier; And

Forwarding data of the specific bearer received on the WLAN carrier to a PDCP entity of a specific bearer in a terminal.
The method of claim 1,

The configuration information,

And information for setting an entity that provides an operation of dividing data received through the WLAN carrier for each specific bearer.
The method of claim 1,

Data received via the WLAN carrier,

And via a GTP-U protocol between the base station and a WLAN end providing the WLAN carrier.
The method of claim 1,

Data received via the WLAN carrier,

And identification information for transmitting data received through the WLAN carrier to a PDCP entity of a specific bearer in the terminal.
The method of claim 4, wherein

The identification information,

And at least one of logical channel identifier information, bearer identification information, and radio bearer index information.
In the method for the base station to transmit data using a WLAN carrier,

Generating configuration information for configuring a specific bearer via a WLAN carrier;

Transmitting the configuration information to a terminal; And

Forwarding data for transmission on the WLAN carrier to a WLAN end point.
The method of claim 6,

The configuration information,

And information for setting an entity in the terminal that provides an operation for distinguishing data transmitted through the WLAN carrier for each specific bearer.
The method of claim 6,

Data transmitted to the WLAN end is,

And via a GTP-U protocol between the base station and a WLAN end providing the WLAN carrier.
The method of claim 6,

Data transmitted through the WLAN carrier,

And the identification information for transmitting the data received through the WLAN carrier to the PDCP entity of a specific bearer in the terminal.
The method of claim 9,

The identification information,

And at least one of logical channel identifier information, bearer identification information, and radio bearer index information.
A terminal for receiving data by merging WLAN carriers,

A transmitter for transmitting WLAN MAC address information or IP address information configured in the terminal;

A receiving unit for receiving configuration information for configuring a specific bearer through a WLAN carrier and receiving data through each of the base station and the WLAN carrier; And

And a controller for transmitting the data of the specific bearer received through the WLAN carrier to the PDCP entity of the specific bearer in the terminal.
The method of claim 11,

The configuration information,

And information for setting an entity that provides an operation of classifying data received through the WLAN carrier for each specific bearer.
The method of claim 11,

Data received via the WLAN carrier,

And a terminal transmitted through a GTP-U protocol between the base station and the WLAN end providing the WLAN carrier.
The method of claim 11,

Data received via the WLAN carrier,

And identification information for transmitting the data received through the WLAN carrier to the PDCP entity of a specific bearer in the terminal.
The method of claim 14,

The identification information,

And one of logical channel identifier information, bearer identification information, and radio bearer index information.
A base station for transmitting data using a WLAN carrier,

A controller configured to generate configuration information for configuring a specific bearer through a WLAN carrier; And

Transmitting the configuration information to the terminal,

And a transmitter for transmitting data for transmission through the WLAN carrier to a WLAN end point.
The method of claim 16,

The configuration information,

The base station, characterized in that it comprises information for setting the entity to the terminal for providing an operation for distinguishing the data transmitted through the WLAN carrier for each specific bearer.
The method of claim 16,

Data transmitted to the WLAN end is,

And a base station carried over a GTP-U protocol between the base station and the WLAN end providing the WLAN carrier.
The method of claim 16,

Data transmitted through the WLAN carrier,

The base station, characterized in that for including the identification information for transmitting the data received via the WLAN carrier to the PDCP entity of a particular bearer in the terminal.
The method of claim 19,

The identification information,

A base station comprising any one of logical channel identifier information, bearer identification information and radio bearer index information.