KR101853527B1 - Methods for processing data using a WLAN carrier and Apparatuses thereof - Google Patents

Abstract

The present invention relates to a method and apparatus for processing data by a terminal and a base station. More particularly, to a method and apparatus for processing user plane data by adding a Wireless Local Area Network (WLAN) to an E-UTRAN carrier at a Radio Access Network (RAN) level. In particular, the present invention provides a method of processing data by a terminal, the method comprising: receiving an interface for transmitting and receiving data through a base station and a WLAN carrier; configuring a user plane entity; receiving user plane data from a base station via an interface; And transmitting control information indicating whether reception of the plane data is successful to the base station through an interface or an interface between the terminal and the base station.

Description

[0001] The present invention relates to a method and apparatus for processing data using a WLAN carrier,

The present invention relates to a method and apparatus for processing data by a terminal and a base station. More particularly, to a method and apparatus for processing user plane data by adding a Wireless Local Area Network (WLAN) to an E-UTRAN carrier at a Radio Access Network (RAN) level.

As communications systems evolved, consumers, such as businesses and individuals, used a wide variety of wireless terminals. In a mobile communication system such as LTE (Long Term Evolution) and LTE-Advanced of the current 3GPP series, a high-speed and large-capacity communication system capable of transmitting and receiving various data such as video and wireless data outside a voice- It is required to develop a technique capable of transmitting large-capacity data in accordance with the above-described method. It is possible to efficiently transmit data using a plurality of cells in a method for transmitting a large amount of data.

However, there is a limit to providing a base station to a plurality of terminals that transmit large amount of data using limited frequency resources. In other words, securing a frequency resource that can be used exclusively by a specific service provider is costly.

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

Accordingly, a mobile communication system is also required to study a technique of transmitting / receiving data to / from a terminal using a corresponding Wi-Fi AP (Access Point).

SUMMARY OF THE INVENTION In view of the foregoing, the present invention provides a method and apparatus for confirming secure transmission of data even when a base station and a terminal transmit and receive data using a WLAN carrier.

Further, the present invention intends to provide a method and apparatus in which the PDCP function in the E-UTRAN can operate in the same manner even when using the WLAN carrier.

According to an aspect of the present invention, there is provided a method of processing data by a terminal, the method comprising: receiving a user plane data from a base station through an interface for transmitting and receiving data through a base station and a WLAN carrier; Receiving; And transmitting control information indicating whether or not the user plane data has been successfully received to the base station through an interface or an interface between the terminal and the base station.

According to another aspect of the present invention, there is provided a method of processing data by a base station, the method comprising: transmitting user plane data to a terminal through an interface for transmitting and receiving data through a WLAN carrier and an interface for configuring a user plane entity; And receiving control information indicating whether the user plane data has been successfully received from the terminal through an interface or an interface between the terminal and the base station.

According to another aspect of the present invention, there is provided a terminal for processing data, comprising: an interface for transmitting and receiving data through a base station and a WLAN carrier; a controller for configuring a user plane entity; a receiver for receiving user plane data from the base station; And transmitting the control information to the base station via an interface or an interface between the terminal and the base station.

According to another aspect of the present invention, there is provided a base station for processing data, the base station including a transmission unit for transmitting user plane data to a terminal through an interface for transmitting and receiving data through a WLAN carrier and a control unit for configuring a user plane object, And a receiving unit for receiving control information indicating whether or not the reception of the received signal is successful from the terminal through an interface or an interface between the terminal and the base station.

The present invention described above provides the effect that the conventional PDCP function operates in the same manner even when the base station and the terminal transmit and receive data by adding a WLAN carrier.

In addition, the present invention provides the effect of enabling data to be transmitted in sequence without duplication of sequence numbers even when a base station and a terminal add WLAN carriers to transmit and receive data.

1 is a diagram illustrating an example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.
2 is a diagram showing another example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.
3 is a diagram showing another example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.
4 is a diagram showing another example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.
5 is a diagram for explaining operations of a terminal according to an embodiment of the present invention.
6 is a diagram illustrating an example of a user plane protocol structure for user plane data transmission according to the present invention.
7 is a diagram illustrating another example of a user plane protocol structure for user plane data transmission according to the present invention.
8 is a diagram illustrating another example of a user plane protocol structure for user plane data transmission according to the present invention.
9 is a view for explaining a base station operation according to another embodiment of the present invention.
10 is a diagram illustrating a terminal configuration according to another embodiment of the present invention.
11 is a diagram illustrating a base station configuration 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, the uplink and downlink are configured on the basis of one carrier or carrier pair to form a standard. 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 PDSCH, and uplink data channel 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.

In the conventional 3GPP Release 12, a technical discussion on 3GPP / WLAN interworking was conducted. 3GPP / WLAN interworking technology provides RAN assisted WLAN interworking. The E-UTRAN may support terminal-based bidirectional traffic steering between the E-UTRAN and the WLAN for terminals in the RRC_IDLE and RRC_CONNECTED states.

The E-UTRAN provides assistance parameters to the terminal via broadcast signaling or dedicated RRC signaling. The RAN helper parameters may include at least one of an E-UTRAN signal strength threshold, a WLAN channel utilization threshold, a WLAN backhaul data rate threshold, a WLAN signal strength, and an Offload Preference Indicator. The E-UTRAN may also provide the terminal with a list of WLAN identifiers via broadcast signaling.

The terminal uses RAN helper parameters to evaluate access network selection and traffic steering rules. When the access network selection and traffic control rules are satisfied, the terminal indicates it to an access stratum (AS) upper layer.

When the UE applies the access network selection and traffic control rules, the UE performs traffic control in units of APN (granularity) between the E-UTRAN and the WLAN. In this way, the RAN assisted WLAN interworking function provides only a way of establishing and interworking E-UTRAN and WLAN in standalone manner.

However, the interworking function described above has a problem that the E-UTRAN and the WLAN are independently constructed and interlocked, and the base station can not control radio resources more tightly considering the radio state or mobility of the UE. Therefore, there is a growing need for a technology that allows tighter integration at the RAN level compared to Release 12 RAN assisted WLAN interworking. That is, when the UE transmits specific user plane data, the E-UTRAN adds a WLAN carrier at the RAN level as one carrier in the E-UTRAN in consideration of the radio state and mobility of the UE and transmits the E-UTRAN carrier and the WLAN carrier There is a problem that it can not be used at the same time. The above-mentioned WLAN carrier refers to a radio resource of a WLAN, which means a WLAN radio link, a WLAN radio, a WLAN radio resource, or a WLAN radio network. Hereinafter, for convenience of understanding, a WLAN radio link, a WLAN radio, a WLAN radio resource, or a WLAN radio network is described as a WLAN carrier.

The E-UTRAN may add a WLAN carrier at the RAN level as one carrier in the E-UTRAN and disconnect the user plane data unit at the E-UTRAN layer 2 to transmit the user plane data via the E-UTRAN carrier and the WLAN carrier split or routing) or interworking may be considered.

For example, the PDCP entity may separately transmit data to be transmitted through the E-UTRAN carrier and / or data to be transmitted through the WLAN carrier, and receive (or merge receive) the PDCP entity with the peered PDCP entity. Alternatively, the PDCP entity may interwork with the data to be transmitted through the WLAN carrier, and may receive the PDCP entity from the peered PDCP entity. For another example, the RLC entity may separately transmit data to be transmitted through the E-UTRAN carrier and / or data to be transmitted through the WLAN carrier, and the peered RLC entity may receive (or merge receive) the same. Alternatively, the RLC entity may interwork with the data to be transmitted through the WLAN carrier, and may receive the data from the peered RLC entity.

However, in the prior art, the PDCP layer is standardized based on the interface with the RLC layer, and the RLC layer is standardized based on the interface with the MAC layer. Therefore, when data to be transmitted through the E-UTRAN carrier and data to be transmitted through the WLAN carrier are separated or interlinked in the PDCP layer or the RLC layer and transmitted through the WLAN carrier, a function required from the lower layer in the PDCP layer or the RLC layer It may not be normally performed. Therefore, when data is transmitted / received through the WLAN carrier, the operation of the PCCP layer or the RLC layer may not operate properly.

For example, the PDCP layer can provide the functions of the PDCP layer through a standardized interface with the lower layer including the RLC layer. For example, the PDCP layer can receive an indication of successful data transfer from the RLC layer, so that the PDCP layer can operate without error in handover. However, when the WLAN carrier is additionally used, such a standardized interface is not determined, so that the operation at the PDCP layer may fail. In this specification, the PDCP layer and the RLC layer can be configured in a terminal or a base station, and entities performing functions in each layer are described as a PDCP entity and an RLC entity. Accordingly, the PDCP layer and the PDCP entity may be used in combination as needed, and may be used in the same sense. Likewise, the RLC layer and RLC entity may be used interchangeably as needed, and may be used in the same sense.

As described above, in the conventional E-UTRAN, in the transmission of specific user plane data, the WLAN carrier is added as one carrier in the E-UTRAN and the user plane data unit is separated or interworked on the E-UTRAN layer 2, The user plane data could not be transmitted through the carrier and the WLAN carrier. Since the PDCP layer of each sublayer on the E-UTRAN layer 2 can provide the functions of the PDCP layer through the standardized interface with the lower layer including the RLC layer, it is possible to transmit the user plane data through the WLAN carrier, There was a problem that the existing operation on the hierarchy might not work properly.

The present invention, which is devised to solve such a problem, adds a WLAN to one carrier in an E-UTRAN when a UE transmits and receives specific user plane data, separates or interlocks user plane data units at a PDCP layer, It is an object of the present invention to provide a separation or interworking method necessary for transmitting user plane data through a carrier and / or a WLAN carrier.

The present invention may be provided in a scenario where a base station (eNodeB) and a WLAN termination are non-co-located. In a scenario where the base station (eNodeB) and the WLAN end are non-co-located, the base station and the WLAN termination can be constructed via non-ideal backhaul or near-ideal backhaul or ideal backhaul. Alternatively, the present invention may be provided in a scenario where a base station (eNodeB) and a WLAN terminal are co-located.

The term WLAN in this context refers to a logical WLAN network node. For example, 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 including an additional function for WLAN merging 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 contained in another entity.

In order for the E-UTRAN to add a WLAN carrier to a terminal in the RAN level as one carrier in the E-UTRAN and transmit and receive user plane data using the E-UTRAN carrier and the WLAN carrier, .

The fact that the E-UTRAN adds the WLAN carrier as one carrier conceptually means that the UE and the base station construct an additional E-UTRAN cell by adding the function for the WLAN carrier.

The E-UTRAN adds the WLAN carrier to the terminal at the RAN level as one carrier in the E-UTRAN and transmits the user plane data in units of radio bearers via the E-UTRAN carrier and / or the WLAN carrier to the E-UTRAN layer 2 The user plane data unit may be split or routed or interworked to transmit user data.

For example, the PDCP entity (or RLC entity) separates and transmits data to be transmitted through the E-UTRAN carrier and data to be transmitted through the WLAN carrier, and receives (or merge receives) it from the peered PDCP entity (or RLC entity) can do. Or the PDCP entity (or the RLC entity) interworkingly transmits the data to be transmitted through the WLAN carrier, and may receive the PDCP entity (or the RLC entity) from the peered PDCP entity (or the RLC entity).

<Data transmission path>

Hereinafter, a scenario is described in which the E-UTRAN adds a WLAN carrier to a terminal in the RAN level as one carrier in the E-UTRAN to transmit and receive user plane data in units of radio bearers via the E-UTRAN carrier and / or the WLAN carrier . That is, uplink and downlink data transmission path scenarios will be described when data to be transmitted through the E-UTRAN carrier and / or data to be transmitted through the WLAN carrier are separated or interlinked in the PDCP layer to transmit user data.

1 is a diagram illustrating an example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.

Referring to FIG. 1, a base station 100 may transmit uplink and downlink data to an SS 120 via an eNB carrier. In addition, the WLAN termination 110 may also transmit and receive both uplink and downlink data to the terminal 120 using a WLAN carrier. That is, both the eNB carrier and the WLAN carrier can process uplink and downlink data.

2 is a diagram showing another example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.

Referring to FIG. 2, the base station 100 may transmit and receive uplink and downlink data to and from the AT 120 via an eNB carrier. On the other hand, the WLAN termination 110 may transmit only downlink data to the terminal 120 using the WLAN carrier. That is, the eNB carrier and the WLAN carrier can be used simultaneously for the downlink, but only the eNB carrier can be used for the uplink.

3 is a diagram showing another example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.

Referring to FIG. 3, both uplink and downlink data may be processed using WLAN carriers. That is, the base station 100 and the WLAN terminal 110 can transmit and receive downlink and uplink data using the WLAN carrier to the terminal 120. [

4 is a diagram showing another example of a data transmission path using an E-UTRAN carrier and a WLAN carrier.

Referring to FIG. 4, the base station 100 may receive uplink data from the terminal 120 using an eNB carrier. The downlink data may also be transmitted using the WLAN carrier via the WLAN termination 110. That is, the eNB carrier can handle uplink transmission and the WLAN carrier can handle downlink transmission, respectively.

1 or 3, it is assumed that the base station 100 is connected to the terminal 120 via the WLAN termination 110 and the terminal 120 is connected to the base station 100 via the WLAN termination 110 for the uplink, Lt; RTI ID = 0.0 &gt; user data &lt; / RTI &gt;

Meanwhile, in the case of FIG. 2 or FIG. 4, a method is required for the base station 100 to transmit user data to the terminal 120 via the WLAN termination 110 for the downlink.

The above-mentioned eNB carrier means an E-UTRAN carrier and means a carrier formed through E-UTRAN radio resources.

< PDCP  Interface layer>

The PDCP layer provides user plane data transmission, header compression, and ciphering services. In addition, the PDCP layer expects the following services to be performed from the lower layers.

An acknowledged data transfer service (PDCP PDU) including an indication of successful delivery of PDCP PDUs,

- unacknowledged data transfer service;

In-sequence delivery (except at re-establishment of lower layers);

- duplicate discarding, except at the re-establishment of lower layers.

On the other hand, competition based multiple access occurs in WLAN compared to E-UTRAN where radio resource management is provided by base station scheduling. Thus, a radio bearer for an unconfirmed data transmission service suitable for delay sensitive services may not be suitable for transmission over a WLAN carrier. Therefore, a detailed description will now be given of confirmation data transmission including an indication of successful delivery of PDCP data (for example, PDCP PDUs or PDCP SDUs) of the above-mentioned services. Hereinafter, PDCP PDUs that the UE receives via the WLAN radio link will be described as an example. However, the PDCP PDUs are merely an example, and can be applied to PDCP SDUs in which user plane data or data, or PDCP SDUs or sequence numbers are associated with each other. That is, PDCP SDUs in which user plane data or data or PDCP SDUs or sequence numbers are associated with each other are used instead of the PDCP PDUs described below, are also included in the embodiment of the present invention.

Most user plane data requiring lossless data transmission uses Acknowledged Mode (AM) RLC. AM RLC guarantees lossless data transmission through retransmission. The receiving side of the AM RLC entity sends an RLC status report to provide a negative acknowledgment for the RLC PDUs not correctly received. The sender of the AM RLC entity retransmits them when an RLC status report is received. The retransmission is repeatedly performed by the receiving side of the AM RLC entity until all RLC PDUs are correctly received or until a maximum number of retransmissions is reached.

On the other hand, if the upper layer requests PDCP re-establishment, the UE performs the following operations.

- reset the header compression protocol (reset the header compression protocol for an IR state in U-mode (if configured);

- apply the encryption algorithm and key provided by the upper layers during the re-establishment procedure;

- Successive delivery of the corresponding PDCP PDU by the lower layer in ascending order of the COUNT value associated with the PDCP SDU before PDCP re-establishment as described below. And performs retransmission of all the PDCP SDUs (from the first PDCP SDU for the successful delivery of the corresponding PDCP PDUs, the retransmission of the PDCP SDUs has not been confirmed by the lower layers, the COUNT values associated with the PDCP SDU prior to the PDCP re-establishment as specified below:

Perform header compression of the PDCP SDU (if configured);

Perform ciphering of the PDCP SDU using the COUNT value associated with this PDCP SDU);

- Submit the PDCP data PDU to the lower layer (submit the resulting PDCP PDU to lower layer).

As described above, with respect to the user plane radio bearer for lossless data transmission, the PDCP entity may retransmit PDCP SDUs when performing a PDCP reset operation by receiving indication / confirmation of successful delivery of PDCP PDUs from the RLC entity.

On the other hand, the PDCP entity requires indication / confirmation of successful delivery of PDCP PDUs in order to control the PDCP sequence number from being duplicated. If no indication / confirmation is provided for successful delivery of PDCP PDUs transmitted over the WLAN carrier, the PDCP entity may generate PDCP data beyond the limited PDCP sequence number, in which case the receiving PDCP entity may process the data in order A difficult problem may arise.

The E-UTRAN may further include a WLAN as a carrier to transmit user plane data for a specific radio bearer, wherein the PDP layer separates or interleaves the user plane data and transmits the user plane data via a WLAN carrier (or an E-UTRAN carrier and a WLAN (Via the carrier). In this case, the PDCP entity must receive indication / confirmation of successful delivery of the PDCP PDUs from the entity transmitting or receiving the PDCP PDUs via the WLAN carrier to retransmit the PDCP SDUs when performing PDCP re-establishment . In addition, the PDCP entity may receive indication / confirmation of the successful delivery of the PDCP PDUs from the entity transmitting or receiving the PDCP PDUs via the WLAN carrier to adjust PDCP data within the limited PDCP sequence number.

Accordingly, an entity that is interfaced with the PDCP entity at the base station and / or the terminal to send or receive PDCP PDUs over the WLAN carrier should be able to provide indication / confirmation of successful delivery of PDCP PDUs to the interfaced PDCP entity.

As described above, the present invention provides a method for enabling a base station to perform a conventional PDCP transmission function in processing data by adding a WLAN carrier as one carrier.

5 is a diagram for explaining operations of a terminal according to an embodiment of the present invention.

A terminal according to an embodiment of the present invention includes an interface for transmitting and receiving data through a base station and a WLAN carrier, a step for configuring a user plane entity, a step for receiving user plane data from a base station through an interface, And transmitting control information indicating the success or failure to the base station through an interface or an interface between the terminal and the base station.

Referring to FIG. 5, the terminal of the present invention includes an interface for transmitting and receiving data through a WLAN carrier with a base station, and configuring a user plane entity (S510). For example, the terminal of the present invention can configure an interface for data transmission / reception with a base station, and configure a data transmission / reception interface using a WLAN carrier. The terminal of the present invention can configure a data transmission / reception interface via a WLAN carrier for each of various scenarios as in the scenario described with reference to Figs. For example, the terminal may configure an interface for receiving downlink data transmitted by the base station using the WLAN termination. Alternatively, the terminal may configure an interface for transmitting uplink data over the WLAN termination. Alternatively, the terminal may configure an interface for data transmission or reception using both the base station and the E-UTRAN carrier and the WLAN carrier.

Meanwhile, the UE can configure a user plane entity to transmit and receive data through the WLAN carrier. The user plane entity may be a functional entity for processing data transmission / reception using a WLAN carrier, and may be composed of a peered entity or a WLAN terminal and a peered entity.

In addition, the user plane entity may be configured for each data radio bearer. That is, whether or not the user plane entity is configured for each data radio bearer can be determined. For example, in the case of a data radio bearer that does not use a WLAN carrier, a user plane entity may not be configured, and a user plane entity may be configured only for a data radio bearer using a WLAN carrier.

The terminal may receive configuration information for configuring the user plane entity from the base station. The configuration information for configuring the user plane entity may be received in the radio bearer configuration information. That is, for the user plane entity configured for each radio bearer, each radio bearer configuration information may include configuration information for the user plane entity. For example, in the case of a radio bearer that transmits and receives data using only an E-UTRAN carrier, the radio bearer configuration information may not include configuration information for configuring a user plane entity. Conversely, in the case of a data radio bearer using a WLAN carrier, the radio bearer configuration information may include configuration information for configuring a user plane entity. The radio bearer configuration information may be received via higher layer signaling. For example, the radio bearer configuration information may be received in an RRC message, such as an RRC connection reconfiguration message.

The terminal of the present invention includes receiving user plane data from a base station through a configured interface (S520). For example, the terminal may receive user plane data using a WLAN carrier according to each scenario as described with reference to Figs. 1-4. In this case, data can be received through the interface using the WLAN carrier configured in step S510. That is, the UE can process the data received through the WLAN carrier through the user plane entity.

The terminal of the present invention includes a step of transmitting control information indicating whether or not the user plane data has been successfully received to the base station through an interface or an interface between the terminal and the base station in operation S530. For example, the control information is information for confirming or displaying the normal arrival of the data transmitted by the PDCP entity. The control information includes the highest PDCP sequence number successfully received / delivered in the PDCP entity (PDCP SUDs / PDUs received from eNB / WLAN termination), the PDCP sequence numbers considered to be lost, and the PDCP data of the highest PDCP sequence number successfully received through the WLAN carrier , User plane data information (e.g., sequence number) that the terminal successfully received via the WLAN carrier, and user plane data information that is considered to be lost. That is, the UE can transmit control information including information indicating whether data received through the WLAN carrier is normally received to the BS.

In this case, the control information may be provided in the user plane entity or the PDCP entity. For example, the user plane entity may check whether the received PDCP PDU is normally received. If a missing PDCP PDU or an out-of-order PDCP PDU is received, the user plane entity may transmit the PDCP PDU to the base station. Alternatively, the PDCP entity may check whether the received PDCP PDU is normally received. If a missing PDCP PDU or an out-of-order PDCP PDU is received, the PDCP entity may transmit the PDCP PDU including the control information to the base station. Alternatively, the control information may be triggered by polling of the base station, a period set by the base station, or a transmission based on a timer. In this case, the terminal may receive the period or timer information for transmitting the control information in advance.

On the other hand, the control information may be transmitted to the base station via an interface configured to process the data using the WLAN carrier. Or control information may be transmitted to the base station via an interface through the E-UTRAN carrier between the terminal and the base station. That is, the control information may be transmitted through the interface using the WLAN carrier, or may be transmitted through the interface using only the E-UTRAN carrier.

In this way, when the user plane entity or the PDCP entity configured in the UE processes the data using the WLAN carrier, it provides the control information on the normal reception status to the base station so that PDCP transmission or PDCP reset within the limited PDCP sequence number It is possible to provide a PDCP PDU retransmission function. Also, the functions provided by the conventional PDCP entity can be similarly provided in the case of data transmission / reception using a WLAN carrier.

Hereinafter, embodiments of the interface configuration and control information transmission according to the present invention will be described with reference to the drawings.

Tunnel-based users Plain  How to use the protocol

6 is a diagram illustrating an example of a user plane protocol structure for user plane data transmission according to the present invention.

In the following embodiments, in order to facilitate understanding, in order to distinguish between the interface constituted when using the above-described WLAN carrier and the interface constituted when using the conventional E-UTRAN carrier, an interface As a Ux interface. For example, a Ux interface may represent an end-to-end interface of a WLAN. For another example, the Ux interface may represent a base station-WLAN end-to-end interface.

A Ux user plane protocol for carrying control information for providing indication or confirmation of the successful delivery of PDCP PDUs on the Ux interface may be provided to the terminal and the base station or terminal and WLAN end of the present invention. The Ux user plane protocol refers to a protocol for controlling the E-UTRAN wireless network user plane data transmission on the Ux interface, and is referred to as Ux UP or Ux UP protocol for convenience of explanation.

Referring to FIG. 6, the Ux UP protocol may be located in a user plane of a radio network layer on an interface connected between the base station 100 and the terminal 120 via a WLAN. Alternatively, the Ux UP protocol may be located in the layer 2 user plane on an interface (Ux interface) that is connected via the WLAN between the base station 100 and the terminal 120. Alternatively, the Ux UP protocol may be located in the PDCP layer user plane on an interface (Ux interface) connected through the WLAN between the base station 100 and the terminal 120. Alternatively, the Ux UP protocol may be located in the RLC layer user plane on an interface (Ux interface) connected between the base station 100 and the terminal 120 via a WLAN. Alternatively, the Ux UP protocol may be located in the lower layer user plane of the PDCP on an interface (Ux interface) connected between the base station 100 and the terminal 120 via WLAN. Alternatively, the Ux UP protocol may be located on the user plane between the PDCP and the RLC layer on an interface (Ux interface) connected between the base station 100 and the terminal 120 via a WLAN.

The UE or the entity in the base station that processes the Ux UP protocol described above may be a user plane entity or a Ux UP protocol entity or a Ux protocol instance or Ux interworking entity or Ux interworking entity or interworking entity or interworking protocol entity or inter- May be variously represented as a working entity or an aggregation entity or a transport protocol entity. Hereinafter, for ease of understanding, the user plane entity or Ux UP protocol entity will be described and described.

A user plane entity may only be associated with one radio bearer (e.g., a data radio bearer). Or each user plane entity may be associated with only one E-RAB.

If configured, the user plane entity may be configured in the base station and the terminal in which the radio bearer is set up / added / set on the Ux interface. For example, the base station may include user plane object configuration information for setting a user plane object in radio bearer configuration information (DRB-ToAddMod) configured bearer-specific (or per radio bearer) It can be delivered to the terminal through a RRC Reconfiguration message.

As shown in FIG. 6, Ux UP protocol data or Ux UP PDU (s) may be included in the GTP-U protocol. Alternatively, Ux UP protocol data or Ux UP SDU (s) or PDCP SDU or PDCP PDU (s) may be included in the GTP-U protocol header as shown in FIG. Alternatively, Ux UP protocol data or Ux UP SDU (s) PDCP SDU or PDCP PDU (s) may be included in the GTP-U Extension header as shown in FIG. 6, the Ux UP protocol data or the Ux UP SDU (s) PDCP SDU (s) or PDCP PDU (s) defines and includes a field (or a container) for the Ux UP protocol in the GTP-U Extension header It is possible.

Meanwhile, the Ux UP protocol can provide a sequence number for user data (or PDCP SDUs / PDUs) transmitted from the base station to the UE via the WLAN carrier. Or the Ux UP protocol may provide a sequence number for user data (or PDCP SDUs / PDUs) transmitted from the terminal to the base station via the WLAN carrier.

The Ux UP protocol may provide control information for confirming / indicating the successful delivery of PDCP SDUs / PDUs transmitted from the base station to the terminal via the WLAN carrier. Or the Ux UP protocol may provide control information for confirming / indicating successful delivery of PDCP SDUs / PDUs transmitted from the UE to the Node B via the WLAN carrier.

When user plane data for a particular radio bearer (or E-RAB) is transmitted over the Ux interface, the user plane entity activates a procedure to provide control information for acknowledging / indicating successful delivery of PDCP SDUs / PDUs .

For example, in the case of downlink data transmission, the base station assigns a consecutive Ux-UP sequence number to each transmitted Ux-UP packet. The UE detects whether a Ux-UP packet is lost at a predetermined period set by the BS or when a request from the BS occurs. Or the UE detects whether the Ux-UP packet is lost or not by the polling field setting included in the Ux-UP packet header by the base station. Alternatively, when downlink data is received using both the E-UTRAN carrier and the WLAN carrier, the UE can detect whether the packet is lost by the reordering function of the PDCP entity and deliver it to the user plane entity.

If an out-of-order or lost Ux-UP packet is detected, the UE receives the highest Ux-UP sequence number successfully received, the highest PDCP sequence number successfully received, and the PDCP sequence One or more of the numbers can be transmitted to the base station. Alternatively, the UE may transmit the highest Ux-UP sequence number successfully received successfully and the highest received PDCP sequence number successfully and in a predetermined period or when a base station's request occurs, or according to the polling field setting, It may transmit one or more of the PDCP sequence numbers considered to be lost to the base station.

Or the UE detects whether the Ux-UP packet has been lost at regular intervals set by the base station or at the request of the base station or by the setting of the polling field included in the Ux-UP packet header from the base station or constantly. If an out-of-sequence or missing Ux-UP packet is detected, the UE shall notify the UE of the highest PDCP sequence number successfully received, the sequence number of the Ux-UP packet declared lost by the UE, The PDCP PDU sequence number, and the PDCP PDU sequence number. At least one of the highest PDCP sequence number successfully received by the UE, the sequence number of the Ux-UP packet declared lost by the UE, and the PDCP PDU sequence number declared lost by the UE, Lt; / RTI &gt;

In one example, the control information may be transmitted via the uplink Ux interface. As another example, the control information may be transmitted via the uplink Uu interface between the base station and the terminal. The Uu interface represents a conventional base station to terminal interface over an E-UTRAN carrier. If transmitted via the Uu interface, the control information may be provided via the PDCP Control PDU. For example, a PDCP STATUS report may be used. Or via a new format PDCP Control PDU for control information transmission.

Meanwhile, the UE can declare a Ux-UP packet that is not received according to a predetermined period or a request from the BS to be lost. Alternatively, the UE may declare the Ux-UP packet that has not been received regularly or in accordance with the polling field setting included in the Ux-UP packet header from the base station to be lost. Alternatively, the UE may declare a Ux-UP packet that has not been received after receiving an out-of-order Ux-UP packet as lost. Alternatively, the UE may receive a Ux-UP packet out of order and may declare the Ux-UP packet that was not received after the expiration time of the base station has passed, to be lost.

The above description has been made on the case where the user plane entity confirms whether the user plane data received using the WLAN carrier is normally received and transmits the control information. However, in the above description, a method of confirming out-of-order data or missing data using a separate sequence number for data received through the WLAN carrier in the user plane entity has been described.

Alternatively, the Ux UP protocol does not provide a sequence number for the user data (or PDCP SDUs / PDUs) transmitted via the WLAN carrier, but uses the sequence number of the SDUs / PDCP PDUs to transmit the PDCP May provide control information to acknowledge / indicate successful delivery of SDUs / PDUs.

For example, in the case of downlink data transmission, the UE detects whether a predetermined period set by the base station or the request or polling field setting of the base station or the Ux-UP packet has been lost at all times.

If a Ux-UP packet out of sequence or lost Ux-UP packet is detected or a lost Ux-UP packet is detected, the UE can transmit the successfully received highest PDCP sequence number to the BS. Alternatively, the UE may transmit the highest PDCP sequence number successfully received at regular intervals or at the request of the base station, or according to the polling field setting included in the Ux-UP packet header from the base station, or always successfully.

Alternatively, the terminal detects whether a predetermined period set by the base station or a request or polling field setting of the base station or a Ux-UP packet has been lost at all times. If a Ux-UP packet out of sequence is detected or a lost Ux-UP packet is detected, the UE receives one or more of the highest PDCP sequence number successfully received and the PDCP PDUs sequence number declared lost by the UE To the base station. Alternatively, the UE may transmit to the Node B one or more of a predetermined period or a request or a polling field setting of the Node B or a highest PDCP Sequence Number that has successfully been successfully received and a PDCP PDU Sequence Number declared to be lost by the UE. Also in this case, information on the highest PDCP sequence number successfully received and PDCP PDUs sequence number declared lost by the UE may be included in the control information.

In one example, the control information may be transmitted via the uplink Ux interface. As another example, the control information may be transmitted via the uplink Uu interface between the base station and the terminal. If the control information is transmitted via the Uu interface, it may be provided via the PDCP Control PDU. For example, control information may be transmitted using a PDCP STATUS report. Or the control information may be transmitted via the PDCP Control PDU in the new format.

On the other hand, the terminal may transmit the Ux-UP packet, which is out of order, at regular intervals set by the base station, or at the request of the base station, or by setting the polling field included in the Ux-UP packet header from the base station, UP packet that has not been received after the UE has received the Ux-UP packet out of order and the expiration time has expired by the base station, the Ux-UP packet can be declared lost.

In the above description, the transmission of the control information indicating successful data success in the case where the terminal receives the downlink data has been described. However, even when the base station receives the uplink data, the same operation can be performed have.

On the other hand, in case of downlink transmission, the BS can remove the buffered PDCP SDUs / PDUs according to the feedback of successfully transmitted PDCP SDUs / PDUs. Likewise, in the case of uplink transmissions, the UE can remove the buffered PDCP SDUs / PDUs according to the feedback of the successfully delivered PDCP SDUs / PDUs.

7 is a diagram illustrating another example of a user plane protocol structure for user plane data transmission according to the present invention.

In FIG. 7, the WLAN termination 110 indicates that routing is performed in the IP layer, but it is also within the scope of the present invention that the WLAN termination 110 performs routing / switching or MAC switching on the Data Link Layer.

 The GTP tunnel can be set up in the base station 100 and the terminal 120 as shown in FIG. For example, when performing a downlink transmission through a WLAN carrier as in the scenario of FIG. 1 to FIG. 4, the base station 100 uses the downlink tunnel to transmit user data to be transmitted or separated through the WLAN carrier to the GTP protocol Or GTP-U protocol or WLAN interworking tunnel protocol or any tunnel protocol). As another example, when performing an uplink transmission through a WLAN carrier as in the scenario of FIGS. 1 and 3, the terminal 120 uses the uplink tunnel to transmit user data to be transmitted, separated or interworked via the WLAN carrier, (Or GTP-U protocol or WLAN interworking tunnel protocol or arbitrary tunnel protocol).

A tunnel between the base station 100 and the terminal 120 (e.g., any tunnel based on GTP tunnel or header encapsulation) may be used to encapsulate user data packets (or packets) encapsulated between a given pair of tunnel endpoints E-UTRAN Layer 2 SDU / PDU or E-UTRAN Layer 2 user data).

For example, when separating or linking data to be transmitted through the E-UTRAN carrier and / or data to be transmitted through the WLAN carrier in the PDCP layer or the PDCP entity, the tunnel between the base station 100 and the terminal 120 may include a tunnel endpoint tunnel endpoints pair between PDCP PDUs or PDCP PDUs.

As another example, when the RLC layer or the RLC entity separates or links the data to be transmitted through the E-UTRAN carrier and / or the data to be transmitted through the WLAN carrier, the tunnel between the base station 100 and the terminal 120 may include a tunnel endpoint tunnel endpoints pair between the RLC PDUs.

A tunnel protocol header (for example, a GTP header or header on any tunnel based on header encapsulation) of the tunnel between the base station 100 and the terminal 120 may include a tunnel endpoint identification information (e.g., a TEID) field . This field may be used to identify a receiving tunneling protocol entity (GTP-U protocol entity or GTP protocol entity or interworking entity or interworking protocol entity or GTP tunnel entity or GTP-U tunnel entity or GTP entity or GTP-U entity or interworking entity, unambiguously identifies a tunnel endpoint within an aggregation entity or merge protocol entity or transport protocol entity, hereinafter referred to as a tunnel protocol entity.

A tunnel endpoint included in a tunnel protocol header may indicate a tunnel to which a particular user data packet belongs.

Or a tunnel endpoint included in a tunnel protocol header may indicate a radio bearer or a radio bearer entity to which a particular user data packet belongs. Or a tunnel endpoint included in the tunnel protocol header may cause a specific user data packet to be mapped to a corresponding radio bearer or a corresponding radio bearer entity.

The tunnel endpoint identification information (e.g., TEID) included in the tunnel protocol header may demultiplex the incoming traffic and be transmitted to the corresponding user plane radio bearer entity.

For example, when data to be transmitted through the E-UTRAN carrier and / or data to be transmitted through the WLAN carrier are separated or interlinked by the base station PDCP entity, the terminal receiving the data through the downlink tunnel transmits the received data to the tunnel end PDCP SDUs / PDUs may be delivered to the peered or corresponding intra-UE PDCP entity through the point identification information.

Base station WLAN End-to-end  Use objects for merging / linking

In order for the E-UTRAN to add a WLAN carrier as a carrier in the PDCP layer and use the carrier and the WLAN carrier simultaneously to transmit the downlink user data traffic, an aggregation entity for merging / ) May be required. The merge entity may be an interworking entity, an LTE-WLAN adaptation entity, an interworking function, a logical entity for LTE-WLAN aggregation, an LTE-WLAN merge entity, etc. Is used to mean both. In addition, depending on the situation, the merge entity may refer to the user plane entity described above.

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

The merge entity may be implemented as a higher layer entity than L1 / L2. For example, when it is configured as a functional entity included in the WLAN end, it can operate as a higher layer entity than the WLAN L1 / L2 and transmit user plane data to the terminal through the WLAN L1 / L2. For example, when configured as a functional entity included in a base station, the base station may operate as an upper layer entity (for example, an IP layer or a session layer or an application layer) to transmit user plane data to a terminal over a WLAN termination. For example, when the PDCP PDU is configured as a functional entity included in a base station, the PDCP PDU may function as an entity for performing PDCP PDUs through the WLAN termination and transmit user plane data to the terminal through the WLAN termination. Alternatively, the merge entity may be configured as a function within the WLAN L2 to allow the WLAN L2 entity to implement the operation for it.

The merge entity may receive PDCP PDUs from the PDCP entity of the base station. Or may receive PDCP PDUs by requesting PDCP PDUs with the PDCP entity of the base station.

The merge entity may transmit the received PDCP PDUs to the terminal via the WLAN carrier. Or the merging entity may transmit the received PDCP PDUs to the terminal using the WLAN L1 / L2 protocol. Or the merge entity may transmit the received PDCP PDUs to the terminal via the WLAN end (or WLAN carrier) using IP communication.

The UE can transmit the PDCP PDUs received through the WLAN carrier to the corresponding PDCP entity in the UE. Alternatively, the terminal may transmit the received PDCP PDUs to the corresponding intra-terminal PDCP entity using the WLAN L1 / L2 protocol in the terminal.

 The BS can separate data traffic belonging to a specific bearer from the PDCP layer through the WLAN end and transmit the data traffic. That is, the PDCP entity may separately transmit the PDCP PDUs to the associated RLC entity and / or the associated merge entity in order to transmit the user plane data through the E-UTRAN carrier and the WLAN carrier in units of the radio bearer. In order to transmit user plane data over an E-UTRAN carrier and a WLAN carrier on a per-radio bearer basis from a PDCP entity, the base station must determine whether the terminal is capable of communicating over the WLAN carrier (or via the WLAN L1 / The PDCP entity can be configured to be able to deliver the received PDCP PDUs to the PDCP entity of the corresponding specific bearer in the terminal. Or to transmit user plane data over an E-UTRAN carrier and a WLAN carrier in a PDCP entity on a per-radio bearer basis, the base station determines whether the terminal is capable of transmitting the user plane data over the WLAN carrier (or via the WLAN L1 / The PDCP entity may send the received PDCP PDUs to the PDCP entity of the corresponding specific bearer in the terminal.

8 is a diagram illustrating another example of a user plane protocol structure for user plane data transmission according to the present invention.

User plane data (PDCP PDUs) on an interface between the base station 100 and the WLAN end 110 in a scenario where the base station 100 and the WLAN end 110 are non-co-located can be carried over the GTP-U protocol . An interface between the base station 100 and the WLAN terminal 110 in the scenario where the base station 100 and the WLAN terminal 110 are non-co-located is provided with an E for a bearer provided through the base station 100 and the WLAN terminal 110 When associated with the RAB, the GTP-U can carry PDCP PDUs.

When the E-UTRAN configures the LTE-WLAN merging to add the WLAN carrier as one carrier and to use the E-UTRAN carrier and the WLAN carrier simultaneously to transmit the downlink user data traffic, the base station 100 and the WLAN termination A user data bearer is set up in an interface between the base station 100 and the WLAN terminal 110, and a user plane protocol instance (UP Protocol entity) is set in the base station 100 and the WLAN terminal 110, respectively, as shown in FIG.

Each user plane protocol instance or UP protocol entity on the interface between the base station 100 and the WLAN end 110 is associated with one E-RAB. Thus, each E-RAB is associated with the user plane data bearer on the interface between the base station 100 and the WLAN end 110 or the endpoints of the user plane data bearer of the base station 100 associated with the bearer, The endpoints of the WLAN endpoints 110 may be identified using a GTP Tunnel endpoint IE (Information Element), respectively.

The merge entity included in the aforementioned WLAN termination 110 may include a user plane instance / entity in the WLAN termination 110 described above. Or merge entity may operate in conjunction with the user plane instance / entity in WLAN termination 110 described above. Or merge entity may operate as a user plane instance / entity within WLAN end 110 as described above.

In another scenario, the user plane data (PDCP PDUs) on the interface between the base station 100 and the WLAN end 110 in a scenario where the base station 100 and the WLAN end 110 are non-co- And transmitted. The base station 100 includes PDCP PDUs (user plane data) to be transmitted to the terminal 120 through the WLAN termination 110 in the data field of the IP packet and uses the IP address of the terminal 120 as the destination address, ) To the terminal 120

Alternatively, user plane data (PDCP PDUs) on an interface between the base station 100 and the WLAN end 110 in a scenario where the base station 100 and the WLAN end 110 are non-co-located include WLAN L2 (or WLAN MAC ) &Lt; / RTI &gt; protocol payload. The base station 100 includes PDCP PDUs (user plane data) to be transmitted to the terminal 120 through the WLAN termination 110 in the data field of the WLAN L2 (or WLAN MAC) frame to transmit the WLAN MAC address of the terminal 120 to the destination Address to the terminal 120 via the WLAN termination 110. [

If the user plane protocol instance (UP Protocol entity) included in the WLAN termination 110 described above is determined to trigger the feedback for downlink data transfer, the PDCP PDUs received from the base station 100, , A buffer size for the corresponding E-RAB, and a user plane protocol instant packet that is considered to be lost, to the base station 100.

To this end, the base station 100 may receive information on the successful reception of the PDCP PDUs from the terminal 120 by the following methods. The function of receiving the control information for successful reception of the PDCP PDUs from the terminal 120 may be included in the merge entity function described above. As described below, when the UE 120 configures a partial RLC entity for the bearer and transmits successful reception control information of the PDCP PDUs, the merge entity receives the partial RLC entity through a partial RLC entity that is peered to the partial RLC entity, can do. In addition, when the UE transmits successful reception control information of the PDCP PDUs to the bearer through the PDCP entity, the merged entity can receive and process the PDCP PDCP through the peered PDCP.

Partial RLC  Configure and use protocol actions

As described above, an interface connected through a WLAN carrier between a base station and a terminal is defined as a Ux interface. (E.g., RLC Status reporting function) for the ARQ procedure of the RLC layer in the UP protocol entity when the user plane entity is configured between the base station and the WLAN end in the user plane entity. That is, it is possible to provide some functions for an ARQ procedure (for example, RLC Status reporting function) of the conventional RLC layer through a new user plane entity (for example, a user plane sublayer entity) in the UE. In the case of LTE-WLAN merging, this is a separate user plane entity separate from the RLC entity for processing PDCP PDUs received over the LTE radio link. For example, a WLAN RLC entity that is distinct from an LTE RLC entity. Hereinafter, this is referred to as a user plane object for convenience of explanation. This is for convenience of explanation and does not limit the name.

The user plane entity may send PDCP PDUs to its peer user plane entity. And provide control information to provide indication / confirmation of successful delivery of PDCP PDUs on the Ux interface at the user plane entity.

For example, in the case of downlink transmission, the user plane entity of the base station may send PDCP PDUs to the user plane entity of the UE. The UE user plane entity may provide control information to the base station including indication / confirmation information for the successful delivery of the downlink PDCP PDUs. That is, the user plane entity of the terminal may send control information to the WLAN end including indication / confirmation of successful delivery of the downlink PDCP PDUs. The WLAN termination may transmit it to the user plane entity of the base station.

For another example, in the case of downlink transmission, the user plane entity at the WLAN end may send the PDCP PDUs received from the base station to the user plane entity of the terminal. The UE user plane entity may send control information including indication / confirmation information for the successful delivery of the downlink PDCP PDUs to the user plane entity at the WLAN end. The user plane entity of the WLAN end can provide it to the base station. That is, the user plane entity of the terminal may transmit control information to the base station over the WLAN termination, including indication / confirmation of successful delivery of the downlink PDCP PDUs.

As an example, STATUS reporting can be triggered whenever the peer user plane entity transmits data. For example, in the case of downlink data transmission, the user plane entity of the terminal may trigger STATUS reporting whenever it receives data.

As another example, STATUS reporting can be triggered at a period set by the base station. For example, in the case of downlink data transmission, the user plane entity of the terminal may trigger STATUS reporting at a period set by the base station.

As another example, STATUS reporting can be triggered by polling from the peer user plane entity. For example, in the case of downlink data transmission, the user plane entity of the terminal may trigger STATUS reporting by polling from the base station user plane entity or by polling to the WLAN end user plane entity. To this end, the Ux UP protocol / UP protocol header may have a polling field, and upon receipt of a Ux UP PDU / UP PDU with the polling field set, it may trigger STATUS reporting.

As another example, STATUS reporting can be triggered upon detecting a failure to receive one Ux UP PDU / UP PDU. For example, in the case of downlink data transmission, a user plane entity of the UE can operate a timer when it receives an out of order Ux UP PDU. When the timer expires, the user plane entity of the terminal may trigger STATUS reporting.

The base station may include configuration information for indicating the user plane entity performing the partial RLC function in the RRC reconfiguration message to the UE. When the user plane entity is set according to the configuration information of the base station, the UE performing the partial RLC function through the user plane entity provides control information including indication / confirmation of successful delivery of the downlink PDCP PDUs to the base station can do. That is, the user plane entity of the terminal may send control information to the WLAN end including indication / confirmation of successful delivery of the downlink PDCP PDUs. The WLAN termination may transmit it to the user plane entity of the base station.

In case of downlink transmission, the base station or the WLAN end can remove the buffered PDCP PDUs according to the feedback of successfully delivered PDCP PDUs. In case of uplink transmission, the UE can remove the buffered PDCP PDUs according to the feedback of the successfully delivered PDCP PDUs.

Ux UP protocol data / UP protocol data or Ux UP PDU (s) / UP PDU may be included in the GTP-U protocol / IP protocol / WLAN MAC protocol data field. Or Ux UP protocol data / UP protocol data or Ux UP PDU (s) / UP PDU (s) may be included in the GTP-U protocol / IP protocol / MAC protocol payload. The Ux UP protocol header / UP protocol header may include a field for distinguishing between user plane data (PDCP PDUs) and control plane data (feedback).

Tunnel endpoint identification information (e.g., TEID) included in the tunnel protocol header (e.g., a header on any tunnel based on GTP header or header encapsulation) demultiplexes the incoming traffic To be forwarded to the corresponding user plane entity.

For example, when data to be transmitted through the E-UTRAN carrier and / or data to be transmitted through the WLAN carrier are separated or interworked in the base station user plane entity, data is transmitted through the WLAN termination connected through the downlink tunnel or the downlink tunnel The receiving terminal may forward the PDCP PDUs to the peered or corresponding user plane entity in the terminal through the identification information included in the tunnel endpoint identification information / UP protocol field.

As another example, when data is interworkingly transmitted through a WLAN carrier in a UE plane plane entity, a base station receiving data through an uplink tunnel or an WLAN end connected through an uplink tunnel transmits PDCP PDUs through the tunnel endpoint identification information To the user plane entity in the peered or corresponding base station.

As another example, when data to be transmitted through the E-UTRAN carrier and / or data to be transmitted through the WLAN carrier are separated or interworked in the base station PDCP entity, data is transmitted through the WLAN termination connected through the downlink tunnel or the downlink tunnel The receiving terminal may transmit the PDCP PDUs to the peered or corresponding intra-terminal PDCP entity through the identification information included in the tunnel end point identification information / UP protocol field.

PDCP Control PDUs  use

As described above, an interface connected through a WLAN between a base station and a terminal is defined as a Ux interface. PDCP entity may provide control information to provide indication / acknowledgment of successful delivery of PDCP SDUs / PDUs on the Ux interface.

For example, in the case of downlink data transmission, a terminal may transmit data at a predetermined period set by the base station, or at the request of the base station, or by the base station setting the polling field included in the PDCP header, And detects whether the received PDCP SDUs / PDUs have been lost. If PDCP SDUs / PDUs out of order are detected or missing PDCP SDUs / PDUs are detected, the UE can transmit the highest received PDCP sequence number to the BS. Alternatively, the terminal may transmit the highest received PDCP sequence number to the base station by a constant period set by the base station or by a request of the base station or by a polling field setting included in the PDCP header from the base station. Or the UE detects whether the PDCP SDUs / PDUs received via the Ux interface have been lost for a predetermined period set by the base station or the request or poll field setting of the base station or always. If out-of-order PDCP PDUs are detected or missing PDCP SDUs / PDUs are detected, the terminal may transmit the sequence number of the PDCP PDUs declared lost by the terminal to the base station. Alternatively, the terminal may transmit to the base station the sequence number of the PDCP SDUs / PDUs declared to be lost by the terminal, either by a predetermined period set by the base station or by a request or poll field setting of the base station or always.

As described above, the highest PDCP sequence number successfully received or the sequence number information of the PDCP SDUs / PDUs declared to be lost by the UE may be included in the control information for successful receipt / display of the above-described data.

In one example, the control information may be transmitted via the uplink Ux interface. As another example, the control information may be transmitted via the uplink Uu interface between the base station and the terminal. For example, control information may be delivered using a PDCP STATUS report. Or control information may be delivered via the PDCP Control PDU in the new format.

On the other hand, the UE can receive PDCP SDUs / PDUs out of order at regular intervals set by the base station, or at the request of the base station, or by setting a polling field in the PDCP SDU / PDU header from the base station, PDCP SDUs / PDUs that have been out of order and that have not been received after the expiration time set by the base station may be declared lost.

In case of downlink transmission, the base station may remove the buffered PDCP SDUs / PDUs according to the feedback of successfully delivered PDCP SDUs / PDUs. For uplink transmissions, the terminal may remove the buffered PDCP SDUs / PDUs according to the feedback of successfully delivered PDCP SDUs / PDUs.

The base station may configure the UE to transmit control information for indicating / confirming successful delivery of PDCP SDUs / PDUs on the Ux interface using PDCP Control SDUs / PDUs. Alternatively, the terminal may be configured to provide information for instructing to provide control information for indication / confirmation of successful delivery of the PDCP SDUs / PDUs using PDCP Control SDUs / PDUs. The base station transmits control information for indicating / confirming successful delivery of the PDCP SDUs / PDUs on the Ux interface using the PDCP Control SDUs / PDUs to the radio bearer configuration information (DRB-ToAddMod) or PDCP configuration information (PDCP-CONFIG) (E.g., a timer or a PollPDU or a PollByte) for instructing the mobile terminal to transmit the information to the mobile terminal.

The operation of transmitting the control information for confirming the data transmission and the normal reception of the data using the WLAN carrier according to each embodiment of the present invention has been described above. For convenience of explanation, the case where the terminal receives the downlink data using the WLAN carrier has been described above. However, even when the base station receives the uplink data using the WLAN carrier, each of the above-described embodiments can be applied to the same subject only by varying the subject.

Hereinafter, the operation of the base station when the above-mentioned terminal receives downlink data will be described with reference to the drawings. Of course, the operation when the terminal transmits the uplink data can also be applied equally to the base station operation and the main body only, which will be described below.

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

A base station according to another exemplary embodiment of the present invention includes an interface for transmitting and receiving data through a WLAN carrier and a terminal, a step for configuring a user plane entity, a step for transmitting user plane data to the terminal through an interface, And receiving control information indicating success or failure from the terminal through an interface or an interface between the terminal and the base station.

Referring to FIG. 9, the base station includes an interface for transmitting and receiving data through a WLAN carrier and a step of configuring a user plane entity (S910). For example, the base station of the present invention can configure an interface for data transmission / reception with a terminal, and configure a data transmission / reception interface using a WLAN carrier. As shown in the scenario described with reference to FIGS. 1 to 4, the base station of the present invention can configure a data transmission / reception interface via a WLAN carrier for each of various scenarios. For example, the base station may configure an interface for transmitting downlink data to be transmitted to the terminal using the WLAN termination. Alternatively, the base station may configure an interface for receiving uplink data over the WLAN termination. Alternatively, the base station may configure an interface for data transmission or reception using both the E-UTRAN carrier and the WLAN carrier.

Meanwhile, the base station can configure the user plane entity to transmit and receive data through the WLAN carrier. The user plane entity may be a functional entity for processing data transmission / reception using a WLAN carrier, and may consist of an entity peered with the terminal.

In addition, the user plane entity may be configured for each data radio bearer. That is, whether or not the user plane entity is configured for each data radio bearer can be determined. For example, in the case of a data radio bearer that does not use a WLAN carrier, a user plane entity may not be configured, and a user plane entity may be configured only for a data radio bearer using a WLAN carrier.

The base station may transmit configuration information for configuring the user plane entity to the terminal. The configuration information for configuring the user plane entity may be received in the radio bearer configuration information. That is, for the user plane entity configured for each radio bearer, each radio bearer configuration information may include configuration information for the user plane entity. For example, in the case of a radio bearer that transmits and receives data using only an E-UTRAN carrier, the radio bearer configuration information may not include configuration information for configuring a user plane entity. Conversely, in the case of a data radio bearer using a WLAN carrier, the radio bearer configuration information may include configuration information for configuring a user plane entity. The radio bearer configuration information may be transmitted via higher layer signaling. For example, the radio bearer configuration information may be included in an RRC message, such as an RRC connection reconfiguration message.

The base station includes transmitting the user plane data to the terminal through the interface (S920). For example, the base station may transmit user plane data using a WLAN carrier according to each scenario as described with reference to Figures 1-4. In this case, the data can be transmitted through the interface using the WLAN carrier configured in step S910. That is, the base station can process the data to be transmitted through the WLAN carrier through the user plane entity.

The base station includes receiving control information indicating whether or not the user plane data has been successfully received from the terminal through an interface or an interface between the terminal and the base station (S930). For example, the control information may include information for confirming or displaying normal arrival of data transmitted by the PDCP entity. That is, the UE transmits control information including information indicating whether data received through the WLAN carrier is normally received to the BS, and the BS can receive the control information.

In this case, the control information may be provided in the user plane entity or the PDCP entity. For example, the user plane entity of the UE may check whether the received PDCP PDU is normally received. If a missing PDCP PDU or an out-of-order PDCP PDU is received, the user plane entity may transmit the PDCP PDU included in the control information to the base station. Alternatively, if the PDCP entity of the UE confirms that the received PDCP PDU is normally received and if a missing or out-of-order PDCP PDU is received, the PDCP entity may transmit the PDCP PDU to the base station. Alternatively, the control information may be triggered by polling of the base station, a period set by the base station, or a transmission based on a timer. In this case, the base station may transmit the period or the timer information for transmitting the control information in advance.

On the other hand, the control information may be received by the base station via an interface configured to process the data using the WLAN carrier. Or the control information may be received by the base station through an interface between the terminal and the base station that does not use the WLAN carrier. That is, the control information may be received via the interface using the WLAN carrier or via the interface using only the E-UTRAN carrier.

The present invention described above provides the effect that the conventional PDCP function operates in the same manner even when the base station and the terminal transmit and receive data by adding a WLAN carrier. In addition, the present invention provides an advantage of allowing a base station and a terminal to perform a retransmission procedure by confirming the completion of data reception even when transmitting and receiving data by adding a WLAN carrier.

A configuration of a terminal and a base station through which each of the embodiments of the present invention described above can operate will be described with reference to the drawings.

10 is a diagram illustrating a terminal configuration according to another embodiment of the present invention.

10, a terminal 1000 according to another embodiment of the present invention includes an interface for transmitting and receiving data through a WLAN carrier and a base station, a controller 1010 for configuring a user plane entity, A receiving unit 1030 for receiving plane data and a transmitting unit 1020 for transmitting control information indicating whether or not the user plane data has been successfully received to an interface or an interface between the terminal and the base station.

In addition, the controller 1010 can configure a user plane entity in association with each data radio bearer. The control unit 1010 adds a WLAN carrier to one carrier in the E-UTRAN in order to transmit the specific user plane data required for performing the above-described present invention, separates or interlocks the user plane data unit on the PDCP layer And controls the overall operation of the terminal according to the separation or interworking operation required to transmit the user plane data through the E-UTRAN carrier and / or the WLAN carrier.

Receiving unit 1030 may receive radio bearer configuration information including configuration information for configuring a user plane entity through higher layer signaling. In addition, the receiving unit 1030 receives downlink control information, data, and messages from the base station via the corresponding channel.

Transmitter 1020 may transmit control information including information for successful receipt / display of received data using an interface via a WLAN carrier or an interface between a terminal and a base station. The control information may be provided in a user plane entity or a PDCP entity. The control information may be triggered based on at least one of a polling of the base station, a period set by the base station, and a timer. The transmission unit 1020 transmits uplink control information, data, and a message to the base station through the corresponding channel.

In addition, the control unit 1010, the transmitting unit 1020, and the receiving unit 1030 can perform all the operations of the terminal 100 necessary for performing the present invention described with reference to FIGS. 1 to 9.

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

11, a base station 1100 according to another embodiment of the present invention includes an interface for transmitting and receiving data via a WLAN carrier and a controller 1110 for configuring a user plane entity, And a receiving unit 1130 for receiving control information indicating whether or not the user plane data has been successfully received from the terminal through an interface or an interface between the terminal and the base station.

The controller 1110 may configure a user plane entity by being linked with each data radio bearer. In addition, when transmitting and receiving specific user plane data required to perform the above-described present invention, the controller 1110 adds a WLAN carrier as one carrier in the E-UTRAN and separates or interlocks the user plane data units on the PDCP layer To control the operation of the overall base station 1100 according to the isolation or interlocking operation required to transmit and receive user plane data over the E-UTRAN carrier and / or the WLAN carrier.

The transmitting unit 1120 may transmit the radio bearer configuration information including the configuration information for configuring the user plane entity to the UE through higher layer signaling.

The receiving unit 1130 can receive control information indicating whether or not the user plane data has been successfully received from the terminal through an interface or an interface between the terminal and the base station. The control information may be provided from a user plane entity or a PDCP entity of the UE. In addition, the control information may be received and triggered by transmission based on at least one of a polling of the base station, a period set by the base station, and a timer.

In addition, the transmitting unit 1120 and the receiving unit 1130 are used to transmit and receive signals, messages, and data necessary for performing the above-described present invention to and from the terminal.

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 some of the standard documents is added to or contained in the scope of the present invention, as falling within 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 (20)

In a method for a terminal to process data,
Constructing a user plane entity for receiving data from a base station via a WLAN carrier;
Receiving user plane data from the base station through the user plane entity; And
And transmitting control information indicating whether or not the user plane data is successfully received through the WLAN carrier to the base station through an interface between the base station and the base station,
Further comprising receiving, by upper layer signaling, radio bearer configuration information or PDCP configuration information including a parameter for transmitting the control information,
Wherein the parameter for transmitting the control information includes transmission method information and transmission period information of the control information,
The control information includes:
Wherein the transmission is triggered based on at least one of a polling of the base station, a period set by the base station, and a timer. The method according to claim 1,
The user plane entity includes:
Gt; a &lt; / RTI &gt; lower layer of the PDCP layer. The method according to claim 1,
The parameter for transmitting the control information includes:
Further comprising information instructing transmission of the control information. The method according to claim 1,
The control information includes:
Wherein the user plane entity or the PDCP entity is provided in the user plane entity or the PDCP entity. delete A method for a base station to process data,
Configuring a user plane entity for transmitting data to a terminal via a WLAN carrier;
Transmitting user plane data to the terminal through the user plane entity; And
Receiving control information indicating whether the user plane data is successfully received through the WLAN carrier from the terminal through an interface between the terminal and the base station,
Further comprising transmitting, by the upper layer signaling, radio bearer configuration information or PDCP configuration information including a parameter for transmitting the control information of the UE to the UE,
Wherein the parameter for transmitting the control information includes transmission method information and transmission period information of the control information,
The control information includes:
Wherein the transmission is triggered based on at least one of a polling of the base station, a period set by the base station, and a timer. The method according to claim 6,
The user plane entity includes:
Gt; a &lt; / RTI &gt; lower layer of the PDCP layer. The method according to claim 6,
The parameter for transmitting the control information includes:
Further comprising information instructing transmission of the control information. The method according to claim 6,
The control information includes:
Wherein the PDCP entity is provided in the user plane entity or the PDCP entity of the UE. delete A terminal for processing data,
A controller configured to configure a user plane entity for receiving data from a base station via a WLAN carrier;
A receiving unit for receiving user plane data from the base station through the user plane entity; And
And a transmitter for transmitting control information indicating whether the user plane data is successfully received through the WLAN carrier to the base station through an interface between the terminal and the base station,
The receiver may further comprise:
Further receiving radio bearer configuration information or PDCP configuration information including parameters for transmission of the control information through higher layer signaling,
Wherein the parameter for transmitting the control information includes transmission method information and transmission period information of the control information,
The control information includes:
Wherein the transmission is triggered based on at least one of a polling of the base station, a period set by the base station, and a timer. 12. The method of claim 11,
The user plane entity includes:
And the PDCP layer. 12. The method of claim 11,
The parameter for transmitting the control information includes:
Further comprising information for instructing transmission of the control information. 12. The method of claim 11,
The control information includes:
Wherein the UE is provided in the user plane entity or the PDCP entity. delete A base station for processing data,
A control unit configuring a user plane entity for transmitting data to a terminal through a WLAN carrier;
A transmitter for transmitting user plane data to the terminal through the user plane entity; And
And a receiver for receiving control information indicating whether or not the user plane data is successfully received through the WLAN carrier from the terminal through an interface between the terminal and the base station,
The transmitter may further comprise:
Further transmitting radio bearer configuration information including a parameter for transmitting the control information of the UE to the UE through higher layer signaling,
Wherein the parameter for transmitting the control information includes transmission method information and transmission period information of the control information,
The control information includes:
Wherein the transmission is triggered based on at least one of a polling of the base station, a period set by the base station, and a timer. 17. The method of claim 16,
The user plane entity includes:
Wherein the base station is configured in a lower layer of the PDCP layer. 17. The method of claim 16,
The parameter for transmitting the control information includes:
Wherein the base station further comprises information for directing transmission of the control information. 17. The method of claim 16,
The control information includes:
Wherein the base station is provided in the user plane entity or the PDCP entity of the UE. delete

Images