Patent Publication Number: US-2022232396-A1

Title: Installation of repeaters for a millimeter wave communications network

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application is a Utility patent application based on previously filed U.S. Provisional Patent Application No. 63/138,306 filed on Jan. 15, 2021, the benefit of the filing date of which is hereby claimed under 35 U.S.C. § 119(e) and the contents of which is further incorporated in entirety by reference. 
    
    
     TECHNICAL FIELD 
     The invention relates generally to employing directional antennas placed on structures, such as poles, or buildings, that provide a wireless network for communicating RF signals between user devices and remotely located resources. Further, in some embodiments, the directional antennas may be installed at the premises of a customer and coupled to base stations and RF signal repeater devices to manage operation of a millimeter wave communications network. 
     BACKGROUND 
     Mobile devices have become the primary mode of wireless communication for most people throughout the world. In the first few generations of wireless communication networks, mobile devices were generally used for voice communication, text messages, and somewhat limited internet access. Newer generations of wireless communication networks have increased bandwidth and lowered latency enough to provide substantially more services to mobile device users, such as purchasing products, paying invoices, streaming movies, playing video games, online learning, dating, and more. Also, for each new generation of wireless communication network, the frequency and strength of the wireless signals are generally increased to provide even more bandwidth with less latency. 
     Unfortunately, the higher a frequency of a wireless signal, the greater the attenuation of wireless signals passing through physical barriers and over shorter distances than lower frequency wireless signals. Moreover, since the recent rollout of 5th generation (5G) wireless communication networks that can use wireless signals with millimeter waveforms at gigahertz frequencies, it has become even more difficult to design and install 5G wireless networks that provide optimized access for mobile devices due to these physical barriers. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  depicts an illustrative scenario for providing wireless service to a multiple-dwelling unit (MDU). 
         FIG. 2  depicts wireless coverage for a portion of a polygon of potential subscribers with only gNBs. 
         FIG. 3  depicts wireless coverage for the same portion of the polygon of potential subscribes with gNBs, open-air repeaters, and window repeaters. 
         FIG. 4  depicts efficiency scenarios for various deployments of gNBs, open-air repeaters, and window repeaters. 
         FIG. 5  depicts a process flow for recommending locations of repeaters. 
         FIG. 6  shows an exemplary computer device that may be included in a system in accordance with the various embodiments. 
     
    
    
     DESCRIPTION OF VARIOUS EMBODIMENTS OF THE INVENTION 
     The present invention now will be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of illustration, specific embodiments by which the invention may be practiced. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Among other things, the present invention may be embodied as methods or devices. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. The following detailed description is, therefore, not to be taken in a limiting sense. 
     Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise. The phrase “in one embodiment” as used herein does not necessarily refer to the same embodiment, though it may. Similarly, the phrase “in another embodiment” as used herein does not necessarily refer to a different embodiment, though it may. As used herein, the term “or” is an inclusive “or” operator, and is equivalent to the term “and/or,” unless the context clearly dictates otherwise. The term “based on” is not exclusive and allows for being based on additional factors not described, unless the context clearly dictates otherwise. In addition, throughout the specification, the meaning of “a,” “an,” and “the” include plural references. The meaning of “in” includes “in” and “on.” 
     The following briefly describes the embodiments of the invention to provide a basic understanding of some aspects of the invention. This brief description is not intended as an extensive overview. It is not intended to identify key or critical elements, or to delineate or otherwise narrow the scope. Its purpose is merely to present some concepts in a simplified form as a prelude to the more detailed description that is presented later. 
     Briefly stated, various embodiments of the invention are directed to a method, apparatus, or system that provides a suite of devices and software tools executing on a computing device, e.g., a distributed cloud computing platform, a desktop computer, a notebook computer or a mobile device. One or more of the various embodiments of the devices and tools enable a user, such as a carrier, to extend millimeter wave coverage for wireless communication networks while reducing costs and optimizing coverage for different environments. In one or more of the various embodiments, the devices may include outdoor network repeaters, e.g., the Pivot 5G™, and indoor subscriber repeaters, e.g., the Echo 5G™. Also, in one or more embodiments, the software tools may include a beam management system, e.g., Pivotal Commware&#39;s Intelligent Beam Management System (IBMS), and an application, e.g., WaveScape™, for modeling and optimizing the placement of the Pivot 5G, Echo 5G, and other mmWave network transmitter devices in a mmWave network. In one or more of the various embodiments, WaveScape may orchestrate the other tools and devices by allowing carriers to plan their mmWave networks and quantify both the physical and economic impact each component has on the network. 
     Overview 
     Millimeter wave (mmWave) communication networks can deliver on low-latency applications that subscribers expect from 5G and on the capacity that carriers need to deliver for their subscribers. Limited line-of-sight (LOS) conditions and propagation challenges associated with mmWave dictate denser networks than ever before, and significant planning is required to balance densification with responsible capex. Legacy macro cell planning tools are not up to the task of modeling the small cell deployments, and many of the fundamental assumptions break down when simulating mmWave. To fully unlock the potential of this spectrum, carriers need an accurate and scalable modeling tool that is built natively on the physics of mmWave. 
     In some approaches, a mmWave ecosystem of products extends millimeter wave coverage at a fraction of the cost of gNB-only networks. This ecosystem can include at least two types of smart repeaters (an outdoor network repeater such as the Pivot 5G and an indoor subscriber repeater such as the Echo 5G), plus an internet-of-things (IoT) management system such as the Intelligent Beam Management System (IBMS), plus a software solution (hereinafter referred to as WaveScape) for modeling and optimizing the placement of Pivot 5G, Echo 5G, and all other mmWave network transmitters. WaveScape orchestrates this ecosystem, allowing users to plan their mmWave networks and quantify both the physical impact and efficiency of each component of the network. 
     In some approaches WaveScape is a network planning platform built with the needs of 5G mmWave and Fixed Wireless Access (FWA) at its core. It can model any set of network elements, including network repeaters such as holographic beamforming (HBF) network repeaters, and allows users to explore the tradeoffs different network deployment strategies. Furthermore, WaveScape can ingest high resolution GIS data, utilize propagation models such as 3GPP propagation models, and run natively in the cloud. This allows it to make accurate and deterministic predictions with near-infinite scalability. 
     FWA QUALIFICATION: WaveScape can ingest the network elements that have been deployed within a region as well as the physical layout of that region. The tool then identifies buildings that likely-subscribers occupy and determines the coverage level within and just outside the building, thus allowing carriers to qualify them for FWA based on minimum signal-level, antenna beamwidth, and placement requirements of different customer premise equipment (CPE). 
     NETWORK PLACEMENT OPTIMIZATION: WaveScape can allow users to set coverage targets for a region—which can be based on FWA scenarios or mobility scenarios. By ingesting utility poles, lampposts, and public building corners that a carrier may have access to, the tool can recommend placement and orientation of new network elements (including, e.g., Echo 5G, Pivot 5G, gNBs, or other equipment in use by the carrier) to reach a given target coverage level. 
     Furthermore, the tool can dynamically ingest and re-optimize based on updated real estate requirements, new target metrics, and newly deployed equipment. Recommendations can be based on efficiency per incremental coverage basis, and the tool allows users to update and refine their efficiency models. 
     DEPLOYMENT STRATEGY &amp; UNIT EFFICIENCY EXPLORATION: WaveScape allows carriers to explore different hypothetical deployment scenarios so they can uncover the most effective deployment strategy for a specific region. By tracking the incremental coverage of each network element, a carrier will be able to select efficient coverage targets for each region. Furthermore, WaveScape&#39;s ability to ingest specifications for any network element allows carriers to compare the efficiency features of all available equipment—including, e.g., both Pivot 5G and Echo 5G equipment. 
     Illustrative Scenario 
     With reference now to  FIG. 1 , an illustrative scenario is depicted. Various approaches involve identifying one or more potential recipients of wireless communications, and then recommending placements of repeaters to deliver signals between one or more wireless base stations and the one or more potential recipients. In this illustrative scenario, the one or more potential recipients are individual residences or premises  101 - 109  within a multiple dwelling unit (MDU)  100 , with respective windows  101 A- 109 A arranged along the exterior of the multiple dwelling unit  100 . While the illustrative scenario depicts multiple premises within a single multiple dwelling unit, other approaches involve a set of single dwelling units, or a combination of single dwelling units and multiple dwelling units. Alternatively or additionally, approaches can include identifying one or more desired coverage regions for mobile recipients, e.g. pedestrians or vehicle occupants who are using mobile devices such as mobile phones. 
     In the illustrative scenario of  FIG. 1 , a wireless base station  110  is positioned north of the northwest corner of the MDU  100 . The wireless base station could be, for example, a 5G gNB base station for mmW communications with recipients within a coverage area of the base station. In some approaches, the location of the wireless base station  110  is predetermined, e.g., previously selected and installed by a wireless service provider. In other approaches, as further discussed below, the WaveScape platform can recommend the placement of the wireless base station to efficiently provide optimized coverage within a selected service area. 
     In the illustrative scenario, the wireless base station  110  can directly provide service to premises  101  and  102  via lines of sight  121  and  122 . The wireless base station  110  also has a direct line of sight  123  with premises  103 ; however, given the relatively oblique angle of incidence between line of sight  123  and window  103 A, it may be desirable, in some approaches, to install a window repeater  103 B in window  103 A. In general, the Wavescape platform may recommend placement of a window repeater when the signal strength is sufficiently low and/or when the angle of incidence is sufficiently oblique. 
     Generally speaking, a window repeater, such as element  103 B in  FIG. 1 , is a device installed on a window and configured to receive signals from a wireless base station (or from another repeater) and rebroadcast the received signals to premises behind the window. For two-way communication, the window repeater can also receive signals from the premises behind the window and rebroadcast them to a wireless base station (or another repeater) outside the window. The window repeater can be entirely mounted on the outside of the window, or entirely mounted on the inside of the window, or it can have exterior and interior portions that adjoin exterior and interior surfaces of the window. In some approaches, the window repeater includes a donor antenna that can be adjusted to point a beam at the relevant wireless base station (or other repeater) outside of the premises, and a service antenna providing a beam that covers the interior of the premises. The donor antenna and/or the service antenna can be electronically adjustable antennas such as holographic beamforming antennas. Various window repeater structures are described, for example, in U.S. Pat. Nos. 10,425,905 and 11,069,975, which are herein incorporated by reference. 
     In the illustrative scenario of  FIG. 1 , an obstruction  130  prevents a line of sight between the base station  100  and premises  104 . The obstruction could be, for example, a tree or other vegetation, or some other physical structure such as a building or tower, or an interference source such as a base station from another wireless service provider. The obstruction  130  is depicted as a tree but this is a schematic depiction and is not intended to be limiting. 
     The WaveScape platform may recommend placement of an open-air repeater  141  to provide coverage to the premises  104 . For example, having ingested geographic information that includes information about the locations of posts, poles, building corners, or other structures suitable for placement of open-air repeaters, the WaveScape platform may recommend placement of open-air repeater  141  on structure  141 A, which could be a post, pole, building corner, or any other structure suitable for installation of an open-air repeater. 
     Generally speaking, an open-air repeater, such as element  141  in  FIG. 1 , is a device installed on a post, pole, building corner, or other structure and configured to receive signals from a wireless base station (or from another repeater) and rebroadcast the received signals. For example, the open-air repeater  141  can receive signals from wireless base station  101  via light of sight  124  and rebroadcast via line of sight  124 R to premises  104 . For two-way communication, the open-air repeater can also receive signals via line of sight  124 R and rebroadcast them to the wireless base station via line of sight  124 . In some approaches, the open-air repeater includes a donor antenna (e.g.,  141 D) that can be adjusted to point a beam at the relevant wireless base station (or other repeater), and a service antenna (e.g.  141 S) providing a beam that covers a rebroadcast service area, e.g., including the premises  104  via line of sight  124 R. The donor antenna and/or the service antenna can be electronically adjustable antennas such as holographic beamforming antennas. Various open-air repeater structures are described, for example, in U.S. Pat. Nos. 10,425,905; 11,190,266; and 11,206,055 which are herein incorporated by reference. 
     In the illustrative scenario of  FIG. 1 , the wireless base station  100 , being situated north of the northwest corner of MDU  100 , does not have a line of sight to provide service to units  105 - 109  on the west side of the MDU. In this context, the WaveScape platform may recommend placement of one or more open-air repeaters facing the west side of the MDU to provide service to the units  105 - 109 . For example, the WaveScape platform may recommend placement of open-air repeater  142  at selected post, pole, building corner, or other structure  142 S; and the WaveScape platform may further recommend placement of a second open-air repeater  143  at selected post, pole, building corner, or other structure  143 S. The more distant repeater  143  may be required to accommodate for signal attenuation between repeaters  142  and  143 , e.g., due to distance and/or the presence of attenuating features such as foliage. In this illustrative scenario, base station  110  broadcasts a signal  125  to open-air repeater  142 ; the signal  125  is rebroadcast via lines of sight  125 R 1 ,  125 R 2 ,  125 R 3  to premises  105 ,  106 , and  107 , respectively (with the  125 R 3  signal being further boosted by window repeater  107 B due to angle of incidence and/or insufficient signal strength of  125 R 3 ); and the signal  125  is rebroadcast via line of sight  125 R 4  to be doubly rebroadcast via lines of sight  125 RR 1  and  125 RR 2  to units  108  and  109 , respectively (with the  125 RR 2  signal being further boosted by window repeater  109 B due to angle of incidence and/or insufficient signal strength of  125 RR 2 ). 
     Example 1: Multiple-Dwelling Unit 
     As a first validation of the utility of the WaveScape platform, a multiple-dwelling unit (MDU) was identified and targeted for fixed wireless access in each dwelling unit. The identified MDU is ten stories high and contains 70 units (7 units per floor). All units have a window on the west side of the building. 
     Wavescape models the baseline coverage of the gNBs and predicts both mobility coverage and FWA qualification. Using 3GPP propagation models on the highest-available resolution GIS data, the tool sees that while the northern face of the building has coverage, most of the potential subscribers (having windows on the west side of the building) are left in the dark. This prediction is validated by live measurements in the field, showing little to no coverage on the west face of the building. 
     WaveScape then ingests all the lampposts, utility poles, building corners, and any other locations in the area where open-air repeaters (e.g., Pivot repeaters) can be mounted. It then automatically calculates which of these candidate locations have adequate signal for the open-air repeaters to repeat, ensuring the repeaters&#39; effectiveness. In this scenario, WaveScape has determined that the pole closer to the MDU does not have line of sight to the gNB, and thus is not eligible for an open-air repeater, but the poles across the street and to the southwest of the building do have sufficient coverage. 
     Now that WaveScape has found two poles in the area where a Pivot can be placed, it optimizes the configuration and orientation of the repeaters to provide maximum coverage at the least cost. WaveScape has found a configuration where only one of the poles is needed to provide coverage, saving the cost of an extra repeater on the other pole for the carrier. 
     When WaveScape&#39;s recommended configuration was put to the test at this MDU, its coverage level predictions were accurate, and it correctly qualified 100% of the units on the west face of the building. 
     Example 2: Polygon of Potential Subscribers 
     As a second validation of the utility of the WaveScape platform, a 1.5 square mile polygon containing 29 gNBs and 4900 potential subscribers was identified and targeted for fixed wireless access in each dwelling unit. 
     As was done in the previous example, WaveScape ingests all gNodeB locations and orientations within the polygon. It then evaluates mmWave coverage based on 3GPP models and high-resolution GIS data. This modeling calculation identified 1700 units with adequate coverage for FWA, or 35% of all dwelling units within the polygon. 
       FIG. 2  depicts the result of this modeling for a portion of the polygon, showing that only the buildings at the top of the figure, near the gNB at top center, have adequate coverage for FWA. 
     To boost FWA enablement and mobility coverage, existing utility poles were made available by the local power company to mount open-air repeaters (e.g. Pivot repeaters). The locations and heights of over 5000 poles within the polygon were ingested by WaveScape. WaveScape identified 1750 poles that are covered by the existing gNBs. WaveScape also accounts for “two hop” scenarios, where a gNB provides coverage to a repeater, which then provides coverage to a second repeater thus further extending the network range and allowing the tool to qualify an additional 1250 poles (a “two hop” scenario is schematically depicted for repeater  143  in  FIG. 1 , as discussed above). 
     WaveScape can allow the user to define an optimal deployment strategy logic by looking at outdoor coverage, FWA enablement, and/or indoor coverage. In the present example, the network is optimized for FWA enablement using window repeaters (e.g. Echo repeaters) as customer premises equipment (CPE). With this optimization goal, WaveScape utilizes cloud computing to determine the optimal repeater locations and orientations based on the coverage outcomes. In some approaches, WaveScape can be a cloud-native application with near-infinite scalability to optimize coverage for polygons of any shape or size. Out of the more than 3000 eligible open-air repeater locations available in this scenario, WaveScape selected 171 open-air repeater locations, which allowed for 90% of units within the polygon to be enabled for FWA. 
       FIG. 3  depicts the result of this optimization example for the same polygon portion that was depicted in  FIG. 2 , as discussed above. As a result of the optimization, open-air repeaters are variously positioned on utility poles within the polygon, as indicated by the repeater locations “P” in the figure. With the addition of these repeaters, and with the further addition of window repeaters (e.g. Echo devices), service can be provided to every premises within the polygon portion as shown. 
     Some premises (shaded as “gNB only”) receive service directly via communication with the gNB. These are analogous to premises  101  and  102  in the schematic example of  FIG. 1 . Other premises (shaded as “Echo only”) receive service via communication with the gNB that is boosted by a window repeater such as an Echo device. These are analogous to premises  103  in the schematic example of  FIG. 1 . Other premises (shaded as “Pivot only”) receive service via communication with the gNB that is repeated by a single open-air repeater such as a Pivot device. These are analogous to premises  104 ,  105 , and  106  in the schematic example of  FIG. 1 . Other premises (shaded as “Pivot+Echo”) receive service via communication with the gNB that is repeated by a single open-air repeater such as a Pivot device and then boosted by a window repeater such as an Echo device. These are analogous to premises  107  in  FIG. 1 . Finally, other premises (shaded as “2hop+Echo”) receive service via communication with the gNB that is repeated by a series of two-open air repeaters such as Pivot devices and then boosted by a window repeater such as an Echo device. These are analogous to premises  109  in  FIG. 1 . 
     Efficiency Analysis 
     By tracking the individual contributions of each gNB and repeater within the network, WaveScape can compare the number of repeaters needed to achieve different target coverage levels. For the polygon of Example 2, alongside the 29 gNB, 56 open-air repeaters were required to reach 70% coverage, while 171 open-air repeaters were required to reach 90% coverage, meaning that it may be more efficient to target 70% coverage for this polygon. 
     In some approaches, WaveScape can be used to test many different hypothetical scenarios. For example, by removing the 5 least impactful gNBs from the polygon being considered, 70% coverage required 24 gNBs+63 open-air repeaters. While more Pivots are required than in the 29 gNB scenario, trading 5 gNBs for 7 Pivots was a more efficient deployment strategy overall. 
     With reference now to  FIG. 4 , several illustrative efficiency scenarios are depicted, plotting the cost of deployment on the horizontal axis versus the estimated coverage percentage on the vertical axis. The triangles indicate the initial deployment of 29 gNBs as discussed above in Example 2. With 29 gNBs already deployed, the diamonds indicate the additional coverage obtained by adding open-air repeaters. It can be seen that adding the open-air repeaters increases the total cost of deployment, but with greater incremental improvement in coverage percentage compared to, say, adding the 29th gNB. 
     In one efficiency scenario, the 5 least effective gNBs are removed. Then, with 24 gNBs already deployed, the squares indicate the additional coverage obtained by adding open-air repeaters. Again, it can be seen that adding the open-air repeaters increases the total cost of deployment, but with greater incremental improvement in coverage percentage compared to, say, adding the 24th gNB. 
     Taking this further, in another efficiency scenario, the 10 least effective gNBs are removed. Then, with 19 gNBs already deployed, the stars indicate the additional coverage obtained by adding open-air repeaters. Again, it can be seen that adding the open-air repeaters increases the total cost of deployment, but with greater incremental improvement in coverage percentage compared to, say, adding the 19th gNB. 
     The diamond, square, and star plots illustrate the trend of greater efficiency when fewer gNBs are previously deployed and WaveScape can optimize locations of more open-air repeaters. Taking this to a logical extreme, in one approach, no gNBs are previously deployed and WaveScape can optimize the locations of both the gNBs and the open-air repeaters. This can be referred to as a “green field” optimization of coverage for a selected set of potential subscribers in a selected service area such as the polygon of Example 2. In  FIG. 4 , the leftmost curve indicates an example of this optimization, with each cross (+) indicating a gNB located as recommended by WaveScape, and each dot indicating an open-air repeater (such as a Pivot device) located as recommended by WaveScape. 
     Process Flows 
     With reference now to  FIG. 5 , an illustrative embodiment is depicted as a process flow diagram. The process  500  includes operation  510 —identifying locations of one or more potential recipients of mmW communications. For example, the operation  510  can include, as in  FIG. 1 , identifying the locations of premises  101 - 109  within a multiple dwelling unit (MDU); or, as in  FIGS. 2 and 3 , identifying locations of potential wireless service subscribers within a service area. In some approaches, the identifying of the locations of the potential recipients is an identifying of one or more desired coverage regions for mobile recipients, e.g., pedestrians or vehicle occupants who are using mobile wireless devices such as mobile phones. 
     The process  500  further includes operation  520 —identifying locations of one or more wireless base stations for the mmW communications or recommending locations of one or more wireless base stations for the mmW communications. If the operation includes identifying these locations, the identifying can include receiving a catalog of locations and orientations of previously-installed wireless base stations, e.g., gNBs. If the operation includes recommending these locations, the recommending can include recommending locations of wireless base stations, e.g., gNBs, to optimize coverage within a desired service area. For example, the operation can include recommending locations and orientations of gNBs according to a “green field” optimization algorithm as discussed above. 
     The process  500  further includes operation  530 —recommending placements of repeaters to deliver signals between one or more wireless base stations and the one or more potential recipients. For example, the operation can include recommending placements of open-air repeaters  141 ,  142 , and  143  and placements of window repeaters  103 B,  107 B, and  109 B as in  FIG. 1 . As another example, the operation can include recommending placements of open-air repeaters “P” as in  FIG. 3 . 
     Operation  530  can include sub-operation  5310 —receiving geographical information about a region that encloses the one or more wireless base stations and the one or more potential recipients. For example, sub-operation  5310  can include ingesting geographical information from a geographical information system (GIS) database. The GIS database can include, e.g., information about the ground topography, the footprints and heights of buildings or other man-made structures, and the locations and heights of trees or other vegetation. The GIS database information can include information about, e.g., density or species of vegetation, building materials (e.g., whether a building is wood frame or concrete-and-steel), locations of roads, building uses (e.g., whether a building is residential or commercial or mixed-use), population density, and local internet connective speeds. 
     Sub-operation  5310  can include sub-sub-operation  5311 —receiving information about the locations of posts, poles, building corners, or other structures suitable for placement of open-air repeaters. For example, the GIS database can include information about the locations of posts, poles, corners, etc., or the GIS database can be supplemented with a catalog of this information, or machine learning algorithms can be used to identify potential locations of posts, poles, corners, etc. The received information about the locations of posts, poles, corners, etc. can include zoning, regulatory, and/or utility information about the availability and suitability of these locations for placement of open-air repeaters. The received information can include, e.g., information about the height, previously-installed equipment, comm-zone availability, and ownership of a given pole. In some approaches, the received information can include information about regions where a pole is not presently installed but could be installed. 
     Sub-operation  5310  can include sub-sub-operation  5312 —receiving information about the locations and/or orientations of windows suitable for placement of window repeaters. For example, the GIS database can include information about the coordinates, altitudes, and orientations of windows on buildings (commercial buildings, single dwelling units, and multiple dwelling units), or the GIS database can be supplemented with a catalog of this information, or machine learning algorithms can be used to identify windows on buildings. The received information about windows can include information about, e.g., the field of view from the window into the premises (e.g., whether the window is a bedroom window or a living room window) and information about the wireless signal transmissibility of the window (e.g., whether the window is low-E glass). 
     Operation  530  can include sub-operation  5320 —using the received geographical information to determine line of sight regions for the wireless base stations and/or the open-air repeaters. For example, the geographical information can include information about buildings or other man-made structures that can impede the line of sight of a wireless base station or open-air repeater. This can be especially relevant in dense urban environments, where city streets or avenues can be “urban canyons” that severely limit the line of sight of a given wireless base station or open-air repeater. The geographical information can also include information about natural terrain or foliage that can impede the line of sight of a wireless base station or open-air repeater. 
     Operation  530  can include sub-operation  5330 —using a wireless propagation model to determine signal strength with the line of sight regions for the wireless base stations and/or the open-air repeaters. For example, the operation can include using a 3GPP or other propagation model to account for attenuation due to distance, terrain, foliage, etc. Thus, the wireless propagation modelling can determine, e.g., the strength of a signal transmitted by a gNB base station and received by an open-air or window repeater, or the strength of a signal transmitted by a first open-air repeater and received by a window repeater or second open-air repeater. 
     Operation  530  can include sub-operation  5340 —selecting one or more locations for placement of the open-air repeaters. For example, the operation can include selecting locations for the placements of open-air repeaters  141 ,  142 , and  142  in  FIG. 1 , or the locations of open-air repeaters “P” in  FIG. 3 . 
     Operation  530  can include sub-operation  5350 —selecting one or more locations for placement of the window repeaters. For example, the operation can include selecting placements of window repeaters  103 B,  107 B, and  109 B on windows  103 A,  107 A, and  109 A, respectively, in  FIG. 1 , or in the windows of premises shaded as “Echo req,” “Pivot+Echo,” or “2-hop+Echo” in  FIG. 3 . 
     The process  500  can further include operation  540 —installing one or more of the repeaters according to the recommended placements. Thus, the process can include physically installing one or more of the open-air repeaters or window repeaters in the recommended locations. 
     Illustrative Computation Environment 
       FIG. 6  shows one embodiment of computer  650  that may include many more, or less, components than those shown. In one or more embodiments, the operation and/or configuration of computer  650  may be included in a distributed cloud computing platform, a remote computer or remote computing system, a local computer or local computing system, a desktop computer, a notebook computer or a mobile device. 
     Computer  650  may include processor  651  in communication with memory  652  via bus  660 . Computer  650  may also include power supply  661 , network interface  662 , audio interface  674 , display  671 , keypad  672 , illuminator  673 , video interface  667 , input/output interface  665 , haptic interface  678 , global positioning systems (GPS) receiver  675 , open air gesture interface  676 , temperature interface  677 , camera(s)  667 , projector  670 , pointing device interface  679 , processor-readable stationary storage device  663 , and processor-readable removable storage device  664 . Computer  650  may optionally communicate with a wireless base station (not shown), an wireless repeater device Snot shown) or directly with another computer. Power supply  661  may provide power to computer  650 . A rechargeable or non-rechargeable battery may be used to provide power. The power may also be provided by an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the battery. 
     Network interface  662  includes circuitry for coupling computer  650  to one or more networks, and it is constructed for use with one or more wired and/or wireless communication protocols and technologies. Examples of various generations (e.g., third (3G), fourth (4G), or fifth (5G) of communication protocols and/or technologies may include, but are not limited to, Global System for Mobile communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access 2000 (CDMA2000), High Speed Downlink Packet Access (HSDPA), Long Term Evolution (LTE), Universal Mobile Telecommunications System (UMTS), Evolution-Data Optimized (Ev-DO), Worldwide Interoperability for Microwave Access (WiMax), time division multiple access (TDMA), Orthogonal frequency-division multiplexing (OFDM), ultra-wide band (UWB), Wireless Application Protocol (WAP), 5G New Radio (5G NR), 5G Technical Forum (5G TF), 5G Special Interest Group (5G SIG), Narrow Band Internet of Things (NB IoT), user datagram protocol (UDP), transmission control protocol/Internet protocol (TCP/IP), various portions of the Open Systems Interconnection (OSI) model protocols, session initiated protocol/real-time transport protocol (SIP/RTP), short message service (SMS), multimedia messaging service (MMS), or various ones of a variety of other communication protocols and/or technologies. 
     Audio interface  674  may be arranged to produce and receive audio signals such as the sound of a human voice. For example, audio interface  674  may be coupled to a speaker and microphone (not shown) to enable telecommunication with others or generate an audio acknowledgement for some action. A microphone in audio interface  674  can also be used for input to or control of computer  650 , e.g., using voice recognition, detecting touch based on sound, and the like. 
     Display  671  may be a liquid crystal display (LCD), gas plasma, electronic ink, light emitting diode (LED), Organic LED (OLED) or any other type of light reflective or light transmissive display that can be used with a computer. Display  671  may also include a touch interface  668  arranged to receive input from an object such as a stylus or a digit from a human hand, and may use resistive, capacitive, surface acoustic wave (SAW), infrared, radar, or other technologies to sense touch or gestures. 
     Projector  670  may be a remote handheld projector or an integrated projector that is capable of projecting an image on a remote wall or any other reflective object such as a remote screen. 
     Video interface  667  may be arranged to capture video images, such as a still photo, a video segment, an infrared video, or the like. For example, video interface  667  may be coupled to a digital video camera, a web-camera, or the like. Video interface  667  may comprise a lens, an image sensor, and other electronics. Image sensors may include a complementary metal-oxide-semiconductor (CMOS) integrated circuit, charge-coupled device (CCD), or any other integrated circuit for sensing light. 
     Keypad  672  may comprise any input device arranged to receive input from a user. For example, keypad  672  may include a push button numeric dial, or a keyboard. Keypad  672  may also include command buttons that are associated with selecting and sending images. 
     Illuminator  673  may provide a status indication or provide light. Illuminator  673  may remain active for specific periods of time or in response to event messages. For example, when illuminator  673  is active, it may backlight the buttons on keypad  672  and stay on while the computer is powered. Also, illuminator  673  may backlight these buttons in various patterns when particular actions are performed, such as dialing another computer. Illuminator  673  may also enable light sources positioned within a transparent or translucent case of the computer to illuminate in response to actions. 
     Further, computer  650  may also comprise hardware security module (HSM)  669  for providing additional tamper resistant safeguards for generating, storing or using security/cryptographic information such as, keys, digital certificates, passwords, passphrases, two-factor authentication information, or the like. In some embodiments, hardware security module may be employed to support one or more standard public key infrastructures (PKI), and may be employed to generate, manage, or store keys pairs, or the like. In some embodiments, HSM  669  may be a stand-alone computer, in other cases, HSM  669  may be arranged as a hardware card that may be added to a computer. 
     Computer  650  may also comprise input/output interface  665  for communicating with external peripheral devices or other computers such as other computers and network computers. The peripheral devices may include an audio headset, virtual reality headsets, display screen glasses, remote speaker system, remote speaker and microphone system, and the like. Input/output interface  665  can utilize one or more technologies, such as Universal Serial Bus (USB), Infrared, WiFi, WiMax, Bluetooth™, and the like. 
     Input/output interface  665  may also include one or more sensors for determining geolocation information (e.g., GPS), monitoring electrical power conditions (e.g., voltage sensors, current sensors, frequency sensors, and so on), monitoring weather (e.g., thermostats, barometers, anemometers, humidity detectors, precipitation scales, or the like), or the like. Sensors may be one or more hardware sensors that collect or measure data that is external to computer  650 . 
     Haptic interface  678  may be arranged to provide tactile feedback to a user of the computer. For example, the haptic interface  678  may be employed to vibrate computer  650  in a particular way when another user of a computer is calling. Temperature interface  677  may be used to provide a temperature measurement input or a temperature changing output to a user of computer  650 . Open air gesture interface  676  may sense physical gestures of a user of computer  650 , for example, by using single or stereo video cameras, radar, a gyroscopic sensor inside a computer held or worn by the user, or the like. One or more cameras  666  may be used by an application to employ facial recognition methods to identify a user, track the user&#39;s physical eye movements, or take pictures (images) or videos. 
     GPS device  675  can determine the physical coordinates of computer  650  on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS device  675  can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference (E-OTD), Cell Identifier (CI), Service Area Identifier (SAI) Tracking Area Identifier (TAI), Enhanced Timing Advance (ETA), Base Station Subsystem (BSS), or the like, to further determine the physical location of computer  650  on the surface of the Earth. It is understood that GPS device  675  can employ a gyroscope to determine an orientation and/or an accelerometer to determine movement of the computer  650 . In one or more embodiment, however, computer  650  may, through other components, provide other information that may be employed to determine a physical location of the computer, including for example, a Media Access Control (MAC) address, IP address, and the like. 
     Human interface components can be peripheral devices that are physically separate from computer  650 , allowing for remote input or output to computer  650 . For example, information routed as described here through human interface components such as display  671  or keypad  672  can instead be routed through network interface  662  to appropriate human interface components located remotely. Examples of human interface peripheral components that may be remote include, but are not limited to, audio devices, pointing devices, keypads, displays, cameras, projectors, and the like. These peripheral components may communicate over a Pico Network such as Bluetooth™ Zigbee™ and the like. One non-limiting example of a computer with such peripheral human interface components is a wearable computer, which might include a remote pico projector along with one or more cameras that remotely communicate with a separately located computer to sense a user&#39;s gestures toward portions of an image projected by the pico projector onto a reflected surface such as a wall or the user&#39;s hand. 
     Computer  650  may include wireless propagation modeling application  657  (WPM) that may be configured to remotely model propagation of wireless signals at one or more locations in one or more wireless networks. For example, WPM may model propagation of wireless signals according to a 3GPP or similar wireless signal propagation model, which may account for, e.g., attenuation due to distance, attenuation due to intervening foliage, etc. WPM  657  may employ geographical information provided by Geographic Information System (GIS) application  658  regarding the one or more locations. In one or more embodiments, WPM  658  may utilize an IoT network to communicate with the at least a portion of the elements in the one or more wireless networks, including the plurality of wireless signal repeater devices. 
     Computer  650  may include web browser application  659  that is configured to receive and to send web pages, web-based messages, graphics, text, multimedia, and the like. For example, the web browser application may provide graphical depictions of coverages areas, analogous to the shadings of the various coverage areas as depicted in  FIG. 3 . The computer&#39;s browser application may employ virtually any programming language, including a wireless application protocol messages (WAP), and the like. In one or more embodiment, the browser application is enabled to employ Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WMLScript, JavaScript, Standard Generalized Markup Language (SGML), HyperText Markup Language (HTML), eXtensible Markup Language (XML), HTML5, and the like. 
     Memory  652  may include Random Access Memory (RAM), Read Only Memory (ROM), or other types of memory. Memory  652  illustrates an example of computer-readable storage medium (devices) for storage of information such as computer-readable instructions, data structures, program modules or other data. Memory  652  may store BIOS  654  for controlling low-level operation of computer  650 . The memory may also store operating system  653  for controlling the operation of computer  650 . It will be appreciated that this component may include a general-purpose operating system such as a version of UNIX, or LINUX™, or a specialized computer communication operating system such as Windows Phone™, Apple iOS™ or the Symbian® operating system. The operating system may include, or interface with a Java virtual machine module that enables control of hardware components or operating system operations via Java application programs. 
     Memory  652  may further include one or more data storage  655 , which can be utilized by computer  650  to store, among other things, applications  656  or other data. For example, data storage  655  may also be employed to store information that describes various capabilities of computer  650 . The information may then be provided to another device or computer based on any of a variety of methods, including being sent as part of a header during a communication, sent upon request, or the like. Data storage  655  may also be employed to store social networking information including address books, buddy lists, aliases, user profile information, or the like. Data storage  655  may further include program code, data, algorithms, and the like, for use by a processor, such as processor  651  to execute and perform actions. In one embodiment, at least some of data storage  655  might also be stored on another component of computer  650 , including, but not limited to, non-transitory processor-readable removable storage device  664 , processor-readable stationary storage device  663 , or even external to the computer. 
     Applications  656  may include computer executable instructions which, when executed by computer  650 , transmit, receive, or otherwise process instructions and data. Applications  656  may include, for example, WPM application  657 , GIS application  658 , web browser  659 , or the like. Computers may be arranged to exchange communications, such as, queries, searches, messages, notification messages, event messages, alerts, performance metrics, log data, API calls, or the like, combination thereof, with application servers or network monitoring computers. 
     Other examples of application programs include calendars, search programs, email applications, IM applications, SMS applications, Voice Over Internet Protocol (VOIP) applications, contact managers, task managers, transcoders, database programs, word processing programs, security applications, spreadsheet programs, games, search programs, and so forth. 
     Additionally, in one or more embodiments (not shown in the figures), computer  650  may include one or more embedded logic hardware devices instead of CPUs, such as, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic (PAL), or the like, or combination thereof. The embedded logic hardware devices may directly execute embedded logic to perform actions. Also, in one or more embodiments (not shown in the figures), computer  650  may include one or more hardware microcontrollers instead of CPUs. In one or more embodiments, the microcontrollers may directly execute their own embedded logic to perform actions and access their own internal memory and their own external Input and Output Interfaces (e.g., hardware pins or wireless transceivers) to perform actions, such as System On a Chip (SOC), or the like. 
     Also, in one or more embodiments, a system may comprise one or more processors and one or more memories that store instructions. Further, the one or more processors that execute the instructions may be configured to carry out any of the methods disclosed herein including, but not limited to, the claimed embodiments of Claims&#39;  1 - 24 . 
     Additionally, in one or more embodiments, a computer-readable non-transitory medium may be arranged to store instructions. Further, one or more processors that execute the instructions may be configured to carry out any of the methods disclosed herein including, but not limited to, the claimed embodiments of Claims&#39;  1 - 24 .