Certain embodiments of the invention relate to signal processing for communication systems. More specifically, certain embodiments of the invention relate to a method and system for MIMO transmission in a distributed transceiver network.
Millimeter Wave (mmWave) devices are being utilized for high throughput wireless communications at very high carrier frequencies. There are several standards bodies such as, for example, 60 GHz wireless standard, WirelessHD, WiGig, and WiFi IEEE 802.11ad that utilize high frequencies such as the 60 GHz frequency spectrum for high throughput wireless communications. In the US, the 60 GHz spectrum band may be used for unlicensed short range data links such as data links within a range of 1.7 km, with data throughputs up to 6 Gbits/s. These higher frequencies may provide smaller wavelengths and enable the use of small high gain antennas. However, these higher frequencies may experience high propagation loss.
Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.
A method and/or system for MIMO transmission in a distributed transceiver network, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.
These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.
Certain embodiments of the invention may be found in a method and system for Multi-Input Multi-Output (MIMO) transmission in a distributed transceiver network. In accordance with various exemplary embodiments of the invention, a transmitting device in a network comprises a plurality of distributed transceivers, a central baseband processor and a network management engine. The central baseband processor may generate data streams at baseband. Diversity coding such as, for example, space-time coding, space-time-frequency coding, orthogonal space-time coding, spatial multiplexing, or multi-user MIMO (MU-MIMO) coding may be performed over the generated data streams at baseband. The transmitting device may concurrently transmit each of the coded streams in a same radio frequency (RF) band to a receiving device over the distributed transceivers through associated antennas. The coded data streams in the baseband may be initially converted into different corresponding intermediate frequency (IF) bands and may be further converted into the same RF band for transmission. The network management engine may determine corresponding beam patterns and antenna orientations in the same RF band for the associated antennas of the distributed transceivers of the transmitting device. The coded streams in the same RF band may be concurrently transmitted to the receiving device over the distributed transceivers through associated antennas with the determined corresponding beam patterns and antenna orientations. When needed, the network management engine may identify auxiliary devices that may provide transceivers and antenna beamformers to the transmitting device for sharing. Beam patterns and antenna orientations may be determined for associated antennas of both the distributed transceivers of the transmitting device and the shared transceivers of the auxiliary devices. Each of the coded data streams in the same radio frequency band may be transmitted to the receiving device over the entire collection of the available transceivers for the transmitting device utilizing the determined corresponding beam patterns and antenna orientations for the associated antennas.
The application devices 111-119 may comprise suitable logic, circuitry, code, and/or interfaces that may be operable to communicate voice and data with one to another over wired and/or wireless connections. In an exemplary embodiment of the invention, each of the application devices 111-119 in the communication network 100 may comprise one or more distributed transceivers (DTs) for communication in the communication network 100. For example, distributed transceivers 111a through 119a may be integrated in the application devices 111 through 119, respectively, and utilized for receiving and transmitting signals. Each distributed transceiver may be equipped with an independently configurable antenna or antenna array that is operable to transmit and receive signals over the air. For example, the distributed transceivers 111a each may be equipped with an independently configurable antenna array 111b, and the distributed transceiver 118a, however, may be equipped with a single independently configurable antenna 118b to transmit and receive signals over the air. Depending on device capabilities and user preferences, distributed transceivers such as the distributed transceivers 111a within the application device 111 may comprise radios such as, for example, a millimeter Wave (mmWave) radio, a WLAN radio, a WiMax radio, a Bluetooth radio, a Bluetooth Low Energy (BLE) radio, cellular radios, or other types of radios. In this regard, radios such as mmWave radios may be utilized at very high carrier frequencies for high throughput wireless communications.
In an exemplary operation, the distributed transceivers 111a through 119a in the communication network 100 are physically positioned and oriented at different locations within corresponding application devices such like laptop, TV, gateway and/or set-top box. The distributed transceivers 111a through 119a may be centrally managed by a single network management engine (NME) 120 of the communication network 100. In an exemplary embodiment of the invention, the network management engine 120 may reside within a specific application device in the communication network 100. The network management engine 120 may be centralized as a full software implementation on a separate network microprocessor, for example. An application device in the communication network 100 may act or function as a master application device or an end-user application device. An application device that comprises the network management engine 120 and/or may have access to manage or control the network management engine 120 to dynamically configure and manage operation of the entire distributed transceivers in the communication network 100 is referred to a master application device. An application device that does not comprise the network management engine 120 and/or may have no access to manage or control the network management engine 120 is referred to as an end-user application device.
In some instances, the application device 111 acts as a master application device in the communication network 100. In an exemplary embodiment of the invention, the network management engine 120 in the master application device 111 may be utilized to configure, control, and manage the entire distributed transceivers 111a through 119a in the communication network 100 to optimize network performance. The application devices 111-119 each may operate in a transmission mode or in a receiving mode. In instances where the master application device 111 is transmitting multimedia information such as, for example, images, video, voice, as well as any other form of data to one or more receiving devices such as, for example, the end-user application devices 112-116, the distributed transceivers 111a of the master application device 111 may be managed to transmit data streams to the end-user application devices 112-116 utilizing various transmission schemes such as, for example, multiple-input-multiple-output (MIMO) transmission. In an exemplary embodiment of the invention, transmit beamforming may be utilized by the distributed transceivers 111a for MIMO transmission. In this regard, each of the data streams may be concurrently transmitted in a same RF band over the full collection of the distributed transceivers 111a of the master application device 111 to a single intended receiving device such as the end-user application device 112.
In an exemplary embodiment of the invention, the network management engine 120 in the master application device 111 may be enabled to monitor and collect corresponding communication environment information or characteristics from the end-user application devices 112-116. The collected communication environment information may comprise, for example, propagation environment conditions, link quality, device capabilities, antenna polarization, radiation pattern, antenna spacing, array geometry, device locations, target throughput, and/or application QoS requirements reported. The network management engine 120 may be operable to dynamically configure the distributed transceivers 111a-116a and associated antennas or antenna arrays 111b-116b, and to coordinate and manage the operation of the distributed transceivers 111a-116a and associated antennas or antenna arrays 111b-116b based on the collected communication environment information.
In the collected communication environment information, the link quality may comprise signal-to-noise ratios (SNR) at different transceivers, and/or signal-to-leakage-noise ratios (SLNR) at different devices and transceivers. The application device capabilities may comprise, for example, battery life, a number of transceivers, a number of antennas per transceiver, antenna beamformers, device interface types, processing protocols, service types, service classes and/or service requirements. The interface types for the application devices 111-119 may comprise access interface types such as, for example, Multimedia over Coax Alliance (MoCa), WiFi, Bluetooth, Ethernet, Femtocell, and/or cordless. The processing protocols may comprise service layer protocols, IP layer protocols and link layer protocols, as specified, for example, in the Open Systems Interconnect (OSI) model. The service layer protocols may comprise, for example, secure protocols such as Secure Sockets Layer (SSL) and control protocols such as Spanning Tree Protocol (STP). The IP layer protocols may comprise IP signaling protocols such as, for example, SIP and H.323, and IP media transport protocols such as, for example, TCP, UDP, RTP, RTC and RTCP. The link layer protocols may comprise technology-specific PHY and MAC layer protocols such as, for example, Multimedia over Coax Alliance (MoCa), WiFi, Ethernet, Femtocell, and/or cordless.
Although communication among the application devices 111-119 with one or more distributed transceivers is illustrated in
The master application device 210 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to communicate multimedia information such as, for example, images, video, voice, as well as any other forms of data with one or more application devices such as the end-user application device 220. The master application device 210 may comprise a collection of distributed transceivers 212a through 212e, and a central processor 217 that comprises a central baseband processor 214, a network management engine 216 and a memory 218. In an exemplary embodiment of the invention, each of the collection of distributed transceivers 212a through 212e may be physically positioned and oriented at different locations within an application device such as, for example, a laptop, TV, gateway, and set-top box. In this regard, the collection of distributed transceivers 212a through 212e may be implemented in various ways such as, for example, a single distributed transceiver integrated in a single chip package; multiple silicon dies on one single chip; and multiple distributed transceivers on a single silicon die. Depending on device capabilities and user preferences, the distributed transceivers 212a-212e may be oriented in a fixed direction or multiple different directions. In another exemplary embodiment of the invention, the collection of distributed transceivers 212a-212e may be operable to receive and/or transmit radio frequency signals from and/or to the end-user application device 220 using air interface protocols specified in UMTS, GSM, LTE, WLAN, 60 GHz/mmWave, and/or WiMAX, for example.
The central baseband processor 214 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to perform baseband digital signal processing needed for transmission and receiving operation of the entire collection of distributed transceivers 212a through 212e. For example, the central baseband processor 214 may be operable to perform waveform generation, equalization, and/or packet processing associated with the operation of the collection of distributed transceivers 212a through 212e. In addition, the central baseband processor 214 may be operable to configure, manage and control orientations of the distributed transceivers 212a-212e.
In an exemplary embodiment of the invention, during MIMO transmission to a receiving device such as the end-user application device 220, the central baseband processor 214 of the master application device 210 may generate data streams in a baseband such as a cellular baseband. The central baseband processor 214 may initially convert the data streams in the baseband into corresponding different IF bands. The data streams in the different IF bands may be further converted into a same RF band for transmission over the air. In this regard, the data streams in the same RF band may be transmit processed through transmit beamforming, for example, such that each of the data streams in the same RF band may be concurrently transmitted over the full collection of the distributed transceivers 212a-212e of the master application device 210 to the single end-user application device 220. In this scenario, each full transceiver 212a-212e may act or function as a path of MIMO coding (in this example, forming a MIMO system with 5 transmitter paths). However, unlike traditional MIMO system, there is an additional degree of programmability in this distributed system. In a traditional MIMO system, each branch/antenna/path in transmitter/receiver has an omnidirectional profile. In this system disclosed in the present invention, each path in transmit/receive chain may be configured through its beamforming weights to result in a different pattern. In this mode of operation, the overall system comprises two layers of programming and coding design. The first level involves the MIMO coding design, assuming 5 transmit paths 212a-212e are available. The second level involves beamforming weights for the 5 antenna arrays within 212a-212e transceivers. In some embodiments of the invention, the above two levels of programming may be decoupled and designed independently (for ease of implementation and processing). In this case, the MIMO coding and waveforms may be generated assuming the 5 paths have omnidirectional response (enabling reuse of existing MIMO waveforms and codes). In other embodiments of the invention, these two levels of design/configurations are conducted jointly for a more globally optimal configuration. For example, if an orthogonal space-time block-code (OSTBC) is used as the MIMO coding, the beamforming patterns of 212a-212e are configured such that the effective propagation responses seen by the equivalent MIMO system are as much uncorrelated as possible, hence increasing OSTBC code's performance.
The network management engine 216 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to monitor and collect communication environment information such as, for example, propagation environment conditions, link quality, application device capabilities, antenna polarization, radiation pattern, antenna spacing, array geometry, transmitter/receiver locations, target throughput, and/or application QoS requirements. The network management engine 216 may utilize the collected communication environment information to configure system, network and communication environment conditions as needed. For example, the network management engine 216 may be operable to perform high level system configurations such as, for example, the number of transceivers that are activated, the number of application devices that are being communicated with, adding/dropping application devices to the communication network 100. As shown in
In some embodiments of the invention, a single device, the master application device 210, the end-user application device 220, or the end-user application device 250, for example, may be configured to deploy a number of baseband processors to implement the system and data processing requirements/demands. For example, several baseband processors may be deployed within the single device to generate and/or decode different data streams transmitted/received by several distributed transceivers. In this configuration, the network management engine 216 may also be operable to control and coordinate the operation of the multiple baseband processors within the single device. In this regard, several internal connection topologies may be used or implemented. In some embodiments of the invention, each baseband processor in the single device may be dedicated to a subset of distributed transceivers and either ring/star topologies may be used. In this case, there may be no data transfer between the subsets of distributed transceivers. In another embodiment of the invention, the entire baseband processors and distributed transceivers within the single device may be connected together through a ring topology (using a single cable). In this case, the baseband processors within the single device may be coordinated to share the cable by time-multiplexed at the same IF frequency or frequency-multiplexed at different IF frequencies methods. The baseband processors within the single device may have different power/processing/communication characteristics. In some embodiments of the invention, one or more baseband processors that are most suitable for a mode of operation (e.g., lower power consumption meeting the throughput requirement) may be activated and other baseband processors may be disabled for power saving.
The memory 218 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to store information such as, for example, executable instructions and data that may be utilized by the central baseband processor 214 and/or other associated component units such as the network management engine 216. The memory 218 may comprise RAM, ROM, low latency nonvolatile memory such as, for example, flash memory and/or other suitable electronic data storage.
End-user application devices such as the end-user application device 220 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to communicate multimedia information such as, for example, images, video, voice, as well as any other forms of data with one or more application devices such as the master application device 210. The end-user application device 220 may comprise transceivers 222 through 224, and a central baseband processor 226, and a memory 228. In an exemplary embodiment of the invention, each of the transceivers 222 through 224 may be a normal transceiver (non-distributed transceivers) or a distributed transceiver. The transceivers 222 through 224 may be equipped with antenna arrays 222a-222m, and 224a-224n, respectively. Depending on device capabilities and user preferences, the transceivers 222 through 224 may be oriented in a fixed direction or multiple different directions. The transceivers 222 through 224 may be operable to receive and/or transmit radio frequency signals from and/or to the master application device 210 using air interface protocols specified in UMTS, GSM, LTE, WLAN, 60 GHz/mmWave, and/or WiMAX, for example. In an exemplary embodiment of the invention, the end-user application device 220 may receive a data stream that may be concurrently transmitted by the master application device 210 over the full collection of associated distributed transceivers 212a through 212e.
The central baseband processor 226 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to perform baseband digital signal processing needed for transmission and receiving operation of the entire collection of transceivers 222 through 224. For example, the central baseband processor 226 may be operable to perform waveform generation, equalization, and/or packet processing associated with the operation of the transceivers 222 through 224. In addition, the central baseband processor 226 may be instructed or signaled by the network management engine 216 to configure, manage and control orientations of the transceivers 222 through 224.
The memory 228 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to store information such as, for example, executable instructions and data that may be utilized by the central baseband processor 226 and/or other associated component units such as, for example, weight coefficients for the antenna arrays 222a-222m, and 224a-224n. The memory 228 may comprise RAM, ROM, low latency nonvolatile memory such as, for example, flash memory and/or other suitable electronic data storage.
In an exemplary operation, a wireless link may be established between the master application device 210 and the end-user application device 220 through a reflector 230. U.S. Pat. No. 9,112,648, filed on May 16, 2012 discloses one or more reflectors that may be used to transmit one data stream or multiple data streams, and is hereby incorporated herein by reference in its entirety.
The master application device 210 may communicate multimedia information such as, for example, images, video, voice, as well as any other form of data with the end-user application device 220 utilizing the wireless link. In an exemplary embodiment of the invention, the master application device 210 may transmit the multimedia information to the end-user application device 220 utilizing MIMO transmission. In this regard, the central baseband processor 214 may be operable to generate a plurality of data streams in a baseband such as a cellular baseband. The central baseband processor 214 may encode the data streams in the baseband utilizing various diversity coding algorithms such as, for example, space-time coding or space-time-frequency coding. The coded data streams in the baseband may be initially converted into different corresponding IF bands and then may be further up-converted to the same radio frequency (RF) band. The central baseband processor 214 may be configured to enable transmit beamforming for MIMO transmission such that each of the coded data stream in the same RF band may be concurrently transmitted at different directions or orientations over the full collection of distributed transceivers 212a-212e of the master application device 210 to the single end-user application device 220.
During the MIMO transmission, the master application device 210 may continuously monitor and collect corresponding communication environment information such as, for example, propagation environment conditions, link quality, device capabilities, locations, target throughput, and/or application QoS requirements reported from the end-user application device 220. In this regard, a feedback channel 240 may be utilized to exchange and negotiate system configurations such as, for example, number of transceivers within devices, number of antennas per transceivers, antenna beamformers, the measured channel responses, the sequence of antenna array coefficients being evaluated, and/or device location.
The network management engine 216 may dynamically configure, coordinate and manage the transceivers 212a-212e, 222, and 224, and associated antennas or antenna arrays based on the collected corresponding communication environment information supplied from the end-user application device 220. For example, in instances where the master application device 210 does not have enough communication capabilities, for example, a number of transceivers and beamformers, to support the MIMO transmission, the network management engine 216 may be operable to identify one or more auxiliary devices that may provide available communication capacity to the master application device 210 for sharing. For example, in some instances the end-user application device 250 may be selected by the network management engine 216 as an auxiliary device for the master application device 210. Once the end-user application device 250 agrees to share the associated antennas 252a-252p, for example, with the master application device 210, the network management engine 216 may coordinate and configure the full collection of the transceivers 212a-212e of the master application device 210 and the auxiliary transceiver 252 of the auxiliary end-user application device 250 forming an extended MIMO system at the master application device 210. In this regard, the network management engine 216 and the central baseband processor 214 may enable transmit beamforming over the full collection of the transceivers 212a-212e and 252 in the extended MIMO system at the master application device 210. Each coded data stream may be concurrently transmitted at different directions or orientations over the full collection of the available transceivers 212a-212e and 252 through associated antennas in the same RF band to the single end-user application device 220.
In an exemplary operation, the antenna array 310 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to transmit and receive radio frequency (RF) signals over the air. For reception, the transceiver 300 may pass a receive signal from the antenna array 310 after down-conversion to the central baseband processor 214. For transmission the transceiver 300 may be operable to receive transmit signals or data streams from the central baseband processor 214.
In an exemplary embodiment of the invention, the transmit data streams may be provided from the central baseband processor 214 by encoding corresponding baseband data streams utilizing space-time coding or space-time-frequency coding. The central baseband processor 214 may initially convert the coded data streams in the baseband to different corresponding IF bands. The transmit data streams in the different corresponding IF bands may be fed into the up-converters 340. The up-converters 340 may be operable to convert the transmit data streams in different IF bands to the antenna array 310 in a same RF band for transmission over the air. In an exemplary embodiment of the invention, antennas 310a-310m of the antenna array 310 may be arranged at different directions or orientations based on corresponding communication environment information. The central baseband processor 214 may perform transmit beamforming such that each of the transmit data streams may be concurrently transmitted in the same RF band over the antennas 310a-310m to the single end-user application device 220.
In some embodiments of the invention, the device 210 may be configured to implement a two-layer beamforming scheme as a special case of MIMO processing. In this regard, assume that the distributed transceivers 212a-212e may be configured to certain beam patterns. The central baseband processor 214 then considers each transceiver as a single antenna in forming a second layer of beamforming. For example, the baseband processor 214 and the NME 216 may formulate a standard beamforming problem with 5 available antennas, that is, the distributed transceivers 212a-212e may be treated as an equivalent antenna. The equivalent propagation channel responses corresponding to each transceiver may be measured and collected by the NME 216. Then, the system configuration becomes equivalent to a 5-antenna beamforming system where the channel responses of each antenna is available to the system. Existing beamforming algorithms such as maximal-ratio-combining (MRC), eigenvalue-decomposition (EVD), and singular-value-decomposition (SVD) methods may be used to derive the complex weighting factors used by the baseband processor 214 for scaling the signals delivered to each transceiver.
The multiplexer 350 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to multiplex the transmit signal received from the central baseband processor 214 and the receive signal supplied from the antenna array 310. In this regard, the multiplexer 350 may utilize either time-division-multiplexing or frequency-domain-multiplexing to communicate the transmit signal and the receive signal over the same medium such as a cable.
The antenna array with/without antenna combiner 320 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to scale and/or phase-shift signals before the down-converters 330 and/or signals after the up-converters 340. For example, in transmission operation the signal provided by the up-converters 340 may be phase-shifted by the shifter by different values. The resulting phase-shifted signals may be fed to different antenna elements within the antenna array 310. In another embodiment of the invention, the antenna array 310 may be oriented in a fixed direction or multiple different directions depending on antenna types and user preferences. For example, the antenna array 310 may be implemented as a fixed directional antenna array to provide maximal directionality (with no explicit combiner). The same two modules, that is, the antenna array 310 and the antenna array with/without antenna combiner 320, may be correspondingly utilized in a reception operation for the transceiver 300. In an exemplary embodiment of the invention, the operation of the antenna array with/without antenna combiner 320 may be managed or programmed by the network management engine 216.
The down-converters 330 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to translate a radio frequency (RF) received from the antenna array 310 to an intermediate-frequency (IF) signal during reception. The up-converters 340 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to translate an intermediate-frequency (IF) signal of a corresponding baseband signal supplied from the central baseband processor 214, for example to a RF signal during transmission.
In an exemplary embodiment of the invention, transceiver modules such as the transceiver 300 may be operable to perform a carrier frequency conversion or translation from F_IF (intermediate frequency) to F_RF (radio frequency) and vice versa. As an example, the network management engine 216 may select F_IF in the range of a few GHz, and may select F_RF in the range of 60 GHz, respectively. In a special case the input/output frequency of the transceiver 300 may be the same, that is, no frequency up-conversion is performed. In this special case the transceiver 300 may only perform signal amplification and feeding of signals into the antenna array 310.
The central processor 400 comprises a baseband processor 420, a network management engine 430, down-converters 440, up-converters 446, a multiplexer 450 and a memory 460. The baseband processor 420 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to provide MODEM functionality. In this regard, the central processor 400 may be operable to perform various baseband digital processing such as, for example, MIMO, OFDM, channel coding, HARQ, channel estimation and equalization, Timing/Carrier recovery and synchronization. The network management engine 430 may operate in substantially the same manner as the network management engine 218 in
The down-converters 440 may translate the RF signal into an IF signal. The IF signal may further be translated to a baseband signal to the baseband processor 420, for example. The multiplexer 450 may be responsible for multiplexing receive/transmit signals utilizing either time-division-multiplexing or frequency-domain-multiplexing. The memory 460 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to store information such as executable instructions and data that may be utilized by the baseband processor 420 and/or other associated component units such as the network management engine 430. The memory 360 may comprise RAM, ROM, low latency nonvolatile memory such as, for example, flash memory and/or other suitable electronic data storage.
In an exemplary embodiment of the invention, a different control channel between the baseband processer 420 and each of the distributed transceivers 410a through 410N may be utilized for configuring and managing corresponding transceivers. As shown, control channels 412a through 412N are utilized for configuring and managing the transceivers 410a through 410N, respectively. In an exemplary embodiment of the invention, the distributed transceivers 410a through 410N may operate in various modes such as, for example, spatial diversity mode, frequency diversity mode, multiplexing mode and multiple-input-multiple-output (MIMO) mode. In addition, the distributed transceivers 410a through 410N may be configured to switch between spatial diversity mode, frequency diversity mode, multiplexing mode and multiple-input-multiple-output (MIMO) mode based on corresponding propagation environment conditions, link quality, device capabilities, device locations, usage of resources, resource availability, target throughput, application QoS requirements.
In some embodiments of the invention, the interface between the baseband processor 420 and the distributed transceivers 410a through 410N may be different than an analog IF connection. In an exemplary case, the distributed transceivers 410a through 410N may comprise analog-to-digital-converters (ADCs) and digital-to-analog-converters (DACs). In this case, a transceiver such as the distributed transceiver 410a may receive digital bits from the baseband processors 420 through a digital link and use its internal DAC to generate an analog waveform and then to perform the frequency up-conversion and beamforming steps for transmission. Similarly, a transceiver such as the distributed transceiver 410a may receive an RF waveform, down-convert it, and then use its internal ADC to digitize the waveform and send the digital bits over a digital connection/cable to the baseband processor 420. In other embodiments of the invention, the distributed transceivers 410a through 410N may comprise multiple digital processing blocks or units. In this case, a portion of processing within the baseband processor 420 may be moved (in terms of partitioning) to inside the transceivers boundary. In the above embodiments of the invention, one or more digital connections or interfaces between the baseband processor 420 and the distributed transceivers 410a through 410N may be implemented or deployed. The digital connections/interfaces may comprise Ethernet and various memory bus protocols.
In spatial diversity mode, the central baseband processing 420 may be operable to utilize the distributed transceivers 410a through 410N to establish a spatial diversity link with intended end user device such as the end-user application device 220. For example, only a portion of the distributed transceivers 410a through 410N that may have strong propagation channel responses are activated and other transceivers are switched off for power saving. In another example, the distributed transceivers 410a through 410N may be arranged such that the master application device 210 (the transmitter) with available LOS towards the end-user device 220 (the receiver) may be configured to directly beam towards the receiver. In an exemplary embodiment of the invention, each active distributed transceiver may communicate data streams utilizing the same final carrier frequency.
In frequency diversity mode, the central baseband processing 420 may manage the distributed transceivers 410a through 410N similar to spatial diversity mode except that each active distributed transceiver may utilize a different final carrier frequency if such frequency spectrum channel is available. In multiplexing mode, the central baseband processing 420 may manage the distributed transceivers 410a through 410N in such a way that different streams of data may be transmitted through different sets of the distributed transceivers 410a through 410N. For example, in multiplexing mode, different distributed transceivers of the distributed transceivers 410a through 410N may be dynamically programmed such that each transceiver's maximum pattern gain may be pointing to a different direction or reflector. As the environment changes (and hence location of reflectors and end user unit change), the antenna pattern of the distributed transceivers 410a through 410N may be re-adjusted. In MIMO mode, the central baseband processing 420 may manage the distributed transceivers 410a through 410N in such a way that different streams of data may be transmitted through different sets of the distributed transceivers 410a through 410N to a single receiver device such as the end-user application device 220. In an exemplary embodiment of the invention, the central baseband processor 420 may enable transmit beamforming for MIMO transmission such that each transmit data stream may be concurrently transmitted in the same RF band over the full collection of distributed transceivers 410a through 41N to the single end-user application device 220.
In an exemplary operation, the antenna array 610 may be a configurable phased antenna array. In this regard, the configurable phased antenna array 610 may have various orientations. Accordingly, the configurable phased antenna array 610 may be utilized to generate a steerable beam pattern to maximize coverage. In an exemplary embodiment of the invention, the switcher 620 may be configured to switch on only the transceivers that have strong propagation channel responses and are activated. Other transceivers may be switched off for power saving. For example, in some instances, the system identifies that transceiver 611a of the configurable phased antenna array 610 has the best LOS link to the receiver end (due to blocking objects in the room or nature of reflectors in the room). In this case, only the transceiver 611a may be switched on by the switcher 620 to transmit data to the receiver end and all other transceivers 611b through 711N of the configurable phased antenna array 710 are switched off for power saving.
Beam patterns of the transceiver 611a may be selected or adjusted in various ways such as, for example, by beam pattern hopping, by correlating beam patterns or configurations with the location of the transceiver 611a, and/or by minimizing the power consumption. In an exemplary embodiment of the invention, in MIMO mode, transmit signals in a baseband may be provided from the central baseband processor 214 by encoding corresponding baseband data streams utilizing space-time coding or space-time-frequency coding. The central baseband processor 214 may initially convert the transmit signals in the baseband into different corresponding IF frequency bands. The transmit signals in the different corresponding IF bands may be fed into the up-converters 640. The up-converters 640 may convert the transmit signals in the different corresponding IF bands to the antenna array 610 in the same RF band for transmission over the air. In an exemplary embodiment of the invention, the antennas 611a-611N of the antenna array 610 may be arranged at different directions or orientations and may be weighted utilizing different set of coefficients w1, w2, . . . , wN based on corresponding communication environment information. The central baseband processor 214 may perform transmit beamforming such that each of the transmit signals in the same RF band may be concurrently transmitted at different directions over the antennas 611a-611N to the single end-user application device 220.
The exemplary steps start with step 704, where the central baseband processor 214, which serves or manages the collection of distributed transceivers 212a-121e of the transmitting device (the master application device 210), may be operable to generate a plurality of data streams at baseband for transmission to an intended receiving device such as the end-user application device 220 in the communication network 100. In step 706, the central baseband processor 214 may perform diversity coding such as, for example, space-time coding (STC) or space-time-frequency coding (STFC) over the generated data streams in the baseband. In step 708, the central baseband processor 214 may convert the resulting coded data streams into different corresponding IF frequency bands to be fed into the up-converters 446, for example. The up-converters 446 may convert the coded data streams in the different corresponding IF bands into the same RF band for transmission over the air.
In step 710, it may be determined whether the master application device 210 comprises sufficient number of transceivers and antenna beamformers to support the MIMO transmission of the coded data streams in the different corresponding IF bands. In instances where the master application device 210 does not comprise sufficient number of transceivers and antenna beamformers for the MIMO transmission of the coded data streams in the different corresponding IF bands, then in step 712, the network management engine 216 may identify one or more auxiliary devices that may provide desired communication capacities such as, for example, a number of transceivers and antenna beamformers available to the master application device 210 for sharing. In step 714, the master application device 210 may negotiate via the network management engine 216 with each of the auxiliary devices such as the end-user application device 250 for sharing the available number of transceivers and antenna beamformers of the end-user application device 250.
In step 716, the network management engine 216 may determine beam patterns and antenna orientations of associated antennas or antenna arrays of the entire collection of available transceivers for the master application device 210 (the transmitting device) for transmission to the end-user application device 220 based on corresponding communication environment information. The collection of available transceivers available for the master application device 210 comprises both the distributed transceivers 212a-121e of the master application device 210 and the auxiliary transceivers of the identified auxiliary devices. In step 718, the master application device 210 may be enabled to concurrently transmit each of the coded data streams to the end-user application device 220 in the same RF band over the full collection of the available transceivers for the master application device 210 through the associated antenna arrays with the determined beam patterns and antenna orientations. The exemplary steps may continue in step 724, where the network management engine 216 may monitor and collect corresponding communication environment information such as, for example, propagation environment conditions, link quality, device capabilities, device locations, target throughput, and/or application QoS requirements from the end-user application device 220. The exemplary steps may return to step 710.
In step 710, in instances where the master application device 210 comprises a sufficient number of transceivers and antenna beamformers for the MIMO transmission of the coded data streams in the different corresponding IF bands, the exemplary steps may continue in step 720, where the network management engine 216 may determine beam patterns and antenna orientations for associated antenna arrays of the distributed transceivers of the master application device 210 for transmission to the end-user application device 220 based on corresponding communication environment information. In step 724, the master application device 210 may be enabled to concurrently transmit each of the coded data streams in the same RF band to the end-user application device 220 over the full collection of the distributed transceivers of the master application device 210 through the associated antenna arrays with the corresponding determined beam patterns and antenna orientations. The exemplary steps continue in step 724.
Aspects of a method and system for MIMO transmission in a distributed transceiver network are provided. In accordance with various exemplary embodiments of the invention, as described with respect to
The master application device 210 may be enabled to concurrently transmit each of the resulting coded streams in a same radio frequency band over the plurality of distributed transceivers 212a-212e through associated antennas to a receiving device such as the end-user application device 220. The central baseband processor 214 may convert the coded data streams in the baseband into different corresponding IF bands to be fed into the up-converters 640, for example. The up-converters 640 may further convert the coded data streams in the different corresponding IF bands into the same radio frequency band for transmission over the air. The network management engine 216 may determine corresponding beam patterns and antenna orientations in the same radio frequency band for the associated antennas of the plurality of distributed transceivers 212a-212e of the master application device 210.
The master application device 210 may be enabled to concurrently transmit each of the coded streams in the same radio frequency band to the end-user application device 220 over the plurality of distributed transceivers 212a-212e through associated antennas with the determined corresponding beam patterns and antenna orientations. In some instances, the master application device 210 does not comprise sufficient number of transceivers and antenna beamformers to support the MIMO transmission of the coded data streams. In this regard, the network management engine 216 may identify one or more auxiliary devices that may provide the desired number of transceivers and antenna beamformers available for sharing. The master application device 210 may negotiate, via the network management engine 216, with each of the identified auxiliary devices such as the end-user application device 250 for sharing the available number of transceivers and antenna beamformers of the end-user application device 250. The network management engine 216 may determine corresponding beam patterns and antenna orientations for associated antennas of the transceivers available for the master application device 210. The master application device 210 may be enabled to concurrently transmit each of the coded data streams to the end-user application device 220 in the same radio frequency band over the full collection of the available transceivers for the master application device 210 through the associated antennas with the determined corresponding beam patterns and antenna orientations. The network management engine 216 may monitor and collect corresponding communication environment information during the concurrent transmission.
In some embodiments of the invention, the antenna elements within the distributed transceiver 222-224 may be used as independent antenna elements for MIMO implementation. In this case, all the antenna elements 222a-222m and 224a-224n may be considered as independent antennas available for MIMO implementation and processing by the baseband processor 226. This embodiment may enable a super-MIMO configuration that offers a larger MIMO size (e.g., equal to sum of number of antennas in all the transceivers). Subsequently, MIMO techniques such as space-time coding (STC), beamforming, or space-time-frequency coding (STFC) may be applied to the larger MIMO dimensions. In this regard, multiple data streams may be needed to be transported to each transceiver module to represent the MIMO coded data streams assigned to each antenna within the transceiver. This may be supported by using multiple cables between the baseband processor 226 and each of the transceivers or using a single cable and multiplexing different data streams over different IF frequencies.
Other embodiments of the invention may provide a non-transitory computer readable medium and/or storage medium, and/or a non-transitory machine readable medium and/or storage medium, having stored thereon, a machine code and/or a computer program having at least one code section executable by a machine and/or a computer, thereby causing the machine and/or computer to perform the steps as described herein for MIMO transmission in a distributed transceiver network.
Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.
This patent application is a continuation application of U.S. patent application Ser. No. 16/101,044, filed on Aug. 10, 2018, published as U.S. Patent Publication 2019-0089501. U.S. patent application Ser. No. 16/101,044 is a continuation application of U.S. patent application Ser. No. 15/595,940, filed on May 15, 2017, issued as U.S. Pat. No. 10,069,608. U.S. patent application Ser. No. 15/595,940 is a continuation application of U.S. patent application Ser. No. 14/980,281, filed Dec. 28, 2015, issued as U.S. Pat. No. 9,686,060. U.S. patent application Ser. No. 14/980,281 is a continuation application of U.S. patent application Ser. No. 13/473,113, filed May 16, 2012, issued as U.S. Pat. No. 9,225,482. U.S. patent application Ser. No. 13/473,113 makes reference to, claims priority to and claims benefit from U.S. Provisional Patent Application Ser. No. 61/548,201 filed on Oct. 17, 2011. U.S. patent application Ser. No. 16/101,044 published as U.S. Patent Publication 2019-0089501; U.S. patent application Ser. No. 15/595,940, issued as U.S. Pat. No. 10,069,608; U.S. patent application Ser. No. 14/980,281, issued as U.S. Pat. No. 9,686,060; and U.S. patent application Ser. No. 13/473,113, issued as U.S. Pat. No. 9,225,482 are incorporated herein by reference. This application makes reference to: U.S. application Ser. No. 13/473,096 filed on May 16, 2012; U.S. application Ser. No. 13/473,144 filed on May 16, 2012; U.S. application Ser. No. 13/473,105 filed on May 16, 2012; U.S. application Ser. No. 13/473,160 filed on May 16, 2012; U.S. application Ser. No. 13/473,180 filed on May 16, 2012; and U.S. application Ser. No. 13/473,083 filed on May 16, 2012. Each of the above stated applications is hereby incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
3618097 | Mcleod, Jr. | Nov 1971 | A |
3835469 | Chen et al. | Sep 1974 | A |
4799062 | Sanderford et al. | Jan 1989 | A |
5473602 | McKenna et al. | Dec 1995 | A |
5479651 | Nakaguchi | Dec 1995 | A |
5525990 | Lewis | Jun 1996 | A |
5561850 | Makitalo et al. | Oct 1996 | A |
5598173 | Forti et al. | Jan 1997 | A |
5666124 | Chethik et al. | Sep 1997 | A |
5771017 | Dean et al. | Jun 1998 | A |
5883602 | Volman | Mar 1999 | A |
5905473 | Taenzer | May 1999 | A |
5936577 | Shoki et al. | Aug 1999 | A |
5940033 | Locher et al. | Aug 1999 | A |
6018316 | Rudish et al. | Jan 2000 | A |
6307502 | Marti-Canales et al. | Oct 2001 | B1 |
6405018 | Reudink et al. | Jun 2002 | B1 |
6433920 | Welch et al. | Aug 2002 | B1 |
6456252 | Goyette | Sep 2002 | B1 |
6487417 | Rossoni et al. | Nov 2002 | B1 |
6577631 | Keenan et al. | Jun 2003 | B1 |
6600776 | Alamouti et al. | Jul 2003 | B1 |
6718159 | Sato | Apr 2004 | B1 |
6802035 | Catreux et al. | Oct 2004 | B2 |
6804491 | Uesugi | Oct 2004 | B1 |
6992622 | Chiang et al. | Jan 2006 | B1 |
7020482 | Medvedev et al. | Mar 2006 | B2 |
7058367 | Luo et al. | Jun 2006 | B1 |
7187949 | Chang et al. | Mar 2007 | B2 |
7206294 | Garahi et al. | Apr 2007 | B2 |
7248217 | Mani et al. | Jul 2007 | B2 |
7248841 | Agee et al. | Jul 2007 | B2 |
7260141 | Bierly et al. | Aug 2007 | B2 |
7333455 | Bolt et al. | Feb 2008 | B1 |
7339979 | Kelkar | Mar 2008 | B1 |
7363058 | Gustaf | Apr 2008 | B2 |
7424225 | Elliott | Sep 2008 | B1 |
7480486 | Oh et al. | Jan 2009 | B1 |
7574236 | Mansour | Aug 2009 | B1 |
7636573 | Walton et al. | Dec 2009 | B2 |
7688909 | Tsutsui | Mar 2010 | B2 |
7689216 | Wandel | Mar 2010 | B2 |
7710319 | Nassiri-Toussi et al. | May 2010 | B2 |
7890114 | Braun et al. | Feb 2011 | B2 |
7904117 | Doan et al. | Mar 2011 | B2 |
7911985 | Proctor, Jr. et al. | Mar 2011 | B2 |
7920889 | Hoshino et al. | Apr 2011 | B2 |
7986742 | Ketchum et al. | Jul 2011 | B2 |
8014366 | Wax et al. | Sep 2011 | B2 |
8098752 | Hwang et al. | Jan 2012 | B2 |
8121235 | Sun et al. | Feb 2012 | B1 |
8126408 | Ahrony et al. | Feb 2012 | B2 |
8140122 | Park et al. | Mar 2012 | B2 |
8160601 | Veselinovic et al. | Apr 2012 | B2 |
8175184 | Kim et al. | May 2012 | B2 |
8190102 | Rofougaran | May 2012 | B2 |
8203978 | Rodney et al. | Jun 2012 | B2 |
8228188 | Key et al. | Jul 2012 | B2 |
8279132 | Jung et al. | Oct 2012 | B2 |
8280445 | Yong et al. | Oct 2012 | B2 |
8314736 | Moshfeghi | Nov 2012 | B2 |
8320304 | Deb et al. | Nov 2012 | B2 |
8364188 | Deb et al. | Jan 2013 | B2 |
8369791 | Hafeez | Feb 2013 | B2 |
8385305 | Negus et al. | Feb 2013 | B1 |
8385452 | Gorokhov | Feb 2013 | B2 |
8396157 | Li et al. | Mar 2013 | B2 |
8457798 | Hackett | Jun 2013 | B2 |
8462047 | Ai et al. | Jun 2013 | B1 |
8482462 | Komijani et al. | Jul 2013 | B2 |
8570988 | Wallace et al. | Oct 2013 | B2 |
8588193 | Ho et al. | Nov 2013 | B1 |
8620301 | Hessel | Dec 2013 | B1 |
8644262 | Sun et al. | Feb 2014 | B1 |
8654815 | Forenza et al. | Feb 2014 | B1 |
8744513 | Chen et al. | Jun 2014 | B2 |
8750264 | Shatti | Jun 2014 | B2 |
8780943 | Moshfeghi | Jul 2014 | B2 |
8787469 | Kim et al. | Jul 2014 | B2 |
8817678 | Moshfeghi | Aug 2014 | B2 |
8854255 | Ehret | Oct 2014 | B1 |
8885628 | Palanki et al. | Nov 2014 | B2 |
9037094 | Moshfeghi | May 2015 | B2 |
9065515 | Pezennec et al. | Jun 2015 | B2 |
9112648 | Moshfeghi | Aug 2015 | B2 |
9185601 | Frerking et al. | Nov 2015 | B2 |
9197982 | Moshfeghi | Nov 2015 | B2 |
9225482 | Moshfeghi | Dec 2015 | B2 |
9226092 | Moshfeghi | Dec 2015 | B2 |
9252908 | Branlund | Feb 2016 | B1 |
9253587 | Moshfeghi | Feb 2016 | B2 |
9438389 | Moshfeghi et al. | Sep 2016 | B2 |
9456354 | Branlund | Sep 2016 | B2 |
9548805 | Moshfeghi et al. | Jan 2017 | B2 |
9602257 | Moshfeghi et al. | Mar 2017 | B2 |
9660777 | Moshfeghi et al. | May 2017 | B2 |
9680554 | Moshfeghi et al. | Jun 2017 | B2 |
9686060 | Moshfeghi | Jun 2017 | B2 |
9698948 | Moshfeghi | Jul 2017 | B2 |
9736637 | Larsen et al. | Aug 2017 | B2 |
9780928 | Moshfeghi et al. | Oct 2017 | B2 |
9787103 | Leabman et al. | Oct 2017 | B1 |
9829563 | Xiao et al. | Nov 2017 | B2 |
9923620 | Moshfeghi et al. | Mar 2018 | B2 |
10020861 | Moshfeghi et al. | Jul 2018 | B2 |
10069555 | Islam et al. | Sep 2018 | B2 |
10069608 | Moshfeghi et al. | Sep 2018 | B2 |
10084576 | Moshfeghi et al. | Sep 2018 | B2 |
10090887 | Rofougaran et al. | Oct 2018 | B1 |
10103853 | Moshfeghi | Oct 2018 | B2 |
10199717 | Rofougaran et al. | Feb 2019 | B2 |
10277370 | Moshfeghi | Apr 2019 | B2 |
10320090 | Zou et al. | Jun 2019 | B2 |
10348371 | Rofougaran et al. | Jul 2019 | B2 |
10560179 | Gharavi et al. | Feb 2020 | B2 |
10587313 | Yoon et al. | Mar 2020 | B2 |
10666326 | Rofougaran et al. | May 2020 | B2 |
20020034958 | Oberschmidt et al. | Mar 2002 | A1 |
20020132600 | Rudrapatna | Sep 2002 | A1 |
20020193074 | Squibbs | Dec 2002 | A1 |
20020196186 | Holt | Dec 2002 | A1 |
20030012208 | Bernheim et al. | Jan 2003 | A1 |
20030090418 | Howell | May 2003 | A1 |
20030125040 | Walton et al. | Jul 2003 | A1 |
20030129989 | Gholmieh et al. | Jul 2003 | A1 |
20030236109 | Nagata | Dec 2003 | A1 |
20040077354 | Jason et al. | Apr 2004 | A1 |
20040077379 | Smith et al. | Apr 2004 | A1 |
20040082356 | Walton et al. | Apr 2004 | A1 |
20040095907 | Agee et al. | May 2004 | A1 |
20040110469 | Judd et al. | Jun 2004 | A1 |
20040116129 | Wilson | Jun 2004 | A1 |
20040127174 | Frank et al. | Jul 2004 | A1 |
20040166808 | Hasegawa et al. | Aug 2004 | A1 |
20040204114 | Brennan et al. | Oct 2004 | A1 |
20050048964 | Cohen et al. | Mar 2005 | A1 |
20050069252 | Hwang et al. | Mar 2005 | A1 |
20050088358 | Larry et al. | Apr 2005 | A1 |
20050134517 | Gottl | Jun 2005 | A1 |
20050136943 | Banerjee et al. | Jun 2005 | A1 |
20050181755 | Hoshino et al. | Aug 2005 | A1 |
20050232216 | Webster et al. | Oct 2005 | A1 |
20050237971 | Skraparlis | Oct 2005 | A1 |
20050243756 | Cleveland et al. | Nov 2005 | A1 |
20050270227 | Stephens | Dec 2005 | A1 |
20060025178 | Tao et al. | Feb 2006 | A1 |
20060063494 | Zhang et al. | Mar 2006 | A1 |
20060121946 | Walton et al. | Jun 2006 | A1 |
20060205342 | McKay et al. | Sep 2006 | A1 |
20060246922 | Gasbarro et al. | Nov 2006 | A1 |
20060267839 | Vaskelainen et al. | Nov 2006 | A1 |
20070001924 | Hirabayashi | Jan 2007 | A1 |
20070040025 | Goel et al. | Feb 2007 | A1 |
20070052519 | Talty et al. | Mar 2007 | A1 |
20070066254 | Tsuchie et al. | Mar 2007 | A1 |
20070093270 | Lagnado | Apr 2007 | A1 |
20070100548 | Small | May 2007 | A1 |
20070115800 | Fonseka et al. | May 2007 | A1 |
20070116012 | Chang et al. | May 2007 | A1 |
20070127360 | Song et al. | Jun 2007 | A1 |
20070160014 | Larsson | Jul 2007 | A1 |
20070280310 | Muenter et al. | Dec 2007 | A1 |
20080025208 | Chan | Jan 2008 | A1 |
20080026763 | Rensburg et al. | Jan 2008 | A1 |
20080076370 | Kotecha et al. | Mar 2008 | A1 |
20080117961 | Han et al. | May 2008 | A1 |
20080166975 | Kim et al. | Jul 2008 | A1 |
20080167049 | Karr et al. | Jul 2008 | A1 |
20080212582 | Zwart et al. | Sep 2008 | A1 |
20080225758 | Proctor et al. | Sep 2008 | A1 |
20080258993 | Gummalla et al. | Oct 2008 | A1 |
20080261509 | Sen | Oct 2008 | A1 |
20080303701 | Zhang et al. | Dec 2008 | A1 |
20080305820 | Sadiq et al. | Dec 2008 | A1 |
20080309555 | Fan et al. | Dec 2008 | A1 |
20080315944 | Brown | Dec 2008 | A1 |
20090009392 | Jacomb-Hood et al. | Jan 2009 | A1 |
20090010215 | Kim et al. | Jan 2009 | A1 |
20090028120 | Lee | Jan 2009 | A1 |
20090029645 | Leroudier | Jan 2009 | A1 |
20090093265 | Kimura et al. | Apr 2009 | A1 |
20090136227 | Lambert | May 2009 | A1 |
20090156227 | Frerking | Jun 2009 | A1 |
20090161235 | Border et al. | Jun 2009 | A1 |
20090175214 | Sfar et al. | Jul 2009 | A1 |
20090195455 | Kim et al. | Aug 2009 | A1 |
20090224137 | Hoermann | Sep 2009 | A1 |
20090233545 | Sutskover et al. | Sep 2009 | A1 |
20090296846 | Maru | Dec 2009 | A1 |
20090325479 | Chakrabarti et al. | Dec 2009 | A1 |
20100042881 | Wong | Feb 2010 | A1 |
20100046655 | Lee et al. | Feb 2010 | A1 |
20100080197 | Kanellakis et al. | Apr 2010 | A1 |
20100090898 | Gallagher et al. | Apr 2010 | A1 |
20100105403 | Lennartson et al. | Apr 2010 | A1 |
20100117890 | Vook et al. | May 2010 | A1 |
20100124895 | Martin et al. | May 2010 | A1 |
20100136922 | Rofougaran | Jun 2010 | A1 |
20100149039 | Komijani et al. | Jun 2010 | A1 |
20100167639 | Ranson et al. | Jul 2010 | A1 |
20100172309 | Forenza | Jul 2010 | A1 |
20100208776 | Song et al. | Aug 2010 | A1 |
20100220012 | Reede | Sep 2010 | A1 |
20100265925 | Liu et al. | Oct 2010 | A1 |
20100266061 | Cheng et al. | Oct 2010 | A1 |
20100267415 | Kakitsu et al. | Oct 2010 | A1 |
20100273504 | Bull et al. | Oct 2010 | A1 |
20100284446 | Mu et al. | Nov 2010 | A1 |
20100291918 | Suzuki et al. | Nov 2010 | A1 |
20100304680 | Kuffner et al. | Dec 2010 | A1 |
20100304770 | Wietfeldt | Dec 2010 | A1 |
20100328157 | Culkin et al. | Dec 2010 | A1 |
20110002410 | Forenza et al. | Jan 2011 | A1 |
20110003610 | Key et al. | Jan 2011 | A1 |
20110045764 | Maruyama et al. | Feb 2011 | A1 |
20110063181 | Walker | Mar 2011 | A1 |
20110069773 | Doron et al. | Mar 2011 | A1 |
20110081875 | Imamura et al. | Apr 2011 | A1 |
20110105032 | Maruhashi et al. | May 2011 | A1 |
20110105167 | Pan et al. | May 2011 | A1 |
20110136478 | Trigui | Jun 2011 | A1 |
20110140954 | Fortuny-Guasch | Jun 2011 | A1 |
20110142104 | Coldrey et al. | Jun 2011 | A1 |
20110149835 | Shimada et al. | Jun 2011 | A1 |
20110164510 | Zheng et al. | Jul 2011 | A1 |
20110190005 | Cheon et al. | Aug 2011 | A1 |
20110194504 | Gorokhov et al. | Aug 2011 | A1 |
20110212684 | Nam et al. | Sep 2011 | A1 |
20110222616 | Jiang et al. | Sep 2011 | A1 |
20110268037 | Fujimoto | Nov 2011 | A1 |
20110299441 | Petrovic et al. | Dec 2011 | A1 |
20120002742 | Cheng | Jan 2012 | A1 |
20120015603 | Proctor et al. | Jan 2012 | A1 |
20120034924 | Kalhan | Feb 2012 | A1 |
20120057508 | Moshfeghi | Mar 2012 | A1 |
20120082070 | Hart et al. | Apr 2012 | A1 |
20120082072 | Shen | Apr 2012 | A1 |
20120083207 | Rofougaran et al. | Apr 2012 | A1 |
20120083223 | Li et al. | Apr 2012 | A1 |
20120083225 | Rofougaran et al. | Apr 2012 | A1 |
20120083233 | Rofougaran et al. | Apr 2012 | A1 |
20120083306 | Rofougaran et al. | Apr 2012 | A1 |
20120093209 | Schmidt et al. | Apr 2012 | A1 |
20120120884 | Yu et al. | May 2012 | A1 |
20120129543 | Patel et al. | May 2012 | A1 |
20120131650 | Gutt et al. | May 2012 | A1 |
20120149300 | Forster | Jun 2012 | A1 |
20120184203 | Tulino et al. | Jul 2012 | A1 |
20120184219 | Richardson et al. | Jul 2012 | A1 |
20120194385 | Schmidt et al. | Aug 2012 | A1 |
20120206299 | Valdes-Garcia | Aug 2012 | A1 |
20120224651 | Murakami et al. | Sep 2012 | A1 |
20120230274 | Xiao et al. | Sep 2012 | A1 |
20120238202 | Kim et al. | Sep 2012 | A1 |
20120250659 | Sambhwani | Oct 2012 | A1 |
20120257516 | Pazhyannur et al. | Oct 2012 | A1 |
20120259547 | Morlock et al. | Oct 2012 | A1 |
20120314570 | Forenza et al. | Dec 2012 | A1 |
20130027240 | Chowdhury | Jan 2013 | A1 |
20130027250 | Chen | Jan 2013 | A1 |
20130039342 | Kazmi | Feb 2013 | A1 |
20130040558 | Kazmi | Feb 2013 | A1 |
20130044028 | Lea et al. | Feb 2013 | A1 |
20130057447 | Pivit et al. | Mar 2013 | A1 |
20130072112 | Gunnarsson et al. | Mar 2013 | A1 |
20130072113 | Lee et al. | Mar 2013 | A1 |
20130089123 | Rahul et al. | Apr 2013 | A1 |
20130094439 | Moshfeghi | Apr 2013 | A1 |
20130094440 | Moshfeghi | Apr 2013 | A1 |
20130094522 | Moshfeghi | Apr 2013 | A1 |
20130094544 | Moshfeghi | Apr 2013 | A1 |
20130095747 | Moshfeghi | Apr 2013 | A1 |
20130095770 | Moshfeghi | Apr 2013 | A1 |
20130095874 | Moshfeghi et al. | Apr 2013 | A1 |
20130114468 | Hui et al. | May 2013 | A1 |
20130155891 | Dinan | Jun 2013 | A1 |
20130272220 | Li et al. | Oct 2013 | A1 |
20130272437 | Eidson et al. | Oct 2013 | A1 |
20130286962 | Heath, Jr. et al. | Oct 2013 | A1 |
20130287139 | Zhu et al. | Oct 2013 | A1 |
20130322561 | Abreu et al. | Dec 2013 | A1 |
20130324055 | Kludt et al. | Dec 2013 | A1 |
20130343235 | Khan | Dec 2013 | A1 |
20140003338 | Rahul et al. | Jan 2014 | A1 |
20140010319 | Baik et al. | Jan 2014 | A1 |
20140016573 | Nuggehalli et al. | Jan 2014 | A1 |
20140035731 | Chan et al. | Feb 2014 | A1 |
20140044041 | Moshfeghi | Feb 2014 | A1 |
20140044042 | Moshfeghi | Feb 2014 | A1 |
20140044043 | Moshfeghi et al. | Feb 2014 | A1 |
20140045478 | Moshfeghi | Feb 2014 | A1 |
20140045541 | Moshfeghi et al. | Feb 2014 | A1 |
20140072078 | Sergeyev et al. | Mar 2014 | A1 |
20140077875 | Wang et al. | Mar 2014 | A1 |
20140079165 | Kludt et al. | Mar 2014 | A1 |
20140086191 | Berntsen et al. | Mar 2014 | A1 |
20140104124 | Chernokalov et al. | Apr 2014 | A1 |
20140125539 | Katipally et al. | May 2014 | A1 |
20140133435 | Forenza et al. | May 2014 | A1 |
20140161018 | Chang et al. | Jun 2014 | A1 |
20140198696 | Li et al. | Jul 2014 | A1 |
20140241296 | Shattil | Aug 2014 | A1 |
20140266866 | Swirhun et al. | Sep 2014 | A1 |
20150003307 | Moshfeghi et al. | Jan 2015 | A1 |
20150011160 | Jurgovan et al. | Jan 2015 | A1 |
20150031407 | Moshfeghi | Jan 2015 | A1 |
20150042744 | Ralston et al. | Feb 2015 | A1 |
20150091706 | Chemishkian et al. | Apr 2015 | A1 |
20150123496 | Leabman et al. | May 2015 | A1 |
20150229133 | Reynolds et al. | Aug 2015 | A1 |
20150241020 | Lee et al. | Aug 2015 | A1 |
20150296344 | Trojer et al. | Oct 2015 | A1 |
20150303950 | Shattil | Oct 2015 | A1 |
20150318897 | Hyde et al. | Nov 2015 | A1 |
20150318905 | Moshfeghi et al. | Nov 2015 | A1 |
20150341098 | Angeletti et al. | Nov 2015 | A1 |
20160014613 | Ponnampalam et al. | Jan 2016 | A1 |
20160043838 | Moshfeghi et al. | Feb 2016 | A1 |
20160054440 | Younis | Feb 2016 | A1 |
20160094092 | Davlantes et al. | Mar 2016 | A1 |
20160094318 | Shattil | Mar 2016 | A1 |
20160142114 | Moshfeghi et al. | May 2016 | A1 |
20160192400 | Sohn et al. | Jun 2016 | A1 |
20160197665 | Moshfeghi et al. | Jul 2016 | A1 |
20160203347 | Bartholomew et al. | Jul 2016 | A1 |
20160211905 | Moshfeghi et al. | Jul 2016 | A1 |
20160219567 | Gil et al. | Jul 2016 | A1 |
20160285481 | Cohen | Sep 2016 | A1 |
20170026218 | Shattil | Jan 2017 | A1 |
20170062944 | Zimmerman et al. | Mar 2017 | A1 |
20170078897 | Duan et al. | Mar 2017 | A1 |
20170126374 | Moshfeghi et al. | May 2017 | A1 |
20170156069 | Moshfeghi et al. | Jun 2017 | A1 |
20170201437 | Balakrishnan et al. | Jul 2017 | A1 |
20170212208 | Baek et al. | Jul 2017 | A1 |
20170230099 | Moshfeghi et al. | Aug 2017 | A1 |
20170237290 | Bakker et al. | Aug 2017 | A1 |
20170257155 | Liang et al. | Sep 2017 | A1 |
20170264014 | Le-Ngoc | Sep 2017 | A1 |
20170279573 | Moshfeghi et al. | Sep 2017 | A1 |
20170288727 | Rappaport | Oct 2017 | A1 |
20170317734 | Moshfeghi | Nov 2017 | A1 |
20170317801 | Moshfeghi et al. | Nov 2017 | A1 |
20170324480 | Elmirghani et al. | Nov 2017 | A1 |
20170332249 | Guey et al. | Nov 2017 | A1 |
20170338921 | Moshfeghi | Nov 2017 | A1 |
20170339625 | Stapleton | Nov 2017 | A1 |
20170353338 | Amadjikpe et al. | Dec 2017 | A1 |
20180026586 | Carbone et al. | Jan 2018 | A1 |
20180027471 | Zhang et al. | Jan 2018 | A1 |
20180041270 | Buer et al. | Feb 2018 | A1 |
20180048390 | Palmer et al. | Feb 2018 | A1 |
20180063139 | Day et al. | Mar 2018 | A1 |
20180090992 | Shrivastava et al. | Mar 2018 | A1 |
20180091270 | Moshfeghi | Mar 2018 | A1 |
20180109303 | Yoo et al. | Apr 2018 | A1 |
20180115305 | Islam et al. | Apr 2018 | A1 |
20180176799 | Lange et al. | Jun 2018 | A1 |
20180183152 | Turpin et al. | Jun 2018 | A1 |
20180220416 | Islam et al. | Aug 2018 | A1 |
20180234158 | Moshfeghi | Aug 2018 | A1 |
20190089434 | Rainish et al. | Mar 2019 | A1 |
20190123866 | Moshfeghi | Apr 2019 | A1 |
20190230626 | Rune et al. | Jul 2019 | A1 |
20190319754 | Moshfeghi | Oct 2019 | A1 |
20190319755 | Moshfeghi | Oct 2019 | A1 |
20190319756 | Moshfeghi | Oct 2019 | A1 |
20200076491 | Zhang et al. | Mar 2020 | A1 |
20200145079 | Marinier et al. | May 2020 | A1 |
20200204249 | Pyun | Jun 2020 | A1 |
20200412519 | Krishnaswamy et al. | Dec 2020 | A1 |
Number | Date | Country |
---|---|---|
1890441 | Feb 2008 | EP |
1890441 | Mar 2013 | EP |
2008027531 | Mar 2008 | WO |
2008027531 | Dec 2008 | WO |
2012055468 | May 2012 | WO |
2013058998 | Apr 2013 | WO |
2013058999 | Apr 2013 | WO |
2016115545 | Jul 2016 | WO |
Entry |
---|
Non-Final Office Action for U.S. Appl. No. 16/016,619 dated Sep. 25, 2018. |
Baggett, Benjamin M.W. Optimization of Aperiodically Spaced Phased Arrays for Wideband Applications. MS Thesis. Virginia Polytechnic Institute and State University, 2011. pp. 1-137. |
Corrected Notice of Allowability for U.S. Appl. No. 15/904,521 dated May 6, 2019. |
Corrected Notice of Allowance for U.S. Appl. 16/031,007 dated Jul. 8, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 15/607,743 dated May 10, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 15/904,521 dated Jun. 21, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 15/904,521 dated May 10, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 13/473,180 dated Jun. 11, 2014. |
Corrected Notice of Allowance for U.S. Appl. No. 15/904,521. |
Corrected Notice of Allowance for U.S. Appl. No. 16/031,007 dated Aug. 5, 2019. |
Corrected Notice of Allowance in U.S. Appl. No. 15/607,743 dated Apr. 3, 2019. |
Corrected Notice of Allowance in U.S. Appl. No. 15/835,971 dated Jul. 23, 2018. |
Dennis R Morgan et al., “A same-frequency cellular repeater using adaptive feedback cancellation,” Global Communications Conference (GLOBECOM), 2012 IEEE, IEEE, (2012) XP032375270, pp. 3825-3830, 2012. |
Ex Parte Quayle Action for U.S. Appl. No. 16/032,668 dated Jul. 10, 2019. |
Examiner's Answer to Appeal Brief for U.S. Appl. No. 13/473,144 dated Jul. 26, 2017. |
Examiner's Answer to Appeal Brief for U.S. Appl. No. 13/473,160 dated Dec. 24, 2015. |
Examiner's Answer to Appeal Brief for U.S. Appl. No. 13/919,932 dated Jan. 10, 2017. |
Final Office Action for U.S. Appl. No. 13/473,144 dated Jul. 28, 2016. |
Final Office Action for U.S. Appl. No. 13/473,144 dated Aug. 14, 2014. |
Final Office Action for U.S. Appl. No. 13/919,932 dated Oct. 23, 2015. |
Final Office Action for U.S. Appl. No. 13/919,972 dated Jan. 21, 2016. |
Final Office Action for U.S. Appl. No. 14/940,130 dated Oct. 14, 2016. |
Final Office Action for U.S. Appl. No. dated Oct. 22, 2014. |
International Preliminary Report on Patentability for International Patent PCT/US2012/058839, 5 pages, dated Apr. 22, 2014. |
International Preliminary Report on Patentability for International Patent PCT/US2012/058839, dated Apr. 22, 2014. |
International Preliminary Report on Patentability for International Patent PCT/US2012/058842, 5 pages, dated Apr. 22, 2014. |
International Search Report and the Written Opinion of the International Searching Authority in International application No. PCT/US12/58842, 6 pages, dated Jan. 4, 2013. |
International Search Report and the Written Opinion of the International Searching Authority in International application No. PCT/US12/58839, 6 pages, dated Apr. 4, 2013. |
International Search Report in PCT/US2018/064184 dated Jul. 1, 2019. |
Invitation to Pay Additional Fees and, Where Applicable, Protest Fee, with Partial Search Report for PCT Appl No. PCT/US2018/064184 dated Apr. 10, 2019. |
K. Flan and K. Huang, “Wirelessly Powered Backscatter Communication networks: Modeling, Coverage and Capacity,” Apr. 9, 2016, Arxiv.com. |
List of References cited by Applicant and considered by Applicant for U.S. Appl. No. 14/325,218 dated Apr. 21, 2017. |
Non-Final Office Action for U.S. Appl. No. 13/473,083 dated Mar. 3, 2014. |
Non-Final Office Action for U.S. Appl. No. 13/473,096 dated Apr. 23, 2014. |
Non-Final Office Action for U.S. Appl. No. 13/473,096 dated Dec. 9, 2013. |
Non-Final Office Action for U.S. Appl. No. 13/473,096 dated Nov. 3, 2014. |
Non-Final Office Action for U.S. Appl. No. 13/473,105 dated Nov. 25, 2013. |
Non-Final Office Action for U.S. Appl. No. 13/473,113 dated Oct. 2, 2014. |
Non-Final Office Action for U.S. Appl. No. 13/473,144 dated Feb. 6, 2014. |
Non-Final Office Action for U.S. Appl. No. 13/473,144 dated Feb. 9, 2015. |
Non-Final Office Action for U.S. Appl. No. 13/473,144 dated Oct. 7, 2015. |
Non-Final Office Action for U.S. Appl. No. 13/473,160 dated Jan. 15, 2014. |
Non-Final Office Action for U.S. Appl. No. 13/473,180 dated Sep. 12, 2013. |
Non-Final Office Action for U.S. Appl. No. 13/919,922 dated Jan. 30, 2015. |
Non-Final Office Action for U.S. Appl. No. 13/919,932 dated Feb. 6, 2015. |
Non-Final Office Action for U.S. Appl. No. 13/919,958 dated Jan. 5, 2015. |
Non-Final Office Action for U.S. Appl. No. 13/919,967 dated Feb. 9, 2015. |
Non-Final Office Action for U.S. Appl. No. 13/919,972 dated Jun. 4, 2015. |
Non-Final Office Action for U.S. Appl. No. 14/455,859 dated Nov. 13, 2015. |
Non-Final Office Action for U.S. Appl. No. 14/709,136 dated Sep. 28, 2016. |
Notice of Allowance issued in U.S. Appl. No. 16/129,423 dated Jul. 15, 2019. |
Patent Board Decision—Examiner Affirmed for U.S. Appl. No. 13/473,144 dated Jun. 4, 2018. |
Patent Board Decision—Examiner Affirmed in Part for U.S. Appl. No. 13/473,160 dated Feb. 21, 2017. |
Patent Board Decision—Examiner Reversed for U.S. Appl. No. 13/919,932 dated Dec. 19, 2017. |
Response to Rule 312 Communication for U.S. Appl. No. 15/834,894 dated Apr. 19, 2019; Miscellaneous Communication to Applicant for U.S. Appl. No. 15/834,894 dated Apr. 19, 2019. |
Restriction Requirement for U.S. Appl. No. 15/893,626 dated Aug. 12, 2016. |
Shimin Gong et al., “Backscatter Relay Communications Powered by Wireless Energy Beamforming,” IEEE Trans. on Communication, 2018. |
USPTO Miscellaneous communication for U.S. Appl. No. 15/834,894 dated Apr. 19, 2019. |
Zeng et al., “Joint relay selection and beamforming for mmWave fronthauling network,” 2017 IEEE/CIC International Conference on Communications in China, Oct. 22, 2017, 6 pages. |
Corrected Notice of Allowance for U.S. Appl. No. 16/031,007 dated Sep. 16, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 15/616,911 dated Oct. 31, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 16/031,007 dated Oct. 22, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 16/032,617 dated Oct. 28, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 16/129,423 dated Nov. 7, 2019. |
Final Office Action for U.S. Appl. No. 16/129,413 dated Aug. 13, 2019. |
Misc Communication from USPTO for U.S. Appl. No. 16/382,386 dated Oct. 8, 2019. |
Non-Final Office Action for U.S. Appl. No. 16/231,903 dated Sep. 18, 2019. |
Non-Final Office Action for U.S. Appl. No. 16/294,025 dated Sep. 12, 2019. |
Non-Final Office Action for U.S. Appl. No. 16/377,980 dated Aug. 21, 2019. |
Non-Final Office Action for U.S. Appl. No. 16/526,544 dated Sep. 18, 2019. |
Non-Final Office Action in U.S. Appl. No. 15/836,198 dated Oct. 31, 2019. |
Notice of Allowance for U.S. Appl. No. 16/032,668 dated Sep. 20, 2019. |
Notice of Allowance for U.S. Appl. No. 15/595,919 dated Oct. 25, 2019. |
Notice of Allowance for U.S. Appl. No. 15/904,521 dated Sep. 20, 2019. |
Notice of Allowance for U.S. Appl. No. 16/111,326 dated Oct. 10, 2019. |
Non-Final Office Action for U.S. Appl. No. 14/813,058 dated Jun. 10, 2016. |
Non-Final Office Action for U.S. Appl. No. 14/940,130 dated Apr. 6, 2016. |
Non-Final Office Action for U.S. Appl. No. 14/980,281 dated Apr. 20, 2016. |
Non-Final Office Action for U.S. Appl. No. 14/980,338 dated Mar. 14, 2017. |
Non-Final Office Action for U.S. Appl. No. 15/229,135 dated Dec. 21, 2017. |
Non-Final Office Action for U.S. Appl. No. 15/372,417 dated May 3, 2018. |
Non-Final Office Action for U.S. Appl. No. 15/441,209 dated Jul. 3, 2018. |
Non-Final Office Action for U.S. Appl. No. 15/595,940 dated Nov. 17, 2017. |
Non-Final Office Action for U.S. Appl. No. 15/616,911 dated Jan. 3, 2019. |
Non-Final Office Action for U.S. Appl. No. 15/706,759 dated Jun. 12, 2018. |
Non-Final Office Action for U.S. Appl. No. 15/893,626 dated Jun. 12, 2018. |
Non-Final Office Action for U.S. Appl. No. 16/101,044 dated Dec. 26, 2018. |
Non-Final Office Action for U.S. Appl. No. 16/125,757 dated Aug. 9, 2019. |
Non-Final Office Action for U.S. Appl. No. 16/129,413 dated Feb. 4, 2019. |
Non-Final Office Action for U.S. Appl. No. 16/129,423 dated Feb. 4, 2019. |
Non-Final Office Action in U.S. Appl. No. 15/432,091 dated Nov. 22, 2017. |
Non-Final Office Action in U.S. Appl. No. 16/111,326 dated Mar. 1, 2019. |
Notice of Allowance for U.S. Appl. No. 13/473,083 dated Jan. 7, 2015. |
Notice of Allowance for U.S. Appl. No. 13/473,096 dated Apr. 17, 2015. |
Notice of Allowance for U.S. Appl. No. 13/473,105 dated Jun. 10, 2014. |
Notice of Allowance for U.S. Appl. No. 13/473,113 dated Aug. 10, 2015. |
Notice of Allowance for U.S. Appl. No. 13/473,160 dated May 25, 2017. |
Notice of Allowance for U.S. Appl. No. 13/473,180 dated May 1, 2014. |
Notice of Allowance for U.S. Appl. No. 13/919,922 dated Oct. 27, 2015. |
Notice of Allowance for U.S. Appl. No. 13/919,932 dated Feb. 28, 2018. |
Notice of Allowance for U.S. Appl. No. 13/919,958 dated Sep. 2, 2015. |
Notice of Allowance for U.S. Appl. No. 13/919,967 dated Jul. 29, 2019. |
Notice of Allowance for U.S. Appl. No. 13/919,972 dated Dec. 20, 2016. |
Notice of Allowance for U.S. Appl. No. 14/325,218 dated Dec. 19, 2016. |
Notice of Allowance for U.S. Appl. No. 14/455,859 dated Apr. 20, 2016. |
Notice of Allowance for U.S. Appl. No. 14/709,136 dated Feb. 16, 2017. |
Notice of Allowance for U.S. Appl. No. 14/813,058 dated Nov. 7, 2016. |
Notice of Allowance for U.S. Appl. No. 14/940,130 dated Feb. 1, 2017. |
Notice of Allowance for U.S. Appl. No. 14/980,281 dated Feb. 7, 2017. |
Notice of Allowance for U.S. Appl. No. 14/980,338 dated Feb. 22, 2018. |
Notice of Allowance for U.S. Appl. No. 15/229,135 dated May 22, 2018. |
Notice of Allowance for U.S. Appl. No. 15/372,417 dated Dec. 7, 2018. |
Notice of Allowance for U.S. Appl. No. 15/441,209 dated Dec. 28, 2018. |
Notice of Allowance for U.S. Appl. No. 15/472,148 dated Dec. 10, 2018. |
Notice of Allowance for U.S. Appl. No. 15/595,919 dated Jun. 5, 2019. |
Notice of Allowance for U.S. Appl. No. 15/595,940 dated May 1, 2018. |
Notice of Allowance for U.S. Appl. No. 15/616,911 dated Jul. 24, 2019. |
Notice of Allowance for U.S. Appl. No. 16/129,423 dated Jul. 15, 2019. |
Notice of Allowance for U.S. Appl. No. 16/382,386 dated Jul. 24, 2019. |
Notice of Allowance for U.S. Appl. No. 16/031,007 dated May 2, 2019. |
Notice of Allowance in U.S. Appl. No. 15/432,091 dated Apr. 11, 2018. |
Notice of Allowance in U.S. Appl. No. 15/607,743 dated Jan. 22, 2019. |
Notice of Allowance in U.S. Appl. No. 15/834,894 dated Feb. 20, 2019. |
Notice of Allowance in U.S. Appl. No. 15/835,971 dated May 29, 2018. |
Notice of Allowance in U.S. Appl. No. 15/904,521 dated Mar. 20, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 16/382,386 dated Dec. 30, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 15/616,911 dated Jan. 24, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 15/616,911 dated Dec. 12, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 15/904,521 dated Jan. 8, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/032,617 dated Jan. 9, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/032,668 dated Dec. 30, 2019. |
Corrected Notice of Allowance for U.S. Appl. No. 16/129,423 dated Jan. 23, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/382,386 dated Feb. 6, 2020. |
Final Office Action for U.S. Appl. No. 16/125,757 dated Dec. 2, 2019. |
Final Office Action for U.S. Appl. No. 16/526,544 dated Feb. 12, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/129,413 dated Feb. 12, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/388,043 dated Dec. 27, 2019. |
Non-Final Office Action for U.S. Appl. No. 16/666,680 dated Feb. 19, 2020. |
Notice of Allowance for U.S. Appl. No. 16/129,423 dated Nov. 27, 2019. |
Notice of Allowance for U.S. Appl. No. 16/294,025 dated Jan. 13, 2020. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/032,668 dated Feb. 14, 2020. |
Corrected Notice of Allowability for U.S. Appl. No. 16/111,326 dated Mar. 9, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/526,544 dated May 13, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 15/836,198 dated May 22, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 15/904,521 dated Mar. 12, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/032,668 dated Mar. 23, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/111,326 dated Apr. 23, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/294,025 dated May 18, 2020. |
Final Office Action for U.S. Appl. No. 15/256,222 dated Oct. 4, 2019. |
Final Office Action for U.S. Appl. No. 16/377,980 dated Mar. 4, 2020. |
Final Office Action for U.S. Appl. No. 16/388,043 dated Apr. 15, 2020. |
Non-Final Office Action for U.S. Appl. No. 15/256,222 dated Aug. 27, 2018. |
Non-Final Office Action for U.S. Appl. No. 15/256,222 dated Mar. 21, 2019. |
Non-Final Office Action for U.S. Appl. No. 16/125,757 dated Mar. 23, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/153,735 dated May 13, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/377,847 dated Apr. 20, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/675,290 dated Apr. 30, 2020. |
Notice of Allowance for U.S. Appl. No. 15/256,222 dated Apr. 3, 2020. |
Notice of Allowance for U.S. Appl. No. 15/607,750 dated Jun. 1, 2020. |
Notice of Allowance for U.S. Appl. No. 15/836,198 dated Apr. 17, 2020. |
Notice of Allowance for U.S. Appl. No. 16/231,903 dated Mar. 24, 2020. |
Notice of Allowance for U.S. Appl. No. 16/377,980 dated Apr. 14, 2020. |
Notice of Allowance for U.S. Appl. No. 16/526,544 dated Apr. 9, 2020. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/129,423 dated Mar. 3, 2020. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/231,903 dated Apr. 30, 2020. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/294,025 dated Mar. 25, 2020. |
Corrected Notice of Allowability for U.S. Appl. No. 15/256,222 dated Jul. 10, 2020. |
Corrected Notice of Allowability for U.S. Appl. No. 16/377,980 dated Jul. 22, 2020. |
Corrected Notice of Allowability for U.S. Appl. No. 16/526,544 dated Jul. 16, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/526,544 dated Aug. 25, 2020. |
Final Office Action for U.S. Appl. No. 16/125,757 dated Jul. 15, 2020. |
Final Office Action for U.S. Appl. No. 16/377,847 dated Jul. 13, 2020. |
Final Office Action for U.S. Appl. No. 16/666,680 dated Jun. 29, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/204,397 dated Sep. 17, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/388,043 dated Aug. 3, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/451,998 dated Sep. 11, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/452,023 dated Sep. 9, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/819,388 dated Jul. 2, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/866,536 dated Sep. 1, 2020. |
Notice of Allowance for U.S. Appl. No. 16/129,413 dated Aug. 12, 2020. |
Notice of Allowance for U.S. Appl. No. 16/153,735 dated Jul. 2, 2020. |
Notice of Allowance for U.S. Appl. No. 16/684,789 dated Jul. 10, 2020. |
Supplemental Notice of Allowability for U.S. Appl. No. 16/153,735 dated Jul. 22, 2020. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/231,903 dated Jul. 1, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 15/256,222 dated Oct. 28, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 15/836,198 dated Oct. 2, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/129,413 dated Nov. 27, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/153,735 dated Nov. 18, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/377,980 dated Oct. 5, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/526,544 dated Sep. 25, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/675,290 dated Dec. 16, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/684,789 dated Nov. 20, 2020. |
Final Office Action for U.S. Appl. No. 16/364,956 dated Oct. 2, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/233,044 dated Oct. 14, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/377,847 dated Dec. 14, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/398,156 dated Oct. 15, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/461,980 dated Sep. 21, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/666,680 dated Nov. 13, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/689,758 dated Sep. 29, 2020. |
Non-Final Office Action for U.S. Appl. No. 16/941,690 dated Nov. 12, 2020. |
Notice of Allowability for U.S. Appl. No. 16/129,413 dated Nov. 9, 2020. |
Notice of Allowance for U.S. Appl. No. 16/125,757 dated Oct. 28, 2020. |
Notice of Allowance for U.S. Appl. No. 16/388,043 dated Nov. 5, 2020. |
Notice of Allowance for U.S. Appl. No. 16/452,023 dated Nov. 16, 2020. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/153,735 dated Oct. 9, 2020. |
Notice of Allowance for U.S. Appl. No. 16/927,470 dated Oct. 29, 2020. |
Notice of Allowability for U.S. Appl. No. 16/129,413 dated Jan. 6, 2021. |
Corrected Notice of Allowability for U.S. Appl. No. 16/684,789 dated Jan. 11, 2021. |
Corrected Notice of Allowance for U.S. Appl. No. 16/125,757 dated Dec. 31, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/125,757 dated Feb. 1, 2021. |
Corrected Notice of Allowance for U.S. Appl. No. 16/388,043 dated Dec. 24, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/388,043 dated Dec. 30, 2020. |
Corrected Notice of Allowance for U.S. Appl. No. 16/927,470 dated Feb. 2, 2021. |
Corrected Notice of Allowance for U.S. Appl. No. 16/927,470 dated Jan. 26, 2021. |
Corrected Notice of Allowance for U.S. Appl. No. 16/388,043 dated Feb. 8, 2021. |
International Preliminary Report on Patentability for International Application No. PCT/US2018/064184 dated Jan 21, 2021. |
Morgan et al., “A Same-Frequency Cellular Repeater Using Adaptive Feedback Cancellation,” IEEE, Mar. 12, 2012, pp. 3825-3830. |
Notice of Allowability for U.S. Appl. No. 15/607,750 dated Jan. 11, 2021. |
Notice of Allowability for U.S. Appl. No. 16/129,413 dated Feb. 18, 2021. |
Notice of Allowance for U.S. Appl. No. 16/204,397 dated Jan. 12, 2021. |
Notice of Allowance for U.S. Appl. No. 16/354,390 dated Feb. 25, 2021. |
Notice of Allowance for U.S. Appl. No. 16/451,998 dated Jan. 14, 2021. |
Notice of Allowance for U.S. Appl. No. 16/666,680 dated Mar. 2, 2021. |
Notice of Allowance for U.S. Appl. No. 16/689,758 dated Jan. 22, 2021. |
Notice of Allowance for U.S. Appl. No. 16/819,388 dated Jan. 25, 2021. |
Notice of Allowance for U.S. Appl. No. 16/866,536 dated Jan. 29, 2021. |
Supplemental Notice of Allowability for U.S. Appl. No. 16/153,735 dated Jan. 11, 2021. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/452,023 dated Feb. 18, 2021. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/153,735 dated Feb. 24, 2021. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/451,998 dated Mar. 2, 2021. |
Corrected Notice of Allowability for U.S. Appl. No. 16/125,757 dated Mar. 11, 2021. |
Corrected Notice of Allowability for U.S. Appl. No. 16/204,397 dated Mar. 11, 2021. |
Corrected Notice of Allowance for U.S. Appl. No. 16/689,758 dated Apr. 7, 2021. |
Non-Final Office Action for U.S. Appl. No. 17/011,042 dated Mar. 23, 2021. |
Notice of Allowability for U.S. Appl. No. 16/388,043 dated Mar. 11, 2021. |
Notice of Allowability for U.S. Appl. No. 16/819,388 dated Apr. 5, 2021. |
Notice of Allowance for U.S. Appl. No. 16/377,847 dated Apr. 5, 2021. |
Notice of Allowance for U.S. Appl. No. 16/391,628 dated Mar. 17, 2021. |
Notice of Allowance fro U.S. Appl. No. 16/451,980 dated Mar. 23, 2021. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/866,536 dated Mar. 17, 2021. |
Corrected Notice of Allowance for U.S. Appl. No. 16/354,390 dated Jun. 3, 2021. |
Corrected Notice of Allowance for U.S. Appl. No. 16/689,758 dated May 27, 2021. |
Notice of Allowability for U.S. Appl. No. 16/819,388 dated May 27, 2021. |
Notice of Allowance for U.S. Appl. No. 16/233,044 dated Jun. 4, 2021. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/451,980 dated May 18, 2021. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/451,998 dated May 18, 2021. |
Supplemental Notice of Allowance for U.S. Appl. No. 16/941,690 dated May 18, 2021. |
Number | Date | Country | |
---|---|---|---|
20190319753 A1 | Oct 2019 | US |
Number | Date | Country | |
---|---|---|---|
61548201 | Oct 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16101044 | Aug 2018 | US |
Child | 16364956 | US | |
Parent | 15595940 | May 2017 | US |
Child | 16101044 | US | |
Parent | 14980281 | Dec 2015 | US |
Child | 15595940 | US | |
Parent | 13473113 | May 2012 | US |
Child | 14980281 | US |