Patent Grant
11063645
Embodiments of this disclosure relate to wirelessly communicating multiple-input multiple output (MIMO) data.
The types of modern computing devices continues to increase along with the differing and dynamic needs of each device. The wireless communication systems providing services to such devices are facing increasing constraints on resources and demands for quality and quantities of service. In certain multiple-input multiple-output wireless communication systems, a peak data rate and/or rank determined by a number of antennas and/or a number of transmit/receive chains of a user equipment arranged to connect to a network system can limit the rate and/or quality at which data is exchanged. Accordingly, improvements in providing wireless communication services in a multiple-input multiple-output system are desired.
Embodiments of this disclosure will now be described, by way of non-limiting example, with reference to the accompanying drawings.
The innovations described in the claims each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the claims, some prominent features of this disclosure will now be briefly described.
One aspect of this disclosure is a user equipment that includes one or more antennas, a peer-to-peer wireless interface, and a processor in communication with the one or more antennas and the peer-to-peer wireless interface. The one or more antennas are configured to receive a first part of a multiple-input multiple-output (MIMO) downlink data transmission from one or more serving nodes. The peer-to-peer wireless interface is configured to receive a second part of the MIMO downlink data transmission from at least one secondary user equipment. The processor is configured to aggregate the first part of the MIMO downlink data transmission together with the second part of the MIMO downlink data transmission.
Another aspect of this disclosure is a method of receiving a multiple-input multiple-output (MIMO) downlink data. The method includes receiving, using one or more antennas of a primary user equipment, a first part of the MIMO downlink data transmission from one or more serving nodes. The method also includes receiving, using a peer-to-peer wireless interface, a second part of the MIMO downlink data transmission from at least one secondary user equipment. The method further includes processing, using a processor of the primary user equipment, the first part of the MIMO downlink data transmission together with the second part of the MIMO downlink data transmission.
Another aspect of this disclosure is a user equipment that includes one or more antennas configured to transmit a first part of a multiple-input multiple-output (MIMO) uplink data transmission, a peer-to-peer wireless interface configured to transmit a second part of the MIMO uplink data transmission to at least one secondary user equipment, and a processor in communication with the one or more antennas and the peer-to-peer wireless interface. The processor is configured to cause transmission of the first part of the MIMO uplink data transmission via the one or more antennas and to cause transmission of a second part of the MIMO uplink data transmission via the peer-to-peer wireless interface.
Another aspect of this disclosure is a method of processing downlink data. The method includes establishing a communication channel between a primary user equipment and a secondary user equipment via a peer-to-peer wireless link between the primary user equipment and the secondary user equipment. The method also includes while the primary user equipment is receiving first multiple-input multiple-output (MIMO) downlink data for the primary user equipment via a cellular communication, receiving second MIMO downlink data for the primary user equipment using one or more antennas of the secondary user equipment. The method also includes transmitting the second MIMO downlink data to the primary user equipment via the communication channel.
Another aspect of this disclosure is a user equipment that includes one or more antennas configured to receive a part of a multiple-input multiple-output (MIMO) downlink data transmission, a peer-to-peer wireless interface configured to communicate with a primary user equipment, and a processor in communication with the one or more antennas and the peer-to-peer wireless interface. The processor is configured to receive the part of the MIMO downlink data transmission via the one or more antennas, determine that the part of the MIMO downlink data is associated with the primary user equipment, and cause transmission of symbol level data corresponding to the part of the MIMO downlink data via the peer-to-peer wireless interface to the primary user equipment.
Another aspect of this disclosure is a method of processing uplink data. The method includes establishing a communication channel between a secondary user equipment and a primary user equipment via a peer-to-peer wireless interface of the secondary user equipment. The method also includes while the primary user equipment is transmitting first multiple-input multiple-output (MIMO) uplink data for the primary user equipment to a network system via a cellular communication, receiving, by the secondary user equipment, second MIMO uplink data transmission from the primary user equipment via the communication channel. The method further includes transmitting, using one or more antennas of the secondary user equipment, the second MIMO uplink data to the network system.
Another aspect of this disclosure is a method of processing uplink data. The method includes receiving, by a network system, a first uplink data transmission associated with a primary user equipment from the primary user equipment. The primary user equipment is configured to transmit uplink data at a rate of up to a peak uplink data rate. The method also includes receiving, by the network system, a second uplink data transmission associated with the primary user equipment from a secondary user equipment. The method further includes processing, by the network system, data associated with the first uplink data transmission together with data associated with the second uplink data transmission so as to process uplink data associated with the primary user equipment at a rate of greater than the peak uplink data rate of the primary user equipment.
Another aspect of this disclosure is a method of transmitting downlink data. The method includes generating, by a network system, downlink transmission data for a primary user equipment. The method also includes while the primary user equipment is in communication with a secondary user equipment via a peer-to-peer link: transmitting, by the network system, a first part of the downlink transmission data for the primary user equipment to the primary user equipment; and transmitting, by the network system, a second part of the downlink transmission data for the primary user equipment to the secondary user equipment.
Another aspect of this disclosure is a method of transmitting downlink data. The method includes determining a secondary user equipment to enter a clone mode based on a joint spectral efficiency of a group of user equipments. The group of user equipments includes the secondary user equipment and a primary user equipment. The method includes signaling to the secondary user equipment to enter the clone mode. The method also includes while the secondary user equipment is in the clone mode, transmitting (a) first downlink data for the primary user equipment to the secondary user equipment and (b) second downlink data for the primary user equipment to the primary user equipment.
Another aspect of this disclosure is a method of multiple-input multiple-output (MIMO) wireless communication. The method includes receiving, by a network system, first uplink MIMO data associated with a primary user equipment from the primary user equipment. The method also includes receiving, by the network system, second uplink MIMO data associated with the primary user equipment from a secondary user equipment, wherein the primary user equipment is in communication with the secondary user equipment via a peer-to-peer link. The method further includes aggregating, by the network system, the first uplink MIMO data together with the second uplink MIMO data. In addition, the method includes transmitting, by the network system, downlink data associated with the primary user equipment to a single user equipment via cellular communications.
Another aspect of this disclosure is a method of multiple-input multiple-output (MIMO) wireless communication. The method is performed while a primary user equipment is in communication with a secondary user equipment via a peer-to-peer link. The method includes transmitting, by a network system, a first part of a downlink MIMO data transmission for the primary user equipment to the primary user equipment. The method also includes transmitting, by the network system, a second part of the downlink MIMO data transmission for the primary user equipment to the secondary user equipment. The method further includes receiving, by the network system, uplink data for the primary user equipment from a single user equipment via cellular communications.
The present disclosure relates to U.S. patent application Ser. No. 16/224,643, titled “USER EQUIPMENT CONFIGURED FOR INCREASED DATA RATE,” U.S. patent application Ser. No. 16/224,528, titled “USER EQUIPMENT WITH CELLULAR LINK AND PEER-TO-PEER LINK,” and U.S. patent application Ser. No. 16/224,568, titled “UNBALANCED WIRELESS COMMUNICATION WITH GROUP OF DEVICES,” each filed on even date herewith and the disclosures of each of which are hereby incorporated by reference in their entireties herein.
For purposes of summarizing the disclosure, certain aspects, advantages and novel features of the innovations have been described herein. It is to be understood that not necessarily all such advantages may be achieved in accordance with any particular embodiment. Thus, the innovations may be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other advantages as may be taught or suggested herein.
The following description of certain embodiments presents various descriptions of specific embodiments. However, the innovations described herein can be embodied in a multitude of different ways, for example, as defined and covered by the claims. In this description, reference is made to the drawings where like reference numerals can indicate identical or functionally similar elements. It will be understood that elements illustrated in the figures are not necessarily drawn to scale. Moreover, it will be understood that certain embodiments can include more elements than illustrated in a drawing and/or a subset of the elements illustrated in a drawing. Further, some embodiments can incorporate any suitable combination of features from two or more drawings. The headings provided herein are for convenience only and do not necessarily affect the scope or meaning of the claims.
In a network that has a relatively large number of transmit and receive antennas at a base station for communicating with user equipment (UE), a peak rate of a given UE can be limited by the multiple-input multiple-output (MIMO) capabilities of the UE. Such MIMO capabilities can include a number of transmit and/or receive chains of the UE and/or a number of antennas of the UE configured to communicate with a network system. For example, if a network system is relatively lightly loaded and has 64×64 transmit and receive chains and a UE has a 2×2 transmit and receive configuration, the UE peak rate can be limited to rank 2 MIMO in both receiving downlink data and transmitting uplink data. Rank can refer to a number of spatial layers available for cellular communications with a UE. Rank is nominally limited by the minimum number of transmit and receive antennas for a link, in this example 2. The rank may be limited by the channel structure, which can further limit the number of spatial layers to less than the antenna limit.
Aspects of this disclosure relate to using a peer-to-peer (P2P) link between a primary UE to a secondary UE in proximity to enable a higher rate data and/or peak data rate for the primary UE. This can enable the primary UE to exchange MIMO data at a higher rank compared to the primary UE communicating with the network system without the P2P link and the secondary UE. The higher effective MIMO order can be achieved with a combination of a cellular link of a primary UE and the primary UE receiving data via the P2P link and a cellular link of the secondary UE. Such a configuration can also enable a primary UE in a heavily congested cell of transmit-receive points (TRPs) to receive traffic from a relatively nearby and less loaded cell of TRPs for higher throughput, upon discovering and establishing a P2P link with a secondary UE in the nearby cell. A variety of methods are disclosed for using a secondary UE to increase the data rate and/or rank associated with data communications between the primary UE and a network system. For example, application routing and aggregation can allow the network system to serve two UEs with a P2P link between them with multi-user MIMO (MU-MIMO). As another example, the UEs with a P2P link between them can form a virtual higher order MIMO transceiver for the primary UE and perform combining at a physical layer through high speed sample transfer between the two UEs. Similar principles and advantages can be applied to transmitting uplink data from the two UEs. Although examples embodiments may be described in terms of a singular secondary UE; any suitable principles and advantages disclosed herein can be applied to cases where two or more secondary UEs are paired with a primary UE.
The technology disclosed herein provides a framework of enabling higher peak rate of a primary UE through a P2P link with a secondary UE for downlink data communications and/or uplink data communications. The mechanisms of achieving a higher peak data rate can be achieved using joint processing at the physical layer and/or aggregation from an application perspective. The mechanism of achieving the higher peak data rate though a higher order physical layer category and MIMO order is also disclosed.
A primary UE and a secondary UE arranged to transmit and/or receive MIMO data associated the primary UE in a coordinated manner can be referred to as a clone pair of UEs. The UEs of the clone pair can each exchange (e.g., transmit and/or receive) MIMO data associated with the primary UE with TRPs. The secondary UE can assist the primary UE in exchanging data with a network. The UEs of the clone pair can also wirelessly communicate with each other over a P2P link. The secondary UE of the clone pair can operate in a clone mode to receive and/or transmit MIMO data associated with the primary UE from and/or to one or more TRPs. In the clone mode, the secondary UE can also wirelessly communicate with the primary UE over the P2P link.
Although embodiments disclosed herein may be discussed with reference to clone pairs of 2 UEs, any suitable principles and advantages discussed herein can be implemented in applications where a group of three or more UEs are arranged to transmit and/or receive MIMO data associated with one of the UEs of the group in a coordinated manner.
A primary UE can discover one or more candidate secondary UEs. The discovery can be performed by the primary UE by itself and/or with assistance of a network system. The candidate secondary UEs can be sufficiently close to the primary UE to establish a P2P link. One or more of the candidate secondary UEs can be idle. In response to discovery, a P2P link can be established between the primary UE and a secondary UE. Data from the primary UE can be transmitted to the secondary UE via the P2P link. Subsequent data transmission to and reception from a network system can be performed, for example, via MU-MIMO and application layer aggregation. As another example, subsequent data transmission to and reception from a network system can be performed via a time-coordinated single-user MIMO (SU-MIMO) though a higher order UE category and higher order data rate request though the primary UE jointly using the TRP information of the secondary UE.
As an example of the technology described herein, a primary UE with 2 receive chains and 2 transmit chains can communicate with a 4×4 cell site with a peak data rate similar to 4×4 MIMO. The primary UE can be active and achieve a data rate corresponding to 2×2 MIMO operating by itself. A secondary UE can be discovered and a P2P link can be established between the primary UE and the secondary UE. By communicating with a network system using hardware of both the primary UE and the secondary UE, the primary UE can achieve a data rate similar to 4×4 MIMO.
The technology disclosed herein can be applied in a variety of applications. For example, two UEs can execute coordinated transmission and/or reception of MIMO data associated with one of the two UEs in applications where excessive network MIMO dimensions are available. In some instances, a higher number of TRPs of a network system are available for transmission than a total number of receive antennas across active UEs. Alternatively or additionally, a higher number of TRPs of a network system are available for receiving than total number of transmit antennas across active UEs.
As another example, nearby UEs in different spatial channels can be available for communicating with different respective TRPs of the network system. A secondary UE nearby a primary UE can establish a high quality P2P connection. The secondary UE can have one or more different preferred spatial beams from one or more TRPs of a network system than the primary UE. The secondary UE can be in relatively low mobility. In this example, the primary UE can be associated with one or more crowded TRPs that can limit service to the primary UE. The primary UE can use a P2P link and the secondary UE to operate at higher order MIMO.
MIMO Network
Various standards and protocols may be implemented in the environment 100 to wirelessly communicate data between a base station and a wireless communication device. Some wireless devices may communicate using an orthogonal frequency-division multiplexing (OFDM) digital modulation scheme via a physical layer. Example standards and protocols for wireless communication in the environment 100 can include the third generation partnership project (3GPP) Long Term Evolution (LTE), Long Term Evolution Advanced (LTE Advanced), 3GPP New Radio (NR) also known as 5G, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), Worldwide Interoperability for Microwave Access (WiMAX), and the IEEE 802.11 standard, which may be known as Wi-Fi. In some systems, a radio access network (RAN) may include one or more base station associated with one or more evolved Node Bs (also commonly denoted as enhanced Node Bs, eNodeBs, or eNBs, gNBs, or any other suitable Node Bs (xNBs)). In some other embodiments, radio network controllers (RNCs) may be provided as the base stations. A base station provides a bridge between the wireless network and a core network such as the Internet. The base station may be included to facilitate exchange of data for the wireless communication devices of the wireless network.
A wireless communication device may be referred to a user equipment (UE). The UE may be a device used by a user such as a smartphone, a laptop, a tablet computer, cellular telephone, a wearable computing device such as smart glasses or a smart watch or an ear piece, one or more networked appliances (e.g., consumer networked appliances or industrial plant equipment), an industrial robot with connectivity, or a vehicle. In some implementations, the UE may include a sensor or other networked device configured to collect data and wirelessly provide the data to a device (e.g., server) connected to a core network such as the Internet. Such devices may be referred to as Internet of Things devices (IoT devices). Any suitable UE disclosed herein can be part of a clone pair. A downlink (DL) transmission generally refers to a communication from the base transceiver station (BTS) or eNodeB to the wireless communication device, and an uplink (UL) transmission generally refers to a communication from the wireless communication device to the BTS.
The illustrated RRUs 125, 135, and 145 include multiple antennas and can provide MIMO communications. For example, an RRU may be equipped with various numbers of transmit antennas (e.g., 2, 4, 8, or more) that can be used simultaneously for transmission to one or more receivers, such as a UE. Receiving devices may include more than one receive antenna (e.g., 2, 4, etc.). An array of receive antennas may be configured to simultaneously receive transmissions from the RRU. Each antenna included in an RRU may be individually configured to transmit and/or receive according to a specific time, frequency, power, and direction configuration. Similarly, each antenna included in a UE may be individually configured to transmit or receive according to a specific time, frequency, power, and direction configuration. The configuration may be provided by the BBU 110. The direction configuration may be generated based on a network estimate using channel reciprocity and/or determined based on feedback from UE via selection of a beamforming codebook index, or a hybrid of the two.
The service areas shown in
A user equipment 152 may be located with an area with overlapping service (e.g., the service area 120 and the service area 130). Each device in the environment 100 may have different performance needs which may, in some instances, conflict with the needs of other devices.
Clone pairs can be formed in the environment 100. For example, there can be more MIMO dimensions from the RRU 125 available to the UE 162 than the UE 162 can process acting alone in certain instances. In such a case, the UE 162 can form a clone pair with the UE 152 to jointly communicate with the RRU 125 in a manner that uses more MIMO dimensions than the UE 162 would alone. As another example, the TRPs of the RRU 125 can be limited for serving the cluster of UEs 160 and the UE 162 in some instances. In such a case, the UE 162 can form a clone pair with the UE 152 and also exchange data associated with the UE 162 with one or more TRPs of the RRU 135. This can enable more TRPs to serve the UE 162 than compared to the UE 162 communicating with the network system alone.
Increasing Rank and/or Data Rate with a Pair of UEs
In various MIMO network environments, a relatively large number of TRPs are available for communicating with UEs. A UE peak data rate can be limited by a antennas and/or streams of the UE in certain instances. For example, a UE with 2 receive antennas and 2 transmit antennas can have an uplink peak rate limited by rank 2 and a downlink peak rate limited by rank 2. With a relatively large number of TRPs available, a network system can have excess capacity to serve the UE. Aspects of this disclosure relate to establishing a P2P link between two UEs and using the reception and/or transmission capabilities of the two UEs to increase the data rate and/or rank associated with one of the UEs. A first UE and a second UE can both wirelessly communicate data associated with the first UE via cellular links. The first UE and the second UE can also communicate with each other via a P2P link while the first UE and the second UE are communicating with a network system via cellular links.
The example MIMO wireless communication environment 200 of
There are a large number of TRPs 204 relative to the number of antennas of the UEs in the environment 200. Accordingly, the communication rate of the primary UE 210 can be limited by the antennas and/or signal chains of the primary UE 210 when the primary UE 210 is in communication with the TRPs 204 by itself. In such a case, the TRPs 204 have excess capacity to serve the primary UE 210.
The primary UE 210 can establish a P2P link with the secondary UE 220. The P2P link can be used to exchange traffic between the primary UE 210 and the secondary UE 220. The P2P link can be a Wi-Fi link, a Bluetooth link, a cellular link, or the like. P2P communications can be out-of-band. P2P communications can be in-band in some cases. The P2P link can enable relatively fast data transfer between the primary UE 210 and the secondary UE 220. In some instances, the secondary UE 220 can process the second part of the MIMO data associated with the primary UE 210 and send the processed data to the primary UE 210 via the P2P link. The data provided over the P2P link can be samples (modulation), bits (physical layer), or bytes (higher layer). The primary UE 210 and the secondary UE 220 can together coordinate transmission and reception of MIMO data associated with the primary UE 210.
Downlink MIMO data associated with the primary UE 210 can be received by the primary UE 210 and the secondary UE 220. A first part of the MIMO data associated with the primary UE 210 can be received by the primary UE 210. A second part of the MIMO data associated with the primary UE 210 can be received by the secondary UE 220. The secondary UE 220 can provide the second part of the MIMO data associated with the primary UE 210 to the primary UE 210 via the P2P link. In the example illustrated in
A realization is to mutually exchange information over the P2P link, and each of the primary and second UE's could process 2 of the 4 MIMO layers, with the final decode data transported back to the primary UE. This approach can share the received antenna information and also share the computational processing between the primary and secondary UE's, which can together form a distributed realization of the virtual UE of higher MIMO capability.
Uplink MIMO data associated with the primary UE 210 can be transmitted by the primary UE 210 and the secondary UE 220. A processor of the primary UE 210 can cause transmission of a first part of a MIMO uplink data transmission via the antennas 214 and to cause transmission of a second part of the MIMO uplink data transmission to the secondary UE 220 via the peer-to-peer link. The secondary UE 220 can then transmit the second part of the uplink MIMO data transmission via the antennas 224. In the example illustrated in
Although the environment 200 of
Embodiments disclosed herein relate to utilizing one or more additional transmit antennas to increase the MIMO rank of a wireless transmission. An alternative approach according to an embodiment is to maintain the same MIMO rank and enable transmit diversity for paired UEs wirelessly communicating with a network system. Accordingly, a secondary UE can provide transmit diversity. Transmit diversity can be, for example, such as described in LTE or another wireless communication standard. The transmit diversity can increase the supported data rate. Examples of transmit diversity include single-frequency network (SFN) modulation and Alamouti space-time block coding (STBC).
The principles and advantages of transmission and/or reception of MIMO data can be applied to other examples beyond the examples shown in
The example MIMO wireless communication environment 300 of
In the environment 300′, the previously idle second UE 330 is used as a relay point for the first UE 320. The first UE 320 can establish a P2P link with the second UE 330 and communicate with the second RRU 304 via the P2P link and the second UE 330. The P2P link can enable spatial diversity. This can enable TRPs of the second RRU 304 to serve the first UE 320. The secondary UE 320 can enable a network system to operate at higher-order MU-MIMO. For example, when the first UE 320 and second UE 330 are similar devices, the rank of MIMO communication between the first UE 320 and the network system can be doubled. The actual MIMO order increase can depend on one or more spatial channel conditions and/or capabilities of the second UE 330 and/or the first UE 320.
The principles and advantages disclosed with reference to
Network System
The base band unit 402 can be coupled with at least one remote radio unit 490. The base band unit 402 can be coupled with a plurality of remote radio units 490. Such remote radio units 490 can be distributed. A remote radio unit 490 can include at least a first antenna 496 and a second antenna 498 for MIMO wireless communications. Any antenna disclosed herein, such as the antenna 496 or the antenna 498, can be referred to as antenna element. A remote radio unit can include any suitable number of antennas and/or arrays of antennas. The antennas 496 and 498 of the RRU 490 can be coupled with a radio frequency (RF) front end 494. The RF front end 494 can process signals received via the antennas 496 and/or 498. Part of processing a signal may include providing the signal to a transceiver 420 included in the BBU 402. The RF front end 494 can process signals provided by the transceiver 420 for transmission via the antennas 496 and/or 498.
As illustrated, the BBU 402 includes a processor 405, a data store 410, a beamformer 415, a transceiver 420, and a bus 480. The bus 480 can couple several elements of the BBU 402. The illustrated processor 405 includes a network monitor 425, a peer pairing engine 430, and a peer data processor 435.
The processor 405 can include any suitable physical hardware configured to perform the functionality described with reference to the processor 405 and elements thereof. The processor 405 can include a processor configured with specific executable instructions, a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device such as field programmable gate array (FPGA), the like, or any combination thereof designed to perform the functions described herein. The processor 405 can be implemented by any suitable combination of computing devices and/or discrete processing circuits in certain applications.
The network monitor 425 can detect one or more characteristics of the network such as areas where TRPs of the network system have excess capacity, areas that are relatively heavily loaded, or the like. The peer pairing engine 430 can receive network characteristic data from the network monitor 425 and use the network characteristic data in determining a clone pair. The network monitor 425 can be implemented by dedicated circuitry of the processor 405 and/or by circuitry of the processor 405 that can be used for other functionality.
In certain instances, the network system can pair a primary UE and a secondary UE for coordinated reception and transmission of MIMO data associated with the primary UE. The peer pairing engine 430 can pair the primary UE with the secondary UE in some applications. In response to determining a clone pair, the peer pairing engine 430 can send a clone pairing command to primary UE and/or secondary UE to initiate a clone pair. The peer pairing engine 430 can be implemented by dedicated circuitry of the processor 405 and/or by circuitry of the processor 405 that can be used for other functionality.
The pairing determination can be based on pairing information transmitted by the primary UE and/or the secondary UE to the network system. The peer pairing engine 430 can determine a clone pair based on joint spectral efficiency of a pair of UEs. The joint spectral efficiency can be transmitted to the network system by a primary UE. In some instances, the peer pairing engine can compute joint spectral efficiency for a pair of UEs based on information received from each UE of the pair.
The BBU 402 can receive information from a plurality of UEs and take into account more information than available to a single UE or a pair of UEs in determining a clone pair. Accordingly, the peer pairing engine 430 can take into account pairing information received from a primary UE and/or secondary UE and additional network information in determining the clone pair. The additional network information can include, for example, one or more of mobility state information for one or more UEs, spatial channel state conditions for one or more UEs, system load information, characteristics of one or more UEs (e.g., a traffic state, an amount of battery life, or a device type), information associated with available TRPs associated with one or more of the UEs, the like, or any suitable combination thereof.
In another mode of operation, the peer pairing engine 430 can decide whether to grant a tunnel request from a primary UE to setup a tunnel between the primary UE and the network system that goes through the secondary UE. In response to granting such a request, the network system can set up a tunnel through the secondary UE to the primary UE, for example, based on a dual connectivity protocol.
The peer data processor 435 of the BBU 402 can process and/or aggregate MIMO data associated with a primary UE for coordinated communication with a clone pair. For example, the peer data processor 435 can receive downlink MIMO data for a primary UE, cause a first part of the downlink data for the primary UE to be transmitted to the primary UE, and cause a second part of the downlink data for the primary UE to be transmitted to a secondary UE, in which the secondary UE has a P2P link established with the primary UE. This can enable the primary UE to receive the downlink MIMO data with higher rank and/or at a higher data rate.
As another example, the peer data processor 435 can receive a first part of uplink MIMO data associated with a primary UE from the primary UE, receive a second part of uplink MIMO data associated with the primary UE from a secondary UE, and jointly process and/or combine the first part and the second part of the MIMO data associated with the primary UE.
The peer data processor 435 can be implemented by dedicated circuitry of the processor 405 and/or by circuitry of the processor 405 that can be used for other functionality.
As illustrated, the processor 405 is in communication the data store 410. The data store 410 include instructions that can be executed by the processor 405 to implement any suitable combination of the features described herein. In some implementations, the data store 410 can retain channel information for UEs served by the BBU 402. The data store 410 may be indexed by UE identifier and/or RRU identifier. This can expedite identification of previously communicated scheduling information for the UE and for monitoring network conditions (e.g., number of UEs allocated to an RRU or antenna element of an RRU).
The beamformer 415 can generate parameters for the serving nodes (e.g., RRUs) for a primary UE and a secondary UE. The parameters can include one or more of transmission mode, time, frequency, power, beamforming matrix, tone allocation, or channel rank. The beamformer 415 can determine optimal parameters for RRUs 490 coupled with the BBU 402 that facilitate a network-wide optimization of downlink data transmissions. Similar functionality can be implemented for receiving uplink data transmission.
The illustrated processor 405 is in communication the transceiver 420. The transceiver 420 includes a receiver and a transmitter. The receiver can process signals received from the RF front end 494. The transmitter can provide signals to the RF front end 494 for transmission via one or more antennas 496 and/or 498.
User Equipment
A variety of different UEs can be part of a clone pair. Such UEs can include any suitable UE disclosed herein. Certain UEs can function as either a primary UE or a secondary UE. Some UEs can only function as a primary UE of a clone pair. Various UEs can only function as a secondary UE of a clone pair. As example UE that can function as either a primary UE or a secondary UE of a clone pair will be discussed with reference to
The UE 500 includes circuitry for cellular communications. The transceiver 550 and the radio frequency front end 555 can generate signals for uplink cellular data transmissions via the antennas 562 and 564. The transceiver 550 includes a transmitter and a receiver. The transmitter can include one or more transmit chains. In certain instances, the transmitter includes a plurality of transmit chains. The number of transmit chains can set a maximum uplink data rate and/or rank for MIMO data transmitted by the antennas of the UE 500 to a network system. In certain instances, the number of antennas available for wirelessly transmitting uplink data to the network system can set a maximum uplink data rate and/or rank for MIMO data transmitted by the antennas of the UE 500 to a network system.
The transceiver 550 and the radio frequency front end 555 can process downlink cellular data transmissions received via the antennas 562 and 564. The receiver of transceiver 550 can include one or more receive chains. In certain instances, receiver can include a plurality of receive chains. The number of receive channels can limit maximum downlink data rate and/or rank for MIMO data received by the antennas of the UE 500 from a network system. In certain instances, the number of antennas available for wirelessly receiving downlink data from the network system can set a maximum downlink data rate and/or rank for MIMO data received by the antennas of the UE 500 from the network system.
The UE 500 can include any suitable number of antennas for wirelessly communicating with a network system. The antennas of the UE 500 can include one or more receive only antennas and/or one or more transmit only antennas. The antennas of the UE 500 can include one or more transmit and receive antennas configured to transmit and receive wireless data.
The UE 500 includes circuitry for peer-to-peer wireless communications with another UE. The peer-to-peer wireless communications can be over a non-cellular communication channel. A peer-to-peer wireless interface can refer to circuitry of the UE 500 configured to wirelessly communicate (e.g., receive and/or transmit) data to another UE via a peer-to-peer communication channel. As shown in
The wireless signals exchanged over the peer-to-peer link can be non-cellular wireless signals. The non-cellular wireless signals can be in accordance with a wireless local area network (WLAN) standard or a wireless personal area network (WPAN) standard. The non-cellular wireless signals can be Bluetooth signals, Wi-Fi signals, ZigBee signals, or the like. The non-cellular wireless signals can have a shorter signal range than cellular signals. In some instances, the non-cellular wireless signals can have a range of about 300 feet or less. The non-cellular wireless signals can have a range of about 150 feet or less in certain applications. The non-cellular wireless signals can have a range of about 35 feet or less in some other applications. In some instances, the wireless signals exchanged over the peer-to-peer link can be cellular signals.
The processor 505 can include any suitable physical hardware configured to perform the functionality described with reference to the processor 505 and elements thereof. The processor 505 can include a processor configured with specific executable instructions, a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device such as field programmable gate array (FPGA), the like, or any combination thereof designed to perform the functions described herein. The processor 505 can be implemented by any suitable combination of computing devices and/or discrete processing circuits in certain applications. The peer selector 506 can be implemented by dedicated circuitry of the processor 505 and/or by circuitry of the processor 505 that can be used for other functionality. The peer communications processor 508 can be implemented by dedicated circuitry of the processor 505 and/or by circuitry of the processor 505 that can be used for other functionality.
In certain instances, the UE 500 can initiate a clone pair. The UE 500 can function as a primary UE in certain instances. The peer selector 506 can perform functions related to selecting a secondary UE for a clone pair with UE 500 serving as a primary UE. For example, the peer selector 506 can cause the UE 500 to discover one or more candidate secondary UEs for a clone pair. The peer selector 506 can execute functionality associated with one or more of collecting data from one or more candidate secondary UEs, determining joint spectral efficiency of possible clone pairs, or prioritizing secondary UEs. The peer selector 506 can send pairing information to a network system for making a pairing decision in certain applications. In some other instances, the peer selector 506 can make a pairing decision and initiate a clone pair. Examples of such functionalities of the peer selector 506 are discussed with reference to
As discussed above, the UE 500 can function as a secondary UE of a clone pair. The peer selector 506 can perform functionality associated with the UE 500 deciding whether to function as a secondary UE of a clone pair. For example, the peer selector 506 can accept or reject a request for the UE 500 to function as a secondary UE for a primary UE. The peer selector 506 can make this determination based on one or more of a variety of factors, such as battery life, traffic state, incentives, etc. The peer selector 506 can also initiate a confirmation or rejection of a clone pair request to be send to a primary UE. Examples of such functionalities of the peer selector 506 are discussed with reference to
The peer communications processor 508 can jointly process and/or aggregate MIMO data associated with the UE 500 when the UE 500 is operating as a primary UE of a clone pair. The peer communications processor 508 can jointly process and/or aggregate downlink data received via the antennas 562, 564, and 548. The peer communications processor 508 can jointly process uplink data for transmission via the antennas 562, 564, and 548. The peer communications processor 508 can establish a peer-to-peer link with another UE.
The peer communications processor 508 can perform operations associated with processing and transmitting MIMO data associated with another UE when the UE 500 is operating as a secondary UE of a clone pair. The peer communications processor 508 can cause the UE 508 to enter a clone mode to operate as a secondary UE. The peer communications processor 508 can detect that received data is associated with a primary UE. In certain applications, the peer communications processor 508 can generate symbol level data from MIMO data received from a network system, and the cause the symbol level data to be transmitted to a primary UE via the peer-to-peer link. The peer communications processor 508 can cause MIMO physical layer data to be transmitted to primary UE via the peer-to-peer link. MIMO physical layer data can include data from, for example, high definition video streaming, a relatively large content download, or a social network content sharing application. The peer communications processor 508 can manage communications with another UE over the peer-to-peer link. Examples of functionalities of the peer communications processor 508 are discussed with reference to
The processor 505 can be in communication with the signal quality analyzer 530. The signal quality analyzer 530 can analyze the quality of signals received and/or transmitted by any of the antennas of the UE 500. This can provide information associated with a spatial channel condition of the UE 500. This information can be provided to the processor 505 for determining one or more of a spectral efficiency of the UE 500, an estimated joint spectral efficiency of the UE 500 and another UE, or a relative priority of other UEs as candidate secondary UEs. In some instances, some or all of the functionality of the signal quality analyzer can be implemented by the processor 505.
The beamformer 525 can perform any suitable beamforming functionality for the UE 500. The beamformer 525 can set and/or adjust one or more parameters associated with receiving and/or transmitting signals associated with the antennas 562 and 564 of the UE 500. The beamformer 525 can be implemented by dedicated circuitry and/or circuitry of the processor 505.
The UE 500 includes a data store 510. The data store 510 can store instructions that can be executed by the processor 505 to implement any suitable features described herein. The data store 510 can data associated with candidate secondary UEs, such as joint spectral efficiency data. When the UE 500 functions as a secondary UE, the data store 510 can store an identifier of the primary UE. The identifier of the primary UE can be used by the UE 500 in functioning as a secondary UE. When the UE 500 functions as a secondary UE, the data store 510 can store any other suitable information about a paired primary UE, such as information about MIMO capabilities and/or number of antennas. The data store 510 can store any other suitable data for the UE 500. The data store 510 can include any suitable memory elements arranged to store data.
As illustrated, the UE 500 also includes a user interface 515. The user interface 515 can be any suitable user interface, such as a display and/or an audio component. In some instances, the user interface 515 can include one or more of touch screen capabilities, a button, a knob, a switch, or a slider.
Several elements included in the UE 500 may be coupled by a bus 580. The bus 580 can be a data bus, communication bus, other bus, or any suitable combination thereof to enable the various components of the UE 1200 to exchange information.
Tightly Coupled Mode
A pair of UEs can perform coordinated transmission and/or reception of MIMO data associated with one UE of the pair either as a tightly coupled pair of UEs or as a loosely coupled pair of UEs. In a tightly coupled pair of UEs, the primary UE and the secondary UE can share an identity from a network perspective. A base station can serve the primary UE and the secondary UE with a single-user MIMO operation in the tightly coupled mode. The secondary UE can send processed data to the primary UE via a P2P link for aggregation on the primary UE. Aggregation of MIMO data can be at the physical layer or a higher layer. Data received at the primary UE and secondary UE can also be jointly processed via information shared over the P2P link. Example operations for tightly coupled UE pairs are discussed with reference to
In a tightly coupled mode, the secondary UE can store information associated with the primary UE in memory, such as an identifier of the primary UE and/or information associated with MIMO capabilities of the primary UE (e.g., a number of antennas). Such information can be provided to the secondary UE from the primary UE via a P2P link. Alternatively or additionally, a network system can provide such information associated with the primary UE to the secondary UE in the tightly coupled mode. The secondary UE can provide MIMO physical layer information to the primary UE via a P2P link in the tightly coupled mode. Example MIMO physical layer information that the secondary UE can provide to the primary UE over a P2P link includes one or more of rank, preferred precoding information, or a channel estimate.
For a tightly coupled mode, a clone pair can be initiated while the primary UE is in a traffic state. The primary UE may determine to dissociate the P2P link with the secondary UE in response to detecting channel degradation of the secondary UE. The primary UE may determine to dissociate the P2P link with the secondary UE in response to detecting a change in state of the secondary UE (e.g., a traffic state change, low battery mode, etc.). The primary UE can return from clone mode to a single user mode prior to a clone-haul disassociation.
Clone paring candidate consideration in a tightly coupled mode can be based on a UE based discovery based on P2P beacon measurement. A clone pair candidate in an idle state can be preferred over another clone pair candidate in an active state. In some instances, a secondary UE can be in an active state and be part of a clone pair. Network assisted discovery with a list of available idle secondary UEs can be implemented. A clone pair association only to UEs in communication with the same BBU and/or cell, but that can be in communication with different TRPs within the same BBU and/or cell can be implemented.
In event 640, the primary UE 610 can discover the secondary UE 620. The discovery may include receiving, at the primary UE 610 a message from the secondary UE 620. In some implementations, the discovery may be a broadcast discovery whereby a message is generally transmitted to devices within a range of the primary UE 610. The discovery may include peer-to-peer beacons and/or signals. The message may include information indicating clone pairing capabilities. In such instances, devices that can perform clone pairing may respond. Although shown as discovering a single secondary UE in
The primary UE 610 can collect information associated with the secondary UE 620. For example, the primary UE 610 can collect one or more of availability of the secondary UE 620 to serve as a secondary UE for the primary UE 610, recent channel quality indicator (CQI) information, precoding selection, or the like. The primary UE 610 can store the collected information associated with the secondary UE 620. The primary UE 610 can collect and store information associated with a plurality of secondary UEs 620.
After discovering the secondary UE 620, the primary UE 610 may generate pairing information at event 642. The primary UE 610 can compute a joint spectral efficiency of the primary UE 610 and the secondary UE 620 operating as a clone pair. The computation of spectral efficiency can be based on information collected associated with discovering the secondary UE in event 640. For example, the joint spectral efficiency can be based on cellular channel information for the secondary UE 620, information about the P2P link, and cellular channel information for the primary UE 610. The UE pairing information can include the joint spectral efficiency. The joint spectral efficiency and/or other pairing information can be computed for one or more additional secondary UEs. The primary UE 610 can generate a priority secondary UE list indicating an order of preference of using secondary UEs as a clone pair in cases where more than one secondary UE is discovered.
The pairing information can include information that can be used by the secondary UE 620 to clone the primary UE 610. The pairing information may include information identifying the primary UE 610 such as precoding information, a UE subscriber identifier (ID), or an assigned Internet Protocol (IP) address. The pairing information may include an identification of a type and/or an amount of data expected to be transmitted and/or received via the clone pairing. In some implementations, the pairing information may identify a desired active set of one or more serving nodes.
The primary UE 610 can initiate a pair request. In event 644, the primary UE 610 can transmit a pairing request to the secondary UE 620. The pairing request can include pairing information generated at event 642. In cases where multiple secondary UEs are discovered, the primary UE 610 may transmit a message to the top candidate secondary UE and wait a pre-determined period of time for an acknowledgement. The top candidate secondary UE can have the highest joint spectral efficiency with the primary UE 610 of the possible clone pairs. The primary UE 610 can prioritize candidate secondary UEs based on one or more operational characteristics of a secondary UE and/or based on one or more pairing metrics associated with the secondary UE. One or more of operational characteristics and/or one or more of the pairing metrics described in association with the secondary UE 620 determining whether to accept the request can be used by the primary UE 610 in prioritizing candidate secondary UEs. If an acknowledgement is not received from the top candidate secondary UE, the primary UE 610 can continue to the next candidate in the priority peer list until an acknowledgement is received. If no acknowledgement is received from any candidate secondary UE, the message flow 600 can terminate and/or start over.
In event 646, the secondary UE 620 can determine whether to accept the clone pairing request. The determination may include evaluating the type and/or amount of data expected via the clone pairing. The determination may compare the expectations to the resources desired by the secondary UE 620 to support its own operations. The determination may include detecting an operational characteristic of the secondary UE 620, such as power level (e.g., battery power), processor load, memory, applications executing on the secondary UE 620, existing clone pairings with other UEs, MIMO capabilities, traffic state of the secondary UE 620 (e.g., whether the secondary UE 620 is idle or actively communicating with the network system 630), a channel condition associated with the secondary UE 620, or another detectable operational metric for the secondary UE 620. In some implementations, the operational characteristic may be compared to a threshold and if the characteristic satisfies the threshold, the determination may indicate the secondary UE 620 is able to establish clone pairing with the primary UE 610. In certain applications, a plurality of operational characteristics can each be compared to a respective threshold, and the determination of whether to accept a clone pairing request can be based on the comparisons. The determination can be made based on some or all of the operational characteristics satisfying respective thresholds.
The determination can be based on one or more of a variety of factors. For example, the determination can be based on one or more pairing metrics. Example pairing metrics include one or more lists associated with a user equipment such as a social network list, one or more a priori agreements, or incentives such as tokens provided for serving in a clone pair. Example incentives include cellular data allowance transfer from the primary UE, digital cash, or credit tokens associated with a social network service. In some instances, a pairing can be based on one or more explicit (e.g., group of users who have agreed to cooperate) or implicit a priori agreements (e.g., a friend list or list of users with common interest defined by social network service). In response to determining to establish a clone pair, the secondary UE 620 can send a confirmation to the primary UE 610 at event 648. If the pairing request is not granted by the secondary UE 620, the primary UE 610 can send a pairing request to the next highest secondary UE on the priority list.
In response to the secondary UE 620 confirming the paring request at event 648, the primary UE 610 and the secondary UE 620 can establish a clone pair. A P2P link can be established between the primary UE 610 and the secondary UE 620. The primary UE 610 can request CQI and/or precoding information from the secondary UE 620. The secondary UE 620 can estimate its own cellular channel information and provide the cellular channel information, such as channel state quality and/or channel noise estimates, to the primary UE 610 via the P2P link.
In event 650, the primary UE 610 can generate a joint channel report including cellular channel information for the primary UE 610 and the secondary UE 620. The joint channel report can include any suitable joint channel information. For example, the joint channel report can include one or more of a joint CQI, rank, or precoding selection. The joint CQI, rank, and/or precoding selection can be computed based on information associated with the primary UE 610 and information associated with the secondary UE 620.
The primary UE 610 can transmit the joint channel report to the network system 630 at event 652. Alternatively or additionally, the secondary UE 620 can transmit the joint channel report to the network system 630. The transmission of the joint channel report may occur via a cellular channel to one or more TRPs. The joint channel report can be periodically generated and transmitted to the network system 630 in certain applications.
The network system 630 can serve traffic associated with the primary UE 610 based on the joint channel report. The network system 630 can serve the primary UE 610 based on the paired CQI of the primary UE 610 and the secondary UE 620. The network system 630 can schedule and transmit cellular communications with the primary UE 610 and the secondary UE 620.
The network system 630 can send a first cellular communication to the primary UE 610 at event 654. The first cellular communication can include a first part of a MIMO transmission to the primary UE 610. The network system 630 can send a second cellular communication to the secondary UE 620 at event 658. The second cellular communication can include a second part of the MIMO transmission to the primary UE 610. The second cellular communication can be concurrent with the first cellular communication. Accordingly, the network system 630 can serve traffic to the primary UE 610 and the secondary UE 620 concurrently. The first part and the second part of the MIMO transmission can include information indicating the respective cellular communications are associated with the primary UE 610. The information can include an identifier or hash code, for example. The information may be implied by a timing slot or frequency used to transmit the cellular communications.
The secondary UE 620 can determine that the second part of the MIMO transmission includes a communication for the primary UE 610. The secondary UE 620 can provide the second part of the MIMO transmission to the primary UE 610 via the P2P link at event 660. The secondary UE 620 can pass the second part of the MIMO transmission directly over the P2P link. In certain applications, the P2P link between the primary UE 610 and the secondary UE 620 can preferably occur over an air interface with a relatively short range, such as Bluetooth, Wi-Fi, ZigBee, or other standardized or proprietary local area network protocol. The P2P link between the primary UE 610 and the secondary UE 620 can enable cellular communications, such as cellular communications at relatively high frequencies. In certain applications, the second part of the MIMO transmission can be encapsulated, modified, or otherwise reformatted into a format suitable for transmission via the peer-to-peer channel.
After event 660, the primary UE 610 can jointly process the first part of the MIMO transmission and the second part of the MIMO transmission.
The primary UE 610 and the secondary UE 620 can also jointly send uplink MIMO data from the primary UE 610 to the network 630. Similar events and communications can be implemented for uplink communications. For example, the primary UE 610 may transmit cellular communications to the network system 630 via a cellular interface and to the secondary UE 620 via the peer-to-peer link. The secondary UE 620 may, in turn, transmit the received communication to the network system 630. In some implementations, the uplink transmissions to the network system 630 from the primary UE 610 and the secondary UE 620 may be coordinated (e.g., time, frequency, and/or spatial). The coordination may be specified during the pairing process.
The pairing may be terminated based on changed network conditions. For example, the primary UE 610 may detect channel degradation for the secondary UE 620 or a change in state (e.g., traffic state change, low battery) of secondary UE 620. Control messages may be exchanged between the primary UE 610 and the secondary UE 620 to indicate one or more such changing conditions. It may be desirable for the primary UE 610 to transmit a channel report identifying a single-user mode before disassociating with the secondary UE 620. In some implementations, the primary UE 610 may be limited to one active clone pairing. Accordingly, if a better secondary UE is detected (e.g., stronger signal strength, power level, etc.), the primary UE 610 may first disassociate from the secondary UE 620 before initiating a clone pairing with the better secondary UE.
In the message flow 600 shown in
In event 740, the primary UE 710 can discover the secondary UE 720. The discovery may include receiving, at the primary UE 710 a message from the secondary UE 720. In some implementations, the discovery may be a broadcast discovery whereby the message is generally transmitted to devices within a range of the primary UE 710. The discovery may include peer-to-peer beacons and/or signals. The message may include information indicating clone pairing capabilities. In such instances, devices that can perform clone pairing may respond. Although shown as discovering a single secondary UE in
The primary UE 710 can collect information associated with the secondary UE 720. For example, the primary UE 710 can collect one or more of availability of the secondary UE 720 to serve as a secondary UE for the primary UE 710, recent CQI information, precoding selection, or the like. The primary UE 710 can store the collected information associated with the secondary UE 720. The primary UE 710 can collect and store information associated with a plurality of secondary UEs 720.
After discovering the secondary UE 720, the primary UE 710 may generate pairing information at block 742. The primary UE 710 can compute a joint spectral efficiency of the primary UE 710 and the secondary UE 720 operating as a clone pair. The computation of spectral efficiency can be based on information collected associated with discovering the secondary UE in event 740. The UE pairing information can include the joint spectral efficiency. The joint spectral efficiency and/or other pairing information can be computed for one or more additional secondary UEs. The primary UE 710 can generate a priority secondary UE list indicating an order of preference of using secondary UEs in a clone pair in cases where more than one secondary UE is available.
The pairing information can include information that can be used by the secondary UE 720 to clone the primary UE 710. The pairing information may include information identifying the primary UE 710 such as precoding information, a UE subscriber ID, or an assigned Internet Protocol (IP) address. The pairing information may include an identification of a type or amount of data expected to be transmitted or received via the clone pairing. In some implementations, the pairing information may identify a desired active set of one or more serving nodes.
The primary UE 710 can transmit UE pairing information to the network system 730 at event 744. Because the network system 730 can detect conditions of the network which may not be accessible to the primary UE 710, the network system 730 may use the increased information to determine the clone pairing for the primary UE 710. In event 746, the network system 710 can determine a clone pair. The network system 730 can update the priority secondary UE list. In the example of
The network system 730 can also take into account other network information in determining the clone pair at event 746. The other network information can include information identifying the mobility of secondary UEs. For example, the primary UE 710 may determine that a specific secondary UE has a particularly strong signal strength but, unbeknownst to the primary UE 710, is that the specific secondary UE is located on a moving vehicle that is likely to soon exceed a desired distance range for clone pairing. The network system 730 can use a criterion based on a set of metrics of the primary UE 710, the secondary UE 710, or/or other UEs served by the network system to determine the best operating regime to serve the primary UE 710. The metrics can include a device mobility state, a Doppler estimate, a measure of the network-to-UE channel matrix condition such as Eigen-value spread, a network congestion measure (e.g., network load), the like, or any suitable combination thereof. The metrics can include one or more operational characteristics of the secondary UE 720 and/or one or more pairing metrics. In a tightly coupled mode, the uplink transmissions from both the primary UE 710 and the secondary UE 720 can appear as one transmission from the primary UE 710. This can be indicated by channel assignment and/or signaling overhead.
If the clone pairing result from event 746 is not to establish a clone pair (e.g., no secondary UEs were available for pairing), the message flow 700 can terminate and/or start over. In such instances, the network system 730 may transmit a message to the primary UE 710 that a clone pair is not being established.
In the message flow 700 shown in
The primary UE 710 can transmit a clone pairing request to the secondary UE 720 at event 750. Then the secondary UE 720 can enter a clone mode. The secondary UE 720 can send a confirmation to the primary UE 710 that the secondary UE 720 accepts the request to enter the clone mode at event 752. In some instances, the secondary UE 720 can also send a confirmation to the network system 730. Unlike in
A P2P communication channel can be established between the primary UE 710 and the secondary UE 720 for clone traffic to and/or from the primary UE 710. In the clone mode, the secondary UE 720 can estimate its own channel information and provide the channel information estimate to the primary UE 710 via the P2P link. The channel information can include cellular channel information for the secondary UE 720, such as channel state quality and/or channel noise estimates.
In event 754, the primary UE 710 can generate a joint channel report for the primary UE 710 and the secondary UE 720. The joint channel report can include any suitable joint channel information. For example, the joint channel report can include one or more of a joint CQI, rank, or precoding selection. The joint QCI, rank, and/or precoding selection can be computed based on information associated with the primary UE 710 and information associated with the secondary UE 720. The joint channel report can appear to the network system 730 as if were associated with a single UE when in fact the primary UE 710 and secondary UE 720 are operating as a clone pair.
The primary UE 710 can transmit the joint channel report to the network system 730 at event 756. Alternatively or additionally, the secondary UE 720 can transmit the joint channel report to the network system 730. The transmission of the joint channel report may occur via a cellular channel to one or more TRPs. The joint channel report can be periodically generated and transmitted to the network system 730 in certain applications.
The network system 730 can serve traffic associated with the primary UE 710 based on the joint channel report. The network system 730 can serve the primary UE 710 based on the paired CQI of the primary UE 710 and the secondary UE 720.
The network system 730 can send a first cellular communication to the primary UE 710 at event 756. The first cellular communication can include a first part of a MIMO transmission to the primary UE 710. The network system 730 can send a second cellular communication to the secondary UE 720 at event 760. The second cellular communication can include a second part of the MIMO transmission to the primary UE 710. The second cellular communication can be concurrent with the first cellular communication. Accordingly, the network system 730 can serve traffic to the primary UE 710 and the secondary UE 720 concurrently. The first part and the second part of the MIMO transmission can include information indicating the respective cellular communications are associated with the primary UE 710. The information can include an identifier or hash code, for example. The information may be implied by a timing slot or frequency used to transmit the cellular communications.
The secondary UE 720 can determine that the second part of the MIMO transmission includes a communication for the primary UE 710. The secondary UE 720 can provide the second part of the MIMO transmission to the primary UE 710 via the P2P link at event 762. The secondary UE 720 can pass the second part of the MIMO transmission directly over the P2P link. The P2P link between the primary UE 710 and the secondary UE 720 can preferably occur over an air interface with a relatively short range, such as Bluetooth, Wi-Fi, ZigBee, or other standardized or proprietary local area network protocol. In certain applications, the second part of the MIMO transmission can be encapsulated, modified, or otherwise reformatted into a format suitable for transmission via the peer-to-peer channel.
After event 762, the primary UE 710 can jointly process the first part of the MIMO transmission and the second part of the MIMO transmission.
The primary UE 710 and the secondary UE 720 can also jointly send uplink MIMO data from the primary UE 710 to the network 730. Similar events and communications can be implemented for uplink communications. For example, the primary UE 710 may transmit cellular communications to the network system 730 via a cellular interface and to the secondary UE 720 via the peer-to-peer link. The secondary UE 720 may, in turn, transmit the received communication to the network system 730. In some implementations, the uplink transmissions to the network system 730 from the primary UE 710 and the secondary UE 720 may be coordinated (e.g., time, frequency, and/or spatial). The coordination may be specified during the pairing process. In a tightly coupled mode, the uplink transmissions from both the primary UE 710 and the secondary UE 720 can appear as one transmission from the primary UE 710. This can be indicated by channel assignment and/or signaling overhead.
The pairing may be terminated based on changed network conditions and/or a change in a UE condition, such as mobility or available battery. For example, the primary UE 710 may detect channel degradation for the secondary UE 720 or a change in state (e.g., traffic state change, low battery) of secondary UE 720. Control messages may be exchanged between the primary UE 710 and the secondary UE 720 to indicate one or more such changing conditions. It may be desirable for the primary UE 710 to transmit a channel report identifying a single-user mode before disassociating with the secondary UE 720. In some implementations, the primary UE 710 may be limited to one active clone pairing. Accordingly, if a better secondary UE is detected (e.g., stronger signal strength, power level, etc.), the primary UE 710 may first disassociate from the secondary UE 720 before initiating a clone pairing with the better secondary UE.
Loosely Coupled Mode
In some implementations, it may be desirable to allow each UE of a clone pair to maintain its own identity, but increase the rate by tunneling. In such instances, first data may be transmitted to the primary UE along a first beam and second data may be transmitted to the secondary UE along a second beam. The secondary UE may then transfer the second data to the primary UE through a cloned peer connection. This tunneling arrangement may be referred to a loose coupling.
In a loosely coupled pair of UEs, the primary UE and the secondary UE can have different identities from a network perspective. The primary UE can establish a dual connectivity (DC) tunnel through the secondary UE. TRPs of a network system can serve both the primary UE and the secondary UE in MU-MIMO operation. A long term evolution-new radio (LTE-NR) DC protocol, for example, can be leveraged by the primary UE to aggregate MIMO data. Aggregation can be performed at a higher layer. For example, a Packet Data Convergence Protocol (PDCP), an application layer (reuse DC protocol), or a radio link control (RLC) protocol can be used in aggregating data by the primary UE. Example operations for tightly coupled UE pairs are discussed with reference to
For a loosely coupled mode, the clone process can be initiated while the primary UE is in a traffic state. The primary UE may determine to dissociate the P2P link with the secondary UE in response to detecting channel degradation of the secondary UE. The primary UE may determine to dissociate the P2P link with the secondary UE in response to detecting a change in state of the secondary UE (e.g., a traffic state change, low battery mode, etc.). Tunnel set up and tear down protocol can leverage an LTE DC protocol. The primary UE can tear down a tunnel before setting up a new tunnel.
Clone paring candidate consideration in a loosely coupled mode can be based on a UE centric discovery based on P2P beacon measurement. A clone pair candidate can be in an idle state or in an active state. Network assisted discovery with a list of available idle secondary UEs can be implemented. Tunnel association can be implemented between UEs connection to the same cell or two or more different cells.
In event 840, the primary UE 810 can discover the secondary UE 820. The discovery may include receiving, at the primary UE 810 a message from the secondary UE 820. In some implementations, the discovery may be a broadcast discovery whereby a message is generally transmitted to devices within a range of the primary UE 810. The discovery may include peer-to-peer beacons and/or signals. The message may include information indicating clone pairing capabilities. In such instances, devices that can perform clone pairing may respond. Although shown as discovering a single secondary UE in
The primary UE 810 can collect information associated with the secondary UE 820. For example, the primary UE 810 can collect one or more of availability of the secondary UE 820 to serve as a secondary UE for the primary UE 810, recent channel quality indicator (CQI) information, precoding selection, or the like. The primary UE 810 can store the collected information associated with the secondary UE 820. The primary UE 810 can collect and store information associated with a plurality of secondary UEs 820.
After discovering the secondary UE 820, the primary UE 810 may generate pairing information at event 842. The primary UE 810 can compute a joint spectral efficiency of the primary UE 810 and the secondary UE 820 operating as a clone pair. The computation of spectral efficiency can be based on information collected associated with discovering the secondary UE in event 840. The primary UE 810 can compute an incremental spectral efficiency that can be gained due to communicating with a network system via the P2P link with the secondary UE. The incremental spectral efficiency can be computed based on a P2P link condition and one or more channel conditions of the secondary UE. The UE pairing information can include the joint spectral efficiency and/or the incremental spectral efficiency. UE pairing information can be computed for one or more additional secondary UEs. The primary UE 810 can generate a priority secondary UE list indicating an order of preference of using secondary UEs as a clone pair in cases where more than one secondary UE is available.
The pairing information can include information that can be used by the secondary UE 820 to clone the primary UE 810. The pairing information may include information identifying the primary UE 810 such as precoding information, a UE subscriber ID, or an assigned Internet Protocol (IP) address. The pairing information may include an identification of a type and/or an amount of data expected to be transmitted and/or received via the clone pairing. In some implementations, the pairing information may identify a desired active set of one or more serving nodes.
The primary UE 810 can initiate a pair request. In event 844, the primary UE 810 can transmit a pairing request to the secondary UE 820. The pairing request can include pairing information generated at event 842. In cases where multiple secondary UEs are discovered, the primary UE 810 may transmit a message to the top candidate secondary UE and wait a pre-determined period of time for an acknowledgement. The top candidate secondary UE can have the highest joint spectral efficiency with the primary UE 810 of the possible clone pairs. The primary UE 810 can prioritize candidate secondary UEs based on one or more operational characteristics of a secondary UE and/or based on one or more pairing metrics associated with the secondary UE. One or more of operational characteristics and/or one or more of the pairing metrics described in association with the secondary UE 820 determining whether to accept the request can be used by the primary UE 810 in prioritizing candidate secondary UEs. If an acknowledgement is not received from the top candidate secondary UE, the primary UE 810 can continue to the next candidate in the priority peer list until an acknowledgement is received. If no acknowledgement is received from any candidate secondary UE, the message flow 800 can terminate and/or start over.
In event 846, the secondary UE 820 can determine whether to accept the clone pairing request. The determination may include evaluating the type and/or amount of data expected via the clone pairing. The determination may compare the expectations to the resources needed by secondary UE 820 to support its own operations. The determination may include detecting an operational characteristic of the secondary UE 820 such as power level (e.g., battery power), processor load, memory, applications executing on the secondary UE 820, existing clone pairings with other UEs, MIMO capabilities, traffic state of the secondary UE 820 (e.g., whether the secondary UE 820 is idle or actively communicating with the network system 830), a channel condition associated with the secondary UE 820, or another detectable operational metric for the secondary UE 820. In some implementations, the operational characteristic may be compared to a threshold and if the characteristic satisfies the threshold, the determination may indicate the secondary UE 820 is able to establish clone pairing with the primary UE 810. In certain applications, a plurality of operational characteristics can each be compared to a respective threshold, and the determination of whether to accept a clone pairing request can be based on the comparisons. The determination can be made based on some or all of the operational characteristics satisfying respective thresholds.
The determination can be based on one or more of a variety of factors. For example, the determination can be based on one or more pairing metrics. Example pairing metrics include one or more lists associated with a user equipment such as a social network list, one or more a priori agreements, or incentives such as tokens provided for serving in a clone pair. Example incentives include cellular data allowance transfer from the primary UE, digital cash, or credit tokens associated with a social network service. In response to determining to establish a clone pair, the secondary UE 820 can send a confirmation to the primary UE 810 at event 848. If the pairing request is not granted by the secondary UE 820, the primary UE 810 can send a pairing request to the next highest secondary UE on the priority list.
In response to the secondary UE 820 confirming the paring request at event 848, the primary UE 810 and the secondary UE 820 can establish a clone pair. A P2P link can be established between the primary UE 810 and the secondary UE 820. The primary UE 810 can request CQI and/or precoding information from the secondary UE 820. The secondary UE 820 can estimate its own cellular channel information and provide the cellular channel information, such as channel state quality and/or channel noise estimates, to the primary UE 810 via the P2P link.
Unlike message flows in the examples of
In event 852, the network system 830 can determine whether to establish the tunnel. If the network system 830 determines to establish the tunnel, the network system 830 can set up the tunnel. Because the network system 830 can detect conditions of the network which are not accessible to the primary UE 810, the network system 830 can use the additional information to determine whether and/or how to tunnel with the primary UE 810. The determination may include identifying the mobility of secondary UE 820. The network system 830 can use a criterion based on a set of metrics of the primary UE 810, the secondary UE 820, or/or other UEs served by the network system 830. The metrics can include a device mobility state, a Doppler estimate, a measure of the network-to-UE channel matrix condition such as Eigen-value spread, a network congestion measure (e.g., network load), the like, or any suitable combination thereof. One or more metrics can be modified to be consistent with the available P2P information exchange bandwidth.
If the network system 830 determines not to establish the tunnel, the message flow 800 can terminate and/or start over. In such instances, the network system 830 may transmit a message to the primary UE 810 declining the tunneling request.
In the message flow 800 shown in
A second part of the tunnel can be established between the primary UE 810 and the secondary UE 820 in event 856. The second part of the tunnel may be established over a peer-to-peer air interface for relatively short distance communications such as Bluetooth or another standardized or proprietary local area network protocol. In some implementations, establishing of the tunnel may be achieved according to an LTE dual-connectivity protocol, an LTE-Wi-Fi offload protocol, a LTE direct protocol, or another suitable standardized or proprietary network tunneling protocol.
Once the tunnel is established from the network system 830 to the primary UE 810, the secondary UE 820 can pass along downlink communications received via the tunnel to the primary UE 810 and uplink communications received via the tunnel to the network system 830. Communications between the secondary UE 820 and the network system 830 can be over a cellular link while the communications between the secondary UE 820 and the primary UE 810 can be via the peer-to-peer air interface. Accordingly, the secondary UE 820 can use different communication technologies for communicating with the primary UE 810 and the network system 830. Alternatively or additionally, the secondary UE 820 can use different communication frequencies for communicating with the primary UE 810 and the network system 830.
The primary UE 810 may aggregate first cellular data received directly from the network system 830 with second data received from the secondary UE 820 via the tunnel.
The primary UE 810 may determine to tear down the tunnel in response to detecting changed conditions. For example, the primary UE 810 may detect channel degradation of secondary UE 820 and/or a change of state (e.g., traffic state change, low battery) for the secondary UE 820. In some implementations, the primary UE 810 may tear down an established tunnel when a more efficient secondary UE is detected. In such instances, the primary UE 810 may tear down the established tunnel before setting up a new tunnel, such as via one or more of the messages shown in the message flow 800.
Providing Different Spatial Beams to UEs of a Clone Pair
In certain embodiments, a secondary UE of a clone pair can wirelessly communicate with different beams and/or TRPs of a network system than a primary UE of the clone pair. This can enable the clone pair to communicate with the network system at a higher data rate and/or with higher MIMO rank than the primary UE is able to communicate with the network system operating alone. Any suitable principles and advantages disclosed herein can be applied to using different spatial beams from a network system to communicate with a clone pair. The primary UE and the secondary UE can communicate with the same serving node via respective different beams to thereby increase a data rate and/or MIMO rank.
The first RRU 902 can transmit a plurality of spatial beams, such as the illustrated beams A1, A2, A3, and A4. Similarly, the second RRU 904 can transmit a plurality of spatial beams, such as the illustrated beams B1, B2, B3, B4, and B5. The primary UE 920 and the secondary UE 930 can each receive different beams from the first RRU 902 and the second RRU 904. For example, the primary UE 920 can receive beams A1 and B2 and the secondary UE 930 can receive beams A4 and B1. Accordingly, beams can be spatially multiplexed to communicate with the primary UE 920 and the secondary UE 930. This can enable the primary UE 920 and the secondary UE 930 to receive data associated with the primary UE 920 over different spatial beams. The secondary UE 930 can provide data received for the primary UE 920 to the primary UE 920 over a P2P link. Cellular communications with the primary UE 920 and the secondary UE 930 using different spatial beams can increase the data rate and/or rank of data associated with the primary UE 920 being transmitted by the network system.
Similar principles and advantages can be applied to using different spatial beams for transmitting uplink data associated with the primary UE 920 using the primary UE 920 and the secondary UE 930.
Methods of Wireless Communication with Clone Pair
At block 1004, a first part of the MIMO downlink data transmission from one or more serving nodes is received by the primary UE. The first part of the MIMO downlink data transmission can be received by one or more antennas of the primary UE. The first part of the MIMO downlink transmission can be received via a cellular link. A second part of the MIMO downlink data transmission can be received from a secondary UE using a peer-to-peer wireless interface at block 1006. The part of the MIMO downlink data transmission can be received by a non-cellular communication over a P2P communication channel between the primary UE and the secondary UE.
The primary UE can process the first part of the MIMO communication together with the second part of the MIMO communication at block 1008. The primary UE can include one or more antennas configured to receive MIMO downlink data at up to a downlink peak data rate. The processing at block 1008 can be performed such that the MIMO downlink data transmission is processed at a higher data rate than the downlink peak data rate. The primary UE can include antennas configured to receive MIMO downlink data at up to a rank of N, wherein N is a positive integer 2 or greater. The first and second parts of downlink MIMO data transmission can together have a rank of greater than N. Accordingly, the processing at block 1008 can involve processing a downlink MIMO data transmission having a rank of greater than N.
At block 1014, a communication channel is established between a primary UE and the secondary UE. The communication channel can be established via a peer-to-peer wireless interface of the primary UE. Non-cellular communications can be transmitted and received over the communication channel. The primary UE can transmit a first part of MIMO uplink data to one or more serving nodes at block 1016. The transmission to the one or more serving nodes can be a cellular communication. The first part of the MIMO uplink data can be transmitted while the primary UE is in communication with the secondary UE via the communication channel established at block 1014. The primary UE can also transmit a second part of the MIMO uplink data to a secondary UE over the communication channel with the secondary UE at block 1018. The transmission to the secondary UE can be a non-cellular communication. The secondary UE can then transmit the second part to the MIMO uplink data to one or more serving nodes.
The method 1010 can enable the primary UE to transmit uplink data to a network system at a higher data rate and/or higher MIMO rank. The primary UE can include one or more antennas configured to transmit MIMO downlink data at up to an uplink peak data rate. The transmissions at blocks 1016 and 1018 can be performed such that the primary UE effectively transmits MIMO uplink data transmission to a network system at a higher data rate than the uplink peak data rate. The primary UE can include antennas configured to transmit MIMO downlink data at up to a rank of N, wherein N is a positive integer 1 or greater. The transmissions at blocks 1016 and 1018 can be performed such that the primary UE effectively transmits uplink MIMO data a rank of greater than N.
At block 1104, a communication channel is established between a primary UE and the secondary UE. The communication channel can be established via a peer-to-peer wireless interface of the secondary UE. Non-cellular communications can be transmitted and received over the communication channel. While the primary UE is receiving first MIMO downlink data for the primary UE via a cellular communication, the secondary UE can receive second MIMO downlink data for the primary UE at block 1106. The secondary UE can receive the second MIMO downlink data via a cellular communication. At block 1108, the secondary UE can transmit the second MIMO downlink data to the primary UE via the communication channel.
The primary user equipment can receive downlink MIMO data at up to a maximum first UE rank via cellular communications, and the first MIMO downlink data and the second MIMO downlink data can are together be included in a MIMO downlink data transmission having a rank that is higher than the maximum first UE rank. The secondary user equipment can receive downlink MIMO data at up to a maximum second UE rank via cellular communications, and the first MIMO downlink data and the second MIMO downlink data can together be included in a MIMO downlink data transmission having a rank that is higher than the maximum second UE rank.
In certain instances, the method 1100 can include generating symbol level data from the second MIMO downlink data received at block 1106. In such instances, the second MIMO downlink data transmitted at block 1108 can include the symbol level data.
In some instances, the method 1100 can include sending MIMO physical layer information to the primary user equipment over the communication channel. The method 1100 can alternatively or additionally include determining to accept a pairing request from the primary user equipment based on an operational characteristic of the secondary user equipment, and wherein the establishing is in response to the determining.
At block 1114, a communication channel is established between a primary UE and the secondary UE. The communication channel can be established via a peer-to-peer wireless interface of the secondary UE. In certain applications, non-cellular communications can be transmitted and received over the communication channel. Cellular communications can be transmitted and received over the communication channel in some applications. While the primary UE is transmitting first MIMO uplink data for the primary UE to a network system via a cellular communication, the secondary UE can receive second MIMO uplink data from the primary UE via the communication channel at block 1116. At block 1118, the secondary UE can transmit the second MIMO uplink data to the network system.
The primary user equipment can transmit uplink MIMO data at up to a maximum first UE rank via cellular communications, and the first MIMO uplink data and the second MIMO uplink data can are together be included in a MIMO uplink data transmission having a rank that is higher than the maximum first UE rank. The secondary user equipment can transmit uplink MIMO data at up to a maximum second UE rank via cellular communications, and the first MIMO uplink data and the second MIMO uplink data can together be included in a MIMO downlink data transmission having a rank that is higher than the maximum second UE rank.
In certain instances, the method 1110 can include generating higher level data from symbol level data received at block 1116. In such instances, the second MIMO uplink data receive and transmitted at blocks 1116 and 1118, respectively, can include the different level data.
In some instances, the method 1110 can include sending MIMO physical layer information to the primary user equipment over the communication channel. The method 1110 can alternatively or additionally include determining to accept a pairing request from the primary user equipment based on an operational characteristic of the secondary user equipment, and wherein the establishing is in response to the determining.
At block 1204, a first uplink data transmission associated with a primary user equipment from the primary user equipment can be received by a network system. The primary user equipment is configured to transmit uplink data at a rate of up to a peak uplink data rate. The network system can receive a second uplink data transmission associated with the primary user equipment from a secondary user equipment at block 1206. The network system can process data associated with the first and second uplink data transmissions at block 1208. The processing at block 1208 can be performed so as to process uplink data associated with the primary UE at a rate of greater than the peak uplink data rate of the primary UE.
At block 1214, the network system can generate downlink transmission data for a primary UE. The network system can transmit parts of the downlink data transmission for the primary UE to the primary UE and the secondary UE while the primary UE and the secondary UE are in communication with each other via a P2P link. The network system can transmit a first part of the downlink transmission data for the primary user equipment to the primary user equipment at block 1216. This can occur while the primary user equipment is in communication with a secondary user equipment via the P2P link. The network system can transmit a second part of the downlink transmission data for the primary user equipment to the secondary user equipment at block 1218. This can occur while the primary user equipment is in communication with a secondary user equipment via the P2P link.
Depending on the embodiment, certain acts, events, or functions of any of the processes or algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described operations or events are necessary for the practice of the algorithm). Moreover, in certain embodiments, operations, or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
Conditional language used herein, such as “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or steps. Thus, such conditional language is not generally intended to imply that features, elements, and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without other input or prompting, whether these features, elements, and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description of Certain Embodiments using the singular or plural may also include the plural or singular, respectively. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.
Disjunctive language such as the phrase “at least one of X, Y, Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.
Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.
The word “coupled,” as generally used herein, refers to two or more elements that may be either directly coupled to each other, or coupled by way of one or more intermediate elements. Likewise, the word “connected,” as generally used herein, refers to two or more elements that may be either directly connected, or connected by way of one or more intermediate elements.
As used herein, the terms “determine” or “determining” encompass a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, generating, obtaining, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like via a hardware element without user intervention. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like via a hardware element without user intervention. Also, “determining” may include resolving, selecting, choosing, establishing, and the like via a hardware element without user intervention.
As used herein, the terms “provide” or “providing” encompass a wide variety of actions. For example, “providing” may include storing a value in a location of a storage device for subsequent retrieval, transmitting a value directly to the recipient via at least one wired or wireless communication medium, transmitting or storing a reference to a value, and the like. “Providing” may also include encoding, decoding, encrypting, decrypting, validating, verifying, and the like via a hardware element.
As used herein a “transmit-receive point” (TRP) (which can alternatively be referred to as a transmission reception point) may refer to a transceiver device or one transceiver element included in a device. When included as a transceiver element, the device may include multiple TRPs. The TRP may include one or more antennas which are coupled to signal processing circuitry. The signal processing circuitry may be included in the device. The TRP may include additional elements to facilitate transmission or receipt of wireless signals for one or more UEs. Example of such elements may include a power source, amplifier, digital-to-analog converter, analog-to-digital converter, or the like. When a TRP is allocated, such as by a BBU, to provide service to a UE, the TRP may be said to be a “serving node” for the UE.
As used herein a “remote radio unit” (RRU) may refer to a device for controlling and coordinating transmission and receipt of wireless signals for one or more UEs. An RRU may include or be coupled with one or more TRPs. The RRU may receive signals from the TRP and include the signal processing circuitry. The signal processing circuitry may be selectively operated to facilitate processing of signals associated with different TRPs.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. For example, circuit blocks and/or method blocks described herein may be deleted, moved, added, subdivided, combined, arranged in a different order, and/or modified. Each of these blocks may be implemented in a variety of different ways. Any portion of any of the methods disclosed herein can be performed in association with specific instructions stored on a non-transitory computer readable storage medium being executed by one or more processors. As can be recognized, certain embodiments described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain embodiments disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5414796 | Jacobs et al. | May 1995 | A |
| 5469115 | Peterzell | Nov 1995 | A |
| 5479475 | Grob | Dec 1995 | A |
| 5487175 | Bayley | Jan 1996 | A |
| 5515177 | Propach | May 1996 | A |
| 5517323 | Propach | May 1996 | A |
| 5539531 | Propach | Jul 1996 | A |
| 5566000 | Propach | Oct 1996 | A |
| D375740 | Mergenthaler et al. | Nov 1996 | S |
| D375937 | Mergenthaler et al. | Nov 1996 | S |
| 5574773 | Grob | Nov 1996 | A |
| D376804 | Mergenthaler et al. | Dec 1996 | S |
| 5590406 | Bayley | Dec 1996 | A |
| 5600754 | Gardner et al. | Feb 1997 | A |
| 5617060 | Wilson | Apr 1997 | A |
| 5657420 | Jacobs et al. | Aug 1997 | A |
| 5663807 | Propach | Sep 1997 | A |
| D386186 | Schnetzer et al. | Nov 1997 | S |
| 5737708 | Grob | Apr 1998 | A |
| 5748104 | Argyroudis | May 1998 | A |
| 5757858 | Black | May 1998 | A |
| 5761204 | Grob | Jun 1998 | A |
| 5778338 | Jacobs et al. | Jul 1998 | A |
| 5781856 | Jacobs et al. | Jul 1998 | A |
| 5784406 | DeJaco et al. | Jul 1998 | A |
| 5844885 | Grob | Dec 1998 | A |
| 5857147 | Gardner et al. | Jan 1999 | A |
| 5864763 | Leung | Jan 1999 | A |
| 5870431 | Easton | Feb 1999 | A |
| 5881368 | Grob | Mar 1999 | A |
| 5884196 | Lekven | Mar 1999 | A |
| D407701 | Chintala et al. | Apr 1999 | S |
| 5898920 | Jacobs | Apr 1999 | A |
| D409561 | Chintala et al. | May 1999 | S |
| 5903862 | Weaver et al. | May 1999 | A |
| D410893 | Chintala et al. | Jun 1999 | S |
| 5912882 | Yafuso | Jun 1999 | A |
| D411823 | Jacobs et al. | Jul 1999 | S |
| D412483 | Chintala et al. | Aug 1999 | S |
| D413117 | Chintala et al. | Aug 1999 | S |
| 5956673 | Weaver et al. | Sep 1999 | A |
| 5956683 | Jacobs et al. | Sep 1999 | A |
| 5960362 | Grob | Sep 1999 | A |
| 5983099 | Yao | Nov 1999 | A |
| 5983114 | Yao | Nov 1999 | A |
| 6006108 | Black | Dec 1999 | A |
| D424573 | Maloney et al. | May 2000 | S |
| 6101397 | Grob | Aug 2000 | A |
| 6107878 | Black | Aug 2000 | A |
| 6134440 | Black | Oct 2000 | A |
| 6147964 | Black | Nov 2000 | A |
| 6181201 | Black | Jan 2001 | B1 |
| 6205129 | Esteves | Mar 2001 | B1 |
| 6205130 | Dejaco | Mar 2001 | B1 |
| 6208858 | Antonio | Mar 2001 | B1 |
| 6208873 | Black | Mar 2001 | B1 |
| 6215779 | Bender | Apr 2001 | B1 |
| 6246885 | Black | Jun 2001 | B1 |
| 6285861 | Bonaccorso | Sep 2001 | B1 |
| 6360093 | Ross et al. | Mar 2002 | B1 |
| 6360100 | Grob | Mar 2002 | B1 |
| 6363102 | Ling | Mar 2002 | B1 |
| 6366779 | Bender | Apr 2002 | B1 |
| 6397070 | Black | May 2002 | B1 |
| 6426971 | Wu | Jul 2002 | B1 |
| 6434376 | Black | Aug 2002 | B1 |
| 6449490 | Chaponniere | Sep 2002 | B1 |
| D468685 | Jacobs et al. | Jan 2003 | S |
| 6535523 | Karmi | Mar 2003 | B1 |
| 6535918 | Bender | Mar 2003 | B1 |
| 6556549 | Bender | Apr 2003 | B1 |
| 6560211 | Esteves | May 2003 | B2 |
| 6574211 | Padovani | Jun 2003 | B2 |
| 6594501 | Black | Jul 2003 | B2 |
| 6594628 | Jacobs et al. | Jul 2003 | B1 |
| 6633552 | Ling | Oct 2003 | B1 |
| 6636568 | Kadous | Oct 2003 | B2 |
| 6661833 | Black | Dec 2003 | B1 |
| 6665272 | Pankaj | Dec 2003 | B1 |
| 6678257 | Vijayan | Jan 2004 | B1 |
| 6680925 | Wu | Jan 2004 | B2 |
| 6680926 | Bender | Jan 2004 | B2 |
| 6680968 | Black | Jan 2004 | B2 |
| 6687510 | Esteves | Feb 2004 | B2 |
| 6693920 | Montojo | Feb 2004 | B2 |
| 6694469 | Jalali | Feb 2004 | B1 |
| 6714526 | Wei | Mar 2004 | B2 |
| 6714780 | Antonio | Mar 2004 | B1 |
| 6725028 | Bonaccorso | Apr 2004 | B2 |
| 6738608 | Black | May 2004 | B2 |
| 6741861 | Bender | May 2004 | B2 |
| 6748201 | Black | Jun 2004 | B2 |
| 6757520 | Attar | Jun 2004 | B2 |
| 6798736 | Black | Sep 2004 | B1 |
| 6801580 | Kadous | Oct 2004 | B2 |
| 6804210 | Bender | Oct 2004 | B2 |
| 6807161 | Bender | Oct 2004 | B2 |
| 6813478 | Glazko | Nov 2004 | B2 |
| 6850769 | Grob | Feb 2005 | B2 |
| 6873606 | Agrawal | Mar 2005 | B2 |
| 6894994 | Grob | May 2005 | B1 |
| 6914965 | Grob | Jul 2005 | B1 |
| 6917799 | Ross et al. | Jul 2005 | B2 |
| 6917821 | Kadous | Jul 2005 | B2 |
| 6920504 | Bender | Jul 2005 | B2 |
| 6928062 | Krishnan | Aug 2005 | B2 |
| 6941133 | Jacobs et al. | Sep 2005 | B2 |
| 6965613 | Karmi | Nov 2005 | B2 |
| 6980514 | Grob | Dec 2005 | B2 |
| 6985516 | Easton | Jan 2006 | B1 |
| 6987778 | Sindhushayana | Jan 2006 | B2 |
| 7010073 | Black | Mar 2006 | B2 |
| 7020073 | Kadous | Mar 2006 | B2 |
| 7020225 | Sindhushayana | Mar 2006 | B2 |
| 7039001 | Krishnan | May 2006 | B2 |
| 7042857 | Krishnan | May 2006 | B2 |
| 7051268 | Sindhushayana | May 2006 | B1 |
| 7068707 | Bender | Jun 2006 | B2 |
| 7069037 | Lott | Jun 2006 | B2 |
| 7072628 | Agashe | Jul 2006 | B2 |
| 7079550 | Padovani | Jul 2006 | B2 |
| 7088701 | Attar | Aug 2006 | B1 |
| 7088957 | Ling | Aug 2006 | B2 |
| 7095790 | Krishnan | Aug 2006 | B2 |
| 7103643 | Jacobs et al. | Sep 2006 | B1 |
| 7106782 | Howard | Sep 2006 | B2 |
| 7113792 | Glazko et al. | Sep 2006 | B2 |
| 7123922 | Chaponniere | Oct 2006 | B2 |
| 7127654 | Jalali | Oct 2006 | B2 |
| 7127655 | Chandhok et al. | Oct 2006 | B2 |
| 7130282 | Black | Oct 2006 | B2 |
| 7133437 | Black | Nov 2006 | B2 |
| 7145940 | Gore | Dec 2006 | B2 |
| 7146174 | Gardner et al. | Dec 2006 | B2 |
| 7149264 | Black | Dec 2006 | B2 |
| 7155246 | Bhushan | Dec 2006 | B2 |
| 7158506 | Jacobs et al. | Jan 2007 | B2 |
| 7165099 | Sprigg et al. | Jan 2007 | B2 |
| 7167684 | Kadous | Jan 2007 | B2 |
| 7177351 | Kadous | Feb 2007 | B2 |
| 7177648 | Attar | Feb 2007 | B2 |
| 7181666 | Grob | Feb 2007 | B2 |
| 7184426 | Padovani | Feb 2007 | B2 |
| 7184713 | Kadous | Feb 2007 | B2 |
| 7184954 | Jacobs et al. | Feb 2007 | B1 |
| 7190951 | Jacobs et al. | Mar 2007 | B2 |
| 7194041 | Kadous | Mar 2007 | B2 |
| 7206580 | Black | Apr 2007 | B2 |
| 7206598 | Attar | Apr 2007 | B2 |
| 7209517 | Sindhushayana | Apr 2007 | B2 |
| 7219145 | Chmaytelli et al. | May 2007 | B2 |
| 7228148 | Esteves | Jun 2007 | B2 |
| 7233794 | Grob | Jun 2007 | B2 |
| 7236535 | Subramaniam | Jun 2007 | B2 |
| 7239622 | Black | Jul 2007 | B2 |
| 7239847 | Attar | Jul 2007 | B2 |
| 7248572 | Bender | Jul 2007 | B2 |
| 7251229 | Montojo | Jul 2007 | B2 |
| 7263382 | Chandhok et al. | Aug 2007 | B2 |
| 7266156 | Montojo | Sep 2007 | B2 |
| 7289473 | Padovani | Oct 2007 | B1 |
| 7295857 | Joshi | Nov 2007 | B2 |
| 7315531 | Black | Jan 2008 | B2 |
| 7324836 | Steenstra et al. | Jan 2008 | B2 |
| 7369549 | Wu | May 2008 | B2 |
| 7376209 | Namgoong | May 2008 | B2 |
| 7382744 | Bhushan | Jun 2008 | B2 |
| 7411930 | Montojo | Aug 2008 | B2 |
| 7418046 | Gore | Aug 2008 | B2 |
| 7424290 | Jacobs et al. | Sep 2008 | B2 |
| 7428269 | Sampath | Sep 2008 | B2 |
| 7450943 | Black | Nov 2008 | B2 |
| 7457639 | Subramaniam | Nov 2008 | B2 |
| D583782 | Jacobs et al. | Dec 2008 | S |
| 7463576 | Krishnan | Dec 2008 | B2 |
| 7472396 | Jacobs et al. | Dec 2008 | B2 |
| 7477693 | Subramaniam | Jan 2009 | B2 |
| 7483699 | Karmi | Jan 2009 | B2 |
| 7499427 | Padovani | Mar 2009 | B2 |
| 7508748 | Kadous | Mar 2009 | B2 |
| 7525909 | Fan | Apr 2009 | B2 |
| 7539507 | Grob | May 2009 | B2 |
| 7564775 | Jayaraman | Jul 2009 | B2 |
| 7564794 | Montojo | Jul 2009 | B2 |
| 7564818 | Black | Jul 2009 | B2 |
| 7567621 | Sampath | Jul 2009 | B2 |
| 7576605 | Lee et al. | Aug 2009 | B2 |
| 7580709 | Black | Aug 2009 | B2 |
| 7596090 | Black | Sep 2009 | B2 |
| 7596098 | Karmi | Sep 2009 | B2 |
| 7599329 | Karmi | Oct 2009 | B2 |
| 7606326 | Krishnan | Oct 2009 | B2 |
| 7609773 | Bhushan | Oct 2009 | B2 |
| 7613978 | Jalali | Nov 2009 | B2 |
| 7620005 | Wei | Nov 2009 | B2 |
| 7630719 | Bender | Dec 2009 | B2 |
| 7646802 | Black | Jan 2010 | B2 |
| 7668125 | Kadous | Feb 2010 | B2 |
| 7672383 | Namgoong | Mar 2010 | B2 |
| 7675886 | Agrawal | Mar 2010 | B2 |
| 7684797 | Jain et al. | Mar 2010 | B2 |
| 7693213 | Sindhushayana | Apr 2010 | B2 |
| 7715356 | Bender | May 2010 | B2 |
| 7719991 | Bhushan | May 2010 | B2 |
| 7729714 | Black | Jun 2010 | B2 |
| 7734285 | Chmaytelli et al. | Jun 2010 | B2 |
| 7738906 | Attar | Jun 2010 | B2 |
| 7742447 | Joshi | Jun 2010 | B2 |
| 7788092 | Jacobs et al. | Aug 2010 | B2 |
| 7796563 | Wu | Sep 2010 | B2 |
| 7817677 | Black | Oct 2010 | B2 |
| 7817760 | Black | Oct 2010 | B2 |
| 7826441 | Black | Nov 2010 | B2 |
| 7830900 | Black | Nov 2010 | B2 |
| 7835695 | Ling | Nov 2010 | B2 |
| 7844040 | Sprigg et al. | Nov 2010 | B2 |
| 7848282 | Padovani | Dec 2010 | B2 |
| 7848283 | Padovani | Dec 2010 | B2 |
| 7848284 | Padovani | Dec 2010 | B2 |
| 7848285 | Padovani | Dec 2010 | B2 |
| 7848298 | Attar | Dec 2010 | B2 |
| 7869387 | Black | Jan 2011 | B2 |
| 7876265 | Black | Jan 2011 | B2 |
| 7877744 | Jacobs et al. | Jan 2011 | B2 |
| 7890144 | Subramaniam | Feb 2011 | B2 |
| 7893873 | Black | Feb 2011 | B2 |
| 7903615 | Gorokhov | Mar 2011 | B2 |
| 7907121 | Jacobs et al. | Mar 2011 | B2 |
| 7924753 | Attar | Apr 2011 | B2 |
| 7929991 | Jacobs et al. | Apr 2011 | B2 |
| 7940663 | Kadous | May 2011 | B2 |
| 7940908 | Sprigg et al. | May 2011 | B2 |
| 7948959 | Wang | May 2011 | B2 |
| 7953062 | Sindhushayana | May 2011 | B2 |
| 7961592 | Black | Jun 2011 | B2 |
| 7974359 | Gorokhov | Jul 2011 | B2 |
| 7995531 | Padovani | Aug 2011 | B2 |
| 7995684 | Montojo | Aug 2011 | B2 |
| 8005042 | Padovani | Aug 2011 | B2 |
| 8009625 | Padovani | Aug 2011 | B2 |
| 8010113 | Black | Aug 2011 | B2 |
| 8014331 | Sarkar | Sep 2011 | B2 |
| 8040942 | Bhushan | Oct 2011 | B2 |
| 8041302 | Gardner et al. | Oct 2011 | B2 |
| 8050198 | Bhushan | Nov 2011 | B2 |
| 8060129 | Grob | Nov 2011 | B2 |
| 8073068 | Kim | Dec 2011 | B2 |
| 8077654 | Sutivong | Dec 2011 | B2 |
| 8077655 | Padovani | Dec 2011 | B2 |
| 8077691 | Kadous | Dec 2011 | B2 |
| 8085678 | Spindola | Dec 2011 | B2 |
| 8089924 | Padovani | Jan 2012 | B2 |
| 8094623 | Attar | Jan 2012 | B2 |
| 8094740 | Bhushan | Jan 2012 | B2 |
| 8098231 | Jacobs et al. | Jan 2012 | B2 |
| 8098767 | Mirbagheri | Jan 2012 | B2 |
| 8102872 | Spindola | Jan 2012 | B2 |
| 8107517 | Naguib | Jan 2012 | B2 |
| 8111663 | Black | Feb 2012 | B2 |
| 8116283 | Black | Feb 2012 | B2 |
| 8126072 | Namgoong | Feb 2012 | B2 |
| 8139672 | Gore | Mar 2012 | B2 |
| 8160596 | Black | Apr 2012 | B2 |
| 8165619 | Attar | Apr 2012 | B2 |
| 8175594 | Attar | May 2012 | B2 |
| 8189540 | Padovani | May 2012 | B2 |
| 8203961 | Yavuz | Jun 2012 | B2 |
| 8204530 | Gorokhov | Jun 2012 | B2 |
| 8213390 | Black | Jul 2012 | B2 |
| 8218573 | Bhushan | Jul 2012 | B2 |
| 8229423 | Sarkar | Jul 2012 | B2 |
| 8249577 | Chmaytelli et al. | Aug 2012 | B2 |
| 8274948 | Bender | Sep 2012 | B2 |
| 8301598 | Chandhok et al. | Oct 2012 | B2 |
| 8306096 | Sampath | Nov 2012 | B2 |
| 8311027 | Padovani | Nov 2012 | B2 |
| 8331310 | Wang | Dec 2012 | B2 |
| 8331377 | Attar | Dec 2012 | B2 |
| 8331385 | Black | Dec 2012 | B2 |
| 8331892 | Kadous | Dec 2012 | B2 |
| 8351372 | Padovani | Jan 2013 | B2 |
| 8351456 | Kadous | Jan 2013 | B2 |
| 8363697 | Grob | Jan 2013 | B2 |
| 8374134 | Wang et al. | Feb 2013 | B2 |
| 8375261 | Shi | Feb 2013 | B2 |
| 8385433 | Wang | Feb 2013 | B2 |
| 8385465 | Kadous | Feb 2013 | B2 |
| 8385923 | Attar | Feb 2013 | B2 |
| 8391196 | Gorokhov | Mar 2013 | B2 |
| 8391337 | Black | Mar 2013 | B2 |
| 8391413 | Mantravadi | Mar 2013 | B2 |
| 8396152 | Attar | Mar 2013 | B2 |
| 8406774 | Yavuz | Mar 2013 | B2 |
| 8411594 | Black | Apr 2013 | B2 |
| 8412227 | Edge | Apr 2013 | B2 |
| 8416756 | Bhushan | Apr 2013 | B2 |
| 8451740 | Sampath | May 2013 | B2 |
| 8451776 | Dayal | May 2013 | B2 |
| 8452011 | Guo | May 2013 | B2 |
| 8457152 | Gorokhov | Jun 2013 | B2 |
| 8462859 | Sampath | Jun 2013 | B2 |
| 8462950 | Jacobs | Jun 2013 | B2 |
| 8472322 | Black | Jun 2013 | B2 |
| 8483223 | Black | Jul 2013 | B2 |
| 8487478 | Kirby | Jul 2013 | B2 |
| 8494593 | Black | Jul 2013 | B2 |
| 8498192 | Bhushan | Jul 2013 | B2 |
| 8514988 | Wu | Aug 2013 | B2 |
| 8537875 | Soriaga | Sep 2013 | B2 |
| RE44577 | Yafuso | Nov 2013 | E |
| 8576760 | Gorokhov | Nov 2013 | B2 |
| 8582621 | Grob | Nov 2013 | B2 |
| 8583137 | Rezaiifar | Nov 2013 | B2 |
| 8588777 | Grob | Nov 2013 | B2 |
| 8589514 | Duggal et al. | Nov 2013 | B2 |
| 8594252 | Black | Nov 2013 | B2 |
| 8605729 | Dayal | Dec 2013 | B2 |
| 8605801 | Rezaiifar | Dec 2013 | B2 |
| 8605880 | Sprigg et al. | Dec 2013 | B2 |
| 8611303 | Rezaiifar | Dec 2013 | B2 |
| 8611305 | Black | Dec 2013 | B2 |
| 8611310 | Black | Dec 2013 | B2 |
| 8611325 | Black | Dec 2013 | B2 |
| 8611815 | Mohammadian | Dec 2013 | B2 |
| 8619717 | Agrawal | Dec 2013 | B2 |
| 8619835 | Grob | Dec 2013 | B2 |
| 8630602 | Attar | Jan 2014 | B2 |
| 8634435 | Kadous | Jan 2014 | B2 |
| 8634438 | Nanda | Jan 2014 | B2 |
| 8635645 | Krishnamoorthi | Jan 2014 | B2 |
| 8638758 | Black | Jan 2014 | B2 |
| 8639190 | Gore | Jan 2014 | B2 |
| 8639662 | Chandhok et al. | Jan 2014 | B2 |
| 8644396 | Lee et al. | Feb 2014 | B2 |
| 8654705 | Wang | Feb 2014 | B2 |
| 8654715 | Wang | Feb 2014 | B2 |
| 8654868 | Jacobs et al. | Feb 2014 | B2 |
| 8655400 | Kadous | Feb 2014 | B2 |
| 8665880 | Yavuz | Mar 2014 | B2 |
| 8676209 | Gorokhov | Mar 2014 | B2 |
| 8687648 | Jacobs et al. | Apr 2014 | B2 |
| 8700083 | Yavuz | Apr 2014 | B2 |
| 8712461 | Yavuz | Apr 2014 | B2 |
| 8712848 | Jacobs et al. | Apr 2014 | B2 |
| 8724545 | Dayal | May 2014 | B2 |
| 8724555 | Krishnan | May 2014 | B2 |
| 8732272 | Deshpande | May 2014 | B2 |
| 8737538 | Grob | May 2014 | B2 |
| 8737911 | Black | May 2014 | B2 |
| 8737981 | Jacobs et al. | May 2014 | B2 |
| 8743751 | Li | Jun 2014 | B2 |
| 8743758 | Bhargava et al. | Jun 2014 | B1 |
| 8743909 | Black | Jun 2014 | B2 |
| 8744018 | Chen | Jun 2014 | B2 |
| 8755350 | Grob | Jun 2014 | B2 |
| 8760994 | Wang | Jun 2014 | B2 |
| 8767885 | Sampath | Jul 2014 | B2 |
| 8773308 | Black | Jul 2014 | B2 |
| 8810194 | Kirby | Aug 2014 | B2 |
| 8818274 | Grob | Aug 2014 | B2 |
| D712881 | Shaanan et al. | Sep 2014 | S |
| 8824979 | Yavuz | Sep 2014 | B2 |
| 8825860 | Linsky | Sep 2014 | B2 |
| 8830934 | Banister | Sep 2014 | B2 |
| 8831156 | Liang | Sep 2014 | B2 |
| 8839079 | Chen | Sep 2014 | B2 |
| 8842693 | Agrawal | Sep 2014 | B2 |
| 8848607 | Wang | Sep 2014 | B2 |
| 8854944 | Jou | Oct 2014 | B2 |
| 8855001 | Gorokhov | Oct 2014 | B2 |
| 8867456 | Yavuz | Oct 2014 | B2 |
| 8868118 | Rezaiifar | Oct 2014 | B2 |
| 8873534 | Sindhushayana | Oct 2014 | B2 |
| 8878393 | Kirby | Nov 2014 | B2 |
| 8879440 | Guo | Nov 2014 | B2 |
| 8879445 | Sadek | Nov 2014 | B2 |
| 8885744 | Kadous | Nov 2014 | B2 |
| 8886126 | Mantravadi | Nov 2014 | B2 |
| 8886239 | Dayal | Nov 2014 | B2 |
| 8891436 | Zhang | Nov 2014 | B2 |
| 8892035 | Mohammadian | Nov 2014 | B2 |
| 8897181 | Wang | Nov 2014 | B2 |
| 8897188 | Black | Nov 2014 | B2 |
| 8897220 | Kadous | Nov 2014 | B2 |
| 8897256 | Cherian | Nov 2014 | B2 |
| 8903021 | Mantravadi | Dec 2014 | B2 |
| 8908496 | Kadous | Dec 2014 | B2 |
| 8923109 | Wang | Dec 2014 | B2 |
| 8923125 | Lott | Dec 2014 | B2 |
| 8923208 | Dayal | Dec 2014 | B2 |
| 8929908 | Agrawal | Jan 2015 | B2 |
| 8947042 | Kirby et al. | Feb 2015 | B2 |
| 8948095 | Black | Feb 2015 | B2 |
| 8948147 | Zheng | Feb 2015 | B2 |
| 8954063 | Sarkar | Feb 2015 | B2 |
| 8963486 | Kirby | Feb 2015 | B2 |
| 8966001 | Rauber | Feb 2015 | B2 |
| 8971461 | Sampath | Mar 2015 | B2 |
| 8971808 | Talvitie et al. | Mar 2015 | B2 |
| 8971811 | Grob | Mar 2015 | B2 |
| 8971823 | Gore | Mar 2015 | B2 |
| 8971884 | Ahluwalia | Mar 2015 | B2 |
| 8983480 | Rezaiifar | Mar 2015 | B2 |
| 8995417 | Jou | Mar 2015 | B2 |
| 9001735 | Padovani | Apr 2015 | B2 |
| 9007942 | Zhao | Apr 2015 | B2 |
| 9014152 | Jou | Apr 2015 | B2 |
| 9037134 | Grob | May 2015 | B2 |
| 9055545 | Black | Jun 2015 | B2 |
| 9059785 | Fertonani | Jun 2015 | B2 |
| 9066306 | Yavuz | Jun 2015 | B2 |
| 9071344 | Smee | Jun 2015 | B2 |
| 9072102 | Yavuz | Jun 2015 | B2 |
| 9078269 | Yavuz | Jul 2015 | B2 |
| 9088389 | Gorokhov | Jul 2015 | B2 |
| 9100549 | Jacobs et al. | Aug 2015 | B2 |
| 9106287 | Wang | Aug 2015 | B2 |
| 9113488 | Oguz | Aug 2015 | B2 |
| 9118387 | Padovani | Aug 2015 | B2 |
| 9119026 | Black | Aug 2015 | B2 |
| 9119217 | Black | Aug 2015 | B2 |
| 9124344 | Padovani | Sep 2015 | B2 |
| 9130407 | Toncich et al. | Sep 2015 | B2 |
| 9131420 | Rezaiifar | Sep 2015 | B2 |
| 9136958 | Walker | Sep 2015 | B2 |
| 9136974 | Gorokhov | Sep 2015 | B2 |
| 9137806 | Yavuz | Sep 2015 | B2 |
| 9141961 | Rajan et al. | Sep 2015 | B2 |
| 9143957 | Sadek | Sep 2015 | B2 |
| 9144036 | Gorokhov | Sep 2015 | B2 |
| 9144084 | Sadek | Sep 2015 | B2 |
| 9148256 | Sampath | Sep 2015 | B2 |
| 9148908 | Bhargava et al. | Sep 2015 | B2 |
| 9154179 | Gudem | Oct 2015 | B2 |
| 9154211 | Sampath | Oct 2015 | B2 |
| 9155106 | Krishnan | Oct 2015 | B2 |
| 9155124 | Bhargava et al. | Oct 2015 | B2 |
| 9161232 | Linsky | Oct 2015 | B2 |
| 9161233 | Wang | Oct 2015 | B2 |
| 9166715 | Jacobs et al. | Oct 2015 | B2 |
| 9172402 | Gudem | Oct 2015 | B2 |
| 9172453 | Wang | Oct 2015 | B2 |
| 9177467 | Tu | Nov 2015 | B2 |
| 9178387 | Mohammadian et al. | Nov 2015 | B2 |
| 9178632 | Grob | Nov 2015 | B2 |
| 9179319 | Gore | Nov 2015 | B2 |
| 9184870 | Sampath | Nov 2015 | B2 |
| 9185718 | Kadous | Nov 2015 | B2 |
| 9185720 | Mantravadi | Nov 2015 | B2 |
| 9191276 | Jacobs et al. | Nov 2015 | B2 |
| 9198053 | Edge | Nov 2015 | B2 |
| 9204437 | Smee | Dec 2015 | B2 |
| 9226173 | Sadek | Dec 2015 | B2 |
| 9246560 | Sampath | Jan 2016 | B2 |
| 9247525 | Jacobs et al. | Jan 2016 | B2 |
| 9253658 | Sadek | Feb 2016 | B2 |
| 9264972 | Fan | Feb 2016 | B2 |
| D751928 | Shaanan et al. | Mar 2016 | S |
| 9277564 | Wang | Mar 2016 | B2 |
| 9282462 | Dayal | Mar 2016 | B2 |
| 9288814 | Yavuz | Mar 2016 | B2 |
| 9294932 | Walker | Mar 2016 | B2 |
| 9307544 | Gore | Apr 2016 | B2 |
| 9344973 | Yavuz | May 2016 | B2 |
| 9358940 | Cooper et al. | Jun 2016 | B2 |
| 9363006 | Bhargava et al. | Jun 2016 | B2 |
| 9363764 | Black | Jun 2016 | B2 |
| 9374791 | Yavuz | Jun 2016 | B2 |
| 9398602 | Kadous | Jul 2016 | B2 |
| 9407327 | Kirby | Aug 2016 | B2 |
| 9408165 | Jou | Aug 2016 | B2 |
| 9408220 | Gore | Aug 2016 | B2 |
| 9414434 | Bhargava et al. | Aug 2016 | B2 |
| 9419751 | Sindhushayana | Aug 2016 | B2 |
| 9428127 | Cooper et al. | Aug 2016 | B2 |
| D765595 | Shaanan et al. | Sep 2016 | S |
| 9450638 | Yan | Sep 2016 | B2 |
| 9451480 | Huang | Sep 2016 | B2 |
| 9451514 | Michel et al. | Sep 2016 | B1 |
| 9454265 | Wyrwas et al. | Sep 2016 | B2 |
| 9461736 | Bhushan | Oct 2016 | B2 |
| 9474075 | Yavuz | Oct 2016 | B2 |
| 9483769 | Rajan et al. | Nov 2016 | B2 |
| 9491722 | Yavuz | Nov 2016 | B2 |
| 9497495 | Krishnamoorthi | Nov 2016 | B2 |
| 9503134 | Sadek | Nov 2016 | B2 |
| 9509452 | Liang | Nov 2016 | B2 |
| 9524502 | Rajan et al. | Dec 2016 | B2 |
| 9525477 | Wu | Dec 2016 | B1 |
| 9544075 | Altman et al. | Jan 2017 | B2 |
| 9578591 | Bhargava et al. | Feb 2017 | B2 |
| 9578649 | Dayal | Feb 2017 | B2 |
| 9585150 | Marsh | Feb 2017 | B2 |
| 9585156 | Bhattad | Feb 2017 | B2 |
| 9609649 | Fan | Mar 2017 | B2 |
| 9660776 | Kadous | May 2017 | B2 |
| 9667817 | Grob | May 2017 | B2 |
| 9673837 | Xue | Jun 2017 | B2 |
| 9716402 | Kirby et al. | Jul 2017 | B2 |
| 9730227 | Marsh | Aug 2017 | B2 |
| 9747613 | Rajan et al. | Aug 2017 | B2 |
| 9750014 | Sadek | Aug 2017 | B2 |
| 9788361 | Valliappan | Oct 2017 | B2 |
| 9793738 | Jacobs et al. | Oct 2017 | B2 |
| 9794949 | Bhargava et al. | Oct 2017 | B2 |
| 9806791 | Bhargava et al. | Oct 2017 | B2 |
| 9819747 | Dacosta | Nov 2017 | B2 |
| 9832785 | Kadous | Nov 2017 | B2 |
| 9860033 | Kadous | Jan 2018 | B2 |
| 9867194 | Kadous | Jan 2018 | B2 |
| 9893800 | Wu | Feb 2018 | B2 |
| 9900856 | Wu | Feb 2018 | B2 |
| 9900880 | Fawazhashim et al. | Feb 2018 | B1 |
| 9924368 | Valliappan | Mar 2018 | B2 |
| 9924436 | Grob | Mar 2018 | B2 |
| 9936400 | Lee | Apr 2018 | B2 |
| 9942921 | Bhargava et al. | Apr 2018 | B2 |
| 9954399 | Toncich et al. | Apr 2018 | B2 |
| 9954668 | Lee | Apr 2018 | B2 |
| 9955476 | Black | Apr 2018 | B2 |
| 9980090 | Gujral et al. | May 2018 | B2 |
| 9986480 | Ta et al. | May 2018 | B2 |
| 9991747 | Toncich et al. | Jun 2018 | B2 |
| 9991986 | Sindhushayana | Jun 2018 | B2 |
| 10038999 | Sprigg et al. | Jul 2018 | B2 |
| 10044438 | Kadous | Aug 2018 | B2 |
| 10044459 | Chendamarai Kannan | Aug 2018 | B2 |
| 10075313 | Black | Sep 2018 | B2 |
| 10091789 | Valliappan | Oct 2018 | B2 |
| 10136311 | Bhargava et al. | Nov 2018 | B2 |
| 10178649 | Liu | Jan 2019 | B2 |
| 10182404 | Prakash | Jan 2019 | B2 |
| 10201014 | Kadous et al. | Feb 2019 | B2 |
| 10205505 | Michel et al. | Feb 2019 | B2 |
| 10218406 | Liu et al. | Feb 2019 | B2 |
| 10219235 | Patel et al. | Feb 2019 | B2 |
| 10219252 | Chendamarai Kannan et al. | Feb 2019 | B2 |
| 10219300 | Gorokhov et al. | Feb 2019 | B2 |
| 10225818 | Liu et al. | Mar 2019 | B2 |
| 10292019 | Ta et al. | May 2019 | B2 |
| 10360593 | Hunter et al. | Jul 2019 | B2 |
| 10420161 | Sava | Sep 2019 | B1 |
| 10517027 | Ta et al. | Dec 2019 | B2 |
| 10568139 | Bhargava et al. | Feb 2020 | B2 |
| 10756795 | Black et al. | Aug 2020 | B2 |
| 10880773 | Huang | Dec 2020 | B2 |
| 20010024437 | Bender | Sep 2001 | A1 |
| 20010034762 | Jacobs et al. | Oct 2001 | A1 |
| 20010034763 | Jacobs et al. | Oct 2001 | A1 |
| 20010044736 | Jacobs et al. | Nov 2001 | A1 |
| 20010044741 | Jacobs et al. | Nov 2001 | A1 |
| 20010047408 | Jacobs et al. | Nov 2001 | A1 |
| 20010055391 | Jacobs | Dec 2001 | A1 |
| 20020029166 | Jacobs et al. | Mar 2002 | A1 |
| 20020059418 | Bird et al. | May 2002 | A1 |
| 20020072967 | Jacobs et al. | Jun 2002 | A1 |
| 20020173315 | Chmaytelli | Nov 2002 | A1 |
| 20030050832 | Jacobs et al. | Mar 2003 | A1 |
| 20030145119 | Bender | Jul 2003 | A1 |
| 20030149738 | Jacobs et al. | Aug 2003 | A1 |
| 20040039642 | Jacobs et al. | Feb 2004 | A1 |
| 20040039784 | Jacobs et al. | Feb 2004 | A1 |
| 20040054588 | Jacobs et al. | Mar 2004 | A1 |
| 20040110525 | Black | Jun 2004 | A1 |
| 20040121730 | Kadous | Jun 2004 | A1 |
| 20040205151 | Sprigg et al. | Oct 2004 | A1 |
| 20040249708 | Jacobs et al. | Dec 2004 | A1 |
| 20040268216 | Jacobs et al. | Dec 2004 | A1 |
| 20050104857 | Jacobs et al. | May 2005 | A1 |
| 20060063569 | Jacobs et al. | Mar 2006 | A1 |
| 20060111920 | Jacobs et al. | May 2006 | A1 |
| 20060119356 | Rabe et al. | Jun 2006 | A1 |
| 20060174314 | Jacobs et al. | Aug 2006 | A1 |
| 20060203794 | Sampath | Sep 2006 | A1 |
| 20060223580 | Antonio et al. | Oct 2006 | A1 |
| 20060229089 | Tokgoz | Oct 2006 | A1 |
| 20070005428 | Jacobs et al. | Jan 2007 | A1 |
| 20070005429 | Jacobs et al. | Jan 2007 | A1 |
| 20070038728 | Jacobs et al. | Feb 2007 | A1 |
| 20070041457 | Kadous | Feb 2007 | A1 |
| 20070066232 | Black | Mar 2007 | A1 |
| 20070071147 | Sampath | Mar 2007 | A1 |
| 20070140192 | Kusumoto | Jun 2007 | A1 |
| 20070165738 | Barriac | Jul 2007 | A1 |
| 20070198981 | Jacobs et al. | Aug 2007 | A1 |
| 20080025241 | Bhushan | Jan 2008 | A1 |
| 20080032740 | Joshi | Feb 2008 | A1 |
| 20080112495 | Gore | May 2008 | A1 |
| 20080126258 | Jacobs et al. | May 2008 | A1 |
| 20090080499 | Yavuz | Mar 2009 | A1 |
| 20090163209 | Black | Jun 2009 | A1 |
| 20090187593 | Chen et al. | Jul 2009 | A1 |
| 20090198608 | Jain et al. | Aug 2009 | A1 |
| 20090307739 | Dean et al. | Dec 2009 | A1 |
| 20100003931 | Krishnan | Jan 2010 | A1 |
| 20100046497 | Jalali | Feb 2010 | A1 |
| 20100057924 | Rauber | Mar 2010 | A1 |
| 20100067422 | Kadous | Mar 2010 | A1 |
| 20100067518 | Kaufman et al. | Mar 2010 | A1 |
| 20100215022 | Black | Aug 2010 | A1 |
| 20100225270 | Jacobs et al. | Sep 2010 | A1 |
| 20110007680 | Kadous | Jan 2011 | A1 |
| 20110007688 | Veeravalli | Jan 2011 | A1 |
| 20110047384 | Jacobs et al. | Feb 2011 | A1 |
| 20110222423 | Spindola | Sep 2011 | A1 |
| 20110256834 | Dayal | Oct 2011 | A1 |
| 20110310858 | Tokgoz | Dec 2011 | A1 |
| 20120016947 | Damola | Jan 2012 | A1 |
| 20120057511 | Sivakumar et al. | Mar 2012 | A1 |
| 20120069232 | Chui | Mar 2012 | A1 |
| 20120077532 | Kadous | Mar 2012 | A1 |
| 20120113906 | Kadous | May 2012 | A1 |
| 20120127870 | Zhao | May 2012 | A1 |
| 20120127923 | Zhao | May 2012 | A1 |
| 20120140798 | Kadous | Jun 2012 | A1 |
| 20120213303 | Kadous | Aug 2012 | A1 |
| 20120258706 | Yu et al. | Oct 2012 | A1 |
| 20130027440 | Martin et al. | Jan 2013 | A1 |
| 20130039262 | Lim et al. | Feb 2013 | A1 |
| 20130170440 | Tavildar et al. | Jul 2013 | A1 |
| 20130201959 | Guo | Aug 2013 | A1 |
| 20130214909 | Meijers et al. | Aug 2013 | A1 |
| 20130217333 | Sprigg et al. | Aug 2013 | A1 |
| 20130229990 | Fan | Sep 2013 | A1 |
| 20130235754 | Lim et al. | Sep 2013 | A1 |
| 20130253918 | Jacobs | Sep 2013 | A1 |
| 20130300358 | Kirby | Nov 2013 | A1 |
| 20130335528 | Vishwanath et al. | Dec 2013 | A1 |
| 20140029705 | Wu | Jan 2014 | A1 |
| 20140038645 | Wu | Feb 2014 | A1 |
| 20140051470 | Patil et al. | Feb 2014 | A1 |
| 20140056239 | Zhang | Feb 2014 | A1 |
| 20140071894 | Kairouz | Mar 2014 | A1 |
| 20140071967 | Velasco | Mar 2014 | A1 |
| 20140079155 | Wang | Mar 2014 | A1 |
| 20140089073 | Jacobs et al. | Mar 2014 | A1 |
| 20140133656 | Wurster et al. | May 2014 | A1 |
| 20140219117 | Meshkati | Aug 2014 | A1 |
| 20140219194 | Varoglu et al. | Aug 2014 | A1 |
| 20140219243 | Meshkati | Aug 2014 | A1 |
| 20140247779 | Wei et al. | Sep 2014 | A1 |
| 20140247814 | Zhang | Sep 2014 | A1 |
| 20140256340 | Prakash et al. | Sep 2014 | A1 |
| 20140269616 | Black | Sep 2014 | A1 |
| 20140273884 | Mantravadi | Sep 2014 | A1 |
| 20140285684 | Huang | Sep 2014 | A1 |
| 20140362744 | Yan | Dec 2014 | A1 |
| 20150063150 | Sadek | Mar 2015 | A1 |
| 20150063151 | Sadek | Mar 2015 | A1 |
| 20150063323 | Sadek | Mar 2015 | A1 |
| 20150065152 | Sadek | Mar 2015 | A1 |
| 20150070323 | Hong | Mar 2015 | A1 |
| 20150071648 | Hong | Mar 2015 | A1 |
| 20150083917 | Wyrwas et al. | Mar 2015 | A1 |
| 20150084928 | Wyrwas et al. | Mar 2015 | A1 |
| 20150084994 | Wyrwas et al. | Mar 2015 | A1 |
| 20150085686 | Chande | Mar 2015 | A1 |
| 20150133184 | Sadek | May 2015 | A1 |
| 20150139015 | Kadous | May 2015 | A1 |
| 20150163823 | Sadek | Jun 2015 | A1 |
| 20150181299 | Rauber | Jun 2015 | A1 |
| 20150195733 | Yavuz | Jul 2015 | A1 |
| 20150223077 | Fan | Aug 2015 | A1 |
| 20150245273 | Grob | Aug 2015 | A1 |
| 20150282077 | Yavuz | Oct 2015 | A1 |
| 20150319702 | Patel | Nov 2015 | A1 |
| 20150326382 | Li | Nov 2015 | A1 |
| 20150350919 | Patel | Dec 2015 | A1 |
| 20150373605 | Kanamarlapudi | Dec 2015 | A1 |
| 20150382190 | Canoy | Dec 2015 | A1 |
| 20160012489 | Rajan et al. | Jan 2016 | A1 |
| 20160037511 | Vincze et al. | Feb 2016 | A1 |
| 20160085440 | Canoy et al. | Mar 2016 | A1 |
| 20160088625 | Kadous | Mar 2016 | A1 |
| 20160095039 | Valliappan | Mar 2016 | A1 |
| 20160095040 | Valliappan | Mar 2016 | A1 |
| 20160128123 | Li | May 2016 | A1 |
| 20160128130 | Sadek | May 2016 | A1 |
| 20160164573 | Birk | Jun 2016 | A1 |
| 20160219578 | Lim et al. | Jul 2016 | A1 |
| 20160255664 | Li | Sep 2016 | A1 |
| 20160315688 | Bhargava et al. | Oct 2016 | A1 |
| 20160316361 | Bhargava et al. | Oct 2016 | A1 |
| 20160337971 | Bhargava et al. | Nov 2016 | A1 |
| 20160353482 | Valliappan | Dec 2016 | A1 |
| 20170005741 | Wu | Jan 2017 | A1 |
| 20170013658 | Ta et al. | Jan 2017 | A1 |
| 20170019814 | Determan | Jan 2017 | A1 |
| 20170027017 | Black | Jan 2017 | A1 |
| 20170048047 | Kadous | Feb 2017 | A1 |
| 20170048889 | Kadous | Feb 2017 | A1 |
| 20170054488 | Michel et al. | Feb 2017 | A1 |
| 20170055260 | Valliappan | Feb 2017 | A1 |
| 20170055285 | Valliappan | Feb 2017 | A1 |
| 20170055291 | Gorokhov | Feb 2017 | A1 |
| 20170064657 | Chendamarai Kannan | Mar 2017 | A1 |
| 20170064729 | Sadek | Mar 2017 | A1 |
| 20170070847 | Altman et al. | Mar 2017 | A1 |
| 20170076311 | Rajan et al. | Mar 2017 | A1 |
| 20170093545 | Kadous | Mar 2017 | A1 |
| 20170093883 | Hebron | Mar 2017 | A1 |
| 20170094680 | Patel | Mar 2017 | A1 |
| 20170135029 | Chendamarai Kannan | May 2017 | A1 |
| 20170142705 | Chendamarai Kannan | May 2017 | A1 |
| 20170142713 | Chendamarai Kannan | May 2017 | A1 |
| 20170156078 | Lee | Jun 2017 | A1 |
| 20170202022 | Chendamarai Kannan | Jul 2017 | A1 |
| 20170208576 | Chendamarai Kannan | Jul 2017 | A1 |
| 20170222771 | Chendamarai Kannan | Aug 2017 | A1 |
| 20170223651 | Patel | Aug 2017 | A1 |
| 20170223737 | Patel | Aug 2017 | A1 |
| 20170250842 | Han et al. | Aug 2017 | A1 |
| 20170251473 | Xue | Aug 2017 | A1 |
| 20170280382 | Radulescu | Sep 2017 | A1 |
| 20170289761 | Stojanovski | Oct 2017 | A1 |
| 20170311316 | Chendamarai Kannan | Oct 2017 | A1 |
| 20170311343 | Chendamarai Kannan | Oct 2017 | A1 |
| 20170311346 | Chendamarai Kannan | Oct 2017 | A1 |
| 20170318586 | Wang | Nov 2017 | A1 |
| 20170332288 | Sadek | Nov 2017 | A1 |
| 20170353874 | Harrang | Dec 2017 | A1 |
| 20170359263 | Barghi | Dec 2017 | A1 |
| 20170359815 | Chendamarai Kannan | Dec 2017 | A1 |
| 20170373807 | Hessler | Dec 2017 | A1 |
| 20180014311 | Bhargava et al. | Jan 2018 | A1 |
| 20180026703 | Bhargava et al. | Jan 2018 | A1 |
| 20180027059 | Miller | Jan 2018 | A1 |
| 20180041917 | Xi et al. | Feb 2018 | A1 |
| 20180042018 | Bhushan | Feb 2018 | A1 |
| 20180048372 | Sun et al. | Feb 2018 | A1 |
| 20180054234 | Stuckman | Feb 2018 | A1 |
| 20180054348 | Luo | Feb 2018 | A1 |
| 20180054382 | Luo | Feb 2018 | A1 |
| 20180054762 | Kadous | Feb 2018 | A1 |
| 20180054780 | Radulescu | Feb 2018 | A1 |
| 20180054783 | Luo | Feb 2018 | A1 |
| 20180054811 | Luo | Feb 2018 | A1 |
| 20180054812 | Luo | Feb 2018 | A1 |
| 20180054830 | Luo | Feb 2018 | A1 |
| 20180054832 | Luo | Feb 2018 | A1 |
| 20180059221 | Slobodyanyuk | Mar 2018 | A1 |
| 20180063799 | Sadek | Mar 2018 | A1 |
| 20180069589 | Liu | Mar 2018 | A1 |
| 20180069594 | Henry | Mar 2018 | A1 |
| 20180069731 | Henry | Mar 2018 | A1 |
| 20180070243 | Liu | Mar 2018 | A1 |
| 20180084430 | Patel | Mar 2018 | A1 |
| 20180098225 | Damnjanovic | Apr 2018 | A1 |
| 20180098335 | Sun | Apr 2018 | A1 |
| 20180103461 | Sun | Apr 2018 | A1 |
| 20180103472 | Zhang | Apr 2018 | A1 |
| 20180109957 | Fan | Apr 2018 | A1 |
| 20180110022 | Fan | Apr 2018 | A1 |
| 20180110063 | Fan | Apr 2018 | A1 |
| 20180115907 | Damnjanovic | Apr 2018 | A1 |
| 20180115933 | Radulescu | Apr 2018 | A1 |
| 20180115973 | Black | Apr 2018 | A1 |
| 20180123859 | Liu | May 2018 | A1 |
| 20180124770 | Yerramalli | May 2018 | A1 |
| 20180124776 | Yerramalli | May 2018 | A1 |
| 20180124777 | Yerramalli | May 2018 | A1 |
| 20180124789 | Yerramalli | May 2018 | A1 |
| 20180124820 | Sun | May 2018 | A1 |
| 20180132236 | Kadous | May 2018 | A1 |
| 20180139616 | Khoshnevisan | May 2018 | A1 |
| 20180139618 | Yerramalli | May 2018 | A1 |
| 20180139782 | Sadek | May 2018 | A1 |
| 20180146480 | Chendamarai Kannan | May 2018 | A1 |
| 20180160328 | Chendamarai Kannan | Jun 2018 | A1 |
| 20180160389 | Yerramalli | Jun 2018 | A1 |
| 20180167848 | Lei | Jun 2018 | A1 |
| 20180167968 | Liu | Jun 2018 | A1 |
| 20180175986 | Chendamarai Kannan | Jun 2018 | A1 |
| 20180176946 | Sun | Jun 2018 | A1 |
| 20180198518 | Wu | Jul 2018 | A1 |
| 20180199379 | Bhargava et al. | Jul 2018 | A1 |
| 20180206213 | Kim | Jul 2018 | A1 |
| 20180206252 | Thangarasa et al. | Jul 2018 | A1 |
| 20180213560 | Naghshvar | Jul 2018 | A1 |
| 20180220428 | Sun | Aug 2018 | A1 |
| 20180227011 | Yerramalli | Aug 2018 | A1 |
| 20180227771 | Malik | Aug 2018 | A1 |
| 20180227797 | Liu | Aug 2018 | A1 |
| 20180227936 | Yerramalli | Aug 2018 | A1 |
| 20180227944 | Yerramalli | Aug 2018 | A1 |
| 20180241494 | Chendamarai Kannan | Aug 2018 | A1 |
| 20180241526 | Chendamarai Kannan | Aug 2018 | A1 |
| 20180242163 | Patel | Aug 2018 | A1 |
| 20180242223 | Chendamarai Kannan | Aug 2018 | A1 |
| 20180242232 | Chendamarai Kannan | Aug 2018 | A1 |
| 20180242277 | Liu | Aug 2018 | A1 |
| 20180242348 | Chendamarai Kannan | Aug 2018 | A1 |
| 20180249380 | Zhang | Aug 2018 | A1 |
| 20180249496 | Radulescu | Aug 2018 | A1 |
| 20180255561 | Barghi | Sep 2018 | A1 |
| 20180255584 | Sun | Sep 2018 | A1 |
| 20180262962 | Ta et al. | Sep 2018 | A1 |
| 20180269962 | Liu | Sep 2018 | A1 |
| 20180278363 | Bhushan | Sep 2018 | A1 |
| 20180279134 | Malik | Sep 2018 | A1 |
| 20180279156 | Malik | Sep 2018 | A1 |
| 20180279212 | Malik | Sep 2018 | A1 |
| 20180279292 | Luo | Sep 2018 | A1 |
| 20180287762 | Sun | Oct 2018 | A1 |
| 20180287840 | Akkarakaran | Oct 2018 | A1 |
| 20180287870 | Yerramalli | Oct 2018 | A1 |
| 20180288747 | Sun | Oct 2018 | A1 |
| 20180288749 | Sun | Oct 2018 | A1 |
| 20180288781 | Akkarakaran | Oct 2018 | A1 |
| 20180294911 | Sun | Oct 2018 | A1 |
| 20180295622 | Sadek | Oct 2018 | A1 |
| 20180302186 | Reddy | Oct 2018 | A1 |
| 20180302201 | Yoo | Oct 2018 | A1 |
| 20180302796 | Zhang | Oct 2018 | A1 |
| 20180309479 | Yerramalli | Oct 2018 | A1 |
| 20180310267 | Liu | Oct 2018 | A1 |
| 20180310341 | Yerramalli | Oct 2018 | A1 |
| 20180317093 | Li | Nov 2018 | A1 |
| 20180317259 | Islam | Nov 2018 | A1 |
| 20180324713 | Yoo | Nov 2018 | A1 |
| 20180331870 | Sun | Nov 2018 | A1 |
| 20180332551 | Liu | Nov 2018 | A1 |
| 20180338299 | Liu | Nov 2018 | A1 |
| 20180343156 | Malik | Nov 2018 | A1 |
| 20180343588 | Sadek | Nov 2018 | A1 |
| 20180343676 | Yerramalli | Nov 2018 | A1 |
| 20180352563 | Liu | Dec 2018 | A1 |
| 20180352597 | Bostick et al. | Dec 2018 | A1 |
| 20180359656 | Liu | Dec 2018 | A1 |
| 20180359685 | Li | Dec 2018 | A1 |
| 20180367362 | Sun | Dec 2018 | A1 |
| 20180368089 | Yerramalli | Dec 2018 | A1 |
| 20180376392 | Wu | Dec 2018 | A1 |
| 20180376393 | Wu | Dec 2018 | A1 |
| 20180376503 | Sun | Dec 2018 | A1 |
| 20190007946 | Yerramalli | Jan 2019 | A1 |
| 20190009756 | Jacobs | Jan 2019 | A1 |
| 20190014481 | Yerramalli, Sr. | Jan 2019 | A1 |
| 20190014507 | Zhang | Jan 2019 | A1 |
| 20190014589 | Yerramalli | Jan 2019 | A1 |
| 20190020424 | Yerramalli | Jan 2019 | A1 |
| 20190020461 | Yerramalli | Jan 2019 | A1 |
| 20190020522 | Sun | Jan 2019 | A1 |
| 20190020527 | Lei | Jan 2019 | A1 |
| 20190020528 | Lei | Jan 2019 | A1 |
| 20190020529 | Lei | Jan 2019 | A1 |
| 20190021080 | Lei | Jan 2019 | A1 |
| 20190028999 | Yerramalli | Jan 2019 | A1 |
| 20190029019 | Zhang | Jan 2019 | A1 |
| 20190037376 | Liu | Jan 2019 | A1 |
| 20190037427 | Yerramalli | Jan 2019 | A1 |
| 20190037481 | Zhang | Jan 2019 | A1 |
| 20190037482 | Damnjanovic | Jan 2019 | A1 |
| 20190037525 | Liu | Jan 2019 | A1 |
| 20190037603 | Damnjanovic | Jan 2019 | A1 |
| 20190044648 | Boudreau et al. | Feb 2019 | A1 |
| 20190053048 | Bhargava et al. | Feb 2019 | A1 |
| 20190053064 | Niu et al. | Feb 2019 | A1 |
| 20190053269 | Lei | Feb 2019 | A1 |
| 20190059001 | Yerramalli | Feb 2019 | A1 |
| 20190059102 | Yerramalli | Feb 2019 | A1 |
| 20190069325 | Yerramalli | Feb 2019 | A1 |
| 20190075597 | Yerramalli | Mar 2019 | A1 |
| 20190182703 | Huang | Jun 2019 | A1 |
| 20190230513 | Ang | Jul 2019 | A1 |
| 20190253844 | Ta et al. | Aug 2019 | A1 |
| 20190319723 | Axmon et al. | Oct 2019 | A1 |
| 20200059813 | Park et al. | Feb 2020 | A1 |
| 20200145881 | Mitra | May 2020 | A1 |
| 20200154475 | Pao | May 2020 | A1 |
| 20200195313 | Black et al. | Jun 2020 | A1 |
| 20200195322 | Black et al. | Jun 2020 | A1 |
| 20200195323 | Black et al. | Jun 2020 | A1 |
| 20200213994 | Feng | Jul 2020 | A1 |
| 20200245384 | Jacobs et al. | Jul 2020 | A1 |
| 20200389212 | Black et al. | Dec 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 2012057547 | May 2012 | WO |
| Entry |
|---|
| 3GPP RP-170750, New WID: Further Enhancements to Coordinated Multi-Point (CoMP) Operation for LTE, Mar. 2017. |
| 3GPP TR 36.741, Study on Further Enhancements to Coordinated Multi-Point (CoMP) Operation for LTE, V14.0.0, Mar. 2017. |
| Agrawal, et al., Dynamic Point Selection for LTE-Advanced: Algorithms and Performance, Wireless Communications and Networking Conference (WCNC), 2014 IEEE, Istanbul, Turkey, Apr. 2014, pp. 1392-1397. |
| Andrews, et al., Are We Approaching the Fundamental Limits of Wireless Network Densification?, IEEE Communications Magazine, vol. 54, No. 10, pp. 184-190, Oct. 2016. |
| Björnson, et al., Cooperative Multicell Precoding: Rate Region Characterization and Distributed Strategies with Instantaneous and Statistical CSI, IEEE Transactions on Signal Processing, vol. 58, No. 8, pp. 4298-4310, Aug. 2010. |
| Buzzi, et al., Cell-Free Massive MIMO: User-Centric Approach, IEEE Wireless Communications Letters, vol. 6, No. 6, pp. 706-709, Dec. 2017. |
| Checko, et al., Cloud RAN for Mobile Networks—a Technology Overview, IEEE Communications Surveys & Tutorials, vol. 17, No. 1, Sep. 2014. |
| Chen, et al., Channel Hardening and Favorable Propagation in Cell-Free Massive MIMO with Stochastic Geometry, version 1, 2017. Available at: http://arxiv.org/abs/1710.00395. |
| Chen, et al., Channel Hardening and Favorable Propagation in Cell-Free Massive MIMO with Stochastic Geometry, version 2, 2018. Available at: http://arxiv.org/abs/1710.00395. |
| Davydov, et al., Evaluation of Joint Transmission CoMP in C-RAN based LTE—A HetNets with Large Coordination Areas, Proc. GLOBECOM'14, Atlanta, U.S., Dec. 2013, pp. 801-806. |
| Forenza, et al., Achieving Large Multiplexing Gain in Distributed Antenna Systems via Cooperation with pCell Technology, 49th Asilomar Conference on Signals, Systems and Computers, Nov. 2015, IEEE, pp. 286-293. |
| Gesbert, et al., Multi-cell MIMO Cooperative Networks: A New Look at Interference, IEEE Journal on Selected Areas in Communications, vol. 28, No. 9, pp. 1380-1408, Dec. 2010. |
| Gilhousen, et al., On the Capacity of a Cellular CDMA system, IEEE Transactions on Vehicular Technology, vol. 40, No. 2, pp. 303-311, May 1991. |
| Interdonato, et al., How Much Do Downlink Pilots Improve Cell-Free Massive MIMO?, IEEE, 2016, 7 pages. |
| Larsson, et al., Massive MIMO for Next Generation Wireless Systems, Jan. 2014. |
| Marzetta, et al., Fundamentals of Massive MIMO, Cambridge University Press, Dec. 2016, Table of Contents. |
| Nayebi, et al., Precoding and Power Optimization in Cell-Free Massive MIMO Systems, IEEE Transactions on Wireless Communications, vol. 16, No. 7, pp. 4445-4459, Jul. 2017. |
| Ngo, et al., Cell-Free Massive MIMO Versus Small Cells, IEEE Transactions on Wireless Communications, vol. 16, No. 3, pp. 1834-1850, Mar. 2017. |
| Ngo, et al., On the Total Energy Efficiency of Cell-Free Massive MIMO, IEEE Transactions on Green Communications and Networking, vol. 2, No. 1, pp. 25-39, Mar. 2018. |
| Osseiran, et al., 5G Mobile and Wireless Communications Technology, Cambridge University Press, Oct. 2016, Ch. 9, Coordinated multi-point transmission in 5G. |
| Rohde & Schwarz, LTE Transmission Modes and Beamforming, White Paper, Jul. 2015. |
| Shamai, et al., Enhancing the Cellular Downlink Capacity via Co-processing at the Transmitting End, Proceedings of IEEE VTC-Spring, vol. 3, 2001, pp. 1745-1749. |
| Sun, et al., Performance Evaluation of CS/CB for Coordinated Multipoint Transmission in LTE-A Downlink, Proceedings of IEEE PIMRC'12, Sydney, Australia, Sep. 2012, pp. 1061-1065. |
| Tanghe, et al., The Industrial Indoor Channel: Large-Scale and Temporal Fading at 900, 2400, and 5200 MHz, IEEE Transactions on Wireless Communications, vol. 7, No. 7, pp. 2740-2751, Jul. 2008. |
| Wu, et al., Cloud Radio Access Network (C-RAN): A Primer, IEEE Network, vol. 29, No. 1, pp. 35-41, Jan./Feb. 2015. |
| Wu, et al., Centralized and Distributed Schedulers for Non-Coherent Joint Transmission, Sep. 2018. |
| Zhou, et al., Distributed Wireless Communication System: A New Architecture for Future Public Wireless Access, IEEE Communications Magazine, vol. 41, No. 3, pp. 108-113, Mar. 2003. |
| International Search Report dated Apr. 17, 2020 for International Patent Application No. PCT/US2019/066639. |
| Written Opinion dated Apr. 17, 2020 for International Patent Application No. PCT/US2019/066639. |
| International Search Report and Written Opinion in International Application No. PCT/US2020/014935, dated Apr. 15, 2020. |
| Krishnaswamy et al., “COBA: Concurrent Bandwidth Aggregation—A Case Study in Parallel Wireless Communications,” Journal of Communications, vol. 7, No. 7, pp. 524-537, 2012. |
| U.S. Appl. No 16/224,643 published as US 2020/0195323, User Equipment Configured for Increased Data Rate, filed Dec. 18, 2018. |
| U.S. Appl. No. 16/224,528 published as US 2020/0195322 now U.S. Pat. No. 10,756,795 User Equipment With Cellular Link and Peer-To-Peer Link, filed Dec. 18, 2018. |
| U.S. Appl. No. 16/926,475 published as US 2020/0389212 Multiple-Input Multiple-Output Communication With Wireless Communication Devices, filed Jul. 10, 2020. |
| U.S. Appl. No. 16/224,568 published as US 2020/0195313 Unbalanced Wireless Communication With Group of Devices, filed Dec. 18, 2018. |
| Number | Date | Country | |
|---|---|---|---|
| 20200195321 A1 | Jun 2020 | US |
