Patent Description:
Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Examples of such multiple-access networks include Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, and Single-Carrier FDMA (SC-FDMA) networks.

A wireless communication network may include a number of base stations (e.g., eNodeBs) that can support communication for a number of user equipments (UEs). A UE may communicate with a base station via the downlink and uplink.

To improve the performance of wireless communications, it may be desirable to aggregate component carriers (CCs) when communicating with a UE in order to increase the bandwidth, and thereby increase the bitrates. When such aggregation involves component carriers that originate from a same eNodeB or from collocated base stations (e.g., eNodeBs and/or access points (APs)), it may be possible to coordinate the operation of the aggregated component carriers through internal communications in the eNodeB or through fast connections between the collocated base stations. In other scenarios, however, the ability to coordinate the aggregation of component carriers becomes more challenging.

In view of the foregoing, it may be understood that there may be significant problems and shortcomings associated with current carrier aggregation technology, as described in documents <CIT>, 3GPP R2-<NUM>, 3GPP R2-<NUM>, 3GPP R2-<NUM>, 3GPP R2-<NUM>, 3GPP RAN2-83BIS and 3GPP TR <NUM>. Relatedly, document 3GPP R2-<NUM> describes user plane architecture, and document 3GPP R1-<NUM> describes FDD-TDD joint operation.

The present invention provides a solution as defined in the independent claims.

Aspects of the present disclosure relate generally to wireless communications, and more particularly, to techniques for using carrier aggregation in dual connectivity wireless communications. For example, techniques for using carrier aggregation when a wireless device is connected to non-collocated network entities are described herein. In dual connectivity wireless communications, a wireless device may be communicatively connected to more than one network entity (e.g., eNodeBs and/or access points (APs)).

In order to facilitate a fuller understanding of the present disclosure, reference is now made to the accompanying drawings, in which like elements are referenced with like numerals. These drawings should not be construed as limiting the present disclosure, but are intended to be illustrative only.

Various methods, apparatuses, devices, and systems are described for carrier aggregation when a wireless device is connected to more than one network entity (e.g., multiple connectivity). In some aspects, a wireless device (e.g., UE), may receive first configuration information to communicate with a first network entity (e.g., a master eNodeB, also referred to as an MeNodeB or MeNB) through a first primary cell of the first network entity (e.g., a master cell group primary cell or PCell). The wireless device may receive second configuration information to communicate with a second network entity (e.g., a secondary eNodeB, also referred to as an SeNodeB or SeNB) through a second primary cell of the second network entity (e.g., a secondary cell group primary cell or PCellSCG). The second network entity may be non-collocated with the first network entity. For example, the second network entity may be disparate from the first network entity and first network entity and the second network entity may be connected via a communication link (e.g., backhaul X2 communication link). An information convergence entity in the wireless device may aggregate configuration information received from the first network entity and the second network entity when the wireless device is in communication (e.g., concurrent communication) with the first network entity and the second network entity.

In some aspects of multiple connectivity, a wireless device may be communicatively coupled to a plurality of network entities. For example, a first network entity (e.g., MeNodeB or MeNB) may be configured to operate a master cell group (MCG) including one or more cells (e.g., each cell in the MCG may operate in different frequency bands and may include one or more component carriers (CCs)). A cell in the MCG may be designated or configured as a first primary cell of the MCG (e.g., PCell). A second network entity (e.g., SeNodeB or SeNB) may be configured to operate a secondary cell group (SCG) including one or more cells (e.g., each cell in the SCG may operate in different frequency bands and may include one or more component carriers (CCs)). A cell in the SCG may be designated or configured as a first primary cell of the SCG (e.g., PCellSCG). For example, the wireless device may receive configuration information from the first network entity via the first primary cell (e.g., PCell) and configuration information from the second network entity via the second primary cell (e.g., PCellSCG). The first network entity may be non-collocated with the second network entity. Aspects of the connectivity of the wireless device to an MeNB and a SeNB may include modifications and/or enhancements to various procedures (e.g., physical layer (PHY) procedures and/or media access control (MAC) layer procedures).

In some aspects, when a wireless device (e.g., UE) is connected to one MeNB and one SeNB (e.g., dual connectivity), a timing advanced group (TAG) may include cells of one just one eNB. There may be instances in dual connectivity in which there is one PCell in the MeNB and another in the SeNB, or there is just one PCell per wireless device. With respect to carrier aggregation (CA) in dual connectivity, it may be desirable to enable packet and/or bearer aggregation by radio resource control (RRC) configuration to limit the number of changes in the protocol stack for different configurations. For example, it may be desirable to include contention-based and contention free random access (RA) procedures allowed towards the SeNB (e.g., message <NUM> sent by SeNB), separate discontinuous reception (DRX) procedures at MeNB and SeNB (with possible coordination), and having the wireless device send a buffer status report (BSR) for bearer aggregation to the eNB where the bearer is served. Other aspects that may be desirable include sending BSR for packet aggregation, power headroom reporting (PHR), power control, sounding reference signal (SRS), and logical channel (LC) prioritization.

In other aspects, carrier aggregation procedures associated with dual or multiple connectivity may include some PCell-specific functionalities. For example, the PCell may handle certain functionalities such as physical uplink control channel (PUCCH), contention-based random access control channel (RACH), and semi-persistent scheduling to name a few. In dual connectivity, carrier aggregation may involve certain enhancements or modifications. Some of these enhancements or modification may include having, for example, five (<NUM>) total component carriers per wireless device (e.g., UE) for carrier aggregation. Another enhancement or modification may include having, for example, four (<NUM>) TAGs per UE for carrier aggregation. Moreover, carrier aggregation may be supported in an MeNB and in an SeNB, that is, the MeNB and the SeNB may have multiple service cells for the wireless device. In addition, and as described herein, a master cell group or MCG may be a group of the serving cells associated with the MeNB, while a secondary cell group or SCG may be a group of the serving cells associated with the SeNB.

The techniques described herein may be used for various wireless communication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other networks. An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>, Flash-OFDMA, etc. UTRA and E-UTRA are part of UMTS. 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are new releases of UMTS that use E-UTRA. For clarity, certain aspects of the techniques are described below for LTE, and LTE terminology is used in much of the description below.

<FIG> is a block diagram conceptually illustrating an example of a wireless communications system <NUM>, in accordance with an aspect of the present disclosure. For example, at least portions of the communications system <NUM> may be configured for implementing carrier aggregation in dual connectivity. In some aspects, carrier aggregation may involve bearer aggregation and/or packet aggregation. The wireless communications system <NUM> includes base stations (or cells) <NUM>, user equipment (UEs) <NUM>, and a core network <NUM>. The base stations <NUM> may communicate with the UEs <NUM> under the control of a base station controller (not shown), which may be part of the core network <NUM> or the base stations <NUM> in various embodiments. The base stations <NUM> may communicate control information and/or user data with the core network <NUM> through first backhaul links <NUM>. In embodiments, the base stations <NUM> may communicate, either directly or indirectly, with each other over second backhaul links <NUM>, which may be wired or wireless communication links. The wireless communications system <NUM> may support operation on multiple carriers (waveform signals of different frequencies). Multi-carrier transmitters can transmit modulated signals simultaneously on the multiple carriers. For example, each communication link <NUM> may be a multi-carrier signal modulated according to the various radio technologies described above. Each modulated signal may be sent on a different carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, data, etc. The wireless communications system <NUM> may also support operation on multiple flows at the same time. In some aspects, the multiple flows may correspond to multiple wireless wide area networks (WWANs) or cellular flows. In other aspects, the multiple flows may correspond to a combination of WWANs or cellular flows and wireless local area networks (WLANs) or Wi-Fi flows.

The base stations <NUM> may wirelessly communicate with the UEs <NUM> via one or more base station antennas. Each of the base stations <NUM> sites may provide communication coverage for a respective geographic coverage area <NUM>. In some embodiments, base stations <NUM> may be referred to as a base transceiver station, a radio base station, an access point, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a NodeB, eNodeB, Home NodeB, a Home eNodeB, or some other suitable terminology. As described above, a master eNodeB may also referred to as an MeNodeB or MeNB, while a secondary eNodeB may also referred to as an SeNodeB or SeNB. The geographic coverage area <NUM> for a base station <NUM> may be divided into sectors making up only a portion of the coverage area (not shown). The wireless communications system <NUM> may include base stations <NUM> of different types (e.g., macro, micro, and/or pico base stations). There may be overlapping coverage areas for different technologies.

In implementations, the wireless communications system <NUM> is an LTE/LTE-A network communication system. In LTE/LTE-A network communication systems, the terms evolved Node B (eNodeB) may be generally used to describe the base stations <NUM>. The wireless communications system <NUM> may be a Heterogeneous LTE/LTE-A network in which different types of eNodeBs provide coverage for various geographical regions. For example, each eNodeB <NUM> may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell. A pico cell would generally cover a relatively smaller geographic area (e.g., buildings) and may allow unrestricted access by UEs <NUM> with service subscriptions with the network provider. A femto cell would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs <NUM> having an association with the femto cell (e.g., UEs <NUM> in a closed subscriber group (CSG), UEs <NUM> for users in the home, and the like). An eNodeB <NUM> for a macro cell may be referred to as a macro eNodeB. An eNodeB <NUM> for a pico cell may be referred to as a pico eNodeB. And, an eNodeB <NUM> for a femto cell may be referred to as a femto eNodeB or a home eNodeB. An eNodeB <NUM> may support one or multiple (e.g., two, three, four, and the like) cells. The wireless communications system <NUM> may support use of LTE and WLAN or Wi-Fi by one or more of the UEs <NUM>.

The term "small cell" may refer to an access point or base station, or to a corresponding coverage area of the access point or the base station, where the access point or base station in this case has a relatively low transmit power or relatively small coverage as compared to, for example, the transmit power or coverage area of a macro network access point or macro cell. For instance, and as noted above, a macro cell may cover a relatively large geographic area, such as, but not limited to, several kilometers in radius. In contrast, a small cell may cover a relatively small geographic area, such as, but not limited to, a home, a building, or a floor of a building. As such, a small cell may include, but is not limited to, an apparatus such as a base station (BS), an access point, a femto node, a femtocell, a pico node, a micro node, a NodeB, evolved NodeB (eNB), home NodeB (HNB) or home evolved NodeB (HeNB). Therefore, the term "small cell" can be used to refer to a relatively low transmit power and/or a relatively small coverage area cell as compared to a macro cell. In some implementations, one or more cells associated with an MeNB and/or one or more cells associated with an SeNB may be small cells.

The core network <NUM> may communicate with the eNodeBs <NUM> or other base stations <NUM> via first backhaul links <NUM> (e.g., S1 interface, etc.). The eNodeBs <NUM> may also communicate with one another, e.g., directly or indirectly via second backhaul links <NUM> (e.g., X2 interface, etc.) and/or via the first backhaul links <NUM> (e.g., through core network <NUM>). The wireless communications system <NUM> may support synchronous or asynchronous operation. For synchronous operation, the eNodeBs <NUM> may have similar frame timing, and transmissions from different eNodeBs <NUM> may be approximately aligned in time. For asynchronous operation, the eNodeBs <NUM> may have different frame timing, and transmissions from different eNodeBs <NUM> may not be aligned in time.

The UEs <NUM> may be dispersed throughout the wireless communications system <NUM>, and each UE <NUM> may be stationary or mobile. A UE <NUM> may also be referred to by those skilled in the art as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE <NUM> may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a device for the Internet of Things (IoT), or the like. A UE <NUM> may be able to communicate with macro eNodeBs, pico eNodeBs, femto eNodeBs, relays, and the like.

The communication links <NUM> shown in the wireless communications system <NUM> may include uplink (UL) transmissions from a UE <NUM> to an eNodeB <NUM>, and/or downlink (DL) transmissions, from an eNodeB <NUM> to a UE <NUM>. The downlink transmissions may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions.

In certain aspects of the wireless communications system <NUM>, a UE <NUM> may be configured to support carrier aggregation (CA) with two or more eNodeBs <NUM>. Carrier aggregation may include, in some aspects, one or both of bearer aggregation and packet aggregation. Each aggregated carrier may be referred to as a component carrier (CC), and the individual component carriers may have the same or different bandwidths. The number of component carriers used for uplink (UL) may be the same or lower than the number of component carriers used for downlink (DL). The eNodeBs <NUM> that are used for carrier aggregation may be collocated or may be connected through fast connections. In either case, coordinating the aggregation of component carriers for wireless communications between the UE <NUM> and the eNodeBs <NUM> may be carried out more easily because information can be readily shared between the various cells being used to perform the carrier aggregation. When the eNodeBs <NUM> that are used for carrier aggregation are non-collocated (e.g., far apart or do not have a high-speed connection between them), then coordinating the aggregation of component carriers may involve additional aspects, which are described herein. For example, in carrier aggregation for dual connectivity (e.g., UE <NUM> connected to two non-collocated eNodeBs <NUM>), the UE <NUM> may receive configuration information to communicate with a first eNodeB <NUM> (e.g., SeNodeB or SeNB) through a primary cell of the first eNodeB <NUM> (see e.g., <FIG>). The first eNodeB <NUM> may include a group of cells referred to as a secondary cell group, or SCG, which includes one or more secondary cells and the primary cell, or PCellSCG, of the first eNodeB <NUM>. The UE <NUM> may also receive configuration information to communicate with a second eNodeB <NUM> (e.g., MeNodeB or MeNB) through a second primary cell of the second eNodeB <NUM>. The second eNodeB <NUM> may include a group of cells referred to as a master cell group, or MCG, which includes one or more secondary cells and the primary cell, or PCell, of the second eNodeB <NUM>. As indicated above, the first and second eNodeBs <NUM> may not be collocated or may not have a fast connection between them, in which case carrier aggregation may involve different aspects from when such entities are collocated or have a fast connection between them. The UE <NUM> may include an information convergence entity (see, e.g., information convergence entity component <NUM> in <FIG> and described below) that may aggregate information (e.g., data packets) received from the first eNodeB <NUM> and the second eNodeB <NUM> when the UE <NUM> is in concurrent communication with both eNodeBs. The information convergence entity may allow the data communicated over different component carriers to be aggregated or combined at the UE <NUM>.

In certain aspects of the wireless communications system <NUM>, carrier aggregation for dual connectivity may involve having a secondary eNodeB <NUM> (e.g., SeNodeB or SeNB) be configured to operate one of its cells as a PCellSCG. The secondary eNodeB <NUM> may transmit, to a UE <NUM>, configuration information through the PCellSCG for the UE <NUM> to communicate with the secondary eNodeB <NUM> while the UE <NUM> is in communication with a master eNodeB <NUM> (e.g., MeNodeB or MeNB). The master eNodeB <NUM> may transmit, to the same UE <NUM>, configuration information via its PCell for that UE <NUM> to communication with the other eNodeB <NUM>. The two eNodeBs <NUM> may be non-collocated. In some implementations, the features, aspects, and/or techniques described herein may be applied to scenarios in which there are multiple connections between a UE (e.g., UE <NUM>) and eNodeBs. In such scenarios, one of the several eNodeBs may operate as the MeNodeB or MeNB.

In some aspects of the communications system <NUM>, for a UE <NUM> in dual connectivity, a PCell may be implemented in an eNodeB <NUM> operating as the MeNB and a PCellSCG may be implemented in another eNodeB <NUM> operating as the SeNB. In a different implementation, there may be one PCell per UE <NUM> in dual connectivity. In this latter case, upper layer functionality related to the PCell need not be changed and other functionality may be implemented in such a way as to minimize or reduce any impact on protocol specification. One approach may include having the PCell retain its per UE functionality with respect to initial configuration, security, system information, and/or radio link failure (RLF). The PCell may be configured as one of the cells of the MeNB, belonging to the MCG associated with the MeNB (see e.g., <FIG>). PUCCH may be used in the configuration of the PCell. Moreover, the PCell may provide the lower layer functionality within the MCG.

<FIG> is a block diagram conceptually illustrating examples of an eNodeB <NUM> and a UE <NUM> configured in accordance with an aspect of the present disclosure. For example, the base station/eNodeB <NUM> and the UE <NUM> of a system <NUM>, as shown in <FIG>, may be one of the base stations/eNodeBs and one of the UEs in <FIG>, respectively. In some aspects, the eNodeB <NUM> may support or may be used in association with multiple connectivity (e.g., dual connectivity) carrier aggregation. In one aspect, the eNodeB <NUM> may be an MeNodeB or MeNB having one of the cells in its MCG configured as a PCell. In another aspect, the eNodeB <NUM> may be an SeNodeB or SeNB having one of its cells in its SCG configured as a PCellSCG. In some aspects, the UE <NUM> may also support multiple connectivity carrier aggregation. For example, the UE <NUM> may be configured to aggregate information, such as configuration information, from different eNodeBs. The UE <NUM> may receive configuration information from the eNodeB <NUM> via the PCell and/or the PCellSCG. The eNodeB <NUM> may be equipped with antennas <NUM><NUM>-t, and the UE <NUM> may be equipped with antennas <NUM><NUM>-r, wherein t and r are integers greater than or equal to one.

At the eNodeB <NUM>, a base station transmit processor <NUM> may receive data from a base station data source <NUM> and control information from a base station controller/processor <NUM>. The control information may be carried on the PBCH, PCFICH, PHICH, PDCCH, etc. The data may be carried on the PDSCH, etc. The base station transmit processor <NUM> may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The base station transmit processor <NUM> may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signal (RS). A base station transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the base station modulators/demodulators (MODs/DEMODs) <NUM><NUM>-t. Each base station modulator/demodulator <NUM> may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each base station modulator/demodulator <NUM> may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators/demodulators <NUM><NUM>-t may be transmitted via the antennas <NUM><NUM>-t, respectively.

At the UE <NUM>, the UE antennas <NUM><NUM>-r may receive the downlink signals from the base station <NUM> and may provide received signals to the UE modulators/demodulators (MODs/DEMODs) <NUM><NUM>-r, respectively. Each UE modulator/demodulator <NUM> may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each UE modulator/demodulator <NUM> may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A UE MIMO detector <NUM> may obtain received symbols from all the UE modulators/demodulators <NUM><NUM>-r, and perform MIMO detection on the received symbols if applicable, and provide detected symbols. A UE reception processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE <NUM> to a UE data sink <NUM>, and provide decoded control information to a UE controller/processor <NUM>.

On the uplink, at the UE <NUM>, a UE transmit processor <NUM> may receive and process data (e.g., for the PUSCH) from a UE data source <NUM> and control information (e.g., for the PUCCH) from the UE controller/processor <NUM>. The UE transmit processor <NUM> may also generate reference symbols for a reference signal. The symbols from the UE transmit processor <NUM> may be precoded by a UE TX MIMO processor <NUM> if applicable, further processed by the UE modulator/demodulators <NUM><NUM>-r (e.g., for SC-FDM, etc.), and transmitted to the eNodeB210. At the eNodeB210, the uplink signals from the UE <NUM> may be received by the base station antennas <NUM>, processed by the base station modulators/demodulators <NUM>, detected by a base station MIMO detector <NUM> if applicable, and further processed by a base station reception processor <NUM> to obtain decoded data and control information sent by the UE <NUM>. The base station reception processor <NUM> may provide the decoded data to a base station data sink <NUM> and the decoded control information to the base station controller/processor <NUM>.

The base station controller/processor <NUM> and the UE controller/processor <NUM> may direct the operation at the eNodeB210 and the UE <NUM>, respectively. The base station controller/processor <NUM> and/or other processors and modules at the eNodeB210 may perform or direct, e.g., the execution of functional blocks illustrated in <FIG> and <FIG>, and/or other processes for the techniques or procedures described herein (e.g., flowchart illustrated in <FIG>). In some aspects, at least a portion of the execution of these functional blocks and/or processes may be performed by block <NUM> in the base station controller/processor <NUM>. It is to be understood that block <NUM>, or at least portions of the operations of block <NUM>, may be performed in other processors and modules of the eNodeB <NUM>. The UE controller/processor <NUM> and/or other processors and modules at the UE <NUM> may also perform or direct, e.g., the execution of the functional blocks illustrated in <FIG> and/or <FIG>, and/or other processes for the techniques described herein (e.g., flowchart illustrated in <FIG>). In some aspects, at least a portion of the execution of these functional blocks and/or processes may be performed by block <NUM> in the UE controller/processor <NUM>. It is to be understood that block <NUM>, or at least portions of the operations of block <NUM>, may be performed in other processors and modules of the UE <NUM>. The base station memory <NUM> and the UE memory <NUM> may store data and program codes for the eNodeB210 and the UE <NUM>, respectively. For example, the UE memory <NUM> may store configuration information for multiple connectivity carrier aggregation provided by the eNodeB210. A scheduler <NUM> may be used to schedule UE <NUM> for data transmission on the downlink and/or uplink.

In one configuration, the eNodeB210 may include means for configuring a first network entity to operate a cell in a group of cells as a first primary cell. The base station <NUM> may include means for transmitting, to a wireless device (e.g., UE <NUM>), configuration information through the first primary cell for the wireless device to communicate with the first network entity while in concurrent communication with a second network entity having a second primary cell, where the first network entity is non-collocated with the second network entity. In one aspect, the aforementioned means may be the base station controller/processor <NUM>, the block <NUM>, the base station memory <NUM>, the base station transmit processor <NUM>, the base station modulators/demodulators <NUM>, and the base station antennas <NUM> configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a module, component, or any apparatus configured to perform the functions recited by the aforementioned means. Examples of such modules, components, or apparatus may be described with respect to <FIG> and/or <FIG>.

In one configuration, the UE <NUM> may include means for receiving, at a wireless device, configuration information to communicate with a first network entity through a first primary cell of the first network entity. The UE <NUM> may include means for receiving, at the wireless device, configuration information to communicate with a second network entity through a second primary cell of the second network entity, the second network entity being non-collocated with the first network entity. The UE <NUM> may include means for aggregating, at an information convergence entity (see e.g., information convergence entity component <NUM> in <FIG>) in the wireless device, information received from the first network entity and the second network entity when the wireless device is in communication with the first network entity and the second network entity. In one aspect, the aforementioned means may be the UE controller/processor <NUM>, the block <NUM>, the UE memory <NUM>, the UE reception processor <NUM>, the UE MIMO detector <NUM>, the UE modulators/demodulators <NUM>, and the UE antennas <NUM> configured to perform the functions recited by the aforementioned means. In another aspect, the aforementioned means may be a module, component, or any apparatus configured to perform the functions recited by the aforementioned means. Examples of such modules, components, or apparatus may be described with respect to <FIG> and/or <FIG>.

<FIG> is a block diagram conceptually illustrating an aggregation of radio access technologies at a UE, in accordance with an aspect of the present disclosure. The aggregation may occur in a system <NUM> including a multi-mode UE <NUM>, which can communicate with an eNodeB <NUM>-a using one or more component carriers <NUM> through N (CC<NUM>-CCN), and with a WLAN access point (AP) <NUM>-b using WLAN carrier <NUM>. A multi-mode UE in this example may refer to a UE that supports more than one radio access technology (RAT). For example, the UE <NUM> supports at least a WWAN radio access technology (e.g., LTE) and a WLAN radio access technology (e.g., Wi-Fi). A multi-mode UE may also support multiple connectivity (e.g., dual connectivity) carrier aggregation as described herein. The UE <NUM> may be an example of one of the UEs of <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, and/or <FIG>. The eNodeB <NUM>-a may be an example of one of the eNodeBs or base stations of <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, and/of <FIG>. The AP <NUM>-b may be an example of an AP of <FIG>. While only one UE <NUM>, one eNodeB <NUM>-a, and one AP <NUM>-b are illustrated in <FIG>, it will be appreciated that the system <NUM> can include any number of UEs <NUM>, eNodeBs <NUM>-a, and/or APs <NUM>-b.

The eNodeB <NUM>-a can transmit information to the UE <NUM> over forward (downlink) channels <NUM>-<NUM> through <NUM>-N on LTE component carriers CC<NUM> through CCN <NUM>. In addition, the UE <NUM> can transmit information to the eNodeB <NUM>-a over reverse (uplink) channels <NUM>-<NUM> through <NUM>-N on LTE component carriers CC<NUM> through CCN. Similarly, the AP <NUM>-b may transmit information to the UE <NUM> over forward (downlink) channel <NUM> on WLAN carrier <NUM>. In addition, the UE <NUM> may transmit information to the AP <NUM>-b over reverse (uplink) channel <NUM> of WLAN carrier <NUM>. Although a single eNodeB <NUM>-a is illustrated for carrier aggregation, it is understood that a similar operation may be implemented with multiple eNodeBs <NUM>-a when the UE <NUM> is operating in multiple connectivity. For example, when a first eNodeB <NUM>-a operates as an MeNB and a second eNodeB <NUM>-a operates as an SeNB, dual connectivity carrier aggregation may be performed in connection with the UE <NUM>.

In describing the various entities of <FIG>, as well as other figures associated with some of the disclosed embodiments, for the purposes of explanation, the nomenclature associated with a 3GPP LTE or LTE-A wireless network is used. However, it is to be appreciated that the system <NUM> can operate in other networks such as, but not limited to, an OFDMA wireless network, a CDMA network, a 3GPP2 CDMA2000 network and the like.

In multi-carrier operations, the downlink control information (DCI) messages associated with different UEs <NUM> can be carried on multiple component carriers. For example, the DCI on a PDCCH can be included on the same component carrier that is configured to be used by a UE <NUM> for physical downlink shared channel (PDSCH) transmissions (i.e., samecarrier signaling). Alternatively, or additionally, the DCI may be carried on a component carrier different from the target component carrier used for PDSCH transmissions (i.e., cross-carrier signaling). In some implementations, a carrier indicator field (CIF), which may be semi-statically enabled, may be included in some or all DCI formats to facilitate the transmission of PDCCH control signaling from a carrier other than the target carrier for PDSCH transmissions (cross-carrier signaling).

In the present example, the UE <NUM> may receive data from one eNodeB <NUM>-a. However, users on a cell edge may experience high inter-cell interference which may limit the data rates. Multiflow allows UEs to receive data from two eNodeBs <NUM>-a simultaneously, as described above. In some aspects, the two eNodeBs <NUM>-a may be non-collocated and may be configured to support multiple connectivity carrier aggregation. Multiflow works by sending and receiving data from the two eNodeBs <NUM>-a in two totally separate streams when a UE is in range of two cell towers in two adjacent cells at the same time (see e.g., <FIG>, which is described below). The UE may communicate with two eNodeB <NUM>-a contemporaneously when the device is on the edge of either eNodeBs' reach. By scheduling two independent data streams to the mobile device from two different eNodeBs at the same time, multiflow exploits uneven loading in HSPA networks. This helps improve the cell edge user experience while increasing network capacity. In one example, throughput data speeds for users at a cell edge may double. In some aspects, multiflow may also refer to the ability of a UE to talk to a WWAN tower (e.g., cellular tower) and a WLAN tower (e.g., AP) simultaneously when the UE is within the reach of both towers. In such cases, the towers may be configured to support carrier aggregation through multiple connections when the towers are not collocated. Multiflow is a feature of LTE/LTE-A that is similar to dual-carrier HSPA, however, there are differences. For example, dual-carrier HSPA doesn't allow for connectivity to multiple towers to connect simultaneously to a device.

LTE-A standardization, LTE component carriers <NUM> have been backwardcompatible, which enabled a smooth transition to new releases. However, this feature caused the LTE component carriers <NUM> to continuously transmit common reference signals (CRS, also referred to as cell-specific reference signals) in every subframe across the bandwidth. Most cell site energy consumption is caused by the power amplifier, as the cell remains on even when only limited control signaling is being transmitted, causing the amplifier to continue to consume energy. CRS were introduced in release <NUM> of LTE and are LTE's most basic downlink reference signal. The CRSs are transmitted in every resource block in the frequency domain and in every downlink subframe. CRS in a cell can be for one, two, or four corresponding antenna ports. CRS may be used by remote terminals to estimate channels for coherent demodulation. A New Carrier Type (NCT) allows temporarily switching off of cells by removing transmission of CRS in four out of five sub frames. This feature reduces power consumed by the power amplifier, as well as the overhead and interference from CRS, as the CRS is no longer continuously transmitted in every subframe across the bandwidth. In addition, the New Carrier Type allows the downlink control channels to be operated using UEspecific Demodulation Reference Symbols. The New Carrier Type might be operated as a kind of extension carrier along with another LTE/LTE-A carrier or alternatively as standalone nonbackward compatible carrier.

<FIG> is a block diagram conceptually illustrating an example of data paths <NUM> and <NUM> between a UE <NUM> and a PDN <NUM> (e.g., Internet) in accordance with an aspect of the present disclosure. The data paths <NUM>, <NUM> are shown within the context of a wireless communications system <NUM> for aggregating data from different radio access technologies. The system <NUM> of <FIG> may be an example of portions of the wireless communications system <NUM>. The wireless communications system <NUM> may include a multi-mode UE <NUM>, an eNodeB <NUM>-a, a WLAN AP <NUM>-b, an evolved packet core (EPC) <NUM>, a PDN <NUM>, and a peer entity <NUM>. The multi-mode UE <NUM> may be configured to support multiple connectivity (e.g., dual connectivity) carrier aggregation. The EPC <NUM> may include a mobility management entity (MME) <NUM>, a serving gateway (SGW) <NUM>, and a PDN gateway (PGW) <NUM>. A home subscriber system (HSS) <NUM> may be communicatively coupled with the MME <NUM>. The UE <NUM> may include an LTE radio <NUM> and a WLAN radio <NUM>. In some implementations, the UE <NUM> may include a WWAN radio, of which the LTE radio <NUM> is an example, along with the WLAN radio <NUM>, of which a Wi-Fi radio may be an example. Dual connectivity with carrier aggregation may be implemented in connection with the WWAN radio, the WLAN radio <NUM>, or both. These elements may represent aspects of one or more of their counterparts described above with reference to the previous or subsequent Figures. For example, the UE <NUM> may be an example of UEs in <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, and/or <FIG>, the eNodeB <NUM>-a may be an example of the eNodeBs/base stations of <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, and/or <FIG>, the AP <NUM>-b may be an example of the AP <NUM>-b of <FIG>, and/or the EPC <NUM> may be an example of at least portions of the core network of <FIG> and/or <FIG>. The eNodeB <NUM>-a and AP <NUM>-b in <FIG> may be not be collocated or otherwise may not be in high-speed communication with each other. On the other hand, although a single eNodeB <NUM>-a is illustrated for carrier aggregation, it is understood that multiple connectivity with carrier aggregation may be implemented with multiple eNodeBs <NUM>-a when the UE <NUM> is operating in multiple connectivity. For example, when a first eNodeB <NUM>-a operates as an MeNB and a second eNodeB <NUM>-a operates as an SeNB, dual connectivity carrier aggregation may be performed in connection with the UE <NUM>. Aggregation may take place from cells of the same eNodeB or from cells of eNodeBs that are collocated or in high-speed communication with each other.

Referring back to <FIG>, the eNodeB <NUM>-a and the AP <NUM>-b may be capable of providing the UE <NUM> with access to the PDN <NUM> using the aggregation of one or more LTE component carriers and/or one or more WLAN component carriers. Accordingly, the UE <NUM> may involve carrier aggregation in dual connectivity, where one connection is to one network entity (eNodeB <NUM>-a) and the other connection is to a different network entity (AP <NUM>-b). Using this access to the PDN <NUM>, the UE <NUM> may communicate with the peer entity <NUM>. The eNodeB <NUM>-a may provide access to the PDN <NUM> through the evolved packet core <NUM> (e.g., through data path <NUM>), and the WLAN AP <NUM>-b may provide direct access to the PDN <NUM> (e.g., through data path <NUM>).

The MME <NUM> may be the control node that processes the signaling between the UE <NUM> and the EPC <NUM>. Generally, the MME <NUM> may provide bearer and connection management. The MME <NUM> may, therefore, be responsible for idle mode UE tracking and paging, bearer activation and deactivation, and SGW selection for the UE <NUM>. The MME <NUM> may communicate with the eNodeB <NUM>-a over an S1-MME interface. The MME <NUM> may additionally authenticate the UE <NUM> and implement Non-Access Stratum (NAS) signaling with the UE <NUM>.

The HSS <NUM> may, among other functions, store subscriber data, manage roaming restrictions, manage accessible access point names (APNs) for a subscriber, and associate subscribers with MMEs <NUM>. The HSS <NUM> may communicate with the MME <NUM> over an S6a interface defined by the Evolved Packet System (EPS) architecture standardized by the 3GPP organization.

All user IP packets transmitted over LTE may be transferred through eNodeB <NUM>-a to the SGW <NUM>, which may be connected to the PDN gateway <NUM> over an S5 signaling interface and the MME <NUM> over an S11 signaling interface. The SGW <NUM> may reside in the user plane and act as a mobility anchor for inter-eNodeB handovers and handovers between different access technologies. The PDN gateway <NUM> may provide UE IP address allocation as well as other functions.

The PDN gateway (PGW) <NUM> may provide connectivity to one or more external packet data networks, such as PDN <NUM>, over an SGi signaling interface. The PDN <NUM> may include the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet-Switched (PS) Streaming Service (PSS), and/or other types of PDNs.

In the present example, user plane data between the UE <NUM> and the EPC <NUM> may traverse the same set of one or more EPS bearers, irrespective of whether the traffic flows over path <NUM> of the LTE link or path <NUM> of the WLAN link. Signaling or control plane data related to the set of one or more EPS bearers may be transmitted between the LTE radio <NUM> of the UE <NUM> and the MME <NUM> of the EPC <NUM>, by way of the eNodeB <NUM>-a.

While aspects of <FIG> have been described with respect to LTE, similar aspects regarding aggregation and/or multiple connections may also be implemented with respect to UMTS or other similar system or network wireless communications radio technologies. Moreover, while aspects of carrier aggregation have been described in <FIG> and <FIG> with respect to an eNodeB and a WLAN AP, a similar approach may be used when two or more eNodeBs are used in a multiple connectivity carrier aggregation scenario, or when two or more cells from a same eNodeB are used in a multiple connectivity carrier aggregation scenario, as described above. Aggregation may take place from cells of the same eNodeB or from cells of eNodeBs that are collocated or in high-speed communication with each other.

<FIG> is a diagram conceptually illustrating multiple connectivity carrier aggregation in accordance with an aspect of the present disclosure. A wireless communications system <NUM> may include a master eNodeB <NUM>-a (MeNodeB or MeNB) having a set or group of cells referred to as a master cell group or MCG that may be configured to serve the UE <NUM>. The MCG may include one primary cell (PCell) <NUM>-a and one or more secondary cells <NUM>-b (only one is shown in <FIG> for illustration). The wireless communications system <NUM> may also include a secondary eNodeB <NUM>-b (SeNodeB or SeNB) having a set or group of cells referred to as a secondary cell group or SCG that may be configured to serve the UE <NUM>. The SCG may include one primary cell (PCellSCG) <NUM>-a and one or more secondary cells <NUM>-b (only one is shown in <FIG> for illustration). Also shown is a UE <NUM> that supports carrier aggregation for multiple connectivity (e.g., dual connectivity) scenarios. The UE <NUM> may communicate with the MeNodeB <NUM>-a via communication link <NUM>-a and with the SeNodeB <NUM>-b via communication link <NUM>-b.

In one implementation, the UE <NUM> may aggregate component carriers from the same eNodeB or may aggregate component carriers from collocated eNodeBs. In such an example, the various cells (e.g., different component carriers (CCs)) being used can be easily coordinated because they are either handled by the same eNodeB or by eNodeBs that can quickly communicate control information. When the UE <NUM>, as in the example of <FIG>, performs carrier aggregation when in communication with two eNodeBs that are non-collocated, then the carrier aggregation operation may be different due to various network conditions. In this case, establishing a primary cell (PCellSCG) in the secondary eNodeB <NUM>-b may allow for appropriate configurations and controls to take place at the UE <NUM> even though the secondary eNodeB <NUM>-b is non-collocated with the primary eNodeB <NUM>-a.

In the example of <FIG>, the carrier aggregation may involve certain functionalities by the PCell of the MeNodeB <NUM>-a. For example, the PCell may handle certain functionalities such as physical uplink control channel (PUCCH), contention-based random access control channel (RACH), and semi-persistent scheduling to name a few. Carrier aggregation with dual or multiple connectivity to non-collocated eNodeBs may involve having to make some enhancements and/or modifications to the manner in which carrier aggregation is otherwise performed. Some of the enhancements and/or modifications may involve having the UE <NUM> connected to the MeNodeB <NUM>-a and to the SeNodeB <NUM>-b as described above. Other features may include, for example, having a timing advance group (TAG) comprise cells of one of the eNodeBs, having contention-based and contention-free random access (RA) allowed on the SeNodeB <NUM>-b, separate discontinuous reception (DRX) procedures for the MeNodeB <NUM>-a and to the SeNodeB <NUM>-b, having the UE <NUM> send a buffer status report (BSR) to the eNodeB where the bearer is served, as well as enabling one or more of power headroom report (PHR), power control, semi-persistent scheduling (SPS), and logical channel prioritization in connection with the PCellSCG in the secondary eNodeB <NUM>-b. The enhancements and/or modifications described above, as well as others provided in the disclosure, are intended for purposes of illustration and not of limitation.

For carrier aggregation in dual connectivity as in the example of <FIG>, different functionalities may be divided between the MeNodeB <NUM>-a and the SeNodeB <NUM>-b. For example, different functionalities may be statically divided between the MeNodeB <NUM>-a and the SeNodeB <NUM>-b, or dynamically divided between the MeNodeB <NUM>-a and the SeNodeB <NUM>-b based on one or more network parameters. In an example, the MeNodeB <NUM>-a may perform upper layer (e.g., layers above the media access control (MAC) layer) functionalities via a PCell, such as but not limited to functionalities related to initial configuration, security, system information, and/or radio link failure (RLF). As described in the example of <FIG>, the PCell may be configured as one of the cells of the MeNodeB <NUM>-a that belongs to the MCG. The PCell may be configured to provide lower layer functionalities (e.g., MAC/PHY layer) within the MCG.

In an example, the SeNodeB <NUM>-b may provide configuration information of lower layer (e.g., PHY/MAC layers) functionalities for the SCG. The configuration information may be provided by the PCellSCG as one or more radio resource control (RRC) messages, for example. The PCellSCG may include both uplink and downlink carriers, and may provide PCell-like lower layer functionality for the SCG. The PCellSCG may be configured to have the lowest cell index (e.g., identifier or ID) among the cells in the SCG. According to the claimed scope of the present invention, some of the functionalities performed by the SeNodeB <NUM>-b via the PCellSCG include carrying the PUCCH, configuring the cells in the SCG to follow the DRX configuration of the PCellSCG, may include configuring resources for contention-based and contention-free random access on the SeNodeB <NUM>-b, carrying downlink (DL) grants having transmit power control (TPC) commands for PUCCH, include estimating pathloss based on PCellSCG for other cells in the SCG, providing common search space for the SCG, and may include providing SPS configuration information for the UE <NUM>.

In some aspects, the PCell may be configured to provide upper level functionalities to the UE <NUM> such as security, connection to a network, initial connection, and/or radio link failure, for example. The PCell may be configured to carry physical uplink control channel (PUCCH) for cells in the MCG, to include the lowest cell index among the MCG, to enable the MCG cells to have the same discontinuous reception (DRX) configuration, to configure random access resources for one or both of contention-based and contention-free random access on the MeNodeB <NUM>-a, to enable downlink grants to convey transmit power control (TPC) commands for PUCCH, to enable pathloss estimation for cells in the MCG, to configure common search space for the MeNodeB <NUM>-a, and/or to configure semi-persistent scheduling.

In some aspects, the PCellSCG may be configured to carry PUCCH for cells in the SCG, to include the lowest cell index among the SCG, to enable the SCG cells to have the same DRX configuration, to configure random access resources for one or both of contention-based and contention-free random access on the SeNodeB <NUM>-b, to enable downlink grants to convey TPC commands for PUCCH, to enable pathloss estimation for cells in the SCG, to configure common search space for the SeNodeB <NUM>-b, and/or to configure semi-persistent scheduling.

Returning to the example of <FIG>, the UE <NUM> may support parallel PUCCH and physical uplink shared channel (PUSCH) configurations for the MeNodeB <NUM>-a and the SeNodeB <NUM>-b. In some cases, the UE <NUM> may use a configuration (e.g., UE-based) that may be applicable to carrier groups from both eNodeBs. These PUCCH/PUSCH configurations may be provided through RRC messages, for example.

The UE <NUM> may also support parallel configuration for simultaneous transmission of acknowledgement (ACK)/negative acknowledgement (NACK) and channel quality indicator (CQI) and for ACK/NACK/SRS for the MeNodeB <NUM>-a and the SeNodeB <NUM>-b. In some cases, the UE <NUM> may use a configuration (e.g., UE-based and/or MCG- or SCG-based) that may be applicable to carrier groups from both eNodeBs. These configurations may be provided through RRC messages, for example.

In another aspect of communications system <NUM>, cross-carrier control can be configured such that one cell may convey control for another cell. One possible exception may be that an SCell may not cross-carrier control a PCell. For dual connectivity, for example, cross-carrier control may be configured within the cell belonging to the same carrier group. In such a scenario, the exception that SCells may not be able to cross-carrier control PCell and PCellSCG may be preserved.

<FIG> is a block diagram <NUM> conceptually illustrating an example of a UE <NUM> having configured components in accordance with an aspect of the present disclosure. In an aspect, the term "component" as used herein may be one of the parts that make up a system, may be hardware or software, and may be divided into other components. A base station/eNodeB <NUM>-a (MeNodeB with a PCell), a station/eNodeB <NUM>-b (SeNodeB with a PCellSCG), and the UE <NUM> of diagram <NUM> may be one of the base stations/eNodeBs (or APs) and UEs as described in various Figures. The MeNodeB <NUM>-a and the UE <NUM> may communicate over communications link <NUM>-a. The SeNodeB <NUM>-b and the UE <NUM> may communicate over communications link <NUM>-b. Each of the communications links <NUM>-a, <NUM>-b may be an example of the communications links <NUM> of <FIG>.

The UE <NUM> may include a multiple connectivity carrier aggregation (CA) manager component <NUM>, an information convergence entity component <NUM>, and a transmitter/receiver component <NUM>. The multiple connectivity CA manager component <NUM> may be configured to receive configuration information to communicate with the SeNodeB <NUM>-b through the PCellSCG, and to receive configuration information to communicate with the MeNodeB <NUM>-a through the PCell, where the SeNodeB <NUM>-b is non-collocated with the MeNodeB <NUM>-a. In some aspect, the configuration information may be received via the transmitter/receiver component <NUM>.

The information convergence entity component <NUM> may be configured to aggregate information (e.g., configuration information, control information, and/or load data) received from the SeNodeB <NUM>-b and the MeNodeB <NUM>-a when the UE <NUM> is in concurrent communication with the SeNodeB <NUM>-b and the MeNodeB <NUM>-a. The information convergence entity component <NUM> may be one of a packet data convergence protocol (PDCP) entity, an internet protocol (IP) entity, and an RRC entity.

The multiple connectivity CA manager component <NUM> may include a PCell configuration component <NUM>, a PCellSCG configuration component <NUM>, a CA control component <NUM>, a DRX coordination component <NUM>, a power control component <NUM>, a pathloss estimation component <NUM>, an SRS component <NUM>, a power headroom reporting component <NUM>, and a logical channel prioritization component <NUM>.

The PCell configuration component <NUM> may be configured to handle various aspects described herein for receiving and/or processing configuration information provided by the PCell of the MeNodeB <NUM>-a.

The PCellSCG configuration component <NUM> may be configured to handle various aspects described herein for receiving and/or processing configuration information provided by the PCellSCG of the SeNodeB <NUM>-b.

The CA control component <NUM> may be configured to handle various aspects described herein for cross-carrier controls and controlling transmission of uplink control information (UCI) over PUCCH or PUSCH in multiple connectivity carrier aggregation.

The DRX coordination component <NUM> may be configured to handle various aspects described herein for coordinating DRX procedures with the MeNodeB <NUM>-a and the SeNodeB <NUM>-b in multiple connectivity carrier aggregation.

The power control component <NUM> may be configured to handle various aspects described herein for processing and/or using transmit power control (TCP) commands in multiple connectivity carrier aggregation.

The pathloss estimation component <NUM> may be configured to handle various aspects described herein for estimating or determining the pathloss of a cell in either the MeNodeB <NUM>-a and the SeNodeB <NUM>-b based at least in part on the downlink component carrier of the particular cell or the primary component carrier.

The SRS component <NUM> may be configured to handle various aspects described herein for processing and/or configuring the sounding reference signal of each serving cell in multiple connectivity carrier aggregation.

The power headroom reporting component <NUM> may be configured to handle various aspects described herein for implementing power headroom reporting in multiple connectivity carrier aggregation.

The logical channel prioritization component <NUM> may be configured to handle various aspects described herein for processing and/or configuring logical channel (LC) prioritization in multiple connectivity carrier aggregation.

With respect to the CA control component <NUM>, the UE <NUM> can be connected to different nodes (e.g., the MeNodeB <NUM>-a and the SeNodeB <NUM>-b) using different carrier frequencies. Each node (e.g., the MeNodeB <NUM>-a or the SeNodeB <NUM>-b) may configure a group of cells (e.g., the MCG and the SCG) for serving the UE <NUM>. The cells (e.g., component carriers) within each group may be configured to cross control other cells within the group. In an example, a secondary cell of a group may not cross control the primary cell of the group. The CA control component <NUM> may receive cross-carrier control information for the MCG and the SCG from the MeNodeB <NUM>-a and the SeNodeB <NUM>-b, respectively. The PUCCH for the UE <NUM> may be configured on an uplink component carrier for each of the MeNodeB <NUM>-a and the SeNodeB <NUM>-b. PUCCH on one of the component carriers for both the MCG associated with MeNodeB <NUM>-a and the SCG associated with SeNodeB <NUM>-b may carry UCI for all the component carriers associated with the respective group of cells. In this case, RRC configuration messages may be used to indicate or specify which component carrier from the MCG and which component carrier from the SCG carries PUCCH. For example, the PUCCH for the MeNodeB <NUM>-a may be carried on the PCell (e.g., PCell component carrier) of the MCG and PUCCH for the SeNodeB <NUM>-b may be carried on the PCellSCG (e.g., PCellSCG component carrier) of the SCG.

With respect to the CA control component <NUM>, when UCI is transmitted on PUSCH, the component carrier of MCG and SCG with the smallest cell index (within its corresponding group of cells) may be used to transmit PUSCH carrying the UCI for the corresponding group of cells.

With respect to the CA control component <NUM>, the PUCCH format for ACK/NACK feedback for each of MCG and SCG may be determined based at least in part on the number of component carriers in each group of cells. For example, PUCCH format 1b with channel selection may be used when a group of cells has two (<NUM>) component carriers. In another example, PUCCH format <NUM> may be used when a group of cells has two (<NUM>) or more component carriers (or non-CA time division duplexing (TDD)).

With respect to the DRX coordination component <NUM>, separate DRX configurations and/or procedures may be used for the MeNodeB <NUM>-a and the SeNodeB <NUM>-b. For example, cells (or component carriers) aggregated within each group (MCG and SCG) may follow the same DRX configuration, as in carrier aggregation. In some cases, the same DRX operation may be applied to all serving cells. The DRX coordination component <NUM> may also coordinate DRX for dual (or multiple) connectivity. For example, in some aggregation (e.g., packet aggregation) schemes, the DRX coordination component <NUM> may be used when the DRX among the MeNodeB <NUM>-a and the SeNodeB <NUM>-b is to be coordinated. In some cases, the same DRX configuration (as configured for PCell of the MeNodeB <NUM>-a) may be applied on all cells when aggregation is configured. In some cases, the SeNodeB DRX configuration (e.g., DRX configuration for the SeNodeB) may be a superset of the MeNodeB DRX configuration (e.g., DRX configuration for the MeNodeB). For example, the SeNodeB DRX configuration may be a superset with respect to the subframes used for DRX. In another example, the SeNodeB DRX configuration may be a superset as configured for PCellSCG, when the concept of a PCellSCG is used with the SeNodeB <NUM>-b.

With respect to the power control component <NUM>, in carrier aggregation, power control may be implemented separately for PUCCH and PUSCH for each carrier component. For example, TPC commands in carrier aggregation may be provided on a downlink grant downlink control information (DCI) of the PCell for PUCCH power control, and TPC commands may be provided in an uplink grant DCI of the corresponding cell for PUSCH power control.

For multiple connectivity, a downlink grant of PCellSCG may convey TPC commands since the PCellSCG has PUCCH configured on the uplink. In such instances, PUCCH format <NUM> resource allocation may be used to denote one of several (e.g., four) possible values configured by higher layers. When PCellSCG is the only cell in SCG, PUCCH format <NUM> resource allocation may not be conveyed and, therefore, PUCCH format <NUM> may not be available in such situations. This may be fine because PUCCH format <NUM> is generally intended for carrier aggregation and larger ACK/NACK (A/N) payload.

The power control component <NUM> may support power scaling and prioritization when the UE <NUM> is power limited. In such scenarios, carrier aggregation principles may be utilized. For example, PUCCHs may be prioritized over other channels. The power control component <NUM> may determine whether to give higher priority to PUCCH on the PCell over PUCCH on the PCellSCG, or scale uniformly across PUCCHS. In another example, PUSCHs carrying UCI may be prioritized. The power control component <NUM> may determine whether to give higher priority to PUSCH with UCI on the PCell over PUSCH with UCI on the PCellSCG, or scale uniformly across PUSCHs with UCI. In yet another example, prioritization may occur among PUSCHs on component carriers in MSG and SCG. The power control component <NUM> may prioritize among PUSCHs on component carriers in MSG and SCG by, for example, giving the higher priority to the MSG PUSCHs or scaling uniformly across all PUSCHs.

With respect to the pathloss estimation component <NUM>, in carrier aggregation, the pathloss estimation of a cell may be performed either based on the corresponding downlink component carrier of the given cell or on the primary cell (e.g., PCell or PCellSCG). The choice may be based on which TAG is associated with the serving cell. The same or similar mechanism may be used for dual connectivity. For example, the pathloss estimation may be based on PCellSCG for the cells in SCG.

With respect to the SRS component <NUM>, the SRS in carrier aggregation may be configured for each serving cell. For example, the UE <NUM> may be configured with SRS parameters for trigger type <NUM> (periodic) and trigger type <NUM> (aperiodic) on each serving cell. The SRS parameters may be serving cell specific and semi-statically configurable by higher layers. These carrier aggregation principles may also be used for dual connectivity.

With respect to the power headroom reporting component <NUM>, two types of power headroom may be supported: Type <NUM>, for which power headroom (PH) = Pcmax,c - PUSCH tx_pwr, and type <NUM>, for which PH = Pcmax,c - PUCCH_tx_pwr - PUSCH tx_pwr, where Pcmax,c is the nominal UE maximum transmit power, PUSCH tx_pwr is the estimated PUSCH transmit power, and PUCCH_tx_pwr is the estimated PUCCH transmit power. Type <NUM> may apply to both PCells and SCells. Type <NUM> may apply to PCells and PUCCH and PUSCH simultaneous transmission. In the context of multiflow (e.g., aggregation), for the case of PUCCH on SCell, Type <NUM> may apply to the SCell as well. For example, RRC may be used to configure the UE <NUM> SCell to transmit/receive (Tx/Rx) Type <NUM> power headroom and the SCell to perform scheduling taking into account information provided in a report.

In case of multiple PUCCHs/PUSCHs on a single component carrier, the PH formula may be adjusted to take into account additional channels. For example, for Type <NUM>, PH = Pcmax,c - (PUSCH_tx_pwr_1+ PUSCH tx_pwr_2+. ), and for Type <NUM>, PH = Pcmax,c - (PUCCH_tx_pwr_1+ PUCCH_tx_pwr_2+. ) - (PUSCH_tx_pwr_1+ PUSCH_tx_pwr_2+. In this example, PUSCH_tx_pwr_1 may refer to the transmit power estimate for a first PUSCH and PUSCH _tx_power_ <NUM> may refer to the transmit power estimate for a second PUSCH. Similarly, PUCCH _tx_pwr_ <NUM> may refer to the transmit power estimate for a first PUCCH and PUCCH_tx_power _2 may refer to the transmit power estimate for a second PUCCH.

With respect to the logical channel prioritization component <NUM>, packet (e.g., data packet) building across component carriers may depend on various aspects. For example, when the UE <NUM> is provided with valid uplink grants in several serving cells in one subframe, the order in which the grants are processed during logical channel prioritization and whether joint or serial processing is applied may be decided by the logical channel prioritization component <NUM> in the UE <NUM>. There may not be a mapping between logical channel traffic and SPS or dynamic grant. For example, data from any logical channel may be sent on any granted PUSCH resources (SPS or dynamic).

The same approach as described above for logical channel prioritization ma be used for dual connectivity with packet aggregation. For example, the buffer status report (BSR) logical channel ID (LCID) coefficients may be signaled and used for logical channel payloadto-grant mapping. In the case of dual connectivity for bearer aggregation, logical channels may be mapped to specific uplink grants. For example, logical channels corresponding to bearers configured on the MeNodeB <NUM>-a are to be mapped to the uplink grants received on component carriers of the MCG. Similarly, logical channels corresponding to bearers configured on the SeNodeB <NUM>-b are to be mapped to the uplink grants received on component carriers of the SCG.

<FIG> is a diagram conceptually illustrating an example of carrier aggregation within the nodes in dual connectivity in accordance with an aspect of the present disclosure. The wireless communications network <NUM> shows an example of carrier aggregation in connection with the multiple connectivity CA manager component <NUM> and/or the CA control component <NUM> of <FIG>. In particular, wireless communications network <NUM> shows an example of controlling transmission of uplink control information over PUCCH in dualconnectivity carrier aggregation. In this example, a UE <NUM> is connected with different nodes using different carrier frequencies. The same carrier aggregation principles used with one node may also be used with the other node. In this example, a master eNodeB <NUM>-a (MeNodeB or MeNB) and a secondary eNodeB <NUM>-b (SeNodeB or SeNB) are shown in communication with the UE <NUM>. The MeNodeB <NUM>-a, the SeNodeB <NUM>-b, and the UE <NUM> may be one of the base stations/eNodeBs and UEs as described in various Figures. For example, the UE <NUM> may correspond to the UE <NUM> of <FIG>. In the example illustrated in <FIG>, there is a single uplink component carrier (f1) being used between the UE <NUM> and the MeNodeB <NUM>-a, and there are two uplink component carriers (f2 and f3) being used between the UE <NUM> and the SeNodeB <NUM>-b. The PUCCH for the MeNodeB <NUM>-a may be carried on component carrier (f1) and the PUCCH for the SeNodeB <NUM>-b may be carried on component carrier (f2), which is the cell with the smallest cell index within the SCG for SeNodeB <NUM>-b. For example, the component carrier (f2) may be configured as the PCellSCG.

Returning to the wireless communications network <NUM> of <FIG>, and as noted above, one PUCCH may be configured for the UE <NUM> on an uplink component carrier for each of the MeNodeB <NUM>-a and the SeNodeB <NUM>-b. PUCCH on one of the component carriers from both MCG (associated with MeNodeB <NUM>-a) and SCG (associated with SeNodeB <NUM>-b) carriers uplink carrier information (UCI) for all the component carriers associated within the cell group. RRC configuration may be used to specify which component carrier (or cell) from MCG and which component carrier (or cell) from SCG carriers the PUCCH for the respective cell group. In one implementation, when the PCell for UE <NUM> is on the MeNodeB <NUM>-a and the PCellSCG is on the SeNodeB <NUM>-b, then PUCCH for MeNodeB/MCG is on PCell and PUCCH for SeNodeB/SCG is on PCellSCG.

In yet another aspect of the wireless communications network <NUM>, if UCI is to be transmitted on PUSCH instead of PUCCH, the component carrier from each of the MCG associated with the MeNodeB <NUM>-a and the SCG associated with the SeNodeB <NUM>-b having the smallest cell index (e.g., cell index of "<NUM>") within the respective cell group that transmits the PUSCH may be used to carry the UCI for the corresponding cell group.

In yet another aspect of the wireless communications network <NUM>, the PUCCH format for ACK/NACK feedback for each group (e.g., MCG associated with MeNodeB <NUM>-a, SCG associated with SeNodeB <NUM>-b) is determined based on the number of component carriers in a group instead of being based on the total number of component carriers. For example, PUCCH format 1b with channel selection may be used when a group of cells includes two (<NUM>) component carriers, while PUCCH format <NUM> may be used when a group of cells includes two (<NUM>) or more component carriers (or non-carrier aggregation (CA) time division duplexing (TDD)).

<FIG> is a block diagram conceptually illustrating an example of a secondary eNodeB <NUM>-b (SeNodeB or SeNB) having configured components in accordance with an aspect of the present disclosure. A UE <NUM>, a core network <NUM> (with backhaul links <NUM>), a MeNodeB <NUM>-a, and the SeNodeB <NUM>-b of diagram <NUM> may be one of the UEs, core networks, and base stations/eNodeBs as described in various Figures. For example, the UE <NUM> may correspond to the UE <NUM> of <FIG> or the UE <NUM> of <FIG>. The SeNodeB <NUM>-b and the UE <NUM> may communicate over communications link <NUM>-b, and the MeNodeB <NUM>-a and the UE <NUM> may communicate over communication link <NUM>-a. Communication links <NUM>-a and <NUM>-b may be an examples of the communications links <NUM> of <FIG>. The SeNodeB <NUM>-b may communicate with other network entities (e.g., base stations/eNodeBs) through the core network <NUM>.

The SeNodeB <NUM>-b may include a multiple connectivity CA manager component <NUM> and a transmitter/receiver component <NUM>. The multiple connectivity CA manager component <NUM> may configure the SeNodeB <NUM>-b to operate a group of cells (SCG) of the SeNodeB <NUM>-b and one cell of the group of cells may be configured as a PCellSCG. The multiple connectivity CA manager component <NUM> may be configured to transmit, to the UE <NUM>, configuration information through the PCellSCG for the UE <NUM> to communicate with the SeNodeB <NUM>-b while in concurrent communication with the MeNodeB <NUM>-a, and where the SeNodeB <NUM>-b is non-collocated with the MeNodeB <NUM>-a. The transmission of the configuration information to the UE <NUM> may be performed at least in part by the transmitter/receiver component <NUM>.

The multiple connectivity CA manager component <NUM> may include a PCellSCG configuration component <NUM>, a UE configuration component <NUM>, a secondary master group component <NUM>, and a semi-persistent scheduling component <NUM>.

The PCellSCG configuration component <NUM> may be configured to handle various aspects described herein for configuring one of the cells in the SCG of the SeNodeB <NUM>-b to operate as a PCellSCG.

The UE configuration component <NUM> may be configured to handle various aspects described herein for determining, processing, and/or transmitting configuration information to the UE <NUM>. The UE configuration component <NUM> may also handle aspects of receiving uplink control information from the UE <NUM> over PUCCH.

The secondary cell group component <NUM> may be configured to handle various aspects described herein for managing the secondary cells of the SCG. For example the secondary cell group component <NUM> may perform cross-carrier control where one cell may convey control for another cell. The secondary cells of the SCG may not be able to cross-carrier control the PCellSCG. In multiple connectivity carrier aggregation, cross-carrier control may be performed within those cells that belong to the same carrier group.

The semi-persistent scheduling component <NUM> may be configured to handle various aspects described herein for configuring semi-persistent scheduling on the PCellSCG. For example, for dual connectivity, it may be desirable to allow SPS on the PCellSCG. Semi-persistent scheduling or SPS may provide additional flexibility in operation. For example, in bearer aggregation, bearers suitable for semi-persistent scheduling may be configured on both the SeNodeB <NUM>-b and the MeNodeB <NUM>-a. In packet aggregation, a packet of a bearer suitable for semi-persistent scheduling transmission may be routed to both the SeNodeB <NUM>-b and the MeNodeB <NUM>-a.

The components and/or subcomponents described above with respect to <FIG> and <FIG> may be implemented in software, hardware, or a combination of software and hardware. Moreover, at least part of the functions of two or more of the components and/or subcomponents may be combined into a single component or single subcomponent and/or at least part of the function(s) of one component or subcomponent may be distributed among multiple components and/or subcomponents. The components and/or subcomponents of a single device (e.g., UE <NUM>) may be in communication with one or more components and/or subcomponents of the same device.

<FIG> is a block diagram conceptually illustrating an example hardware implementation for an apparatus <NUM> employing a processing system <NUM> in accordance with an aspect of the present disclosure. The processing system <NUM> includes a multiple connectivity CA manager component <NUM>. In one example, the apparatus <NUM> may be the same or similar, or may be included with one of the eNodeBs described in various Figures. In such example, the multiple connectivity CA manager component <NUM> may correspond to, for example, the multiple connectivity CA manager component <NUM>. In another example, the apparatus <NUM> may be the same or similar, or may be included with one of the UEs described in various Figures. In such example, the multiple connectivity CA manager component <NUM> may correspond to, for example, the multiple connectivity CA manager component <NUM> and may include the functionality of the information convergence entity component <NUM>. The processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits including one or more processors (e.g., central processing units (CPUs), microcontrollers, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs)) represented generally by the processor <NUM>, and computer-readable media, represented generally by the computer-readable medium <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. A bus interface <NUM> provides an interface between the bus <NUM> and a transceiver <NUM>, which is connected to one or more antennas <NUM> for receiving or transmitting signals. The transceiver <NUM> and the one or more antennas <NUM> provide a mechanism for communicating with various other apparatus over a transmission medium (e.g., over-the-air). The transceiver <NUM> may be an example of the transmitter/receiver components <NUM> and <NUM> of <FIG> and <FIG>, respectively. Depending upon the nature of the apparatus, a user interface (UI) <NUM> (e.g., keypad, display, speaker, microphone, joystick) may also be provided.

The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described herein for any particular apparatus. The computer-readable medium <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The multiple connectivity CA manager component <NUM> as described above may be implemented in whole or in part by processor <NUM>, or by computer-readable medium <NUM>, or by any combination of processor <NUM> and computer-readable medium <NUM>.

<FIG> is a flowchart illustrating a method <NUM> for aggregation in dual connectivity in a UE (e.g., UE <NUM>) in accordance with an aspect of the present disclosure. Some or all of the method <NUM> may be implemented by the UEs of <FIG> and/or the processing system <NUM> of <FIG>.

At block <NUM>, a wireless device (e.g., UE) may receive first configuration information to communicate with a first network entity (e.g., MeNodeB or MeNB) through a first primary cell (e.g., PCell) of the first network entity. For example, the multiple connectivity CA manager component <NUM>, the information convergence entity component <NUM>, and/or the transmitter/receiver component <NUM> of <FIG> may receive the configuration information.

At block <NUM>, the wireless device may receive second configuration information to communicate with a second network entity (e.g., SeNodeB or SeNB) through a second primary cell (e.g., PCellSCG) of the second network entity. For example, the multiple connectivity CA manager component <NUM>, the information convergence entity component <NUM>, and/or the transmitter/receiver component <NUM> of <FIG> may receive the configuration information. The second network entity may be non-collocated with the first network entity.

At block <NUM>, an information convergence entity in the wireless device may aggregate the first configuration information and the second configuration information received from the first network entity and the second network entity when the wireless device is in communication with the first network entity and the second network entity. For example, the information convergence entity component <NUM> of <FIG> may aggregate the configuration information.

Optionally at block <NUM>, the wireless device may transmit PUCCH for cells operated by the first network entity over the first primary cell and PUCCH for cells operated by the second network entity over the second primary cell. For example, the multiple connectivity CA manager component <NUM>, the CA control component <NUM>, the information convergence entity component <NUM>, and/or the transmitter/receiver component <NUM> of <FIG> may operate to transmit PUCCH.

<FIG> is a flowchart illustrating a method <NUM> for aggregation in dual connectivity in a secondary eNodeB (e.g., eNodeB <NUM>-a) in accordance with an aspect of the present disclosure. Some or all of the method <NUM> may be implemented by the SeNodeBs/SeNBs of various Figures and/or the processing system <NUM> of <FIG>.

At block <NUM>, a second network entity (e.g., SeNodeB) is configured to operate a cell in a group of cells (e.g., SCG) as a second primary cell (PCellsco). For example, the multiple connectivity CA manager component <NUM> and/or the PCellSCG configuration component <NUM> of <FIG> may configure a cell in an SCG as a secondary primary cell.

At block <NUM>, the second network entity may transmit to a wireless device (e.g., UE) configuration information through the second primary cell for the wireless device to communicate with the second network entity while in communication with a first network entity (e.g., MeNodeB) operating a first set of cells having a first primary cell (e.g., PCell). For example, the multiple connectivity CA manager component <NUM> and/or the transmitter/receiver <NUM> of <FIG> may transmit configuration information. The first network entity may be non-collocated with the second network entity.

Optionally at block <NUM>, the second network entity may receive PUCCH for cells in the second set of cells over the second primary cell, where the first network entity receives PUCCH for cells in the first set of cells over the first primary cell. For example, the multiple connectivity CA manager component <NUM>, the UE configuration component <NUM>, and/or the transmitter/receiver component <NUM> may operate to receive PUCCH for one or more cells.

The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein.

Claim 1:
A method (<NUM>) for dual connectivity in wireless communications, the method comprising:
configuring (illo) a second network entity (<NUM>-b, <NUM>-b) to operate a cell in a second set of cells as a second primary cell (<NUM>-a), wherein the second primary cell (<NUM>-a) is configured to carry physical uplink control channel, PUCCH, for cells in the second set of cells, and is characterized by being configured to perform pathloss estimation for other cells in the second set of cells and to configure the cells in the second set of cells to have the same discontinuous reception, DRX, configuration; and
transmitting (<NUM>), to a wireless device (<NUM>, <NUM>) connected to a first primary cell (<NUM>-a) operated by a first network entity (<NUM>-a, <NUM>-a), configuration information through the second primary cell (<NUM>-a) for the wireless device (<NUM>, <NUM>) to communicate with the second network entity (<NUM>-b, <NUM>-b);
wherein the second primary cell (<NUM>-a) is further configured to:
configure common search space for the second network entity (<NUM>-b, <NUM>-b).