KR20160110617A - Methods and apparatus for PUCCH SCell control in LTE - Google Patents

Abstract

In providing carrier aggregation (CA) or dual connectivity (DC) in E-UTRAN, the present invention relates to a method and an apparatus for performing transmission of PUCCH related to activation or inactivation of SCell when forming PUCCH through the SCell.

Description

[0001] PUCCH SCELL CONTROL METHOD AND APPARATUS [0002]

The present invention relates to a method and an apparatus for controlling CSI reporting via a PUCCH SCELL when constructing a PUCCH via a SCELL in providing CA (Carrier Aggregation) in the E-UTRAN or providing DC (Dual Connectivity) will be.

The present invention provides a method and apparatus for transmitting a CSI report in a method for transmitting a CSI report in a SCell, and transmitting CSI report in accordance with a priority process of a SCell for the PUCCH transmission do.

1 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
2 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.

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

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

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

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

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

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

Since the various cells listed above exist in the base station controlling each cell, the base station can be interpreted into two meanings. i) a device itself providing a megacell, a macrocell, a microcell, a picocell, a femtocell, or a small cell in relation to a wireless region, or ii) 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 megacell, a macrocell, a microcell, a picocell, a femtocell, a small cell, an RRH, an antenna, an RU, a low power node (LPN), a point, an eNB, Quot;

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

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

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

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

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

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

The wireless communication system to which the embodiments are applied may be a coordinated multi-point transmission / reception system (CoMP system) or a coordinated multi-point transmission / reception system in which two or more transmission / reception points cooperatively transmit signals. antenna transmission system, or a cooperative multi-cell communication system. A CoMP system may include at least two multipoint transmission / reception 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 multiplex transmission / reception point to a terminal, and an uplink refers to a communication or communication path from a terminal to a multiplex 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.

The CA technology started with 3GPP Rel-10 added multiple UL timing advance in Rel-11, dual connectivity (DC) in Rel-12 and FDD-TDD CA technology. However, prior CA-related technologies (CA, DC, etc.) prior to Rel-12 were able to aggregate up to five carriers into the UE.

Recently, 3GPP Rel-13 proposed a LTE (Licensed-Assisted Access) that utilizes the license-free frequency band as one of measures to cope with the explosion of mobile data traffic. Based on CA technology (or CA related technology), we are studying all the necessary information to use unlicensed spectrum of 5GHz band.

For LTE, aggregation for five or more carriers may be required to enable bandwidth utilization similar to at least IEEE 802.11ac Wave 2 through the LAA. In addition to the bands already used for LTE, other frequency bands such as 3.5GHz may be used for more than five carrier aggregations. By extending the CA technology to aggregation using more than five carriers, the operator has the opportunity to more efficiently use the available spectrum for communication demand.

However, as the number of CA capable terminals and aggregated CCs increase, the cells used as PCells can cause very high load. This may be one of the major functions that apply only to the PCell, PUCCH transmission. For the reference, UEs feedback UCI (SR, HARQ-ACK, CSI) related to MCG (Master Cell group) in conventional DC can be transmitted only to MeNB and UEs feedback UCI (SR, HARQ-ACK , CSI) can only be transmitted to SeNB. In the MCG, the PUCCH for the MCG is supported only in the PCell, and the PUCCH for the SCG in the SCG can be supported only in the PSCell.

Accepting all PUCCH transmissions in PCell can have a significant impact on the performance of CA terminals as well as non-CA terminals.

As a method for solving this, a method of providing PUCCH on SCell can be considered. For example, the UE may transmit UCI (e.g., HARQ-ACK, CSI reporting, HARQ-ACK, CSI reporting, SR, etc.) through SCell providing PUCCH. Here, CSI (Channel State Information) reporting indicates CQI (Channel Quality Indicator) / PMI (Precoding Matrix Indicator) / PTI (Precoding Type Indicator) / RI (Rank Indicator) reporting by the base station. (Or the CSI report may be composed of CQI / PMI / PTI / RI controlled by the base station).

However, there is no specific procedure for providing the PUCCH on the SCell which is considered as a method for distributing the PUCCH transmission load.

Hereinafter, a case where one SCell is provided with a PUCCH will be described for convenience of explanation. This is for convenience of explanation, and the present invention can be equally applied to a case where one or more SCells are provided with a PUCCH.

For example, if a PUCCH is provided on one of the SCells in addition to PCell for the CA, then the SCells will use the PCell to select a group of cells providing the PUCCH (hereinafter referred to as the PCell PUCCH group for convenience) May belong to one PUCCH group among a group of cells providing a PUCCH (hereinafter referred to as a SCELL PUCCH group for convenience of explanation). That is, when PUCCH is provided on SCell of one SCell in addition to PCell for CA, all CCs are assigned to PCell PUCCH group providing PUCCH through PCell and PUCCH group of SCell PUCCH group providing PUCCH through SCell Belongs.

Hereinafter, the SCell providing the PUCCH is referred to as the PUCCH SCell for convenience of explanation. This is for the convenience of explanation, SCell which provides PUCCH, SCell which supports PUCCH, SCell which carries PUCCH, SCell which carries PUCCH, and PUCCH when MCG or PUCCH are provided in two or more cells in SCG SCELL provided, PUCCH provided for CA, SCell, etc.).

The mapping between the PUCCH SCell and other SCells belonging to the PUCCH SCell can be configured by the RRC.

PUCCH SCell is also a sort of SCell. Therefore, the PUCCH SCell can also be provided with activation / deactivation that is used by the CA to reduce the terminal power consumption.

The existing 3GPP TS 36.321 MAC standard according to the prior art is as follows.

The MAC entity must do for each TTI and each configured SCell:

- If the MAC entity receives an enable / disable MAC control element that activates the SCell in this TTI, the MAC entity shall do the following in the TTI according to the timing defined in 3GPP TS 36.213:

- Activate SCell: (normal SCell operation applied)

- Start or restart the SCellDeactivationTimer associated with SCell:

(The MAC entity shall for each TTI and for each configured SCell:

- If the MAC entity receives an activation / deactivation MAC control element in this TTI activating the SCI, the MAC entity shall in accordance with the TTI defined in [TS 36.213]:

- activate the SCell; i.e. apply normal SCell operation including:

- start or restart the SCellDeactivationTimer associated with the SCell;

The normal SCell operation here includes:

- SRS transmission on SCELL; CQI / PMI / RI / PTI reporting for SCell; PDCCH monitoring on SCell; PDCCH monitoring for the SCELL (PDCCH monitoring for the SCell).

If activation / deactivation is provided to the PUCCH SCell, the UE (or base station) must operate according to the timing for SCell activation / deactivation of the existing 3GPP TS 36.213 for PUCCH SCell as described above.

The above-mentioned timing related standards of the existing 3GPP TS 36.213 are as follows.

When a terminal receives an activation command for a secondary cell in subframe n, the corresponding actions are applied to subframe n + 8, with the exception of the minimum requirements defined in 3GPP TS 36.133, It should be applied not too late and not faster than sub-frame n + 8.

Actions related to -CSI reporting

- actions associated with the sCellDeactivationTimer associated with the secondary cell

(When a UE receives an activation command for a secondary cell in a subframe n, the corresponding actions in [36.321] will be applied no later than the minimum requirement defined in [36.133] and no earlier than subframe n + 8, except for the following :

- the actions related to CSI reporting

- the actions related to the sCellDeactivationTimer associated with the secondary cell [36.321]

which will be applied in subframe n + 8. )

When the UE receives an activation command for the secondary cell in subframe n or when the sCellDeactivationTimer associated with the secondary cell expires in subframe n, it is associated with CSI reporting that should be applied to subframe n + 8 Shall be applied no later than the minimum requirements defined in 3GPP TS 36.133, except for the actions. [36.321] When a UE receives a deactivation command for a secondary cell or the secondary cell expires in subframe n, the corresponding action in [36.321] shall be no later than the minimum requirement defined in [36.133], except for the actions related to CSI reporting which will be applied in subframe n + 8.

The minimum requirements defined in 3GPP TS36.133 are as follows.

For the SCell activation delay requirement, if the terminal sends a valid measurement report during the same period as max (5 measCycleSCell, 5 DRX cycles) before receiving the SCell activation command and the SCell remains in a detectable state, it is later than subframe n + 24 Otherwise, the terminal must be able to apply the operation no later than subframe n + 34. (Upon receiving SCELL activation command in subframe n, the UE shall be able to transmit valid CSI report and apply actions as specified for the SCELL being activated no later than subframe n + 24) the SCell:

- During the period equal to max (5 measCycleSCell, 5 DRX cycles) before the reception of the SCell activation command:

- The UE has sent a valid measurement report for the SCell being activated and

- the SCell being activated remains detectable according to the cell identification conditions specified in section 8.3.3.2,

- SCELL being activated also remains detectable during the SCELL activation delay according to 8.3.3.2.

If the SCell activation command in subframe n, the UE shall be able to transmit valid CSI report and apply actions related to the activation command for the SCELL being activated no later than subframe n + the first attempt.)

In case of the SCell deactivation delay requirement, the UE should operate no later than n + 8.

(Upon receiving the SCell deactivation command or upon expiration of the SCellDeactivationTimer in subframe n, the UE shall perform the deactivation actions for the SCell being deactivated no later than subframe n + 8.

In the prior art, if the UE is composed of more than one serving cell, the UE transmits only one serving cell's CSI report in any given subframe. (If the UE is configured with more than one serving cell, the UE transmits a CSI report of only one serving cell in any given subframe.

For example, for a given subframe, the CSI report with a serving cell's PUCCH reporting type 3, 5, 6 or 2a and the PUCCH report type 1, 1a, 2b, 2c or 4 of another serving cell CSI report with a PUCCH report type of 1, 1a, 2, 2b, 2c or 4 is dropped with a lower priority if it has a collision on a CSI report with a lower priority (for a given subframe). PUCCH reporting type 3, 5, 6, or 2a of one serving cell with a CSI report with PUCCH reporting type 1, 1a, 2b, 2c, 1a, 2, 2b, 2c, or 4) has lower priority and is dropped.

For another example, for a given subframe, if the CSI report with PUCCH reporting type 2, 2b, 2c or 4 of one serving cell and the CSI report with PUCCH report type 1, 1a of another serving cell are collisions, A CSI report with a PUCCH report type of 11a is dropped with a lower priority. (For a given subframe, a CSI report with PUCCH reporting type 2, 2b, 2c, or 4 of one serving cell with CSI report with PUCCH reporting type 1 or 1a of another serving cell, the latter report with PUCCH reporting type 1, or 1a has lower priority and is dropped.

For another example, if there is a collision between the serving cells having the UEs configured in transmission mode 1-9 and the CSI reports of different serving cells with a PUCCH reporting type of the same priority for a given subframe, The CSI report for all these serving cells except the serving cell with the ServCellIndex is dropped. (For a given subframe and serving cells with UEs in transmission mode 1-9, with PUCCH reporting type of the same priority, the CSI reports for all these serving cells except the ServCellIndex are dropped.)

For another example, for a given subframe with serving cells having a UE configured in transmission mode 10, different serving with a CSI report corresponding to a CSI process with the same priority PUCCH reporting type and csi-ProcessId- If there is a collision between the CSI reports of the cells, the CSI report for all these serving cells except for the serving cell with the smallest ServCllIndex is dropped. (For a given subframe and serving cells with UE configured in transmission mode 10, and the CSI reports of the same priority and the CSI reports corresponding to the CSI processes with the same CSI-ProcessId-r11, the CSI reports of all the serving cells except the ServCellIndex are dropped.)

For another example, for serving cells with a UE configured in transmission mode 10 and for a given subframe, different PUCCH reporting types and CSI reports corresponding to CSI processes with different csi-ProcessId- If a collision occurs between the CSI reports of the serving cells, the CSI report for all such serving cells is dropped except for the serving cell with the CSI report corresponding to the CSI process with the smallest csi-ProcessId-r11. a given subframe and serving cell with UE configured in transmission mode 10, in case of collision between CSI reports of different serving cells with PUCCH reporting type of same priority and the CSI reports corresponding to CSI processes with different csi-ProcessId-r11, the CSI reports of all the serving cells except the serving cell with CSI reports corresponding to CSI process with the lowest csi-ProcessId-r11 are droppe d.)

For another example, for a given subframe, a CSI report of a given serving cell with a UE configured in transmit mode 1-9, and a CSI report (s) corresponding to the CSI process (s) of another serving cell with a UE configured in transmit mode 10 (S) corresponding to the CSI process (s) having csi-ProcessId-r11 > 1 in another serving cell, if a collision occurs between the serving cell's CSI reports having the same priority PUCCH reporting type (S) are dropped. (For a given subframe, the CSI report of a given serving cell with the UE is configured in transmission mode 1-9, and CSI report (s) corresponding to CSI process (CSI) process with csi-process-id 11, and the CSI report of the serving cell with the same priority, the CSI report of the different serving ce ll are dropped.)

For another example, for a given subframe, a CSI report of a given serving cell with a UE configured in transmit mode 1-9 and a CSI process with csi-ProcessId-r11 = 1 of another serving cell with a UE configured in transmit mode 10 The corresponding CSI report of the serving cell with the highest ServCellIndex is dropped when a collision occurs between the CSI report corresponding to the serving cell and the CSI reports of the serving cell having the same priority PUCCH reporting type.

When CSI reporting is transmitted via PUCCH SCell, collision may occur between CSI reporting of different serving cells. However, there has been a problem that the processing for this can not be performed effectively.

As described above, there is no specific procedure for providing the PUCCH on the SCell which is considered as a method for distributing the PUCCH transmission load. In particular, in the prior art, when a UE is configured with more than one serving cell, the UE transmits only one serving cell's CSI report in any given subframe. Therefore, when CSI reporting is transmitted through PUCCH SCELL, collision may occur between CSI reporting of different serving cells, and the priority of CSI reporting through PUCCH SCELL, which is a function of transmitting PUCCH, may not be considered effectively .

In order to solve the above problems, the present invention provides a method for solving collision of PUCCH CSI reporting by effectively considering CSI reporting through PUCCH SCell in providing CSI reporting by a UE configured to transmit PUCCH through SCell .

Hereinafter, for convenience of description, it is assumed that a CA is provided with a PUCCH in one SCell. The present invention is equally applicable to the case where the PUCCH is provided to one or more SCells in the CA or the PUCCH is provided in the MCG or in the SCG through one or more cells.

CSI reporting is periodic or aperiodic.

If the terminal is configured with more than one serving cell, the terminal transmits CSI only for the active serving cell (s).

If the terminal is not configured for simultaneous PUSCH and PUCCH transmission, the terminal transmits periodic CSI reporting on the PUCCH without PUSCH allocation.

In another example, if the UE is not configured for simultaneous PUSCH and PUCCH transmission, the UE transmits periodic CSI reporting on the PUCCH of the PUCCH SCELL with no PUSCH allocation for the SCells belonging to the SCELL PUCCH group.

If the UE is not configured for simultaneous PUSCH and PUCCH transmission, the UE transmits periodic CSI reporting on the PUSCH of the serving cell having the smallest ServCellIndex in the subframe having the PUSCH allocation.

In another example, if the UE is not configured for simultaneous PUSCH and PUCCH transmission, the UE may send periodic CSI reporting on the PUSCH of the serving cell that provides the PUCCH SCell in the subframe with the PUSCH allocation.

As another example, if the UE is not configured for simultaneous PUSCH and PUCCH transmission, the UE transmits periodic CSI reporting on the PUSCH of the serving cell that provides the PUCCH SCell to the subframe having the PUSCH allocation for the SCells belonging to the SCell PUCCH group .

If the specified conditions are met, the terminal sends aperiodic CSI reporting on the PUSCH.

If both periodic CSI reporting and aperiodic CSI reporting occur in the same subframe, the terminal transmits only the aperiodic CSI report to that subframe.

As another example, if both the periodic CSI reporting of the SCELL PUCCH group and the aperiodic CSI reporting of the PCELL PUCCH group occur in the same subframe, the terminal transmits only the aperiodic CSI report to that subframe.

As another example, if both the periodic CSI reporting of the SCELL PUCCH group and the aperiodic CSI reporting of the PCELL PUCCH group occur in the same subframe, the UE transmits only the periodic CSI report of the SCELL PUCCH group to that subframe.

When decoding the uplink DCI format 4 or random access response grant in subframe n, the terminal uses the PUSCH in the n + k subframe on the serving cell c, if the CSI request field is set and not scheduled to trigger the report You should perform aperiodic CSI reporting.

The UE is configured semi-static by the upper layer to periodically feed back different CSI elements (CQI, PMI, PTI, and / or RI) on the PUCCH using the reporting mode specified in 3GPP TS 36.213.

The following CQI / PMI and RI reporting types with Distinct period and offset are supported for PUCCH CSI reporting mode as specified in TS 36.213.

- Type 1 report supports CQI feedback for the UE selected sub-bands

- Type 1a report supports subband CQI and second PMI feedback

- Type 2, Type 2b, and Type 2c report supports wideband CQI and PMI feedback

- Type 2a report supports wideband PMI feedback

- Type 3 report supports RI feedback

- Type 4 report supports wideband CQI

- Type 5 report supports RI and wideband PMI feedback

- Type 6 report supports RI and PTI feedback

In the prior art, if the UE is composed of more than one serving cell, the UE transmits only one serving cell's CSI report in any given subframe. If a PUCCH SCELL is configured, a problem may arise in the prior art. To solve this problem, the following methods can be used.

When a CSI report of one serving cell is transmitted within a subframe, priority processing

If a terminal is composed of more than one serving cell, the terminal transmits only one serving cell's CSI report in any given subframe. If there is a collision in the CSI report within a given subframe, a CSI report with a PUCCH reporting type of PUCCH SCell, or a CSI report with a PUCCH SCell, a CSI report with a PUCCH reporting type of PUCCH SCell Alternatively, the CSI report of the PUCCH SCell can be processed first.

Or, if there is a collision on the CSI report within a given subframe, if it has a CSI report with a PUCCH reporting type of PUCCH SCELL, or if it has a CSI report of a PUCCH SCELL, and if it has a PCUC PUCCH reporting type If you do not have a CSI report, or you do not have a PCSI CSI report, you can preferentially process a CSI report with a PUCCH SCELL CSI report or a PUCCH SCELL PUCCH reporting type during a collision.

For example, for a given subframe, the CSI report with a serving cell's PUCCH reporting type 3, 5, 6 or 2a and the PUCCH report type 1, 1a, 2b, 2c or 4 of another serving cell The CSI report with PUCCH report type 1, 1a, 2, 2b, 2c or 4 drops with a low priority.

For another example, for a given subframe, if the CSI report with PUCCH reporting type 2, 2b, 2c or 4 of one serving cell and the CSI report with PUCCH report type 1, 1a of another serving cell are collisions, A CSI report with a PUCCH report type of 1,1a drops with a low priority.

For another example, if there is a collision between the serving cells having the UEs configured in transmission mode 1-9 and the CSI reports of different serving cells with a PUCCH reporting type of the same priority for a given subframe, The CSI report for all these serving cells except the serving cell with ServCellIndex is dropped.

For another example, if a collision occurs between the serving cells with the UEs configured in transmission mode 1-9 and the CSI reports of different serving cells with a PUCCH reporting type of the same priority for a given subframe, If a small ServCellIndex is not 0 (i.e. PCell) and there is a CSI report of a PUCCH SCell in the collision, all of the serving cells except for the serving cell that is the PUCCH SCell (except for the CSI report of the PUCCH SCell) The report is dropped.

For another example, for a given subframe with serving cells having a UE configured in transmission mode 10, different serving with a CSI report corresponding to a CSI process with the same priority PUCCH reporting type and csi-ProcessId- If a collision occurs between the CSI reports of the cells, the CSI report for all such serving cells except the serving cell with the smallest ServCellIndex is dropped.

For another example, for a given subframe with serving cells having a UE configured in transmission mode 10, different serving with a CSI report corresponding to a CSI process with the same priority PUCCH reporting type and csi-ProcessId- If there is a collision between the CSI reports of the cells, if the smallest ServCellIndex is not 0 (i.e. PCell) and there is a CSI report of the PUCCH SCell during the collision, the serving cell excluding the PUCCH SCell (i.e., Except for the CSI report), the CSI report for all these serving cells is dropped.

For another example, for serving cells with a UE configured in transmission mode 10 and for a given subframe, different PUCCH reporting types and CSI reports corresponding to CSI processes with different csi-ProcessId- If a collision occurs between the serving cell's CSI reports, the CSI report for all such serving cells is dropped except for the serving cell with the CSI report corresponding to the CSI process with the smallest csi-ProcessId-r11.

For another example, for a given subframe, a CSI report of a given serving cell with a UE configured in transmit mode 1-9, and a CSI report (s) corresponding to the CSI process (s) of another serving cell with a UE configured in transmit mode 10 (S) corresponding to the CSI process (s) having csi-ProcessId-r11 > 1 in another serving cell, if a collision occurs between the serving cell's CSI reports having the same priority PUCCH reporting type (S) are dropped.

For another example, for a given subframe, a CSI report of a given serving cell with a UE configured in transmit mode 1-9 and a CSI process with csi-ProcessId-r11 = 1 of another serving cell with a UE configured in transmit mode 10 The corresponding CSI report of the serving cell with the highest ServCellIndex is dropped when a collision occurs between the CSI report corresponding to the serving cell and the CSI reports of the serving cell having the same priority PUCCH reporting type.

For another example, for a given subframe, a CSI report of a given serving cell with a UE configured in transmit mode 1-9 and a CSI process with csi-ProcessId-r11 = 1 of another serving cell with a UE configured in transmit mode 10 If the collision occurs between the CSI reports corresponding to the PUCCH report type and the serving cell having the same priority PUCCH reporting type, if the smallest ServCellIndex is not 0 (i.e. PCell) and the PUCCH SCell The CSI report for all these serving cells is dropped except for the Serving Cell with the highest ServCllIndex of the CSI report, except for the Serving Cell which is the PUCCH SCell (i.e. excluding the CSI report of the PUCCH SCell).

Within the subframe, two Of the serving cell CSI  How to Send a Report

When the PUCCH SCell is configured, if the UE is configured with more than one serving cell, the UE transmits only one serving cell's CSI report in the PCell PUCCH group in any given subframe.

When the PUCCH SCell is configured, if the UE is configured with more than one serving cell, the UE transmits only one serving cell's CSI report in the SCELL PUCCH group in any given subframe.

For example, if a PUCCH SCell is configured, within a SCELL PUCCH group, for a given subframe, a CSI report with a serving cell's PUCCH reporting type 3, 5, 6 or 2a and a PUCCH report type 1 , The CSI report with PUCCH report type 1, 1a, 2, 2b, 2c or 4 drops with a lower priority if it is a collision on a CSI report with 1a, 2, 2b, 2c or 4

For another example, if a PUCCH SCell is configured, within a SCELL PUCCH group, for a given subframe, a CSI report with a serving cell's PUCCH reporting type 2, 2b, 2c, or 4 and a PUCCH report type 1 , Collision on CSI report with 1a, CSI report with PUCCH report type 1, 1a is dropped with low priority.

For another example, if a PUCCH SCell is configured, for a given subframe, in a SCell PUCCH group, for serving cells with a UE configured in transmission mode 1-9, and for a given subframe, If a collision occurs between CSI reports of different serving cells, the CSI report for all such serving cells except the serving cell with the smallest ServCellIndex is dropped.

For another example, if a PUCCH SCell is configured, for a given subframe, in a SCell PUCCH group, for serving cells with a UE configured in transmission mode 1-9, and for a given subframe, If a collision occurs between CSI reports of different serving cells, the CSI report for all such serving cells except the serving cell with PUCCH SCell is dropped.

For another example, if a PUCCH SCELL is configured, in a SCELL PUCCH group, for a given subframe and a serving cell having a UE configured in the transmission mode 10, a PUCCH reporting type with the same priority and a CSI with the same csi-ProcessId- If a collision occurs between CSI reports of different serving cells with a CSI report corresponding to the process, the CSI report for all such serving cells is dropped except for the serving cell with the smallest ServCellIndex.

For another example, if a PUCCH SCELL is configured, in a SCELL PUCCH group, for a given subframe and a serving cell having a UE configured in the transmission mode 10, a PUCCH reporting type with the same priority and a CSI with the same csi-ProcessId- If a collision occurs between CSI reports of different serving cells with a CSI report corresponding to the process, the CSI report for all such serving cells except the serving cell with the PUCCH SCell is dropped.

For another example, if the PUCCH SCell is configured, within the SCell PUCCH group, for serving cells with given UEs configured in transmission mode 10, and for a given subframe, with a PUCCH reporting type of the same priority and a different csi-ProcessId- If a collision occurs between CSI reports of different serving cells with a CSI report corresponding to the CSI process, then all such serving, except serving cells with a CSI report corresponding to the CSI process with the smallest csi-ProcessId- The CSI report for the cells is dropped.

For another example, if a PUCCH SCell is configured, within a SCELL PUCCH group, for a given subframe, a CSI report of a given serving cell with a UE configured in transmit mode 1-9 and another serving cell with a UE configured in transmit mode 10 Of the serving cell, if a collision occurs between the CSI report (s) corresponding to the CSI process (s) of the serving cell and the CSI reports of the serving cell having the PUCCH reporting type of the same priority, csi-ProcessId- The CSI report (s) corresponding to the CSI process (s) in question are dropped.

For another example, if a PUCCH SCell is configured, within a SCELL PUCCH group, for a given subframe, a CSI report of a given serving cell with a UE configured in transmit mode 1-9 and another serving cell with a UE configured in transmit mode 10 A collision occurs between the CSI reports corresponding to the CSI process (s) of csi-ProcessId-r11 = 1 of the serving cell and the CSI reports of the serving cell having the PUCCH reporting type of the same priority, The corresponding CSI report of the cell is dropped.

For another example, if a PUCCH SCell is configured, within a SCELL PUCCH group, for a given subframe, a CSI report of a given serving cell with a UE configured in transmit mode 1-9 and another serving cell with a UE configured in transmit mode 10 And a CSI report corresponding to the CSI process (s) having the csi-ProcessId-r11 = 1 of the same priority and a CSI report of the serving cell having the PUCCH reporting type having the same priority, a cell having no PUCCH SCell Is dropped.

How to assign a PUCCH SCELL with a lowest ceill index or a PUCCH SCELL

If a terminal is composed of more than one serving cell, the terminal transmits only one serving cell's CSI report in any given subframe. If there is a collision in the CSI report within a given subframe, a CSI report with PUCCH SCELL's PUCCH reporting type, or a PUCCH SCELL CSI report, then the PUCCH SCELL's CSI report can be processed first have.

In the existing specification, PCell has a ServCellIndex value set to 0. Therefore, when a collision occurs in some specific examples described above, PCell is preferentially processed when the PCell having the smallest ServCellIndex value is included in the collision. Likewise, the PUCCH SCell can be processed first after the PCell so that the lowest index is assigned to the PUCCH SCell, or the lowest index is given except for PCell.

Alternatively, the PUCCH SCell can be prioritized after the PCELL by indicating the configuration information that distinguishes the PUCCH SCELL from the normal SCELL through the RRC message.

(For example, SCell_PUCCH_ServCellIndex) used for distinguishing cells in the SCell PUCCH group through the RRC message, and configures this index (for example, SCell_PUCCH_ServCellIndex) to 0 for the PUCCH SCell, SCell can be processed first (or similar to PCell) after PCell (or the terminal can be considered to have the lowest index after PCell).

The embodiments described above in the present invention can be used individually or in combination.

The above-described embodiments of the present invention can be applied while the PUCCH SCell is configured. Or the above-described embodiments of the present invention may be applied while the PUCCH SCell is active. Or the above-described embodiments of the present invention can be applied until the PUCCH SCell is activated.

As described above, the present invention has an effect of effectively solving the collision of PUCCH CSI reporting considering priority of CSI reporting through PUCCH SCell in providing CSI reporting by a UE configured to transmit PUCCH through SCell.

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

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

The control unit 1010 effectively solves the collision of the PUCCH CSI reporting considering the CSI reporting through the PUCCH SCell in providing the CSI reporting by the UE configured to transmit the PUCCH through the SCell necessary for carrying out the present invention described above Thereby controlling the overall operation of the base station.

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

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

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

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

In addition, the control unit 1120 may consider the CSI reporting through the PUCCH SCell to be effective in the PUCCH CSI reporting in order to provide the CSI reporting by the UE configured to transmit the PUCCH through the SCell, And controls the overall operation of the terminal according to the resolution.

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

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

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

Claims (1)

A method for a terminal to transmit CSI reporting,
Configured to transmit a PUCCH in SCell; And
And transmitting CSI reporting according to priority processing of the SCell for the PUCCH transmission.

Images