KR20160116042A - PERIODIC CHANNEL STATE INFORMATION REPORTING FOR COORDINATED MULTIPOINT (CoMP) SYSTEMS - Google Patents

Abstract

A technique for periodic channel state information (CSI) reporting in cooperative multipoint (CoMP) scenarios is disclosed. One method may comprise a user equipment (UE) generating a plurality of CSI reports for transmission within a subframe for a plurality of CSI processes. Each CSI report can correspond to a CSI process with CSIProcessIndex. The UE may drop the CSI reports corresponding to the CSI processes except for the CSI process with the lowest CSIProcessIndex. The UE may send at least one CSI report for the CSI process to the evolved NodeB (eNB).

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates generally to cooperative multi-point (CoMP) systems,

Related Applications

The present application is filed on August 3, 2012, the priority of which is U.S. Provisional Patent Application Serial No. 61 / 679,627, attorney docket number P46630Z, which incorporates this patent application by reference.

Wireless mobile communication technologies use various standards and protocols for transferring data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device). Some wireless devices use orthogonal frequency-division multiple access (OFDMA) in downlink (DL) transmission and single carrier frequency division multiple access (OFDMA) in uplink (SC-FDMA). < / RTI > Standards and protocols that use orthogonal frequency-division multiplexing (OFDM) for a single transmission can be found in the third generation partnership project (3GPP) long term evolution (LTE) The groups are typically connected to the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standards (e.g., 802.16e, 802.16m) and industry groups, commonly known as Worldwide Interoperability for Microwave Access (WiMAX) Lt; RTI ID = 0.0 > WiFi. ≪ / RTI >

In 3GPP radio access network (RAN) LTE systems, a node is an evolved universal terrestrial radio access network (E-UTRAN) Node B (also commonly referred to as an evolved node (E. G., Bs, enhanced Node Bs, eNodeBs or eNBs) and a radio network controller (RNC) communicating with a wireless device known as user equipment . A downlink (DL) transmission may be a communication from a node (e.g., eNodeB) to a wireless device (e.g., UE), and an uplink (UL) transmission may be from a wireless device to a node.

In homogeneous networks, a node, referred to as a macro node, can provide basic wireless coverage to wireless devices in a cell. The cell may be an area and within which the wireless devices may operate to communicate with the macro node. Heterogeneous networks (HetNet) can be used to handle traffic loads on macro nodes that are increased by increasing use and functionality of wireless devices. HetNets include a layer of planned high power macro nodes (macro eNBs), on which the subnets that can be placed in a less than fully or even totally cooperative manner within the coverage area (cell) of the macro node Are covered with layers of power nodes (small-eNBs, micro-eNBs, pico-eNBs, femto-eNBs or home eNMs [HeNBs]). Lower power nodes (LPNs) may generally be referred to as "low power nodes ", small nodes, or small cells.

Macro nodes can be used for default coverage. Low power nodes can be used to fill the coverage holes to improve the boundaries between the coverage areas of macro nodes or in hot-zones, and to improve indoor coverage where the building structure interferes with signal transmission have. Inter-cell interference coordination (ICIC) or enhanced ICIC (eICIC) is a resource coordination scheme for reducing interference between nodes, such as macro nodes and low power nodes in HetNet. ). ≪ / RTI >

A Coordinated MultiPoint (CoMP) system can also be used to reduce interference from neighboring nodes in both homogeneous networks and HetNet. In a CoMP system, the nodes, also referred to as cooperating nodes, may also be grouped together with other nodes, in which nodes in a plurality of cells can transmit signals to and receive signals from the wireless device. The cooperating nodes may be nodes in a homogeneous network or macro nodes and / or lower power nodes (LPN) in HetNet. The CoMP operation is applicable to downlink transmissions and uplink transmissions. The downlink CoMP operation can be divided into two categories: co-ordinated scheduling or co-ordinated beamforming (CS / CB or CS / CBF) and joint processing or co- joint transmission (JP / JT). In the case of CS / CB, a given subframe may be transmitted from one cell to a given wireless device (e.g., a UE), and scheduling including cooperative beamforming may control interference between different transmissions And / or < / RTI > In the case of joint processing, the co-transmission may be performed by a plurality of cells to a wireless device (e.g., a UE), where multiple nodes are simultaneously transmitting at the same time using the same time and frequency radio resources and / send. The uplink CoMP operation can be divided into two categories: joint reception (JR) and cooperative scheduling and beamforming (CS / CB). In JR, a physical uplink shared channel (PUSCH) transmitted by a wireless device (e.g., a UE) may be received jointly at multiple points in a time frame. The set of multiple points may constitute a CoMP set of reception points (RP) and may be included in a part of the UL CoMP cooperative set or in the entire UL CoMP cooperative set. JR can be used to improve received signal quality. In the CS / CB, user scheduling and precoding selection decisions can be made in cooperation between points corresponding to the UL CoMP cooperation set. In the CS / CB, the PUSCH transmitted by the UE may be received at one point.

BRIEF DESCRIPTION OF THE DRAWINGS The features and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate, by way of example, the features of the invention.
Figure 1 is a block diagram of various component carrier (CC) bandwidths according to one example.
2A is a block diagram of a plurality of contiguous elementary carriers according to one example.
2B is a block diagram of in-band non-adjacent element carriers in accordance with one example.
2C is a block diagram of interband non-adjacent element carriers according to one example.
FIG. 3A is a block diagram of a symmetric-asymmetric carrier aggregation configuration according to one example.
Figure 3B is a block diagram of an asymmetric-symmetric carrier aggregation configuration according to one example.
4 is a block diagram of an uplink radio frame resource (e.g., a resource grid) according to one example.
5 is a block diagram of frequency hopping for a physical uplink control channel (PUCCH) according to one example.
6 is a diagram illustrating a table of physical uplink control channel (PUCCH) reporting types and mode states per PUCCH reporting mode according to one example.
Figure 7A is a block diagram of a homogeneous network using an intra-site cooperative multipoint (CoMP) system (e.g., CoMP scenario 1) in accordance with one example.
7B is a block diagram of a homogeneous network with high transmit power using an inter-site cooperative multipoint (CoMP) system (e.g., CoMP scenario 2) according to one example.
7C is a block diagram of a cooperative multipoint (CoMP) system (e. G., CoMP scenario 3 or 4) in a heterogeneous network with low power nodes according to one example.
8 is a diagram illustrating the functionality of a computer circuit element of a user equipment (UE) operable to report periodic channel state information (CSI) configured in a designated transmission mode according to one example.
9 is a flow diagram of a method for periodic channel state information (CSI) reporting in a cooperative multipoint (CoMP) scenario in a wireless device according to one example.
10 is a block diagram of a serving node, cooperative node, and wireless device according to one example.
11 is a diagram illustrating a wireless device (e.g., a UE) in accordance with one example.
Reference will now be made to the exemplary embodiments which will now be described and specific language will be used herein to describe it. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended.

Before the present invention is disclosed and described, it is to be understood that the invention is not limited to the specific structures, process steps or materials disclosed herein, but may be extended to equivalents thereof as will be appreciated by those skilled in the art . It is also to be understood that the terminology used herein is not intended to be limiting and used for purposes of describing particular examples only. The same reference numerals in different drawings represent the same elements. The numbers provided in the flowcharts and processes provide clarity in describing steps and operations and are not necessarily indicative of a particular order or sequence.

Illustrative Embodiments

Initial outlines of the technical embodiments are provided below, and then specific technical embodiments are described in further detail. This initial summary is intended to help the reader understand the technology more quickly but is not intended to limit the scope of the claimed subject matter without intending to identify key features or essential features of the technology.

The increase in wireless data transmission has resulted in congestion in wireless networks that use an authorized spectrum to provide wireless communication services to wireless devices such as smartphones and tablet devices. Congestion is particularly evident in high density and high-use locations such as downtown locations and colleges.

One technique for providing additional bandwidth capacity to wireless devices is through the use of carrier aggregation of a number of smaller bandwidths to form a virtual broadband channel at a wireless device (e.g., a UE). In a carrier aggregation (CA), a number of element carriers (CCs) may be aggregated and used jointly for transmission to / from a single terminal. Carriers are signals within the allowed frequency domain in which information is placed. The amount of information that can be placed on the carrier is determined by the bandwidth of the aggregated carriers in the frequency domain. The allowed frequency domains are often limited within the bandwidth. Bandwidth constraints can become more stringent when a large number of users are simultaneously using bandwidth in the allowed frequency domains.

1 illustrates a carrier bandwidth, a single bandwidth, or a component carrier (CC) that can be used by a wireless device. For example, the LTE CC bandwidths may include: 1.4 MHz (210), 3 MHz (212), 5 MHz (214), 10 MHz (216), 15 MHz (218), and 20 MHz (220). The 1.4 MHz CC may include six resource blocks (RBs) including 72 subcarriers. The 3 MHz CC may include 15 RBs including 180 subcarriers. The 5 MHz CC may include 25 RBs containing 300 subcarriers. A 10 MHz CC may include 50 RBs containing 600 subcarriers. A 15 MHz CC may include 75 RBs containing 900 subcarriers. The 20 MHz CC may include 100 RBs containing 1200 subcarriers.

It is possible for the carrier aggregation (CA) to simultaneously communicate multiple carrier signals between the user's wireless device and the node. A number of different carriers may be used. In some instances, the carriers may originate from other allowed frequency domains. Carrier aggregation allows more bandwidth to be obtained by providing a wider choice for wireless devices. This larger bandwidth can be used to communicate bandwidth intensive operations such as streaming video or communicating large data files.

2A shows an example of carrier aggregation of continuous carriers. In this example, the three carriers are located consecutively in the frequency band. Each carrier may be referred to as an element carrier. In a continuous type of system, the element carriers are located adjacent to each other and typically can be located in a single frequency band (e.g., band A). The frequency band may be a selected frequency range within the electromagnetic spectrum. The selected frequency bands are designated for use in wireless communications such as wireless telephones. Specific frequency bands are owned or borrowed by wireless service providers. Each adjacent elementary carrier may have the same bandwidth or a different bandwidth. The bandwidth is a selected portion of the frequency band. Wireless telephones have traditionally been performed within a single frequency band. In continuous carrier aggregation, only one fast Fourier transform (FFT) module and / or one wireless frontend may be used. Continuous element carriers may have similar propagation characteristics that may use similar reports and / or processing modules.

Figures 2b and 2c show an example of carrier aggregation of discontinuous element carriers. Non-continuous element carriers can be separated along the frequency range. Each element frequency can even be in different frequency bands. Non-continuous carrier aggregation can provide aggregation of fragmented spectra. In-band (or single band) discontinuous carrier aggregation provides discontinuous carrier aggregation within the same frequency band (e.g., band A), as shown in FIG. 2B. Inter-band (or multi-band) discontinuous carrier aggregation provides discontinuous carrier aggregation within different frequency bands (e.g., bands A, B, or C), as shown in FIG. It is possible to use the element carriers within different frequency bands, making it possible to use the available bandwidth more efficiently and to increase aggregated data throughput.

Network symmetric (or asymmetric) carrier aggregation may be defined by a number of downlink (DL) and uplink (UL) component elements supplied by the network in the sector. UE symmetric (or asymmetric) carrier aggregation may be defined by a number of downlink (DL) and uplink (UL) element carriers configured for the UE. The number of DL CCs may be at least a number of UL CCs. A system information block type 2 (SIB2) may provide a specific linking between DL and UL. FIG. 3A shows a block diagram of a symmetric-asymmetric carrier aggregation configuration, where carrier aggregation is symmetric between DL and UL for a network and asymmetric between DL and UL for a UE. FIG. 3B shows a block diagram of an asymmetric-symmetric carrier aggregation configuration wherein carrier aggregation is asymmetric between DL and UL for a network and symmetrical between DL and UL for a UE.

The element carrier is a physical (PHY) carrier using a common LTE frame structure during uplink transmission between a node (e.g., eNodeB) and a wireless device (e.g., UE) Lt; RTI ID = 0.0 > layer) < / RTI > Although an LTE frame structure is shown, other types of communication standards using IEEE 802.16 standard (WiMax), IEEE 802.11 standard (WiFi) or SC-FDMA or OFDMA may also be used.

4 shows an uplink radio frame structure. In this example, the radio frame 100 of the signal used to transmit control information or data may be configured to have a duration T _f of 10 milliseconds (ms). Each radio frame may be segmented or segmented into 10 subframes 110i each 1 ms long. Each subframe may be further sub-divided into two slots 120a and 120b each having a duration (T _slot ) of 0.5 ms. Each slot for the element carrier (CC) used by the wireless device and node may comprise a number of resource blocks (RBs) 130a, 130b, 130i, 130m and 130n based on the CC frequency bandwidth. Each RB (physical RB or PRB) 130i includes 12 to 15 kHz subcarriers 136 (on the frequency axis) and 6 or 7 SC-FDMA symbols 132 (on the time axis) per subcarrier . RB can use 7 SC-FDMA symbols when a short or normal cyclic prefix is used. RB can use six SC-FDMA symbols when an extended cyclic prefix is used. The resource blocks may be mapped to 84 resource elements (REs) 140i using short or normal cyclic transpositions, or resource blocks may be mapped to 72 REs (Not shown). RE may be a unit by one subcarrier (i.e., 15 kHz) 146 of one SC-FDMA symbol 142. [ Each RE can transmit information of two bits 150a and 150b in the case of quadrature phase-shift keying (QPSK) modulation. To transmit a smaller number of bits (a single bit) in each RE, such as 16 quadrature amplitude modulation (QAM) or 64 QAM to transmit a greater number of bits in each RE, Other types of modulation may be used, such as bi-phase shift keying (BPSK) modulation. The RB may be configured for uplink transmission from the wireless device to the node.

A reference signal (RS) may be transmitted via resource elements in the resource blocks by SC-FDMA symbols. The reference signals (or pilot signals or tones) may be known signals used for various reasons, such as synchronizing the timing and estimating the noise in the channel and / or the channel. The reference signals may be received and transmitted by wireless devices and nodes. Different types of reference signals (RS) may be used in the RB. For example, in LTE systems, uplink reference signal types include a sounding reference signal (SRS) and a UE-specific reference signal (UE-specific RS or UE-RS) or a demodulation reference signal ; DM-RS). In LTE systems, the downlink reference signal types may include channel state information reference signals (CSI-RSs) that can be measured by a wireless device to provide CSI reports on the channel.

The uplink signal or channel may include data for a physical uplink shared channel (PUSCH) or control information for a physical uplink control channel (PUCCH). In LTE, uplink physical channel (PUCCH) carrier uplink control information (UCI) includes channel state information (CSI) reports, Hybrid Automatic Retransmission ReQuest (HARQ) / ACKnowledgment (ACKnowledgment / ACK / NACK) and uplink scheduling request (SR).

Wireless devices may provide aperiodic CSI reporting using PUSCH or periodic CSI using PUCCH. PUCCH may provide various modulation and coding schemes (MCSs) to multiple formats (i.e., PUCCH format), as described for LTE in Table 1. [ For example, PUCCH format 3 may be used to convey a multi-bit HARQ-ACK that may be used for carrier aggregation.

In another example, PUCCH format 2 may use frequency hopping, as shown in FIG. Frequency hopping may be performed between a number of frequency channels using a specific sequence known to both a pseudorandom sequence or a transmitter (e.g., UE in the uplink) and a receiver (e.g., an eNB in the uplink) To quickly transmit the radio signals by switching the carrier wave at the mobile station. Frequency hopping may enable the UE to utilize the frequency diversity of the wideband channel used in LTE during uplink while maintaining a continuous allocation (in the time domain).

The PUCCH may include various channel state information (CSI) reports. The CSI components in the CSI reports include a channel quality indicator (CQI), a precoding matrix indicator (PMI), a precoding type indicator (PTI), and / And a rank indication (RI) reporting type. A CQI is a modulation and coding scheme (MCS), which may be based on a measurement of the received downlink signal to interference plus noise ratio (SINR) May be signaled by the UE to the eNodeB to indicate an appropriate data rate, such as a value. The PMI may be a signal provided back by the UE to support multiple-input multiple-output (MIMO) operation. The PMI may correspond to the index of the precoder (in the codebook shared by the UE and the eNodeB), which may maximize the total number of data bits that can be received across all downlink space transport layers. PTI can be used to distinguish between slow and fast fading environments. RI may be signaled to the eNodeB by the UEs configured for PDSCH transmission modes 3 (e.g., open loop spatial multiplexing) and 4 (e.g., closed loop spatial multiplexing). The RI may correspond to a number of useful transport layers for spatial multiplexing (based on the UE estimate of the downlink channel), so that it is possible for the eNodeBs to adapt PDSCH transmissions accordingly.

The granularity of a CQI report can be divided into three levels: broadband, UE select subband and upper layer constituent subband. The broadband CQI report can provide one CQI value for the entire downlink system bandwidth. The UE selected subband CQI report may divide the system bandwidth into a plurality of subbands, where the UE selects a set of preferred lower bands (the best M subbands) and then one CQI for the broadband And a single differential CQI value for this set can be reported (assuming transmission for only the M subbands selected). Upper Tier Configurations Subband CQI reports can provide the highest granularity. In a higher layer constituent subband CQI report, the wireless device may divide the total system bandwidth into a plurality of subbands, and then report one broadband CQI value and a number of differential CQI values as for each subband .

The UCI carried by the PUCCH may use different PUCCH reporting types (or CQI / PMI and RI reporting types) to specify which CSI reports are being transmitted. For example, PUCCH reporting type 1 may support CQI feedback for UE selected subbands; Type 1a may support lower-band CQI and second PMI feedback; Type 2, Type 2b, and Type 2c can support wideband CQI and PMI feedback; Type 2a can support broadband PMI feedback; Type 3 can support RI feedback; Type 4 can support wideband CQI; Type 5 can support RI and broadband PMI feedback; And Type 6 can support RI and PTI feedback.

The different CSI components may be included based on the PUCCH reporting type. For example, RI may be included in PUCCH reporting types 3, 5, or 6. Broadband PTI may be included in PUCCH reporting type 6. Broadband PMI may be included in PUCCH reporting types 2a or 5. The wideband CQI may be included in PUCCH reporting types 2, 2b, 2c or 4. The lower band CQI may be included in PUCCH reporting types 1 or 1a.

The CQI / PMI and RI (PUCCH) reporting types with different periods and offsets may be supported for the PUCCH CSI reporting modes illustrated by the table in FIG. FIG. 5 shows an example of PUCCH reporting type and PUCCH reporting mode payload size and mode status for LTE.

The CSI information being reported may vary based on the downlink transmission scenarios used. Various scenarios for the downlink may be reflected in different transmission modes (TMs). For example, in LTE, TM 1 may use a single transmit antenna; TM 2 can use transmit diversity; TM 3 may use open loop spatial multiplexing with cyclic delay diversity (CDD); TM 4 can use closed-loop spatial multiplexing; TM 5 can use multi-user MIMO (MU-MIMO); TM 6 can use closed-loop spatial multiplexing using a single transport layer; TM 7 can use beamforming by UE-specific RS; TM 8 may use single or dual layer beamforming by UE specific RSs; And TM 9 can use closed-loop single-user single-MIMO (SU-MIMO) or multi-layer transmission to support carrier aggregation. In one example, the TM 10 may be used for cooperative multipoint (CoMP) signaling such as joint processing (JP), dynamic point selection (DPS) and / or cooperative scheduling / cooperative beamforming .

Each transmission mode may use different PUCCH CSI reporting modes, where each PUCCH CSI reporting mode may represent different CQI and PMI feedback types, as shown for LTE in Table 2. [

For example, in LTE, TMs 1, 2, 3, and 7 may use PUCCH CSI reporting modes (1-0 or 2-0); TMs 4, 5, and 6 may use PUCCH CSI reporting modes (1-1 or 2-1); TM 8 indicates PUCCH CSI reporting modes (1-1 or 2-1) when the UE is configured with PMI / RI reporting, or PUCCH CSI reporting modes (1-0 or 2-1) when the UE is configured without PMI / 2-0) can be used; The TMs 9 and 10 may then transmit PUCCH CSI reporting modes (1-1 or 2-1) if the UE is configured for PMI / RI reporting and the number of CSI-RS ports is greater than one, Or use PUCCH CSI reporting modes (1-0 or 2-0) if the number of CSI-RS ports is equal to one. Based on the downlink transmission scheme (e.g., transmission mode), the UE may send more CSI reports than can be allowed to be sent to nodes (e.g., eNBs) without causing signal collisions or interference . A wireless device (e.g., a UE) may determine whether CSI reports should be continuously transmitted and which CSI reports are to be dropped or discarded (and not transmitted) to prevent collisions on subframes.

In CSI reporting, PUCCH Format 2 can carry 4 to 11 CSI (CQI / PMI / PTI / RI) bits from UE to eNB. In carrier aggregation, each serving cell may be independently configured by radio resource control (RRC) signaling on the CSI configuration, such as periodicity, start offset, or PUCCH mode. However, the transmission of CSI using PUCCH format 2 can be performed only in the primary cell. In one example using PUCCH format 2, one CSI report for a particular serving cell may be transmitted, while the remaining CSI reports for other serving cells may contain one or more CSI reports for multiple serving cells, May be dropped when they have the potential to collide with each other. Dropping CSI reports for other serving cells may prevent collision of CSI reports in the same subframe. In one example, the criteria used to determine the priority of transmitted periodic CSI reports and periodic CSI reports being dropped is based on the PUCCH reporting type, where a lower CSI reporting type priority is dropped. PUCCH reporting types 3, 5, 6 and 2a may have the highest or highest priority and PUCCH reporting types 2, 2b, 2c and 4 may have the next priority or second priority, and PUCCH reporting types 3, Types 1 and 1a may have a third or lowest priority. Therefore, the UE first drops CSI reports with PUCCH reporting types 1, 1a first and then PUCCH reporting types (2, 2b, 2c and 4) secondly above the number of transmitted CSI report (s) , And then drop any CSI reports with PUCCH reporting types 3, 5, 6 and 2a. In one example, a CSI report can be generated for each element carrier (CC). Each CC may be represented by a serving cell index (i.e., ServCellIndex). Of the CSI reports with reporting types (e.g., PUCCH reporting types 3, 5, 6, and 2a) having the same priority, the priority of the cell depends on the increase of the corresponding serving cell index (i.e. ServCellIndex) (I.e., the lower-level cell index has a higher priority).

In another example, the CSI report priority may be based on a CSI component, where RI and broadband PMI reporting have a higher priority than CQI reporting and broadband CQI reporting has a higher priority than lower band CQI reporting. RI can have a higher priority because RI can provide overall information about network channel conditions. In one example, the PMI and CQI may depend on the RI. The broadband CQI may have a higher priority than the subband CQI because the broadband CQI may provide the overall quality information for the channel or may provide the worst case scenario for the channel, Because it provides more narrow subband channel quality information.

In one example, additional CSI reports may be generated in a cooperative multipoint (CoMP) system. Additional criteria may be used to drop CSI reports in the CoMP system. The CoMP system (also known as multi-eNobeB multiple-input multiple-output [MIMO]) can be used to improve interference mitigation. At least four basic scenarios for CoMP operation can be used.

FIG. 7A shows an example of a cooperative area 308 (drawn in bold) of an intra-site CoMP system within a homogeneous network, which may illustrate LTE CoMP scenario 1. Each node 310A and 312B through 312G can serve multiple cells (or sectors) 320A through 320G, 322A through 322G and 324A through 324G. A cell is a logical definition generated by a geographic transmission area or sub-area (within the total coverage area) covered by a node or node, which is a logical definition generated by a node or node, such as control channel, reference signals and element carrier (CC) And may include a specific cell identification (ID) that defines the parameters. By coordinating the transmission between multiple cells, the interference from other cells can be reduced and the received power of the desired signal can be increased. The nodes outside the CoMP system may be non-cooperating nodes 312B through 312G. In one example, the CoMP system may be illustrated with a plurality of cooperating nodes (not shown) surrounded by a plurality of non-cooperating nodes.

FIG. 7B shows an example of an inter-site CoMP system having high-power remote radio heads (RRHs) within a homogeneous network, which may illustrate LTE CoMP scenario 2. The cooperative area 306 (drawn in bold) may include eNBs 310A and RRHs 314H through 314M, where each RRH is a backhaul link (optical or wired link) RTI ID = 0.0 > eNB < / RTI > Cooperating nodes may include eNBs and RRHs. In CoMP systems, nodes can be grouped together as cooperating nodes in adjacent cells, where cooperating nodes from multiple cells can send signals to wireless device 302 and receive signals from the wireless device . Cooperating nodes may coordinate transmission / reception from / to wireless device 302 (e.g., UE). Collaborating nodes of each CoMP system may be included in the collaboration set. The CSI report may be generated during the CSI process based on transmissions from each cooperative set.

FIG. 7C shows an example of a CoMP system having low power nodes (LPNs) within a cell coverage area in a mat. FIG. 7C shows LTE CoMP scenarios 3 and 4. In the intra-site CoMP example shown in FIG. 7C, the LPNs (or RRHs) of the macro node 310A may be located in different places in space, and CoMP cooperation may be within a single macro cell. Cooperative area 304 may include eNBs 310A and LPNs 380N through 380S where each LPN may be configured to communicate with an eNB via a backhaul link 332 (optical or wired link) have. The cell 326A of the macro node can be further subdivided into the lower cells 330N to 330S. LPNs (or RRHs) 380N through 380S may transmit and receive signals for the lower cell. The wireless device 302 may be on a lower cell edge (or cell edge) and intra-site CoMP cooperation may occur between LPNs (or RRHs) or between eNBs and LPNs. In CoMP scenario 3, the low power RRHs that provide the transmit / receive points within the macrocell coverage area may have cell IDs different from macrocells. In CoMP scenario 4, the low power RRHs that provide transmit / receive points within the macrocell coverage area may have the same cell ID as the macrocell.

The downlink (DL) CoMP transmission can be divided into two categories: cooperative scheduling or cooperative beamforming (CS / CB or CS / CBF) and joint processing or joint transmission (JP / JT). In CS / CB, a given subframe may be transmitted from one cell to a given mobile communication device (UE), and scheduling involving cooperative beamforming may control interference between different transmissions and / It cooperates dynamically between cells to reduce. In the case of joint processing, joint transmission may be performed by a plurality of cells to a mobile communication device (UE), where multiple nodes simultaneously transmit using the same time and frequency radio resources and dynamic cell selection. Two methods can be used for joint transmission: non-coherent transmission using soft combining reception of an OFDM signal; And a coherent transmission that performs precoding between the cells for in-phase combining at the receiver. By coordinating and combining signals from multiple antennas, CoMP allows mobile users to enjoy consistent performance and quality for high bandwidth services, whether the mobile user is near the center of the cell or at the outer edges of the cell .

Even in a single serving cell (i.e., a single element carrier (CC) scenario), a number of periodic CSI reports can be sent for DL CoMP. The PUCCH report may define the format in which the CSI can be provided and the uplink resources, i.e., the PUCCH report configuration may specify how to transmit the CSI feedback. For CoMP operations, measuring the CSI may be defined by a "CoMP CSI process" which may include the configuration of channels and interference portions. Therefore, different CSI reports can be associated with different processes. For example, CoMP CSI measurements associated with one CoMP CSI process can be transmitted using periodic or aperiodic feedback modes.

Multiple periodic CSI processes may be configured using specific IDs or index numbers by the network to facilitate multiple periodic CSI feedbacks. As shown herein, the CSI process index (CSIProcessIndex or CSIProcessID) refers to the realization of a number of such periodic CSI processes. For example, if a serving cell (e.g., serving node) configures three periodic CSI processes, the network may configure three CSI period processes and the CSIProcessIndex may be numbered 0, 1, and 2 . Each periodic CSI process can be independently configured by RRC signaling.

In legacy LTE, only one periodic CSI report can be sent by PUCCH format 2, 2a or 2b. In the event that one or more periodic CSI transmissions occur simultaneously in a subframe, only one periodic CSI report may be transmitted and the remaining periodic CSI reports may be dropped. The maximum payload for the aggregated periodic CSI can still be limited, although a number of periodic CSI reports may be transmitted on the PUCCH or on the PUSCH with PUCCH format 3. For example, up to 22 information bits may be transmitted using PUCCH format 3. Therefore, if the total number of periodic CSI bits exceeds 22 bits, the remaining CSI reports can be dropped. In one example, if PUCCH format 2 is used for periodic CSI transmission, only one CSI process may be selected for transmission regardless of capacity criterion.

Various methods can be used to determine which CSI process or CSI report can be dropped when CSIProcessID is used. For illustrative purposes, a PUCCH with PUCCH format 3 that can carry multiple CSIs is assumed, but the same principle may be used in other cases, such as other PUCCH formats or PUSCH formats.

If the summed periodic CSI information bits do not exceed the maximum capacity of a particular PUCCH format (e.g., PUCCH format 2, PUCCH format 3, PUSCH, or other formats), the aggregated periodic CSI can be transmitted on the corresponding PUCCH format have. Otherwise, the periodic CSIs between the CSI processes may be less than the maximum capacity for the PUCCH format used in the PUCCH by the periodic CSI payloads (i.e., if the summed periodic CSI information bits do not exceed the maximum capacity of the particular PUCCH format) And may be selected to be CSI processes with no more maximum number. For example, if the number of CSI processes is 5, the PUCCH format 3 is used, and the number of CSI bits is 11 for each CSI process, the CSI for only two CSI processes on PUCCH format 3 can be transmitted and the remaining three CSI Processes can be dropped.

Many methods can be used to determine the priority rules that drop CSI processes and / or reports. A PUCCH format 3 that uses the PUCCH format 2 with a single CSI process or a PUCCH format 3 that uses the multi-process CSI transmission can be used. For example, if the PUCCH uses PUCCH Format 2 for periodic CSI transmissions, only one CSI process may be selected for transmission regardless of the capacity criterion.

In one method (i.e., method 1), the priority to hold (or drop) the CSI processes in the colliding sub-frame (or potentially colliding sub-frame) is first determined by the PUCCH reporting type and / or the PUCCH reporting mode Can be determined. A first or highest priority CSI process may be provided in PUCCH reporting types 3, 5, 6 and 2a, after which the next or second priority CSI process is provided to PUCCH reporting types 2, 2b, 2c and 4 , And then a third or last priority CSI process may be provided for PUCCH reporting types 1 and 1a.

If the total number of CSI bits still exceeds 22 bits in PUCCH format 3 or one or more CSI processes remain in PUCCH format 2, one of two rules can be used. Using the first rule, CQI / PMI / PTI / RI reporting priorities among CSI processes with PUCCH reporting modes and / or types of the same priority can be determined based on the CSI process index (e.g., CSIProccessID) have. For example, the priority of the CSI process ID decreases when the corresponding CSI process ID increases, so that the lower CSI process ID can have a higher priority. Using the second rule, the priority may be a CSI process configured by RRC signaling.

In another method (i.e., method 2), the priority of holding (or dropping) CSI processes in a colliding sub-frame may be provided by RRC signaling. In one example, the maximum capacity for PUCCH format 2 may be 11 bits, PUCCH format 3 may be 22 bits, and the PUSCH may be 55 bits.

The priority to hold (or drop) CSI reports may also be determined to co-use CoMP scenarios (using CSIProcessID or CSIProcessIndex) such as Carrier aggregation (using ServCellIndex) and Transport Mode 10. The priorities for dropping CSI reports can be defined by considering both the carrier and CSI process domains.

For example, in the method (i.e., method A), element carriers and CSI processes used to drop (or retain) CSI reports within a colliding sub-frame (or potentially colliding sub-frame) The ranking may first be based on the PUCCH reporting type and / or the PUCCH reporting mode. A first or highest priority CSI process may be provided in PUCCH reporting types 3, 5, 6 and 2a, after which the next or second priority CSI process is provided to PUCCH reporting types 2, 2b, 2c and 4 , And then a third or last priority CSI process may be provided for PUCCH reporting types 1 and 1a.

One of three rules may be used if the total number of CSI bits is still 22 or more in PUCCH format 3 or if more than one CSI process is still in PUCCH format 2. Using the first rule, the CQI / PMI / PTI / RI reporting priorities among the serving cells having the same priority of the PUCCH reporting modes and / or types are based on serving cell indices (e.g. ServCellIndex) Can be determined. The priority of a cell may decrease when the corresponding serving cell index increases.

If the total number of CSI bits is still greater than or equal to 22 in PUCCH format 3, or if more than one CSI process is still in PUCCH format 2, then CSI processes with the same priority PUCCH reporting mode and / or types and / The CQI / PMI / PTI / RI reporting priorities between the base station and the base station can be determined based on the CSI process index (e.g., CSIProcessID or CSIProcessIndex). The priority of the CSI process index may decrease as the corresponding CSI process index increases.

Using the second rule, the CQI / PMI / PTI / RI reporting priorities among the CSI processes for each serving cell with the same priority PUCCH reporting mode and / or types are stored in the CSI process index (e.g., CSIProcessID Or CSIProcessIndex). The priority of the CSI process index may decrease as the corresponding CSI process index increases.

If the total number of CSI bits is still equal to or greater than 22 in PUCCH format 3 or if more than one CSI process still remains in PUCCH format 2, then the number of serving cells having the same priority PUCCH reporting mode and / or types and having the same CSI process index The CQI / PMI / PTI / RI reporting priorities can be determined based on the serving cell index (e.g., ServCellIndex). The priority of a cell may decrease when the corresponding serving cell index increases.

Using the third rule, CSI process indexes used in priority and / or CoMP scenarios across CCs used for carrier aggregation can be configured by RRC signaling.

In another method (i.e., method B), all priorities for CSI processes used in CoMP scenarios and for element carriers used for carrier aggregation can be configured by RRC signaling.

In another method (i.e. Method C), the CSI process index can be uniquely defined across serving cells and CSI processes (i.e., the unique CSI process index can be a combination of CSIProcessIndex and ServCellIndex). In one example, the CSI process index can be determined and communicated via RRC signaling. For example, if there are two CSI processes per two serving cell aggregates and serving cells, then the total number of CSI processes is six CSI processes (i. E., CSI processes 0,1,2,3,4 and 5) Can be uniquely defined.

Using the unique CSI process index, the priority for the CSI processes used to drop (or retain) the CSI reports in the colliding sub-frame (or potentially colliding sub-frame) is first determined using the PUCCH reporting type and / May be based on a reporting mode. A first or highest priority CSI process may be provided in PUCCH reporting types 3, 5, 6 and 2a, and then the next or second priority CSI process is provided to PUCCH reporting types 2, 2b, 2c and 4 , And then a third or last priority process may be provided for PUCCH reporting types 1 and 1a.

If the total number of CSI bits is still greater than or equal to 22 in PUCCH format 3 or if more than one CSI process is still in PUCCH format 2, then the CQI / PMI / CSI between CSI processes with PUCCH reporting modes and / The PTI / RI reporting priorities may be determined based on the CSI process index (e.g., CSIProcessID or CSIProcessIndex). The priority of the CSI process index may decrease as the corresponding CSI process index increases.

In another method (i.e., method D), a default CSI process index may be specified in each serving cell. Each default CSI process index may have the highest priority per serving cell. Using the default CSI process index for each serving cell, the priority for CSI processes used to drop (or retain) the CSI reports in the colliding sub-frame (or potentially colliding sub-frame) is first determined using the PUCCH reporting type And / or a PUCCH reporting mode. A first or highest priority CSI process may be provided in PUCCH reporting types 3, 5, 6 and 2a, after which the next or second priority CSI process is provided to PUCCH reporting types 2, 2b, 2c and 4 , And then a third or last priority CSI process may be provided for PUCCH reporting types 1 and 1a.

PMI / PMI < / RTI > between default CSI processes with PUCCH reporting modes and / or priority of types if the total number of CSI bits is still 22 or more in PUCCH format 3 or one or more CSI processes still remains in PUCCH format 2. & The PTI / RI reporting priorities may be determined based on the CSI process index (e.g., CSIProcessID or CSIProcessIndex). The priority of the CSI process index may decrease as the corresponding CSI process index increases.

Combinations of various methods are also contemplated.

In another example, the drop rules for the combined carrier aggregation and CoMP scenarios can be used for multiplexing CSI and HARQ-ACK using PUCCH Format 3. An automatic repeat request is a feedback mechanism that is requested by a terminal receiving retransmission of packets that are detected as having an error. Hybrid ARQ is a simultaneous combination of Automatic Retransmission ReQuest (ARQ) and forward error correction (FEC) that can enable the overhead of error correction to be dynamically adapted to channel quality . When HARQ is used and errors can be corrected by FEC, no retransmission may be requested, and if errors can be detected but not corrected, a retransmission may be requested. An acknowledgment (ACK) signal may be sent indicating that one or more blocks of data have been successfully received and decoded, such as at the PDSCH. The HARQ-ACK / Negative ACKnowledgement (NACK or NAK) information may include feedback from the receiver to the transmitter (via NACK or NAK) to acknowledge the correct reception of the packet or to request a new retransmission.

In one example, in the case of a UE configured in PUCCH format 3 for HARQ-ACK transmission and in the case of a subframe in which the UE is configured to transmit HARQ-ACK transmission by periodic CSI, and if the PUCCH format 3 resource is a HARQ- In the case of a subframe indicating for-ACK transmission, the UE may transmit HARQ-ACK and single cell periodic CSI according to the following process. No additional PUCCH format 3 resources other than Format 3 resources may be configured for HARQ-ACK and CSI multiplexing. The HARQ-ACK and periodic CSI can be jointly coded with up to 22 bits including schedule requests (SRs). For periodic CSI reporting, the serving cell may be selected when the selected periodic CSI report can fit into the PUCCH format 3 payload size with HARQ-ACK feedback bits (including SR). Then periodic CSI and HARQ-ACK bits (including SR) may be transmitted, otherwise HARQ-ACK (including SR) may be transmitted without periodic CSI.

In the case of combined carrier aggregation and CoMP, only one CSI report can be selected for the combined CSI process and ACK / NACK (A / N) feedback in the PUCCH with PUCCH format 3. The selection rules of methods A, B, C and D above can be used to select one periodic CSI report for the combined CSI process and A / N on the PUCCH with PUCCH format 3.

For example, a drop rule using method A can be expressed as: < RTI ID = 0.0 > drop (or retain) < / RTI > CSI reports in a priority for CSI processes and in a conflicting subframe (or potentially colliding subframe) May be based on the PUCCH reporting type and / or the PUCCH reporting mode. A first or highest priority CSI process may be provided in PUCCH reporting types 3, 5, 6 and 2a, after which the next or second priority CSI process is provided to PUCCH reporting types 2, 2b, 2c and 4 , And then a third or last priority CSI process may be provided for PUCCH reporting types 1 and 1a.

If one or more CSI processes still remain in PUCCH format 2, the CQI / PMI / PTI / RI reporting priorities between CSI processes for each serving cell with the same priority PUCCH reporting mode and / (E.g., CSIProcessID or CSIProcessIndex). The priority of the CSI process index may decrease as the corresponding CSI process index increases.

Then, if one or more of the CSI processes still remain in PUCCH Format 2, the CQI / PMI / PTI / RI reporting priorities among the serving cells having the same priority PUCCH reporting mode and / or types and having the same CSI process index, May be determined based on the cell index (e.g., ServCellIndex). The priority of a cell may decrease when the corresponding serving cell index increases.

Another example provides the functionality 500 of a computer circuit of a user equipment (UE) operable to report periodic channel state information (CSI) configured in a particular transmission mode, as shown in the flow diagram in Fig. This function may be implemented as a method, or the function may be executed as instructions on a machine, where instructions are contained on at least one computer readable medium or one non-volatile machine readable storage medium. The computer circuitry is configured to generate a plurality of CSI reports for transmission to a plurality of CSI processes for transmission within a subframe, each CSI report corresponding to a CSI process having a CSIPProcessIndex, The computer circuitry may be further configured to drop CSI reports corresponding to the CSI processes except for the CSI process with the lowest CSIProcessIndex, The computer circuitry may also be configured to send at least one CSI report for the CSI process to the evolved Node B (eNB), as at block 530. [

In one example, a computer circuit configured to drop CSI reports determines a selected number of CSI reports to transmit based on a physical uplink control channel (PUCCH) format; And to drop CSI reports corresponding to all CSI processes except the selected number of highest priority CSI reports corresponding to the CSI processes to prevent CSI reporting conflicts in the subframe. The PUCCH format may include PUCCH formats 2, 2a, 2b, and 3 as at least one CSI report.

In another example, a computer circuit configured to drop CSI reports can be further configured to drop CSI reports based on ServCellIndex, except for CSI reports with the lowest ServCellIndex when CSIProcessIndex for CSI reports are the same. In another example, the computer circuitry is further configured to drop at least one lower priority CSI report based on the serving cell's physical uplink control channel (PUCCH) reporting type prior to dropping the lower priority CSI report based on the CSIProcessIndex . PUCCH reporting types 3, 5, 6 and 2a may have a higher priority than PUCCH reporting types 1, 1a, 2, 2b, 2c and 4 and PUCCH reporting types 2, 2b, 2c and 4 may have higher priority than PUCCH reporting types 1, It has a higher priority than types 1 and 1a. The highest priority CSI report may contain the lowest CSIProcessIndex. In another configuration, the computer circuitry may be further configured to assign a highest priority CSI process for a serving cell corresponding to a lowest CSIProcessIndex to a default CSI process. In another example, CSIProcessIndex may be unique for a particular CSI process and a particular serving cell. A particular transmission mode may be used for cooperative multipoint (CoMP) configuration. In one example, a particular transmission mode may include a transmission mode 10 used in a CoMP configuration.

Another example provides a method 600 for periodic channel state information (CSI) reporting from a user equipment (UE) in a cooperative multipoint (CoMP) scenario, as shown in the flow chart in FIG. The method may be executed as instructions on a machine, wherein instructions are contained on at least one computer readable medium or one non-volatile machine readable storage medium. The method includes determining at the UE a plurality of CSI reports colliding in a subframe, as in block 610, wherein the CSI CSI reports include a plurality of processes, each CSI report having a CSI process index Corresponds to the CSI process. The operation of prioritizing multiple CSI reports with a lower priority CSI process having a lower CSI process index follows, as at block 620. [ The next operation of the method may be to drop the lower priority CSI report based, in part, on the CSI process index, as in block 630. [ The method may further comprise transmitting at least one highest priority CSI report from the UE to the node, such as in block 640.

Prioritizing multiple CSI reports is based on a channel quality indicator (CQI) / precoding matrix indicator (PMI) / rank indication (RI) reporting type Wherein the CQI / PMI / RI reporting types 3, 5, 6, and 2a further comprise prioritizing multiple CSI reports, wherein the CQI / PMI / RI reporting types 1, 1a, 2, 2b, 2c And CQI / PMI / RI reporting types 2, 2b, 2c, and 4 have higher priorities than CQI / PMI / RI reporting types 1 and 1a. In one example, the operation of prioritizing a plurality of CSI reports may include prioritizing a plurality of CSI reports based on a serving cell index or element carrier (CC), when the CC having a higher priority has a lower serving cell index And then prioritizing the multiple CSI reports based on the CSI process index. In another example, the operation of prioritizing multiple CSI reports prioritizes multiple CSI reports based on the CSI process index, and then prioritizes multiple CSI reports based on the serving cell index or element carrier (CC) The CC having the higher priority has the lower serving cell index.

In another configuration, the act of prioritizing multiple CSI reports may include receiving, via radio resource control (RRC) signaling, a priority for CSI reports based on a CSI process index or element carrier (CC) for each CSI report Quot; In another example, a unique CSI process index may be assigned for a particular CSI process and a particular CC. In another example, the method may further comprise defining a default CSI process having a highest priority CSI process. The default CSI process may correspond to the lowest CSI process index.

The operation of transmitting at least one highest priority CSI report may further comprise transmitting a non-colliding CSI report for each of up to 11 bits available in the PUCCH format. A node may be a base station (BS), a Node B (NB), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH) a radio equipment (RRE), and a remote radio unit (RRU).

10 illustrates an exemplary node (e.g., serving node 710 and cooperating node 730) and exemplary wireless device 720. The node may include node devices 712 and 732. The node device or node may be configured to communicate with the wireless device. The node device may be configured to receive periodic channel state information (CSI) transmissions configured in a particular transmission mode, such as transmission mode 10. A node device or node may be configured to communicate with other nodes via a backhaul link 740 (optical or wired link), such as the X2 application protocol (X2AP). The node device may include processing modules 714 and 734 and transceiver modules 716 and 736. The transceiver module may be configured to receive periodic channel state information (CSI) on the PUCCH. The transceiver modules 716 and 736 may be further configured to communicate with the coordinating node via the X2 application protocol (X2AP). The processing module may be further configured to process periodic CSI reports of the PUCCH. A node (e.g., serving node 710 and cooperating node 730) may communicate with a base station (BS), a node B (NB), an evolved Node B (eNB), a baseband unit RRH), a remote radio equipment (RRE) or a remote radio unit (RRU).

The wireless device 720 may include a transceiver module 724 and a processing module 722. The wireless device may be configured for periodic channel state information (CSI) transmission, which is configured in a particular transmission mode, such as the transmission mode used for CoMP operation. The processing module may be configured to generate a priority of a CSI report in a plurality of CSI reports for a subframe based on a CSI process index and a physical uplink control channel (PUCCH) reporting type, and to drop low priority CSI reports have. The CSI process index may correspond to a downlink (DL) CoMP CSI process. The transceiver module may be configured to transmit at least one higher priority CSI report to the node.

In one example, the highest priority CSI process for a serving cell may correspond to a low field CSIProcessIndex. PUCCH reporting types with rank indication (RI) or wide band precoding matrix indicator (PMI) feedback without channel quality indicator (CQI) feedback may have a higher priority than PUCCH reporting types with CQI feedback, and broadband CQI PUCCH reporting types with feedback may have a higher priority than a PUCCH with subband CQI feedback.

In one configuration, the processing module 722 may be further configured to prioritize the CSI reports based on the serving cell index and then prioritize the CSI reports based on the CSI process index. A CSI report with a lower serving cell index may have a higher priority than a CSI report with a higher serving cell index and a CSI report for a particular serving cell index with a lower CSI process index may have a higher CSI process index And may have a higher priority than the CSI report for a particular serving cell index.

In another configuration, the processing module 722 may be further configured to prioritize the CSI reports based on the CSI process index and then prioritize the CSI reports based on the serving cell index. A CSI report with a CSI process index may have a higher priority than a CSI report with a higher CSI process index and a CSI report for a particular CSI process index with a lower serving cell index may be a particular CSI process with a higher serving cell index It may have a higher priority than the CSI report for the index.

In another configuration, the transceiver module 724 may be further configured to receive, via radio resource control (RRC) signaling, a priority for a particular CSI process index or a CSI report with a particular serving cell index. In one example, the processing module 722 may be further configured to prioritize the CSI reports based on the combined CSI process index and serving cell index. A CSI report with a lower combined CSI process index and serving cell index may have a higher priority than a CSI report with a higher combined CSI process index and serving cell index. In another example, the processing module may be further configured to assign a highest priority CSI process to the default CSI process. The default CSI process may have the lowest CSI process index for a plurality of CSI processes.

In another example, the processing module 722 multiplexes the Hybrid Automatic Repeat Request-Acknowledgment (HARQ-ACK) and CSI report and generates a CSI report with HARQ-ACK feedback bits and an optional scheduling request May be further configured to determine if the physical uplink control channel (PUCCH) format 3 payload matches the physical uplink control channel (PUCCH) format 3 payload. The transceiver module transmits HARQ-ACK feedback bits including any SR without a CSI report when the CSI report with HARQ-ACK feedback bits and any SR is inconsistent with the PUCCH format 3 payload, and transmits a HARQ-ACK And to send multiplexed HARQ-ACK feedback bits including any SR with a CSI report when the CSI report with feedback bits and any SR fits in the PUCCH Format 3 payload. In another configuration, the transceiver module may be further configured to transmit a plurality of non-colliding CSI reports for a physical uplink control channel (PUCCH) format. Each CSI report can use up to 11 CSI bits.

11 provides an illustration of an example of a wireless device, such as a user equipment (UE), mobile station (MS), mobile wireless device, mobile communication device, tablet, handset or other type of wireless device. A wireless device may include a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE) A macro node, a low power node (LPN), a radio relay station (RS), a radio equipment (RE) or other type of wireless wide area network (WWAN) Or one or more antennas configured to communicate with a transmitting station. The wireless device may be configured to communicate using at least one wireless communication standard, including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth and WiFi. The wireless device may communicate using separate antennas for each wireless communication standard or using shared antennas for multiple wireless communication standards. A wireless device may communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and / or a WWAN.

Figure 11 also provides an illustration of one or more speakers and microphone that may be used for audio input and output from a wireless device. The display screen may be a liquid crystal display (LCD) screen, or other type of display screen, such as an organic light emitting diode (OLED) display. The display screen may be configured as a touch screen. The touch screen may use capacitive, resistive or other types of touch screen technology. The application processor and graphics processor may be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port may also be used to provide the user with data input / output options. A non-volatile memory port may also be used to extend the memory capabilities of the wireless device. The keyboard may be integrated with the wireless device to provide additional user input or wirelessly connected to the wireless device. A virtual keyboard can also be provided using the touch screen.

The various techniques or specific aspects or portions thereof may be embodied in a program embodied in a type of medium such as floppy diskettes, CD-ROMs, hard drives, non-volatile computer readable storage media or any other machine- Code (i. E., Instructions), wherein when the program code is loaded into a machine such as a computer and executed by the machine, the machine becomes an apparatus executing various techniques. The circuitry may include hardware, firmware, program code, executable code, computer instructions and / or software. Non-volatile computer-readable storage medium may be a computer-readable storage medium that contains no signals. When executing the program code on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one Output device. Volatile and nonvolatile memory and / or storage elements may be RAM, EPROM, flash drive, optical drive, magnetic hard drive, solid state drive or other medium for storing electronic data. The node and the wireless device may also include a transceiver module, a counter module, a processing module and / or a clock module or a timer module. One or more programs that may implement or use the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high-level procedure or object-oriented programming language to communicate with a computer system. However, the program (s) may be implemented in assembly or machine language, if desired. However, the language is a compiled or interpreted language and can be combined with hardware implementations.

It should be understood that many of the functional units described herein have been labeled as modules to more particularly emphasize the implementation independence of the units themselves. For example, the module may be implemented as a hardware circuit that includes custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors or other discrete components . The modules may also be implemented with programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, and the like.

The modules may also be implemented in software to be executed by various types of processors. A module of executable code that is identified may comprise, for example, one or more physical or logical blocks of computer instructions, for example, organized into objects, procedures, or functions. Nonetheless, executable ones of the identified modules do not need to be physically co-located, but when combined logically, include heterogeneous instructions that contain the module and are stored in different locations that achieve the stated purpose for the module can do.

Indeed, a module of executable code may be single instructions or multiple instructions, and may even be distributed among different programs, across different code segments, and across multiple memory devices. Similarly, operational data may be identified and illustrated within the modules herein, implemented in any suitable form, and organized within any suitable type of data structure. Operational data may be aggregated as a single data set or distributed across different locations, including spanning different storage devices, and may exist, at least in part, as electronic signals only on the system or network. The modules may be passive or active, including agents operable to perform the desired functions.

Throughout this specification, "an example" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present invention. Therefore, the phrases "in one embodiment " appearing at various places throughout this specification are not necessarily all referring to the same embodiment.

As used herein, a plurality of items, structural elements, components and / or materials may be presented in a common list for convenience. However, these lists must be interpreted as if each member of the list is individually identified as a distinct and unique member. Therefore, any individual member of such a list must not be interpreted as being substantially equivalent to any other member of the same list based solely on its own presentation in the common group, unless indicated otherwise. In addition, various embodiments and examples of the present invention may be referred to herein with alternatives to other elements of the invention. It is to be understood that such embodiments, examples and alternatives should not, in fact, be construed as mutually exclusive equivalents, but should be construed as separate and proprietary expressions of the present invention.

Moreover, the features, structures, or characteristics described may be combined in any suitable manner in one or more embodiments. In the following description, specific details are set forth, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the invention. However, those skilled in the art will recognize that the invention may be practiced without one or more of the details set forth, or with other methods, components, layouts, and the like. In other instances, well-known structures, materials, or operations are not shown or described in detail in order to avoid obscuring aspects of the present invention.

Although the foregoing examples illustrate the principles of the invention in one or more specific applications, many modifications in form, usage, and implementation details, without departing from the spirit of the invention and the principles of the invention, It will be apparent to those skilled in the art that the present invention may be practiced. Accordingly, it is not intended that the invention be limited except as by the appended claims.

Claims (20)

1. An apparatus of a user equipment (UE) reporting periodic channel state information (CSI)
The apparatus comprising one or more processors and a memory,
Wherein the one or more processors and memories comprise:
Each CSI report comprising a CSI process index (CSIProcessIndex) and a plurality of CSIs with a serving cell index (ServCellIndex) of a plurality of serving cell indices Corresponding to the physical uplink control channel (PUCCH) reporting type of the processes,
Determining a different priority corresponding to each of the plurality of PUCCH reporting types,
Determining a first collision between CSI reports comprising a PUCCH reporting type having the same priority in the subframe among the plurality of CSI reports and determining a first collision among CSI reports having a minimum CSIProcessIndex in determining the first collision; Dropping the CSI report corresponding to all CSI processes except for < RTI ID = 0.0 >
Determining a second collision between the CSI reports containing the CSIProcessIndex having the same priority in the subframe among the retained CSI reports of the plurality of CSI reports after the determination of the first collision, 2 When the collision is determined, the CSI report corresponding to all ServCellIndexes except for the CSI report having the minimum ServCllIndex is dropped,
configured to multiplex hybrid automatic repeat request-acknowledgment (HARQ-ACK) feedback bits with at least one non-colliding CSI report of the non-dropped CSI reports for transmission to the eNodeB
Device.
The method according to claim 1,
Wherein the one or more processors and the memory are further configured to determine whether the at least one non-colliding CSI report multiplexed with the HARQ-ACK feedback bits and any scheduling request (SR) conforms to a payload of PUCCH format 3 Constituted
Device.
3. The method of claim 2,
Collision CSI report with HARQ-ACK feedback bits and any SR does not fit into the payload of the PUCCH Format 3, the at least one non- A transceiver module configured to transmit HARQ-ACK feedback bits
≪ / RTI >
3. The method of claim 2,
Collision CSI report with HARQ-ACK feedback bits and any SR fits into the payload of the PUCCH Format 3, includes any SRs multiplexed with the at least one non-colliding CSI report The HARQ-ACK feedback bits to transmit the HARQ-ACK feedback bits
≪ / RTI >
The method according to claim 1,
The UE is configured to operate in a transmission mode (TM) 10 used in a coordinated multipoint (CoMP) scenario and in a carrier aggregation (CA)
Device.
The method according to claim 1,
A CSI report on a particular ServCellIndex with a lower CSIProcessIndex has a higher priority than a CSI report on the particular ServCellIndex with a higher CSIProcessIndex than the lower CSIProcessIndex
Device.
The method according to claim 1,
A CSI report on a particular CSIProcessIndex with a lower ServCellIndex has a higher priority than a CSI report on the particular CSIProcessIndex with a ServCellIndex higher than the lower ServCellIndex
Device.
The method according to claim 1,
The PUCCH reporting type may be one of the PUCCH reporting types 1, 1a, 2, 2b, 2c, or 4,
The PUCCH reporting type may be one of the PUCCH reporting types 3, 5, or 6
Device.
A user equipment (UE) operable to report periodic channel state information (CSI)
One or more antennas in communication with an evolved Node B (eNodeB)
An application processor,
The application processor,
Each CSI report comprising a CSI process index (CSIProcessIndex) and a plurality of CSIs with a serving cell index (ServCellIndex) of a plurality of serving cell indices Corresponding to the Physical Uplink Control Channel (PUCCH) reporting type of the processes,
Determining a different priority corresponding to each of the plurality of PUCCH reporting types,
Determining a first collision between CSI reports comprising a PUCCH reporting type having the same priority in the subframe among the plurality of CSI reports and determining a first collision among CSI reports having a minimum CSIProcessIndex in determining the first collision; The CSI report corresponding to all the CSI processes except for,
Determining a second collision between the CSI reports containing the CSIProcessIndex having the same priority in the subframe among the retained CSI reports of the plurality of CSI reports after the determination of the first collision, 2 When the collision is determined, the CSI report corresponding to all ServCellIndexes except for the CSI report having the minimum ServCllIndex is dropped,
Preparing at least one non-colliding CSI report from the non-dropped CSI reports,
And to multiplex the hybrid automatic repeat request (HARQ-ACK) feedback bits with at least one non-colliding CSI report of the non-dropped CSI reports for transmission to the eNodeB
User Equipment (UE).
10. The method of claim 9,
The application processor,
Determining if the at least one non-colliding CSI report with HARQ-ACK feedback bits and any scheduling request (SR) matches a payload of PUCCH format 3,
Collision CSI report with HARQ-ACK feedback bits and any SR does not fit into the payload of the PUCCH Format 3, the at least one non- Preparing to transmit HARQ-ACK feedback bits to the eNodeB,
Collision CSI report with HARQ-ACK feedback bits and any SR fits into the payload of the PUCCH Format 3, includes any SRs multiplexed with the at least one non-colliding CSI report To prepare for sending the HARQ-ACK feedback bits to the eNodeB
User Equipment (UE).
10. The method of claim 9,
The UE is configured to operate in a Cooperative Multipoint (CoMP) scenario and in a Transport Mode (TM) 10 used in a Carrier Acceptance (CA)
User Equipment (UE).
10. The method of claim 9,
A CSI report on a particular ServCellIndex with a lower CSIProcessIndex has a higher priority than a CSI report on the particular ServCellIndex with a higher CSIProcessIndex than the lower CSIProcessIndex
User Equipment (UE).
10. The method of claim 9,
A CSI report on a particular CSIProcessIndex with a lower ServCellIndex has a higher priority than a CSI report on the particular CSIProcessIndex with a ServCellIndex higher than the lower ServCellIndex
User Equipment (UE).
10. The method of claim 9,
The PUCCH reporting type may be one of the PUCCH reporting types 1, 1a, 2, 2b, 2c, or 4,
The PUCCH reporting type may be one of the PUCCH reporting types 3, 5, or 6
User Equipment (UE).
10. The method of claim 9,
The UE comprises at least one of an antenna, a touch-sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, an internal memory, a non-volatile memory port,
User Equipment (UE).
At least one machine-readable storage medium comprising instructions for reporting periodic channel state information (CSI)
The instructions, when executed,
Generating a plurality of CSI reports for a serving cell for transmission in a subframe using one or more processors of a user equipment (UE), each CSI report comprising a CSI process index (CSIProcessIndex) and a plurality of serving cells Corresponding to a Physical Uplink Control Channel (PUCCH) reporting type among a plurality of CSI processes having a serving cell index (ServCellIndex) of indices,
Using the one or more processors of the UE to determine a different priority corresponding to each of a plurality of PUCCH reporting types;
Using the one or more processors of the UE to determine, among the plurality of CSI reports, a first collision between CSI reports comprising a PUCCH reporting type having the same priority in the subframe, Dropping a CSI report corresponding to all CSI processes except a CSI process having a minimum CSIProcessIndex in determining a collision;
Using the one or more processors of the UE to generate a second collision between the CSI reports containing the CSIProcessIndex having the same priority in the subframe among the retained CSI reports of the plurality of CSI reports, 1 < / RTI > collision, dropping a CSI report corresponding to all ServCellIndexes except a CSI report having a minimum ServCellIndex at the time of determining the second collision,
Using the one or more processors of the UE to prepare at least one non-colliding CSI report from the non-dropped CSI reports,
Using the one or more processors of the UE, multiplexing at least one non-colliding CSI report of the non-dropped CSI reports and hybrid automatic repeat request-acknowledgment (HARQ-ACK) feedback bits for transmission to the eNodeB Perform
At least one machine-readable storage medium.
17. The method of claim 16,
When executed,
Determining if the at least one non-colliding CSI report with HARQ-ACK feedback bits and any scheduling request (SR) matches a payload of PUCCH format 3;
Collision CSI report with HARQ-ACK feedback bits and any SR does not fit into the payload of the PUCCH Format 3, the at least one non- Preparing to transmit HARQ-ACK feedback bits to the eNodeB;
Collision CSI report with HARQ-ACK feedback bits and any SR fits into the payload of the PUCCH Format 3, includes any SRs multiplexed with the at least one non-colliding CSI report Preparing to transmit the HARQ-ACK feedback bits to the eNodeB
The computer program product further comprising instructions for: < Desc / Clms Page number 18 >
17. The method of claim 16,
The UE is configured to operate in a Cooperative Multipoint (CoMP) scenario and in a Transport Mode (TM) 10 used in a Carrier Acceptance (CA)
At least one machine-readable storage medium.
17. The method of claim 16,
A CSI report on a particular ServCellIndex with a lower CSIProcessIndex has a higher priority than a CSI report on the particular ServCellIndex with a higher CSIProcessIndex than the lower CSIProcessIndex
At least one machine-readable storage medium.
17. The method of claim 16,
A CSI report on a particular CSIProcessIndex with a lower ServCellIndex has a higher priority than a CSI report on the particular CSIProcessIndex with a ServCellIndex higher than the lower ServCellIndex
At least one machine-readable storage medium.

Images