Patent Publication Number: US-2017366980-A1

Title: Unmanned aerial vehicles landing zones at cell sites

Description:
CROSS-REFERENCE TO RELATED APPLICATION(S) 
     The present patent/application is continuation-in-part of, and the content of each are incorporated by reference herein: 
     
       
         
           
               
               
               
             
               
                   
               
               
                 Filing Date 
                 Serial No. 
                 Title 
               
               
                   
               
             
            
               
                 Aug. 26, 2016 
                 15/248,634  
                 USING DRONES TO LIFT PERSONNEL  
               
               
                   
                   
                 UP CELL TOWERS  
               
               
                 Jul 8, 2016  
                 15/205,313  
                 CELL TOWER INSTALLATION AND  
               
               
                   
                   
                 MAINTENANCE SYSTEMS AND  
               
               
                   
                   
                 METHODS USING ROBOTIC DEVICES  
               
               
                 Jun. 23, 2016  
                 15/190,450  
                 CELL TOWER INSTALLATION SYSTEMS  
               
               
                   
                   
                 AND METHODS WITH UNMANNED  
               
               
                   
                   
                 AERIAL VEHICLES  
               
               
                 Jun. 7, 2016  
                 15/175,314  
                 WIRELESS COVERAGE TESTING  
               
               
                   
                   
                 SYSTEMS AND METHODS WITH  
               
               
                   
                   
                 UNMANNED AERIAL VEHICLES  
               
               
                 Apr. 18, 2016  
                 15/131,460  
                 UNMANNED AERIAL VEHICLE-BASED  
               
               
                   
                   
                 SYSTEMS AND METHODS ASSOCIATED 
               
               
                   
                   
                 WITH CELL SITES AND CELL TOWERS  
               
               
                   
                   
                 WITH ROBOTIC ARMS FOR  
               
               
                   
                   
                 PERFORMING OPERATIONS  
               
               
                 Jun. 11, 2015  
                 14/736,925  
                 TETHERED UNMANNED AERIAL  
               
               
                   
                   
                 VEHICLE-BASED SYSTEMS AND  
               
               
                   
                   
                 METHODS ASSOCIATED WITH CELL  
               
               
                   
                   
                 SITES AND CELL TOWERS  
               
               
                 Apr. 14, 2015  
                 14/685,720  
                 UNMANNED AERIAL VEHICLE-BASED  
               
               
                   
                   
                 SYSTEMS AND METHODS ASSOCIATED 
               
               
                   
                   
                 WITH CELL SITES AND CELL TOWERS 
               
               
                   
               
            
           
         
       
     
     FIELD OF THE DISCLOSURE 
     The present disclosure relates generally to Unmanned Aerial Vehicle (UAV) or drone systems and methods. More particularly, the present disclosure relates to UAV landing zones at cell sites, namely various structures and methods supporting UAV landing and take-off at cell sites. 
     BACKGROUND OF THE DISCLOSURE 
     Due to the geographic coverage nature of wireless service, there are hundreds of thousands of cell towers in the United States. For example, in 2014, it was estimated that there were more than 310,000 cell towers in the United States. Cell towers can have heights up to 1,500 feet or more. Concurrently, the use of unmanned aerial vehicles (UAV), also referred to as drones, is evolving. There are limitations associated with UAVs, including emerging FAA rules and guidelines associated with their commercial use. With the expected proliferation of UAV usage, especially for commercial use, there will be a need for geographically diverse landing zones for various purposes. 
     BRIEF SUMMARY OF THE DISCLOSURE 
     In an exemplary embodiment, a cell site with a landing zone for an Unmanned Aerial Vehicle (UAV) includes a cell tower including cell site components for wireless service; a cabinet or shelter with equipment for the wireless service; and one or more landing zones defined at the cell site for the UAV with associated structure for each of the one or more landing zones, equipment for one or more purposes associated with the UAV, and access privileges to the cell site for personnel associated with the UAV, wherein the one or more landing zones are located on one or more of the cell tower, the cabinet or shelter, and surrounding geography around the cell tower. The one or more landing zones can include a location on top of the cell tower for battery recharging via a battery recharge station. The one or more landing zones can include a location at or near ground for the one or more purposes requiring physical access to the UAV. The one or more landing zones can include a location outside of a fence at the cell site. The one or more landing zones can include a location on or near an access road at the cell site. The one or more landing zones can include a location on a fence at the cell site. The one or more purposes can include any of battery recharge, battery replacement, maintenance, emergency landing, and pick up or drop off of cargo. The one or more purposes can include automated purposes which are performed automatically without physical access to the UAV by personnel and manual purposes which require physical access to the UAV. The associated structure can include a platform installed on the cell tower. 
     In another exemplary embodiment, a method of providing landing zones for an Unmanned Aerial Vehicle (UAV) at a cell site includes, at a cell tower including cell site components for wireless service and a cabinet or shelter with equipment for the wireless service, providing one or more landing zones defined at the cell site for the UAV with associated structure for each of the one or more landing zones; providing equipment for one or more purposes associated with the UAV; and providing access privileges to the cell site for personnel associated with the UAV, wherein the one or more landing zones are located on one or more of the cell tower, the cabinet or shelter, and surrounding geography around the cell tower. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The present disclosure is illustrated and described herein with reference to the various drawings, in which like reference numbers are used to denote like system components/method steps, as appropriate, and in which: 
         FIG. 1  is a diagram of a side view of an exemplary cell site; 
         FIG. 2  is a diagram of a cell site audit performed with an unmanned aerial vehicle (UAV); 
         FIG. 3  is a screen diagram of a view of a graphical user interface (GUI) on a mobile device while piloting the UAV; 
         FIG. 4  is a perspective view of an exemplary UAV for use with the systems and methods described herein; 
         FIG. 5  is a block diagram of a mobile device, which may be used for the cell site audit or the like; 
         FIG. 6  is a flow chart of a cell site audit method utilizing the UAV and the mobile device; 
         FIG. 7  is a network diagram of various cell sites deployed in a geographic region; 
         FIG. 8  is a diagram of a tethered configuration with a UAV at a cell site; 
         FIG. 9  is a diagram of another tethered configuration with a UAV at a cell site; 
         FIG. 10  is a flowchart of a method with a tethered UAV associated with a cell site; 
         FIG. 11  is a diagram of a UAV with robotic arms at a cell site; 
         FIG. 12  is a block diagram of the UAV with robotic arms and a payload at a cell site; 
         FIG. 13  is a flowchart of a method with a UAV with robotic arms at a cell site; 
         FIG. 14  is a block diagram of functional components associated with the UAV to support wireless coverage testing; 
         FIG. 15  is a map of three cell sites and associated coverage areas for describing conventional drive testing; 
         FIG. 16  is a 3D view of a cell tower with an associated coverage area in three dimensions—x, y, and z for illustrating UAV-based wireless coverage testing; 
         FIG. 17  is a flowchart of a UAV-based wireless coverage testing process; 
         FIG. 18  is a diagram of a partial view of the exemplary cell site for describing installation of equipment with the UAV; 
         FIG. 19  is a diagram of a view of the horizontal support structures on the cell tower and the antenna for describing installation of equipment with the UAV; 
         FIG. 20  is a flowchart of an Unmanned Aerial Vehicle (UAV)-based installation method for equipment on cell towers; 
         FIGS. 21A-21C  are diagrams of different types of cell towers, namely a self-support tower ( FIG. 21A ), a monopole tower ( FIG. 21B ), and a guyed tower ( FIG. 21C ); 
         FIG. 22  is a block diagram illustrates a robotic device configured for use with the cell towers for installation and/or maintenance of cell site components on the cell towers; 
         FIG. 23  is a flowchart of a method for installation and maintenance of cell site components with the robotic device; 
         FIG. 24  is a diagram of a drone adapted to transport a person up a cell tower; 
         FIG. 25  is a diagram of another drone adapted to transport a person up the cell tower; 
         FIG. 26  is a diagram of a single person propulsion system adapted to transport a person up the cell tower; 
         FIG. 27  is a diagram of a cell tower with various platforms for receiving a person from a drone or the like; 
         FIG. 28  is a flowchart of a method for transporting maintenance personnel to a cell tower; 
         FIGS. 29A, 29B, and 29C  are diagrams of various counterbalance techniques for the UAV including an extendible arm ( FIG. 29A ), opposing robotic arms ( FIG. 29B ), and moveable weights ( FIG. 29C ); 
         FIG. 30  is a perspective diagram of a cell site with surrounding geography; and 
         FIG. 31  is a perspective diagram illustrates another view of the cell site and the surrounding geography for illustrating exemplary structures or markings for the landing zones. 
     
    
    
     DETAILED DESCRIPTION OF THE DISCLOSURE 
     In various exemplary embodiments, the present disclosure to UAV landing zones at cell sites, namely various structures and methods supporting UAV landing and take-off at cell sites. The present disclosure leverages the fact that there are hundreds of thousands of cell sites geographically distributed such as every few miles. Further, the cell sites do not have a significant amount of traffic including people or vehicles. Accordingly, cell sites are optimal for landing sites for UAVs. For example, cell sites could be used for recharging/replacing batteries, maintenance, emergency landings, pick up/drop off, etc. Advantageously, landing zones and apparatus at cell sites could provide an additional revenue opportunity for cell site operators as well as providing UAV operators convenient and geographically desirable locations. 
     §1.0 Exemplary Cell Site 
     Referring to  FIG. 1 , in an exemplary embodiment, a diagram illustrates a side view of an exemplary cell site  10 . The cell site  10  includes a cell tower  12 . The cell tower  12  can be any type of elevated structure, such as 100-200 feet/30-60 meters tall. Generally, the cell tower  12  is an elevated structure for holding cell site components  14 . The cell tower  12  may also include a lighting rod  16  and a warning light  18 . Of course, there may various additional components associated with the cell tower  12  and the cell site  10  which are omitted for illustration purposes. In this exemplary embodiment, there are four sets  20 ,  22 ,  24 ,  26  of cell site components  14 , such as for four different wireless service providers. In this example, the sets  20 ,  22 ,  24  include various antennas  30  for cellular service. The sets  20 ,  22 ,  24  are deployed in sectors, e.g. there can be three sectors for the cell site components—alpha, beta, and gamma. The antennas  30  are used to both transmit a radio signal to a mobile device and receive the signal from the mobile device. The antennas  30  are usually deployed as a single, groups of two, three or even four per sector. The higher the frequency of spectrum supported by the antenna  30 , the shorter the antenna  30 . For example, the antennas  30  may operate around 850 MHz, 1.9 GHz, and the like. The set  26  includes a microwave dish  32  which can be used to provide other types of wireless connectivity, besides cellular service. There may be other embodiments where the cell tower  12  is omitted and replaced with other types of elevated structures such as roofs, water tanks, etc. 
     §2.0 Cell Site Audits Via UAV 
     Referring to  FIG. 2 , in an exemplary embodiment, a diagram illustrates a cell site audit  40  performed with an unmanned aerial vehicle (UAV)  50 . As described herein, the cell site audit  40  is used by service providers, third party engineering companies, tower operators, etc. to check and ensure proper installation, maintenance, and operation of the cell site components  14  and shelter or cabinet  52  equipment as well as the various interconnections between them. From a physical accessibility perspective, the cell tower  12  includes a climbing mechanism  54  for tower climbers to access the cell site components  14 .  FIG. 2  includes a perspective view of the cell site  10  with the sets  20 ,  26  of the cell site components  14 . The cell site components  14  for the set  20  include three sectors—alpha sector  54 , beta sector  56 , and gamma sector  58 . 
     In an exemplary embodiment, the UAV  50  is utilized to perform the cell site audit  40  in lieu of a tower climber access the cell site components  14  via the climbing mechanism  54 . In the cell site audit  40 , an engineer/technician is local to the cell site  10  to perform various tasks. The systems and methods described herein eliminate a need for the engineer/technician to climb the cell tower  12 . Of note, it is still important for the engineer/technician to be local to the cell site  10  as various aspects of the cell site audit  40  cannot be done remotely as described herein. Furthermore, the systems and methods described herein provide an ability for a single engineer/technician to perform the cell site audit  40  without another person handling the UAV  50  or a person with a pilot&#39;s license operating the UAV  50  as described herein. 
     §2.1 Cell Site Audit 
     In general, the cell site audit  40  is performed to gather information and identify a state of the cell site  10 . This is used to check the installation, maintenance, and/or operation of the cell site  10 . Various aspects of the cell site audit  40  can include, without limitation: 
     
       
         
           
               
               
             
               
                   
               
             
            
               
                   
                 Verify the cell site 10 is built according to a current revision  
               
               
                   
                 Verify Equipment Labeling  
               
               
                   
                 Verify Coax Cable (“Coax”) Bend Radius  
               
               
                   
                 Verify Coax Color Coding/Tagging  
               
               
                   
                 Check for Coax External Kinks &amp; Dents  
               
               
                   
                 Verify Coax Ground Kits  
               
               
                   
                 Verify Coax Hanger/Support  
               
               
                   
                 Verify Coax Jumpers  
               
               
                   
                 Verify Coax Size  
               
               
                   
                 Check for Connector Stress &amp; Distortion  
               
               
                   
                 Check for Connector Weatherproofing  
               
               
                   
                 Verify Correct Duplexers/Diplexers Installed  
               
               
                   
                 Verify Duplexer/Diplexer Mounting  
               
               
                   
                 Verify Duplexers/Diplexers Installed Correctly  
               
               
                   
                 Verify Fiber Paper  
               
               
                   
                 Verify Lacing &amp; Tie Wraps  
               
               
                   
                 Check for Loose or Cross-Threaded Coax Connectors  
               
               
                   
                 Verify Return (“Ret”) Cables  
               
               
                   
                 Verify Ret Connectors  
               
               
                   
                 Verify Ret Grounding  
               
               
                   
                 Verify Ret Installation  
               
               
                   
                 Verify Ret Lightning Protection Unit (LPI)  
               
               
                   
                 Check for Shelter/Cabinet Penetrations  
               
               
                   
                 Verify Surge Arrestor Installation/Grounding  
               
               
                   
                 Verify Site Cleanliness  
               
               
                   
                 Verify LTE GPS Antenna Installation 
               
               
                   
               
            
           
         
       
     
     Of note, the cell site audit  40  includes gathering information at and inside the shelter or cabinet  52 , on the cell tower  12 , and at the cell site components  14 . Note, it is not possible to perform all of the above items solely with the UAV  50  or remotely. 
     §3.0 Piloting the UAV at the Cell Site 
     It is important to note that the Federal Aviation Administration (FAA) is in the process of regulating commercial UAV (drone) operation. It is expected that these regulations would not be complete until 2016 or 2017. In terms of these regulations, commercial operation of the UAV  50 , which would include the cell site audit  40 , requires at least two people, one acting as a spotter and one with a pilot&#39;s license. These regulations, in the context of the cell site audit  40 , would make use of the UAV  50  impractical. To that end, the systems and methods described herein propose operation of the UAV  50  under FAA exemptions which allow the cell site audit  40  to occur without requiring two people and without requiring a pilot&#39;s license. Here, the UAV  50  is constrained to fly up and down at the cell site  10  and within a three-dimensional (3D) rectangle at the cell site components. These limitations on the flight path of the UAV  50  make the use of the UAV  50  feasible at the cell site  10 . 
     Referring to  FIG. 3 , in an exemplary embodiment, a screen diagram illustrates a view of a graphical user interface (GUI)  60  on a mobile device  100  while piloting the UAV  50 . The GUI  60  provides a real-time view to the engineer/technician piloting the UAV  50 . That is, a screen  62  provides a view from a camera on the UAV  50 . As shown in  FIG. 3 , the cell site  10  is shown with the cell site components  14  in the view of the screen  62 . Also, the GUI  60  has various controls  64 ,  66 . The controls  64  are used to pilot the UAV  50 , and the controls  66  are used to perform functions in the cell site audit  40  and the like. 
     §3.1 FAA Regulations 
     The FAA is overwhelmed with applications from companies interested in flying drones, but the FAA is intent on keeping the skies safe. Currently, approved exemptions for flying drones include tight rules. Once approved, there is some level of certification for drone operators along with specific rules such as speed limit of 100 mph, height limitations such as 400 ft, no-fly zones, day only operation, documentation, and restrictions on aerial filming. Accordingly, flight at or around cell towers is constrained, and the systems and methods described herein fully comply with the relevant restrictions associated with drone flights from the FAA. 
     §4.0 Exemplary Hardware 
     Referring to  FIG. 4 , in an exemplary embodiment, a perspective view illustrates an exemplary UAV  50  for use with the systems and methods described herein. Again, the UAV  50  may be referred to as a drone or the like. The UAV  50  may be a commercially available UAV platform that has been modified to carry specific electronic components as described herein to implement the various systems and methods. The UAV  50  includes rotors  80  attached to a body  82 . A lower frame  84  is located on a bottom portion of the body  82 , for landing the UAV  50  to rest on a flat surface and absorb impact during landing. The UAV  50  also includes a camera  86  which is used to take still photographs, video, and the like. Specifically, the camera  86  is used to provide the real-time display on the screen  62 . The UAV  50  includes various electronic components inside the body  82  and/or the camera  86  such as, without limitation, a processor, a data store, memory, a wireless interface, and the like. Also, the UAV  50  can include additional hardware, such as robotic arms or the like that allow the UAV  50  to attach/detach components for the cell site components  14 . Specifically, it is expected that the UAV  50  will get bigger and more advanced, capable of carrying significant loads, and not just a wireless camera. The present disclosure contemplates using the UAV  50  for various aspects at the cell site  10 , including participating in construction or deconstruction of the cell tower  12 , the cell site components  14 , etc. 
     These various components are now described with reference to a mobile device  100 . Those of ordinary skill in the art will recognize the UAV  50  can include similar components to the mobile device  100 . Of note, the UAV  50  and the mobile device  100  can be used cooperatively to perform various aspects of the cell site audit  40  described herein. In other embodiments, the UAV  50  can be operated with a controller instead of the mobile device  100 . The mobile device  100  may solely be used for real-time video from the camera  86  such as via a wireless connection (e.g., IEEE 802.11 or variants thereof). Some portions of the cell site audit  40  can be performed with the UAV  50 , some with the mobile device  100 , and others solely by the operator through visual inspection. In some embodiments, all of the aspects can be performed in the UAV  50 . In other embodiments, the UAV  50  solely relays data to the mobile device  100  which performs all of the aspects. Other embodiments are also contemplated. 
     Referring to  FIG. 5 , in an exemplary embodiment, a block diagram illustrates a mobile device  100 , which may be used for the cell site audit  40  or the like. The mobile device  100  can be a digital device that, in terms of hardware architecture, generally includes a processor  102 , input/output (I/O) interfaces  104 , wireless interfaces  106 , a data store  108 , and memory  110 . It should be appreciated by those of ordinary skill in the art that  FIG. 5  depicts the mobile device  100  in an oversimplified manner, and a practical embodiment may include additional components and suitably configured processing logic to support known or conventional operating features that are not described in detail herein. The components ( 102 ,  104 ,  106 ,  108 , and  102 ) are communicatively coupled via a local interface  112 . The local interface  112  can be, for example, but not limited to, one or more buses or other wired or wireless connections, as is known in the art. The local interface  112  can have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, among many others, to enable communications. Further, the local interface  112  may include address, control, and/or data connections to enable appropriate communications among the aforementioned components. 
     The processor  102  is a hardware device for executing software instructions. The processor  102  can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the mobile device  100 , a semiconductor-based microprocessor (in the form of a microchip or chip set), or generally any device for executing software instructions. When the mobile device  100  is in operation, the processor  102  is configured to execute software stored within the memory  110 , to communicate data to and from the memory  110 , and to generally control operations of the mobile device  100  pursuant to the software instructions. In an exemplary embodiment, the processor  102  may include a mobile optimized processor such as optimized for power consumption and mobile applications. The I/O interfaces  104  can be used to receive user input from and/or for providing system output. User input can be provided via, for example, a keypad, a touch screen, a scroll ball, a scroll bar, buttons, bar code scanner, and the like. System output can be provided via a display device such as a liquid crystal display (LCD), touch screen, and the like. The I/O interfaces  104  can also include, for example, a serial port, a parallel port, a small computer system interface (SCSI), an infrared (IR) interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, and the like. The I/O interfaces  104  can include a graphical user interface (GUI) that enables a user to interact with the mobile device  100 . Additionally, the I/O interfaces  104  may further include an imaging device, i.e. camera, video camera, etc. 
     The wireless interfaces  106  enable wireless communication to an external access device or network. Any number of suitable wireless data communication protocols, techniques, or methodologies can be supported by the wireless interfaces  106 , including, without limitation: RF; IrDA (infrared); Bluetooth; ZigBee (and other variants of the IEEE 802.15 protocol); IEEE 802.11 (any variation); IEEE 802.16 (WiMAX or any other variation); Direct Sequence Spread Spectrum; Frequency Hopping Spread Spectrum; Long Term Evolution (LTE); cellular/wireless/cordless telecommunication protocols (e.g. 3G/4G, etc.); wireless home network communication protocols; paging network protocols; magnetic induction; satellite data communication protocols; wireless hospital or health care facility network protocols such as those operating in the WMTS bands; GPRS; proprietary wireless data communication protocols such as variants of Wireless USB; and any other protocols for wireless communication. The wireless interfaces  106  can be used to communicate with the UAV  50  for command and control as well as to relay data therebetween. The data store  108  may be used to store data. The data store  108  may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, and the like)), nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, and the like), and combinations thereof. Moreover, the data store  108  may incorporate electronic, magnetic, optical, and/or other types of storage media. 
     The memory  110  may include any of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)), nonvolatile memory elements (e.g., ROM, hard drive, etc.), and combinations thereof. Moreover, the memory  110  may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory  110  may have a distributed architecture, where various components are situated remotely from one another but can be accessed by the processor  102 . The software in memory  110  can include one or more software programs, each of which includes an ordered listing of executable instructions for implementing logical functions. In the example of  FIG. 5 , the software in the memory  110  includes a suitable operating system (O/S)  114  and programs  116 . The operating system  114  essentially controls the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The programs  116  may include various applications, add-ons, etc. configured to provide end user functionality with the mobile device  100 , including performing various aspects of the systems and methods described herein. 
     It will be appreciated that some exemplary embodiments described herein may include one or more generic or specialized processors (“one or more processors”) such as microprocessors, digital signal processors, customized processors, and field programmable gate arrays (FPGAs) and unique stored program instructions (including both software and firmware) that control the one or more processors to implement, in conjunction with certain non-processor circuits, some, most, or all of the functions of the methods and/or systems described herein. Alternatively, some or all functions may be implemented by a state machine that has no stored program instructions, or in one or more application specific integrated circuits (ASICs), in which each function or some combinations of certain of the functions are implemented as custom logic. Of course, a combination of the aforementioned approaches may be used. Moreover, some exemplary embodiments may be implemented as a non-transitory computer-readable storage medium having computer readable code stored thereon for programming a computer, server, appliance, device, etc. each of which may include a processor to perform methods as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a hard disk, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory), Flash memory, and the like. When stored in the non-transitory computer readable medium, the software can include instructions executable by a processor that, in response to such execution, cause a processor or any other circuitry to perform a set of operations, steps, methods, processes, algorithms, etc. 
     §4.1 RF Sensors in the UAV 
     In an exemplary embodiment, the UAV  50  can also include one or more RF sensors disposed therein. The RF sensors can be any device capable of making wireless measurements related to signals associated with the cell site components  14 , i.e., the antennas. In an exemplary embodiment, the UAV  50  can be further configured to fly around a cell zone associated with the cell site  10  to identify wireless coverage through various measurements associated with the RF sensors. 
     §5.0 Cell Site Audit with UAV and/or Mobile Device 
     Referring to  FIG. 6 , in an exemplary embodiment, a flow chart illustrates a cell site audit method  200  utilizing the UAV  50  and the mobile device  100 . Again, in various exemplary embodiments, the cell site audit  40  can be performed with the UAV  50  and the mobile device  100 . In other exemplary embodiments, the cell site audit  40  can be performed with the UAV  50  and an associated controller. In other embodiments, the mobile device  100  is solely used to relay real-time video from the camera  86 . While the steps of the cell site audit method  200  are listed sequentially, those of ordinary skill in the art will recognize some or all of the steps may be performed in a different order. The cell site audit method  200  includes an engineer/technician at a cell site with the UAV  50  and the mobile device  100  (step  202 ). Again, one aspect of the systems and methods described herein is the usage of the UAV  50 , in a commercial setting, but with constraints such that only one operator is required and such that the operator does not have to hold a pilot&#39;s license. As described herein, the constraints can include a flight of the UAV  50  at or near the cell site  10  only, a flight pattern up and down in a 3D rectangle at the cell tower  12 , a maximum height restriction (e.g., 500 feet or the like), and the like. For example, the cell site audit  40  is performed by one of i) a single operator flying the UAV  50  without a license or ii) two operators including one with a license and one to spot the UAV  50 . 
     The engineer/technician performs one or more aspects of the cell site audit  40  without the UAV  50  (step  204 ). Note, there are many aspects of the cell site audit  40  as described herein. It is not possible for the UAV  50  to perform all of these items such that the engineer/technician could be remote from the cell site  10 . For example, access to the shelter or cabinet  52  for audit purposes requires the engineer/technician to be local. In this step, the engineer/technician can perform any audit functions as described herein that do not require climbing. 
     The engineer/technician can cause the UAV  50  to fly up the cell tower  12  or the like to view cell site components  14  (step  206 ). Again, this flight can be based on the constraints, and the flight can be through a controller and/or the mobile device  100 . The UAV  50  and/or the mobile device  100  can collect data associated with the cell site components  14  (step  208 ), and process the collected data to obtain information for the cell site audit  40  (step  210 ). As described herein, the UAV  50  and the mobile device  100  can be configured to collect data via video and/or photographs. The engineer/technician can use this collected data to perform various aspects of the cell site audit  40  with the UAV  50  and the mobile device  100  and without a tower climb. 
     The foregoing descriptions detail specific aspects of the cell site audit  40  using the UAV  50  and the mobile device  100 . In these aspects, data can be collected—generally, the data is video or photographs of the cell site components  14 . The processing of the data can be automated through the UAV  50  and/or the mobile device  100  to compute certain items as described herein. Also, the processing of the data can be performed either at the cell site  10  or afterward by the engineer/technician. 
     In an exemplary embodiment, the UAV  50  can be a commercial, “off-the-shelf” drone with a Wi-Fi enabled camera for the camera  86 . Here, the UAV  50  is flown with a controller pad which can include a joystick or the like. Alternatively, the UAV  50  can be flown with the mobile device  100 , such as with an app installed on the mobile device  100  configured to control the UAV  50 . The Wi-Fi enable camera is configured to communicate with the mobile device  100 —to both display real-time video and audio as well as to capture photos and/or video during the cell site audit  40  for immediate processing or for later processing to gather relevant information about the cell site components  14  for the cell site audit  40 . 
     In another exemplary embodiment, the UAV  50  can be a so-called “drone in a box” which is preprogrammed/configured to fly a certain route, such as based on the flight constraints described herein. The “drone in a box” can be physically transported to the cell site  10  or actually located there. The “drone in a box” can be remotely controlled as well. 
     §5.1 Antenna Down Tilt Angle 
     In an exemplary aspect of the cell site audit  40 , the UAV  50  and/or the mobile device  100  can be used to determine a down tilt angle of individual antennas  30  of the cell site components  14 . The down tilt angle can be determined for all of the antennas  30  in all of the sectors  54 ,  56 ,  58 . The down tilt angle is the mechanical (external) down tilt of the antennas  30  relative to a support bar  200 . In the cell site audit  40 , the down tilt angle is compared against an expected value, such as from a Radio Frequency (RF) data sheet, and the comparison may check to ensure the mechanical (external) down tilt is within ±1.0° of specification on the RF data sheet. 
     Using the UAV  50  and/or the mobile device  100 , the down tilt angle is determined from a photo taken from the camera  86 . In an exemplary embodiment, the UAV  50  and/or the mobile device  100  is configured to measure three points—two defined by the antenna  30  and one by the support bar  200  to determine the down tilt angle of the antenna  30 . For example, the down tilt angle can be determined visually from the side of the antenna  30 —measuring a triangle formed by a top of the antenna  30 , a bottom of the antenna  30 , and the support bar  200 . 
     §5.2 Antenna Plumb 
     In an exemplary aspect of the cell site audit  40  and similar to determining the down tilt angle, the UAV  50  and/or the mobile device  100  can be used to visually inspect the antenna  30  including its mounting brackets and associated hardware. This can be done to verify appropriate hardware installation, to verify the hardware is not loose or missing, and to verify that antenna  30  is plumb relative to the support bar  200 . 
     §5.3 Antenna Azimuth 
     In an exemplary aspect of the cell site audit  40 , the UAV  50  and/or the mobile device  100  can be used to verify the antenna azimuth, such as verifying the antenna azimuth is oriented within ±5° as defined on the RF data sheet. The azimuth (AZ) angle is the compass bearing, relative to true (geographic) north, of a point on the horizon directly beneath an observed object. Here, the UAV  50  and/or the mobile device  100  can include a location determining device such as a Global Positioning Satellite (GPS) measurement device. The antenna azimuth can be determined with the UAV  50  and/or the mobile device  100  using an aerial photo or the GPS measurement device. 
     §5.4 Photo Collections 
     As part of the cell site audit  40  generally, the UAV  50  and/or the mobile device  100  can be used to document various aspects of the cell site  10  by taking photos or video. For example, the mobile device  100  can be used to take photos or video on the ground in or around the shelter or cabinet  52  and the UAV  500  can be used to take photos or video up the cell tower  12  and of the cell site components  14 . The photos and video can be stored in any of the UAV  50 , the mobile device  100 , the cloud, etc. 
     In an exemplary embodiment, the UAV can also hover at the cell site  10  and provide real-time video footage back to the mobile device  100  or another location (for example, a Network Operations Center (NOC) or the like). 
     §5.5 Compound Length/Width 
     The UAV  50  can be used to fly over the cell site  10  to measure the overall length and width of the cell site  10  compound from overhead photos. In one aspect, the UAV  50  can use GPS positioning to detect the length and width by flying over the cell site  10 . In another aspect, the UAV  50  can take overhead photos which can be processed to determine the associated length and width of the cell site  10 . 
     §5.6 Data Capture—Cell Site Audit 
     The UAV  50  can be used to capture various pieces of data via the camera  86 . That is, with the UAV  50  and the mobile device  100 , the camera  86  is equivalent to the engineer/technician&#39;s own eyes, thereby eliminating the need for the engineer/technician to physically climb the tower. One important aspect of the cell site audit  40  is physically collecting various pieces of information—either to check records for consistency or to establish a record. For example, the data capture can include determining equipment module types, locations, connectivity, serial numbers, etc. from photos. The data capture can include determining physical dimensions from photos or from GPS such as the cell tower  12  height, width, depth, etc. The data capture can also include visual inspection of any aspect of the cell site  10 , cell tower  12 , cell site components  14 , etc. including, but not limited to, physical characteristics, mechanical connectivity, cable connectivity, and the like. 
     The data capture can also include checking the lighting rod  16  and the warning light  18  on the cell tower  12 . Also, with additional equipment on the UAV  50 , the UAV  50  can be configured to perform maintenance such as replacing the warning light  18 , etc. The data capture can also include checking maintenance status of the cell site components  14  visually as well as checking associated connection status. Another aspect of the cell site audit  40  can include checking the structural integrity of the cell tower  12  and the cell site components  14  via photos from the UAV  50 . 
     §5.7 Flying the UAV at the Cell Site 
     In an exemplary embodiment, the UAV  50  can be programmed to automatically fly to a location and remain there without requiring the operator to control the UAV  50  in real-time, at the cell site  10 . In this scenario, the UAV  50  can be stationary at a location in the air at the cell site  10 . Here, various functionality can be incorporated in the UAV  50  as described herein. Note, this aspect leverages the ability to fly the UAV  50  commercially based on the constraints described herein. That is, the UAV  50  can be used to fly around the cell tower  12 , to gather data associated with the cell site components  14  for the various sectors  54 ,  56 ,  58 . Also, the UAV  50  can be used to hover around the cell tower  12 , to provide additional functionality described as follows. 
     §5.8 Video/Photo Capture—Cell Site 
     With the UAV  50  available to operate at the cell site  10 , the UAV  50  can also be used to capture video/photos while hovering. This application uses the UAV  50  as a mobile video camera to capture activity at or around the cell site  10  from the air. It can be used to document work at the cell site  10  or to investigate the cell site  10  responsive to problems, e.g. tower collapse. It can be used to take surveillance video of surrounding locations such as service roads leading to the cell site  10 , etc. 
     §5.9 Wireless Service Via the UAV 
     Again, with the ability to fly at the cell site  10 , subject to the constraints, the UAV  50  can be used to provide temporary or even permanent wireless service at the cell site. This is performed with the addition of wireless service-related components to the UAV  50 . In the temporary mode, the UAV  50  can be used to provide service over a short time period, such as responding to an outage or other disaster affecting the cell site  10 . Here, an operator can cause the UAV  50  to fly where the cell site components  14  are and provide such service. The UAV  50  can be equipped with wireless antennas to provide cell service, Wireless Local Area Network (WLAN) service, or the like. The UAV  50  can effectively operate as a temporary tower or small cell as needed. 
     In the permanent mode, the UAV  50  (along with other UAVs  50 ) can constantly be in the air at the cell site  10  providing wireless service. This can be done similar to the temporary mode but over a longer time period. The UAV  50  can be replaced over a predetermined time to refuel or the like. The replacement can be another UAV  50 . The UAV  50  can effectively operate as a permanent tower or small cell as needed. 
     §6.0 Flying the UAV from Cell Site to Another Cell Site 
     As described herein, the flight constraints include operating the UAV  50  vertically in a defined 3D rectangle at the cell site  10 . In another exemplary embodiment, the flight constraints can be expanded to allow the 3D rectangle at the cell site  10  as well as a horizontal operation between adjacent cell sites  10 . Referring to  FIG. 7 , in an exemplary embodiment, a network diagram illustrates various cell sites  10   a - 10   e  deployed in a geographic region  300 . In an exemplary embodiment, the UAV  50  is configured to operate as described herein, such as in  FIG. 2 , in the vertical 3D rectangular flight pattern, as well as in a horizontal flight pattern between adjacent cell sites  10 . Here, the UAV  50  is cleared to fly, without the commercial regulations, between the adjacent cell sites  10 . 
     In this manner, the UAV  50  can be used to perform the cell site audits  40  at multiple locations—note, the UAV  50  does not need to land and physically be transported to the adjacent cell sites  10 . Additionally, the fact that the FAA will allow exemptions to fly the UAV  50  at the cell site  10  and between adjacent cell sites  10  can create an interconnected mesh network of allowable flight paths for the UAV  50 . Here, the UAV  50  can be used for other purposes besides those related to the cell site  10 . That is, the UAV  50  can be flown in any application, independent of the cell sites  10 , but without requiring FAA regulation. The applications can include, without limitation, a drone delivery network, a drone surveillance network, and the like. 
     As shown in  FIG. 7 , the UAV  50 , at the cell site  10   a , can be flown to any of the other cell sites  10   b - 10   e  along flight paths  302 . Due to the fact that cell sites  10  are numerous and diversely deployed in the geographic region  300 , an ability to fly the UAV  50  at the cell sites  10  and between adjacent cell sites  10  creates an opportunity to fly the UAV  50  across the geographic region  300 , for numerous applications. 
     §7.0 UAV and Cell Towers 
     Additionally, the systems and methods described herein contemplate practically any activity at the cell site  10  using the UAV  50  in lieu of a tower climb. This can include, without limitation, any tower audit work with the UAV  50 , any tower warranty work with the UAV  50 , any tower operational ready work with the UAV  50 , any tower construction with the UAV  50 , any tower decommissioning/deconstruction with the UAV  50 , any tower modifications with the UAV  50 , and the like. 
     §8.0 Tethered UAV Systems and Methods 
     Referring to  FIGS. 8 and 9 , in an exemplary embodiment, diagrams illustrate a cell site  10  for illustrating the UAV  50  and associated tethered UAV systems and methods. Specifically,  FIGS. 8 and 9  is similar to  FIG. 2 , but here, the UAV  50  is tethered at or near the cell site  10  via a connection  400 . The connection  400  can include a cable, rope, a power cable, a communications cable, a fiber optic cable, etc., i.e., any connection with the strength to constrain the UAV  50  to the cell site  10 . In an exemplary embodiment in  FIG. 8 , the connection  400  is tethered to the top of the cell tower  12 , such as at the cell site components  14  or at one of the alpha sector  54 , beta sector  56 , and gamma sector  58 . In another exemplary embodiment in  FIG. 8 , the connection  400  is tethered to the cell tower  12  itself, such as at any point between the base and the top of the cell tower  12 . In a further exemplary embodiment in  FIG. 8 , the connection  400  is tethered to the bottom of the cell site  10 , such as at the shelter or cabinet  52  or a base of the cell tower  12 . Specifically, in  FIG. 8 , the tethered configuration includes the connection  400  coupled to some part of the cell tower  12  or the like. 
     In  FIG. 9 , the tethered configuration includes the connection  400  coupled to something that is not part of the cell tower  12 , such as a connection point  401 , i.e., in  FIG. 9 , the UAV  50  is tethered at or near the cell site  10  and, in  FIG. 8 , the UAV  50  is tethered at the cell tower  12 . In various exemplary embodiments, the connection point  401  can include, without limitation, a stake, a pole, weight, a fence, a communications device, a wireless radio, a building or other structure, or any other device or object at or near the cell site  12 . As described herein, the UAV  50  is in a tethered configuration where the UAV  50  is coupled at or near the cell site  10  via the connection  400 . 
     In an exemplary embodiment, the UAV  50  can be housed or located at or near the cell site  10 , connected via the connection  400 , and stored in housings  402 ,  404 , for example. The housings  402 ,  404  are shown for illustration purposes, and different locations are also contemplated. The housing  402  is on the cell tower  12 , and the housing  404  is at or part of the shelter or cabinet  52 . In operation, the UAV  50  is configured to selectively enter/exit the housing  402 ,  404 . The connection  400  can be tethered to or near the housing  402 ,  404 . The housing  402 ,  404  can include a door that selectively opens/closes. Alternatively, the housing  402 ,  404  includes an opening where the UAV  50  enters and exits. The housing  402 ,  404  can be used to store the UAV  50  while not in operation. 
     One unique aspect of the tethered configuration described herein, i.e., the UAV  50  with the connection  400 , is that the UAV  50  can now be viewed as an attached device to the cell site  10 , and not a free-flying drone. Advantageously, such a configuration can avoid airspace regulations or restrictions. Furthermore, with the connection  400  providing power and/or data connectivity, the UAV  50  contemplates extended periods of time for the operation. 
     As costs decrease, it is feasible to deploy the UAV  50  with the connections  400 , and optionally the housing  402 ,  404  at all cell sites  10 . The UAV  50  with the connection  400  contemplates implementing all of the same functionality described herein with respect to  FIGS. 1-6 . Specifically, the UAV  50  with the connection  400  can be used to perform the cell site audit  40  and the like as well as other features. Also, the UAV  50  with the connection  400  is ideal to act as a wireless access point for wireless service. Here, the connection  400  can provide data and/or power, and be used for 1) additional capacity as needed or 2) a protection antenna to support active components in the cell site components  14  that fail. The UAV  50  with the connection  400  can be used to support overflow capacity as well as needed, providing LTE, WLAN, WiMAX, or any other wireless connectivity. Alternatively, the UAV  50  can be used as an alternative service provider to provide wireless access at the cell site  10  without requiring antennas on the cell tower  12 . 
     Referring to  FIG. 8 , in an exemplary embodiment, a flowchart illustrates a method  500  with a tethered Unmanned Aerial Vehicle (UAV) associated with a cell site. The method  500  includes causing the UAV to fly at or near the cell site while the UAV is tethered at or near the cell site via a connection, wherein flight of the UAV at or near the cell site is constrained based on the connection (step  502 ); and performing one or more functions via the UAV at or near the cell site while the UAV is flying tethered at or near the cell site (step  504 ). 
     The method  500  can further include transferring power and/or data to and from the UAV via the connection (step  506 ). The connection can include one or more of a cable, rope, a power cable, a communications cable, and a fiber optic cable. The one or more functions can include functions related to a cell site audit. The one or more functions can include functions related to providing wireless service via the UAV at the cell site, wherein data and/or power is transferred between the UAV and the cell site to perform the wireless service. The one or more functions can include providing visual air traffic control via one or more cameras on the UAV. The method  500  can further include storing the UAV at the cell site in a housing while the UAV is not in use. The UAV can be configured to fly extended periods at the cell site utilizing power from the connection, where the extended periods are longer than if the UAV did not have power from the connection. The connection can be configured to constrain a flight path of the UAV at the cell site. 
     In another exemplary embodiment, a tethered Unmanned Aerial Vehicle (UAV) associated with a cell site includes one or more rotors disposed to a body, wherein the body is tethered to the cell site via a connection; a camera associated with the body; wireless interfaces; a processor coupled to the wireless interfaces and the camera; and memory storing instructions that, when executed, cause the processor to: process commands to cause the one or more rotors to fly the UAV at the cell site while the UAV is tethered to the cell site via the connection, wherein flight of the UAV at the cell site is constrained based on the connection; and perform one or more functions via the UAV at the cell site while the UAV is flying tethered to the cell site, utilizing one or more of the camera and the wireless interfaces. 
     §8.1 Tethered UAV Systems and Methods—Visual Air Traffic Control 
     In an exemplary embodiment, the tethered UAV  50  can be configured to provide visual air traffic control such as for other UAVs or drones. Here, various tethered UAVs  50  can be deployed across a geographic region at various cell sites  10 , and each UAV  50  can have one or more cameras that can provide a 360-degree view around the cell site  10 . This configuration essentially creates a drone air traffic control system that could be monitored and controlled by Network Control Center (NOC). Specifically, the UAV  50  can be communicatively coupled to the NOC, such as via the connection  400 . The NOC can provide the video feeds of other drones to third parties (e.g., Amazon) and other drone users to comply with current FAA regulations that require eyes on drones at all times. 
     §9.0 UAV Systems and Methods Using Robotic Arms or the Like 
     Referring to  FIGS. 11 and 12 , in an exemplary embodiment, diagrams illustrate a cell site  10  for illustrating the UAV  50  and associated UAV systems and methods with robotic arms for performing operations associated with the cell site components  14 . Specifically,  FIGS. 11 and 12  are similar to  FIG. 2  (and  FIGS. 8 and 9 ), but here, the UAV  50  is equipped with one or more robotic arms  600  for carrying payload  602  and/or performing operations associated with the cell site components  14  on the cell tower  12 . Since the robotic arms  600  and the payload  602  add weight and complexity when maneuvering, the systems and methods include a connection  604  between the UAV  50  and the cell tower  12  which physically supports the UAV  50  at the cell site components  14 . In this manner, there are no counterbalance requirements for the UAV  50  for the robotic arms  600  and the payload  602 . In another exemplary embodiment, the connection  604  can also provide power to the UAV  50  in addition to physically supporting the UAV  50 . That is, the connection  604  is adapted to provide power to the UAV  50  when connected thereto. Specifically, the robotic arms  600  could require a large amount of power, which can come from a power source connected through the connection  604  to the UAV. In an exemplary embodiment, the UAV  50 , once physically connected to the connection  604 , can shut off the flight and local power components and operate the robotic arms  600  via power from the connection  604 . 
     In another exemplary embodiment, the UAV  50  with the robotic arms  600  can utilize the tethered configuration where the UAV  50  is coupled at or near the cell site  10  via the connection  400 . Here, the UAV  50  can use both the connection  400  for a tether and the connection  604  for physical support/stability when at the cell tower  12  where operations are needed. Here, the connection  400  can be configured to provide power to the UAV  50  as well. The UAV  50  can also fly up the connection  400  from the ground that supplies power and any other functions such as a video feed up or down. The tethered UAV  500  attaches itself to the cell tower  12  via the connection  604 , shuts off rotors, engages the robotic arms  600  and then does work, but in this case the power for those robotic arms  600  as well as the rotors comes from a power feed in the connection  400  that is going down to the ground. The UAV  50  also may or may not have a battery, and it may or may not be used. 
     The UAV  50  with the robotic arms  600  is configured to fly up the cell tower  12 , with or without the payload  602 . For example, with the payload  602 , the UAV  50  can be used to bring components to the cell site components  14 , flying up the cell tower  12 . Without the payload  602 , the UAV  50  is flown to the top with the robotic arms  600  for performing operations on the cell tower  12  and the cell site components  14 . In both cases, the UAV  50  is configured to fly up the cell tower  12 , including using all of the constraints described herein. During the flight, the UAV  50  with the robotic arms  600  and with or without the payload  602  does not have a counterbalance issue because the robotic arms  600  and the payload  602  are fixed, i.e., stationary. That is the UAV  50  flies without movement of the robotic arms  600  or the payload  603  during the flight. 
     Once the UAV  50  reaches a desired location on the cell tower  12 , the UAV  50  is configured to physically connect via the connection  604  to the cell tower  12 , the cell site components  14 , or the like. Specifically, via the connection  604 , the UAV  50  is configured to be physically supported without the rotors  80  or the like operating. That is, via the connection  604 , the UAV  50  is physically supporting without flying, thereby eliminating the counterbalancing problems. Once the connection  604  is established, and the UAV  50  flight components are disengaged, the robotic arms  600  and the payload  602  can be moved, manipulated, etc. without having balancing problems that have to be compensated by the flight components. This is because the connection  604  bears the weight of the UAV  50 , allowing any movement by the robotic arms  600  and/or the payload  602 . 
     In an exemplary embodiment, the connection  604  includes a grappling arm that extends from the UAV  50  and physically attaches to the cell tower  12 , such as a grappling hook or the like. In another exemplary embodiment, the connection  604  includes an arm located on the cell tower  12  that physically connects to a connection point in the UAV  50 . Of course, the systems and methods contemplate various connection techniques for the connection  604 . The connection  604  has to be strong enough to support the weight of the UAV  50 , the robotic arms  600 , and the payload  602 . 
     In an exemplary embodiment, the UAV  50  can carry the payload  602  up the cell tower  12 . The payload  602  can include wireless components, cables, nuts/bolts, antennas, supports, braces, lighting rods, lighting, electronics, RF equipment, combinations thereof, and the like. That is, the payload  602  can be anything associated with the cell site components  14 . With the robotic arms  600 , the UAV  500  can be used to perform operations associated with the payload  602 . The operations can include, without limitation, installing cables, installing nuts/bolts to structures or components, installing antennas, installing supports or braces, installing lighting rods, installing electronic or RF equipment, etc. 
     In another exemplary embodiment, the UAV  50  does not include the payload  602  and instead uses the robotic arms  600  to perform operations on existing cell site components  14 . Here, the UAV  50  is flown up the cell site  12  and connected to the connection  604 . Once connected and the flight components disengaged, the UAV  50  can include manipulation of the robotic arms  600  to perform operations on the cell site components  14 . The operations can include, without limitation, manipulating cables, removing/tightening nuts/bolts to structures or components, adjusting antennas, adjusting lighting rods, replacing bulbs in lighting, opening/closing electronic or RF equipment, etc. 
     Referring to  FIG. 13 , in an exemplary embodiment, a flowchart illustrates a method  700  with a UAV with robotic arms at a cell site. The method  700  contemplates operation with the UAV  50  with the robotic arms  600  and optionally with the payload  602 . The method  700  includes causing the UAV to fly at or near the cell site, wherein the UAV includes one or more manipulable arms which are stationary during flight (step  702 ); physically connecting the UAV to a structure at the cell site and disengaging flight components associated with the UAV (step  704 ); and performing one or more functions via the one or more manipulable arms while the UAV is physically connected to the structure, wherein the one or more manipulable arms move while the UAV is physically connected to the structure (step  706 ). The method  700  can further include utilizing the one or more manipulable arms to provide payload to a cell tower at the cell site, wherein the payload is stationary in the one or more manipulable arms during flight (step  708 ). The payload can include any of wireless components, cables, nuts/bolts, antennas, supports, braces, lighting rods, lighting, electronics, and combinations thereof. The method  700  can further include utilizing the one or more manipulable arms to perform operations on a cell tower at the cell site (step  710 ). The operations can include any of installing wireless components, installing cables, installing nuts/bolts, installing antennas, installing supports, installing braces, installing lighting rods, installing lighting, installing electronics, and combinations thereof. The physically connecting can include extending a grappling arm from the UAV to attach to the structure. The physically connecting can include connecting the UAV to an arm extending from the structure which is connectable to the UAV. The physically connecting can be via a connection which bears the weight of the UAV, enabling movement of the one or more manipulable arms without requiring counterbalancing of the UAV due to the movement while the UAV is in flight. 
     §10.0 Cell Site Operations 
     There are generally two entities associated with cell sites—cell site owners and cell site operators. Generally, cell site owners can be viewed as real estate property owners and managers. Typical cell site owners may have a vast number of cell sites, such as tens of thousands, geographically dispersed. The cell site owners are generally responsible for the real estate, ingress and egress, structures on site, the cell tower itself, etc. Cell site operators generally include wireless service providers who generally lease space on the cell tower and in the structures for antennas and associated wireless backhaul equipment. There are other entities that may be associated with cell sites as well including engineering firms, installation contractors, and the like. All of these entities have a need for the various UAV-based systems and methods described herein. Specifically, cell site owners can use the systems and methods for real estate management functions, audit functions, etc. Cell site operators can use the systems and methods for equipment audits, troubleshooting, site engineering, etc. Of course, the systems and methods described herein can be provided by an engineering firm or the like contracted to any of the above entities or the like. The systems and methods described herein provide these entities time savings, increased safety, better accuracy, lower cost, and the like. 
     §11.0 UAV Configuration for Wireless Testing 
     Referring to  FIG. 14 , in an exemplary embodiment, a block diagram illustrates functional components associated with the UAV  50  to support wireless coverage testing. Specifically, the UAV  50  can include a processing device  800 , one or more wireless antennas  802 , a GPS and/or GLONASS location device  804 , one or more scanners  806 , WIFI  808 , and one or more mobile devices  810 . The processing device  800  can include a similar architecture as the mobile device  100  described herein and can generally be used for control of the UAV  50  as well as control of the wireless coverage testing. The one or more wireless antennas  802  can be configured to operate at any operating band using any wireless protocol (GSM, CDMA, UMTS, LTE, etc.). The one or more wireless antennas  802  can be communicatively coupled to the processing device  800  for control and measurement thereof. The location device  804  is configured to denote a specific location of the UAV  50  at a specific time and can be communicatively coupled to the processing device  800 . The location device  804  can collect latitude and longitude of each point as well as elevation. With this location information, the processing device  800  can correlate measurement data, time, speed, etc. with location. The location information can also be used to provide feedback for the correct route of the UAV  50 , during the wireless coverage testing and during general operation. 
     The one or more scanners  806  are configured to collect measurement data in a broad manner, across the wireless network. The scanners  806  can collect data that is not seen by the mobile devices  810 . The WIFI  1008  can be used to collect wireless coverage data related to Wireless Local Area Networks (WLANs), such as based on IEEE 802.11 and variants thereof. Note, some cell sites  10  additionally provide WLAN coverage, such as for public access WIFI or for airplane WIFI access. Finally, the mobile devices  810  are physical mobile phones or emulation thereof and can be used to collect measurement data based on what a mobile device  810  would see. 
     Thus, the processing device  800  provides centralized control and management. The location device  804  collects a specific data point—location at a specific time. Finally, the antennas  802 , the one or more scanners  806 , the WIFI  808 , and the one or more mobile devices  810  are measurement collection devices. Note, in various exemplary embodiments, the UAV  50  can include a combination of one or more of the antennas  802 , the one or more scanners  806 , the WIFI  808 , i.e., a practical embodiment does not require all of these devices. 
     The UAV  50  body can be configured with the antennas  802 , the one or more scanners  806 , the WIFI  808 , and the one or more mobile devices  810  such that there is the distance between these devices to avoid electromagnetic interference or distortion of the radiation pattern of each that can affect measurements. In an exemplary embodiment, the antennas  802 , the one or more scanners  806 , the WIFI  808 , and the one or more mobile devices  810  are positioned on the UAV  50  with a minimum spacing between each, such as about a foot. In an exemplary embodiment, the UAV  50  is specifically designed to perform wireless coverage testing. For example, the UAV  50  can include a long bar underneath with the associated devices, the antennas  802 , the one or more scanners  806 , the WIFI  808 , and the one or more mobile devices  810 , disposed thereon with the minimum spacing. 
     §11.1 Conventional Drive Testing 
     Referring to  FIG. 15 , in an exemplary embodiment, a map illustrates three cell towers  12  and associated coverage areas  1050 ,  1052 ,  1054  for describing conventional drive testing. Typically, for a cell site  10 , in rural locations, the coverage areas  1050 ,  1052 ,  1054  can be about 5 miles in radius whereas, in urban locations, the coverage areas  1050 ,  1052 ,  1054  can be about 0.5 to 2 miles in radius. For a conventional drive test, a vehicle drives a specific route  1056 . Of course, the route  1056  requires physical access, i.e., roads. Alternatively, the drive test can be walked. Of course, this conventional approach is inefficient and only provides measurements on the ground. 
     §11.2 UAV-Based Wireless Coverage Testing 
     Referring to  FIG. 16 , in an exemplary embodiment, a 3D view illustrates a cell tower  12  with an associated coverage area  1060  in three dimensions—x, y, and z for illustrating UAV-based wireless coverage testing. The UAV  50 , with the configuration described in  FIG. 30 , can be flown about the coverage area  1060  taking measurements along the way on a route  1062 . Specifically, the coverage area  1060  also includes an elevation  1064 , i.e., the z-axis. The UAV  50  has the advantage over the conventional drive test in that it is not constrained to a specific route on the ground, but can fly anywhere about the coverage area  1060 . Also, the UAV  50  can obtain measurements much quicker as a UAV flight is significantly faster than driving. Further, the UAV  50  can also perform testing of adjacent cell towers  12  in the same flight, flying to different coverage areas. For example, the UAV  50  can also measure overlapping regions between cell sites  12  for handoffs, etc. Thus, the UAV  50  has significant advantages over the conventional drive testing. 
     In an exemplary embodiment, the elevation  1064  can be up to 1000′ or up to 500′, providing coverage of areas at elevations the UAVs  50  intend to fly. In an exemplary embodiment, the route  1062  can include a circle about the cell tower  12 . In another exemplary embodiment, the route  1062  can include circles of varying elevations about the cell tower  12 . In a further exemplary embodiment, the route  1062  can include a path to cover the majority of the area within the coverage area  1060 , using an optimal flight path therein. The UAV  50  can perform the wireless coverage testing at any time of day—at night, for example, to measure activities related to system design or during the day to measure performance and maintenance with an active network. 
     The wireless coverage testing with the UAV  50  configuration in  FIG. 30  can perform various functions to measure: Signal intensity, Signal quality, Interference, Dropped calls, Blocked calls, Anomalous events, Call statistics, Service level statistics, Quality of Service (QoS) information, Handover information, Neighboring cell information, and the like. The wireless coverage testing can be used for network benchmarking, optimization and troubleshooting, and quality monitoring. 
     For benchmarking, sophisticated multi-channel tools can be used to measure several network technologies and service types simultaneously to very high accuracy, to provide directly comparable information regarding competitive strengths and weaknesses. Results from benchmarking activities, such a comparative coverage analysis or comparative data network speed analysis, are frequently used in marketing campaigns. Optimization and troubleshooting information is more typically used to aid in finding specific problems during the rollout phases of new networks or to observe specific problems reported by users during the operational phase of the network lifecycle. In this mode, the wireless testing data is used to diagnose the root cause of specific, typically localized, network issues such as dropped calls or missing neighbor cell assignments. 
     Service quality monitoring typically involves making test calls across the network to a fixed test unit to assess the relative quality of various services using Mean opinion score (MOS). Quality monitoring focuses on the end user experience of the service and allows mobile network operators to react to what effectively subjective quality degradations by investigating the technical cause of the problem in time-correlated data collected during the drive test. Service quality monitoring is typically carried out in an automated fashion by the UAV  50 . 
     Once the UAV  50  starts the route  1062  and acquires location information, the wireless coverage testing process begins. Again, the UAV  50  can use two different location identifiers, e.g., GPS and GLONASS, to provide improved accuracy for the location. Also, the UAV  50  can perform subsequent tests from the same launch point and orientation as described herein. During the flight on the route  1062 , the UAV  50  obtains measurements from the various wireless measurement devices, i.e., the antennas  1002 , the one or more scanners  1006 , the WIFI  1008 , and the one or more mobile devices  1010 , and denotes such measurements with time and location identifiers. 
     The UAV  50  is configured based on the associated protocols and operating bands of the cell tower  12 . In an exemplary embodiment, the UAV  50  can be configured with two of the mobile devices  1010 . One mobile device  1010  can be configured with a test call during the duration of the flight, collecting measurements associated with the call during a flight on the route  1062 . The other mobile device  1010  can be in a free or IDLE mode, collecting associated measurements during a flight on the route  1062 . The mobile device  1010  making the call can perform short calls, such as 180 seconds to check if calls are established and successfully completed as well as long calls to check handovers between cell towers  12 . 
     Subsequent to the wireless coverage testing process, the collected measurement data can be analyzed and processed by various software tools. The software tools are configured to process the collected measurement data to provide reports and output files. Each post-processing software has its specific analysis, and as the collected measurement data is large, they can be of great help to solve very specific problems. These tools present the data in tables, maps and comparison charts that help in making decisions. 
     §11.3 UAV-Based Wireless Coverage Testing—Aerial Results 
     The wireless coverage testing with the UAV  50  enables a new measurement—wireless coverage above the ground. As described herein, cell towers  12  can be used for control of UAVs  50 , using the wireless network. Accordingly, the wireless coverage testing is useful in identifying coverage gaps not only on the ground where users typically access the wireless network but also in the sky, such as up to 500 or 1000′ where UAVs  50  will fly and need wireless coverage. 
     §11.4 UAV-Based Wireless Coverage Testing Process 
     Referring to  FIG. 17 , in an exemplary embodiment, a flowchart illustrates a UAV-based wireless coverage testing process  1080 . The UAV-based wireless coverage testing process  1080  includes, with a UAV including a wireless coverage testing configuration, flying the UAV on a route in a wireless coverage area associated with a cell tower (step  1082 ); collecting measurement data via the wireless coverage testing configuration during the flying and associating the collected measurement data with location identifiers (step  1084 ); and, subsequent to the flying, processing the collected measurement data with the location identifiers to provide an output detailing wireless coverage in the wireless coverage area including wireless coverage at ground level and above ground level to a set elevation (step  1086 ). The wireless coverage testing configuration can include one or more devices including any of wireless antennas, wireless scanners, Wireless Local Area Network (WLAN) antennas, and one or more mobile devices, communicatively coupled to a processing device, and each of the one or more devices disposed in or on the UAV. Each of the one or more devices can be positioned a minimum distance from one another to prevent interference, such as one foot. The UAV  50  can include a frame disposed thereto with the one or more devices attached thereto with a minimum distance from one another to prevent interference. The location identifiers can include at least two independent location identification techniques thereby improving accuracy thereof, such as GPS and GLONASS. Each subsequent of the flying steps for additional wireless coverage testing can be performed with the UAV taking off and landing at a same location and orientation at a cell site associated with the cell tower. The route can include a substantially circular pattern at a fixed elevation about the cell tower or a substantially circular pattern at varying elevations about the cell tower. 
     The wireless coverage testing configuration can be configured to measure a plurality of Signal intensity, Signal quality, Interference, Dropped calls, Blocked calls, Anomalous events, Call statistics, Service level statistics, Quality of Service (QoS) information, Handover information, and Neighboring cell information. The route can include locations between handoffs with adjacent cell towers. The UAV-based process  1080  can further include, subsequent to the flying and prior to the processing, flying the UAV in a second route in a second wireless coverage area associated with a second cell tower; and collecting second measurement data via the wireless coverage testing configuration during the flying the second route and associating the collected second measurement data with second location identifiers. 
     In another exemplary embodiment, an Unmanned Aerial Vehicle (UAV) adapted for wireless coverage testing includes one or more rotors disposed to a body; wireless interfaces; a wireless coverage testing configuration; a processor coupled to the wireless interfaces, the one or more rotors, and the wireless coverage testing configuration; and memory storing instructions that, when executed, cause the processor to: cause the UAV to fly in a route in a wireless coverage area associated with a cell tower; collect measurement data via the wireless coverage testing configuration during the flight and associate the collected measurement data with location identifiers; and, subsequent to the flight, provide the collected measurement data with the location identifiers for processing to provide an output detailing wireless coverage in the wireless coverage area including wireless coverage at ground level and above ground level to a set elevation. 
     §12.0 Installation of Equipment with UAVs 
     Referring to  FIG. 18 , in an exemplary embodiment, a diagram illustrates a partial view of the exemplary cell site  10  for describing the installation of equipment with the UAV  50 . Again, the cell site  10  includes the cell tower  12 . The cell tower  12  includes horizontal support structures  1100 ,  1102  which is attached to a pole  1104  at varying heights. The antennas  30  are attached/supported by the horizontal support structures  1100 ,  1102 . Techniques are described herein for installing the antennas  30  via the UAV  50 . Those of ordinary skill in the art will recognize that other types of equipment could also be installed using these techniques, such as lighting rods, lights, radios, and the like. For example, conventionally, radios were located in the shelter or cabinet  52 . However, which use different spectrum, e.g., 1.9 GHz, some radios are being located closer to the antennas  30 . Additionally, some configurations support the integration of the radios in the antennas  30 . 
     The UAV  50  is configured to provide the equipment, such as the antenna  30 , up the cell tower  12  to the appropriate location, i.e., the horizontal support structures  1100 ,  1102 . Note, the horizontal support structures  1100 ,  1102  can be located in the middle or the top of the cell tower  12 . The UAV  50  can include additional rotors  80  and the rotors  80  can be larger. Also, the body  82  can be larger as well. Generally, for the systems and methods described herein, the UAV  50  is configured to support equipment weighing a couple hundred pounds, such as, for example, 150-250 lbs. The UAV  50  can support the equipment through the robotic arms  600 . Also, the arms  60  can be fixed. In an exemplary embodiment, the UAV  50  does not require the arms  60  to move the equipment, but rather the entire UAV  50  moves the equipment and places it appropriately. However, the arms  600  are configured to hold the equipment during the flight and to release once positioned and connected to the horizontal support structures  1100 ,  1102 . 
     The arms  600  are configured based on the type of equipment they support. For example, the antennas  30  are typically rectangular, and the arms  600  can be configured to clasp a center portion of the antenna  30 . The UAV  50  generally flies vertically from the base of the cell tower  12  with the antenna  30  secured in the arms  600 . For example, the antenna  30  can be secured to the arms  600  on the ground at the base of the cell tower  12  by one or more installers. 
     Once secured, the UAV  50  can be manually, automatically, or a combination of both flown to the appropriate location on the cell tower  12 , i.e., the horizontal support structures  1100 ,  1102 . Note, the systems and methods contemplate an operator flying the UAV  50  as described herein. In another embodiment, the UAV  50  can operate autonomously or semi-autonomously, such as based on directional aids, location identifiers, objects of interest, or the like. For example, the UAV  50 , via a processor  102  or the like, can be programmed with the location on the horizontal support structures  1100 ,  1102  for placement. The UAV  50  can use the directional aids, location identifiers, objects of interest, or the like to direct the flight based on the location. 
     Referring to  FIG. 19 , in an exemplary embodiment, a diagram illustrates a view of the horizontal support structures  1100 ,  1102  and the antenna  30 . The horizontal support structures  1100 ,  1102  can include directional aids  1150  indicative of a location where the antenna  30  or other equipment is to be placed. The directional aids  1150  can be barcodes, Quick Response (QR) codes, a number, a symbol, a picture, a color, a phrase such as “drop here,” or combinations thereof. The directional aids  1150  can be detected and monitored by the camera  86  in the UAV  50  which can maintain a visual connection to determine proper flight, such as a feedback loop to automatically fly to the horizontal support structures  1100 ,  1102  to place the antenna  30 . Those of ordinary skill in the art will recognize the UAV  50  can use any autonomous flight algorithm with the directional aids  1150  providing the location to arrive at. 
     The horizontal support structures  1100 ,  1102  can include magnets  1152 , and the antenna  30  can also include magnets  1154 . In an exemplary embodiment, only one of the horizontal support structures  1100 ,  1102  and the antenna  30  include the magnets  1152 ,  1154 . In another exemplary embodiment, both the horizontal support structures  1100 ,  1102  and the antenna  30  include the magnets  1152 ,  1154 . Generally, the magnets  1152 ,  1154  can be used to hold the antenna  30  on the horizontal support structures  1100 ,  1102 , i.e., the UAV  50  can place the antenna  30  on the horizontal support structures  1100 ,  1102  with the magnets  1100 ,  1102 . The magnets  1152 ,  1154  can be permanent magnets or electrically energized magnets. For example, the magnets  1152 ,  1154  can be selectively magnetic using the electrically energized magnets. 
     This selective magnetic embodiment can be used to have the magnets  1152 ,  1154  for temporary use, i.e., the UAV  50  places the antenna  30  on the horizontal support structures  1100 ,  1102  with the magnets  1152 ,  1154  used to temporary hold the antenna  30  in place while the antenna is physically attached to the horizontal support structures  1100 ,  1102 . Once the antenna  30  is fixedly attached to the horizontal support structures  1100 ,  1102 , the magnets  1152 ,  1154  can be turned off. Note, the magnets  1152 ,  1154 , when energized or magnetic, may interfere with the antennas  30 . Thus, the selective magnetic embodiment allows for the magnets  1152 ,  1154  to become non-magnetic after they are fixed to the horizontal support structures  1100 ,  1102 . 
     The horizontal support structures  1100 ,  1102  are generally not drilled into and the attachment between the horizontal support structures  1100 ,  1102  and the antennas  30  can be a clamp  1156 . In an exemplary embodiment, the clamp  1156  is attached to the antenna  30  after the UAV  50  delivers the antenna  30  and has it held in place by the magnets  1152 ,  1154  by an installer on the cell tower. Here, the installer can perform the normal installation with the systems and methods providing a convenient and efficient mechanism to deliver the antenna  30 . 
     In another exemplary embodiment, the clamps  1156  have an automatic mechanical grabbing feature where no installer is required. Here, the UAV  50  can fly the antenna  30  to the clamps  1156  and the clamps  1156  can automatically attach to the antenna  30 . This automatic mechanical feature may or may not use the magnets  1152 ,  1154 . For example, the clamps  1156  can have a mechanical locking mechanism similar to handcuffs where the UAV  50  pushes the antenna  30  in and the clamps automatically lock. 
     In a further exemplary embodiment, the automatic mechanical feature can include other techniques such as a vacuum on the horizontal support structures  1100 ,  1102  or the antenna  30  which can selectively grab and connect. 
     In a further exemplary embodiment, the magnets  1152 ,  1154  can be used to hold the antenna  30  in place, and the robotic arms  600  can be used to fixedly attach the antenna  30 , such as via the clamps  1156 . All of the techniques described herein are also contemplated for operations during the installation. 
     §12.1 UAV-Based Installation Method 
     Referring to  FIG. 20 , in an exemplary embodiment, a flowchart illustrates an Unmanned Aerial Vehicle (UAV)-based installation method  1180  for equipment on cell towers. The UAV-based installation method  1180  includes flying the UAV with the equipment attached thereto upwards to a desired location on the cell tower, wherein the desired location includes one or more horizontal support structures (step  1182 ); positioning the equipment to the desired location on the cell tower (step  1184 ); connecting the equipment to the desired location (step  1186 ); and disconnecting the equipment from the UAV (step  1188 ). The UAV-based installation method  1180  can further include attaching the equipment to the UAV via one or more robotic arms prior to the flying. The equipment can include one or more of an antenna and a radio. The positioning can be via one or more directional aids located on the one or more horizontal support structures, wherein the directional aids are monitored via a camera associated with the UAV. The one or more directional aids can include one or more of barcodes, Quick Response (QR) codes, numbers, symbols, pictures, a color, a phrase, and a combination thereof. 
     The positioning can include temporarily fixing the equipment to the desired location for the connecting. The positioning can include attaching the equipment to the desired location via one or more magnets. The one or more magnets can be selectively energized for the positioning and the connecting and turned off subsequent to the connecting. The connecting can include attaching one or more clamps between the equipment and the one or more horizontal support structures. The one or more clamps can automatically connect to the equipment. The flying can be performed by an operator with assistance from one or more directional aids located on the one or more horizontal support structures. The flying can be performed by autonomously by the UAV based on one or more directional aids located on the one or more horizontal support structures. The UAV-based installation method  1180  can further include performing the disconnecting subsequent to the positioning; and using one or more robotic arms on the UAV to perform the connecting. 
     In another exemplary embodiment, an Unmanned Aerial Vehicle (UAV) used in installation of equipment on cell towers includes one or more rotors disposed to a body; wireless interfaces; one or more arms adapted to connect and disconnect from the equipment; a processor coupled to the wireless interfaces, the one or more rotors, and the one or more arms; and memory storing instructions that, when executed, cause the processor to: fly with the equipment attached to the one or more arms upwards to a desired location on the cell tower, wherein the desired location includes one or more horizontal support structures; position the equipment to the desired location on the cell tower; connect the equipment to the desired location; and disconnect the equipment from the UAV. 
     §13.0 Installation and Maintenance of Equipment on Cell Towers with Robotic Devices 
     Referring to  FIGS. 21A-21C , in various exemplary embodiments, diagrams illustrate different types of cell towers  12 , namely a self-support tower  12 A ( FIG. 21A ), a monopole tower  12 B ( FIG. 21B ), and a guyed tower  12 C ( FIG. 21C ). These three types of towers  12 A,  12 B,  12 C have different support mechanisms. The self-support tower  10 A can also be referred to as a lattice tower, and it is free standing, with a triangular base with three or four sides. The monopole tower  12 B is a single tube tower, and it is also free standing, but typically at a lower height than the self-support tower  12 A. The guyed tower  12 C is a straight rod supported by wires attached to the ground. 
     Referring to  FIG. 22 , in an exemplary embodiment, a block diagram illustrates a robotic device  1200  configured for use with the cell towers  12 A,  12 B,  12 C for installation and/or maintenance of cell site components  14  on the cell towers  12 A,  12 B,  12 C. The robotic device  1200  is configured to traverse up and down the cell tower  12  with climbing components  1202  and to perform physical manipulation of equipment, cabling, etc. with manipulation components  1204 . In addition to the climbing components  1202  and the manipulation components  1204 , the robotic device  1200  includes a body  1206  which may include power, physical support for the climbing components  1202  and the manipulation components  1204 , processing (e.g., the robotic device  1200  can include the mobile device  100  or equivalent disposed or associated with the body  1206 ). 
     Thus, the robotic device  1200  reduces or avoids tower climbs for installation and maintenance on equipment on the cell towers  12 . The robotic device  1200  can crawl to the top of the cell tower  12 , can be delivered by Unmanned Aerial Vehicles (UAV)  50 , can be delivered by the guide wire, can be delivered by a crane, pulley, etc. or the like. While on the cell tower  12 , the robotic devices  1200  can be used, either manually, autonomously, or a combination of both, to perform various tasks on cell tower components  14  such as antennas or the like. In an exemplary embodiment, the robotic device  1200  can be used to bring cabling up the cell tower  12  in conjunction with UAV-based systems and methods which install equipment such as antennas. 
     The climbing components  1202  are configured to allow the robotic device  1200  to traverse up and down the cell tower  12 . Those of ordinary skill in the art will recognize the robotic device  1200  can include any mechanism for climbing, but in an exemplary embodiment, the climbing components  1202  can include various wheels  1210 . For example, to traverse the self-support tower  12 A, the monopole tower  12 B, the guyed tower  12 C, etc., wheels  1210 A,  1210 B are on the body  1206  to roll up or down the tower  12  while a wheel  1210 C is spaced apart from the body  1206  via a member  1212  to keep the robotic device  1200  affixed to the tower  12  during transit. Also, this arrangement of the climbing components  1202  could be used with a guide wire to traverse up and down the cell tower  12 . 
     The manipulation components  1204  can include one or more robotic arms  1220  which can include a member  1222  which is rotatable or moveable relative to the body  1206  and a grasping device  1224  which can physically interact and/or manipulate with the cell site components  14 . The robotic device  1200  can include multiple arms  1220  in some embodiments and a single arm  1220  in another embodiment. 
     In another exemplary embodiment, the climbing components  1202  can be the same as the manipulation components  120 , such as when there is more than one robotic arm  1220 . Here, the robotic arms  1220  can be used to both install/manipulate the cell site components  14  as well as to climb the cell tower  12 . For example, the robotic arms  1220  can grasp stairs on the cell tower  12 , supports on a lattice tower, safety climb wires, or the like. 
     The climbing components  1202  may also include magnets including selectively enabled magnets. Note, the cell towers  12  include metal, and the magnets could be used to traverse up and down the cell tower  12 . 
     Thus, in operation, the climbing components  1202  are used to traverse up and down the cell tower as well as to maintain the robotic device  1200  in a stable position at a desired location on the cell tower  12 . Once at the desired location, the manipulation components  1204  are used to perform installation and/or maintenance. For example, the manipulation components  1204  can be controlled with a mobile device  100  or controller which is wirelessly connected to the robotic device  1200 , through a Heads Up Display (HUD) or Virtual Reality (VR) controller which is wirelessly connected to the robotic device  1200 , or the like. With the HUD or VR controller, an operator can remotely operate the robotic device  1200 , from the ground, thereby having arms in the sky without the tower climb. 
     The manipulation components  1204  can be used to perform similar functionality as the robotic arms  600 , including bringing the payload  602  up the cell tower  12 . In an exemplary embodiment, the manipulation components  1204  can be used to bring cabling up the cell tower  12 , such as in conjunction with the UAV-based installation method  1180 . 
     In an exemplary embodiment, a plurality of robotic devices  1200  can be used in combination. For example, the plurality of mobile devices  1200  can combine with one another at the desired location to form an aggregate robotic device. 
     Referring to  FIG. 23 , in an exemplary embodiment, a flowchart illustrates a method  1300  for installation and maintenance of cell site components with the robotic device  1200 . The method  1300  includes causing the robotic device to traverse up the cell tower to the desired location proximate to the cell site components (step  1302 ); once at the desired location and stabilized to the cell tower, causing manipulation components to perform one or more of installation and maintenance of the cell site components (step  1304 ); and, subsequent to the one or more of installation and maintenance of the cell site components, causing the robotic device to traverse down the cell tower (step  1306 ). 
     The robotic device traverses up and down the cell tower via climbing components associated with the robotic device. The climbing components can include a plurality of wheels configured to traverse the cell tower and stabilize the robotic device to the cell tower; a plurality of magnets; and a pulley system. The cell tower can include one of a self-support tower, a monopole tower, and a guyed tower, and climbing components for the robotic device are configured based on a type of the cell tower. 
     The manipulation components can include one or more members with robotic arms coupled thereto. The robotic device can include a body comprising a processor and wireless components; climbing components disposed to the body; and the manipulation components movably disposed to the body. 
     The causing can be performed by one of a mobile device and a controller wirelessly coupled to the robotic device. The causing can be performed by one of a Heads Up Display and a Virtual Reality controller wirelessly coupled to the robotic device. The robotic device can be utilized to bring a cable up the cell tower and to connect the cable to the cell site components. The cell site components can be installed by an Unmanned Aerial Vehicle (UAV). 
     In another exemplary embodiment, an apparatus for installation and maintenance of cell site components on a cell tower with a robotic device includes a wireless interface; a processor communicatively coupled to the wireless interface; and memory storing instructions that, when executed, cause the processor to cause the robotic device to traverse up the cell tower to the desired location proximate to the cell site components; once at the desired location and stabilized to the cell tower, cause manipulation components to perform one or more of installation and maintenance of the cell site components; and, subsequent to the one or more of installation and maintenance of the cell site components, cause the robotic device to traverse down the cell tower. 
     §14.0 Using Drones to Transport Maintenance Personnel to a Cell Tower 
     Referring to  FIGS. 24-26 , in various exemplary embodiments, diagrams illustrate drones  1450 ,  1452  and a single person propulsion system  1454  each adapted to transport a person up the cell tower  12 . Specifically,  FIG. 24  is a diagram of a drone adapted to transport a person up a cell tower;  FIG. 25  is a diagram of another drone adapted to transport a person up the cell tower; and  FIG. 26  is a diagram of a single person propulsion system adapted to transport a person up the cell tower. Those of ordinary skill in the art that any type of drone or propulsion system is contemplated herein. 
     The drones  1450 ,  1452  or the system  1454  are adapted to quickly and safely bring maintenance personnel up to the cell tower  12  in lieu of a tower climb. After performing numerous tower climbs for cell site audits, maintenance, installation, etc., a time study was performed which showed the process of a tower climb takes well over an hour, including suiting up with gear, climbing the cell tower  12 , clicking in and out of safety harnesses along the way, etc. Also, maintenance personnel are exhausted at the end of the tower climb. 
     The drone  1450  includes a support structure  1460  with a plurality of rotors thereon. A person (or multiple persons) are connected to the support structure  1460  via support wires or members  1462 . The person can sit in a seat  1464  or connect to the members  1462  via harnesses, a vest, etc. (not shown). The seat  1464  can include landing members  1466 . If the support wires or members  1462  are rigid members, the landing members  1466  can support the drone  1450  on the ground. If the support wires or members  1462  are wires, the support structure  1460  can land apart from the person, take off and lift the person. 
     The drone  1452  includes a single set of rotors  1470  connected to a motor  1472  which connects to a support member  1474  which extends for a distance and connects to a base  1476 . The base  1476  can support maintenance personnel through harnesses, a vest, or a seat. The base  1476  can connect to landing members  1478  which support the drone  1452  on the ground. A control system  1480  extends from the support member  1474  for control of the drone  1452 . 
     Both of the drones  1450 ,  1452  are specifically adapted to the task of raising and lowering people along the cell tower  12 . Specifically, the support wires or members  1462  and the support member  1474  have a significant length allowing the support structure  1460  or the rotors  1470  to clear the top of the cell tower  12 . In this manner, the drones  1450 ,  1452  can position a person directly adjacent to the cell tower  12  such as to a platform thereon without interfering, i.e., touching, causing damage, etc., to the cell tower  12  or the cell site components  14 . 
     In  FIG. 26 , the single person propulsion system  1454  is shown which includes a base  1490  which connects to one or more jet propulsion systems  1492  and a harness  1494 . Here, a person connects to the harness  1494  and uses the jet propulsion systems  1492  to go up the cell tower  12 . 
     Again, the present disclosure contemplates any other means of aerial propulsion such as helicopters, quadcopters, or the like. In an exemplary embodiment, a key aspect is any system should include enough length, i.e., a substantial length, between the aerial flying components and any maintenance personnel such that the aerial flying components can extend over the height of the cell tower  12  such that the cell tower  12  and the cell site components  14  are protected and such that the maintenance personnel can be placed directly adjacent to a desired location on the cell tower  12 . The substantial length can be 20-40 feet or the like. Note, the drones  1450 ,  1452  only require substantially vertical flight to go up and down. Thus, having the flying components significantly higher than the person is not an issue. 
     Referring to  FIG. 27 , in an exemplary embodiment, a diagram illustrates a cell tower with various platforms  1500  for receiving a person from a drone or the like. Using drones, it is necessary to have a place to locate maintenance personnel on the cell tower  12 . In an exemplary embodiment, the cell tower  12  can include fixed or removable platforms  1500  for the drones  1450 ,  1452  or the like to place the personnel and for the personnel to get back in the drones  1450 ,  1452  to fly back to the ground. The drones  1450 ,  1452  can include a connection to safely connect to the platforms  1500  for stability during ingress and egress. 
     In an exemplary embodiment, the platforms  1500  are fixed, i.e., built into the cell tower  12 . In another exemplary embodiment, the platforms  1500  are selectively removable and can be added by the maintenance personnel on an as needed basis. For example, the platform  1500  can also be connected to the drones  1450 ,  1452  and be locked into place on the cell tower  12  during maintenance. After maintenance and after the personnel are back in the drones  1450 ,  1452 , the platforms  1500  can be removed and brought back to the ground with the personnel. 
     The present disclosure can be used for site audits, site surveys, maintenance, and installation to avoid slow, inefficient tower climbs. In an exemplary embodiment, at least two drones  1450 ,  1452  can be on site—one for operation and one for backup. 
     The drones  1450 ,  1452  can operate autonomously based on location identification information since the flight plan here is constrained to a small area, i.e., just at the cell tower  12 . For example, using a GUI or the like, an exact position can be specified such as on a map, 3D model, photograph or the like, and the drones  1450 ,  1452  can automatically fly to this location, avoiding the cell tower  12  or cell site components  14 . In another exemplary embodiment, the drones  1450 ,  1452  can fly under control of the person therein or via remote control from an operator. 
     In an exemplary embodiment, the drones  1450 ,  1452  are configured to bring the person to the top of the cell tower  12 , and if there is a need to access lower cell site components  14 , the person can perform a tower climb down, using safety harnesses, etc. Climbing down slightly is quick and does not exhaust the same amount of physical resources. 
     Referring to  FIG. 28 , in an exemplary embodiment, a flowchart illustrates a method  1550  for transporting maintenance personnel to a cell tower  12 . The method  1550  includes, responsive to a requirement for a tower climb for one or more of a site survey, a site audit, maintenance, and installation at the cell tower, securing a person in a drone, wherein the drone comprises flight components at a substantial length from the person allowing the flight components to fly over a top of the cell tower and to place the person directly adjacent to a desired location on the cell tower (step  1552 ); flying the drone up the cell tower to locate the person directly adjacent to the desired location (step  1554 ); and performing the one or more of a site survey, a site audit, maintenance, and installation at the cell tower (step  1556 ). 
     The method  1550  can further include connecting to a platform on the cell tower for the person to egress and ingress to the drone. The platform can be transported with the drone and selectively connected to the cell tower by the person. The drone can include a support structure with a plurality of rotors and support wires or members for the securing, wherein the support wires or members comprise the substantial length. The drone can include a single set of rotors connected to a motor connected to a base via a support member, wherein the person is secured to the base, and wherein the support member comprises the substantial length. The drone can include a single person propulsion system. The drone can be automatically guided to the desired location based on location identifiers and wherein the desired location is set via a Graphical User Interface or three-dimensional model of the cell tower. The drone can be one of manually operated by the person and by remote control via an operator. The method  1550  can further include maintaining a second drone for backup. The substantial length can be at least 20 feet. 
     In another exemplary embodiment, a drone for transporting maintenance personnel at a cell tower includes one or more rotors connected to a structure; one or more support members connected to the structure, wherein a person is selectively secured to the one or more support members, wherein the one or more support members comprise a substantial length from the person to the one or more rotors allowing the one or more rotors to fly over a top of the cell tower and to place the person directly adjacent to a desired location on the cell tower; wherein, responsive to a requirement for a tower climb for one or more of a site survey, a site audit, maintenance, and installation at the cell tower, the drone is adapted to fly the person up the cell tower for performance thereof. The drone can further include a connector adapted to connect to a platform on the cell tower for the person to egress and ingress to the drone. The platform can be transported with the drone and selectively connected to the cell tower by the person. 
     The drone can include a plurality of rotors and the one or more support members comprise support wires or members connected to the structure for the securing, wherein the support wires or members comprise the substantial length. The one or more rotors can include a single set of rotors connected to a motor on the structure, and the one or more support members comprise a single support member, wherein the person is secured to a base connected to the single support member, and wherein the single support member comprises the substantial length. The drone can include a single person propulsion system. The drone can be automatically guided to the desired location based on location identifiers and wherein the desired location is set via a Graphical User Interface or three-dimensional model of the cell tower. The drone can be one of manually operated by the person and by remote control via an operator. A second drone can be maintained at the cell tower for backup. The substantial length can be at least 20 feet. 
     §15.0 UAV Counterbalancing Techniques 
     Referring to  FIGS. 29A, 29B, and 29C , in exemplary embodiments, diagrams illustrate various counterbalance techniques for the UAV  50  including an extendible arm  1600  ( FIG. 29A ), opposing robotic arms  600 A ( FIG. 29B ), and moveable weights  1650  ( FIG. 29C ). As described herein, the UAV  50  can be used with the robotic arms  600 , the payload  602 , the connection  604 , etc. The UAV  50  can be used to attach the antenna  30  to the horizontal support structures  1100 ,  1102 , and the like. In these applications and others, the UAV  50  has weight distribution change while in flight. Accordingly, the UAV counterbalancing techniques are presented to compensate for weight distribution change in flight to avoid negative impact on the UAV  50  flight. 
     Variously, the counterbalancing techniques ensure weight distribution on the UAV  50  remains substantially the same despite moving members on the UAV  50 , e.g., robotic arms  600 , the connection  604 , etc. In  FIG. 29A , a first counterbalancing technique includes the extendable arm  1600  which can extend coincident with movement of the robotic arms  600  to offset any weight distribution changes. The extension can be in substantially an opposite direction as the robotic arms  600  and controlled by the processor  102  in the UAV  50  to ensure the weight distribution remains substantially the same. The extendable arms  1600  can move back and forth while the robotic arms  600  move as well to continually balance the weight distribution. The processor  102  can implement a process to balance the UAV  50  based on feedback from sensors associated with the UAV  50 , such as an accelerometer or the like. The extendible arms  1600  can also extend in the embodiment where the connection  604  extends from the UAV  50  to connect to the cell tower  12 , again to offset the weight distribution changes. 
     In  FIG. 29B , a second counterbalancing technique includes a second set of robotic arms  600 A located on an opposite side of the UAV  50  from the robotic arms  600 . Here, any movement by the robotic arms  600  can be mirrored by the second set of robotic arms  600 A in the opposite direction. The robotic arms  600 ,  600 A can be substantially the same including about the same weight. Thus, opposing movement offsets any weight distribution changes. The benefit of this approach is it requires a less sophisticated tracking process, i.e., the movements are just opposed versus taking sensor measurements and making changes accordingly. Also, either set of robotic arms  600 ,  600 A could be used for operations thereby making the UAV  50  flight more convenient. 
     In  FIG. 29C , a third counterbalancing technique includes the moveable weights  1650  which can be disposed or attached to the UAV  50 , such as on a lower portion. The moveable weights  1650  include one or more weight plates  1650 , ball bearings, etc. which have different weights and weight distribution. The direction or orientation of the plates  1650 , ball bearings, etc. can be changed via a rotating member  1654 . In this manner, the moveable weights  1650  can provide various different weight profiles to counterbalance any movement of items on the UAV  50 , such as the robotic arms  600 , the payload  602 , etc. The moveable weights  1650  can be controlled in a similar manner as the extendible arm  1600 . 
     §16.0 UAV Landing Zones at Cell Sites 
     Referring to  FIG. 30 , in an exemplary embodiment, a perspective diagram illustrates a cell site  10  with the surrounding geography  1700 .  FIG. 30  is an example of a typical cell site; those skilled in the art will recognize different configurations are also contemplated. The cell tower  12  can generally be classified as a self-support tower, a monopole tower, and a guyed tower. These three types of cell towers  12  have different support mechanisms. The self-support tower can also be referred to as a lattice tower, and it is free standing, with a triangular base with three or four sides. The monopole tower is a single tube tower, and it is also free standing, but typically at a lower height than the self-support tower. The guyed tower is a straight rod supported by wires attached to the ground. The guyed tower needs to be inspected every 3 years, or so, the self-support tower needs to be inspected every 5 years, and the monopole tower needs to be inspected every 7 years. 
     A typical cell site  10  can include the cell tower  12  and the associated cell site components  14  as described herein. The cell site  10  can also include the shelter or cabinet  52  and other physical structures—buildings, outside plant cabinets, etc. The cell site  10  can include aerial cabling, an access road  1702 , trees, etc. The cell site operator is concerned generally about the integrity of all of the aspects of the cell site  10  including the cell tower  12  and the cell site components  14  as well as everything in the surrounding geography  1700 . In general, the surrounding geography  1700  can be about an acre; although other sizes are also seen. Physical ingress and egress to the cell site  10  may be via the access road  1702 . Also, the cell site  10  may have a fence  1704  or the like with a gate  1706 . 
     In various exemplary embodiments, the present disclosure uses the cell site  10  and/or the surrounding geography  1700  for landing/take-off of the UAVs  50 . Specifically, the present disclosure contemplates the UAVs  50  in any configuration such as commercial, government, hobby use, etc. and not solely for the UAVs  50  performing operations at the cell site  10 . Again, the vast number of cell sites  10 , the geographic diversity, and the minimal traffic make the cell sites  10  ideal locations for UAV  50  landing and take-off. 
     As described herein, landing zones are defined and include various structures at the cell site  10  and/or the surrounding geography  1700 . The various structures can include platforms or the like on any component at the cell site  10  described as follows. The landing zones contemplate the UAVs  50  landing for various purposes along with supporting equipment, access privileges, etc. The purposes can include battery recharge, battery replacement, maintenance, emergency landing, pick up or drop off of cargo, or the like. These purposes can be categorized as manual purposes that require personnel to access the UAV  50  and thus need to be low to the ground or accessible from the ground and automated purposes that require no access to the UAV  50 . For example, the battery recharge, emergency landing, or battery replacement can automated purposes whereas the battery replacement, the maintenance, emergency landing, pick up or drop off of cargo can be manual purposes (note, some of these purposes can be in both categories). 
     Generally, the present disclosure provides 1) landing zone definition at the cell site or surrounding geography  1700 , 2) structures for the landing zones, 3) additional equipment to support the purposes above, and 4) access privileges for personnel to the cell site  10  for some of the purposes above. Each of these is described as follows. 
     §16.1 Landing Zone Definition 
     Variously, a landing zone  1750  can be anywhere at the cell site  10  or the surrounding geography. For example,  FIG. 30  illustrates various locations for the landing zone  1750  including on the cell tower  12  at an intermediate point, on top of the cell tower  12 , on the shelter or cabinet  52 , near the cell tower  12  or the shelter or cabinet  52 , on the access road  1702 , outside of the fence  1704  (anywhere including at the gate  1706 ), on the fence  1704 , etc. The landing zone  1750  can include a platform structure ( FIG. 31 ) when required such as when the landing zone  1750  is on the cell tower  12 , on the shelter or cabinet  52 , on the fence  1704 . Alternatively, the landing zone  1750  can be a paved structure, dirt, gravel, etc. such as when the landing zone  1750  is near the shelter or cabinet  52  or cell tower  12 , on the access road  1702 , or outside the fence  1704 . 
     §16.2 Landing Zone Structures 
     Referring to  FIG. 31 , in an exemplary embodiment, a perspective diagram illustrates another view of the cell site  10  and the surrounding geography  1700  for illustrating exemplary structures  1760  or markings  1770  for the landing zones  1750 . The structures  1760  for the landing zones  1750  can be metal, mesh, etc. platforms located on the cell tower  12 , on top of the cell tower  12 , on the cabinet or shelter  52 , on the fence  1704 , on the ground in the surrounding geography  1700 , etc. The markings  1770  can be painted, landscaped, gravel, etc. Note, the landing zone  1750  location is based on the purposes—automated or manual supported at the particular cell site  10 . 
     §16.3 Additional Equipment for Supporting UAV-Related Purposes at the Cell Site 
     In addition to the landing zone structures  1760 , the cell site  10  and/or the surrounding geography  1700  can include additional equipment to support the various purposes. In an exemplary embodiment, the cell site  10  can include a battery recharge station  1780  where the UAV  50  can land and automatically connect to recharge its onboard battery. For example, the UAV  50  can land on the structure  1760  and automatically connect to the battery recharge station  1780 . Various approaches are contemplated. First, the battery recharge station  1780  could use inductive charging where the UAV  50  is in close proximity to the battery recharge station  1780 . Second, the battery recharge station  1780  can include a connection that extends from it and connects to the UAV  50  for charging. Third, the UAV  50  can include a connection that extends from it and connects to the battery recharge station  1780  for charging. Fourth, a person can manually connect the UAV  50  and the battery recharge station  1780 . Of course, other embodiments are contemplated. The additional equipment can also include other types of equipment such as storage housings for the UAVs  50 , maintenance equipment, storage locations for cargo from the UAVs  50 , storage housings for used or depleted batteries, etc. 
     §16.4 Access Privileges for the Cell Site 
     Finally, for the various purposes and specifically for the manual purposes, there is a requirement to provide some form of access privileges to the cell site  10  for associated personnel related to the UAVs  50 . First, the access privileges are required where the landing zone  1750  is within the fence  1704 . For example, if the landing zone  1750  is outside the fence  1704 , the access privileges can be that personnel are allowed to access the landing zone  1750 . If the landing zone  1750  is within the fence  1704 , etc., the access privileges include the right and any security measures for personnel to enter the cell site  10  and/or the surrounding geography  1700 . 
     As noted herein, the cell site operator can see additional revenue from operating the landing zones  1750 . However, there are security concerns related to additional traffic at the cell site  10 . The access privileges can include security codes, ID badges, RFID cards, etc. to allow a certified person access to the cell site  10 , e.g., such as through the gate  1706 . Automated processes can keep track of ingress and egress which can be used to monitor and prevent security issues. 
     Although the present disclosure has been illustrated and described herein with reference to preferred embodiments and specific examples thereof, it will be readily apparent to those of ordinary skill in the art that other embodiments and examples may perform similar functions and/or achieve like results. All such equivalent embodiments and examples are within the spirit and scope of the present disclosure, are contemplated thereby, and are intended to be covered by the following claims.