Method and system for centralized or distributed resource management in a distributed transceiver network

Information

  • Patent Grant
  • 11108512
  • Patent Number
    11,108,512
  • Date Filed
    Sunday, September 9, 2018
    8 years ago
  • Date Issued
    Tuesday, August 31, 2021
    5 years ago
Abstract
A master application device comprises a plurality of distributed transceivers, a central baseband processor, and a network management engine that manages operation of the master application device and end-user application devices. The master application device communicates data streams to the end-user devices utilizing one or more distributed transceivers selected from the plurality of distributed transceivers. The selected distributed transceivers and the end-user devices are concurrently configured by the network management engine based on corresponding link quality and propagation environment. The network management engine allocates resources to the selected distributed transceivers and the end-user devices during the data communication. The network management engine continuously monitors communication environment information to configure beamforming settings and/or antenna arrangement for the selected distributed transceivers. Beam patterns are selected for the selected distributed transceivers so as to minimize power consumption and/or based on the location and orientation information of the end-user application devices.
Description
FIELD OF THE INVENTION

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 centralized or distributed resource management in a distributed transceiver network.


BACKGROUND OF THE INVENTION

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.


BRIEF SUMMARY OF THE INVENTION

A method and/or system for centralized or distributed resource management 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.





BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS


FIG. 1 is a block diagram illustrating an exemplary communication system that supports resource management in a centralized managed distributed transceiver network, in accordance with an embodiment of the invention.



FIG. 2A is a diagram that illustrates an exemplary usage scenario where distributed transceivers are centrally managed to create a high-performance link between a transmitting device and one receiving device, in accordance with an embodiment of the invention.



FIG. 2B is a diagram that illustrates an exemplary usage scenario where high-performance links are created between a master application device and one or more end-user application devices in a centralized managed distributed transceiver network, in accordance with an embodiment of the invention.



FIG. 3 is a diagram that illustrates an exemplary transceiver module, in accordance with an embodiment of the invention.



FIG. 4 is a diagram illustrating an exemplary master device with a collection of distributed transceivers that are implemented in a star topology, in accordance with an embodiment of the invention.



FIG. 5 is a diagram illustrating an exemplary master device with a collection of distributed transceivers that are implemented in a ring topology, in accordance with an embodiment of the invention.



FIG. 6 is a diagram illustrating an exemplary transceiver module with a single antenna that has fixed directionality, in accordance with an embodiment of the invention.



FIG. 7 is a diagram illustrating an exemplary transceiver module with a configurable phased antenna array, in accordance with an embodiment of the invention.



FIG. 8 is a diagram illustrating exemplary steps utilized by a master device with a collection of distributed transceivers to establish a high-throughput link with an end-user application device, in accordance with an embodiment of the invention.



FIG. 9 is a diagram illustrating exemplary steps utilized by a master device for resource management during communication, in accordance with an embodiment of the invention.





DETAILED DESCRIPTION OF THE INVENTION

Certain embodiments of the invention may be found in a method and system for centralized or distributed resource management in a distributed transceiver network. In accordance with various exemplary embodiments of the invention, a single network management engine is utilized to manage operation of a master application device and a plurality of end-user application devices that are served or managed by the master application device in a communication network. In some embodiments of the invention, the “master” device may be just a logical assignment and all devices in the network may have similar computational and communications capabilities. In such embodiments, a peer-to-peer network may be established with no access point involved. The master application device comprises a plurality of distributed transceivers, a central baseband processor, and the network management engine. An end-user application device served by the master application device does not comprise the network management engine and has no access to manage the network management engine. The master application device may communicate data streams utilizing one or more distributed transceivers selected from the plurality of the distributed transceivers to one or more end-user devices. The network management engine may concurrently configure the selected one or more distributed transceivers and the one or more end-user devices based on corresponding link quality and propagation environment. The network management engine may allocate and manage resources in the communication network and perform transmit power control, frequency hopping and/or beam pattern hopping to reduce outside electrical or RF interference during the data communication. The central baseband processor may perform digital signal processing needed for transmit and receive operations for each of the selected one or more distributed transceivers. The network management engine may continuously monitor communication environment information such as, for example, propagation environment conditions, link quality, device capabilities, usage of resources, available resources, device locations, target throughput, and/or application quality of service (QoS) requirements. Beamforming settings, transmit power levels per transceiver for different devices and/or antenna arrangement may be configured for the selected one or more distributed transceivers based on the communication environment information. The network management engine may select beam patterns so as to minimize power consumption, and/or based on device location and orientation information.



FIG. 1 is a block diagram illustrating an exemplary communication system that supports resource management in a centralized managed distributed transceiver network, in accordance with an embodiment of the invention. Referring to FIG. 1, there is shown a communication network 100 comprising a plurality of application devices, of which application devices 111-119 are displayed.


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, for example, may comprise radios such as, for example, a millimeter Wave (mmWave), a WLAN, WiMax, Bluetooth, Bluetooth Low Energy (BLE), cellular radios, WiMAX radio, 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 or remote 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. The application device may be an access point (e.g., WLAN 802.11abgn), a base station (e.g., cellular 3G/LTE), or a node in a peer-to-peer link (e.g., Bluetooth). 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 the end-user application devices 112-116, 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 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 antenna or antenna array 111b-116b or transmit power levels of 111b-116b of the associated antenna or antenna array 111b-116b, and to coordinate and manage the operation of the distributed transceivers 111a-116a and associated antenna or antenna array 111b-116b based on the collected communication environment information.


In an exemplary embodiment of the invention, the network management engine 120 may be operable to perform resource allocation and management for the master application device 111 and the end-user application devices 112-116 during the transmission. For example, the management engine 120 may decide which transceivers at the master application device 111 need to be activated or switched on, and at what transmit power levels. Frequency or channel assignment may be performed by the management engine 120 to each of the active distributed transceivers at the master application device 111. In this regard, the management engine 120 may configure the master application device 111 to maintain continuous connections with the plurality of end-user application devices 112-116 as needed. In another example, for each of the active distributed transceivers at the master application device 111, the management engine 120 may select beam patterns, antenna polarization, antenna spacing, and/or array geometry with least power consumption in accordance with corresponding physical locations of the activated distributed transceivers. Furthermore, the management engine 120 may enable implementation of transmit power control to save power, minimize cross-interference between various wireless links, and to optimize end-to-end network performance.


In the collected communication environment information, the link quality may comprise signal-to-noise ratios (SNR) at different transceivers, signal-to-interference-noise ratios (SINR) at different transceivers, and/or signal-to-leakage-noise ratios (SLNR) at different devices and transceivers. The application device capabilities may comprise battery capacity, battery life, number of transceivers, number of antennas per transceiver, device interface types, maximum transmit power level, power consumption in transmit/receive modes, 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 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 FIG. 1, the invention may not be so limited. Accordingly, an application device may be operable to utilize one or more associated distributed transceivers to communicate with one or more application devices with normal transceivers without departing from the spirit and scope of various embodiments of the invention (thereby providing backward compatibility with traditional or standard transceiver implementations). In some embodiments of the invention, a subset of the application devices 111-119 may comprise or support positioning techniques to identify the device's location. Such techniques may comprise global navigation satellite system (GNSS) (e.g. GPS, GALILEO, GLONASS), assisted-GPS, WLAN based positioning, and triangulation-based techniques. The location data may be then utilized by the NME 120 according to some other embodiments of this patent application.



FIG. 2A is a diagram that illustrates an exemplary usage scenario where distributed transceivers are centrally managed to create a high-performance link between a transmitting device and one receiving device, in accordance with an embodiment of the invention. Referring to FIG. 2A, there is shown a master application device 210 and an end-user application device 220.


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 224 may be operable to configure, manage and control orientations of the distributed transceivers 212a-212e.


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 FIG. 2A, the network management engine 216 is residing in the master application device 210. However, in some embodiments the network management engine 216 may reside on different network devices such as, for example, separate network microprocessors and servers on the communication network 100. The network management engine 216 may comprise a full software implementation, for example. In addition, the functionality of the network management engine 216 may be distributed over several devices in the communication network 100. In some embodiments the network management engine 216 may be operable to manage communication sessions over the communication network 100. In this regard, the network management engine 216 may be operable to coordinate operation of baseband processors in the communication network 100 such that various baseband processing may be split or shared among the baseband processors. For example, the network management engine 216 may enable multiple central baseband processors such as, for example, the central baseband processor 214 and the central baseband processor 226 for parallel baseband processing in order to increase throughput if needed.


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.


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 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.


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.


In some embodiments of the invention, a multi-dimensional transmit-power-control scheme may be implemented by the NME module 216. In this regard, the NME 216 may be operable to form an optimization problem with transmit power levels of transceivers 212a-212e as optimization parameters. The NME 216 may then search iteratively or in a single shot for a set of transmit power levels for the distributed transceivers 212a-212e that satisfy a set of corresponding requirements/criteria. In an exemplary embodiment of the invention, exemplary criteria that may be used for the above optimization may comprise maintaining reliable wireless link per transceiver, achieving a target total throughput (sum of throughputs over all active transceivers), minimizing total power transmitted over all active transceivers, minimizing total power consumption by the active transceivers, achieving a target sum “channel capacity” (sum of channel capacities corresponding to active transceivers), minimizing total/effective cross-interference at the receiving end's transceivers, and/or minimizing total undesired interference caused to other active devices in the vicinity.


Some embodiments of the invention may comprise transmit power distribution/budgeting schemes that may be applied over the transceivers within a device, the master application device 210, the end-user application device 220, or the end-user application device 250. In this regard, distribution of transmit power levels may be optimized through meeting certain performance criteria. For example, assume that the throughput achievable by the distributed transceiver 212 a as a function its transmit power level is represented by T_212 a{TXP_212 a}. The total achievable throughput then becomes T_total=T_212 a{TXP_212 a}+ . . . +T_212 e{TXP_212 e}. Then the power distribution optimization problem becomes finding a set of {TXP_212 a, . . . , TXP_212 e} values such that T_total is above a target/desired throughput while the sum of TXP_212 a+ . . . +TXP_212 e is minimized. The relationship between throughput and transmit power level (i.e., T{.} function) may be defined by a look-up table based on communication/system/implementation parameters, or derived from analytical throughput/channel-capacity formulas. In another example, when cross-interference between the different simultaneous links is not negligible, then the throughput functions may be modified to represent the impact of all other transceivers' transmit power levels on each transceiver's throughput. In this case, the total throughput functions may be modified as T_total=T_212 a{TXP_212 a, . . . , TXP_212 e} + . . . +T_212 e{TXP_212 a, . . . , TXP_212 e}, since every link's throughput now depends on all other transmit power levels. Again, the power distribution optimization problem becomes finding a set of {TXP_212 a, . . . , TXP_212 e} values such that the above T_total exceeds a target/desired throughput while the sum of TXP_212 a+ . . . +TXP_212 e is minimized.


In some embodiments of the invention, the throughput function T{.} is substituted with Shannon channel capacity function C{.} which is again a function of transmit power level.


In some embodiments of the invention, a single device, the master application device 210 or the end-user application device 220, 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 that may be 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 utilizing time-multiplexing at the same IF frequency or frequency-multiplexing at different IF frequencies. 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 228 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 central baseband processor 226 and/or other associated component units such as 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. In an exemplary embodiment of the invention, the master application device 210 may be operable to continuously scan the propagation environment to identify the directions and antenna patterns that result in strong reflected signals at the end-user application device 220. Then, the master application device 210 may associate each strong reflector with one of the collection of distributed transceivers 212 a through 212 e so as to transmit an independent different data stream to the end-user application device 220 over each distributed transceiver and through each strong reflector. For example, the master application device 210 transmits two data streams to the end-user application device 220 using two different distributed transceivers 212 a and 212 d that may use the same frequency channel. In particular, the distributed transceivers 212 a may choose a beam pattern 250 and orientation for a direct line of sight (LOS) to a transceiver 222, for example, of the end-user application device 220 (the receiving device) and transmit a first data stream over a carrier frequency RF1. On the other hand, the distributed transceiver 212 d may choose a different beam pattern 252 and orientation that is pointing towards the reflector 230 and transmit a second data stream also over the same carrier frequency RF1. The reflector 230 then may reflect the beam 252 towards a different transceiver 224 of the end-user application device 220. The selection of the beam patterns 250 and 252 may come from the central baseband processor 214 and the network management engine 216. In an exemplary embodiment of the invention, the central baseband processor 214 may profile channel energy for directions of arrival and other schemes. The network management engine 216 may know communication environment information such as, for example, the number of users, number of streams needed, and/or available frequency channels.


The network management engine 216 may correlate beam patterns or configurations with physical location utilizing a database 219 in the master application device 210. The database 219 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to record and/or store beam patterns or configurations in terms of corresponding location and orientation information. In this regard, once the location (even a coarse/initial location) and orientation of an application device and/or the distributed transceivers within an application device are determined, an initial assignment of active transceivers and/or beam pattern or configuration for the associated antenna array 212a may be selected from the database 219. The database 219 may comprise data the represents the mapping of physical locations and/or orientations of application devices in the environment to some initial “good” network configurations such as list of transceivers to be active within each device and their corresponding antenna/beam configurations. The database 219 may continuously be updated and fine-tuned by the master application device 210 as more application devices enter the network and finer configurations may be derived by the network management engine 216. Additionally, the database 219 may be utilized to store and track the positions of dominant reflectors in the environment and how the location of those reflectors impacts the selection of optimal transceivers and antenna configurations. The NME 216 is operable to feed both the approximate locations of application device and dominant reflectors to the database 219 to derive an initial “good” network/device configuration. Various positioning techniques such as Angle-of-arrival (AOA), Time-of-Arrival (TOA) measurements may be utilized for initial coarse positioning. In an exemplary embodiment of the invention, an end-user application device such as the end-user application device 220 may be operable to utilize Bluetooth and/or wireless LAN (WLAN) and/or mmWave to identify its own coarse position. In general, the same primary wireless protocol used for data communication (or an auxiliary wireless protocol) may be used for the purpose of the above-mentioned positioning. In this regard, beaconing may be transmitted to communicate location and orientation information of the end-user application device 220 to the network management engine 216. The network management engine 216 may configure the associated distributed transceivers to different directions and beams. Antennas equipped to the distributed transceivers may not necessarily be omnidirectional. The transmitted beacons may cover the entire geographic area of interest without requiring the distributed transceivers to be equipped with omnidirectional antennas or omnidirectional antenna arrays. Beacon packets may be generally used for control/negotiation amongst the devices in the network (e.g., time/frequency allocations, network coordination/synchronization). Beacon packets therefore require a high fidelity and should be reliably communicated even without any good beamforming configurations. To achieve this, beacon packets are desired to be transmitted in an omnidirectional fashion. In some embodiments of the invention, the available distributed transceivers are utilized and configured to provide an effective omnidirectional coverage while maintaining high effective-transmit-power in every direction. This may be achieved by setting each transceiver in directional/beamforming configuration, but each pointing at a different direction (and collectively covering the full space). In some embodiments of the invention, the beaconing phase/period may be also used for initial/coarse positioning (in addition to network setup/synchronization) where this initial positioning data is fed into the database to derive “good” antenna/device configurations to be used for consequent high-throughput packets.


An orientation finding unit 215 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to identify or find orientation information of the master application device 210. The orientation finding unit 215 may comprise a gyroscope and/or an accelerometer. The database 219 may be trained and improved over time so as to map fine beam patterns with location and orientation of device. In an exemplary embodiment of the invention, the network management engine 216 may utilize device location and orientation information to configure corresponding beam patters to be utilized. For example, the central baseband processor 214 and the network management engine 216 may select narrow beams for close devices and may select wide beams for further devices, respectively.


In one embodiment of the invention, the master application device 210 may be operable to utilize the reflector 230 for the second data stream, for example, to lower the chances of an object blocking both the first and second data streams, simultaneously. In other words, if a big enough object blocks the LOS between the master application device 210 and the end-user application device 220, the second data stream may likely be intact and sustained by complete direct reflecting through a reflected path 252a. Although FIG. 2A shows one reflector 230, in one embodiment of the invention, several reflectors may be used to transmit one data stream or multiple data streams. The use of multiple reflectors may provide reflection diversification in case one reflector or a sub-set of reflectors are blocked. In other words, instead of directing all transmit power towards one reflector only, the total transmit power may be distributed to propagate over a set of “good” reflectors in the environment. This distribution of power over different reflectors may be done in a controlled, configurable, adaptive, and intelligent manner. For example, reflectors may be chosen and targeted that provide better orthogonality between the different paths. In FIG. 2A, the master application device 210 may use a second reflector at a different location and another distributed transceiver 212c, for example, to communicate with the end-user application device 220 and send a third data stream. Also the reflected path 252a may be caused by more than one reflector where, for example, the distributed transceiver 212e transmits towards the reflector 230 and the reflection transmits towards a second reflector and the reflection of the second reflector reaches the end-user application device 220. In another embodiment of the invention, the first and second data streams in FIG. 2A may comprise the same data content and the use of LOS path and one or more reflector paths may provide link robustness for data content in case an obstacle blocks some of the paths.


In an exemplary embodiment of the invention, the master application device 210 may continuously monitor and collect 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 by the end-user device 220 to report and negotiate configuration information with the master application device 210. The feedback channel 240 may comprise a low-throughput connection or link, and may be implemented through a WLAN, Bluetooth, and/or 60 GHz link, for example. The reported information from the end-user application device 220 may comprise, for example, channel measurement, device capabilities, battery life, number of transceivers, number of antennas per transceiver, antenna polarization, radiation pattern, measured cross-interference levels, antenna spacing, array geometry, the sequence of antenna array coefficients being evaluated, device locations, target throughput, and/or application QoS requirements.


The network management engine 216 may allocate and manage resources such as, for example, frequency channels, time slots, processors and/or storage to establish and maintain connections or links between the master application device 210 and the end-user application device 220 based on the reported information. For example, the management engine 120 may be operable to determine which transceivers are to be switched ON for transmission and at what transmit power levels based on device locations, power and battery storage capabilities and/or capacities, and antenna beamforming capabilities. Transmit power control, frequency hopping and/or beam pattern hopping may be utilized to reduce outside electrical or RF interference during transmission.



FIG. 2B is a diagram that illustrates an exemplary usage scenario where high-performance links are created between a master application device and one or more end-user application devices in a centralized managed distributed transceiver network, in accordance with an embodiment of the invention. Referring to FIG. 2B, there is shown the master application device 210 and the end-user application device 220.


In an exemplary operation, two control links 280b and 280a may be established between the master application device 210 and the end-user application device 220. The control link 280b is an uplink connection from the end-user device 220 to the master application device 210. The control link 280a is a downlink connection from the master application device 210 to the end-user device 220. The two control links 280b and 280a may be implemented as low-rate high-fidelity high-range links utilizing Bluetooth in the 2.4 GHz band, MAN in the 5 GHz band, or even a low-throughput mode of 60 GHz. In some instances, the master application device 210 may attempt to establish a high-throughput link 280 with the end-user application device 220. Initially, the master application device 210 and the end-user application device 220 may utilize the downlink control link 280a and the uplink control link 280b, respectively, to negotiate corresponding configurations to be used for the high-throughput link 280. The network management engine 216 may be operable to collect information from both the master application device 210 and the end-user application device 220. In an exemplary embodiment of the invention, the NME 216 may be operable to collect information from all other devices in the vicinity even if no high-throughput links are established yet. The collected information may comprise, for example, a number of transceivers, a number of antennas per transceiver, antenna polarization, radiation pattern, antenna spacing, array geometry, the sequence of antenna array coefficients being evaluated or to be evaluated in the next time slots, device locations, target throughput, and/or application QoS requirements. Furthermore, the network management engine 216 may track the usage and availability of resources such as frequency bands and bandwidth requests by other devices in the vicinity. The network management engine 216 may instruct or signal the master application device 210 and the end-user application device 220 to start with an initial mode of operation such as the spatial diversity mode. For example, in instances where the requested throughput targets are high and the network management engine 216 identifies several available frequency bands, the network management engine 216 instructs the master application device 210 to use the frequency diversity mode. At this point, the master application device 210 and the end-user application device 220 may be enabled to perform channel estimation, and to analyze and identify the best direction/pattern for each transceiver based on reflections and environment conditions. Once optimal configurations are selected, the master application device 210 and the end-user application device 220 may report corresponding link quality figures back to the network management engine 216. At this maintenance phase, the master application device 210 and the end-user application device 220 may continue reporting their link quality figures, as well as target throughputs and QoS requirements, to the network management engine 216. If at any time, the network management engine 216 determines that the throughput and QoS requirements of the high-throughput link 280 between the master application device 210 and the end-user application device 220 are substantially above the requested levels, the network management engine 216 may configure the master application device 210 and the end-user application device 220 to switch to the spatial diversity mode, for example, to free up bandwidth for other potential users. This change in configuration may be already available to the master application device 210, and the end-user application device 220 may be notified about it over the downlink control link 280a. The network management engine 216 may utilize different rules or policies for configuring application devices such as, for example, the master application device 210 and the end-user application device 220 in the communication network 100.


In an exemplary embodiment of the invention, the network management engine 216 may configure the master application device 210 to maintain connections with the plurality of different end-user application devices in the communication network 100 as needed. For example, a different end-user application device 230 in the communication network 100 may also request to establish a different high-throughput link 290 with the master application device 210. In this case, two different control links 290b and 290a may be established between the master application device 210 and the end-user application device 230. The control link 290b is an uplink connection from the end-user device 230 to the master application device 210. The control link 290a is a downlink connection from the master application device 210 to the end-user device 230. The two control links 290b and 290a may be implemented as low-rate high-fidelity links utilizing Bluetooth in the 2.4 GHz band, WLAN in the 5 GHz band, or even a low-throughput mode of 60 GHz.


In some instances, the end-user application device 230 may communicate the link-request to the master application device 210 and to the network management engine 216 through a low-throughput control link 290a from the end-user device 230 to the master application device 210. Based on the throughput request of the end-user application device 230, the network management engine 216 may configure the master application device 210 to free up a few of its distributed transceivers and shift the data streams between the master application device 210 and the end-user application device 220 to be transported over the same frequency channel. The network management engine 216 may configure the idle transceivers of the master application device 210 to establish the high throughput link 290 with the end-user application device 230 on a different channel frequency. In an exemplary embodiment of the invention, the network management engine 216 may continuously monitor network requirements and conditions and may reconfigure the settings and utilizations of the entire application devices in the communication network 100. The network management engine 216 may be responsible for compiling data such as the numbers of routes and buses for a given network as well as its service population, and switching associated transceivers between different modes of operation, such as, for example, spatial diversity mode, frequency diversity mode, multiplexing mode, and MIMO mode.



FIG. 3 is a diagram that illustrates an exemplary transceiver module, in accordance with an embodiment of the invention. Referring to FIG. 3, there is shown a transceiver 300 comprising an antenna array 310, an antenna array with/without antenna combiner 320, down-converters 330, up-converters 340, and a multiplexer 350.


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 transmission the transceiver 300 may be operable to receive a transmit signal from the central baseband processor 214. The transmit signal received from the central baseband processor 214 may be up-converted to RF frequency via the up-converters 340. For reception, the transceiver 300 may pass a receive signal from the antenna array 310 after down-conversion to the central baseband processor 214. 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 an embodiment of the invention, the input/output frequency of the transceiver 300 may be the same, that is, and in this regard, no frequency up-conversion may be performed. In this regard, the transceiver 300 may only perform signal amplification and feeding of signals into the antenna array 310.



FIG. 4 is a diagram illustrating an exemplary master device with a collection of distributed transceivers that are implemented in a star topology, in accordance with an embodiment of the invention. Referring to FIG. 4, there is shown a central processor 400 that is connected to a collection of transceivers 410a through 410N. As shown, the collection of transceivers 410a through 410N are connected to the central processor 400 in a star topology with direct separate cables, for example, from the central processor 400 to each of the collection of transceivers 410a through 410N.


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 FIG. 2. During transmission, a baseband signal supplied from the baseband processor 420 may be translated into an intermediate-frequency (IF) signal. The up-converters 446 may further translate the IF signal to a final radio-frequency (RF) and send it over the air through an antenna array such as the antenna array 411a. For reception, the transceiver 410a, for example, may pass a received RF signal from the antenna array 411a to the down-converters 440. 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 this regard, the network management engine 430 may determine which of the transceivers are to be switched ON or activated, and at what power levels. The network management engine 430 may select beam patterns for the activated transceivers so that the least power consumption is utilized. Beam patterns of the activated transceivers may be selected by correlating beam patterns or configurations with physical locations and/or orientations of the activated transceivers. In this regard, the network management engine 430 may communicate with the database 219 to identify or determine corresponding beam patters or configurations based on corresponding physical locations and orientations of the activated transceivers. In addition, the baseband processer 420 may manage and control transmit power levels at each of the activated transceivers. In this regard, transmit power control mechanism may be applied at each of the activated transceivers to improve network performance.


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 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 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 one or more characteristics or factors, such as for example, corresponding propagation environment conditions, link quality, device capabilities, device locations, usage of resources, resource availability, target throughput, application QoS requirements, etc.


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 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, 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 some embodiments of the invention, the cable connection between the central processor 400 and the distributed transceivers 410a through 410N may be substituted with an optical connection, printed-board connection, Ethernet cable, and/or another wireless connection.



FIG. 5 is a diagram illustrating an exemplary master device with a collection of distributed transceivers that are implemented in a ring topology, in accordance with an embodiment of the invention. As shown, the collection of transceivers 410a through 410N may be connected to the central processor 400 in a ring topology with a single direct cable from the central processor 400 to each of the collection of transceivers 410a through 410N. In this regard, a single control channel between the baseband processer 420 and each of the distributed transceivers 410a through 410N may be utilized for configuring the entire distributed transceivers 410a through 410N as needed.



FIG. 6 is a diagram illustrating an exemplary transceiver module with a single antenna that has fixed directionality, in accordance with an embodiment of the invention. Referring to FIG. 6, there is shown a transceiver 600. The transceiver 600 comprises an antenna 610, a switcher 620, down-converters 630, up-converters 640, and a multiplexer 650. The down-converters 630, the up-converters 640, and the multiplexer 650 may operate in substantially the same manner as the down-converters 330, the up-converters 340, and the multiplexer 350, respectively. In some embodiments, a device may utilize several such directional antennas each attached to a different transceiver and installed at a different point within the device. These antennas may be mounted to have their main lobes pointing at different directions in order to cover the space. Depending on environment/link conditions, then one or more of these transceivers/antennas may be selected by the NME 216 to provide a good link resulting in high received signal power at the other end.


In an exemplary operation, the antenna 610 may have fixed directionality. In this regard, the antenna 610 with fixed directionality may be utilized to generate a fixed beam pattern, which results in the minimized amount of power amplifiers (PAs) and low noise amplifiers (LNAs) in the transceiver 600. The switcher 620 may comprise suitable logic, circuitry, interfaces and/or code that may be operable to switch on or off the transceiver 600. For example, the switcher 620 may be configured or programmed to switch on the transceiver 600 only orientated in the vicinity of the fixed directionality of the antenna 610 for power saving.



FIG. 7 is a diagram illustrating an exemplary transceiver module with a configurable phased antenna array, in accordance with an embodiment of the invention. As shown a transceiver 700 that comprises an antenna array 710, a switcher 620, down-converters 630, up-converters 640, and a multiplexer 650.


In an exemplary operation, the antenna array 710 may be a configurable phased antenna array. In this regard, the configurable phased antenna array 710 may have various orientations. Accordingly, the configurable phased antenna array 710 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 711a of the configurable phased antenna array 710 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 711a may be switched on by the switcher 620 to transmit data to the receiver end and all other transceivers 711a through 711N of the configurable phased antenna array 710 are switched off for power saving. Beam patterns of the transceiver 711a 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 711a, and/or by minimizing the power consumption. Beam pattern hopping is a method of beamforming by hopping beam patterns among a set of transmit/receive antennas.



FIG. 8 is a diagram illustrating exemplary steps utilized by a master device with a collection of distributed transceivers to establish a high-throughput link with an end-user application device, in accordance with an embodiment of the invention. Referring to FIG. 8, in step 802, the master application device 210 with one or more distributed transceivers 212a through 212e is attempting to establish a high-throughput link with an end-user application device such as the end-user application device 220. The exemplary steps start with step 804, where the master application device 210 may be operable to establish two low-throughput high-fidelity links 280b and 280a between the master application device 210 and the end-user application device 220. The low-throughput high-fidelity link 280b is an uplink connection from the end-user device 220 to the master application device 210. The low-throughput high-fidelity link 280a is a downlink connection from the master application device 210 to the end-user device 220.


In step 806, the network management engine 216 may be operable to track and collect information about device capability, device locations, target throughput, and/or application QoS requirements utilizing the low-throughput high-fidelity links from both the master application device 210 and the end-user application device 220. In step 808, the master application device 210 and the end-user application device may utilize the two low-throughput high-fidelity links 280b and 280a to negotiate corresponding device configurations to be used for the high-throughput link based on the collected information. In step 810, the network management engine 216 may concurrently configure the master application device 210 and the end-user application device 220 utilizing the negotiated corresponding device configurations. In step 812, the network management engine 216 may track the usage and availability of resources in the communication network 100. In step 814, the network management engine 216 may instruct or signal the master application device 210 and the end-user application device 220 to establish the high-throughput link utilizing the allocated resources. In step 816, the master application device 210 may communicate data streams with the end-user application device 220 over the high-throughput link.



FIG. 9 is a diagram illustrating exemplary steps utilized by a master device for resource management during communication, in accordance with an embodiment of the invention. Referring to FIG. 9, in step 902, the master application device 210 with one or more distributed transceivers 212a through 212e is communicating data streams over a high-throughput link with one or more end-user application devices such as the end-user application devices 220-230. The exemplary steps start with step 904, where the network management engine 216 in the master application device 210 may continuously monitor and collect propagation environment conditions, link quality, device capabilities, device locations, target throughput, and/or application QoS requirements from the master application device 210 and the end-user devices 220-230. In step 904, the network management engine 216 determines if a device configuration change is needed. For example, the network management engine 216 may evaluate the reported information such as link quality. In some instances, the reported link quality may be substantially way below acceptable levels. The network management engine 216 may determine that the master application device 210 and the end-user devices 220-230 need to be re-configured. The exemplary steps continue in step 906.


In step 906, the network management engine 216 may determine configurations for the master application device 210 and the end-user devices 220-230 based on the collected propagation environment conditions, link quality, device capabilities, device locations, target throughput, and/or application QoS requirements. The network management engine 216 may concurrently configure the master application device 210 and the end-user devices 220-230 based on the determined configurations. In step 908, the network management engine 216 may be operable to allocate and manage available resources to the master application device 210 and the end-user application devices 220-230. Various resource allocation and management mechanisms may be utilized by the network management engine 216. For example, for a given target throughput, the network management engine 216 may determine which transceivers in the master application device 210 and/or the end-user devices 220-230 should be switched ON or activated, and at what transmit levels. The network management engine 216 may adjust and manage transmit power levels of the activated transceivers.


In another example, the network management engine 216 may perform frequency and channel assignment, and beamforming without interfering with one another. In this regard, frequency hoping and beam pattern hopping may be utilized in frequency and channel assignment, and beamforming, respectively. In addition, the network management engine 216 may allocate resources and select beam patterns for the activated transceivers based on the physical locations of the activated transceivers. For example, narrow beams may be selected for devices in close proximity, and wide beams may be selected for devices that may be further away, respectively. For transmission, the network management engine 216 may set low transmit power for data transmission to close devices, and high transmit power for further devices, respectively. The exemplary process continues in step 910, where the master application device 210 may communicate subsequent data streams with the end-user devices 220-230 utilizing the allocated resources.


Aspects of a method and system for centralized resource management in a distributed transceiver network are provided. In accordance with various exemplary embodiments of the invention, as described with respect to FIG. 1 through FIG. 9, a device such as the master application device 210 comprises a plurality of distributed transceivers 212a-212e, the central baseband processor 214 and the network management engine 216. The plurality of distributed transceivers 212a-212e may be connected to the central baseband processor 214 and the network management engine 216 in the central processor 217 in a star topology or a ring topology as shown in FIGS. 4 and 5, respectively. The master application device 210 may be operable to communicate data streams that may comprise various multimedia information such as, for example, images, video, voice, as well as any other form of data utilizing one or more distributed transceivers selected from the plurality of the distributed transceivers 212a-212e to one or more other devices such as the end-user application devices 220-230. The network management engine 216 may concurrently configure the selected one or more distributed transceivers, for example, the distributed transceivers 212a-212c, and the end-user application devices 220-230 based on corresponding link quality and propagation environment during the data communication.


In an exemplary embodiment of the invention, the network management engine 216 may track the use and availability of resources such as, for example, frequency and channel, time slots, processors and storage in the communication network 100 during data communication. The network management engine 216 may allocate and manage resources through transmit power control, frequency hopping and/or beam pattern hopping to reduce outside electrical or RF interference during the data communication. The entire collection of the distributed transceivers 212a-212e may be communicatively coupled to the central processor 217 in a star topology or a ring topology. The central baseband processor 214 may be operable to perform digital signal processing needed for transmit and receive operations for the selected one or more distributed transceivers 212a-212c. During the data communication, the network management engine 216 may be operable to monitor or scan communication environment information such as, for example, propagation environment conditions, link quality, device capabilities, usage of resources, available resources, device locations, target throughput, and/or application QoS requirements. In an exemplary embodiment of the invention, the network management engine 216 may identify directions and antenna patterns that results in strong receive signals and/or a maximal coverage at the receiving devices such as the end-user application device 220 based on the corresponding propagation environment conditions and link quality.


The network management engine 216 may be operable to configure beamforming settings and/or antenna arrangement for the selected one or more distributed transceivers 212a-212c based on the identified directions and antenna patterns, device orientation, and/or receiver locations. For example, the network management engine 216 may select beam patterns for the selected distributed transceivers so as to minimize power consumption. In another example, the network management engine 216 may select beam patterns for the selected distributed transceivers based on the location and orientation information of the end-user application devices 220-230. In this regard, the network management engine 216 may identify the location and orientation information of the end-user application devices 220-230 through beaconing transmitted from the end-user application devices 220-230 utilizing Bluetooth and/or WLAN.


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 centralized or distributed resource management 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.

Claims
  • 1. A method of processing signals, the method comprising: in a first device that comprises a plurality of distributed transceivers, a central baseband processor and a network management engine: communicating data streams utilizing one or more of said plurality of distributed transceivers to a second device; anddetermining power levels of said one or more of said plurality of distributed transceivers and said second device based on link quality and propagation environment during communication,wherein said link quality is associated with a link between said plurality of distributed transceivers and said second device; anddistributing said power levels to at least one of said plurality of distributed transceivers, said first device, or said second device,wherein said power levels are distributed based on an optimization function of a throughput of a plurality of active transceivers of said plurality of distributed transceivers and said power levels, wherein a relationship of said throughput of said plurality of active transceivers and said power levels is defined in a look-up table,modifying the optimization function based on a cross-interference between a plurality of different links between said plurality of distributed transceivers and said second device; andutilizing said modified optimization function to find said plurality of active transceivers of said plurality of distributed transceivers such that a throughput of said found plurality of active transceivers exceeds a desired throughput value.
  • 2. The method according to claim 1, comprising allocating resources by said network management engine, to said first device and said second device during said communication.
  • 3. The method according to claim 2, wherein said resource allocating comprises at least one of frequency hopping, beam pattern hopping, or transmit power controlling.
  • 4. The method according to claim 1, wherein said plurality of distributed transceivers are communicatively coupled to said central baseband processor and said network management engine in a star topology.
  • 5. The method according to claim 1, comprising digital signal processing by said central baseband processor for transmit and receive operations for each of said one or more of said plurality of distributed transceivers during said communication.
  • 6. The method according to claim 1, comprising monitoring by said network management engine, said link quality and said propagation environment during said communication.
  • 7. The method according to claim 6, comprising configuring beamforming settings and antenna arrangement for said one or more of said plurality of distributed transceivers based on said monitoring.
  • 8. The method according to claim 7, comprising selecting beam patterns for said beamforming settings by minimizing power consumption.
  • 9. The method according to claim 7, comprising selecting beam patterns for said beamforming settings based on corresponding locations of said second device.
  • 10. The method according to claim 9, wherein said corresponding locations of said second device are identified based on at least one of Bluetooth or wireless local area network (LAN).
  • 11. A system for processing signals, the system comprising: a first device that comprises a plurality of distributed transceivers, a central baseband processor and a network management engine, said first device is operable to: communicate data streams utilizing said one or more of said plurality of distributed transceivers to a second device; anddetermine power levels of said one or more of said plurality of distributed transceivers and said second device based on link quality and propagation environment during said communication,wherein said link quality is associated with a link between said plurality of distributed transceivers and said second device; anddistribute said power levels to at least one of said plurality of distributed transceivers, said first device, or said second device,wherein said power levels are distributed based on an optimization function of a throughput of a plurality of active transceivers of said plurality of distributed transceivers and said power levels, wherein a relationship of said throughput of said plurality of active transceivers and said power levels is defined in a look-up table,modify the optimization function based on a cross-interference between a plurality of different links between said plurality of distributed transceivers and said second device; andutilize said modified optimization function to find said plurality of active transceivers of said plurality of distributed transceivers such that a throughput of said found plurality of active transceivers exceeds a desired throughput value.
  • 12. The system according to claim 11, wherein said network management engine allocates resources to said first device and said second device during said communication.
  • 13. The system according to claim 12, wherein said resource allocating comprises at least one of frequency hopping, beam pattern hopping, or transmit power controlling.
  • 14. The system according to claim 11, wherein said plurality of distributed transceivers are communicatively coupled to said central baseband processor and said network management engine in a star topology.
  • 15. The system according to claim 11, wherein said central baseband processor of said first device is operable to perform digital signal processing for transmit and transmit and receive operations for each of said one or more of said plurality of distributed transceivers during said communication.
  • 16. The system according to claim 11, wherein said network management engine of said first device is operable to monitor said link quality and said propagation environment during said communication.
  • 17. The system according to claim 16, wherein said network management engine of said first device is operable to configure beamforming settings and antenna arrangement for said one or more of said plurality of distributed transceivers based on said monitoring.
  • 18. The system according to claim 17, wherein said first device is further operable to select beam patterns for said beamforming settings by minimizing power consumption.
  • 19. The system according to claim 17, wherein said first device is further operable to select beam patterns for said beamforming settings based on corresponding locations of said second device.
  • 20. The system according to claim 19, wherein said corresponding locations of said second device are identified based on at least one of Bluetooth or wireless local area network (LAN).
CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This Patent Application 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, and is a Continuation Application of U.S. patent application Ser. No. 15/229,135, filed on Aug. 5, 2016, which is a Continuation Application of U.S. patent application Ser. No. 14/455,859, filed on Aug. 8, 2014, which is a Continuation Application of U.S. patent application Ser. No. 13/473,105, filed on May 16, 2012. This application makes reference to: U.S. application Ser. No. 13/473,096, filed on May 16, 2012, now issued as U.S. Pat. No. 9,112,648; U.S. application Ser. No. 13/473,144, filed on May 16, 2012, now published as U.S. Patent No. 2013/0095747; U.S. application Ser. No. 13/473,160, filed on May 16, 2012, now published as U.S. Patent No. 2013/0095874; U.S. application Ser. No. 13/473,180, filed on May 16, 2012, now issued as U.S. Pat. No. 8,780,943; U.S. application Ser. No. 13/473,113, filed on May 16, 2012, now issued as U.S. Pat. No. 9,225,482; and U.S. application Ser. No. 13/473,083, filed on May 16, 2012, now issued as U.S. Pat. No. 9,037,094. Each of the above stated applications is hereby incorporated herein by reference in its entirety.

US Referenced Citations (378)
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 Jun 2002 B1
6433920 Welch et al. Aug 2002 B1
6456252 Goyette Sep 2002 B1
6487417 Rossoni et al. Nov 2002 B1
6577631 Keenan Jun 2003 B1
6600776 Alamouti et al. Jul 2003 B1
6718159 Sato Apr 2004 B1
6802035 Catreux Oct 2004 B2
6804491 Uesugi Oct 2004 B1
6992622 Chiang et al. Jan 2006 B1
7020482 Medvedev 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 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 Feb 2011 B2
7904117 Doan Mar 2011 B2
7911985 Proctor, Jr. et al. Mar 2011 B2
7920889 Hoshino Apr 2011 B2
7986742 Ketchum et al. Jul 2011 B2
8014366 Wax Sep 2011 B2
8045638 Grant Oct 2011 B2
8098752 Hwang Jan 2012 B2
8121235 Sun et al. Feb 2012 B1
8126408 Ahrony Feb 2012 B2
8140122 Park Mar 2012 B2
8160601 Veselinovic Apr 2012 B2
8175184 Kim et al. May 2012 B2
8190102 Rofougaran May 2012 B2
8203978 Walton Jun 2012 B2
8228188 Key et al. Jul 2012 B2
8279132 Jung et al. Oct 2012 B2
8280445 Yong Oct 2012 B2
8314736 Moshfeghi Nov 2012 B2
8320304 Deb Nov 2012 B2
8364188 Srinivasan Jan 2013 B2
8369791 Hafeez Feb 2013 B2
8385305 Negus et al. Feb 2013 B1
8385452 Gorokhov Feb 2013 B2
8396157 Li 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 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
9277510 Wang Helmersson Mar 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
10355720 Shattil 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 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
20090092120 Goto Apr 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
20090191910 Athalye 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 et al. 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 et al. Dec 2010 A1
20100328157 Culkin et al. Dec 2010 A1
20110002410 Forenza 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 Apr 2012 A1
20120083223 Li et al. Apr 2012 A1
20120083225 Rofougaran Apr 2012 A1
20120083233 Rofougaran Apr 2012 A1
20120083306 Rofougaran 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
20190020402 Gharavi et al. Jan 2019 A1
20190074942 Moshfeghi Mar 2019 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
Foreign Referenced Citations (10)
Number Date Country
1890441 Feb 2008 EP
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
2016115545 Oct 2016 WO
Non-Patent Literature Citations (268)
Entry
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.
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. No. 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. 16/129,413 dated Aug. 13, 2019.
Final Office Action for U.S. Application Serial 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/58839, 6 pages, dated Apr. 4, 2013.
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 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. Han and K. Huang, “Wirelessly Powered Backscatter Communication networks: Modeling, Coverage and Capacity,” Apr. 9, 2016, Arxiv.com.
List of References 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.
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/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/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.
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.
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.
Supplemental Notice of Allowance for U.S. Appl. No. 16/032,668 dated Feb. 14, 2020.
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.
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/153,735 dated May 13, 2020.
Non-Final Office Action for U.S. Appl. No. 16/364,956 dated Apr. 10, 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/364,956 dated Dec. 11, 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/364,956 dated Jan. 6, 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.
Supplemental Notice of Allowability for U.S. Appl. No. 16/153,735 dated Jan. 11, 2021.
Notice of Allowability for U.S. Appl. No. 15/607,750 dated Jan. 11, 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/451,998 dated Jan. 14, 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.
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.
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.
Notice of Allowability for U.S. Appl. No. 16/129,413 dated Feb. 18, 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/666,680 dated Mar. 2, 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 Allowance for U.S. Appl. No. 16/927,470 dated Feb. 2, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/388,043 dated Feb. 8, 2021.
Notice of Allowance for U.S. Appl. No. 16/866,536 dated Jan. 29, 2021.
Supplemental Notice of Allowance for U.S. Appl. No. 16/941,690 dated May 18, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/204,397 dated Apr. 28, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/204,397 dated Jun. 7, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/233,044 dated Jun. 11, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/354,390 dated Apr. 9, 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/364,956 dated May 6, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/388,043 dated Apr. 15, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/689,758 dated Apr. 29, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/689,758 dated Apr. 7, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/689,758 dated May 27, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/866,536 dated Apr. 29, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/927,470 dated Apr. 29, 2021.
First Office Action for U.S. Appl. No. 16/233,044 dated Apr. 19, 2021.
Final Office Action for U.S. Appl. No. 16/398,156 dated Apr. 19, 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. 28, 2021.
Notice of Allowability for U.S. Appl. No. 16/819,388 dated Apr. 5, 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.
Notice of Allowance for U.S. Appl. No. 16/377,847 dated Apr. 5, 2021.
Notice of Allowance for U.S. Appl. No. 16/388,043 dated May 7, 2021.
Notice of Allowance for U.S. Appl. No. 16/391,628 dated Mar. 17, 2021.
Notice of Allowance for U.S. Appl. No. 16/451,980 dated Mar. 23, 2021.
Notice of Allowance for U.S. Appl. No. 16/941,690 dated May 5, 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/452,023 dated Apr. 30, 2021.
Supplemental Notice of Allowance for U.S. Appl. No. 16/666,680 dated Jun. 10, 2021.
Supplemental Notice of Allowance for U.S. Appl. No. 16/866,536 dated Jun. 7, 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/364,956 dated Jun. 23, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/377,847 dated Jul. 6, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/391,628 dated Jun. 29, 2021.
Corrected Notice of Allowance for U.S. Appl. No. 16/689,758 dated Jul. 6, 2021.
Final Office Action for U.S. Appl. No. 17/011,042 dated Jul. 2, 2021.
Non-Final Office Action for U.S. Appl. No. 17/091,520 dated Jul. 8, 2021.
Notice of Allowance for U.S. Appl. No. 16/398,156 dated Jul. 6, 2021.
Supplemental Notice of Allowance for U.S. Appl. No. 16/451,980 dated Jun. 30, 2021.
Supplemental Notice of Allowance for U.S. Appl. No. 16/451,998 dated Jun. 24, 2021.
Supplemental Notice of Allowance for U.S. Appl. No. 16/666,680 dated Jul. 9, 2021.
Related Publications (1)
Number Date Country
20190074942 A1 Mar 2019 US
Provisional Applications (1)
Number Date Country
61548201 Oct 2011 US
Continuations (3)
Number Date Country
Parent 15229135 Aug 2016 US
Child 16125757 US
Parent 14455859 Aug 2014 US
Child 15229135 US
Parent 13473105 May 2012 US
Child 14455859 US