PRIORITY CLAIM

[0001] This application claims the benefit of priority to U.S. Patent

Application Serial No. 14/741,233, filed June 16, 2015, which claims the benefit of priority to U.S. Provisional Patent Application Serial No. 62/084,997, filed November 26, 2014, and U.S. Provisional Patent Application Serial No.

62/081,281, filed November 18, 2014, each of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments pertain to radio access networks. Some

embodiments relate to aperiodic channel state information (CSI) processing and reporting in cellular networks, such as Long Term Evolution (LTE) and LTE advanced (LTE-A) networks.

BACKGROUND

[0003] Current issues with communicating data over a wireless network can include low throughput, frequent handovers, handover failures, inefficient offloads, and service interruptions.

[0004] Dual connectivity in an LTE network can significantly improve per-user throughput, reduce handovers, and reduce handover failures by allowing a user to be connected simultaneously to a master cell group and a secondary cell group via a macro evolved Node B (eNB) and a small cell eNB.

[0005] With regards to low throughput, dual connectivity can increase per-user throughput by aggregating radio resources from at least two eNBs.

Additionally, throughput can be increased by transmitting or receiving multiple streams and dynamically adapting to the best radio conditions of multiple cells. Also, small cell eNBs can provide additional capacity for user equipments (UEs) having multiple radio connections.

[0006] Moreover, moving UEs suffer frequent handover failure, inefficient offload, and service interruption. The consequences are more severe if the UE's velocity is higher and cell coverage is smaller. Dual connectivity can reduce the handover failure rate by maintaining the macro eNB (e.g., primary cell) connection as the coverage layer. Dual connectivity also helps in load balancing between the macro eNB and the small cell eNB (e.g., secondary cell).

[0007] Furthermore, dual connectivity can reduce signaling overhead towards the core network due to frequent handover. For example, signaling overhead can be reduced by not issuing handover operations as long as the UE is within macro coverage.

[0008] However, dual connectivity can impose several technical challenges.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] FIG. 1 is a functional diagram of a 3rd Generation Partnership Project (3GPP) network, in accordance with some embodiments;

[0010] FIG. 2 is a functional diagram of a User Equipment (UE), in accordance with some embodiments;

[0011] FIG. 3 is a functional diagram of an Evolved Node B (eNB), in accordance with some embodiments;

[0012] FIG. 4 illustrates an example of a heterogeneous network for a dual connectivity implementation, in accordance with some embodiments;

[0013] FIG. 5 illustrates an example scenario of dual connectivity implementation, in accordance with some embodiments;

[0014] FIG. 6 illustrates an example of channel state information (CSI) attributes used for prioritizing CSI process calculations, in accordance with some embodiments; [0015] FIG. 7 illustrates the operation of a method performed by a UE for calculating prioritized CSI processes for a CSI report based on two CSI aperiodic requests received in the same subframe; and

[0016] FIG. 8 illustrates the operation of a method performed by an eNB for selecting a transmission mode based on the CSI report received from the UE, in accordance with some embodiments.

DETAILED DESCRIPTION [0017] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0018] In this disclosure, embodiments are often discussed with reference to macro eNBs and small cell eNBs. A small cell eNB can be a pico eNB. Additionally, various embodiments disclosed herein are applicable in other settings with other terminology. For example, a macro eNB can be denoted as an "anchor eNB," "primary eNB," or "master eNB," while a small cell eNB can be denoted as an "assisting eNB," "secondary eNB," or "slave eNB".

[0019] FIG. 1 is a functional diagram of a 3GPP network, in accordance with some embodiments. The network comprises a radio access network (RAN) (e.g., as depicted, the E-UTRAN or evolved universal terrestrial radio access network) 100 and a core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together through an SI interface 1 15. For the sake of convenience and brevity, only a portion of the core network 120, as well as the RAN 100, is shown.

[0020] The core network 120 includes a mobility management entity (MME) 122, a serving gateway (serving GW) 124, and a packet data network gateway (PDN GW) 126. The RAN 100 includes Evolved Node-Bs (eNBs) 104 (which can operate as base stations) for communicating with User Equipments (UEs) 102. The eNBs 104 can include macro eNBs and low power (LP) eNBs, such as micro eNBs.

[0021] The MME 122 is similar in function to the control plane of legacy

Serving GPRS Support Nodes (SGSN). The MME 122 manages mobility aspects in access, such as gateway selection and tracking area list management. The serving GW 124 terminates the interface toward the RAN 100, and routes data packets between the RAN 100 and the core network 120. In addition, the serving GW 124 may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes. The PDN GW 126 terminates an SGi interface toward a packet data network (PDN). The PDN GW 126 routes data packets between the core network 120 and the external PDN, and may be a key node for policy enforcement and charging data collection. It can also provide an anchor point for mobility with non-LTE accesses. The external PDN can be any kind of IP network, as well as an IP Multimedia Subsystem (IMS) domain. The PDN GW 126 and the serving GW 124 may be implemented in one physical node or separate physical nodes.

[0022] The eNBs 104 (macro and micro) terminate the air interface protocol and may be the first point of contact for a UE 102. In some

embodiments, an eNB 104 can fulfill various logical functions for the RAN 100, including but not limited to RNC (radio network controller) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In accordance with embodiments, the UEs 102 may be configured to communicate orthogonal frequency- division multiplexing (OFDM) communication signals with an eNB 104 over a multicarrier communication channel in accordance with an orthogonal frequency- division multiple access (OFDMA) communication technique. The OFDM signals may comprise a plurality of orthogonal subcarriers.

[0023] The S 1 interface 1 15 is the interface that separates the RAN 100 and the core network 120. It is split into two parts: the SI -MME, which carries data traffic between the eNBs 104 and the serving GW 124, and the Sl-MME, which is a signaling interface between the eNBs 104 and the MME 122. The X2 interface is the interface between eNBs 104. The X2 interface comprises two parts, the X2-C and X2-U. The X2-C is the control plane interface between the eNBs 104, while the X2-U is the user plane interface between the eNBs 104.

[0024] In cellular networks, LP cells are typically used to extend coverage to indoor areas where outdoor signals do not reach well, or to add network capacity in areas with very dense phone usage, such as train stations. As used herein, the term "low power (LP) eNB" refers to any suitable relatively low power eNB for implementing a narrower cell (narrower than a macro cell), such as a femtocell, a picocell, or a micro cell. Femtocell eNBs are typically provided by a mobile network operator to its residential or enterprise customers. A femtocell is typically the size of a residential gateway or smaller and generally connects to the user's broadband line. Once plugged in, the femtocell connects to the mobile operator's mobile network and provides extra coverage in a typical range of 30 to 50 meters for residential femtocells. Thus, an LP eNB might be a femtocell eNB since it is coupled through the PDN GW 126. Similarly, a picocell is a wireless communication system typically covering a small area, such as in-building (offices, shopping malls, train stations, etc.), or more recently in-aircraft. A picocell eNB can generally connect through the X2 link to another eNB such as a macro eNB through its base station controller (BSC)

functionality. Thus, an LP eNB may be implemented with a picocell eNB since it is coupled to a macro eNB via an X2 interface. Picocell eNBs or other LP eNBs may incorporate some or all functionality of a macro eNB. In some cases, an LP eNB may be referred to as an "access point base station" or "enterprise femtocell."

[0025] In some embodiments, a downlink resource grid may be used for downlink transmissions from an eNB 104 to a UE 102, while uplink

transmissions from the UE 102 to the eNB 104 may utilize similar techniques. The grid may be a time-frequency grid, called a "resource grid" or "time- frequency resource grid," which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is common for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid correspond to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time- frequency unit in a resource grid is denoted as a "resource element." Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements in the frequency domain and may represent the smallest quanta of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks. With particular relevance to this disclosure, two of these physical downlink channels are the physical downlink shared channel and the physical downlink control channel.

[0026] The physical downlink shared channel (PDSCH) carries user data and higher-layer signaling to a UE 102. The physical downlink control channel (PDCCH) or enhanced downlink control channel (EPDCCH) carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It also informs the UE 102 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to UEs 102 within a cell) is performed at the eNB 104 based on channel quality information fed back from the UEs 102 to the eNB 104, and then the downlink resource assignment information is sent to a UE 102 on the control channel (PDCCH) used for (assigned to) the UE 102.

[0027] The PDCCH uses control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols are first organized into quadruplets, which are then permuted using a sub-block inter-leaver for rate matching. Each PDCCH is transmitted using one or more of these CCEs, where each CCE corresponds to nine sets of four physical resource elements known as resource element groups (REGs). Four quadrature phase-shift keying (QPSK) symbols are mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of downlink control information (DO) and the channel condition. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level L=l, 2, 4, or 8).

[0028] FIG. 2 is a functional diagram of a User Equipment (UE) 200, in accordance with some embodiments. FIG. 3 is a functional diagram of an Evolved Node B (eNB) 300, in accordance with some embodiments. It should be noted that in some embodiments, the eNB 300 can be a stationary non-mobile device. The UE 200 can be a UE 102 as depicted in FIG. 1, while the eNB 300 can be an eNB 104 as depicted in FIG. 1. The UE 200 can include physical layer circuitry (PHY) 202 for transmitting and receiving signals to and from the eNB 300, other eNBs, other UEs, or other devices, using one or more antennas 201. The eNB 300 can include physical layer circuitry (PHY) 302 for transmitting and receiving signals to and from the UE 200, other eNBs, other UEs, or other devices, using one or more antennas 301.

[0029] The UE 200 can also include medium access control layer (MAC) circuitry 204 for controlling access to the wireless medium, while the eNB 300 can also include medium access control layer (MAC) circuitry 304 for controlling access to the wireless medium.

[0030] The UE 200 can also include processing circuitry 206 and memory 208 arranged to perform the operations described herein, and the eNB 300 can also include processing circuitry 306 and memory 308 arranged to perform the operations described herein.

[0031] The eNB 300 can also include one or more interfaces 310, which can enable communication with other components, including other eNBs 104 (FIG. 1), components in the core network 120 (FIG. 1), or other network components. In addition, the interfaces 310 may enable communication with other components that may not be shown in FIG. 1, including components external to the network. The interfaces 310 may be wired, wireless, or a combination thereof.

[0032] The antennas 201, 301 may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of radio frequency (RF) signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas 201, 301 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[0033] In some embodiments, mobile devices or other devices described herein may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or another device, including wearable devices that may receive and/or transmit information wirelessly. In some embodiments, the mobile device or other device can be a UE or an eNB configured to operate in accordance with 3GPP standards. In some embodiments, the mobile device or other device may be configured to operate according to other protocols or standards, including IEEE 802.1 1 or other IEEE standards. In some

embodiments, the mobile device or other device may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0034] Although the UE 200 and the eNB 300 are each illustrated as having several separate functional elements, one or more of the functional elements can be combined and can be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements can comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio- frequency integrated circuits (RFICs), and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements can refer to one or more processes operating on one or more processing elements.

[0035] Embodiments can be implemented in one or a combination of hardware, firmware, and software. Embodiments can also be implemented as instructions stored on a computer-readable storage device, which can be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device can include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device can include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. Some embodiments can include one or more processors that can be configured with instructions stored on a computer-readable storage device.

[0036] In some embodiments, the UE 200 can be configured to receive

OFDM communication signals over a multicarrier communication channel in accordance with an OFDMA communication technique. The OFDM signals can comprise a plurality of orthogonal subcarriers. In some broadband multicarrier embodiments, the eNB 300 can be part of a broadband wireless access (BWA) communication network, such as a Worldwide Interoperability for Microwave Access (WiMAX) communication network, a 3rd Generation Partnership Project (3 GPP) Universal Terrestrial Radio Access Network (UTRAN) Long-Term- Evolution (LTE) network, or a Long-Term-Evolution (LTE) communication network, although the scope of this disclosure is not limited in this respect. In these broadband multicarrier embodiments, the UE 200 and the eNB 300 can be configured to communicate in accordance with an OFDMA technique.

[0037] FIG. 4 illustrates an example of a heterogeneous network 400 for a dual connectivity implementation, according to some embodiments. FIG. 4 illustrates an example of different deployments that includes a large cell representing a macro cell 410. The heterogeneous network 400 can also include a small cell 420 (e.g., micro cell) in the same frequency as the macro layer, which includes the macro cell 410. Additionally, the heterogeneous network 400 can include small cells 430 deployed in clusters and small cells deployed in non- clusters (e.g., spread in a city) in a frequency layer different from that of the macro cell 410. Furthermore, the heterogeneous network 400 can include beamforming small cells 440 in a different radio access technology (RAT) which are deployed with beamforming ability.

[0038] Accordingly, in such a heterogeneous network 400, dual connectivity can allow the UE 102 to connect simultaneously to the macro cell 410 and the small cells 430 in a frequency layer different from the macro cell 410.

[0039] As previously mentioned, dual connectivity in an LTE network can significantly improve per-user throughput, reduce handovers, and reduce handover failures by allowing a user to be connected simultaneously to the macro cell 410 and small cells (e.g., small cell 420, small cell 430, and/or small cell 440).

[0040] FIG. 5 illustrates an example of a scenario 500 of a dual connectivity implementation, in accordance with some embodiments. In dual connectivity, the serving cells are operated in different eNBs. For example, the primary cell is served from a macro cell 510 and a secondary cell is served from a small cell (e.g., a first small cell 520, and/or a second small cell 530). In some instances, the small cell can be a pico cell or a femto cell. For example, the first small cell 520 is a first pico cell, and the second small cell 530 is a second pico cell.

[0041] As previously mentioned, one of the motivations of dual connectivity is to avoid frequent handovers in heterogeneous deployment, as illustrated in FIG. 4. As shown in the scenario 500, the UE 102 can move within a coverage area 560 of the macro cell 510. Since the coverage area (not pictured) of each of the small cells (e.g., coverage of first small cell 520 and second small cell 530) is smaller than that of the macro cell 510, the UE 102 may need to be handed over to the macro cell 510 or another small cell if the UE is connected to the small cell only. On the other hand, if the UE is connected to the macro cell 510, handover is not required, but offloading to the small cell is not provided. To achieve offloading and avoid the frequent handover, carrier aggregation can be performed.

[0042] With carrier aggregation, the UE can be served by both the macro cell 510 operating at a first frequency 540, and the small cell (e.g., first small cell

520, and/or second small cell 530) operating at a second frequency 550. For example, the primary cell can be the macro cell 510 and the secondary cell can be the small cell (e.g., first small cell 520, second small cell 530).

[0043] For example, at Ti, the UE 102, being within the coverage area

(e.g., coverage area 560) of the macro cell 510, can be served by the macro cell 510 as the primary cell. Then at T ₂ , when the UE 102 is within the coverage area of the macro cell 510 and the first small cell 520, the first small cell 520 can be added as a secondary cell while the macro cell 510 is maintained as the primary cell. Additionally, at T3, when the UE 102 is within the coverage area of the macro cell 510 but moves out of the coverage area of the first small cell 520, the first small cell 520 can be removed as the secondary cell while the macro cell 510 is maintained as the primary cell. Subsequently at T ₄ , when the UE 102 is within the coverage area of the macro cell 510 and the second small cell 530, the second small cell 530 can be added as a secondary cell while the macro cell 510 is maintained as the primary cell. Finally at T5, when the UE 102 is within the coverage area of the macro cell 510 but moves out of the coverage area of the second small cell 530, the second small cell 530 can be removed as the secondary cell while the macro cell 510 is maintained as the primary cell.

[0044] In the example in FIG. 5, the primary cell (e.g., macro cell 510) can be responsible for mobility management, and therefore the UE 102 does not need to be handed over as long as the UE 102 is moving within the coverage area of the macro cell 510. Additionally, the secondary cell (e.g., first small cell 520, second small cell 530) can be used for data transmission, and the UE can take advantage of offloading to the secondary cell. The change from the first small cell 520 to second small cell 530 may be supported with secondary cell addition or removal, instead of handover.

[0045] In the scenario illustrated in FIG. 5, an example of a difference between dual connectivity and LTE Rel- 10 carrier aggregation is illustrated. For example, in dual connectivity, the macro cell (e.g., macro cell 510) and the small cell (e.g., first small cell 520, second small cell 530) are served by different eNBs 104 and the two cells are connected through an X2 interface. In LTE Rel- 10 carrier aggregation, it can be assumed that all serving cells are served by the same eNB 104.

[0046] Given that the macro cell (e.g., macro cell 510) and the small cell (e.g., first small cell 520, second small cell 530) are served by different eNBs 104, it is possible that the UE 102 receives more than one aperiodic CSI request in the same subframe from both the macro cell and the small cell. FIGS. 6-8 illustrate techniques for prioritizing and calculating CSI processes when multiple aperiodic CSI requests are received in the same subframe.

[0047] Additionally, in some embodiments, LTE carrier aggregation can be deployed on top of dual connectivity. For example, the macro and/or pico eNB 104 may aggregate multiple component carriers (or cells) in downlink and/or uplink channels.

Channel State Information (CSD Reporting

[0048] LTE-Advanced (LTE-A) can support two types of CSI reporting, which are periodic and aperiodic reporting. Periodic CSI reporting may be mainly used to indicate the channel quality of the downlink channel at the UE 102 on a long-term basis. Periodic CSI can be provided by the UE 102 in accordance with a predefined reporting time schedule configured by the serving cell using higher-layer signaling (e.g. Radio Resource Control (RRC)) and usually has low overhead.

[0049] In contrast, aperiodic CSI reporting can be used to provide larger and more detailed reporting in a single reporting instance based on a dynamic CSI request triggered by the serving cell using a CSI request filed in the downlink control information (DCI). The DCI can include a Physical Downlink Control Channel (PDCCH) or an enhanced Physical Downlink Control Channel (EPDCCH).

[0050] In transmission mode 10, multiple CSI reports corresponding to multiple CSI processes on the same serving frequency can be requested by the eNB 104 in accordance with the Table 7.2.1-1B defined in TS 36.213 Rel-1 1 (reproduced below). The set of CSI processes for reporting corresponding to CSI request fields "01 ", " 10", and " 1 1 " are configured using RRC signaling.

Table 7.2.1-1B: CSl Request field for PDCCH/EPDCCH with uplink DCI format in UE specific search space

Value of CSl

Description

request Held

'00' No aperio die CSl report is triggered

Aperiodic CSl report is triggered for a set of CSl process(es) configurec by higher layers for serving cell C

Aperiodic CSl report is triggered for a 1 ^st set of CSl process(es ) configured by higher layers

, j j , Aperiodic CSl report is triggered for a 2 ^nd set of CSl

process(es ) configured by higher layers

[0051] In carrier aggregation mode, multiple CSl reports corresponding to multiple downlink cells can be requested by the eNB 104 in accordance with the Table 7.2.1 - lA defined in TS 36.213 Rel- 10 (reproduced below). The set of serving cells for reporting corresponding to CSl request fields "10" and " 1 1" are configured using RRC signaling.

Table 7.2.1-lA: CSl Request field for PDCCH/EPDCCH with uplink DCI format in UE specific search space

[0052] Given that the UE 102 is not expected to receive more than one

CSl request in one downlink subframe as defined in Section 7.2.1 of TS 36.21 1 , the maximum number of CSl reports generated by the UE 102 in one subframe can be limited to five.

[0053] In the case of carrier aggregation, the maximum number of CSl requests is five due to an ideal backhaul link and a limit of one CSl request per downlink subframe. As previously mentioned, In LTE Rel- 10 carrier aggregation, it can be assumed that all serving cells are served by the same eNB 104. [0054] However, with dual connectivity, the macro cell (e.g., macro cell

510) and the small cell (e.g., first small cell 520, second small cell 530) are served by different eNBs 104 and two cells are connected through an X2 interface. Therefore, it can be possible for more than one CSl request to be sent in one downlink subframe. Additionally, with regards to dual connectivity, which can have a non-ideal backhaul link with high and variable delays, it can be difficult to ensure that only one CSl request is sent in each downlink subframe.

[0055] Furthermore, due to the CSl computational complexity, it is desirable to keep CSl calculation at the UE 102 at a reasonable level. Therefore, in some instance, a predetermined number of CSl reports to be calculated by the UE 102 can be set. For example, the predetermined number of CSl reports can be set to five, which is the existing constraint on the maximum number of CSl reports. In this disclosure, several embodiments are set forth that limit the number of CSl processes to be computed and reported in any subframe to five. For example, the CSl processes are prioritized and the top five CSl processes are calculated by the UE 102.

[0056] According to some embodiments, various aperiodic CSl reporting processes disclosed herein enable a reduction in CSl computational complexity at the UE 102 when dual connectivity is used.

[0057] FIG. 6 illustrates an example of CSl attributes 600, in accordance with some embodiments. For example, when more than five CSl processes are requested during the same subframe, the CSl attributes 600 can be used to select (e.g., prioritize) the top five CSl processes for the UE 102 to calculate. The CSl attributes can include, but are not limited to, a cell group index 610, a CSl process index 620, a component carrier (CC) index 630, and a CSl subframe index 640. The cell group index 610 can include an index value corresponding to a macro cell 612 and an index value corresponding to a small cell 614.

[0058] In a first set of embodiments, when simultaneous aperiodic CSl requests are received by the UE 102 from a primary eNB and a secondary eNB, the CSl (e.g., CSl process) computational priorities may be defined based on predetermined rules.

[0059] For example, For N total CSl processes requested in a given subframe, with N > 5, the UE 102 may update a predetermined number (e.g., five) of top priority CSl processes. Additionally, the remaining (e.g., N-5 when the predetermined number is five) lower-priority CSl processes may not be updated. In some instances, a default value can be used for the remaining (e.g., non-updated) CSl processes. Alternatively, a previously calculated value can be used for the remaining CSl processes.

[0060] The CSl process priority list can be defined based on the CSl attributes 600, such as the cell group index 610 (e.g., Type of eNB), the CSl process index 620, the CC index 630, and the CSl subframe index 640.

[0061] Examples of possible ordering of the priorities (starting with the higher priority) can be defined as follows:

• Cell group index 610 > CSl process index 620 > CC index 630 > CSl subframe index 640;

• CSl process index 620 > Cell group index 610 > CC index 630 > CSl subframe index 640;

· CSl process index 620 > CC index 630 > Cell group index 610 > CSl subframe index 640

• CSl process index 620 > CC index 630 > CSl subframe index 640 > Cell group index 610

[0062] In one example, a lower cell group index 610 value (e.g., index value corresponding to a small cell 614) can have a higher priority for CSl computation than a higher cell group index 610 value (e.g., index value corresponding to a macro cell 612). Alternatively, in another example, a lower cell group index 610 value can have a lower priority for CSl computation than a higher cell group index 610 value. In some embodiments, the macro cell 612 may be included in a cluster of macro cells that operates in a different frequency band than the small cell 614 or another macro cell.

[0063] In some instances, all CSl requests for CSl processes may be reported, but not all of them may be updated. The non-updated CSl reports can be a previously reported CSl report based on previously received aperiodic CSl data or a default value. For example, the default values can be a channel quality indicator (CQI) with an index value of "0," which can correspond to an indication of the UE 102 being out of range. Additionally, a CQI with an index value of "0" can indicate that the UE 102 has not received any usable LTE signals. Furthermore, the aperiodic CSI configuration (i.e., the configuration of CSI request fields for different UEs 102) may be exchanged over an X2 interface between the primary eNB and the secondary eNB.

[0064] In a second set of embodiments, the sum of the maximum number of CSI processes configured for each CSI request field by the primary eNB and the secondary eNB may not exceed a predetermined number (e.g., five) of CSI processes.

[0065] In a third set of embodiments, different CSI subframes may be used by the primary eNB and the secondary eNB for aperiodic CSI triggering. The subframes used for triggering by the primary eNB may not be used for aperiodic CSI triggering by the secondary eNB. The subframes can be coordinated between the primary eNB and the secondary eNB using bitmap signaling, which for the frequency division duplexing (FDD) case, may have a length of 40 bits.

[0066] FIG. 7 illustrates the operation of a method 700 for calculating

CSI for selected CSI processes, in accordance with some embodiments. As illustrated in FIGS. 5 and 6, multiple CSI requests can be received in the same subframe, which can result in more than five requested CSI processes needing to be calculated by the UE 102. In such cases, a selected subset of requested CSI processes are calculated based on the CSI attributes 600. Embodiments are not limited to these configurations, however, and some or all of the techniques and operations described herein may be applied to systems or networks that exclusively use macro cells or micro cells.

[0067] It is important to note that embodiments of the method 700 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 7. In addition, embodiments of the method 700 are not necessarily limited to the chronological order that is shown in FIG. 7. In describing the method 700, reference may be made to FIGS. 1-6, although it is understood that the method 700 may be practiced with any other suitable systems, interfaces, and components. For example, reference may be made to the scenario 500 in FIG. 5 (described earlier) for illustrative purposes, but the techniques and operations of the method 700 are not so limited. [0068] In addition, while the method 700 and other methods described herein may refer to eNBs 104 or UEs 102 operating in accordance with 3 GPP or other standards, embodiments of those methods are not limited to just those eNBs 104 or UEs 102 and may also be practiced by other mobile devices, such as a Wi-Fi access point (AP) or user station (STA). Moreover, the method 700 and other methods described herein may be practiced by wireless devices configured to operate in other suitable types of wireless communication systems, including systems configured to operate according to various IEEE standards such as IEEE 802.1 1.

[0069] At operation 710 of the method 700, the UE 102 receives, in a first subframe, a first aperiodic CSI request from a first cell group. The physical layer circuitry 202 (in FIG. 2) can receive the first aperiodic CSI request from an eNB (e.g., eNB 104). The first cell group can be served by a primary eNB. The first cell group can include the macro cell 510.

[0070] As described in Table 7.2.1- IB above, the request field value for the first aperiodic CSI request can be "01", "10", or "1 1" in the transmission mode 10.

[0071] As described in Table 7.2.1 - 1 A above, the request field value for the first aperiodic CSI request can be "10", or "1 1" in the carrier aggregation mode.

[0072] Dual connectivity in an LTE network allows the UE 102 to be connected simultaneously to a primary cell group and a secondary cell group via a primary eNB and a secondary eNB. As a result, in some instances, the UE 102 can receive more than one aperiodic CSI request in the same subframe. For example, the UE 102 can receive a CSI request from the primary eNB at operation 710 and another CSI request from the secondary eNB in the same subframe at operation 720.

[0073] At operation 720, the UE 102 receives, in the first subframe, a second aperiodic CSI request from a second cell group. The physical layer circuitry 202 can receive the second aperiodic CSI request from another eNB 104. The second cell group can be served by a secondary eNB. The second cell group can include the first small cell 520 or the second small cell 530. Additionally, the second cell group can operate at a different frequency than the first cell group.

[0074] As described in Table 7.2.1 -IB above, the request field value for the second aperiodic CSI request can be "01", "10", or "11" in the transmission mode 10.

[0075] As described in Table 7.2.1 - 1 A above, the request field value for the second aperiodic CSI request can be "10", or "1 1" in the carrier aggregation mode.

[0076] In some instances, the first aperiodic CSI request and the second aperiodic CSI request are received in the first subframe when the first aperiodic CSI request is received within 33 microseconds of the second aperiodic CSI request.

[0077] In one example, the first cell group includes a macro eNB and the second cell group includes a small cell eNB. In another example, the first cell group includes a small cell eNB and the second cell group includes a macro eNB. In yet another example, the first cell group and the second cell group can include different macro eNBs operating at different frequencies. In yet another example, the first cell group and the second cell group can include different small cell eNBs operating at different frequencies.

[0078] At operation 730, the UE 102 determines a number of requested

CSI processes corresponding to the first aperiodic CSI request and the second aperiodic CSI request. In some instances, the processing circuitry 206 (in FIG. 2) determines the number of requested CSI processes. The number of requested CSI processes can be determining by adding the number of CSI processes associated with the first aperiodic CSI request and the number of CSI processes associated with the second aperiodic CSI request. As previously mentioned, due to the CSI computational complexity, the number of CSI processes to be computed and reported in any subframe may be limited to predetermined number (e.g., five) of CSI processes.

[0079] At operation 740, the UE 102 selects a subset of the requested

CSI processes when the determined number of requested CSI processes is more than a predetermined number (e.g., five). For example, the UE 102 can select a subset of the requested CSI processes when there are more than five requested CSl processes. In some instances, the processing circuitry 206 selects the subset of CSl processes for updating (e.g., calculating). The number of requested CSl processes is determined at operation 730.

[0080] In some instances, the selected CSl processes comprise a total of five CSl processes. For example, the CSl processes are prioritized and the top five CSl processes are selected by the UE 102.

[0081] In some instances, the selected CSl processes comprise at least one fewer CSl process than the requested CSl processes. For example, when the number of requested CSl processes is seven, the number of selected CSl processes is 6 or less.

[0082] In some instances, the processing circuitry 206 is further configured to generate a priority list of the requested CSl processes based on CSl attributes. Additionally, the selecting of the subset of the requested CSl processes at operation 740 can be based on the priority list. The CSl attributes can include the CSl attributes 600 of FIG. 6. The CSl attributes 600 include the cell group index 610, the CSl process index 620, the CC index 630, and the CSl subframe index 640.

[0083] The priority list can be preset by a UE (e.g., UE 102) or an eNB

(e.g., eNB 104). In some instances, the CSl process index 620 can have a higher priority in the priority list than the CC index 630. In some instances, the CC index 630 can have a higher priority in the priority list than the CSl subframe index 640.

[0084] In some instances, a lower cell group index 610 may have a higher priority in the priority list than a higher cell group index 610.

Alternatively, the lower cell group index 610 may have a lower priority in the priority list than the higher cell group index 610. The lower cell group index 610 can correspond to a small cell eNB or secondary eNB. The higher cell group index 610 can correspond to a macro eNB or primary eNB.

[0085] At operation 750, the UE 102 calculates CSl for the selected CSl processes from operation 740. The processing circuitry 206 can calculate the CSl for each selected CSl process. As previously mentioned, a total of five CSl processes can be selected at operation 740, and therefore CSl for five processes can be calculated at operation 750. [0086] The calculated CSI can include a precoding matrix indicator value. As described in method 800, a transmission parameter that is set or transmitted by a eNB 104 can include a precoding weight for transmitting antennas of eNB that is based on the precoding matrix indicator value.

[0087] Additionally, the calculated CSI can include a Rank Indicator

(RI) value. The number of layers determined by the eNB 104 in method 800 is based on the RI value.

[0088] Furthermore, the calculated CSI can include a Channel Quality

Indicator (CQI) value. A modulation and coding scheme (MCS) determined by the eNB 104 in method 800 can be based on the CQI value.

[0089] In some instances, the method 700 can further include generating a first CSI report and a second CSI report. For example, the CSI reports can be generated using the processing circuitry 206. The first CSI report can include the calculated CSI, from operation 750, corresponding to the first aperiodic CSI request. The second CSI report can include the calculated CSI, from operation 750, corresponding to the second aperiodic CSI request.

[0090] Additionally, the method 700 can further include transmitting the first CSI report to the first cell group, and the second CSI report to the second cell group. As previously mentioned, the first cell group sent the first aperiodic CSI request at operation 710, and the second cell group sent the second aperiodic CSI request at operation 720. For example, the physical layer circuitry 202 can transmit the first CSI report to the first cell group, and transmit the second CSI report to the second cell group.

[0091] Furthermore, all of the requested CSI processes from the first and second aperiodic requests are included in the first CSI report or second CSI report, but CSI is only calculated for the CSI processes selected at operation 740.

[0092] In some instances, the processing circuitry 206 is further configured to access previously stored CSI for a remaining process, the remaining process being different from the CSI processes selected at operation 740. Additionally, the first CSI report or the second CSI report can include the accessed CSI for the remaining process. For example, a remaining CSI process is a CSI process that is not updated (e.g., calculated) at operation 750. The processing circuitry 206 can access the value of the remaining CSI process stored in the memory 208. The value can correspond to previously calculated CSI associated with the remaining CSI process.

[0093] In some instances, the processing circuitry 206 is further configured to generate generic CSI for the remaining process. As previously mentioned, the remaining process is different from the CSI processes selected at operation 740. Additionally, the generic CSI indicates that the remaining process has not been calculated. Furthermore, the first CSI report or the second CSI report can include the generic CSI for the remaining process. For example, the portion of the first CSI report associated with the remaining process includes a Channel Quality Indicator (CQI) value that is set to zero to indicate that the CQI has not been calculated.

[0094] In some instances, the processing circuitry 206 is further configured to generate a CSI report based on the calculated CSI for the selected processes. Additionally, the physical layer circuitry 202 is further configured to transmit the CSI report to the first cell group and the second cell group.

[0095] FIG. 8 illustrates the operation of a method 800 for selecting a transmission mode based on the calculated CSI, in accordance with some embodiments. It is important to note that embodiments of the method 800 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 8. In addition, embodiments of the method 800 are not necessarily limited to the chronological order that is shown in FIG. 8. In describing the method 800, reference may be made to FIGS. 1-7, although it is understood that the method 800 may be practiced with any other suitable systems, interfaces, and components.

[0096] In addition, while the method 800 and other methods described herein may refer to eNBs 104 or UEs 102 operating in accordance with 3 GPP or other standards, embodiments of those methods are not limited to just those eNBs 104 or UEs 102 and may also be practiced by other mobile devices, such as a Wi-Fi access point (AP) or user station (STA). Moreover, the method 800 and other methods described herein may be practiced by wireless devices configured to operate in other suitable types of wireless communication systems, including systems configured to operate according to various IEEE standards such as IEEE 802.1 1. [0097] The method 800 can be performed by an eNB 104 for selecting a transmission mode for a UE (e.g., UE 102) having dual connectivity in heterogeneous network.

[0098] At operation 810, the eNB 104 can send an aperiodic CSI request to a UE 102. In some instances, the physical layer circuitry 302 can send the CSI request.

[0099] In some instances, different CSI subframes may be used by the primary eNB and the secondary eNB for aperiodic CSI triggering. The subframes used for aperiodic CSI triggering by the primary eNB may not be used for aperiodic CSI triggering by the secondary eNB. The subframes can be coordinated between the primary eNB and the secondary eNB using bitmap signaling, which for the frequency division duplexing (FDD) case, may have a length of 40 bits. Additionally, each bit can correspond to a downlink subframe, where a "1" indicates that triggering may be used and a "0" indicates that triggering may not be used.

[00100] At operation 820, the PHY 302 of the eNB 104 can receive a CSI report based on the aperiodic request sent at operation 810. The CSI report can be generated and sent by the UE 102 using the method 700 in FIG. 7. In some instances, the physical layer circuitry 302 of the eNB 300 can receive the CSI report.

[00101] The CSI report can include CSI for selected CSI processes calculated at operation 750. Additionally, the CSI processes can be selected by the UE 102 at operation 740. Furthermore, the CSI report can include generic CSI for a remaining process. The remaining process can be a CSI process not selected at operation 740, but requested in the aperiodic CSI request sent at operation 810.

[00102] At operation 830, the eNB 104 can determine that the remaining

CSI process has not been calculated based on the generic CSI. In some instances, operation 830 can be performed by the processing circuitry 306 of the eNB 300.

[00103] At operation 840, the processing circuitry 306 of the eNB 104 can select a transmission parameter based on the calculated CSI for the selected CSI processes in the CSI report. In some instances, operation 840 can be performed by the processing circuitry 306 of the eNB 300. [00104] The transmission parameter(s) may be received at the UE 102.

The transmission parameters may be set or transmitted by one of the eNBs 104, such as the eNB 104 of the serving cell. Accordingly, the decision of the eNB 104 to indicate the transmission mode may be based at least partly on information included in the CSI report previously described.

[00105] In some instances, the transmission parameters include a precoding weight for transmitting antennas of eNB that is based on a precoding matrix indicator value in the calculated CSI for one of the selected CSI processes.

[00106] In some instances, the transmission parameters include a number of layers that is based on the Rank Indicator (RI) value in the calculated CSI for one of the selected CSI processes.

[00107] In some instances, the transmission parameters include a modulation and coding scheme (MCS) that is based on a Channel Quality Indicator (CQI) value in the calculated CSI for one of the selected CSI processes.

[00108] A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors to perform operations for reporting channel state information (CSI) in a cellular network is also disclosed herein. The operations may configure a UE to receive, in a first subfiame, a first aperiodic CSI request from a first cell group; receive, in the first subframe, a second aperiodic CSI request from a second cell group; determine a number of requested CSI processes corresponding to the first aperiodic CSI request and the second aperiodic CSI request; select a subset of the requested CSI processes when the determined number of requested CSI processes is more than five; calculate CSI for the selected CSI processes; generate a CSI report based on the calculated CSI for the selected CSI processes; and transmit the CSI report to the first cell group and the second cell group.

[00109] The Abstract is provided to comply with 37 C.F.R. Section 1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.