KR20180103717A - Methods for transmitting a buffer status report and Apparatuses thereof - Google Patents

Abstract

The present disclosure relates to a technology for redundantly transmitting data by allowing a terminal to configure a carrier aggregation with one base station in a next generation mobile communication network (NR) and transmitting a buffer state report as a result thereof. According to an embodiment, provided are a method and an apparatus, in a method for transmitting a buffer state report by a terminal configuring carrier aggregation, wherein the method comprises the steps of: receiving higher layer signaling including information for configuring data duplication transmission through carrier aggregation from a base station; configuring a plurality of radio link control (RLC) entities including first and second RLC entities linked to one packet data convergence protocol (PDCP) entity on the basis of the higher layer signaling, and configuring logical channels linked to the first and second RLC entities in one medium access control (MAC) entity; and transmitting a buffer state report configured by setting a PDCP data volume to be included in all logical channel groups linked to the first and second RLC entities when the data duplication transmission is activated.

Description

FIELD OF THE INVENTION The present invention relates to a method for transmitting a buffer status report,

The present disclosure relates to a technology for a UE to construct a carrier merging with a single base station in a next generation mobile communication network (NR) to transmit data redundantly and transmit a buffer status report accordingly.

More particularly, the present invention relates to a configuration method and apparatus for redundantly transmitting user plane or control plane data in a single base station based carrier merging state, and more particularly to a method and apparatus for transmitting a buffer status report in a single base station based carrier merging state .

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), LTE-Advanced, and 5G of the current 3GPP series, a high-speed and large-capacity communication system capable of transmitting and receiving various data such as video data and wireless data is required beyond a voice- have.

To this end, technologies for next generation wireless access networks for accommodating data transmission and reception of more terminals and providing higher QoS are being developed after LTE-Advanced. For example, a development work for a tentative 5G network centering on 3GPP is under way.

Meanwhile, the base station can improve the data transmission / reception speed and capacity of the terminal by using a plurality of cells constituted (provided) by the base station. For example, a base station and a terminal can satisfy a requirement of a user by configuring a carrier merging using a plurality of carriers.

In particular, to reliably deliver services such as Ultra-Reliable and Low-Latency Communications (URLLC) with low latency, a more reliable and reliable method that does not suffer from data loss and speed is required. To do so, there is a need for a technique for ensuring reliability by redundantly transmitting data using a plurality of cells.

However, at present, no specific method and related technique for the terminal to transmit data redundantly through one radio bearer have been developed, and accordingly, a method of transmitting the buffer status report has not been disclosed. Therefore, it is difficult to satisfy the URLLC service requirement, which is one of the core requirements of 5G mobile communication technology.

The present embodiment is intended to provide a configuration and a processing technique for a terminal and a base station to construct a carrier merging using a plurality of cells and to transmit and receive data redundantly through a plurality of carriers-merged cells.

In addition, the present embodiment intends to provide a concrete technique for transmitting a buffer status report by a UE having a redundant transmission configuration.

In order to solve the above-described problems, one embodiment of the present invention is directed to a method of transmitting a buffer status report by a terminal constituting a carrier merging, comprising the steps of: receiving upper layer signaling including information for configuring redundant data transmission through carrier merging from a base station; A plurality of RLC entities including a first RLC entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity based on higher layer signaling, Configuring a logical channel associated with a first RLC entity and a logical channel associated with a second RLC entity in a Medium Access Control (MAC) entity, and, when data redundancy transmission is enabled, The buffer status report configured to be included in both the logical channel group and the logical channel group associated with the second RLC entity is transmitted to the base station It provides a method comprising the step of transmitting.

According to another aspect of the present invention, there is provided a method of receiving a buffer status report by a base station constituting a carrier merging in a terminal, comprising the steps of: generating information for configuring redundant data transmission through carrier merging; And a logical channel group associated with a first RLC entity of the UE and a logical channel group associated with a second RLC entity of the UE when the data redundancy transmission of the UE is activated, And receiving a buffer status report including a PDCP data volume of the UE set to be included in all of the groups.

In an exemplary embodiment of the present invention, a terminal for transmitting a buffer status report constituting a merge of carriers includes a receiver for receiving an upper layer signaling including information for configuring data redundancy transmission through carrier merging from a base station, A plurality of RLC entities including a first RLC entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity are configured, and a plurality of RLC entities including one RLC entity 1 RLC entity and a logical channel associated with the second RLC entity, and a control section for configuring the PDCP data volume to a logical channel group associated with the first RLC entity and a logical channel group associated with the first RLC entity, And transmits the buffer status report configured to be included in all the logical channel groups to be connected to the base station Device.

According to an embodiment of the present invention, there is provided a base station for receiving a buffer status report by configuring a carrier merging in a terminal, the base station comprising: a controller for generating information for configuring data redundancy transmission through carrier merging; And a logical channel group associated with a first RLC entity of the UE and a logical channel group associated with a second RLC entity of the UE, And a receiving unit receiving the buffer status report including the PDCP data volume of the UE set to be included in the buffer status report.

The present embodiment described above provides a concrete method of dividing data to be transmitted and received by logical channels and providing an effect that a terminal and a base station can quickly and accurately transmit and receive data for providing a low-delay high-reliability service Effect.

In addition, the present embodiment provides an effect that a terminal having a redundant transmission can transmit an accurate buffer status report to a base station.

1 is a diagram showing an example of a layer 2 structure for a new radio access technology (New RAT).
2 is a diagram for explaining a terminal operation according to an embodiment.
3 is a diagram for explaining a base station operation according to an embodiment.
4 is a view for explaining a base station operation according to another embodiment.
5 is a diagram exemplarily showing a split bearer structure through a master cell group in a multi-connectivity between different types of base stations.
6 is a diagram illustrating an example of a structure for carrier merging-based data redundancy transmission.
7 is a diagram showing another example of a structure for carrier merging-based data redundancy transmission.
8 is a diagram illustrating another example of a structure for carrier merging-based data redundancy transmission.
9 is a diagram illustrating an example of RLC configuration information according to an embodiment.
10 is a diagram illustrating another example of RLC configuration information according to an embodiment.
11 is a diagram illustrating another example of RLC configuration information according to an embodiment.
12 is a diagram illustrating another example of RLC configuration information according to an embodiment.
13 is a diagram illustrating another example of RLC configuration information according to an embodiment.
Figure 14 is a diagram illustrating a Short BSR and Truncated BSR format according to the prior art.
15 is a diagram illustrating a Long BSR format according to the prior art.
16 is a diagram illustrating an example of radio bearer configuration information according to an embodiment.
17 is a diagram illustrating an example of cell group configuration information according to an embodiment.
18 is a diagram illustrating a terminal configuration according to an embodiment.
19 is a diagram illustrating a base station configuration according to an embodiment.

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 CDMA (Code Division Multiple Access), TDMA (Time Division Multiple Access), FDMA (Frequency Division Multiple Access), OFDMA (Orthogonal Frequency Division Multiple Access), OFDM-FDMA, OFDM- . An embodiment of the present invention can be applied to asynchronous wireless communication that evolves into LTE and LTE-advanced via GSM, WCDMA, and HSPA, and synchronous wireless communication that evolves into CDMA, CDMA-2000, and UMB. The present invention should not be construed as limited to or limited to a specific wireless communication field and should be construed as including all technical fields to which the idea of the present invention can be applied.

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

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

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

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

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

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

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

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

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

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

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

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

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

Enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliable and Low Latency Communication (URLLC) have been proposed as typical usage scenarios in NR (New Radio), which is under discussion in 3GPP.

In this specification, a frequency, a frame, a subframe, a resource, a resource block, a region, a band, a subband, a control channel, a data channel, a synchronization signal, various reference signals, various signals, May be interpreted as past or presently used meanings or various meanings used in the future.

For example, LTE and NR in this specification refer to different radio access technologies, and a new radio access technology under discussion in Release-15 of 3GPP will be described as NR. NR may include various differences such as LTE, frame structure, channel, and core network technology, and various functions for wireless transmission, high-speed, and large-capacity data transmission in the high band can be added.

Hereinafter, for convenience of description, the conventional wireless access technology will be described as LTE and the new wireless access technology discussed in 3GPP will be described as NR. Also, the base station may be an eNB using LTE technology, a gNB using NR technology, and separately described according to need.

The term " cell " used herein refers to a wireless path for transmitting data, a wireless link, a carrier, and the like, and one base station can transmit and receive data through a plurality of cells. Alternatively, a terminal can transmit and receive data using a plurality of cells through cells controlled by two base stations. As described below, carrier merging is described when one base station controls a plurality of cells, and dual connectivity is described when a plurality of cells controlled by two or more base stations are used.

LTE Dual Connectivity operation

Conventional LTE technology supports a dual connectivity technology in which a terminal simultaneously uses two base station radio resources. For multiple RX / TX terminals in the RRC Connected state, the dual connectivity operation is configured to connect to two base stations connected via a non-ideal backhaul and utilize the radio resources provided by two different schedulers located at each base station.

In the case of dual connectivity, a UE can transmit and receive data through a plurality of cells provided by two or more base stations, a main base station is described as a MeNB (master eNB), a base station for providing additional cells is called a SeNB (Secondary eNB) Will be described.

An SeNB addition procedure is used to set the terminal context to the SeNB in order to provide the terminal with radio resources from the SeNB.

NR (New Radio)

In 3GPP, research is underway on next generation / 5G wireless access technology (hereinafter referred to as NR for convenience of explanation). NR provides a new AS sublayer on top of the PDCP to provide flow-based QoS.

1 is a diagram showing an example of a layer 2 structure for a new radio access technology (New RAT).

As shown in FIG. 1, the main services and functions of the new AS sublayer are as follows.

- Mapping between a QoS flow and a data radio bearer;

- Marking QoS flow ID in both DL and UL packets.

In addition, a new user plane protocol layer can be applied to the connection to the next generation core. A single protocol entity of the new user plane protocol layer can be configured for each individual PDU session (the new user plane protocol layer is applicable to the NextGen Core. A single protocol entity of the new user plane protocol layer is configured for each individual PDU session.).

As a requirement for architecture and migration for next-generation wireless access technologies, the RAN architecture needs to support tight interworking between NR and LTE. LTE dual connectivity technology is expected to be recycled for tight interworking between NR and LTE. Also, dual connectivity techniques can be used between NR base stations in NRs. Dual connectivity in an NR environment can be defined as multi-connectivity. For example, the multi-connectivity may be defined as a mode of operation of a terminal for utilizing radio resources configured by an LTE base station and / or a NR base station. (Multi-Connectivity: Multiple Rx / Tx UE in the connected mode is configured to utilize radio resources amongst E-UTRA and / or NR provided by multipledistinct schedulers connected via non-ideal backhaul.

On the other hand, NR can be constructed even at high frequencies (for example, a high frequency of 6 GHz or more). In this case, fast SINR drops may occur depending on the link blocking factor in the high frequency band and high transmission loss. This may lead to unnecessary delays or reduce reliability if the NR base station wishes to send control plane RRC messages or user plane data via the NR and the inter-terminal interface. In particular, this problem makes it difficult to provide services such as URLLC.

As an example to solve this problem, a control plane RRC message may be transmitted over one or more radio paths in order to provide RRC diversity. As another example for solving such a problem, user plane data may be redundantly transmitted over one or more wireless paths based on a multi-connectivity.

Single base station based redundant transmission

In order to increase the data transmission rate and transmission rate, a new radio access technology also needs to provide Carrier Aggregation (CA). For example, a terminal may transmit data through a plurality of cells based on a CA by a single base station. Hereinafter, the description will be made in terms of a cell, but a wireless path, a wireless link, a carrier, etc. may be used in combination if necessary. As used herein, the term " wireless path, " " wireless link, carrier, or cell " refers to a data path provided by a base station for data transmission / reception with a terminal.

In providing a CA by a single base station, a terminal may perform redundant transmission through one or more cells. For example, the control plane RRC message may be transmitted over one or more cells. As another example, the user plane data may be transmitted redundantly through one or more cells. However, the procedures and technical contents related to the redundant transmission using the carrier merging have not been disclosed.

As described above, redundant transmission over two or more radio paths can be considered as a method for reliably providing a service such as a URLLC in a radio access network with low delay. However, when a CA is configured in a terminal based on a single base station, it has not been possible to support redundant transmission over two radio paths through a CA.

Further, when a CA is configured in a terminal based on a single base station, a specific procedure and method for transmitting the buffer status report to the base station have not been disclosed.

In order to solve such a problem, the present disclosure aims at providing a method and apparatus for redundant transmission of a terminal and a base station so as to efficiently process a service such as a URLLC when a single base station based CA is applied. It is another object of the present invention to provide a method for effectively controlling a CA-based multiple transmission cell.

It is another object of the present invention to provide a detailed description of a buffer status reporting method when a CA is configured in a terminal based on a single base station.

The present disclosure may be applied to any wireless access (e.g., LTE) network and terminals as well as next generation mobile communication (5G mobile communication / NR) terminals.

For convenience of explanation, the base station may represent an eNodeB or an LTE base station of an LTE / E-UTRAN or an NR Node, a CU, a DU, or a Node B in a 5G wireless network in which a CU (Central Unit) CU and DU can represent gNodeB, NR base stations implemented as a single logical entity. Hereinafter, the NR base station is referred to as the NR base station for convenience of explanation, but all the above-mentioned objects can be included in the scope of the present invention.

In NR-LTE, the following scenarios can be considered:

- When one or more NR cells and one or more LTE cells are provided through an LTE base station and apply a CA.

- one or more NR cells and one or more LTE cells are provided to the NR base station to apply the CA.

- one or more NR cells are provided to the NR base station to apply the CA.

- One or more LTE cells are provided to an LTE base station to apply a CA.

For convenience of description, the case where the NR base station applies CA through one or more NR cells will be described. This is for convenience of explanation, and other scenarios described above are also included in the scope of the present embodiment. In this case, the LTE base station and the NR base station provide at least one LTE cell and at least one NR cell, respectively, and apply dual connectivity to the terminal while applying the CA, as an embodiment of the present disclosure. For example, LTE-NR dual connectivity where the LTE base station becomes the master base station and the NR base station becomes the secondary base station, the NR-LTE dual connectivity where the NR base station becomes the master base station and the LTE base station becomes the secondary base station becomes the master base station A case where another NR base station provides a redundant transmission by applying a CA to a corresponding NR-NR dual connectivity as a secondary base station may also be included in the embodiment of the present disclosure. That is, in the case where a plurality of base stations or a plurality of NR base stations using different radio access technologies form dual connectivity, and a single base station also forms a carrier merging, the embodiment in this specification can be applied.

The NR base station can control NR radio resources of the UE. NR base station adds / modifies / releases / manages NR cell / cell group / transmission point / transmission point group / transmission / reception point / transmission / reception point group / TRP / antenna / antenna group / beam (hereinafter, NR radio resource allocation, NR radio resource allocation, NR radio bearer addition / correction / release, NR radio resource configuration, and NR mobility control. The NR base station may indicate one or more of the control functions described above for the terminal via an RRC configuration or reconfiguration message.

The NR base station can configure the CA through one or more NR cells in the UE.

The NR base station can perform data redundancy transmission to the CA using the PDCP redundancy transmission function.

The PDCP entity of the base station copies PDCP PDUs (or PDCP SDUs) having the same SN (sequence number) to duplicate or submit the PDCP PDUs (or PDCP SDUs) having the same SN to the lower layer to duplicate data through one or more wireless cells.

The PDCP entity of the UE receives PDCP PDUs (or PDCP SDUs) received via one or more radio cells. For example, the PDCP entity may first process the received data and discard the duplicated data. For another example, the function of detecting and discarding duplicated data can be performed by the PDCP entity. For example, the transmitting side may transmit data having the same PDCP SN through two paths, and the receiving side may detect (or detect) redundant data based on the PDCP SN. The base station can indicate to the terminal the configuration information for indicating / processing such an operation.

For uplink transmission, the PDCP entity of the UE copies / duplicates PDCP PDUs (or PDCP SDUs) having the same SN to the lower layer so as to transmit data redundantly through one or more wireless cells.

The PDCP entity of the base station receives PDCP PDUs (or PDCP SDUs) received via one or more radio cells. For example, the PDCP entity may first process the received data and discard the duplicated data. For another example, the function of detecting and discarding duplicated data can be performed by the PDCP entity. For example, the transmitting side may transmit data having the same PDCP SN through two paths, and the receiving side may detect (or detect) redundant data based on the PDCP SN. The base station can indicate to the terminal the configuration information for indicating / processing such an operation.

In the case of user plane data, redundant data transmission can be handled in the PDCP layer connected through the new AS sublayer. On the other hand, the RRC message may or may not pass through the new AS sublayer.

For example, in the case of an RRC message, the redundant data transmission in the PDCP can be handled through the new AS sublayer. In another example, in the case of an RRC message, a redundant data transfer can be handled by directly connecting to the PDCP without a new AS sublayer.

Hereinafter, an operation of the terminal and the base station configuring a single base station-based CA to configure the redundant transmission and the operation of processing the buffer status report in this case will be described. The operation of the terminal and the base station described with reference to FIG. 2 to FIG. 4 will be described with reference to an embodiment of the present disclosure, and detailed configurations of the terminal and the base station will be described in detail later.

2 is a diagram for explaining a terminal operation according to an embodiment.

Referring to FIG. 2, the UE may perform a step of receiving upper layer signaling including information for configuring data redundancy transmission through merging of carriers from a base station (S210).

For example, a terminal may receive an RRC message comprising additional RLC configuration information for configuring a carrier merging with one base station and using carrier merging to duplicate the same data over a plurality of carriers to the base station.

For example, the information for configuring the redundant transmission includes information on a plurality of RLC entities configured in the UE, logical channel information associated with each RLC entity, information on each RLC entity and one PDCP Information for association of objects, and MAC entity configuration information for redundant transmission.

In addition, the UE configures a plurality of RLC entities including a first RLC entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity based on upper layer signaling, A logical channel associated with a first RLC entity and a logical channel associated with a second RLC entity may be configured in a Medium Access Control (MAC) entity at step S220.

For example, the UE may configure an additional RLC entity in the UE based on the information for configuring the received redundancy transmission. A plurality of RLC entities may be configured according to the configuration of the base station, but two RLC entities will be described herein for convenience of explanation. However, the present invention is not limited thereto. The UE may configure the first RLC entity and the second RLC entity in association with one PDCP entity according to the higher layer signaling. In addition, the UE may configure a logical channel in association with an RLC entity to identify RLC entities added to one MAC entity. That is, the UE may configure the MAC entity with a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity. In this way, the MAC entity maps the data transmitted and received through one radio bearer to each logical channel and processes the PDCP data by duplicating the PDCP data to the BS through the plurality of RLC entities, and transmits the redundantly received data to the PDCP entity It can also be delivered over each logical channel.

For example, one MAC entity may transmit data, which is transmitted through a logical channel associated with a first RLC entity and a logical channel associated with a second RLC entity, to different base stations via different carriers.

In another example, the first RLC entity and the second RLC entity may be configured in association with different logical channels based on logical channel identifiers.

As another example, the first RLC entity and the second RLC entity may be configured in association with the one PDCP entity based on a radio bearer identifier.

If the data redundancy transmission is activated, the UE sets up the PDCP data volume to be included in both the logical channel group associated with the first RLC entity and the logical channel group associated with the second RLC entity, and transmits the buffer status report to the base station (S230). ≪ / RTI >

For example, the UE can transmit a buffer status report to the BS according to a buffer status report trigger condition when a redundant transmission configuration such as a plurality of RLC entities is completed and a data redundancy transmission function is activated. However, even if the terminal is configured for redundant transmission, the redundant transmission function may not be activated depending on the setting. In this case, the activation of the data redundancy transmission may be indicated through a separate signal from the base station. For example, a signal for activation of a redundant transmission may be directed from a base station via a MAC control element for each data radio bearer. That is, the BS can activate or deactivate the redundancy transmission function configured for the UE through the MAC control element for each radio bearer.

As described above, when a buffer status report is triggered when redundant transmission is configured in the terminal and the redundant transmission function is activated, the terminal transmits a buffer status report to the base station. However, in this case, it is important to transmit the PDCP data volume to the base station by transmitting data to the base station through redundant transmission.

For example, the UE can set the PDCP data volume to be included in both the logical channel group associated with the first RLC entity and the logical channel group associated with the second RLC entity. In addition, the UE can set the PDCP data volume of the logical channel associated with the second RLC entity (the RLC entity additionally configured for the redundant transmission) to include and remove the PDCP control PDU, The PDCP data volume may be set to include a PDCP control PDU. In this case, the terminal can transmit a buffer status report including buffer information of each logical channel group to the base station. That is, the PDCP data volume can be set to be included in all the logical channel groups associated with each RLC entity.

In addition, the terminal may perform all the operations of the embodiments described below, and some of the steps may be changed, omitted, or added as necessary.

3 is a diagram for explaining a base station operation according to an embodiment.

Referring to FIG. 3, the base station may perform a step of generating information for configuring data redundancy transmission through merging of carriers (S310). For example, the information for configuring the redundant transmission includes information on a plurality of RLC entities configured in the UE, logical channel information associated with each RLC entity, information on each RLC entity and one PDCP Information for association of objects, and MAC entity configuration information for redundant transmission.

The base station may perform a step of transmitting upper layer signaling including information for configuring data redundancy transmission through merging carriers to the terminal (S320).

The base station can transmit information for configuring a single base station based redundant transmission of the above-described terminal through higher layer signaling such as an RRC message.

The UE constructs a plurality of RLC entities including a first RLC entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity by receiving information for configuring redundant transmission, A logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity may be configured in one Medium Access Control (MAC) entity.

For example, the UE may configure an additional RLC entity in the UE based on the information for configuring the received redundancy transmission. A plurality of additional RLC entities may be configured according to the configuration of the base station. In addition, the first RLC entity and the second RLC entity may be configured to be linked to one PDCP entity. In addition, the UE may configure a logical channel in association with an RLC entity to identify RLC entities added to one MAC entity. That is, the UE may configure the MAC entity with a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity. In addition, the first RLC entity and the second RLC entity may be configured in association with different logical channels based on logical channel identifiers. Alternatively, the UE may be configured such that the first RLC entity and the second RLC entity are associated with one PDCP entity based on a radio bearer identifier.

Thereafter, when the data redundancy transmission of the MS is activated, the BS can repeatedly receive the data transmitted in association with each logical channel of the MS through different carriers. That is, the same data can be received redundantly. Here, the different carriers may be the carriers constituting the CA of the terminal.

When the data redundancy transmission of the UE is activated, the BS stores the PDCP data volume of the UE set to be included in both the logical channel group associated with the first RLC entity of the UE and the logical channel group associated with the second RLC entity of the UE A step of receiving a status report may be performed (S330).

When the UE has a redundant transmission configuration similar to that of a plurality of RLC entities and the data redundancy transmission function is activated, the UE transmits the buffer status report to the BS according to the buffer status report trigger condition, and the BS can receive the report.

The buffer status report may include a PDCP data volume for each logical channel group. To do so, the terminal may assign a PDCP data volume to both logical channel groups associated with the first RLC entity and logical channel groups associated with the second RLC entity To the base station. That is, the PDCP data volume may be received in all logical channel groups associated with each RLC entity. At this time, the PDCP data volume of the logical channel associated with the second RLC entity may be removed from the PDCP control PDU and the included value may be received. In addition, a PDCP data volume of a logical channel associated with the first RLC entity may receive a value including a PDCP control PDU. That is, the PDCP control PDU included in the PDCP data volume may be included only in the logical channel (logical channel group) associated with the first RLC entity. Therefore, the PDCP control PDU can be indicated as a MAC entity in a state not included in the PDCP data volume of the logical channel or logical channel group associated with the RLC entity configured for redundant transmission.

In addition, the base station can perform all of the operations of each embodiment described below, and some steps may be changed, omitted, and added as necessary.

4 is a view for explaining a base station operation according to another embodiment.

Referring to FIG. 4, before receiving a buffer status report, the BS performs a step of transmitting information indicating that data redundancy transmission of a UE is activated through a MAC Control Element (MAC Control Element) for each data radio bearer (S410). That is, the activation of the data redundancy transmission can be indicated through a separate signal from the base station. For example, a signal for activation of a redundant transmission may be directed to a terminal through a MAC control element for each data radio bearer. That is, the base station can activate or deactivate the redundancy transmission function configured for the UE through the MAC Control Element (MAC Control Element) for each radio bearer.

If the UE is configured to be in an active state when a redundant transmission is configured, the BS may not transmit a MAC control element for activating the redundant transmission.

Through the operations described above, the UE and the BS can configure a redundant transmission over a single base station-based CA and process the buffer status report. Hereinafter, various embodiments in which a terminal and a base station configure redundant transmission will be described, and various embodiments for processing a buffer status report thereafter will be described.

First, an embodiment of a redundant transmission configuration will be described, and each of the embodiments described below may be applied independently, or all or some of the embodiments may be applied mutually in combination. All cases are included in the embodiments of the present disclosure. In the following description, uplink redundant transmission is mainly described, but the same or similar can be applied to the case of downlink redundant transmission.

1. MAC entity (MAC entity)

1) Embodiment using two MAC entities

5 is a diagram exemplarily showing a split bearer structure through a master cell group in a multi-connectivity between different types of base stations.

Referring to FIG. 5, when data is redundantly transmitted through one or more cells between a single base station and a terminal based on a CA, a dual / multi-connectivity based split bearer structure can be reused and used. For example, if the master base station is the NR base station 501 and the secondary base station is the LTE base station 502, the terminal can configure a dual connectivity-based split bearer structure. That is, the UE can transmit and receive data through the two radio resources through the bearer through the NR base station 501 and the split bearer branched from the PDCP entity of the NR base station 501 and linked to the RLC entity of the LTE base station 502 have.

In a single base station-based CA, a redundant transmission can be made in a structure similar to that of the split bearer as shown in FIG.

6 is a diagram illustrating an example of a structure for carrier merging-based data redundancy transmission. 7 is a diagram showing another example of a structure for carrier merging-based data redundancy transmission.

Referring to FIGS. 6 and 7, the terminals 601 and 701 may be configured to transmit data redundantly through one or more carriers provided according to the CA by using two MAC entities in the terminals 601 and 701. FIG. In order to perform data redundancy transmission through two MAC entities in the UE, the BS transmits a MAC entity for redundant transmission (referred to as a second MAC entity for convenience of description) MAC entities, and MAC entities added for redundant transmissions on a single base station basis are referred to as second MAC entities).

For example, the UEs 601 and 701 generate a second MAC entity upon receiving an RRC (reconfiguration) message including configuration information indicating a CA-based redundancy transmission for a single base station 602 and 702. Unlike the SCG MAC entity configured by the master base station and the independent base station (secondary base station) on the basis of the dual connectivity, the second MAC entity configured by a single base station can efficiently transmit detailed configuration information on two MAC entities Can be set.

For example, the first MAC entity and the second MAC entity may independently perform some or all of the MAC procedures. Because the second MAC entity is used for reliable redundancy rather than efficiency, the second MAC entity may perform procedures independent of the first MAC entity for some or all of the MAC procedure. Such a MAC procedure may be one or more of a buffer state report (BSR), a scheduling request (SR), a logical channel prioritization (LCP), and a power headroom report (PHR).

As another example, the first MAC entity and the second MAC entity may perform MAC procedures through coordination. The second MAC entity is used for reliable redundant transmission rather than efficiency, but it may be efficient for some MAC procedures to coordinate themselves. Such a MAC procedure may be one or more of BSR, SR, LCP, PHR and DRX procedures.

As another example, the first MAC entity may provide all or most of the procedures generated in the two MAC entities, and the second MAC entity may perform only some limited functions. For example, a function of associating data transmitted / received from a second RLC entity belonging to one radio bearer with a logical channel, a routing function associated therewith, or a function of adding / removing information for distinguishing it on a data header May be performed in the second MAC entity.

Each MAC entity can distinguish between logical channels associated with each RLC entity belonging to one radio bearer. Or each MAC entity may comprise one or more carriers.

When the redundant transmission function is configured, at least one of the carriers (or cells) included in each MAC entity must be activated to enable redundant transmission.

For example, a BS may configure one or more cells configured in a second MAC entity to be in an activated state when configuring a redundant transmission function.

As another example for providing this, when the BS configures the redundant transmission function, the BS may define one or more cells configured in the second MAC entity as a special cell different from the general SCell. However, this particular cell may not need to provide a function for transmitting the PUCCH.

As another example of this, when the base station configures the redundant transmission function, the specific cell configured in the second MAC entity can always be configured to be in an activated state.

As another example of this, when the base station configures the redundant transmission function, the cell configured in the second MAC entity is configured to be in an inactive state. The base station may activate one or more of the cells (or specific cells) configured in the second MAC entity to activate the redundant transmission function. The cell can be disabled from applying the deactivation timer provided to SCell.

As another example of this, when the base station configures the redundant transmission function, the cell configured in the second MAC entity is configured to be in an inactive state. The base station can activate the redundant transmission function only when at least one of the cells configured in the second MAC entity is activated.

As another example of this, when the base station configures the redundant transmission function, the cell configured in the second MAC entity is configured to be in an inactive state. The base station can maintain (or activate) the redundant transmission function such that one or more of the cells configured in the second MAC entity are not deactivated. Or to restart the timer. Alternatively, a deactivation timer may be indicated as a specific value.

As another example of this, when the base station configures the redundant transmission function, the cell configured in the second MAC entity is configured to be in an inactive state. The base station may instruct to activate one or more of the cells configured in the second MAC entity when configuring (or activating) the redundant transmission capability. Alternatively, the terminal can activate one or more of the cells configured in the second MAC entity when configuring the redundant transmission function by the base station or activating the redundant transmission function.

As another example of this, when a base station configures a redundant transmission function, a redundant transmission activation condition can be configured as a terminal. The terminal may instruct the base station to activate at least one of the cells configured in the second MAC entity if the redundant transmission condition is satisfied.

2) Embodiment using one MAC entity

8 is a diagram illustrating another example of a structure for carrier merging-based data redundancy transmission.

Referring to FIG. 8, one MAC entity in the UE 801 may be configured to transmit data redundantly via one or more cells / carriers provided through a CA. In order to perform data redundancy transmission through one MAC entity in the UE 801, the BS 802 can include one or more RLC entities and one or more logical channels for one radio bearer, associated with one MAC entity have. A MAC entity may include one or more cells / carriers.

When the redundant transmission function is configured, each logical channel belonging to one radio bearer must be mapped (linked or linked) with one or more mutually exclusive cells / carriers. That is, redundant data must be transmitted in the PDCP through different cells / carriers. This will be described later.

When the redundant transmission function is configured, at least one of the cells / carriers associated with each logical channel belonging to one radio bearer must be activated to enable redundant transmission.

For example, when configuring the redundant transmission function, the base station may configure one or more cells among the cells / carriers associated with each logical channel belonging to one radio bearer to be in an activated state.

As another example of this, one or more cells on a cell / carrier / cell group / carrier group that does not include a PCell for a cell / carrier / cell group / carrier group associated with each logical channel belonging to one radio bearer It can be defined as a special cell distinguished from a scell.

As another example of this, when a base station configures a redundant transmission function, a certain cell (a specific secondary cell) associated with each logical channel belonging to one radio bearer can always be configured to be activated.

As another example of this, when the base station configures the redundant transmission function, it configures the secondary cell associated with each logical channel belonging to one radio bearer into a disabled state. The base station can activate one or more of the secondary cells / carriers (or specific cells) associated with each logical channel belonging to one radio bearer to activate the redundant transmission function. The cell can be disabled from applying the deactivation timer provided to SCell.

As another example of this, when the base station configures the redundant transmission function, it configures the secondary cell associated with each logical channel belonging to one radio bearer into a disabled state. The base station can enable the redundant transmission function only when at least one of the secondary cells associated with each logical channel belonging to one radio bearer is activated.

As another example of this, when the base station configures the redundant transmission function, it configures the secondary cell associated with each logical channel belonging to one radio bearer into a disabled state. The base station can keep the secondary cell associated with each logical channel belonging to one radio bearer inactive when configuring (or activating) the redundant transmission function. Or to restart the timer. Alternatively, a deactivation timer may be indicated as a specific value.

As another example of this, when the base station configures the redundant transmission function, it configures the secondary cell associated with each logical channel belonging to one radio bearer into a disabled state. The base station can instruct to activate the secondary cell associated with each logical channel belonging to one radio bearer when configuring (or activating) the redundant transmission function. Alternatively, the terminal can activate the secondary cell associated with each logical channel belonging to one radio bearer when configuring the redundant transmission function by the base station or activating the redundant transmission function.

As another example of this, when a base station configures a redundant transmission function, a redundant transmission activation condition can be configured as a terminal. When the condition for duplicate transmission is satisfied, the MS transmits information for activating at least one secondary cell associated with each logical channel belonging to one radio bearer (for example, a secondary cell associated with a cell group not including PCell) .

3) Example of logical channel to cell mapping

Hereinafter, a mapping between logical channels and cells (carriers) will be described. A logical channel and inter-cell mapping can be provided for the above cases.

A traffic transmission (or routing) restriction may be configured for each logical channel for one or more logical channels belonging to one SRB or DRB. The logical channel configuration may indicate whether traffic for one logical channel can be transmitted in certain cells.

For example, this may be configured for each serving cell. As another example, this can be configured for each logical channel.

For example, PCell may be configured in the first MAC entity described above. SCell may be included in either the first MAC entity or the second MAC entity. The base station may include information for indicating this in the SCell configuration information.

In another example, a cell configured in the first MAC entity may be configured to transmit traffic only to a logical channel / logical channel group configured in the first MAC entity. The cell configured in the second MAC entity can be configured to transmit traffic only to the logical channel / logical channel group configured in the second MAC entity. Joint processing of the uplink grant in one TTI is allowed only when the uplink grant in each MAC entity serves the same logical channel. For an uplink grant for a cell belonging to a first MAC entity, the terminal performs LCP on the logical channels associated with the first MAC entity. For an uplink grant for a cell belonging to a second MAC entity, the terminal performs LCP on the logical channels associated with the second MAC entity.

For example, the base station refers to a second cell or a second cell group for convenience of description, that is, a general cell (PCell or SCell) based on a single base station is referred to as a first cell or a second cell One cell group, and the SCell added for redundant transmission on a single base station basis is referred to as a second cell or a second cell group). For each logical channel belonging to one radio bearer, the base station refers to a basic logical channel (referred to as a first logical channel for convenience of explanation, i.e., a MAC entity for one radio bearer The logical channel added to the radio bearer is referred to as a secondary logical channel) to the second logical channel added to the first logical channel Can be configured to instruct to transmit through the second cell or the second cell group described above.

For example, the base station may include at least one of cell identification information (PCI, ServingCellindex, and SCellindex) of the second cell for redundant transmission or a cell identification information list of the second logical Channel traffic information may be included in the logical channel configuration information as a sequence or a bitmap. If the ServingCellindex / SCellindex is less than or equal to 7, For example, when ServingCellindex / SCellindex is configured as a second cell and a third cell is configured as a second cell / second cell group, a '00110000' cell may be configured as a cell / second cell group. May be included in the logical channel configuration information for the second logical channel. The logical channel may be configured to be transmitted only through the cell set to 1 in the corresponding bitmap There can be, for example, assuming a ServingCellindex of PCell to zero bits with SCellindex 2 times of the bit having the third-bit, 3 SCellindex may be available for the fourth bit.

If the second cell / second cell group is composed of SCell having ServingCellindex / SCellindex of 15 or less, a bitmap composed of 16 bits can be constructed. For example, when ServingCellindex / SCellindex configures a second cell and a third cell is a second cell / second cell group, a bitmap indicated as '0011000000000000' may be included in the logical channel configuration information for the second logical channel . The logical channel can be configured to be transmitted only through the cell set in the corresponding bitmap to 1. If the SCell with ServingCellindex / SCellindex less than or equal to 31 constitutes the second cell / second cell group, a 32-bit composed bitmap Can be configured. For example, when ServingCellindex / SCellindex configures the second, third, and eighth cells as the second cell / second cell group, the bitmap indicated as '00110000000000000000000000000000' is included in the logical channel configuration information for the second logical channel can do. The logical channel can be configured to be transmitted only through the cell set to 1 in the corresponding bitmap.

For the uplink grant for the first cell or the first cell group, the terminal performs the LCP only for the logical channel transmitted to the first cell or the first cell group.

For the uplink grant for the second cell or the second cell group, the terminal performs the LCP only for the logical channel transmitted to the second cell or the second cell group.

For another example, it is possible to indicate, for one or more logical channels belonging to one SRB or DRB, whether or not transmission is possible in a particular cell for each logical channel. For example, the first logical channel may be instructed to be transmitted only via PCell, and the second logical channel may be directed to transmit (or not allow transmission via PCell) over the remaining cell / cell group. Another example is to allow the first logical channel to transmit through a particular cell group including the PCell and the second logical channel to transmit through the remaining cell / cell group (or to allow transmission over a particular cell group including PCell) You can tell.

For another example, it may be instructed to transmit only through a specific SCell / cell group.

The two logical channels belonging to the redundant transmission bearer may have a cell identifier or a cell identifier list for each logical channel. The cell identifier or cell identifier group for each logical channel may be configured so that they do not overlap with each other. A cell identifier or a cell identifier group for each logical channel may be configured mutually exclusive.

When the redundant transmission function is configured, the PDCP data belonging to one radio bearer may be transmitted to the associated cell / carrier separated by each logical channel through one or more RLC entities.

As an example, a cell group / carrier group (or a second cell group) for the redundant transmission can be defined. And / or a logical channel group (or a second logical channel group) mapped to this cell group may be defined. The logical channel identification information in each logical channel group can be configured independently of each other. Or one value from 3 to 8 for DRB within each logical channel group. RLC entities associated with this cell group or logical channel group can be identified and configured.

As another example, a logical channel group (or a second logical channel group) mapped to a cell / cell group using a cell group / carrier group (or a cell group other than a second cell group or a specific cell or a specific cell) Or logical channel group (or second logical channel group) list may be defined. The logical channel group list included in the cell group / carrier group configuration information may be included as a sequence or bitmap. For example, the cell group / carrier group configuration information may include, in order, each logical channel configuration information having each logical channel identifier included in the second logical channel group. The cell group / carrier group configuration information may include information for indicating the second cell / second cell group. As an example, this may be provided via a cell group identifier. As another example, this may be indicated via an identifier value different from the MCG cell group identifier value. The logical channel identification information in each logical channel group can be configured independently of each other. Or a value of 3 to 8 or 4 to 31 for the DRB in each logical channel group. (Logical channel identification information) for one RLC entity (second RLC entity) configuration information and one logical channel (second logical channel) for one radio bearer for this logical channel group. Which may be mapped via radio bearer identification information

2. RLC entity (RLC entity)

1) Additional RLC entity configuration example for redundant transmission

The base station is indicated by an additional RLC entity for redundant transmission (hereinafter referred to as a second RLC entity for redundant transmission for convenience of explanation), this is for convenience of description and the use of other terminology is also included in the scope of the present disclosure For example, any name such as a secondary RLC entity (secondary RLC entity) distinguished from a primary RLC entity configured for one bearer may be used in the UE.

A base station can configure a CA for a single connection with one base station. Accordingly, the terminal can transmit and receive data to and from a single base station through a plurality of radio paths. The base station can instruct configuration information for the terminal to the terminal. For example, the BS may configure one or more RLC entities that are mapped to one data radio bearer (DRB) in the MS. This may be an RLC entity that is distinct from the SCG RLC entity provided for the split bearer in conventional dual connectivity. That is, it may be an RLC entity included in the DRB configuration information (DRB-ToAddModd) which is distinguished from the RLC entity included in the DRB configuration information (DRB-ToAddModSCG) added for the SCG (or added for the MCG). Or it may be an RLC entity included in the cell group configuration information (CellGroupConfig) added for the MCG to be distinguished from the RLC entity included in the cell group configuration information (CellGroupConfig) added for the SCG.

9 is a diagram illustrating an example of RLC configuration information according to an embodiment.

As shown in FIG. 9, the RLC configuration information may include at least one of an RLC entity for redundant transmission, a logical channel identifier for redundant transmission, and logical channel configuration information for redundant transmission for one SRB or DRB. Accordingly, the UE can configure the second RLC entity for the redundant transmission in conjunction with the logical channel for the redundant transmission.

10 is a diagram illustrating another example of RLC configuration information according to an embodiment.

As shown in FIG. 10, the RLC configuration information includes radio bearer identification information for redundant transmission for one SRB or DRB, RLC entity for redundant transmission, logical channel identifier for redundant transmission, and logical channel configuration information for redundant transmission The above information may be included. Accordingly, the UE can configure the second RLC entity for the redundant transmission in conjunction with the logical channel for the redundant transmission. And may be configured to associate with the first RLC entity and the second RLC entity for the corresponding radio bearer in the PDCP entity.

11 is a diagram illustrating another example of RLC configuration information according to an embodiment.

As shown in FIG. 11, the radio bearer configuration information for one SRB or DRB may include at least one of RLC configuration information used for redundant transmission and logical channel configuration information used for redundant transmission. In order to associate a plurality of entities with one radio bearer, the RLC configuration information may be listed in a SEQUENCE format. The RLC configuration information may include information for identifying each RLC entity associated with one radio bearer. For example, RLC identification information. The RLC identification information can be configured to have up to two or four RLC identification information. Or information (BOOLEAN) that identifies a redundant RLC entity. When having an integer value, the smallest value (for example, 0) may be a basic RLC entity (first RLC entity). For example, the identification information of one RLC entity may be set to the same value as the logical channel identification information (logical channel identifier). As another example, mapping information / mapping rules thereof may be included for mapping the RLC entity and logical channel information. For example, RLC entities for redundant transmission can be identified through logical channel identification information of a logical channel for redundant transmission. And may be configured to associate with the first RLC entity and the second RLC entity for the corresponding radio bearer in the PDCP entity.

12 is a diagram illustrating another example of RLC configuration information according to an embodiment. 13 is a diagram illustrating another example of RLC configuration information according to an embodiment.

As shown in FIG. 12 or FIG. 13, the radio bearer configuration information for one SRB or DRB may include information for distinguishing between the RLC entity and the logical channel used for redundant transmission and mapping. For example, the RLC entity may be distinguished by logical channel identification information of a logical channel for redundant transmission to one radio bearer. And may be configured to associate with the first RLC entity and the second RLC entity for the corresponding radio bearer in the PDCP entity.

If additional RLC configuration information is configured by the base station, or if additional RLC configuration information is configured and redundant transmission is enabled, the terminal may perform redundant transmission.

The PDCP entity of the base station duplicates / submits PDCP PDUs (or PDCP SDUs) having the same SN to the lower layer to duplicate data through one or more wireless cells. The PDCP entity of the UE receives PDCP PDUs (or PDCP SDUs) received via one or more radio cells. For example, the PDCP entity may first process the received data and discard the duplicated data.

The PDCP entity of the UE copies / duplicates PDCP PDUs (or PDCP SDUs) having the same SN to the lower layer so as to transmit data redundantly through one or more wireless cells. The PDCP entity of the base station receives PDCP PDUs (or PDCP SDUs) received via one or more radio cells.

If redundant transmission is not enabled (or if it does not meet the activation condition), the PDCP entity of the base station forwards the PDCP PDUs to the first RLC entity for downlink transmission. Otherwise, the PDCP entity of the base station submits the PDCP PDUs to the first RLC entity and to the second RLC entity.

If redundant transmission is not enabled (or if it does not correspond to an activation condition), the PDCP entity of the terminal forwards the PDCP PDUs to the first RLC entity for uplink transmission. Otherwise, the PDCP entity of the base station submits the PDCP PDUs to the first RLC entity and to the second RLC entity.

For downlink reception, the terminal receives data through a plurality of carriers by PDCP redundancy based on a single base station. The MAC entity of the UE transmits it to the upper layer (RLC) based on the logical channel identification information. That is, the MAC entity of the UE transmits data to the RLC entity based on the logical channel identification information. In the prior art, since there is only one logical channel and an RLC entity of a MAC entity for one radio bearer, data can be transferred to the corresponding RLC entity based on the logical channel identification information included in the MAC header. However, if there is more than one RLC entity and more than one logical channel for one radio bearer, then it may be necessary to provide a mapping relationship between the RLC entity and the logical channel.

Accordingly, the MAC entity of the UE can transmit the corresponding data to the respective RLC entities based on the respective logical channel identification information. For this, the base station must be able to configure each RLC entity and each logical channel mapping information in the terminal. For example, this may be provided by combining one or more of the embodiments of Figs. 6 to 11 described above. As another example, this can be provided through the various embodiments described above.

For uplink transmission, the terminal transmits data through multiple carriers by PDCP redundancy on a single base station basis. The PDCP entity of the UE copies / duplicates PDCP PDUs (or PDCP SDUs) having the same SN to the lower layer so as to transmit data redundantly through one or more wireless cells. For example, the PDCP entity duplicates / submits PDCP PDUs (or PDCP SDUs) having the same SN to one or more RLC entities. This can be provided based on one PDCP entity configuration information and one or more RLC entity configuration information belonging to one radio bearer. For example, it may be mapped based on the same radio bearer identifier (e.g. DRB-identity). As another example, this may be provided by configuring one PDCP configuration information in association with one or more RLC entities. Each RLC entity delivers it to the MAC entity. For example, if one or more MAC entities are used, each RLC entity may deliver an RLC PDU to each MAC entity associated therewith.

For another example, if one MAC entity is used, it can operate as follows. For example, each RLC entity transmits a corresponding RLC PDU to a MAC entity. The MAC entity may generate the MAC PDU based on the logical channel identification information associated with the RLC entity. The RLC entity configuration information must be able to map the logical channel configuration information associated therewith. This can be provided by combining the embodiments of Figs. 9 to 13 described above or one or several of the various embodiments according to the present invention.

This can be provided by defining logical channel identification information and RLC entity identification information, mapping through it, logical channel identification information and RLC entity index, and mapping through it. Alternatively, the RLC entity index (or RLC identification information) may be provided in the same manner as the logical channel identification information. Or RLC entity in conjunction with logical channel identification information. Alternatively, if two RLC entities and two logical channels are configured, they can be provided by mapping a second RLC entity and a second logical channel to one radio bearer

On the other hand, additional radio resources are consumed by redundantly transmitting RRC signaling messages or user plane data on a plurality of radio interfaces. However, this can improve the reliability of the transmission of the control plane message or the transmission of the user plane data. Also, if the secondary base station can transmit the RRC message directly to the mobile station via the air interface, there may be an advantage that data can be transmitted quickly without delaying the backhaul interval between the base stations. As described above, the multi-path redundant transmission scheme improves the reliability but consumes radio resources due to complexity and redundant transmission.

Hereinafter, the description will be made on the basis of the redundant transmission of the RRC message. This is for convenience of explanation, and user plane data redundant transmission can be equally provided. Therefore, user plane data redundant transmission is also included in the scope of the present invention. For example, it can be handled by the PDCP entity of the individual radio bearer that processes it per control plane data or user plane data.

If it is configured to always operate redundant transmission over a plurality of paths, excess radio resources can be wasted. In order to reduce the radio resource consumption due to the redundant transmission, for example, the function (redundant transmission function) is activated / deactivated or on / off (referred to as enable / disable, on / off, activation / deactivation, etc.) can be used.

The downlink RRC data redundancy transmission enables the base station to efficiently transmit RRC data redundantly in an implementation and transmit data. The uplink RRC data redundant transmission can be performed by an instruction of the base station.

For example, when instructing the UE by setting the indication information indicating whether the RRC message duplication transmission is enabled, the UE generates the RRC message by transmitting two RRC messages from the PDCP entity, .

In another example, when the BS instructs the UE to set the indication information indicating whether the RRC message duplication transmission is enabled or disabled, the UE generates the RRC message by transmitting one RRC message from the PDCP entity It is possible to transmit it through the path.

In another example, when the base station instructs the terminal to set the information indicating whether to enable the RRC message duplication transmission to be inactivated, when generating the uplink RRC message, the terminal transmits the RRC message to the designated transmission path And the like. The transmission path for this may be pre-configured in the terminal or indicated by the base station.

If redundant transmission through multiple paths is always operated, excessive radio resources can be wasted.

The downlink RRC data redundancy transmission enables the base station to efficiently transmit RRC data redundantly in an implementation and transmit data.

On the other hand, in order for the UE to efficiently process the uplink RRC data redundancy transmission, it is necessary for the UE to control the RRC or the PDCP entity to transmit the RRC message through two paths by controlling the base station.

If duplicate transmissions are indicated via two paths, it may not be desirable to continue to perform redundant transmissions during the RRC connection. Thus, the base station can indicate a timer for multi-path redundant transmission.

For example, the base station may indicate a redundant transmission activation timer. When the UE receives the RRC message including the redundant transmission activation timer, it starts the corresponding timer. When the uplink RRC message is generated while the timer is operating, the UE may transmit the RRC message through the two transmission paths in the PDCP entity. If the RRC message is generated after the timer expires, the UE can transmit the PDCP entity through one transmission path. The transmission path for this may be pre-configured in the terminal or indicated by the base station. It may be an RLC entity configured by default for the corresponding radio bearer. As described above, the RLC entity, the primary RLC entity, the default RLC entity, and the initial RLC entity configured for convenience of explanation may be used as various names and the names are not limited.

For another example, the base station may indicate a timer for deactivating the redundant transmission when the redundant transmission is activated. After receiving the RRC message including the timer for deactivating the redundant transmission, the UE starts the timer when the redundant transmission is activated according to a specific instruction or condition. When the uplink RRC message is generated while the corresponding timer is operating, the UE may transmit the corresponding RRC message through the two transmission paths from the PDCP entity. If the RRC message is generated after the timer expires, the UE can transmit the PDCP entity through one transmission path.

For example, when the uplink RRC message is generated while the timer for deactivating the redundant transmission is generated, or when the PDCP entity transmits the RRC message through two transmission paths, or when the PDCP entity transmits a redundant transmission It is possible to restart the timer. If the RRC message is generated after the timer expires, the UE can transmit the PDCP entity through one transmission path.

The base station can check the radio link quality status of the UE through an RRM measurement report or CQI feedback from the UE. Accordingly, the base station can instruct activation / deactivation of the redundant transmission through the lower layer information.

For example, whether to activate the redundant transmission function in the PDCP entity configured in the UE can be indicated through the MAC CE. That is, if the BS has a redundant transmission function in the PDCP entity, the BS may transmit indication information for instructing activation or deactivation of the corresponding function to the MS, including the MAC CE. The indication information may include information for indicating whether to activate or not for each data radio bearer. When the indication information indicates the active state, the terminal can transmit data to the radio bearer over a plurality of radio paths in a redundant manner. To this end, the PDCP entity may forward the same PDCP PDU to different RLC entities. The indication information provided through the MAC CE to indicate whether the corresponding PDCP entity for each of the one or more data radio bearers is to be activated or deactivated is configured to indicate an activation / deactivation state for each radio bearer corresponding to each radio bearer identifier And may include bitmap information. For another example, the base station can indicate via the PDCCH indication information indicating whether to activate or not. In another example, if the UE receives the indication information through the MAC CE or the PDCCH, the UE may transmit the indication information to the RRC or the PDCP layer that processes the redundant transmission. For another example, the base station may indicate the indication information through the PDCP control data.

On the other hand, the terminal may transmit information indicating to the base station whether to enable or disable (or enable / disable) redundant transmission using MAC CE or PUCCH.

The configuration information indicating the configuration of the RRC message re-transmission to the UE may include condition information for activating / deactivating the RRC data re-transmission. Or the configuration information may include switching information for instructing the terminal to switch the data transmission path between two paths constituted by dual connectivity, and the switching information may include condition information for switching the data transmission path . For convenience of description, the conditions for activating the redundant transmission will be described below. The conditions for instructing to switch the data transmission path between two paths constituted by dual connectivity may be set to be the same or similar. The condition may be included in the above-described condition information.

For example, the reference radio signal quality value for activating the RRC message duplication transmission may be included in the condition information. For example, a terminal may be referred to as a master base station (or a master TRP or a master cell or a PCELL or anchor beam or a best beam, a master base station for convenience of explanation, but any transmission signal on the NR is also included in the scope of the present embodiment) If the quality meets (or exceeds, or is equal to or greater than) the corresponding reference radio quality value, then there is no need to activate the RRC redundant transmission. For example, when the radio quality of the master base station is greater than (or equal to or greater than) the reference value indicated by the base station, the RRC message may be transmitted through one transmission path from the PDCP entity. That is, the corresponding RRC message can be transmitted through the master base station. In another example, the terminal may activate the RRC redundant transmission if the radio quality of the master base station is less than (or equal to or less than) the reference radio quality value. That is, when the radio quality of the master base station is smaller than (or equal to or less than) the threshold value indicated by the base station, the RRC message may be transmitted from the PDCP entity through two transmission paths.

For another example, the condition may be an uplink data separation threshold. If the data redundancy transmission is not configured and activated, and if the data transfer is configured but not activated, if the available PDCP data volumes associated with the two RLC objects and the RLC data volume are less than the corresponding conditions, the PDCP data To the configured single path RLC entity.

In another example, if the radio quality of the secondary base station is greater than (or equal to or greater than) the threshold value indicated by the base station, the RRC message may be transmitted on one transmission path from the PDCP entity. For example, the terminal can transmit data only through the secondary base station.

In another example, the master base station and the secondary base station may be instructed to transmit data via a path that provides better radio quality.

For example, if both the master base station and the secondary base station are smaller than (or equal to or less than) a certain threshold value, the RRC message may be transmitted from the PDCP entity through two transmission paths.

When the condition for activating / deactivating the RRC redundant transmission is satisfied for the above operation, the physical layer can transmit the condition to the upper layer. For example, when transmitting through two transmission paths in the PDCP layer, the physical layer can indicate it as a PDCP entity. Or when the RRC layer transmits through two transmission paths, the physical layer can instruct it to the RRC.

The PDCP entity may activate or deactivate redundant transmissions if indicated by the physical layer that the condition is satisfied.

To this end, the base station may be configured to determine a radio quality threshold associated with activation / deactivation, a threshold condition (e.g., a number of higher quality thresholds, a quality lower than threshold, a number of consecutive outofsync, Link data separation data amount threshold value, etc.), a timer for checking a threshold value condition, a period for checking a threshold value condition, an indication condition to an upper layer, and a filtering parameter. For example, an RLM procedure can be used for this purpose. Another example is to use RRM measurements for this. Another example is to use the Beam measurement for this purpose.

The downlink radio quality can be monitored by the UE for a specific cell in the master cell group or for all the cells in the master cell group. This may be for triggering (determining / stopping / canceling / stopping) RRC duplicated transmission or PDCP data (PDCP SDU or PDCP PDU) redundant transmission. Or monitoring may be directed to an upper layer for RRC redundancy transmission or PDCP data redundancy transmission.

Likewise, downlink radio quality can be monitored by the UE for a particular cell in the secondary cell group or for all cells in the secondary cell group. This may be for triggering (determining / stopping / canceling / stopping) RRC duplicated transmission or PDCP data (PDCP SDU or PDCP PDU) redundant transmission. Alternatively, the monitoring may be to indicate to the upper layer a state for RRC redundant transmission or PDCP data redundant transmission.

If the RLM is used, the BS can indicate a threshold value for instructing the upper layer to perform the RLM operation by the physical layer of the UE. The threshold value may be a separate threshold value separate from the threshold value for the conventional general RLM operation.

As described above, the UE may configure one or more MAC entities or RLC entities to duplicate data over a single base station based CA. Through this, the terminal can efficiently perform redundant transmission even when redundantly transmitting data requiring reliability.

Hereinafter, detailed embodiments of a buffer status report (buffer status report) in the case where a UE configures a single base station-based CA to perform redundant transmission will be described in more detail.

Buffer status reporting procedure

The buffer status reporting procedure is a procedure used to provide the serving base station with information about data available for transmission in uplink (UL) buffers associated with the MAC entity. The RRC entity configures three timers (e.g. , periodic BSR -Timer , retxBSR-Timer and logicalChannelSR-ProhibitTimer ) and provides buffer status reporting (Buffer) by signaling to allocate a logical channel to a logical channel group for each logical channel Status Repot, BSR) transmission.

The buffer status report should be triggered when the following events occur:

Uplink data is available for one logical channel belonging to one logical channel group (LCG) for transmission in an RLC (Radio Link Control) entity or a PDCP (Packet Data Convergence Protocol) entity. Loses. And the data belongs to one logical channel belonging to any logical channel group and having a higher priority than the priority of logical channels for already available data, or belongs to one logical channel belonging to one logical channel group No data is available for any. In this case, the buffer status report is called " Regular BSR ". (UL data, a logical channel which belongs to a LCG, becomes available for transmission in the RLC entity or the PDCP entity [3] and [4] respectively) and either the data belongs to a logical channel with higher priority than the priorities of the logical channels which are any of LCG and for which data is already (BSR), which is used for transmission of any kind of logical channels, and which is used for transmission.

- The buffer status report is called "padding BSR" when the uplink resource is allocated and the number of padding bits is equal to or greater than the size of the buffer status report MAC control element plus its subheader.

- The buffer status report when the retransmission BSR timer (retxBSR-Timer) has expired and the terminal has available data for transmission on any of the logical channels belonging to the LCG is also referred to as " Regular BSR ".

- The buffer status report when the periodic BSR timer (periodic BSR-Timer) expires is called " periodic BSR ".

In addition, the buffer status report can be classified into Short BSR, Truncated BSR, and Long BSR according to the format as well as classification according to the BSR trigger type.

FIG. 14 is a diagram illustrating a Short BSR format according to the prior art, and FIG. 15 is a diagram illustrating a Long BSR format according to the prior art.

For Regular BSR and Periodic BSR, if more than one LCG has available data for transmission in the TTI (Transmission Time Interval) in which the BSR is transmitted, it transmits Long BSR (if more than one LCG has data available for transmission in the TTI where BSR is transmitted: report Long BSR). Otherwise, it sends a Short BSR.

If, for a Padding BSR, the number of padding bits is equal to or greater than the size of the Short BSR plus its subheader, but less than the size of the Long BSR plus its subheader, and if the BSR has more than one LCG in the transmitted TTI If it has available data, it sends the Truncated BSR of the LCG with the highest priority logical channel with the available data for transmission (if the number of padding bits is equal to or greater than the size of the Short BSR plus its subheaderbutsmaller than the size of the long BSR plus its subheader: if more than one LCG has data available for transmission in the TTI where BSR is transmitted: report Truncated BSR of the LCG with the highest priority logical channel with data available for transmission; . Otherwise, it sends a Short BSR.

Otherwise, if the number of Padding bits is equal to or greater than the size of the Long BSR plus its subheader, then a Long BSR is transmitted.

As shown in FIG. 2, the Short BSR and the Truncated BSR include logical channel group ID information and buffer size information. As shown in FIG. 3, the Long BSR sequentially includes buffer size information for four LCGs.

The BSR is transmitted to the MAC Control Element (MAC CE), and one MAC PDU (Protocol Data Unit) may include at most one MAC BSR control element.

If one BSR is included in one MAC PDU for transmission, all triggered BSRs are canceled.

The MAC entity shall transmit at most one Regular / Periodic BSR within one Transmission Time Interval (TTI).

All BSRs transmitted in one TTI always indicate the buffer status after all MAC PDUs are created for this TTI. Each logical channel group must transmit at most one buffer status value per TTI. And this value should be transmitted in all the BSRs transmitting the buffer status for this logical channel group.

Data available for transmission or data volume

For reporting the buffer status of the MAC layer, the UE shall consider the following as the amount of data available in the RLC layer:

- RLC SDUs not yet included in the RLC data PDU, or segments

- pending RLC data PDUs for retransmission (RLC AM)

- RLC data PDUs pending for initial transmission

For reporting the buffer status of the MAC layer, the UE shall consider the following PDCP control PDUs as the amount of data available in the PDCP layer.

For SDUs whose PDUs are not submitted as lower layers,

- If there is an SDU that has not yet been processed by the PDCP, the SDU itself

- If there is an SDU processed by the PDCP,

As described above, in the conventional LTE technology, the buffer status of the UE is reported through Regular BSR, Periodic BSR, or Padding BSR. If packet re-transmission is configured for a CA-based bearer between a single base station and a terminal, duplicate packet transmission for the bearer is started / activated / on, and the UE reports a buffer status through a short BSR procedure, The buffer state to be actually transmitted may not be accurately grasped. Accordingly, the base station has a problem that the uplink resource can be under-allocated to the corresponding terminal.

In order to solve such a problem, this embodiment effectively provides a buffer status reporting of a UE when packet redundancy transmission is configured for a CA-based specific bearer between a single base station and a terminal or when packet redundancy transmission for a corresponding bearer is started / And to provide a method and an apparatus for carrying out the present invention.

Hereinafter, a description will be given of a method for efficiently providing buffer status reporting of a UE when packet redundant transmission is configured for a CA-based specific bearer between a single base station and a terminal, or when packet redundancy transmission for a corresponding bearer is started / activated / on. The embodiments described below may be applied individually, or some or all of them may be applied mutually combined. All such embodiments are included in this disclosure.

For the sake of convenience of description, the term " TTI " in the present specification may mean a transmission unit defined in NR (e.g., any physical layer transmission unit such as a slot or a minislot).

First, a method of triggering and reporting a buffer status report (BSR) will be described, and an embodiment in which a PDCP data volume is calculated and processed later will be described.

First Embodiment: One transmission unit ( TTI)  Single BSR  Two different Carrier  ≪ RTI ID = 0.0 >

In the prior art, a MAC entity must transmit at most one Regular / Periodic BSR within one Transmission Time Interval (TTI). However, in this case, when a radio bearer configured to provide PDCP redundant transmission is configured, it may be difficult to stably transmit the buffer status for the two logical channels associated with the radio bearer.

For example, when a radio bearer configured to provide PDCP redundant transmission is configured or when the PDCP redundancy transmission of the radio bearer is initiated / activated by L2 signaling (MAC CE or PDCP Control PDU) of the base station, the BSR is triggered .

In another example, when a radio bearer configured to provide PDCP redundant transmission is configured or when the PDCP redundant transmission of the radio bearer is initiated / activated by L2 signaling (MAC CE or PDCP Control PDU) of the base station, the existing BSR trigger criteria The BSR may be triggered.

For example, two logical channels associated with the radio bearer may be directed to be included in different logical channel groups. When a Regular BSR or Periodic BSR is triggered for each of two logical channel / logical channel groups associated with a different logical channel group (LCG) associated with a corresponding radio bearer, if the TTI to which the BSR is transmitted has more than one LCG If you have available data for transmission, you can report Long BSR. Therefore, when each logical channel associated with the corresponding radio bearer is included in a different logical channel group, the BSR including the buffer status information of each corresponding logical channel group can be transmitted to the base station.

The BSR including the buffer status of each logical channel group described above can be transmitted through one TTI on each mutually exclusive cell / carrier associated with each logical channel belonging to the corresponding radio bearer.

As an example for this, each scheduling request (SR) may be triggered on each mutually exclusive carrier. Another example for this is when a radio bearer configured to provide PDCP redundant transmission is configured to transmit the corresponding BSR on each mutually exclusive carrier, the base station receiving the SR can transmit the corresponding BSR on each mutually exclusive carrier So that uplink resources can be allocated. As another example, when the PDCP redundancy transmission of the corresponding radio bearer is started / activated by the L2 signaling (MAC CE or PDCP Control PDU) of the base station so that the corresponding BSR can be transmitted on each mutually exclusive carrier, A base station may allocate uplink resources to transmit the corresponding BSR on each mutually exclusive cell / carrier.

On the other hand, an SR may be triggered to transmit the corresponding BSR on each mutually exclusive carrier. The SR may include information for indicating this. In another example, the base station may indicate information indicating that the SR is allowed.

The BSR including the buffer status of each logical channel group may be transmitted in one TTI via one of the mutually exclusive carriers associated with each logical channel belonging to the corresponding radio bearer.

The amount of available data of the PDCP entity included in the buffer status report may be included in the buffer size of each logical channel group. Processing of the PDCP data volume including this will be described later.

SECOND EMBODIMENT: To provide redundant transmission On the radio bearer  For the associated logical channels BSR  Embodiment for indicating a retransmission timer

When a UE reports BSR to a BS for a radio bearer for which PDCP redundancy transmission of a corresponding radio bearer is initiated / activated by L2 signaling of a radio bearer or a base station configured for redundant transmission, the base station allocates an uplink grant . If the MAC PDU including the BSR is lost, reliable low-delay transmission may be difficult if uplink data is available for the two logical channels associated with the corresponding radio bearer.

For example, the base station may set a RetxBSR-Timer for the corresponding radio bearer (or for each radio bearer). In another example, the BS may set the Retransmission BSR-Timer for the corresponding radio bearer (or the radio bearer) to a specific value instead of the existing retransmission BSR timer values (sf320, sf640, sf1280, sf2560, sf5120, sf10240). In another example, the terminal may trigger (or transmit to the base station) the BSR when the retransmission BSR timer (retxBSR-Timer) expires.

As another example, when the timers (periodicBSR-Timer, retxBSR-Timer) described above are configured for each radio bearer, for each logical channel, or for each logical channel group, for each radio bearer / logical channel / logical channel group timer Each radio bearer, per logical channel, per logical channel group, or each radio bearer / per logical channel / logical channel group timer and timer (common to the UE) Lt; / RTI >

Third Embodiment: A method for providing redundant transmission On the radio bearer  For the associated logical channels Uplink  When data becomes available, buffer status Reporting Triggering Embodiment

For example, two logical channels associated with the radio bearer may be directed to be included in the same logical channel group.

In another example, the two logical channels associated with that radio bearer may be directed to be included in different logical channel groups.

According to the prior art, when uplink data is available for two logical channels associated with a radio bearer for which the PDCP redundancy transmission of the radio bearer is initiated / activated by the L2 signaling of the radio bearer or base station for which the redundant transmission is configured, The logical channel / logical channel group belongs to one logical channel having a higher priority than the priority of the logical channels for the already available data, or belongs to any one of the logical channels belonging to one logical channel group The Regular BSR is triggered only if no data is available.

In this case, even if the uplink data belonging to the radio bearer continues to be generated, the buffer status report can not be quickly sent to the base station, so reliable low-delay transmission can be difficult.

Accordingly, for a radio bearer in which the PDCP re-transmission of the corresponding radio bearer is initiated / activated by the L2 signaling of the radio bearer or the base station configured for redundant transmission, the UE transmits uplink data Can be used to trigger a Regular BSR.

This may be preconfigured in the terminal or indicated by signaling of the base station. For example, the base station can instruct the terminal to transmit information for indicating the information through the RRC signaling. In another example, if the base station indicates a Periodic BSR-Timer with a particular value (e.g., 0), the UE may trigger the Regular BSR if the uplink data for that radio bearer is available. In another example, the base station may set the corresponding radio bearer dedicated (or per radio bearer) Periodic BSR-Timer. In this case, the UE can trigger the Regular BSR if the uplink data for the corresponding radio bearer (or logical channel / logical channel group) becomes available.

As another example, for a radio bearer in which the PDCP re-transmission of the radio bearer is initiated / activated by the L2 signaling of the radio bearer or the base station for which the redundant transmission is configured, the UE sets a specific threshold value for the two logical channels associated with the radio bearer To trigger the Regular BSR if the available uplink data is greater than or equal to the corresponding threshold value. For this purpose, the BS can indicate a threshold value for the corresponding radio bearer or logical channel to the MS.

Fourth Embodiment: A method for providing redundant transmission On the radio bearer  For the associated logical channels Uplink  Once the data becomes available padding BSR (Or redundant transmission BSR ) ≪ RTI ID = 0.0 >

In the prior art, the logical channel priority procedure considers the following relative priorities: (For the Logical Channel Prioritization procedure, the MAC entity shall take into account the following relative priority in decreasing order)

- MAC control element for C-RNTI or data from UL-CCCH;

- MAC control element for DPR;

- MAC control element for SPS confirmation;

- MAC control element for BSR, with exception of BSR included for padding;

- MAC control element for PHR, Extended PHR, or Dual Connectivity PHR;

- MAC control element for Sidelink BSR, with exception of Sidelink BSR included for padding;

- data from any Logical Channel, except data from UL-CCCH;

- MAC control element for the recommended bit rate query;

- MAC control element for BSR included for padding;

- MAC control element for Sidelink BSR included for padding.

Accordingly, the priority of the MAC CE for the BSR included in the padding is lower than that of data from any logical channel.

When uplink data is available for two logical channels associated with a radio bearer for which the PDCP redundancy transmission of the radio bearer has been started / activated by the L2 signaling of the radio bearer or the base station for which the redundant transmission is configured, an uplink belonging to the radio bearer If the link data continues to occur, it is necessary to send the BSR quickly. For this, the priority of the MAC CE for the BSR included in the padding can be considered to be higher. For example, the priority of the MAC CE for the BSR included in the padding can be made higher than the data from any logical channel. For another example, the priority of the MAC CE for the BSR included in the padding can be set higher than any priority order described above.

Alternatively, if the Padding BSR is included, the MAC PDU can be transmitted to the base station without including the additional Padding BSR. As another example, even when the Padding BSR is included, the MAC PDU including the additional padding BSR can be transmitted to the BS.

When uplink data becomes available for two logical channels associated with a radio bearer for which the PDCP redundancy transmission of the radio bearer has been started / activated by L2 signaling of the radio bearer or the base station for which the redundant transmission is configured, BSR for available uplink data transmission can be defined. The priority of MAC CE for BSR can be considered higher. For example, the priority of the MAC CE for the BSR may be higher than the data from any logical channel. For another example, the priority of the MAC CE for that BSR may be higher than any of the precedence sequences described above. For another example, the priority of the MAC CE for the BSR may be set to be equal to or higher than the MAC control element for BSR, with exception of BSR included for padding.

Fifth Embodiment: A method for providing redundant transmission On the radio bearer  The buffer status for only one logical channel for the associated logical channel Example of reporting

When a UE reports BSR to a BS for a radio bearer where PDCP redundancy transmission of the corresponding radio bearer is initiated / activated by L2 signaling of a radio bearer or a base station for which redundant transmission is configured, the base station can allocate uplink grant have. The base station knows information about a logical channel / logical channel group belonging to the radio bearer, and mutually exclusive carriers associated with the logical channel. Therefore, it is possible to allocate the uplink grant according to the reception of only the buffer status for one of the logical channels without reporting the buffer status for each logical channel / logical channel group belonging to the corresponding radio bearer. This is also possible for a logical channel group when only one radio bearer is included in the logical channel group, or when only logical bearers are configured / activated in the logical channel group. If there is a missing RLC packet on an individual carrier, the buffer state for each logical channel may vary, but only one of the transmissions may succeed and this probability may not be significant.

Accordingly, for example, the UE can transmit only the buffer status of one of the bearers (or the logical channel including the first logical channel or the default logical channel or the PCell or the logical channel associated with the first RLC entity) to the base station have. In another example, the UE transmits only available data for uplink data of one logical channel of the bearer (or the logical channel including the first logical channel or the default logical channel or PCell or the logical channel associated with the first RLC entity) to the base station . In another example, the UE transmits available data for uplink data of a logical channel other than the logical channel (or a logical channel including the second logical channel or the PCell or a logical channel associated with the second RLC entity) It may not be considered as a trigger object. As another example, the UE may determine that the RLC entity has notified the uplink data to a logical channel other than the logical channel (or a logical channel that does not include the second logical channel or the PCell or a logical channel associated with the second RLC entity) It may be instructed not to instruct the MAC entity or ignore the indicated available data. Another example may include a field that identifies a duplicate BSR in a particular indication (e.g., a logical channel identifier (LCID) or an index value or a break value). Another example is to allow the BSR to send a buffer status report for a single logical channel group using Short BSR.

Sixth Embodiment: A method for providing redundant transmission On the radio bearer  For the associated logical channel / logical channel group Triggered BSR  Keep or next Uplink  Examples of Transfer to Grant

In the prior art, if one BSR is included in one MAC PDU, all triggered BSRs are canceled. However, an increase in the number of logical channel groups may require improvements to this BSR cancellation. That is, when only a BSR for one logical channel group is transmitted through the Short BSR or the Truncated BSR, it is difficult for the BS to identify the BSR of the remaining logical channel group, so that a mismatch occurs between the UE and the BS, The base station can not effectively perform the uplink resource allocation.

For example, if the number of logical channel groups is less than a certain value, all triggered BSRs can be canceled if one BSR is included in one MAC PDU for transmission. The aforementioned specific values may be pre-configured (or fixed) to the terminal or may be indicated to the terminal by the base station.

As another example, if the number of logical channel groups is larger than a certain value, one BSR can be retained in one MAC PDU for transmission except for the transmitted BSR (or a specific BSR triggered excluding the transmitted BSR). The BSR can then be transmitted if the uplink grant is received at the next TTI or within a specified number of TTIs.

As another example, for a radio bearer where duplicated transmission of PDCP of the corresponding radio bearer is initiated / activated by L2 signaling of the radio bearer or base station configured for redundant transmission, one BSR transmits the logical channel / logical channel group of the corresponding radio bearer (Or a specific BSR triggered by including the logical channel / logical channel group of the corresponding radio bearer excluding the transmitted BSR) may be retained even though it is included in one MAC PDU for the UE. The BSR can then be transmitted if the uplink grant is received at the next TTI or within a specified number of TTIs.

Hereinafter, a case where one radio bearer supports redundant transmission through two RLC entities will be described as an example. This is for convenience of description and can be applied to the various MAC entities and the RLC entity embodiments described with reference to FIGS. 5 to 13, the same or similar.

As described above, the base station can configure two RLC entities associated with one radio bearer for redundant transmission to the UE. A base station can configure two RLC entities associated with a single radio bearer in a terminal by dividing the RLC entity into a basic / default RLC entity and an additional RLC entity. For convenience of description, a RLC entity added for redundant transmission of a basic / default RLC entity associated with a radio bearer to a first RLC entity will be referred to as a second RLC entity in the following description.

Hereinafter, each embodiment of the data available for transmission or data volume calculation or processing will be described in detail.

The buffer status reporting procedure is used to provide the serving base station with information about available data or data available for transmission in uplink (UL) buffers of the terminal associated with the MAC entity of the serving base station. For convenience of explanation, the available data or transmission data for transmission in the uplink (UL) buffers of the terminal will be referred to as "available data" or " do.

For MAC buffer state reporting, the UE shall consider the following as available data for transmission in the RLC layer.

- RLC SDUs, or segments (RLC SDUs, or segments thereof, that have not been included in an RLC data PDU)

- RLC data PDUs or portions (RLC data PDUs, or portions thereof, that are pending for retransmission (RLC AM). RLC data PDUs, or portions thereof,

Conventionally, for the purpose of MAC buffer status reporting, the UE must consider the PDCP control PDUs and the following as available data for transmission in the PDCP layer.

For any SDU that has not been submitted to the lower layer (PDUs for which PDU has been submitted to lower layers)

- the SDU itself, if not already processed by the PDCP (the SDU itself, if the SDU has not yet been processed by PDCP), or

If the SDU has been processed by the PDCP, the PDU (the PDU if the SDU has been processed by PDCP)

PDCP control PDUs

In this way, the PDCP data PDUs corresponding to the user data and the PDCP data PDUs and the PDCP control PDUs used for the user data control in the PDCP layer are used for calculating the available PDCP data volume.

In addition, for a radio bearer mapped onto an RLC AM, if the PDCP entity has performed a reset procedure, the UE shall consider the following as the amount of data available for transmission at the PDCP layer (PDCP data volume).

Except for those SDUs indicated to have been successfully delivered by the PDCP status report, to the SDU for that PDU that the PDU was submitting only to the lower layer prior to the PDCP reset, for the delivery of the corresponding PDUs not acknowledged by the lower layer Starting from the first SDU

- SDU, if not yet processed by the PDCP

- The PDU that was processed by the PDCP (the PDU has been processed by PDCP.

If the PDCP entity provides redundant transmission, the embodiments described below may be used individually or in combination to process the available data in the terminal. This can be applied not only to a case where a single base station performs redundant transmission through a plurality of carriers on a CA basis but also to a case where redundant transmission is performed through a plurality of cells based on two base stations (dual connectivity).

First Embodiment: Redundant Transmission Bearer Activated  If available data PDCP Amount of data  Embodiments in which the redundant (multiple)

The base station can configure one PDCP entity and two associated RLC entities in one radio bearer for redundant transmission to the UE.

For one radio bearer providing redundant transmission, when indicating available data (data volume) for transmission to the MAC entity for BSR triggering and buffer size calculation, the UE can operate as follows.

For example, if a condition (threshold / threshold) for a redundant transmission is configured and the redundant transmission condition is satisfied (or if the redundant transmission condition parameter is greater than or equal to the redundant transmission threshold, , The terminal (PDCP entity of the terminal) indicates twice the data buffered in the PDCP entity as available data for transmission to the MAC entity. Indicates n times the amount of data buffered in a PDCP entity that is redundantly transmitting over n radio paths through n logical channels.

As another example, if the radio bearer indication information for the redundant transmission is configured by the base station and the L2 signaling (for example, MAC CE) for activating the redundant transmission is received by the base station, the terminal (PDCP entity of the terminal) It indicates twice the amount of data buffered in the PDCP entity as available data for transmission to the MAC entity. For example, the above-described L2 signaling may be information for instructing the RLC layer (or the first RLC entity) to define a control PDU to activate a redundant transmission. As another example, the above-described L2 signaling may be information for instructing the PDCP layer (or the PDCP entity) to define a control PDU to activate a redundant transmission. For another example, the above-described L2 signaling may be information for instructing to define a control PDU in the MAC layer (or MCG MAC entity) or activate a redundant transmission through a MAC Control element (having a new LCID). The MAC Control element may include radio bearer identification information for activating the redundant transmission, logical channel identification information for the logical channel, activation / deactivation indication information of the corresponding radio bearer or logical channel.

As another example, when the UE provides the PDCP redundancy transmission using one MAC entity on a CA basis in a single base station as shown in FIG. 8, the UE (PDCP entity of the UE) under the above- It can indicate twice the total data buffered in the PDCP entity. For example, the PDCP data volume of the logical channel associated with the first RLC entity may be set to include the PDCP data volume for the PDCP SDUs, the PDCP data PDUs, and the PDCP control PDUs, and be directed to the corresponding MAC entity. The PDCP data volume of the logical channel associated with the second RLC entity may also be set to include the PDCP data volume for the PDCP SDUs, the PDCP data PDUs, and the PDCP control PDUs, and may be indicated to the corresponding MAC entity. That is, in the calculation of the PDCP data volume of the logical channel associated with the first RLC entity and the logical channel associated with the second RLC entity, the data volumes for the PDCP SDUs, the PDCP data PDUs, and the PDCP control PDUs, Can be calculated.

As another example, for any SDU that has not been submitted as a lower layer to any PDU (For SDUs for which no PDU has been submitted to lower layers)

- The SDU itself, if it has not yet been processed by the PDCP (the SDU itself, if the SDU has not yet been processed by the PDCP), can be indicated twice the calculated PDCP usable data.

- If the SDU has been processed by the PDCP, the PDU (PDU if the SDU has been processed by PDCP) PDCP data PDU available data can be indicated.

- For PDCP control PDU, PDCP control PDU usable data may be indicated.

The PDCP usable data calculated by the above method can be designated as a MAC entity. Therefore, when the PDCP PDU is copied by the PDCP, the amount of the SDU data is doubled, since the PDCP PDUs already have twice the amount of data, but the PDCP PDU data amount can be directly transmitted to the terminal MAC entity. Also, since the PDCP control PDUs used for user data control do not need redundant transmission, the PDCP control PDUs other than the user data can directly indicate the corresponding data amount. Redundant transmissions are for low latency and high reliability services for user data. Accordingly, the PDCP control PDU for controlling the user data can be transmitted through the cell / cell group associated with the first cell or the first RLC entity. For example, the PDCP data volume of the logical channel associated with the first RLC entity may be indicated as a corresponding MAC entity including PDCP data volumes for PDCP SDUs, PDCP data PDUs, and PDCP control PDUs. The PDCP data volume of the logical channel associated with the second RLC entity may be indicated as a corresponding MAC entity including only the PDCP data volume for the PDCP SDUs. That is, the PDCP data volume of the logical channel associated with the second RLC entity may instruct the corresponding MAC entity except for the PDCP data PDUs and the PDCP data volumes for the PDCP control PDUs.

As another example, for any SDU that has not been submitted as a lower layer to any PDU (For SDUs for which no PDU has been submitted to lower layers)

- The SDU itself, if not already processed by the PDCP (the SDU itself, if the SDU has not yet been processed by the PDCP), may be indicated twice the calculated PDCP SDU usable data.

- If the SDU is being processed by the PDCP and the PDCP is not duplicated / copied yet, the PDCP Data PDU usable data calculated by the SDU (or PDU) can be doubled.

If the SDU has been processed by the PDCP, the SDU has been processed by the PDCP or the PDCP if the PDU has been processed by the PDCP or the PDCP PDU (if duplicated / copied, or if there are duplicated PDUs before submitting to the lower layer from the PDCP) Available data may be indicated.

For a PDCP control PDU, the PDCP control PDU available data / data volume may be indicated.

The PDCP usable data calculated by the above method can be designated as a MAC entity. This is because the PDCP duplicate function may be a function provided by the PDCP. For example, when a duplicated / copied PDCP PDU exists when calculating the PDCP data volume, when calculating the PDCP data volume, the duplicated / copied PDCP PDU and the duplicated / copied PDCP PDU should be distinguished from each other and processed. Otherwise, if PDCP PDUs for user data are to be duplicated / copied when submitting PDCP PDUs for user data to lower layers, PDCP PDUs may have to be distinguished and processed when calculating the PDCP data volume. Therefore, when the PDCP PDU is duplicated / copied when the PDCP PDU is submitted to the lower layer by the PDCP, the PDCP PDU is instructed to double the data amount for the PDCP SDUs or PDCP PDUs until the PDCP PDU for the user data is duplicated / copied . However, the amount of PDCP control PDU data other than the user data can be directly transmitted to the terminal MAC entity. For example, the PDCP data volume of the logical channel associated with the first RLC entity may be indicated as a corresponding MAC entity, including PDCP data volumes for PDCP SDUs, PDCP data PDUs, and PDCP control PDUs. The PDCP data volume of the logical channel associated with the second RLC entity may be indicated as a corresponding MAC entity including PDCP data volumes for PDCP SDUs and PDCP data PDUs. That is, the PDCP data volume of the logical channel associated with the second RLC entity may be indicated as a corresponding MAC entity except for the PDCP data volume for the PDCP control PDUs.

As another example, when a mobile station provides two PDCP duplicated transmissions using two MAC entities based on DCs in two base stations, the terminal (PDCP entity of the terminal) under the above-mentioned conditions transmits PDCP The amount of available data buffered in the entity may be indicated.

Embodiment 2: Redundant transmission wireless Bearer  If it is disabled, PDCP Embodiment for indicating the amount of data

The base station can configure one PDCP entity and two associated RLC entities in one radio bearer for redundant transmission to the UE.

For one radio bearer providing redundant transmission, the UE can operate as follows when indicating available data (data volume) for transmission to the MAC entity for BSR triggering and buffer size calculation.

For example, if a condition (threshold / threshold) for redundant transmission is configured but the redundant transmission condition is not satisfied (or the redundant transmission condition parameter is smaller than the redundant transmission threshold, or the physical layer does not reach the redundant transmission condition (PDCP entity of the terminal) does not receive the information indicating that the duplicated transmission condition has been reached by the physical layer), the terminal (PDCP entity of the terminal) can not buffer the PDCP entity in the PDCP entity as available data for transmission to the MAC entity Quot; As another example, if the radio bearer indication information for the redundant transmission is configured by the base station and L2 signaling for activating the redundant transmission is not received by the base station, or if L2 signaling for deactivating the redundant transmission is received by the base station , Or signaling to disable / deactivate the redundant transmission by the base station, the terminal (PDCP entity of the terminal) indicates the amount of data buffered in the PDCP entity as available data for transmission to the MAC entity. That is, if the CA is configured on the basis of a single base station, the terminal (PDCP entity of the terminal) is not activated if the redundant transmission is configured and activated in the terminal, for example, if redundant transmission is not configured or if redundant transmission is configured, And directly indicates the amount of data buffered in the PDCP entity as available data for transmission to the MAC entity (MAC entity associated with the first RLC entity).

As another example, when the UE provides a PDCP redundancy transmission using one MAC entity in a single base station in a single base station as shown in FIG. 8, the UE (PDCP entity of the UE) (E.g., a MAC entity that has received the MAC PDU), the amount of available data buffered in the PDCP entity as available data for transmission.

Embodiment 3: Redundant transmission Bearer  Depending on activation Second RLC  An embodiment indicating the available data of the entity

For example, as shown in FIG. 8, when a UE provides a PDCP redundant transmission using a single MAC entity based on a CA in a single base station, it can indicate available data of a second RLC entity according to whether a redundant transmission bearer is activated have. For example, if radio bearer indication information for redundant transmission is configured by the base station and L2 signaling for activating redundant transmission is received from the base station, the terminal (the PDCP entity of the terminal or the second RLC entity of the terminal) And indicates available data buffered in the second RLC entity as available data for transmission. As another example, if a condition (threshold / threshold) for redundant transmission is configured and the redundant transmission condition is satisfied (or if the redundant transmission condition parameter is greater than or equal to the redundant transmission threshold, or if the physical layer reaches a redundant transmission condition ), The terminal (the second RLC entity of the terminal) indicates the available data buffered in the second RLC entity as available data for transmission to the MAC entity.

As another example, if a condition for a redundant transmission (condition / threshold) is configured but the redundant transmission condition is not satisfied (or the redundant transmission condition parameter is smaller than the redundant transmission threshold, or the physical layer does not reach the redundant transmission condition (Or the second RLC entity of the terminal) does not receive the information indicating that the duplicated transmission condition has been reached by the physical layer), the terminal (the terminal's second RLC entity) sets the available data for transmission to the MAC entity as 0 Indicate. Or do not tell.

As another example, if the radio bearer indication information for the redundant transmission is configured by the base station and L2 signaling for activating the redundant transmission is not received by the base station, or if L2 signaling for deactivating the redundant transmission is received by the base station , Or signaling for releasing / deactivating the redundant transmission by the base station, the terminal (the second RLC entity of the terminal) indicates 0 to the available data for transmission to the MAC entity. Or do not tell.

Fourth Embodiment: Redundant transmission On the bearer  As available data PDCP Data volume  Examples of direct indication

The MAC entity can calculate the buffer size by including the PDCP data volume in the logical channel / logical channel group associated with the corresponding radio bearer, respectively.

The base station can configure one PDCP entity and two associated RLC entities for one radio bearer for redundant transmission to the terminal. The BS may transmit information instructing the UE to activate / deactivate the redundant transmission for the radio bearer that has configured the redundant transmission. Accordingly, the base station can perform rough uplink scheduling in consideration of the amount of uplink buffer for a specific bearer. Therefore, even if the UE constructs the indication information for the RB bearer, the UE can directly instruct the PDCP available data amount. Alternatively, when the buffer status reporting is performed in the MAC entity, the buffer status size of the corresponding radio bearer may be calculated in consideration of whether or not the redundant transmission is activated in calculating the buffer status size of the radio bearer for the corresponding redundant transmission.

For example, if a condition (threshold / threshold) is configured for a redundant transmission and the redundant transmission condition is satisfied (or if the redundant transmission condition parameter is greater than or equal to the redundant transmission threshold, or if the physical layer has reached a redundant transmission condition ), The terminal (PDCP entity of the terminal) indicates data buffered in the PDCP entity as available data for transmission to the MAC entity. The MAC doubles the available data of the PDCP entity corresponding to the buffer status reporting to calculate the buffer status. That is, the buffer status of the first logical channel associated with the radio bearer and the available data amount of the PDCP entity when calculating the buffer status of the second logical channel, respectively.

As another example, if the radio bearer directive information for the redundant transmission is configured by the base station and the L2 signaling for activating the redundant transmission is received by the base station, the terminal (PDCP entity of the terminal) transmits the available data for transmission to the MAC entity Indicates the data buffered in the PDCP entity. The MAC doubles the available data of the PDCP entity corresponding to the buffer status reporting to calculate the buffer status. That is, the buffer status of the first logical channel associated with the radio bearer and the available data amount of the PDCP entity when calculating the buffer status of the second logical channel, respectively.

As another example, if the UE provides the PDCP redundancy transmission using one MAC entity based on the CA in a single base station as shown in FIG. 8, the terminal (PDCP entity of the terminal) uses the PDCP entity Lt; RTI ID = 0.0 > buffered < / RTI > The MAC doubles the available data of the PDCP entity corresponding to the buffer status reporting to calculate the buffer status. That is, the buffer status of the first logical channel associated with the radio bearer and the available data amount of the PDCP entity when calculating the buffer status of the second logical channel, respectively.

For example, it is possible to process the data volume (available data) of the PDCP entity for each of the two logical channels associated with one radio bearer. The UE may transmit to the BS a buffer size including the PDCP data volume in each logical channel or logical channel group associated with one radio bearer.

Hereinafter, a procedure of reporting the buffer status by instructing the PDCP data volume to the MAC will be described in more detail. In order to clearly understand the above description, the RRC configuration parameters that the base station configures in the UE will be described first.

The RRC connection reconfiguration message used to configure / modify the RRC connection, for example to set / modify / release the radio bearer, or to add / modify / unlock the SCell and cell groups, includes master cell group configuration information, Group configuration information, radio bearer configuration information, dedicated NAS configuration information (dedeicatedInfoNAS), measurement configuration information, and other configuration information.

16 is a diagram illustrating an example of radio bearer configuration information according to an embodiment. 17 is a diagram illustrating an example of cell group configuration information according to an embodiment.

16 and 17, the radio bearer configuration information includes SRB configuration information (eg srb-ToAddModList), DRB configuration information (eg drb-ToAddModList), and security configuration information (eg, securityConfig ). ≪ / RTI >

SRB configuration information (e.g., srb-ToAddMod) and DRB configuration information (e.g., drb-ToAddMod) may include PDCP configuration information. Conventionally, the PDCP entity configured in the corresponding radio bearer and the RLC entity associated therewith can be identified through the radio bearer type information. However, in NR, more radio bearer types are defined than LTE due to the introduction of SCG split bearers, which complicates radio bearer reconfiguration procedures. In order to solve this problem, the upper layer configuration (for example, the bearer configuration including the PDCP and the SDAP) and the lower layer configuration (for example, the MCG / SCG configuration including the RLC and MAC) are divided into the radio bearer configuration information To design RRC signaling information.

The cell group configuration information may include a master cell group (master node) configuration information or a secondary cell group (secondary node) configuration information. The base station indicates a configuration parameter for one cell group to the terminal through a cell group configuration information element (CellGroupConfig IE). The cell group configuration information can distinguish the MCG from the SCG through the cell group identifier. For example, if the cell group identifier is not included, it may indicate MCG, otherwise SCG. In another example, the cell group configuration information may include parameters for distinguishing MCG and SCG.

Cell group configuration information includes logical channel configuration information (eg logicalChannel-ToAddModList), MAC cell group configuration information (eg mac-CellGroupConfig), RLF timer configuration information (eg rlf-TimersAndConstants), PCell configuration information (eg pCellConfig) (e.g., sCellToAddModList).

When designing the RRC signaling information in the above-described manner, it is necessary to designate the mapping / linkage information between the PDCP entity included in the radio bearer configuration information, which is the upper layer configuration information, and the RLC entity included in the cell group configuration information, do.

For example, when a CA-based redundant transmission is configured, the PDCP entity may include information for indicating an additional RLC entity associated with the PDCP configuration information for the PDCP entity included in the radio bearer configuration information. This indicates information that is different from information for indicating a basic RLC entity associated with the PDCP configuration information for the PDCP entity included in the radio bearer configuration information when the CA-based redundant transmission is not configured. As described above, in a CA-based redundant transmission, one radio bearer is configured with two logical channels associated with each non-overlapping cell and two RLC entities associated with each logical channel. Thus, the information for indicating the RLC entity may be associated using a logical channel identifier (logical channel identifier). In addition, the PDCP configuration information may include information for indicating a redundant transmission configuration.

As another example, when CA-based redundant transmission is configured, the logical channel configuration information (LCH-Config) included in the cell group configuration information includes information (RLC-config) for indicating the configuration of the RLC entity . In addition, the logical channel configuration information (LCH-Config) may include radio bearer identification information associated with the logical channel or Cell information (allowedCells) or cell list information allowed for the logical channel.

As described above, the UE can process the available data (data volume) of the PDCP entity according to the number of associated RLC entities, the configuration of the PDCP redundancy transmission and the activation, and the redundancy transmission of the CA-based PDCP.

For example, the terminal (or the PDCP entity of the terminal) can process the PDCP usable data as follows.

If the transmitting PDCP entity is associated with one RLC entity (or if it is associated with one logical channel or only one RLC entity is configured in tandem), the terminal (PDCP entity of the terminal) transmits the PDCP data volume to the corresponding MAC entity . This indicates that the PDCP entity of the UE instructs the PDCP data volume to the MAC entity associated with the first RLC entity.

- Otherwise, if the sending PDCP entity has been associated with two RLC entities (or associated with two logical channels), a PDCP redundancy transmission (pdcpDuplication) has been configured and activated, and the different logical channels for redundant transmission are the same MAC entity The terminal (PDCP entity of the terminal) indicates the PDCP data volume as a corresponding MAC entity for each of the two logical channels associated with the corresponding MAC entity. Or the terminal (PDCP entity of the terminal) indicates twice the volume of the PDCP data to the corresponding MAC entity. Alternatively, the terminal indicates two logical channel identification information and a PDCP data volume associated with the corresponding MAC entity to the corresponding MAC entity. Or the terminal (PDCP entity of the terminal) indicates the PDCP data volume with the corresponding MAC entity. Or the terminal (PDCP entity of the terminal) directs the PDCP data volume of the first logical channel associated with the first RLC entity to the associated MAC entity and associates the PDCP data volume of the second logical channel associated with the second RLC entity Indicate to the MAC entity. At this time, the terminal (PDCP entity of the terminal) calculates the BSR buffer size including the corresponding PDCP data ballroom for each of the two logical channels associated with each other.

- Otherwise, if the sending PDCP entity has been associated with two RLC entities (or associated with two logical channels), PDCP duplicated transmission (pdcpDuplication) has been configured and activated, but the different logical channels for redundant transmission are different MAC entities The terminal (PDCP entity of the terminal) directs the PDCP data volume to both the MCG MAC entity and the SCG MAC entity (both the MCG MAC entity and the SCG MAC entity). Or the terminal (PDCP entity of the terminal) directs the data volume of the first logical channel associated with the first RLC entity to the associated first MAC entity and the data volume of the second logical channel associated with the second RLC entity to the associated To the second MAC entity.

- Alternatively, if the transmitting PDCP entity is associated with two RLC entities (or associated with two logical channels), and PDCP redundancy transmission (pdcpDuplication) is configured but not activated, then a different logical channel for redundant transmission If included in the same MAC entity, the terminal (PDCP entity of the terminal) directs the PDCP data volume to the corresponding MAC entity. Or the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MCG MAC entity. Or the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity associated with the first RLC entity. Or the terminal (PDCP entity of the terminal) indicates the PDCP data volume as a corresponding MAC entity for one logical channel associated with the corresponding MAC entity.

- when the transmitting PDCP entity is associated with two RLC entities (or associated with two logical channels), and the PDCP redundancy transmission (pdcpDuplication) is configured but not activated, the different logical channels for the redundant transmission are different MAC entities The terminal (PDCP entity of the terminal) instructs the PDCP data volume to the corresponding MAC entity. Or the terminal indicates the PDCP data volume to the MCG MAC entity. Or the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity associated with the first RLC entity.

- if the sending PDCP entity is associated with two RLC entities (or associated with two logical channels), if PDCP duplication transmission (pdcpDuplication) is not configured and if all two pending RLC entities If the PDCP data volume and the RLC data volume are less than the uplink data separation threshold (ul-DataSplitThreshold) (or if the PDCP data volume is less than the uplink data separation threshold (ul-DataSplitThreshold)), Entity) indicates the PDCP data volume to the corresponding MAC entity. Or the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity configured as an uplink path. Or the terminal (PDCP entity of the terminal) directs the PDCP data volume to the associated MAC entity. Or the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity associated with the associated RLC entity. Or the terminal (PDCP entity of the terminal) directs the PDCP data volume to the MAC entity including the associated logical channel. The terminal (PDCP entity of the terminal) indicates the PDCP data volume as a MAC entity associated with the first RLC entity.

The terminal (PDCP entity of the terminal) instructs the PDCP data volume to be 0 with another MAC entity. Or the terminal (PDCP entity of the terminal) indicates the PDCP data volume as 0 with the MAC entity associated with the second RLC entity.

- if the sending PDCP entity is associated with two RLC entities (or associated with two logical channels), if PDCP duplication transmission (pdcpDuplication) is not configured and if all two pending RLC entities (PDCP entity) of the UE if the PDCP data volume and the RLC data volume are larger than the uplink data separation threshold (ul-DataSplitThreshold) (or if the PDCP data volume is larger than the uplink data separation threshold (ul-DataSplitThreshold) Indicates the PDCP data volume to the MCG MAC entity and the SCG MAC entity (both the MCG MAC entity and the SCG MAC entity). The terminal (PDCP entity of the terminal) indicates the PDCP data volume as a MAC entity associated with the first RLC entity and a MAC entity associated with the second RLC entity.

As described above, according to the present embodiment, when a UE is configured or activated by redundant transmission through a CA by a single base station with respect to a specific bearer, effectively providing buffer status reporting of the UE enables the base station to efficiently allocate uplink resources As shown in FIG.

Hereinafter, a terminal and a base station apparatus capable of performing a part or all of the embodiments described with reference to Figs. 1 to 17 will be described with reference to the drawings.

18 is a diagram illustrating a terminal configuration according to an embodiment.

Referring to FIG. 18, a terminal 1800 that constitutes a carrier merging and transmits a buffer status report includes a receiver 1830 that receives upper layer signaling including information for configuring data redundancy transmission through carrier merging from a base station A plurality of RLC entities including a first RLC entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity based on upper layer signaling, A control unit 1810 for configuring a logical channel associated with a first RLC entity and a logical channel associated with a second RLC entity in a control object, and a control unit 1810 for configuring a PDCP data volume to logical And a transmitter 1820 for transmitting a buffer status report configured to be included in both the channel group and the logical channel group associated with the second RLC entity to the base station The.

For example, the receiver 1830 may configure a carrier merging with one base station and may receive an RRC message including additional RLC configuration information for duplicating the same data over the plurality of carriers to the base station using carrier merging have. For example, the information for configuring the redundant transmission includes information on a plurality of RLC entities configured in the UE, logical channel information associated with each RLC entity, information on each RLC entity and one PDCP Information for association of objects, and MAC entity configuration information for redundant transmission.

In addition, the controller 1810 may configure an additional RLC entity in the UE based on information for configuring the received redundant transmission. A plurality of RLC entities may be configured according to the configuration of the base station. The control unit 1810 may configure the first RLC entity and the second RLC entity in association with one PDCP entity according to the higher layer signaling. In addition, the controller 1810 can configure a logical channel in association with the RLC entity to identify RLC entities added to one MAC entity. That is, the controller 1810 may configure the MAC entity with a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity. In this way, the MAC entity maps the data transmitted and received through one radio bearer to each logical channel and processes the PDCP data by duplicating the PDCP data to the BS through the plurality of RLC entities, and transmits the redundantly received data to the PDCP entity It can also be delivered over each logical channel.

The transmitter 1820 can transmit the MAC entity to each of the logical channels associated with the first RLC entity and the data transmitted through the logical channel associated with the second RLC entity to the base station via different carriers. The first RLC entity and the second RLC entity may be configured in association with different logical channels based on logical channel identifiers. Alternatively, the first RLC entity and the second RLC entity may be configured in association with one PDCP entity based on the radio bearer identifier.

The transmitter 1820 can transmit the buffer status report to the base station according to the buffer status report trigger condition when the redundant transmission configuration such as a plurality of RLC entities is completed and the data redundancy transmission function is activated. However, even if the terminal is configured for redundant transmission, the redundant transmission function may not be activated depending on the setting. In this case, the activation of the data redundancy transmission may be indicated through a separate signal from the base station. For example, a signal for activation of a redundant transmission may be directed from a base station via a MAC control element for each data radio bearer. That is, the BS can activate or deactivate the redundancy transmission function configured for the UE through the MAC control element for each radio bearer.

In addition, the controller 1810 may set the PDCP data volume to be included in both the logical channel group associated with the first RLC entity and the logical channel group associated with the second RLC entity. In this case, the transmitter 1820 can transmit a buffer status report including buffer information of each logical channel group to the base station. That is, the PDCP data volume can be set to be included in all the logical channel groups associated with each RLC entity.

In addition to this, the control unit 1810 can process the information for configuring the redundant transmission or the information for activating the redundant transmission or the data for the redundant transmission.

In addition to this, the control unit 1810 controls the overall terminal (hereinafter, referred to as " BS ") to process the buffer status report by repeatedly transmitting and receiving data through a plurality of carriers, 1800). The receiving unit 1830 receives the downlink control information, data, and a message from the base station through the corresponding channel, and the transmitting unit 1820 transmits the uplink control information, data, and a message to the base station through the corresponding channel.

19 is a diagram illustrating a base station configuration according to an embodiment.

19, a base station 1900 configured to merge carriers into a UE and receive a buffer status report includes a controller 1910 for generating information for configuring data redundancy transmission through carrier merging, A transmitter 1920 for transmitting upper layer signaling including information for configuring data redundancy transmission, and a second RLC entity 1920 for transmitting a logical channel group associated with a first RLC entity of the UE, And a receiving unit 1930 receiving the buffer status report including the PDCP data volume of the UE set to be included in all logical channel groups associated with the logical channel group.

For example, the information for configuring the redundant transmission includes information on a plurality of RLC entities configured in the UE, logical channel information associated with each RLC entity, information on each RLC entity and one PDCP Information for association of objects, and MAC entity configuration information for redundant transmission.

The transmitting unit 1920 can transmit information for configuring the single base station based redundant transmission of the above-described terminal through higher layer signaling such as an RRC message.

As described above, the UE receives the information for configuring the redundant transmission and generates a first RLC (Radio Link Control) entity associated with one PDCP (Packet Data Convergence Protocol) entity and a plurality of RLC And configures a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity in one Medium Access Control (MAC) entity.

When the data redundancy transmission of the MS is activated, the receiver 1930 can receive the data transmitted in association with each logical channel of the MS through the different carriers. That is, the receiving unit 1930 can receive the same data redundantly through different carriers. Here, the different carriers may be the carriers constituting the CA of the terminal.

The buffer status report may include a PDCP data volume for each logical channel group. To do so, the terminal may assign a PDCP data volume to both logical channel groups associated with the first RLC entity and logical channel groups associated with the second RLC entity To the base station. That is, the PDCP data volume may be received in all logical channel groups associated with each RLC entity.

Meanwhile, the transmitter 1920 may transmit information indicating that the data redundancy transmission of the UE is activated through the MAC Control Element for each data radio bearer. For example, a signal for activation of a redundant transmission may be directed to a terminal through a MAC control element for each data radio bearer.

In addition, the control unit 1910 transmits and receives the same data over a plurality of carriers through a plurality of carriers from a terminal constituting a single base station-based CA according to the above-described embodiments, and receives a buffer status report accordingly To control the operation of the overall base station 1900. The transmission unit 1920 and the reception unit 1930 are used to transmit and receive signals, messages, and data necessary for performing the above-described embodiments to and from the terminals.

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

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

Claims (22)

A method for transmitting a buffer status report by a terminal constituting a carrier merge,
Receiving higher layer signaling including information for configuring data redundancy transmission through carrier merging from a base station;
A plurality of RLC entities including a first RLC entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity based on the higher layer signaling,
Configuring a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity in a Medium Access Control (MAC) entity; And
When the data redundancy transmission is activated, a buffer status report configured by setting a PDCP data volume to be included in both a logical channel group associated with the first RLC entity and a logical channel group associated with the second RLC entity is transmitted to the base station ≪ / RTI > The method according to claim 1,
Wherein the one MAC entity comprises:
Wherein the RLC entity transmits data through a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity to the base station via different carriers. The method according to claim 1,
The activation of the data redundancy transmission is performed by,
And is instructed from the base station through a MAC control element for each data radio bearer. The method according to claim 1,
Wherein the first RLC entity and the second RLC entity,
And is associated with a different logical channel based on a logical channel identifier. The method according to claim 1,
The PDCP control PDU included in the PDCP data volume includes:
Wherein the RLC entity is configured to be included only in a logical channel group associated with the first RLC entity. A method for receiving a buffer status report by a base station that constitutes a carrier merging in a terminal,
Generating information for configuring data redundancy transmission through carrier merging;
Transmitting an upper layer signaling including information for configuring data redundancy transmission through the carrier merging to a terminal; And
When the data redundancy transmission of the UE is activated, the PDCP data volume of the UE set to be included in both the logical channel group associated with the first RLC entity of the UE and the logical channel group associated with the second RLC entity of the UE, ≪ / RTI > comprising: receiving a buffer status report including a buffer status report; The method according to claim 6,
The information for configuring the data redundant transmission includes:
Wherein the UE is configured to associate the first RLC entity and the second RLC entity with one PDCP entity,
And a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity in one MAC entity configured in the UE. 8. The method of claim 7,
Wherein the first RLC entity and the second RLC entity,
And is associated with a different logical channel based on a logical channel identifier. 8. The method of claim 7,
The PDCP control PDU included in the PDCP data volume includes:
Wherein the RLC entity is configured to be included only in a logical channel group associated with the first RLC entity. The method according to claim 6,
Prior to the step of receiving the buffer status report,
And transmitting information indicating that the data redundancy transmission of the UE is activated through a MAC Control Element for each data radio bearer. The method according to claim 6,
The base station comprises:
Wherein the logical channel associated with the first RLC entity and the data transmitted through the logical channel associated with the second RLC entity are received through different carriers. A terminal for transmitting a buffer status report by configuring a carrier merging,
A receiver for receiving upper layer signaling including information for configuring data redundancy transmission through carrier merging from a base station;
A plurality of RLC entities including a first RLC entity and a second RLC entity associated with one Packet Data Convergence Protocol (PDCP) entity based on the higher layer signaling,
A controller configured to configure a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity in a MAC (Medium Access Control) entity; And
When the data redundancy transmission is activated, a buffer status report configured by setting a PDCP data volume to be included in both a logical channel group associated with the first RLC entity and a logical channel group associated with the second RLC entity is transmitted to the base station And a transmitting unit for transmitting the data. 13. The method of claim 12,
Wherein the one MAC entity comprises:
Wherein the RLC entity transmits data to a base station through a different carrier, the data being transmitted through a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity. 13. The method of claim 12,
The activation of the data redundancy transmission is performed by,
And is instructed from the BS through a MAC control element for each data radio bearer. 13. The method of claim 12,
The PDCP control PDU included in the PDCP data volume includes:
Wherein the RLC entity is configured to be included only in a logical channel group associated with the first RLC entity. 13. The method of claim 12,
Wherein the first RLC entity and the second RLC entity,
And associating the PDCP entity with the one PDCP entity based on a radio bearer identifier. A base station configured to merge carriers into a terminal and receive a buffer status report,
A control unit for generating information for configuring data redundancy transmission through carrier merging;
A transmitter for transmitting upper layer signaling including information for configuring data redundancy transmission through the carrier merging to a terminal; And
When the data redundancy transmission of the UE is activated, the PDCP data volume of the UE set to be included in both the logical channel group associated with the first RLC entity of the UE and the logical channel group associated with the second RLC entity of the UE, And a receiver for receiving a buffer status report including the received buffer status report. 18. The method of claim 17,
The information for configuring the data redundant transmission includes:
Wherein the UE is configured to associate the first RLC entity and the second RLC entity with one PDCP entity,
And a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity in one MAC entity configured in the UE. 19. The method of claim 18,
Wherein the first RLC entity and the second RLC entity,
And is configured to be linked to different logical channels based on logical channel identifiers. 19. The method of claim 18,
The PDCP control PDU included in the PDCP data volume includes:
And is included only in a logical channel group associated with the first RLC entity. 18. The method of claim 17,
The transmitter may further comprise:
And further transmits information indicating that the data redundancy transmission of the UE is activated through a MAC control element for each data radio bearer. 18. The method of claim 17,
The receiver may further comprise:
Wherein the RLC entity receives data transmitted through a logical channel associated with the first RLC entity and a logical channel associated with the second RLC entity through different carriers.

Images