Detecting, monitoring and communicating with unmanned aircraft systems

Abstract

Systems and methods for detecting, monitoring, and communicating with unmanned aerial vehicle (UAV) systems are provided. The system allows individuals to set desired perimeters. The system monitors communication signals from nearby UAVs to determine whether a UAV has intruded into the desired perimeter. The system is configured to identify UAVs within the desired perimeter and collect and store their flight information. The system is configured to send communications to the UAV's operator and, as needed, to send communications to relevant authorities.

Description

Technical Field

[0001] This disclosure generally relates to unmanned aircraft (“UA”) and unmanned aircraft systems (“UAS”), and specifically to identifying the presence of a UA and communicating with the operator of the UAS. Background Technology

[0002] Unmanned aerial vehicle (UAV) systems typically consist of three parts: the aircraft, the controller used by the operator to control the aircraft's flight, and the communication link between the aircraft and the controller. UAVs are commonly referred to as drones, unmanned aerial vehicles ("UAVs"), or UAs, and can be either fixed-wing or rotary-wing. UAV systems are also commonly referred to as remotely piloted aircraft systems ("RPAS") or UASs.

[0003] With the increasing popularity of User-Agent Flight Systems (UAS), many enthusiasts and recreational users enjoy piloting UAS for entertainment and creating content for social media. A growing concern with UAS is that operators may intentionally or unintentionally fly UAS over crowds in private or public areas, and this proximity is perceived as an invasion of privacy. Therefore, a system and methodology are needed to overcome these significant problems. Summary of the Invention

[0004] This disclosure provides a system and method for addressing significant issues related to UASs, which are increasingly operating near individuals and businesses in public and private locations. The system operates to allow individuals approaching an unknown UAS to identify the UAS and capture its flight data. The system also facilitates individuals approaching an unknown UAS to send messages to the operator of that UAS. Where feasible, the system also facilitates reporting the UAS to the Federal Aviation Administration (“FAA”) or other relevant authorities.

[0005] In some aspects, the technology disclosed herein relates to a system comprising: a user equipment including: a wireless receiver configured to receive wireless communication signals from an unmanned aerial vehicle (UAV) near the user equipment; a non-transitory computer-readable medium configured to store executable programming modules; a processor communicatively coupled to the wireless receiver and the non-transitory computer-readable medium, the processor being configured to execute one or more programming modules stored in the non-transitory computer-readable medium to process signals received from the UAV by the wireless receiver and to identify the UAV; and a server device including: a non-transitory computer-readable medium configured to store executable programming modules; and a processor communicatively coupled to the non-transitory computer-readable medium, the processor being configured to execute one or more programming modules stored in the non-transitory computer-readable medium to process signals received from the user equipment, identify an operator corresponding to the UAV, and send messages to the operator of the UAV.

[0006] In some aspects, the technology disclosed herein relates to a user equipment comprising: a wireless receiver configured to receive wireless communication signals from an unmanned aerial vehicle (UAV) near the user equipment; a non-transitory computer-readable medium configured to store executable programming modules; and a processor communicatively coupled to the wireless receiver and the non-transitory computer-readable medium, the processor being configured to execute one or more programming modules stored in the non-transitory computer-readable medium to: process the signals received from the UAV by the wireless receiver to identify the UAV; identify the operator corresponding to the UAV; and send messages to the operator of the UAV.

[0007] In some aspects, the technology disclosed herein relates to a system comprising at least one processor communicatively coupled to at least one non-transitory computer-readable medium, wherein the at least one processor is programmed to: receive wireless communication signals from an unmanned aerial vehicle (UAV); parse the wireless communication signals to obtain an identifier corresponding to the UAV; use the identifier to determine the operator of the UAV; obtain the contact information of the UAV; and send a message to the operator of the UAV.

[0008] In some respects, the technology disclosed herein relates to a method in which one or more processors are programmed to perform the following steps: receiving wireless communication signals from an unmanned aerial vehicle (UAV); parsing the wireless communication signals to obtain an identifier corresponding to the UAV; using the identifier to determine the operator of the UAV; obtaining contact information of the UAV operator; and sending a message to the UAV operator.

[0009] In some respects, the technology disclosed herein relates to a non-transitory computer-readable medium having stored thereon one or more instruction sequences for causing one or more processors to perform the following steps: receiving wireless communication signals from an unmanned aerial vehicle (UAV); parsing the wireless communication signals to obtain an identifier corresponding to the UAV; using the identifier to determine the operator of the UAV; obtaining contact information of the UAV operator; and sending a message to the UAV operator.

[0010] Other features and advantages of the present invention will be more readily understood by those skilled in the art after reading the following detailed description and accompanying drawings. Attached Figure Description

[0011] The structure and working principle of the present invention can be understood by reading the following detailed embodiments and accompanying drawings, wherein the same reference numerals refer to the same components, as follows:

[0012] Figure 1 This is a block diagram illustrating an exemplary prior art unmanned aerial vehicle system according to an embodiment of the present invention;

[0013] Figure 2 An exemplary communication infrastructure according to one embodiment is shown, in which one or more processing flows described herein may be implemented;

[0014] Figure 3 An exemplary processing system according to one embodiment is shown, through which one or more processing flows described herein may be executed;

[0015] Figure 4 This is a block diagram illustrating an exemplary spherical radius perimeter according to an embodiment of the present invention;

[0016] Figure 5 This is a block diagram illustrating another exemplary spherical radius perimeter according to an embodiment of the present invention;

[0017] Figure 6 This is a block diagram of an exemplary unmanned aerial vehicle system according to an embodiment of the present invention;

[0018] Figure 7 This is a block diagram of an exemplary unmanned aerial vehicle system according to an embodiment of the present invention;

[0019] Figure 8 This is a flowchart illustrating an exemplary processing flow for establishing a perimeter according to an embodiment of the present invention;

[0020] Figure 9 This is a flowchart illustrating an exemplary processing flow for monitoring User Agents according to an embodiment of the present invention;

[0021] Figure 10This is a flowchart illustrating an exemplary processing flow for communicating with an operator of a User Agent (UA) according to an embodiment of the present invention.

[0022] Figure 11 This is a flowchart illustrating an exemplary processing flow for communicating with a UA according to an embodiment of the present invention;

[0023] Figure 12 This is a flowchart illustrating an exemplary processing flow for communicating with a UA according to an embodiment of the present invention;

[0024] Figure 13 This is a flowchart illustrating an exemplary processing procedure for reporting flight data corresponding to the UAS, according to an embodiment of the present invention. Detailed Implementation Plan

[0025] This document discloses systems, methods, and non-transitory computer-readable media for detecting and monitoring unmanned aerial vehicle (UAV) systems and communicating with them. For example, one method disclosed herein allows a user device to identify a UAV within a certain short range and collect and store flight information corresponding to that UAV. The method also allows the user to send messages to the UAV's operator and, as needed, report the UAV and its operator to the FAA or other competent authorities.

[0026] Those skilled in the art will readily understand how the invention can be implemented in various alternative embodiments and applications after reading this specification. However, although various embodiments of the invention will be described herein, it should be understood that these embodiments are presented by way of example only and do not constitute limitation. Therefore, the detailed description of various alternative embodiments in this specification should not be construed as limiting the scope or breadth of the invention as defined in the appended claims.

[0027] Figure 1 This is a block diagram illustrating an exemplary prior art unmanned aerial vehicle (UAS) system 100 according to an embodiment of the present invention. In the prior art, the UAS 100 includes a UA 110, a controller 120, and a communication link 130. The controller 120 is configured to be operated by an operator 140, who uses the controller 120 to send flight commands to the UA 110 via the communication link 130. In one aspect, the operator 140 may be equipped with a wireless communication device 150, which communicates with the controller 120 via a wired or wireless communication link 160.

[0028] 1. System Overview

[0029] 1.1 Infrastructure

[0030] Figure 2An exemplary infrastructure 200 according to one embodiment is illustrated, in which one or more processing flows disclosed herein may be implemented. The infrastructure may include a platform 210 (e.g., one or more servers) that hosts and / or performs one or more of the various functions, processing flows, methods, and / or software modules described herein. Platform 210 may include dedicated servers, or alternatively, cloud instances that utilize shared resources of one or more servers. These servers or cloud instances may be located in the same location and / or geographically distributed. Platform 210 may also include server application 212 and / or one or more databases 214, or communicate with them. Furthermore, platform 210 may communicate with one or more user systems 230 via one or more networks 220. Platform 210 may also communicate with one or more external systems 250 (e.g., other platforms, servers, websites, etc.) via one or more networks 220. In one embodiment, platform 210 may also communicate with one or more unmanned aerial vehicle systems 240 via one or more networks 220.

[0031] Network 220 may include the Internet. Platform 210 may use standard transfer protocols such as Hypertext Transfer Protocol (HTTP), Secure Hypertext Transfer Protocol (HTTPS), File Transfer Protocol (FTP), Secure File Transfer Protocol (FTPS), Secure Shell File Transfer Protocol (SFTP), and proprietary protocols to communicate with user system 230 via the Internet. Although platform 210 is shown connected to various systems via a set of networks 220, it should be understood that platform 210 may connect to various systems via one or more different sets of networks. For example, platform 210 may connect to a subset of user systems 230 and / or external systems 250 via the Internet, and connect to one or more other user systems 230 and / or external systems 250 via an intranet. Furthermore, although only a small number of user systems 230, external systems 250, a server application 212, and a set of databases 214 are shown in the figure, it should be understood that the infrastructure may include any number of user systems, external systems, server applications, and databases.

[0032] User system 230 may include any type of computing device capable of wired and / or wireless communication, including but not limited to desktop computers, laptops, tablets, smartphones or other mobile phones, home security systems, vehicle security systems, other security systems, servers, game consoles, head-mounted displays, etc. User system 230 is configured to receive wireless signals broadcast by drones, such as drone 244, within signal range.

[0033] Platform 210 may include a web server hosting one or more websites and / or network services. In embodiments providing websites, the websites may include a graphical user interface, such as one or more pages (e.g., web pages) generated in Hypertext Markup Language (HTML) or other languages. Platform 210 sends or provides one or more pages of the graphical user interface in response to a request from user system 230. In some embodiments, these pages may be provided in a wizard-like manner, i.e., two or more pages are provided sequentially, and one or more sequential pages may depend on the user or user system 230's interaction with one or more previous pages. Requests sent to platform 210 and responses from platform 210 (including pages of the graphical user interface) may be transmitted over network 220 (which may include the Internet) using standard communication protocols such as HTTP, HTTPS, etc. These pages (such as web pages) may contain a combination of content and elements, such as text, images, videos, animations, references (such as hyperlinks), frames, input components (such as text boxes, text areas, checkboxes, radio buttons, drop-down menus, buttons, forms, etc.), scripts (such as JavaScript), and elements composed of or derived from data stored in one or more databases (such as database 214) that are accessible locally and / or remotely by platform 210. Platform 210 may also respond to other requests from user system 230.

[0034] Platform 210 may also include one or more databases 214, communicatively coupled to, or otherwise accessed by, said databases. For example, platform 210 may include one or more database servers for managing the one or more databases 214. User system 230 or server application 212 running on platform 210 may submit data to be stored in database 214 (such as user data, form data, etc.) and / or request access to data stored in database 214. Any suitable database may be used, including but not limited to MySQL™, Oracle™, IBM™, Microsoft SQL™, Access™, PostgreSQL™, etc., including cloud-based databases and proprietary databases. For example, data may be sent to platform 210 using well-known HTTP-supported POST requests, via FTP, and / or similar methods. This data, along with other requests, may be processed, for example, by server-side web technologies executed by platform 210, such as servlets or other software modules (e.g., included in server application 212).

[0035] In embodiments providing web services, platform 210 may receive requests from external system 250 and provide responses in Extensible Markup Language (XML), JavaScript Object Notation (JSON), and / or any other suitable or desired format. In such embodiments, platform 210 may provide an Application Programming Interface (API) that defines how user system 230 and / or external system 250 interact with the web service. Therefore, user system 230 and / or external system 250 (which may itself be a server) may define its own user interface and rely on the web service to implement or provide the backend processing flows, methods, functions, storage, etc., described herein. For example, in this embodiment, client application 232 executing on one or more user systems 230 may interact with server application 212 executing on platform 210 to perform one or more or a portion of the various functions, processing flows, methods, and / or software modules described herein. Client application 232 may be a "thin client," meaning that the processing is primarily performed on the server side by server application 212 on platform 210. A basic example of a thin client application 232 is a browser application that only requests, receives, and renders web pages on user system 230, while server application 212 on platform 210 is responsible for generating web pages and managing database functions. Alternatively, the client application can be a "fat client," where processing is primarily performed on the client by user system 230. It should be understood that, depending on the design goals of a particular implementation, client application 232 may perform a certain amount of processing relative to server application 212 on platform 210, somewhere between a "thin client" and a "fat client." In either case, the application described herein may reside entirely on platform 210 (e.g., all processing is performed by server application 212) or on user system 230 (e.g., all processing is performed by client application 232), or be distributed between platform 210 and user system 230 (e.g., both server application 212 and client application 232 perform processing), and may include one or more executable software modules to implement one or more processing flows, methods, or functions of the application described herein.

[0036] The unmanned aerial vehicle (UAV) system 240 includes a controller 242, a UAV 244, and a communication link between the controller 242 and the UAV 244. In one embodiment, the communication link may be one or more networks 220; in an alternative embodiment, the communication link may be direct wireless communication. As described above, the controller 242 is configured to be operated by an operator who uses the controller 242 to send flight commands to the UAV 244 via the communication link 220.

[0037] External system 250 may include various types of servers, such as web servers, software-as-a-service servers, and data storage servers. External system 250 may be owned and operated by third parties, such as individuals or entities, government agencies, quasi-governmental agencies, etc. In one embodiment, external system 250 is operated by or on behalf of the FAA.

[0038] 1.2 Exemplary Processing Device

[0039] Figure 3 A block diagram of an exemplary wired or wireless system 300 that can be used in conjunction with the various embodiments described herein is shown. For example, system 300 may be used as, or in conjunction with, one or more of the functions, processes, or methods described herein (e.g., for storing and / or executing an application or one or more software modules of an application), and may represent components of platform 210, user system 230, controller 242 and drone 244 of UAS 240, external system 250, and / or other processing devices described herein. System 300 may be a server, any conventional personal computer, or any other processor-enabled device capable of wired or wireless data communication. Those skilled in the art will readily understand that other computer systems and / or architectures may also be used.

[0040] System 300 preferably includes one or more processors, such as processor 310. Additional processors may also be provided, such as auxiliary processors for managing input / output, auxiliary processors for performing floating-point mathematical operations, dedicated microprocessors (such as digital signal processors) with architectures suitable for fast execution of signal processing algorithms, slave processors (such as back-end processors) subordinate to the main processing system, additional microprocessors or controllers for dual-processor or multi-processor systems, and / or coprocessors. Such auxiliary processors may be discrete processors or integrated with processor 310. Examples of processors that may be used in system 300 include, but are not limited to, Pentium® processors, Core i7® processors, and Xeon® processors manufactured by Intel Corporation (Santa Clara, California).

[0041] Processor 310 is preferably connected to communication bus 305. Communication bus 305 may include a data channel to facilitate information transfer between the memory of system 300 and other peripheral components. Furthermore, communication bus 305 may provide a set of signals for communicating with processor 310, including a data bus, address bus, and / or control bus (not shown). Communication bus 305 may include any standard or non-standard bus architecture, such as Industry Standard Architecture (ISA), Extended Industry Standard Architecture (EISA), Micro Channel Architecture (MCA), Peripheral Component Interconnect (PCI) local bus architecture, and standards issued by the Institute of Electrical and Electronics Engineers (IEEE) (including IEEE 488 Universal Interface Bus (GPIB), IEEE 696 / S-100, etc.).

[0042] System 300 preferably includes main memory 315, and may also include auxiliary memory 320. Main memory 315 provides storage for instructions and data for programs executed on processor 310 (such as one or more functions and / or modules described herein). It should be understood that programs stored in memory and executed by processor 310 can be written and / or compiled in any suitable language, including but not limited to C / C++, Java, JavaScript, Perl, Visual Basic, .NET, etc. Main memory 315 is typically a semiconductor-based memory, such as dynamic random access memory (DRAM) and / or static random access memory (SRAM). Other semiconductor-based memory types include synchronous dynamic random access memory (SDRAM), Rambus dynamic random access memory (RDRAM), ferroelectric random access memory (FRAM), etc., including read-only memory (ROM).

[0043] The auxiliary storage 320 may optionally include internal media 325 and / or removable media 330. The removable media 330 can be read and / or written in any known manner. The removable storage media 330 may be, for example, a magnetic tape drive, an optical disc (CD) drive, a digital versatile optical disc (DVD) drive, other optical drives, a flash memory drive, etc.

[0044] Auxiliary storage 320 is a non-transitory computer-readable medium that stores computer-executable code (such as publicly available software modules) and / or other data. Computer software or data stored in auxiliary storage 320 is read into main memory 315 for execution by processor 310.

[0045] In an alternative embodiment, auxiliary memory 320 may include other similar means for allowing computer programs or other data or instructions to be loaded into system 300. Such means may include, for example, a communication interface 345 that allows software and data to be transferred from external storage medium 350 to system 300. Examples of external storage medium 350 may include external hard disk drives, external optical drives, external magneto-optical drives, etc. Other examples of auxiliary memory 320 may include semiconductor-based memories such as programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable read-only memory (EEPROM), and flash memory (a block memory similar to EEPROM).

[0046] As described above, system 300 may include a communication interface 345. Communication interface 345 allows software and data to be transferred between system 300 and external devices (such as printers), networks, or other information sources. For example, computer software or executable code can be transferred from a network server (such as platform 110) to system 300 via communication interface 345. Examples of communication interface 345 include built-in network adapters, network interface cards (NICs), PCMCIA network cards, card bus network adapters, wireless network adapters, Universal Serial Bus (USB) network adapters, modems, wireless data cards, communication ports, infrared interfaces, IEEE 1394 FireWire interfaces, and any other devices that enable system 300 to interface with a network (such as network 220) or other computing devices. The communication interface 345 preferably implements industry-issued protocol standards, such as Ethernet IEEE 802, Fibre Channel, Digital Subscriber Line (DSL), Asymmetric Digital Subscriber Line (ADSL), Frame Relay, Asynchronous Transfer Mode (ATM), Integrated Services Digital Network (ISDN), Personal Communication Services (PCS), Transmission Control Protocol / Internet Protocol (TCP / IP), Serial Line Internet Protocol / Point-to-Point Protocol (SLIP / PPP), etc., but may also implement custom or non-standard interface protocols.

[0047] Software and data transmitted via communication interface 345 are typically in the form of electrical communication signals 360. These signals 360 can be provided to communication interface 345 via communication channel 355. In one embodiment, communication channel 355 can be a wired or wireless network (such as network 220), or various other communication links. Communication channel 355 carrying signals 360 can be implemented using various wired or wireless communication methods, such as wires or cables, optical fibers, conventional telephone lines, cellular telephone links, wireless data communication links, radio frequency (“RF”) links, infrared links, etc.

[0048] Computer-executable code (such as computer programs, for example, publicly disclosed application programs or software modules) is stored in main memory 315 and / or secondary memory 320. Computer programs may also be received via communication interface 345 and stored in main memory 315 and / or secondary memory 320. When executed, such computer programs cause system 300 to perform various functions of the disclosed embodiments described in other parts of this document.

[0049] In this specification, the term "computer-readable medium" is used to refer to any non-transitory computer-readable storage medium used to provide or within system 300 computer-executable code and / or other data. Examples of such media include main memory 315, secondary memory 320 (including internal memory 325, removable media 330, and external storage media 350), and any peripheral device (including a network information server or other network device) communicatively coupled to communication interface 345. These non-transitory computer-readable media are carriers for providing executable code, programming instructions, software, and / or other data to system 300.

[0050] In embodiments implemented in software, the software may be stored on a computer-readable medium and loaded into system 300 via removable medium 330, input / output interface 335, or communication interface 345. In this embodiment, the software is loaded into system 300 in the form of an electrical communication signal 360. When executed by processor 310, the software preferably causes processor 310 to perform one or more processing flows and functions described in other parts of this document.

[0051] In one embodiment, the input / output interface 335 provides an interface between one or more components of the system 300 and one or more input and / or output devices 340. Exemplary input devices include, but are not limited to, sensors, keyboards, touchscreens or other touch-sensitive devices, biometric sensing devices, computer mice, trackballs, pen pointing devices, etc. Exemplary output devices include, but are not limited to, other processing devices, cathode ray tubes (CRTs), plasma displays, light-emitting diode (LED) displays, liquid crystal displays (LCDs), printers, vacuum fluorescent displays (VFDs), surface-conducting electron emission displays (SEDs), field emission displays (FEDs), head-mounted displays (HMDs), etc. In some cases, the input and output devices 340 may be integrated, such as in the case of touch panel displays (e.g., touch panel displays in smartphones, tablets, or other mobile devices).

[0052] In one embodiment, the input / output device 340 may be any type of external or integrated display, and may include one or more discrete displays collectively constituting the input / output device 340. The input / output device 340 is capable of presenting two-dimensional or three-dimensional visual information to the user of the system 300. In one embodiment, the input / output device 340 may be a virtual reality or augmented reality device in the form of a head-mounted display, so that the user can visualize the three-dimensional presentation of information.

[0053] System 300 may also include optional wireless communication components to facilitate wireless communication over voice and / or data networks (e.g., in the case of user system 230). The wireless communication components include an antenna system 375, a radio frequency (RF) system 370, and a baseband system 365. In system 300, radio frequency (RF) signals are transmitted and received over the air by the antenna system 375 under the management of the RF system 370.

[0054] In one embodiment, antenna system 375 may include one or more antennas and one or more multiplexers (not shown) that perform switching functions to provide transmit and receive signal paths to antenna system 375. In the receive path, received radio frequency signals may be coupled from the multiplexer to a low-noise amplifier (not shown), which amplifies the received radio frequency signals and transmits the amplified signals to radio frequency system 370.

[0055] In an alternative embodiment, the radio frequency system 370 may include one or more radio frequency devices configured to communicate at multiple frequencies. For example, the radio frequency system 370 may be configured to communicate with a local device (not shown), a local base station (not shown), and / or a satellite (not shown), with communication with each such device employing different frequencies and / or different radio frequency devices. In one embodiment, the radio frequency system 370 may integrate a demodulator (not shown) and a modulator (not shown) in a single integrated circuit (IC). The demodulator and modulator may also be discrete components. In the input path, the demodulator strips the radio frequency carrier signal to obtain a baseband received audio signal, which is transmitted from the radio frequency system 370 to the baseband system 365.

[0056] If the received signal contains audio information, the baseband system 365 decodes the signal and converts it into an analog signal, then amplifies the signal and sends it to a speaker. The baseband system 365 also receives analog audio signals from a microphone. These analog audio signals are converted into digital signals and encoded by the baseband system 365. The baseband system 365 further encodes the digital signals for transmission and generates a baseband transmit audio signal, which is routed to the modulator section of the radio frequency system 370. The modulator mixes the baseband transmit audio signal with the radio frequency carrier signal to generate a radio frequency transmit signal, which is routed to the antenna system 375 and may pass through a power amplifier (not shown). The power amplifier amplifies the radio frequency transmit signal and routes it to the antenna system 375, where the signal is switched to the antenna port for transmission.

[0057] The baseband system 365 is also communicatively coupled to a processor 310, which may be a central processing unit (CPU). The processor 310 has access to data storage areas 315 and 320. The processor 310 is preferably configured to execute instructions (i.e., computer programs, such as disclosed application programs or software modules) that can be stored in main memory 315 or secondary memory 320. The computer program may also be received from the baseband processor 360 and stored in main memory 310 or secondary memory 320, or executed upon receipt. When executed, such a computer program causes the system 300 to perform various functions of the disclosed embodiments.

[0058] 1.3 Exemplary Workflow

[0059] return Figure 2 In infrastructure 200, the system is configured to enable application 232 to establish a spherical radius perimeter. User system 230 includes a wireless receiver configured to receive signals from UA 244. User system 230 processes the signals from UA 244 to determine the distance between UA 244 and user system 230; if the distance is equal to or less than the established spherical radius, application 232 is configured to initiate the sending of a message to UA 244.

[0060] In one aspect, to initiate message transmission, application 232 may send a message to platform 210. The message sent to platform 210 contains a unique identifier for UA 244 obtained by application 232 from a signal received from UA 244. Accordingly, platform 244 may query its local database 214 to obtain relevant information about UAS 240, including contact information for the operator of UAS 240. Alternatively, platform 244 may request relevant information about UAS 240, including contact information for the operator of UAS 240, from external system 250. In one aspect, external system 250 may be a server maintained by the FAA and configured to provide information corresponding to each uniquely identified UA, such as UA 244. After platform 210 obtains the contact information for the operator of UA 244, application 212 is configured to send a message to the operator of UA 244, such as a message indicating that UA 244 is too close to a person, object, facility, or other object corresponding to user system 230.

[0061] Figure 4 This is a block diagram illustrating an exemplary spherical perimeter 400 according to one embodiment of the present invention. In alternative embodiments, the perimeter 400 may have a non-spherical alternative shape. For example, the perimeter 400 may be defined by a polygonal (or other shaped) geofence surrounding the user system 410, extending upwards from the ground to a predetermined height above the ground. For simplicity, the perimeter 400 is described herein as spherical, but the perimeter may also take any regular or irregular shape to define the area surrounding the user system 410.

[0062] In the illustrated embodiment, user system 410 (e.g., a wireless communication device associated with person 405) is located at the center point defining the perimeter 400 of the spherical radius. In one aspect, user system 410 is used to determine the center point of the perimeter 400 of the spherical radius.

[0063] As shown in the illustrated embodiment, the radius 420 of the spherical perimeter 400 is 50 feet. The radius 420 of the spherical perimeter 400 may also be other distances. In one aspect, the operator of the user system 410 may select the radius 420 to set the distance. Advantageously, the user system 410 is configured to receive signals from drones 450 and 460, and process the signals to determine the distance between the user system 410 and drone 450, and the distance between the user system 410 and drone 460.

[0064] If the distance between user system 410 and drone 450 exceeds the radius of the spherical perimeter, user system 410 is configured to take no action. If the distance between user system 410 and drone 460 is less than the radius of the spherical perimeter, user system 410 is configured to take action. For example, user system 410 may be configured to analyze signals to identify the drone, use the drone's identifier to determine the drone operator's contact information, and use that contact information to send a message to the drone operator. In one aspect, the message sent to the operator is a warning message, indicating that the drone is too close to a person and needs to move away.

[0065] Figure 5 This is a block diagram illustrating another exemplary spherical radius perimeter 500 according to one embodiment of the present invention. In alternative embodiments, perimeter 500 may have a non-spherical alternative shape. For example, perimeter 500 may be defined by a polygonal (or other shaped) geofence surrounding user system 510, extending upwards from the ground to a predetermined height above the ground. For simplicity, perimeter 500 is described herein as spherical, but the perimeter may also take any regular or irregular shape to define the area surrounding user system 510.

[0066] In the illustrated embodiment, user system 510 (e.g., a wireless communication device associated with a member of a group 505) is located at the center point defining the perimeter 500 of the spherical radius. In one aspect, user system 510 is used to determine the center point of the perimeter 500 of the spherical radius.

[0067] As shown in the embodiment, the radius 520 of the spherical perimeter 500 is 100 feet. The radius 520 of the spherical perimeter 500 can also be other distances. In one aspect, the radius 520 can be selected and set by the operator of the user system 510 to set the distance of the radius 520. For example, depending on the size of the crowd, to maintain a distance of at least 50 feet from any person in the crowd, the radius 500 of the spherical perimeter 500 can be set to 100 feet or 150 feet.

[0068] Advantageously, user system 510 is configured to receive signals from UAV 550 and UAV 560, and process these signals to determine the distance between user system 510 and UAV 550, and the distance between user system 510 and UAV 560. If the distance between user system 510 and UAV 550 exceeds the radius of the spherical perimeter, user system 510 is configured to take no action.

[0069] Alternatively, when the distance between user system 510 and UAV 560 is less than the radius of the spherical perimeter, user system 510 is configured to take action. For example, user system 510 may be configured to analyze signals to identify the UA, determine the UA's operator's contact information using the UA's identifier, and send a message to the UA's operator using that contact information. In one aspect, the message sent to the operator is a warning message, indicating that the UA is too close to the crowd 560 and needs to move away.

[0070] Figure 6 This is a block diagram illustrating an exemplary unmanned aerial vehicle (UAS) system 600 according to an embodiment of the present invention. In the illustrated embodiment, the UAS 600 includes a UA 610 and a controller 620, the controller 620 being configured to wirelessly communicate with the UA 610 via a wireless communication link 630. In one aspect, the controller 620 communicates with the UA 610 via separate video and control channels, for example, the video communication channel may employ a 5 GHz bandwidth and the control channel may employ a 2.4 GHz bandwidth.

[0071] Operator 640 interacts with controller 620 and sends commands to UA 610. Operator 640 may also use user system 650, which is configured to communicate with controller 620 via wired or wireless communication link 660.

[0072] Individually, user 670 is equipped with a corresponding user system 680, which is configured to receive wireless communication signals from UA 610 via wireless communication link 690. In one aspect, user system 680 can also be configured to transmit wireless communication signals to the drone via wireless communication link 690. User system 680 is configured to process the wireless communication signals received from UA 610 to determine the distance between UA 610 and user system 680. User system 680 is also configured to determine whether the distance between UA 610 and user system 680 exceeds a predetermined threshold, such as 50 feet or 100 feet.

[0073] In one aspect, the wireless receiver of user system 680 receives signals from UA 610. User system 680 runs an application that processes the signals from UA 610 to determine an estimated distance between user system 680 and UA 610. Since UA 610 is in flight, possibly hovering or moving, the application can be configured to analyze multiple signals from UA 610 to estimate the average distance between user system 680 and UA 610. The application can also be configured to determine the closest distance between user system 680 and UA 610 and a greater distance between them, for example, within a specific time period (during which the closest distance exceeds a threshold), which could be 5 minutes before and after the moment the distance exceeds the threshold.

[0074] If user system 680 determines that the distance between UA 610 and user system 680 exceeds a threshold (e.g., the radius of a sphere around user system 680), user system 680 is configured to initiate a notification to UA 610, operator 640 controlling UA 610, or user system 650 of the operator. User system 650 can then transmit the message to UA 610 via controller 620. In one aspect, user system 680 executes an application to initiate a notification to UA 610. For example, the application can send a message to server 697 via wireless communication link 694 and network 695. This message advantageously contains an identifier that uniquely identifies UA 610. In one aspect, the unique identifier of UA 610 can be parsed by user system 680 from wireless signals received from UA 610. Advantageously, user system 680 sends a message to server 697, which retrieves the contact information of the operator of UA 610. For example, server 697 may have a local database of multiple UAS containing the contact information of the operators of the UA. Alternatively, server 697 may contact other servers (not shown) to obtain the contact information of the operator of UA 610. Once the contact information of the operator of UA 610 is obtained by server 697, server 697 is configured to send a message to the user system 650 of the operator of UA 610. The message from server 697 can be sent via wireless communication link 692 between network 695 and user system 650. In one aspect, the message sent by server 697 to the user system 650 of the operator of UA 610 may indicate to the operator of UA 610 that UA 610 is too close to user 670 (or other person, facility, or object).

[0075] Figure 7 This is a block diagram illustrating an exemplary unmanned aerial vehicle (UAV) system 700 according to an embodiment of the present invention. System 700 is similar to the previously referenced... Figure 6 The system 600 described will therefore be referred to Figure 7 Description only Figure 7 Those aspects that differ from those described previously.

[0076] More specifically, if user system 780 determines that the distance between UA 710 and user system 780 exceeds a threshold (e.g., corresponding to the radius of a sphere around user system 780), user system 780 is configured to initiate sending a notification to UA 710. In one aspect, user system 780 executes an application that initiates sending a notification to UA 710. The notification sent to UA 710 can be sent directly or indirectly.

[0077] For example, the application can send messages directly to UA 710 via communication link 790. Alternatively, the application can send messages indirectly to UA 710 via satellite 795, with user system 780 communicating with satellite 795 via communication link 794. Satellite 795 then communicates directly with UA 710 via communication link 796. Satellite 795 can also communicate directly with controller 720 via communication link 798, and controller 720 then communicates directly with UA 710 via communication link 730. Satellite 795 can also communicate directly with user system 750 (such as operator 740's user system) via communication link 792, user system 750 communicates directly with controller 720 via communication link 760, and controller 720 then communicates directly with UA 710 via communication link 730. Satellite 795 can also communicate directly with user system 750 (such as operator 740's user system) via communication link 792. User system 750 sends messages to operator 740 through user interface. Operator 740 inputs instructions to controller 720. Controller 720 communicates directly with UA 710 via communication link 730.

[0078] Figure 8 This is a flowchart illustrating an exemplary process flow 800 for establishing a perimeter according to an embodiment of the present invention. In one aspect, Figure 8 The processing flow shown can be generated by Figure 2 , Figure 6 or Figure 7 The system combination Figure 3 The one or more processing devices may execute, for example, processing flow 800 may be executed by application 232 running on user system 230.

[0079] First, in step 810, the user system presents a user interface to the user. The user interface may include text input fields, speech-to-text input functionality, or other user interface fields or functions that facilitate receiving user input. In step 815, the user system receives user input; in step 820, the user system calculates the perimeter of the area surrounding the user system based on the user input. In one aspect, the user may input a radius value, and the user system calculates a sphere centered on the user system's location. For example, the user may input the value 50, and the user system can calculate a sphere with a radius of 50 feet (or 50 meters) and, using the latitude and longitude values ​​of the user system's current location, determine a sphere 50 feet around the user system. In another aspect, by assuming the user system is located on a plane and that the UA occupies only a hemispherical space around the user system, with the other hemisphere below the ground, the user system can approximate the sphere.

[0080] On the other hand, users can input a street address and a height value of 200 feet. The user system calculates the perimeter of a polygon based on the distance of the height value and the plot boundary associated with that street address. This polygon extends 200 feet (or 200 meters) into the air.

[0081] Furthermore, in step 825, the user system optionally initiates the transmission of a beacon signal containing an identifier of the perimeter of the area surrounding the user system. In one aspect, the area surrounding the user system can be identified by determining a center point and the radius of a definable spherical area using latitude and longitude coordinates or Global Positioning System (GPS) coordinates. In another aspect, the area surrounding the user system can be identified by providing a geofenced area on the ground (e.g., using latitude and longitude coordinates or GPS coordinates) along with an altitude value that defines a regular or irregular area surrounding the user system. This allows the UA to determine, under certain circumstances, whether it is within that area. It also allows the UA to avoid flying into the area identified by the user system under certain circumstances. Advantageously, the user system can optionally be configured to periodically broadcast the beacon signal as shown in step 830, enabling any UA within range of receiving the beacon signal to leave the sphere surrounding the user system or avoid flying into the sphere surrounding the user system.

[0082] Figure 9 This is a flowchart illustrating an exemplary processing flow 900 for monitoring User Agents according to an embodiment of the present invention. In one aspect, Figure 9 The processing flow shown can be generated by Figure 2 , Figure 6 or Figure 7 The system combination Figure 3 The one or more processing devices may execute, for example, processing flow 900 may be executed by application 232 running on user system 230.

[0083] First, in step 910, the user system receives a beacon signal broadcast by the UV. The beacon signal may include certain information about the UV, such as a unique identifier for the UV. The beacon signal may also include other information, such as location information corresponding to the UV. Next, in step 915, the user system processes the beacon signal and calculates the distance between the UA and the user system. In one aspect, the user system may process multiple beacon signals to calculate the distance between the UA and the user system. Alternatively, the user system may obtain the UA's location information from the beacon signal and use this information in conjunction with the user system's location information to calculate the distance between the UA and the user system.

[0084] In step 920, the user system analyzes the distance between itself and the UA to determine if the distance exceeds a threshold. For example, the user system may have already established a perimeter sphere based on the radius of the center point defined by the user system's location. If the UA is wholly or partially within the perimeter sphere, the user system can determine that the UA has exceeded the threshold. If the user system determines in step 920 that the UA has not exceeded the threshold distance, the processing flow returns to a loop, and the user system receives subsequent beacon signals from the UV.

[0085] However, if the user system determines in step 920 that the UA exceeds the threshold, in step 925, the user system parses the beacon signal to identify the UV. Subsequently, the user system initiates the transmission of a proximity warning message to the UV. In one aspect, the user system may optionally initiate the transmission of a proximity warning message directly to the UV via direct wireless communication or other means in step 930. Alternatively, the user system may optionally initiate the transmission of a proximity warning message indirectly to the UV in step 935, for example, by sending communication to a server or satellite, which then transmits the proximity warning message to the UV.

[0086] Figure 10 This is a flowchart illustrating an exemplary processing flow 1000 for communicating with an operator of a User Agent (UA) according to an embodiment of the present invention. In one aspect, Figure 10 The processing flow shown can be generated by Figure 2 , Figure 6 or Figure 7 The system combination Figure 3 The one or more processing devices may perform the process, for example, process flow 1000 may be performed by application 232 running on user system 230 and application 212 running on platform 210.

[0087] First, in step 1010, the user system receives a beacon signal broadcast by the UV. The beacon signal may contain some information about the UV, such as its unique identifier. The beacon signal may also contain other information, such as location information corresponding to the UV. Next, in step 1015, the user system processes the beacon signal to calculate the distance between the UA and the user system. In one aspect, the user system may process multiple beacon signals to calculate the distance between the UA and the user system. Alternatively, the user system may obtain the UA's location information from the beacon signal and use this information in conjunction with location information about the user system to calculate the distance between the UA and the user system.

[0088] In step 1020, the user system analyzes the distance between the UA and the user system to determine whether the distance exceeds a threshold. For example, the user system can establish a spherical perimeter based on the radius value of the center point defined by the user system's location. If the UA is wholly or partially within the spherical perimeter, the user system can determine that the UA exceeds the threshold. If the user system determines in step 1020 that the UA does not exceed the threshold distance, the processing flow returns to a loop, and the user system receives subsequent beacon signals from the UV.

[0089] However, if the user system determines in step 1020 that the UA exceeds the threshold, in step 1025, the user system parses the beacon signal to identify the UV. Subsequently, the user system initiates the sending of a proximity warning message to the operator of the UV. In one aspect, the user system may optionally initiate the sending of a proximity warning message to the operator of the UA via a server in step 1030. The server is communicatively coupled to the user system via one or more networks, and simultaneously communicatively coupled to the operator's user system via one or more networks. For example, the one or more networks used by the server may include the Internet and involve one or more public or private networks. Alternatively, the user system may optionally initiate the sending of a proximity warning message to the operator of the UA via a satellite in step 1035. The satellite is communicatively coupled to the user system directly or via one or more networks, and simultaneously communicatively coupled to the operator's user system directly or via one or more networks. In one aspect, the one or more networks used by the satellite may include the Internet and involve one or more public or private networks.

[0090] Figure 11 This is a flowchart illustrating an exemplary processing flow 1100 for direct communication with a UA, according to an embodiment of the present invention. In one aspect, Figure 11 The processing flow can be provided by Figure 2 , Figure 6 or Figure 7 The system combination Figure 3 The one or more processing devices may perform, for example, processing flow 1100 may be performed at least in part by application 232 running on user system 230.

[0091] First, in step 1110, the user system receives the beacon signal broadcast by the UV. The beacon signal may contain certain information about the UV, such as its unique identifier. It may also include other information, such as location information corresponding to the UV. In one aspect, the beacon signal broadcast periodically by the UA (e.g., 10 times per second or 10 times per minute) may also contain contact information for the UA and / or its operator. In another aspect, the UA's contact information may include an identifier of a wireless communication channel used to send messages directly to the UA. Advantageously, any user system receiving the beacon signal broadcast by the UA can use an application (such as application 232) to parse the beacon signal and determine the direct wireless communication channel with the UA.

[0092] Next, in step 1115, the user system processes the beacon signals and calculates the distance between the UA and the user system. In one aspect, the user system may process multiple beacon signals to calculate the distance between the UA and the user system. Alternatively, the user system may obtain the UA's location information from the beacon signals and use this information, combined with the user system's location information, to calculate the distance to the UA.

[0093] In step 1120, the user system analyzes the distance between the UA and the user system to determine if the distance exceeds a threshold. For example, the user system may have established a spherical perimeter based on the radius of a center point defined by the user system's location. If the UA is wholly or partially within the spherical perimeter, the user system can determine that the UA exceeds the threshold. If the user system determines in step 1120 that the UA does not exceed the threshold distance, the processing flow returns to a loop, and the user system receives subsequent beacon signals from the UV.

[0094] However, if the user system determines in step 1120 that the UA exceeds the threshold, in step 1125, the user system parses the beacon signal, identifies the UA, and identifies a direct wireless communication channel that can be used to send messages directly to the UA. Subsequently, in step 1130, the user system initiates the direct transmission of a proximity warning message to the UA using the wireless communication channel. In several aspects, the direct wireless communication channel can be implemented using Bluetooth®, WiFi Direct®, Bluetooth Low Energy, Zigbee, Z-Wave, NFC, conventional WiFi, and a variety of other short-range wireless communication technologies. After the direct wireless communication proximity warning message has been sent to the UA, in step 1135, the UA may optionally notify its operator that the proximity warning message has been received, and the UA may also optionally drive away. In one aspect, the UA maintains a "no-fly zone" map in its memory, and the UA may update its "no-fly zone" map and drive away, or the UA may simply drive away until no further proximity warning messages are received within a predetermined time.

[0095] Figure 12 This is a flowchart illustrating an exemplary processing flow 1200 for direct communication with a User Agent (UA) according to an embodiment of the present invention. In one aspect, Figure 12 The processing flow can be provided by Figure 2 , Figure 6 or Figure 7 The system combination Figure 3 The one or more processing devices may execute, for example, processing flow 1200 may be executed by application 232 running on user system 230.

[0096] First, in step 1210, the user system receives a beacon signal broadcast by the UV. The beacon signal may contain certain information about the UV, such as its unique identifier. It may also include other information, such as location information corresponding to the UV. In one aspect, the beacon signal broadcast periodically by the UA (e.g., 10 times per second or 10 times per minute) may also contain contact information for the UA and / or its operators. In one aspect, the UA's contact information may include an identifier of a wireless communication channel used to send messages directly to the UA. In another aspect, the UA's contact information may include an identifier of a satellite communication channel that the UA is monitoring to receive air traffic control information and other messages and information. Advantageously, any user system receiving the beacon signal broadcast by the UA can use an application (such as application 232) to parse the beacon signal and determine the satellite communication channel that the UA is monitoring.

[0097] Next, in step 1215, the user system processes the beacon signals and calculates the distance between the UA and the user system. In one aspect, the user system may process multiple beacon signals to calculate the distance between the UA and the user system. Alternatively, the user system may obtain location information about the UA from the beacon signals and use this information, combined with location information about the user system, to calculate the distance between the UA and the user system.

[0098] In step 1220, the user system analyzes the distance between the UA and the user system to determine if the distance exceeds a threshold. For example, the user system may have established a spherical perimeter based on the radius value of the center point defined by the user system's location. If the UA is wholly or partially within the spherical perimeter, the user system can determine that the UA exceeds the threshold. If the user system determines in step 1220 that the UA does not exceed the threshold distance, the processing flow returns to a loop, and the user system receives subsequent beacon signals from the UV.

[0099] However, if the user system determines in step 1220 that the UA exceeds the threshold, in step 1225, the user system parses the beacon signal, identifies the UA, and identifies the satellite communication channel that the UA is listening on. Subsequently, in step 1230, the user system initiates the transmission of a proximity warning message to the UA via the satellite communication channel. In one aspect, the user system is directly coupled to satellite communication, or indirectly coupled through one or more networks, which may include the Internet and involve one or more public or private networks. The user system sends a message to the satellite containing the UA's unique identifier, the satellite communication channel that the UA is listening on, and the location information of the user system where the UA is approaching at close range.

[0100] Next, in step 1235, the satellite broadcasts a proximity warning message to the geographic area surrounding the user system's location. The proximity warning message is broadcast on the same satellite communication channel that the UA is listening on and contains the UA's unique identifier. Upon receiving the proximity warning message via the satellite communication channel, the UA identifies its own unique identifier and determines that the message is targeted at that UA.

[0101] After receiving an approach warning message from a satellite, in step 1240, the UA may optionally notify its operator that it has received the approach warning message, and the UA may also optionally leave the area. In one aspect, the UA maintains a "no-fly zone" map in its memory, and the UA may update its "no-fly zone" map and leave the area, or the UA may simply leave the area until no further approach warning messages are received within a predetermined time.

[0102] Figure 13 This is a flowchart illustrating an exemplary processing flow 1300 for reporting flight data corresponding to the User Agent (UA) according to an embodiment of the present invention. In one aspect, Figure 13 The processing flow can be provided by Figure 2 , Figure 6 or Figure 7 The system combination Figure 3 The one or more processing devices may perform, for example, processing flow 1300 may be performed by application 232 running on user system 230 and application 212 running on platform 210.

[0103] First, in step 1310, the platform receives notification that a proximity warning message has been sent to the UA, and the platform generates and stores a report of the proximity warning message in its memory. The proximity warning message can be sent directly or indirectly to the UA, for example, via direct wireless communication, satellite, web server, etc. The proximity warning message can also be sent to the UA by its operator. Advantageously, in all cases where a proximity warning message is sent to the UA, the platform receives a report that the proximity warning message has been sent to the UA and stores a record of the proximity warning report in its memory. The proximity warning report stored in the memory includes the UA's unique identifier, as well as information such as the date and time the proximity warning message was generated and sent to the UA, the user system that initiated the report, the location of the user system that initiated the report, the method by which the proximity warning message was sent to the UA, whether the proximity warning message was sent to the UA's operator or the UA's operator's user system, and other relevant information regarding the generation and transmission of the proximity warning message.

[0104] After storing a proximity warning report in its memory, in step 1315, the platform identifies the User Agent (UA) involved in the proximity warning report; in step 1320, the platform retrieves all proximity warning reports involving the same UA within a specific time period from its memory. For example, the time period can be 30 minutes, 6 hours, 12 hours, 18 hours, 24 hours, 48 ​​hours, 7 days, 14 days, 21 days, 30 days, or other time periods. After identifying all proximity warning reports involving the same UA within that time period, the total number of reports within that time period is determined. In one aspect, the platform can determine the total number of reports for each of multiple time periods.

[0105] Next, in step 1325, the platform compares the total number of reports within a specific time period with a predetermined threshold for that time period. For example, the threshold for 30 minutes could be 3 reports, the threshold for 6 hours could be 10 reports, and the threshold for 30 days could be 30 reports. If the total number of reports within that time period exceeds the predetermined threshold, in step 1330, the platform generates a report identifying the UA and sends the report to the UA's flight management authority. In one aspect, the report may contain all known flight data for the UA. For example, the report sent to the UA's flight management authority may contain all detailed information stored in each proximity warning report stored in the platform's memory. In another aspect, the report sent to the UA's flight management authority is a composite file of all proximity warning reports for the UA stored in the platform's memory.

[0106] The foregoing description of the disclosed embodiments is intended to enable any person skilled in the art to make or use the invention. Various modifications will be readily apparent to those skilled in the art to these embodiments, and the general principles herein can be applied to other embodiments without departing from the spirit or scope of the invention. Therefore, it should be understood that the specification and drawings herein represent currently preferred embodiments of the invention and thus represent a broad scope of the invention. It should also be understood that the scope of protection of the invention fully encompasses other embodiments readily conceived by those skilled in the art, and therefore the scope of protection of the invention is not limited.

Claims

1. A method in which one or more processors are programmed to perform the following steps: Receive wireless communication signals from the unmanned aerial vehicle (UA); Parse the wireless communication signal to obtain the identifier corresponding to the UA; The operator of the UA is identified using the identifier; Obtain the contact information of the operator of the UA; as well as Send a message to the operator of the UA.

2. The method of claim 1, wherein the message is sent directly to the operator of the UA.

3. The method of claim 1, wherein the message is indirectly sent to the operator of the UA.

4. The method of claim 3, wherein the message is sent indirectly to the operator of the UA via a server.

5. The method of claim 3, wherein the message is indirectly transmitted to the operator of the UA via satellite.

6. The method of claim 1, wherein the one or more processors are further programmed to perform the following steps: Calculate the distance to the UA based on the received wireless signal; Determine whether the calculated distance exceeds a predetermined threshold; and When the calculated distance exceeds the predetermined threshold, a proximity warning message is sent to the operator of the UA.

7. The method of claim 6, wherein the proximity warning message is sent directly to the operator of the UA.

8. The method of claim 6, wherein the proximity warning message is indirectly sent to the operator of the UA.

9. The method of claim 8, wherein the message is sent indirectly to the operator of the UA via a server.

10. The method of claim 8, wherein the message is indirectly transmitted to the operator of the UA via satellite.

11. A system comprising at least one processor, said at least one processor being communicatively coupled to at least one non-transitory computer-readable medium, wherein said at least one processor is programmed to: Receive wireless communication signals from the unmanned aerial vehicle (UA); Parse the wireless communication signal to obtain the identifier corresponding to the UA; The operator of the UA is identified using the identifier; Obtain the contact information of the operator of the UA; as well as Send a message to the operator of the UA.

12. The system of claim 11, wherein the message is sent directly to the operator of the UA.

13. The system of claim 11, wherein the message is indirectly sent to the operator of the UA.

14. The system of claim 13, wherein the message is sent indirectly to the operator of the UA via a server.

15. The system of claim 13, wherein the message is transmitted indirectly to the operator of the UA via satellite.

16. The system of claim 11, wherein the at least one processor is further programmed to perform the following steps: Calculate the distance to the UA based on the received wireless signal; Determine whether the calculated distance exceeds a predetermined threshold; and When the calculated distance exceeds the predetermined threshold, a proximity warning message is sent to the operator of the UA.

17. The system of claim 16, wherein the proximity warning message is sent directly to the operator of the UA.

18. The system of claim 16, wherein the proximity warning message is indirectly sent to the operator of the UA.

19. The system of claim 18, wherein the message is sent indirectly to the operator of the UA via a server.

20. The system of claim 18, wherein the message is transmitted indirectly to the operator of the UA via satellite.

21. A non-transitory computer-readable medium having stored thereon one or more instruction sequences, the instruction sequences being configured to cause one or more processors to perform the following steps: Receive wireless communication signals from the unmanned aerial vehicle (UA); Parse the wireless communication signal to obtain the identifier corresponding to the UA; The operator of the UA is identified using the identifier; Obtain the contact information of the operator of the UA; as well as Send a message to the operator of the UA.

22. The medium of claim 1, wherein the message is sent directly to the operator of the UA.

23. The medium of claim 1, wherein the message is indirectly sent to the operator of the UA.

24. The medium of claim 3, wherein the message is sent indirectly to the operator of the UA via a server.

25. The medium of claim 3, wherein the message is transmitted indirectly to the operator of the UA via satellite.

26. The medium according to claim 1, wherein the one or more processors further perform the following steps: Calculate the distance to the UA based on the received wireless signal; Determine whether the calculated distance exceeds a predetermined threshold; and When the calculated distance exceeds the predetermined threshold, a proximity warning message is sent to the operator of the UA.

27. The medium of claim 6, wherein the proximity warning message is sent directly to the operator of the UA.

28. The medium of claim 6, wherein the proximity warning message is indirectly sent to the operator of the UA.

29. The medium of claim 8, wherein the message is sent indirectly to the operator of the UA via a server.

30. The medium of claim 8, wherein the message is transmitted indirectly to the operator of the UA via satellite.

31. A method in which one or more processors are programmed to perform the following steps: Receive wireless communication signals from the unmanned aerial vehicle (UA); The distance to the UA is calculated based on the received wireless communication signal; It is determined that the calculated distance exceeds a predetermined threshold; Analyze the wireless communication signal to identify the wireless communication channel corresponding to the UA; as well as A proximity warning message is sent to the UA via the wireless communication channel.

32. The method of claim 31, wherein the UA forwards the proximity warning message to the operator of the UA.

33. The method of claim 31, wherein the proximity warning message is sent directly to the UA.

34. The method of claim 31, wherein the proximity warning message is sent indirectly to the UA.

35. The method of claim 34, wherein the proximity warning message is sent indirectly to the UA via a server.

36. The method of claim 34, wherein the proximity warning message is indirectly transmitted to the UA via satellite.

37. The method of claim 36, wherein the satellite broadcasts the proximity warning message to the UA.

38. A method in which one or more processors are programmed to perform the following steps: Present the user interface on the user's device; Input is received through the user interface, and the input corresponds to a distance. Calculate the perimeter of the area surrounding the user equipment based on the input; as well as The wireless communication signal that identifies the perimeter of the area is broadcast periodically.

39. The method of claim 38, wherein the region is substantially spherical.

40. The method of claim 38, wherein the region is substantially polygonal.

41. The method of claim 38, wherein the region has a bottom surface including the Earth's surface and extends upward from the bottom surface.

42. A method in which one or more processors are programmed to perform the following steps: Receive notification of proximity warning messages sent to the first User Agent; The notification of the proximity warning message is stored in association with the first UA; Identify all proximity warning notifications associated with the first UA within the first time period; The number of proximity warnings associated with the first UA during the first time period exceeds a first threshold. Acquire the flight data of the first UA corresponding to each proximity warning associated with the first UA within the first time period; as well as A report is generated, which includes each proximity warning associated with the first UA during the first time period, and the flight data of the first UA corresponding to each proximity warning associated with the first UA during the first time period.

43. The method of claim 42, wherein the one or more processors are further programmed to send the report to the competent authority.

44. A system comprising: User equipment includes: A wireless receiver is configured to receive wireless communication signals from a drone (UA) near the user equipment; A non-transitory computer-readable medium configured to store an executable programmable module; A processor, communicatively coupled to the wireless receiver and the non-transitory computer-readable medium, is configured to execute one or more programming modules stored in the non-transitory computer-readable medium to process signals received by the wireless receiver from the UA and identify the UA; and Server equipment, including: A non-transitory computer-readable medium configured to store an executable programmable module; and A processor, communicatively coupled to the non-transitory computer-readable medium, is configured to execute one or more programming modules stored in the non-transitory computer-readable medium to process signals received from the user equipment, identify an operator corresponding to the UA, and send messages to the operator of the UA.

45. A user equipment, comprising: A wireless receiver is configured to receive wireless communication signals from a drone (UA) near the user equipment; A non-transitory computer-readable medium configured to store an executable programmable module; as well as A processor, communicatively coupled to the wireless receiver and the non-transitory computer-readable medium, is configured to execute one or more programming modules stored in the non-transitory computer-readable medium to: The wireless receiver receives signals from the UA to identify the UA; Identify the operator corresponding to the UA; And send a message to the operator of the UA.

Images