Fully autonomous drone flight control

By introducing pre-programmed flight plan and facial recognition modules into autonomous drone systems, the problem of autonomous drone safety control in electromagnetic interference and multi-drone coexistence environment is solved, and the efficiency of drones in complex environments is achieved Self-flight and safe landing.

CN119096212APending Publication Date: 2024-12-06SNAP INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380036074.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-11-07
Filing Date
2023-04-05
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Existing autonomous drones have challenges in safety and control, especially in the case of electromagnetic interference environments or the coexistence of multiple drones, making it difficult to achieve efficient remote control and safe flight.

Method used

A fully autonomous drone system was designed. Through pre-programmed flight plan and facial recognition module, autonomous drone can fly after initial facial recognition and descend on the user's hand, using navigation system and sensor data to achieve autonomous navigation. and land to avoid interference from external electronic control.

Benefits of technology

It realizes autonomous flight and landing without external electronic control, improves the safety and operation efficiency of drones, and is suitable for scenarios where multiple drones coexist in complex environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096212A_ABST
    Figure CN119096212A_ABST
Patent Text Reader

Abstract

Apparatuses, methods, and computer readable media for fully autonomous drone flight are disclosed. An example method includes takeoff, navigating according to a flight plan, and navigating the drone to land. The autonomous drone performs a flight plan based on an initial flight command for flight of the autonomous drone, and in some examples, based on an indication of a landing space, such as an open hand, presented beneath the autonomous drone. After receiving the initial flight command, the autonomous drone is not controlled by the remote control device. Since the autonomous drone does not respond to the command during flight, the autonomous drone enters a lower energy state while flying with the wireless connection off.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Priority Claim

[0002] This application claims the benefit of priority to U.S. Provisional Application Serial No. 63 / 335,429 filed on April 27, 2022 and U.S. Patent Application Serial No. 17 / 981,807 filed on November 7, 2022, each of which is incorporated herein by reference in its entirety. Technical Field

[0003] Examples of the present disclosure generally relate to fully autonomous drone flight. More particularly, but not by way of limitation, the present disclosure provides systems and methods for fully autonomous drone flight, wherein the autonomous drone receives only an initial flight command and an indication of an object or hand to land on at the end of a flight plan and flies according to the flight plan. Background Art

[0004] Autonomous drones that provide photography services to users are becoming increasingly popular. But autonomous drone designs are limited by size and power constraints. And users of autonomous drones continue to demand more and more services from autonomous drones. Furthermore, autonomous drones need to be safe to use. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In the drawings, which are not necessarily drawn to scale, similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

[0006] Figure 1 is a diagrammatic representation of a networked environment in which the present disclosure may be deployed, according to some examples.

[0007] Figure 2 is a diagrammatic representation of a messaging system having both client-side and server-side functionality according to some examples.

[0008] Figure 3 is a diagrammatic representation of data structures as maintained in a database according to some examples.

[0009] Figure 4 is a graphical representation of messages according to some examples.

[0010] Figure 5 is a flow chart of an access restriction process according to some examples.

[0011] Figure 6 Examples of components for an autonomous drone are shown according to some examples.

[0012] Figure 7 is a schematic diagram illustrating an autonomous drone system according to some examples.

[0013] Figure 8 An autonomous drone is shown according to some examples.

[0014] Fig. 9 A system 900 for fully autonomous drone flight is shown according to some examples.

[0015] Fig.10 State 1000 of an autonomous drone is shown according to some embodiments.

[0016] Fig.11 An autonomous drone is shown unlocking 1100 according to some embodiments.

[0017] Fig.12 An autonomous drone 710 is shown flying according to some embodiments.

[0018] Fig.13 Autonomous drone landing 1300 is shown according to some embodiments.

[0019] Fig.14 A method 1400 for fully autonomous drone flight according to some examples is shown.

[0020] Fig.15 is a diagrammatic representation of a machine in the form of a computer system according to some examples within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein.

[0021] Fig.16 is a block diagram illustrating a software architecture in which examples may be implemented.

[0022] Fig.17 is a diagrammatic representation of a processing environment according to some examples. DETAILED DESCRIPTION

[0023] The following description includes systems, methods, techniques, instruction sequences and computer program products for implementing the illustrative examples of the present disclosure. In the following description, for the purpose of illustration, many specific details are set forth to provide an understanding of the various examples of the subject matter of the present invention. However, it will be apparent to those skilled in the art that the examples of the subject matter of the present invention can be put into practice without these specific details. Typically, known instruction instances, protocols, structures and techniques are not necessarily shown in detail.

[0024] Systems, computer readable media, and methods for fully autonomous drone flight are disclosed. Remote control devices are often difficult to use and often take too long to use to safely control a drone. Additionally, sending commands to an autonomous drone may be difficult in some environments. For example, there may be electromagnetic interference or many other autonomous drones using similar wavelengths.

[0025] The autonomous drone 710 performs a fully autonomous flight according to a predetermined pre-programmed flight plan 960. The person controls the autonomous drone 710 by using the user interface controls of the autonomous drone 710 to instruct the autonomous drone 710 to execute the fully autonomous pre-programmed flight plan 960. For example, the person can select a setting for the control knob 614 of the autonomous drone 710 that selects a pre-programmed flight plan 960, such as flying around the person and taking a video. The person then selects the fly button 806, which instructs the autonomous drone 710 to execute the selected pre-programmed flight plan 960. The autonomous drone 710 captures images to ensure that the fly button 806 is not accidentally pressed, and if a suitable initial face is found, the autonomous drone 710 executes the pre-programmed flight plan 960 and returns to the person. The autonomous drone 710 hovers in front of the person and lands on the person's hand when the person places their hand under the autonomous drone 710. In some examples, the autonomous drone 710 enters a lower power state 641 to save energy while it is flying. For example, wireless connection 666 can be turned off because autonomous drone 710 does not need to receive instructions or commands when it flies. According to some embodiments, autonomous drone 710 is referred to as a personal autonomous drone, drone, semi-autonomous drone or other terms.

[0026] Networked computing environment

[0027] Figure 1 1 is a block diagram illustrating an example messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple instances of client devices 102, each of which hosts multiple applications including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on respective other client devices 102), a messaging server system 108, and a third-party server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with the local host application 106 using an application program interface (API).

[0028] The messaging clients 104 are able to communicate and exchange data with other messaging clients 104 and with the messaging server system 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and the messaging server system 108 includes functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0029] The messaging server system 108 provides server-side functionality to specific messaging clients 104 via the network 112. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client 104 or by the messaging server system 108, it may be a design choice whether certain functions are located within the messaging client 104 or within the messaging server system 108. For example, it may be technically preferred to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the messaging client 104 where the client device 102 has sufficient processing power.

[0030] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include sending data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 104. As examples, the data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the messaging system 100 is activated and controlled by functions available via the user interface (UI) of the messaging client 104.

[0031] Turning now specifically to the messaging server system 108, an application program interface (API) server 116 is coupled to the application server 114 and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to the application server 114 and provides a web-based interface to the application server 114. To this end, the web server 128 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0032] The application program interface (API) server 116 receives and sends message data (e.g., commands and message payloads) between the client device 102 and the application server 114. Specifically, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to activate the functions of the application server 114. An application program interface (API) server 116 exposes various functions supported by application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via application server 114; sending media files (e.g., images or videos) from a messaging client 104 to messaging server 118 and for possible access by another messaging client 104; setting of media data collections (e.g., stories); retrieving a friend list of a user of client device 102; retrieving such collections; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends within a social graph; and opening application events (e.g., related to messaging client 104).

[0033] The application server 114 hosts multiple server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and a social network server 124. The messaging server 118 implements multiple message processing technologies and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. As will be described in more detail, text and media content from multiple sources can be aggregated into collections of content (e.g., referred to as stories or galleries). These collections are then made available to the messaging client 104. In view of the hardware requirements for other processor and memory intensive data processing, other processor and memory intensive data processing can also be performed on the server side by the messaging server 118.

[0034] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically with respect to images or videos within the payload of messages sent from or received at the messaging server 118 .

[0035] The social network server 124 supports various social networking functions and services and makes them available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph 308 (e.g., Figure 3). Examples of functions and services supported by the social network server 124 include identifying other users in the messaging system 100 that have a relationship with a particular user or that the particular user is "following," and identifying interests and other entities of a particular user.

[0036] Returning to the messaging client 104, the features and functions of the external resource (e.g., application 106 or applet) are made available to the user via the interface of the messaging client 104. In this context, "external" refers to the fact that the application 106 or applet is outside the messaging client 104. External resources are usually provided by a third party, but can also be provided by the creator or provider of the messaging client 104. The messaging client 104 receives a user selection of an option to launch or access the features of such an external resource. The external resource can be an application 106 installed on the client device 102 (e.g., a "local app"), or a small-scale version of the application hosted on the client device 102 or away from the client device 102 (e.g., on a third-party server 110) (e.g., a "applet"). The small-scale version of the application includes a subset of the features and functions of the application (e.g., a full-scale, local version of the application) and is implemented using a markup language document. In one example, the small-scale version of the application (e.g., a "applet") is a web-based markup language version of the application and is embedded in the messaging client 104. In addition to using markup language documents (eg, .*ml files), applets may include scripting languages ​​(eg, .*js files or .json files) and style sheets (eg, .*ss files).

[0037] In response to receiving a user selection of an option to launch or access a feature of an external resource, the messaging client 104 determines whether the selected external resource is a web-based external resource or a locally installed application 106. In some cases, the application 106 locally installed on the client device 102 can be independent of the messaging client 104 and launched separately from the messaging client 104, such as by selecting an icon corresponding to the application 106 on a home screen of the client device 102. A small-scale version of such an application can be launched or accessed via the messaging client 104, and in some examples, none of the portions of the small-scale application can be accessed outside of the messaging client 104 or limited portions of the small-scale application can be accessed outside of the messaging client 104. The small-scale application can be launched by the messaging client 104 receiving a markup language document associated with the small-scale application, such as from a third-party server 110, and processing such a document.

[0038] In response to determining that the external resource is a locally installed application 106, the messaging client 104 instructs the client device 102 to launch the external resource by executing the locally stored code corresponding to the external resource. In response to determining that the external resource is a web-based resource, the messaging client 104 communicates with the third-party server 110 (for example) to obtain a markup language document corresponding to the selected external resource. The messaging client 104 then processes the obtained markup language document to present the web-based external resource within the user interface of the messaging client 104.

[0039] The messaging client 104 may notify the user of the client device 102 or other users (e.g., "friends") associated with such a user of activities occurring in one or more external resources. For example, the messaging client 104 may provide a participant in a conversation (e.g., a chat session) in the messaging client 104 with a notification related to the current or recent use of an external resource by one or more members of a user group. One or more users may be invited to join a valid external resource or to launch an external resource that was recently used but is currently inactive (in the friend group). The external resource may provide the participants in the conversation, each using a corresponding messaging client 104, with the ability to share items, conditions, states, or locations in the external resource with one or more members of the user group entering the chat session. The shared item may be an interactive chat card that members of the chat may interact with, for example, to launch a corresponding external resource, view specific information within an external resource, or bring members of the chat to a specific location or state within an external resource. Within a given external resource, a response message may be sent to a user on the messaging client 104. The external resource may selectively include different media items in the response based on the current context of the external resource.

[0040] The messaging client 104 may present a list of available external resources (e.g., applications 106 or applets) to the user to launch or access a given external resource. The list may be presented in the form of a context-sensitive menu. For example, icons representing different applications (or applets) of the application 106 (or applets) may vary based on how the user launches the menu (e.g., from a conversational interface or from a non-conversational interface).

[0041] System Architecture

[0042] Figure 21 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 includes a plurality of subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a transient timer system 202, a collection management system 204, an augmentation system 208, a mapping system 210, a gaming system 212, an external resource system 214, and an autonomous drone management system 216.

[0043] The transient timer system 202 is responsible for implementing temporary or time-limited access to content by the messaging client 104 and the messaging server 118. The transient timer system 202 includes a plurality of timers that selectively enable access (e.g., for presentation and display) of messages and associated content via the messaging client 104 based on duration and display parameters associated with a message or a collection of messages (e.g., a story). Additional details regarding the operation of the transient timer system 202 will be provided below.

[0044] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) may be organized into "event galleries" or "event stories." Such collections may be made available for a specified period of time (e.g., the duration of the event to which the content relates). For example, content related to a concert may be made available as a "story" for the duration of the concert. The collection management system 204 may also be responsible for publishing an icon to the user interface of the messaging client 104 that provides notification of the existence of a particular collection.

[0045] The collection management system 204 also includes a curation interface 206 that enables a collection manager to manage and curate a particular content collection. For example, the curation interface 206 enables an event organizer to curate a collection of content related to a particular event (e.g., to delete inappropriate content or redundant messages). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation may be paid to users for including user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such users for use of their content.

[0046] The enhancement system 208 provides various functions that enable a user to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays for messages processed by the messaging system 100. The enhancement system 208 is operable to supply media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geographic location of the client device 102. In another example, the enhancement system 208 is operable to supply media overlays to the messaging client 104 based on other information such as social network information of the user of the client device 102. The media overlay can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos, digital objects) at the client device 102. For example, the media overlay can include text or images that can be superimposed on the top of a photo taken by the client device 102. In another example, the media overlay includes a location identification overlay (e.g., Venice Beach), the name of a live event, or a business name overlay (e.g., Beach Cafe). In another example, the augmentation system 208 uses the geolocation of the client device 102 to identify a media overlay that includes the name of a business at the geolocation of the client device 102. The media overlay may include other logos associated with the business. The media overlay may be stored in the database 126 and accessed through the database server 120.

[0047] In some examples, the enhancement system 208 provides a user-based publishing platform that enables a user to select a geolocation on a map and upload content associated with the selected geolocation. The user may also specify under what circumstances a particular media overlay should be provided to other users. The enhancement system 208 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

[0048] In other examples, the enhancement system 208 provides a merchant-based publishing platform that enables merchants to select specific media overlays associated with a geographic location via a bidding process. For example, the enhancement system 208 associates the media overlays of the highest bidding merchant with the corresponding geographic location for a predefined amount of time.

[0049] The mapping system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables the display of a user icon or avatar (e.g., stored in the profile data 316) on a map to indicate the current location or past location of the user's "friends" and media content (e.g., a collection of messages including photos and videos) generated by such friends in the context of the map. For example, on the map interface of the messaging client 104, messages posted by the user to the messaging system 100 from a particular geolocation can be displayed to the "friends" of the particular user within the context of that particular location on the map. The user can also share his or her location and status information with other users of the messaging system 100 (e.g., using an appropriate status avatar) via the messaging client 104, where the location and status information is similarly displayed to selected users within the context of the map interface of the messaging client 104.

[0050] The gaming system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a gaming interface that provides a list of available games that can be launched by a user within the context of the messaging client 104 and played with other users of the messaging system 100. The messaging system 100 also enables a particular user to invite other users to participate in the play of a particular game by sending an invitation to such other users from the messaging client 104. The messaging client 104 also supports both voice and text messaging (e.g., chat) within the context of the game play, provides leaderboards for the game, and also supports the provision of in-game rewards (e.g., coins and items).

[0051] The external resource system 214 provides an interface for the messaging client 104 to communicate with a remote server (e.g., a third-party server 110) to launch or access external resources (i.e., applications or applets). Each third-party server 110 hosts, for example, an application or a small-scale version of an application based on a markup language (e.g., HTML5) (e.g., a game application, a utility application, a payment application, or a ride-sharing application). The messaging client 104 can launch a web-based resource (e.g., an application) by accessing an HTML5 file from a third-party server 110 associated with a web-based resource. In some examples, the application hosted by the third-party server 110 is programmed in JavaScript using a software development kit (SDK) provided by the messaging server 118. The SDK includes an application programming interface (API) having functions that can be called or activated by a web-based application. In some examples, the messaging server 118 includes a JavaScript library that provides a given external resource access to certain user data of the messaging client 104. HTML5 is used as an example technology for programming games, but applications and resources programmed based on other technologies can be used.

[0052] To integrate the functionality of the SDK into a web-based resource, the SDK is downloaded by the third-party server 110 from the messaging server 118, or received by the third-party server 110 in other ways. Once downloaded or received, the SDK will be included as part of the application code of the web-based external resource. The code of the web-based resource can then call or activate certain functions of the SDK to integrate the features of the messaging client 104 into the web-based resource.

[0053] The SDK stored on the messaging server 118 effectively provides a bridge between external resources (e.g., applications 106 or applet) and the messaging client 104. This provides users with a seamless experience of communicating with other users on the messaging client 104 while retaining the look and feel of the messaging client 104. In order to bridge the communication between the external resources and the messaging client 104, in some examples, the SDK facilitates the communication between the third-party server 110 and the messaging client 104. In some examples, the WebViewJavaScriptBridge running on the client device 102 establishes two one-way communication channels between the external resources and the messaging client 104. Messages are sent asynchronously via these communication channels between the external resources and the messaging client 104. Each SDK function activation is sent as a message and a callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with the callback identifier.

[0054] By using the SDK, not all information from the messaging client 104 is shared with the third-party server 110. The SDK limits which information is shared based on the needs of the external resource. In some examples, each third-party server 110 provides an HTML5 file corresponding to a web-based external resource to the messaging server 118. The messaging server 118 can add a visual representation (e.g., box art or other graphics) of the web-based external resource in the messaging client 104. Once the user selects the visual representation or instructs the messaging client 104 to access the features of the web-based external resource through the GUI of the messaging client 104, the messaging client 104 obtains the HTML5 file and instantiates the resources required to access the features of the web-based external resource.

[0055] The messaging client 104 presents a graphical user interface (e.g., a login page or title screen) for the external resource. During, before, or after presenting the login page or title screen, the messaging client 104 determines whether the launched external resource has been previously authorized to access the user data of the messaging client 104. In response to determining that the launched external resource has been previously authorized to access the user data of the messaging client 104, the messaging client 104 presents other graphical user interfaces of the external resource including the functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access the user data of the messaging client 104, after displaying the login page or title screen of the external resource for a threshold period of time (e.g., 3 seconds), the messaging client 104 slides a menu for authorizing the external resource to access the user data (e.g., animating the menu to emerge from the bottom of the screen to the middle or other portion of the screen). The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving the user selection of the accept option, the messaging client 104 adds the external resource to the list of authorized external resources and enables the external resource to access the user data from the messaging client 104. In some examples, the messaging client 104 authorizes the external resource to access the user data according to the OAuth 2 framework.

[0056] The messaging client 104 controls the type of user data shared with the external resource based on the type of external resource that is authorized. For example, an external resource including a full-scale application (e.g., application 106) is provided with access to a first type of user data (e.g., only a two-dimensional avatar of the user with or without different avatar characteristics). As another example, an external resource including a small-scale version of an application (e.g., a web-based version of the application) is provided access to a second type of user data (e.g., payment information, a two-dimensional avatar of the user, a three-dimensional avatar of the user, and an avatar with various avatar characteristics). Avatar characteristics include different ways to customize the look and feel of an avatar (e.g., different poses, facial features, clothing, etc.).

[0057] Autonomous UAV management system 216 provides for managing Figure 7 , Figure 8 , Fig.11 and Fig.12 710 of the autonomous drone. In some examples, the control application resides in a host device such as the client device 102, the off-site client device 704, the server 706, the smartphone 708. For example, the control application enables a user to set thresholds, flight plans for the control knob 614, and other preferences. In some examples, the autonomous drone management system 216 provides functions and routines that assist the control application.

[0058] Data Architecture

[0059] Figure 3 is a diagram illustrating a data structure 300 that may be stored in a database 126 of a messaging server system 108 according to some examples. Although the contents of the database 126 are illustrated as including a plurality of tables, it should be understood that data may be stored in other types of data structures (e.g., as an object-oriented database).

[0060] Database 126 includes message data stored in message table 302. For any particular message, the message data includes at least message sender data, message recipient (or receiver) data, and payload. Figure 4 Additional details regarding information that may be included in a message and included within the message data stored in message table 302 are described.

[0061] The entity table 306 stores entity data and is linked (e.g., referenced) to the entity graph 308 and profile data 316. The entities for which records are maintained within the entity table 306 may include individuals, corporate entities, organizations, objects, places, events, etc. Regardless of the entity type, any entity about which the messaging server system 108 stores data may be an identified entity. Each entity is provided with a unique identifier as well as an entity type identifier (not shown).

[0062] The entity graph 308 stores information about relationships and associations between entities. By way of example only, such relationships may be social, professional (e.g., working in a common company or organization), interest-based, or activity-based.

[0063] The profile data 316 stores multiple types of profile data about a particular entity. Based on the privacy settings specified by the particular entity, the profile data 316 can be selectively used and presented to other users of the messaging system 100. In the case where the entity is a person, the profile data 316 includes, for example, a user name, phone number, address, settings (e.g., notification and privacy settings), and an avatar representation (or a collection of such avatar representations) selected by the user. The particular user can then selectively include one or more of these avatar representations within the content of messages transmitted via the messaging system 100 and on a map interface displayed to other users by the messaging client 104. The collection of avatar representations can include a "status avatar" that presents a graphical representation of a status or activity that a user can select to communicate at a particular time.

[0064] Where the entity is a group, the profile data 316 for the group may similarly include one or more avatar representations associated with the group, in addition to the group name, members, and various settings related to the group (eg, notifications).

[0065] Database 126 also stores enhancement data, such as overlays or filters, in enhancement table 310. Enhancement data is associated with and applied to videos (whose data is stored in video table 304) and images (whose data is stored in image table 312).

[0066] In one example, a filter is an overlay displayed as an overlay on an image or video during presentation to a recipient user. Filters can be of various types, including filters selected by a user from a set of filters presented to a sending user by messaging client 104 when the sending user is composing a message. Other types of filters include geolocation filters (also referred to as geofilters), which can be presented to a sending user based on geolocation. For example, a geolocation filter specific to a nearby or special location can be presented by messaging client 104 within a user interface based on geolocation information determined by a global positioning system (GPS) unit of client device 102.

[0067] Another type of filter is a data filter, which can be selectively presented to the sending user by the messaging client 104 based on other input or information collected by the client device 102 during the message creation process. Examples of data filters include the current temperature at a particular location, the current speed at which the sending user is traveling, the battery life of the client device 102, or the current time.

[0068] Other augmented data that may be stored in the image table 312 include augmented reality content items (eg, corresponding to application lenses or augmented reality experiences). Augmented reality content items may be real-time special effects and sounds that may be added to an image or video.

[0069] As described above, augmented data includes augmented reality content items, overlays, image transformations, AR images, and similar terms referring to modifications that can be applied to image data (e.g., videos or images). This includes real-time modifications that modify images when they are captured using a device sensor (e.g., one or more cameras) of the client device 102 and then display the modified images on the screen of the client device 102. This also includes modifications to stored content such as video clips in a gallery that can be modified. For example, in a client device 102 that can access multiple augmented reality content items, a user can use a single video clip with multiple augmented reality content items to watch how different augmented reality content items will modify the stored clips. For example, by selecting different augmented reality content items for the content, multiple augmented reality content items that apply different pseudo-random movement models can be applied to the same content. Similarly, real-time video capture can be used with the modifications shown to show how the video image currently captured by the sensor of the client device 102 will modify the captured data. Such data may simply be displayed on the screen without being stored in memory, or content captured by the device sensors may be recorded and stored in memory with or without modification (or both). In some systems, a preview function may display how different augmented reality content items will be displayed simultaneously in different windows of the display. This may, for example, enable viewing of multiple windows with different pseudo-random animations on the display simultaneously.

[0070] Thus, data and various systems using augmented reality content items or other such transformation systems that modify content using such data may involve detection of objects (e.g., faces, hands, bodies, cats, dogs, surfaces, objects, etc.) in video frames; tracking of such objects as they leave, enter, and move around the field of view; and modification or transformation of such objects as they are tracked. In various examples, different methods for implementing such transformations may be used. Some examples may involve: generating a three-dimensional mesh model of one or more objects and using transformations and animated textures of the models within a video to implement the transformations. In other examples, tracking of points on an object may be used to place an image or texture (which may be two-dimensional or three-dimensional) at the tracked location. In further examples, neural network analysis of a video frame may be used to place an image, model, or texture in content (e.g., an image or video frame). Thus, an augmented reality content item refers to both images, models, and textures used to create transformations in the content, as well as additional modeling and analysis information required to implement such transformations using object detection, tracking, and placement.

[0071] Real-time video processing can be performed using any kind of video data (e.g., video streams, video files, etc.) stored in the memory of any kind of computerized system. For example, a user can load video files and store them in the memory of the device, or a sensor of the device can be used to generate a video stream. In addition, any object, such as a human face and parts of a human body, an animal, or a non-living thing (e.g., a chair, a car, or other objects) can be processed using computer animation models.

[0072] In some examples, in the case where a specific modification is selected together with the content to be transformed, the element to be transformed is identified by the computing device, and then if the element to be transformed is present in the video frame, the element to be transformed is detected and tracked. The elements of the object are modified according to the request for modification, thereby transforming the frame of the video stream. The transformation of the frame of the video stream can be performed by different methods for different types of transformations. For example, for the transformation of the frame that mainly involves changing the form of the elements of the object, the characteristic points of each element of the object are calculated (for example, using an active shape model (ASM) or other known methods). Then, for each element of at least one element of the object, a grid based on the characteristic points is generated. The grid is used for the subsequent stage of tracking the elements of the object in the video stream. During the tracking process, the grid mentioned for each element is aligned with the position of each element. Then, additional points are generated on the grid. A first set of first points is generated for each element based on the request for modification, and a set of second points is generated for each element based on the set of first points and the request for modification. Then, the frame of the video stream can be transformed by modifying the elements of the object based on the set of first points and the set of second points and the grid. In such a method, the background of the modified object may also be changed or deformed by tracking and modifying the background of the modified object.

[0073] In some examples, the transformation of some areas of the object using the elements of the object can be performed by calculating the characteristic points of each element of the object and generating a grid based on the calculated characteristic points. Points are generated on the grid, and then various areas are generated based on the points. Then, the elements of the object are tracked by aligning the area of ​​each element with the position of each element of at least one element, and the properties of the area can be modified based on the modification request, thereby transforming the frame of the video stream. Depending on the specific modification request, the properties of the mentioned area can be transformed in different ways. Such modifications may involve: changing the color of the area; removing at least some parts of the area from the frame of the video stream; including one or more new objects in the area based on the modification request; and modifying or distorting the elements of the area or object. In various examples, any combination of such modifications or other similar modifications can be used. For certain models to be animated, some characteristic points can be selected as control points for determining the entire state space of options for model animation.

[0074] In some examples of computer animation models that use face detection to transform image data, faces are detected on an image using a specific face detection algorithm (e.g., Viola-Jones). An active shape model (ASM) algorithm is then applied to the face region of the image to detect facial feature reference points.

[0075] Other methods and algorithms suitable for face detection can be used. For example, in some examples, landmarks are used to locate features, which represent distinguishable points that exist in most of the images considered. For example, for facial landmarks, the location of the left eye pupil can be used. If the initial landmark is not recognizable (for example, if the person wears an eye patch), secondary landmarks can be used. Such a landmark recognition process can be used for any such object. In some examples, a set of landmarks forms a shape. The shape can be represented as a vector using the coordinates of the points in the shape. One shape is aligned with another shape using a similarity transformation (allowing translation, scaling, and rotation) that minimizes the average Euclidean distance between the shape points. The mean shape (meanshape) is the average value of the aligned training shapes.

[0076] In some examples, a landmark search begins with an average shape that aligns with the location and size of a face determined by a global face detector. Such a search then repeats the steps of suggesting tentative shapes by adjusting the positioning of shape points by template matching the image texture around each point, and then conforming the tentative shapes to a global shape model until convergence occurs. In some systems, individual template matches are unreliable, and the shape model pools the results of weak template matches to form a stronger overall classifier. The entire search is repeated at each level of the image pyramid from coarse to fine resolution.

[0077] The transformation system can capture an image or video stream on a client device (e.g., client device 102) and perform complex image manipulations locally on the client device 102 while maintaining an appropriate user experience, computational time, and power consumption. Complex image manipulations can include size and shape changes, mood transformations (e.g., changing a face from a frown to a smile), state transformations (e.g., aging a subject, reducing apparent age, changing gender), style transformations, application of graphical elements, and any other suitable image or video manipulations enabled by a convolutional neural network that has been configured to execute efficiently on the client device 102.

[0078] In some examples, a computer animation model for transforming image data can be used by a system in which a user can capture an image or video stream of the user (e.g., a selfie) using a client device 102 having a neural network that operates as part of a messaging client 104 operating on the client device 102. A transformation system operating within the messaging client 104 determines the presence of a face within the image or video stream and provides a modification icon associated with the computer animation model to transform the data image, or the computer animation model can be presented in association with an interface described herein. The modification icon includes the following changes, which can be the basis for modifying the face of the user within the image or video stream as part of the modification operation. Once the modification icon is selected, the transformation system initiates a process of transforming the image of the user to reflect the selected modification icon (e.g., generating a smiley face on the user). Once the image or video stream is captured and the specified modification is selected, the modified image or video stream can be presented in a graphical user interface displayed on the client device 102. The transformation system can implement a complex convolutional neural network on a portion of the image or video stream to generate and apply the selected modification. That is, a user can capture an image or video stream, and once a modification icon has been selected, the modified result can be presented in real time or near real time. In addition, when the video stream is being captured, the modification can be persistent and the selected modification icon remains toggled. Machine learning neural networks can be used to implement such modifications.

[0079] The graphical user interface presenting the modifications performed by the transformation system can supply additional interactive options for the user. Such options can be based on the interface for initiating content capture and selecting a specific computer animation model (e.g., initiated from a content creator user interface). In various examples, the modifications can be persistent after the modification icon is initially selected. The user can switch the modification on or off by tapping or otherwise selecting the face being modified by the transformation system, and store it for later viewing or browsing other areas of the imaging application. In the case of multiple faces being modified by the transformation system, the user can globally switch the modification on or off by tapping or selecting a single face modified and displayed within the graphical user interface. In some examples, each face in a plurality of face groups can be modified individually, or such modifications can be switched individually by tapping or selecting a single face or a series of faces displayed within the graphical user interface.

[0080] The story table 314 stores data about a collection of messages and associated image, video or audio data that are compiled into a collection (e.g., a story or gallery). The creation of a particular collection can be initiated by a particular user (e.g., each user whose record is maintained in the entity table 306). A user can create a "personal story" in the form of a collection of content that has been created and sent / broadcasted by the user. To this end, the user interface of the messaging client 104 may include a user-selectable icon to enable the sending user to add specific content to his or her personal story.

[0081] A collection may also constitute a "live story" that is a collection of content from multiple users, created manually, automatically, or using a combination of manual and automatic techniques. For example, a "live story" may constitute a curated stream of content submitted by users from different locations and events. Users whose client devices have location services enabled and who are at a co-located event at a particular time may be presented with an option, for example via a user interface of the messaging client 104, to contribute content to a particular live story. Live stories may be identified to a user by the messaging client 104 based on his or her location. The end result is a "live story" told from a community perspective.

[0082] Another type of content collection is referred to as a "location story," which enables users whose client devices 102 are located within a particular geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some embodiments, contributions to location stories may require secondary authentication to verify that the end user belongs to a particular organization or other entity (e.g., is a student on a university campus).

[0083] As mentioned above, the video table 304 stores video data, which in one example is associated with a message whose record is saved within the message table 302. Similarly, the image table 312 stores image data associated with a message whose message data is stored in the entity table 306. The entity table 306 can associate various enhancements from the enhancement table 310 with the various images and videos stored in the image table 312 and the video table 304.

[0084] Data communication architecture

[0085] Figure 4 is a schematic diagram illustrating the structure of a message 400 generated by a messaging client 104 for transmission to another messaging client 104 or a messaging server 118 according to some examples. The content of a particular message 400 is used to populate a message table 302 stored in a database 126 accessible by a messaging server 118. Similarly, the content of the message 400 is stored in memory as "in-flight" or "in-flight" data of a client device 102 or application server 114. The message 400 is shown to include the following example components:

[0086] Message identifier 402 : a unique identifier that identifies the message 400 .

[0087] Message text payload 404 : Text to be generated by a user via the user interface of the client device 102 and included in the message 400 .

[0088] Message image payload 406 : Image data captured by a camera component of the client device 102 or retrieved from a memory component of the client device 102 and included in the message 400 . Image data for a sent or received message 400 may be stored in the image table 312 .

[0089] Message video payload 408 : Video data captured by the camera component or retrieved from the memory component of the client device 102 and included in the message 400 . The video data for a message 400 sent or received may be stored in the video table 304 .

[0090] Message audio payload 410 : audio data captured by a microphone or retrieved from a memory component of the client device 102 and included in the message 400 .

[0091] Message enhancement data 412 : Enhancement data (eg, filters, stickers, or other annotations or enhancements) representing enhancements to be applied to the message image payload 406 , message video payload 408 , or message audio payload 410 of the message 400 . The enhancement data for a sent or received message 400 may be stored in the enhancement table 310 .

[0092] Message duration parameter 414: A parameter value indicating the amount of time in seconds that the content of a message (eg, message image payload 406, message video payload 408, message audio payload 410) will be presented to or made accessible to a user via messaging client 104.

[0093] Message geolocation parameters 416: Geolocation data (e.g., latitude and longitude coordinates) associated with the content payload of the message. Multiple message geolocation parameter 416 values ​​may be included in the payload, each of which is associated with a content item included in the content (e.g., a specific image within a message image payload 406 or a specific video in a message video payload 408).

[0094] Message story identifier 418: An identifier value that identifies one or more content collections (e.g., a "story" identified in story table 314) associated with a particular content item in message image payload 406 of message 400. For example, multiple images within message image payload 406 may each be associated with multiple content collections using an identifier value.

[0095] Message tags 420: Each message 400 may be tagged with a plurality of tags, each of which indicates the subject of the content included in the message payload. For example, where a particular image included in the message image payload 406 depicts an animal (e.g., a lion), a tag value may be included within the message tags 420 indicating the relevant animal. The tag value may be manually generated based on user input, or may be automatically generated using, for example, image recognition.

[0096] • Message sender identifier 422: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 on which the message 400 was generated and from which the message 400 was sent.

[0097] • Message recipient identifier 424: An identifier (eg, a messaging system identifier, an email address, or a device identifier) ​​that indicates the user of the client device 102 to which the message 400 is addressed.

[0098] The content (e.g., value) of the various components of message 400 may be pointers to locations in a table storing content data values. For example, the image value in message image payload 406 may be a pointer to a location within image table 312 (or the address of a location within image table 312). Similarly, the value within message video payload 408 may point to data stored within video table 304, the value stored within message enhancement 412 may point to data stored in enhancement table 310, the value stored within message story identifier 418 may point to data stored in story table 314, and the values ​​stored within message sender identifier 422 and message recipient identifier 424 may point to user records stored within entity table 306.

[0099] Time-based access restriction architecture

[0100] Figure 5 is a schematic diagram illustrating an access restriction process 500 in which access to content (e.g., a multimedia payload of an ephemeral message 502 and associated data) or a collection of content (e.g., an ephemeral message group 504) can be time-restricted (e.g., made ephemeral).

[0101] The ephemeral message 502 is shown to be associated with a message duration parameter 506, the value of which determines the amount of time that the messaging client 104 will display the ephemeral message 502 to the receiving user of the ephemeral message 502. In one example, depending on the amount of time specified by the sending user using the message duration parameter 506, the receiving user can view the ephemeral message 502 for up to 10 seconds.

[0102] The message duration parameter 506 and the message recipient identifier 424 are shown as inputs to a message timer 510, which is responsible for determining the amount of time that the transient message 502 is shown to a particular receiving user identified by the message recipient identifier 424. In particular, the transient message 502 will only be shown to the relevant receiving user for a period of time determined by the value of the message duration parameter 506. The message timer 510 is shown as providing an output to a more general transient timer system 202, which is responsible for the overall timing of displaying content (e.g., the transient message 502) to the receiving user.

[0103] Short message 502 Figure 5504 (e.g., a collection of messages in a personal story or an event story). The ephemeral message group 504 has an associated group duration parameter 508, the value of which determines the duration for which the ephemeral message group 504 is presented and accessible to users of the messaging system 100. For example, the group duration parameter 508 may be the duration of a concert, where the ephemeral message group 504 is a collection of content about the concert. Alternatively, a user (an owning user or a curator user) may specify a value for the group duration parameter 508 when performing setup and creation of the ephemeral message group 504.

[0104] In addition, each ephemeral message 502 within the ephemeral message group 504 has an associated group participation parameter 512, the value of which determines the duration for which the ephemeral message 502 will be accessible within the context of the ephemeral message group 504. Thus, a particular ephemeral message group 504 may "expire" and become inaccessible within the context of the ephemeral message group 504 before the ephemeral message group 504 itself expires according to the group duration parameter 508. The group duration parameter 508, the group participation parameter 512, and the message recipient identifier 424 each provide inputs to a group timer 514, which is operable to first determine whether a particular ephemeral message 502 in the ephemeral message group 504 is to be displayed to a particular receiving user, and if so, how long to display it. Note that the identity of the particular receiving user is also known to the ephemeral message group 504 due to the message recipient identifier 424.

[0105] Thus, the group timer 514 is operable to control the overall lifespan of the associated ephemeral message group 504 and the individual ephemeral messages 502 included in the ephemeral message group 504. In one example, each ephemeral message 502 within the ephemeral message group 504 remains viewable and accessible for a period of time specified by the group duration parameter 508. In another example, within the context of the ephemeral message group 504, a particular ephemeral message 502 may expire based on the group participation parameter 512. Note that even within the context of the ephemeral message group 504, the message duration parameter 506 may still determine the duration for which a particular ephemeral message 502 is displayed to a receiving user. Thus, the message duration parameter 506 determines the duration for which a particular ephemeral message 502 is displayed to a receiving user, regardless of whether the receiving user is viewing the ephemeral message 502 within or outside the context of the ephemeral message group 504.

[0106] The transient timer system 202 may also be operable to remove a particular transient message 502 from the transient message group 504 based on a determination that an associated group participation parameter 512 has been exceeded. For example, where a sending user has established a group participation parameter 512 of 24 hours from posting, the transient timer system 202 will remove the associated transient message 502 from the transient message group 504 after the designated 24 hours. The transient timer system 202 may also be operable to remove a transient message group 504 when the group participation parameter 512 for each transient message 502 within the transient message group 504 has expired, or when the transient message group 504 itself has expired according to the group duration parameter 508.

[0107] In some use cases, the creator of a particular ephemeral message group 504 may specify an indefinite group duration parameter 508. In this case, the expiration of the group participation parameter 512 for the last remaining ephemeral message 502 within the ephemeral message group 504 will determine when the ephemeral message group 504 itself expires. In this case, a new ephemeral message 502 with a new group participation parameter 512 added to the ephemeral message group 504 effectively extends the life of the ephemeral message group 504 to a value equal to the group participation parameter 512.

[0108] In response to the transient timer system 202 determining that the transient message group 504 has expired (e.g., is no longer accessible), the transient timer system 202 communicates with the messaging system 100 (and, for example, in particular, the messaging client 104) to cause the indicia (e.g., icon) associated with the relevant transient message group 504 to no longer be displayed within the user interface of the messaging client 104. Similarly, when the transient timer system 202 determines that the message duration parameter 506 for a particular transient message 502 has expired, the transient timer system 202 causes the messaging client 104 to no longer display the indicia (e.g., icon or text identification) associated with the transient message 502.

[0109] Unlocking Autonomous Drones

[0110] Figure 6 An example of components 600 for an autonomous drone is shown, according to some examples. Figure 6 The component 600 shown in FIG. 1 is such as Figure 7 , Figure 8 , Fig.10 and Fig.11Components 600 are organized into functional groups including input / output devices 602, processor 604, memory 606, battery 608, power chip 610, sensor 648, wireless connection 666, power and communication connection 646, and propulsion system 684. Those skilled in the art will recognize that components 600 may be organized into different functional groups, or may all be part of an autonomous drone individually.

[0111] Components 600 are connected via power and communication connections 646. According to some examples, power and communication connections 646 include one or more communication buses, power buses, and / or point-to-point connections. In addition, one or more components in components 600 may be optional. And components 600 may include additional components. In addition, the number of components as shown may be different. For example, there may be multiple processors 604. The terms electrical and electronic may be used to refer to electrical components and / or electronic components.

[0112] The propulsion system 684 includes electric motors 686, each of which includes a rotor 688 associated with a propeller 690. According to some examples, the propeller 690 provides powered lift to the autonomous drone 710, as well as accelerates and rotates the autonomous drone. The motor 686, which is activated once in response to a signal including a motor operation instruction from, for example, the processor 604, spins the rotor 688, which spins the propeller 690. The motor 686 and the actuator 638 are powered by the battery 608 and / or the power chip 610 and are controlled by a signal from the processor 604. According to some examples, the motor 686 is a variable motor. In some examples, the motor 686 has a low setting, which the processor 604 can use to indicate to the user of the autonomous drone that the autonomous drone is preparing to take off.

[0113] Having more than one propeller 690 enables the autonomous drone to continue flying if one or more of the motors 686, rotors 688, or propellers 690 fails. For example, if one of the motors 686 fails, the autonomous drone 710 can still remain aloft with the remaining motors 686 working together to compensate. In some examples, the propulsion system 684 sends a signal to the processor 604 indicating that the motor 686 is not operating properly. In some examples, the motor 686 provides a signal to the processor 604 indicating whether the motor 686 is operating properly. In addition, the greater the number of motors 686 incorporated into the autonomous drone, the greater the lift that the autonomous drone 710 will generate, allowing the autonomous drone to carry a heavier payload, such as one or more sensors 648.

[0114] In some examples, the propulsion system 684 includes one or more actuators 638 that tilt the motor 686 so that the motor 686 can operate at a certain angle relative to the reference frame of the autonomous drone. For example, each motor 686 is rotationally mounted on the autonomous drone with a single rotation axis, where the actuator 638 controls the angle of the motor 686. In some examples, each motor 686 is rotationally mounted with two or more rotation axes controlled by one or more actuators 638. In some examples, one or more actuators 638 control the angle of more than one motor 686.

[0115] The functional group includes a sensor 648, which has a component 600 including a photographic camera 650, a navigation camera 651, an inertial measurement unit (IMU) A 652, an altimeter 654, a gyroscope 656, an IMU B 658, an accelerometer 665, an altitude detector 660 (which includes a light 662 and a light detector 664), a magnetic sensor 659, a wind speed sensor 661, a clock 663, a motion sensor 667, a microphone 669, an orientation 671, etc.

[0116] In some examples, sensor 648 generates data that is processed by processor 604 and stored as data in memory 606 (e.g., stored as data 630 in memory 1 626 or stored as data 636 in memory N 632). For example, altimeter 654 is an instrument used to determine the altitude reached. Thus, when the autonomous drone is set to hover in position, processor 604 uses data from altimeter 654 to determine the altitude and adjust propulsion system 684 to maintain that altitude.

[0117] Alternatively or additionally, the altitude detector 660 is used to generate data that can be used to determine the altitude of the autonomous drone above the ground. For example, the light 662 of the altitude detector 660 is mounted on the bottom of the autonomous drone to shine light downward toward the ground, which reflects and hits the light detector 664. The processor 604 uses the data generated from the light irradiated by the light 662 and received at the light detector 664 to determine the altitude of the autonomous drone above the ground based on the flight time of the light and the speed of the light. The light 662 is a suitable light source that is strong enough to produce a reflection on the ground that is detectable by the light detector 664. In some examples, the light 662 emits electromagnetic radiation at a specific wavelength, and the light detector 664 is manufactured to detect the specific wavelength. In some examples, the altitude is also determined based on the roll and pitch of the autonomous drone to account for the fact that the light 662 may not shine light straight down. In some examples, the altitude detector 660 is based on sonar.

[0118] IMU A 652 and IMU B 658 use a combination of accelerometers, gyroscopes, and optionally magnetometers to output measurements such as specific force, angular rate, and orientation of autonomous drones. Altimeter 654, gyroscope 656, accelerometer 665, and other sensors 648 can be replaced by IMU A 652 and / or IMU B 658. Various combinations of sensors 648 can be used to generate data required for navigating autonomous drones. In some examples, sensor 648 includes a lidar system, a radar system, a light sensor, or other forms of sensors that can be used to assist navigation and / or photography. In some examples, sensors 648 that enable autonomous drones to determine the pitch, yaw, and roll of autonomous drones are included. In some examples, sensor 648 includes a motion sensor 667 that does not require power but generates signals based on the autonomous drone being moved. Motion sensor 667 can be used to generate events to which processor 604 responds.

[0119] The photographic camera 650 and other sensors 648 generate data that can be captured for the purpose of displaying or saving data for a user of the autonomous drone. The photographic camera 650 includes a sensor divided into pixels. In some examples, the photographic camera 650 is mounted horizontally relative to the axis of the propeller 690 of the autonomous drone 710, and the navigation camera 651 is mounted vertically relative to the axis of the propeller 690 and is oriented to face downward.

[0120] The sensor generates an electrical signal based on the light shining on the sensor. In some examples, reference Fig. 9 , the data generated is associated with the location 952 and time 936 of the autonomous drone 710. In some examples, IMU A 652 is coupled to the camera 650, which enables the processor 604 to stabilize the camera 650 to obtain improved photography, and determine whether the photo is unreliable because the camera 650 has not been stabilized. The camera 651 can be rotatably mounted on the body of the autonomous drone, so as to be coupled to the body via one or more actuators or other mechanisms to control the orientation of the camera 650 relative to the body of the autonomous drone. IMU B 658 is attached to the autonomous drone to provide data for navigation. The processor 604 uses the data generated by the IMU for navigation, and in some examples, to stabilize the camera 650. In some examples, there are more than one camera 650.

[0121] The navigation camera 651 is mounted on the body of the autonomous drone to provide data to assist the navigation of the autonomous drone. There may be more than one navigation camera 651. For example, the navigation may be a front camera mounted on the body of the autonomous drone, wherein the navigation camera 651 is positioned to pick up an image of the scene to which the autonomous drone is pointing. Additionally or alternatively, the navigation camera 651 may be mounted vertically on the body of the autonomous drone, wherein the navigation camera 651 is positioned to pick up an image of the terrain being flown over. One or more navigation cameras 651 may be movably or fixedly mounted on the body of the autonomous drone, thereby being coupled to the body via one or more actuators or other mechanisms to control the orientation of one or more navigation cameras 651 relative to the body of the autonomous drone. In some examples, the photographic camera 650 also serves as the navigation camera 651. In some examples, the photographic camera 650 provides a greater pixel resolution than the navigation camera 651 and requires more power to operate.

[0122] Data such as video and digital images captured by the photographic camera 650 and the navigation camera 651 can be stored in the memory 606 as data 630, 636. In addition, the data captured by the photographic camera 650 and / or the navigation camera 651 can be wirelessly streamed to the external device 682 in near real time using a wireless connection. In addition, the autonomous drone can send or receive data including instructions to or from the external device 682.

[0123] Magnetic sensor 659 provides data about the orientation of the autonomous drone within the magnetic field. Wind speed sensor 661 indicates wind speed, which may be wind speed and / or direction on the surface, which processor 604 may use to estimate the true wind speed based on the flight characteristics and settings of the autonomous drone (such as, power to motor 686). Clock 663 generates data indicating time. In some embodiments, clock 663 indicates Greenwich Mean Time. In some embodiments, clock 663 generates time relative to events such as power supply of the autonomous drone. Microphone 669 converts sound waves into electrical signals that may be stored as data 630, 636 processed by processor 604. Orientation 671 is a sensor that indicates the orientation of the autonomous drone 710. For example, orientation 671 indicates whether the autonomous drone is facing right side up or upside down.

[0124] The wireless connection 666 includes one or more wireless protocols that may include radio waves and / or light waves. As shown, the wireless connection 666 includes a GPS chip 668, a lower power wireless chip 670 connected to a transceiver / antenna 672, and a higher power wireless chip 676 connected to a transceiver / antenna 678. The GPS chip 668 is connected to an antenna / transceiver that may be inside or outside the chip. The GPS chip 668 receives communications from satellites and uses information based on signals received from multiple satellites to determine the location of the autonomous drone. The GPS chip 668 is a higher power chip 676. In some examples, the processor 604 receives setup data required for the operation of the GPS chip 668 from an external device 682, wherein the setup data may include information about the satellites from which the GPS chip 668 receives signals, wherein the data may include location information about the satellites.

[0125] The lower power wireless chip 670 may include a chip that executes one or more lower power wireless protocols. For example, Bluetooth Low Energy (BLE) may be used to communicate with a closer external device 682. The higher power wireless chip 676 includes a chip that executes one or more higher power wireless protocols. For example, 3GPP protocols and IEEE 802.11 protocols.

[0126] The input / output device 602 provides input and output to the autonomous drone that can be used by the user. The indicator light 612 indicates the status of the autonomous drone and is visible to the user of the autonomous drone. For example, the indicator light 612 can indicate on and off, the charge level, the charging state such as charging or not charging, the standby state, whether there are photos or videos in the memory, whether the memory is full or not full, whether the wireless connection 666 is on or off, etc. An electronic display such as an LCD display can be in addition to or in place of the indicator light 612. In some embodiments, one of the buttons 618 is a flight button that, when pressed, indicates to the autonomous drone 710 that it should take off.

[0127] The control knob 614, which may take other forms, is a knob mounted on the exterior of the autonomous drone that provides a user with the ability to control the operation of the autonomous drone. According to some embodiments, the control knob 614 may be referred to as a control user interface device or other similar terminology. The control knob 614 has multiple positions or states, such as off, on, for transmitting data such as images out of the autonomous drone, various flight paths and behaviors, etc. The state 615 is an internal state that provides information to the processor 604 about the setting of the control knob 614. Other input and output user interface items may be used in addition to or in place of the control knob 614.

[0128] Connector 616 is an external connector that provides a power connection and / or a data connection from an external device 682 to an autonomous drone. For example, there is a power connector 616 for charging an autonomous drone. Power connector 616 or another connector 616 can be used to transmit data to a host device or to receive power from another power source. In some examples, connector 616 is a wirelessly rechargeable connector 616 so that the autonomous drone is placed on or near a charging base. In some examples, there is a connector 616 for a micro secure digital (SD) card or another external storage device.

[0129] In some examples, there is a button 618 for performing one or more functions. For example, button 618, when pressed, instructs the autonomous drone to perform any function indicated by control knob 614, such as taking off as quickly as possible and taking a portrait photo of the user of the autonomous drone.

[0130] The processor 604 executes instructions 620 to process data 630, 636 and / or to control the operation of the autonomous drone. The instructions 620 are machine instructions that specify the operations to be performed by the processor 604 and can be stored in a cache memory that is part of the processor 604 chip. Power section 1 622 to power section N 624 indicate that the processor 604 is divided into different parts so that the power chip 610 can select which parts of the processor 604 to provide power to according to the different power states 641 of the autonomous drone. Throughout the discussion, the processor 604 is described as a participant in determining various functions, but those skilled in the art will recognize that dedicated chips can be included in various components of the autonomous drone to perform specific functions. For example, the altitude detector 660 may include a processing circuit system that determines the height above the ground and outputs data indicating the height above the ground for consumption by the processor 604.

[0131] The memory 606 includes memory 1 626 to memory N 632. Memory 1 626 and memory N 632 include instructions 628, 634 and data 630, 636, respectively. The processor 604 and one or more other components 600 can access the memory via power and communication connection 646. The memory of memory 1 626 to memory N 632 is a main memory, which is used to store data generated by the sensor 648 and other data for communication such as to and from the wireless connection 666. According to some examples, the main memory is a dynamic memory such as DRAM or RAM. Another memory of memory 1 626 to memory N 632 is a static memory such as SRAM or a ROM that does not require power to maintain a state. In some examples, another memory of memory 1 626 to memory N 632 is a storage unit as a machine-readable medium. For example, the storage unit is a removable micro SD card. The power chip 610 has connections to different memories so that the power chip 610 can provide power to one or more of the memories of memory 1 626 to memory N 632. Instructions 628, 634 and data 630, 636 reside completely or partially in main memory, static memory, storage unit and / or within the processor 604, such as in a cache memory, or any suitable combination thereof. The main memory, static memory, storage unit and memory of the processor 604 are examples of machine-readable media.

[0132] The autonomous drone may have a pre-programmed flight path or operation that controls the flight path and operation of the autonomous drone. Fig. 9 , pre-programmed flight plan 960. Pre-programmed flight plan 960 can be associated with the position or state 615 of control knob 614. Memory 606 stores pre-programmed flight paths or maneuvers. In some examples, the autonomous drone downloads new pre-programmed flight paths or maneuvers from external device 682.

[0133] Alternatively or in addition, the movement of the autonomous drone can be controlled by a remote controller such as external device 682 that acts as a remote control device, which can be used by a pilot or user to start, land, take photos or videos, and navigate the autonomous drone if the autonomous drone is not acting as an autonomous drone. In these embodiments, the autonomous drone does not act as an autonomous drone but is a remotely controlled drone. The remote controller can take many forms, from game controller-like controllers to smartphones and tablets. Regardless of their design, the remote controller needs to communicate with the autonomous drone, and typically uses radio waves to communicate. For example, drones typically operate over 2.4 gigahertz radio waves. To communicate with autonomous drones, many drone controllers use one of the communication protocols of IEEE 802.11, which may be referred to as Wi-Fi, which can transmit on the 2.4 gigahertz spectrum and is used by smartphones and tablets for communication. In one example, referring to Figure 7 , UAV 710 uses Wi-Fi or Communicates with smartphone 708. External devices 682 include remote control / host devices, such as off-site client device 704, server 706, smartphone 708, or other devices.

[0134] A power source is required to power the motor 686 and to power other components 600. In some examples, the autonomous drone includes one or more batteries 608 as a power source for components 600 such as the motor 686. According to some examples, the battery 608 is removable. In some examples, the battery 608 is rechargeable, wherein one or more connectors 616 are connected to the battery 608 directly or via electrical or electronic components. In some examples, the power chip 640 manages the battery 608 by performing various functions, such as determining the charge of the battery 608, turning on or off recharging, providing capacitors, resistors, and / or inductors to the output of the battery 608, and the like. In some examples, the power chip 640 includes a power state 641, which indicates which of the components 600 of the autonomous drone are currently being powered. The power state 641 includes different power states 641, such as power state 1 642 to power state N 644. Different power states 641 provide power to different subsets of components 600, and thus consume different amounts of power and provide different levels of functionality for autonomous drones as discussed herein. Different power states 641 are implemented by providing power to different sets of power and communication connections 646. In some examples, components 600 are included as part of machine 1500. In some examples, one or more of components 600 are capable of operating, such as The real-time operating system is part of the processor 604 on the motherboard.

[0135] Figure 7 7 is a schematic diagram showing an autonomous drone system 700 according to some examples. In some examples, the autonomous drone 710 is an autonomous drone or a semi-autonomous drone. The autonomous drone 710 is configured to operate in a controlled manner by using Figure 6 The wireless connection 666 sends communications 712, 713 to a remote control / host device, such as an off-site client device 704, a server 706, a mobile phone or smartphone 708, or another device to communicate. The wireless network 702 is a cellular telephone network, such as an LTE network, an IEEE 802.11 network, In some examples, autonomous drone 710 communicates directly with a remote control / host device via communication 713, where communication 713 is sent using a communication protocol such as the communication protocol discussed for wireless network 702.

[0136] In the example, the autonomous drone 710 sends communications 712, 713 including data and / or commands or requests to another device, such as a smartphone 708. In some cases, communications between a remote control / host device, such as a smartphone 708, and the autonomous drone 710 may be via a wireless network 702. The wireless network 702 may include access to the Internet and / or the autonomous drone 710 may access the Internet via another connected device, such as a smartphone 708.

[0137] In some examples, server 706 provides a social networking service to enable content such as photos, videos, status updates, media content messages, etc. to be communicated directly from an autonomous drone 710 that may be in flight to a user such as a In some examples, server 706 is a messaging server system 108, and data captured by camera 650 of drone 710 is transmitted or otherwise communicated (which may be in near real time) to a remote control / host device such as a smartphone 708, to server 706, client device 704, or another device via wireless network 702. Autonomous drone 710 may communicate directly or via another device with Figure 2 Contact the drone management system 216.

[0138] One or more of the remote control / host devices, such as the smartphone 708, can assist in the processing of data, such as the data 630, by wirelessly receiving the data, processing the data, and then wirelessly sending the information back to the autonomous drone 710. For example, the smartphone 708 can receive an image from the autonomous drone 710 and determine that the image is a landmark, such as a museum, a restaurant, a park, a national monument, etc. The smartphone 708 can send back information used by the autonomous drone 710 to assist in the flight path associated with the landmark. The smartphone 708 can contact the drone management system 216 to perform functions for the autonomous drone 710. The autonomous drone 710 can contact the autonomous drone management system 216 by sending commands to the autonomous drone management system 216, such as storing data for a user, requesting a user or purchaser of the autonomous drone, etc.

[0139] In some examples, a remote control / host device such as a smartphone 708 includes an associated application that can be used by a user or device to control or send instructions to the autonomous drone 710, such as returning to the user, assuming a particular setting of flight, moving left, moving right, moving up or down, tilting, taking a set of photos, shutting down, etc. The associated application can provide real-time or near real-time images of the video being captured by the autonomous drone 710. In some examples, the associated application enables the user to configure the autonomous drone 710 by setting timeouts, conditions, and / or thresholds. In addition, the user can select configurations regarding the wireless connections 666 to indicate which wireless protocols should be used in which states of the autonomous drone.

[0140] In some examples, the remote control / host device acts as a router or passes messages or data packets to other devices directly or indirectly connected to the wireless network 702. For example, the smartphone 708 receives images from the autonomous drone 710 via communication 713. The smartphone 708 takes the image and sends it to the server 706 for posting on a social media website, which can be in near real time. The server 706 can host the autonomous drone management system 216. According to some examples, the remote control / host device such as the smartphone 708 controls the state of the autonomous drone 710 by sending instructions to the autonomous drone 710 via communications 713, 712.

[0141] Figure 8 An autonomous drone 710 is shown according to some examples. The autonomous drone 710 is shown from a bottom view of the autonomous drone 710. Figure 6 and Figure 8, the autonomous drone 710 includes propellers 690, a control knob 614 that may be on the top, an altitude detector 660, a battery 608, a photo camera 650, an indicator light 612, a connector 616, a center case 804, a navigation camera 651, and a flight button 806. The charging / transmission cable 802 is inserted into the connector 616. The center case 804 includes various components 600, such as a processor 604, a memory 606, a wireless connection 666, etc. In some examples, the autonomous drone 710 is plastic and is approximately six inches long and four inches wide. In some examples, the autonomous drone 710 is a quadrotor. The flight button 806 is a button 618 that, when pressed, indicates that the autonomous drone 710 should take off and execute the flight plan. According to some embodiments, the state 615 of the control knob 614 selects Fig. 9 960 of pre-programmed flight plans.

[0142] Fig. 9 A system 900 for fully autonomous drone flight is shown according to some examples. A navigation system 916 guides an autonomous drone 710 along a flight plan 910. According to some embodiments, the navigation system 916 is stored in the memory 606 and executed by the processor 604.

[0143] The navigation system 916 generates the flight plan 910 based on the preprogrammed flight plan 960. For example, the preprogrammed flight plan 960 is to fly a few feet from and above the user's head and complete a 360-degree video of the person. The navigation system 916 must determine the flight plan 910 that complies with the preprogrammed flight plan 960.

[0144] An example pre-programmed flight plan 960 includes a path to follow, such as to circle a user or object, follow a predetermined route around or near a user or object, where the path may be designed to capture video or photos, hover in front of the user, go to a destination and return, go to a destination and circle the destination to capture video, follow the user, etc. The pre-programmed flight plan 960 may include a target distance from a person associated with a face and a target altitude above the ground for the autonomous drone.

[0145] Sensor data 912 is data generated by sensors 648 and / or other components 600 such as wireless connections 666. Sensor data 912 also includes information about input / output devices 602, such as state 615 of control knob 614. Propulsion system commands 914 include determining power for motor 686 and position of actuator 638.

[0146] In some examples, navigation system 916 determines autonomous drone velocity 934 associated with time 936, direction 950, and location 952. The velocity of autonomous drone 710 is autonomous drone speed 934 and direction 950. In some examples, navigation system 916 enables autonomous drone 710 to be fully autonomous, where autonomous drone 710 takes off, flies, lands, and optionally captures images or video without additional input from an electronic control device external to autonomous drone 710.

[0147] In some examples, the autonomous drone speed 934 or velocity is determined based on images from a navigation camera 651 in a vertical position, and in some examples, also based on an altitude estimate using an altimeter 654 or another sensor 648. In some examples, the autonomous drone speed 934 or velocity is determined using dead reckoning using sensor data 912. Those skilled in the art will recognize that the autonomous drone speed 934 can be determined in other ways using sensor data 912. The wind speed is determined directly by a sensor such as a wind speed sensor 661, or based on a difference in the expected speed of the autonomous drone 710 compared to the actual speed of the autonomous drone 710. In some examples, the speed of the autonomous drone 710 is determined based on a difference in the positioning of the autonomous drone 710, which can be based on a GPS position generated by a GPS chip 668. In some examples, the positioning of the autonomous drone 710 is determined based on a wireless protocol such as IEEE 802.11, where messages are sent between the autonomous drone 710 and one or more hosts to determine the positioning of the autonomous drone 710. In some examples, the location of autonomous drone 710 is determined based on the location of a host computer such as smartphone 708 and information about the distance of autonomous drone 710 from smartphone 708, which can be coupled with the altitude above the ground to determine coordinates of the location of autonomous drone 710.

[0148] The altitude 927 is determined based on sensor data 912, such as from a navigation camera 651, an altitude detector 660, or another component 600. The altitude 927 is associated with a time 929. The autonomous drone speed 934 and the altitude 927 can be determined in different ways. The time 929 associated with the altitude 927 and the time 936 associated with the autonomous drone speed 934 are generated by a clock 663. The navigation system 916 includes a state 972 that indicates a goal or purpose of the autonomous drone 710 or the navigation system 916. Fig.10, the two states 972 of the navigation system 916 include “not flying” 1002 and “flying” 1006. In some examples, when the autonomous drone 710 is “flying” 1006, the autonomous drone 710 enters a reduced power state 641. For example, since the autonomous drone 710 does not need to receive commands, the wireless connection 666 can be turned off and the input / output device 602 is not used for navigation or image capture.

[0149] The facial recognition module 970 recognizes the face. The facial recognition module 970 is based on a neural network, feature recognition and placement, or other methods. In some examples, after recognizing the initial face 968, the facial recognition module 970 uploads the initial face 968 to a server such as the autonomous drone management system 216, which trains a neural network to recognize the face in the initial face 968 and downloads weights to the autonomous drone 710 to make it easier to recognize the initial face 968 in subsequent images.

[0150] The facial recognition module 970 determines an initial face 968. The initial face 968 may include not only a person's face, but also a person's body. The unlocking module 967 unlocks or releases the autonomous drone 710 based on the sensor data 912. In some examples, the unlocking module 967 receives an indication of the selection of the flight button 806, and in response, sends a command to the camera 650 to capture an image, which is processed by the facial recognition module 970. If the facial recognition module 970 determines that there is a suitable face in the image, then the unlocking module 967 unlocks the autonomous drone 710 for flight. The takeoff module 966 is called to start the flight. In some examples, the unlocking module 967 does not receive a command from an external electronic control indicating that the autonomous drone 710 should be unlocked. The unlocking module 967 unlocks the autonomous drone 710 based on the user interacting with the input / output device 602 of the autonomous drone 710.

[0151] The takeoff module 966 performs initial navigation for the autonomous drone 710. The takeoff module 966 sends propulsion system commands 914 to lift the autonomous drone 710 into flight according to the initial flight plan. The navigation flight module 962 determines the flight plan 910, which is based on a preprogrammed flight plan 960. In some examples, the preprogrammed flight plan 960 is based on the state 615 of the control knob 614.

[0152] The navigation flight module 962 navigates the autonomous drone 710 along the flight plan 910 based on receiving sensor data 912 and sending propulsion system commands 914 .

[0153] The landing module 964 lands the autonomous drone 710 after the navigation flight module 962 has completed the flight plan 910. The landing module 964 sends a propulsion system command 914 to land the autonomous drone 710. In some examples, the navigation system 916 including the unlock module 967, the takeoff module 966, the navigation flight module 962, and the landing module 964 operates without any additional instructions or commands from an external electronic device or a remote device. For example, the navigation system 916 receives a takeoff instruction from the person 1106, but does not receive multiple additional instructions or an additional instruction indicating a landing location, such as the person 1106 placing an open hand 1214 under the autonomous drone 710.

[0154] Fig.10 The state 1000 of an autonomous drone is shown according to some embodiments. The autonomous drone 710 starts in the state 972 of "not flying" 1002. The autonomous drone 710 may leave or be in another state 972 where the autonomous drone 710 is not flying. A "flight instruction" 1004 is received by the autonomous drone 710. In some examples, the "flight instruction" 1004 is received from a user of the autonomous drone 710 turning a control knob 614 or pressing a flight button 806. The autonomous drone 710 may perform checks to ensure that the autonomous drone 710 should fly by, for example, capturing an image and using a facial recognition module 970 to ensure that a suitable initial face 968 is within the captured image. In the state 972 of "flying" 1006, the navigation system 916 navigates the autonomous drone 710. According to some examples, the "flight" 1006 is broken down into flight phases utilizing a takeoff module 966, a navigation flight module 962, and a landing module 964. The autonomous drone 710 transitions back to the “not flying” 1002 state 972 at the end of the flight 1008 .

[0155] Fig.11 Unlocking 1100 an autonomous drone is shown in accordance with some embodiments. A person 1106 presses the fly button 806 and points the camera 650 at their face 1102. The facial recognition module 970 determines whether the face 1102 is suitable as an initial face 968, based on the distance 1104 of the face 1102 from the autonomous drone 710. The unlock module 967 unlocks the autonomous drone 710 and recognizes the combination of the face 1102 and the press of the fly button 806 as a "fly instruction" 1004, which transitions the autonomous drone 710 to a state 972 of "fly".

[0156] Fig.12 An autonomous drone 710 is shown flying according to some embodiments. Fig.12 yes Fig.111206, where the autonomous drone 710 is in a "flying" state 972. The autonomous drone 710 first follows the path of the navigation to flight plan 1210, where the takeoff module 966 navigates the autonomous drone 710. According to some examples, the navigate flight module 962 navigates the autonomous drone along the path of the actual flight path 1208 based on the flight plan 1206. The flight plan 1206 is based on the pre-programmed flight plan 960. The navigate flight module 962 keeps the camera 650 pointed at the person 1106, and in some examples, at the head or face 1002 of the person 1106.

[0157] The landing module 964 navigates the autonomous drone 710 along a path to navigate to land 1212. In some examples, the landing module 964 hovers in front of the person 1106 and waits for an indication that a hand or other object is placed under the autonomous drone 710. For example, the person 1106's arm may have initially been in the arm position 1202, but the person 1106 may have let their arm drop to their side. The person 1106 then moves their arm back to the arm position 1202, the arm moves 1204, the autonomous drone 710 detects the arm movement 1204 and descends to land on the open hand 1214 or the palm of the open hand 1214. For example, the altitude detector 660 may detect a large change in altitude or an object or arm approaching the bottom of the autonomous drone 710. In some embodiments, the autonomous drone 710 only receives movement of the person 1106's arm from the time the autonomous drone 710 takes off, with this detection of the arm movement 1204 acting as a command until the autonomous drone 710 lands on the open hand 1214. The entire flight of navigating to the flight plan 1210, the actual flight path 1208, and navigating to land 1212 is all performed without external commands from an electronic device, and in some examples, without external commands including commands from non-electronic devices (e.g., voice or gestures). In some examples, the flight can be initiated only from the input / output device 602 of the autonomous drone 710 operated by a person 1106.

[0158] Fig.13 Autonomous drone landing 1300 is shown according to some embodiments. Fig.13 Additional details of the path navigated to land 1212 are shown. The landing module 964 follows the path from Fig.111304. The person 1106 is standing on the ground 1304. The landing module 964 navigates the autonomous drone 710 to a hover 1306 position and waits to detect an open hand 1214 under the autonomous drone 710 using the altitude sensor / camera 1302. For example, the person 1106 moves their open hand 1214 under the autonomous drone 710. According to some examples, the altitude sensor / camera 1302 is an altitude detector 660 or a navigation camera 651.

[0159] Fig.14 A method 1400 for fully autonomous drone flight according to some examples is shown. The method 1400 begins at operation 1402, where an image is captured using an image capture device of an autonomous drone. For example, Fig.11 The autonomous drone 710 uses the photographic camera 650 to capture images.

[0160] The method 1400 continues at operation 1404 where the image is processed to identify a face. For example, the facial recognition module 970 processes the image to determine if a suitable initial face 968 is present.

[0161] Method 1400 continues at operation 1406 where navigation is performed according to a flight plan, where the flight plan is based on identifying faces in subsequent images captured by the image capture device. Fig.12 , the navigation flight module 962 navigates the autonomous drone 710 along the path of the actual flight path 1208 by capturing an image of the face 1002 with the photographic camera 650.

[0162] Method 1400 continues at operation 1408, where the autonomous drone is navigated to land. Fig.13 , the landing module 964 navigates the autonomous drone 710 along a path to land 1212, and hovers 1306 waiting for the person 1106 to raise their open hand 1214. After detecting the open hand 1214, the landing module 964 navigates the autonomous drone 710 to land on the open hand 1214, which can only reduce the power to the motor 686 so that the autonomous drone 710 descends into the open hand 1214.

[0163] Method 1400 may be performed by one or more devices or devices discussed herein, alone or in combination with each other. For example, autonomous drone 710, messaging system 100, smartphone 708, other devices or devices may perform method 1400, alone or in combination with each other. One or more of the operations of method 1400 may be optional. Method 1400 may include one or more additional operations. One or more operations of method 1400 may be performed in a different order.

[0164] Machine Architecture

[0165] Fig.15 The illustrative embodiment of the present invention is a diagrammatic representation of a machine 1500 within which instructions 1510 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1500 to perform any one or more of the methodologies discussed herein. For example, the instructions 1510 may cause the machine 1500 to perform any one or more of the methodologies described herein. The instructions 1510 convert a general purpose, unprogrammed machine 1500 into a specific machine 1500 that is programmed to perform the functions described and illustrated in the manner described. The machine 1500 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a network deployment, the machine 1500 may operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1500 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web device, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 1510 specifying actions to be taken by the machine 1500. In addition, although only a single machine 1500 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 1510 to perform any one or more of the methods discussed herein. For example, the machine 1500 may include any of the client device 102 or a plurality of server devices forming part of the messaging server system 108. In some examples, the machine 1500 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side and certain operations of the particular method or algorithm are performed on the client side.

[0166] The machine 1500 may include a processor 1504, a memory 1506, and an input / output I / O component 1502, which may be configured to communicate with each other via a bus 1540. In an example, the processor 1504 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), other processors, or any suitable combination thereof) may include, for example, a processor 1508 that executes instructions 1510 and a processor 1512. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that may execute instructions simultaneously. Although Fig.15 Multiple processors 1504 are shown, but the machine 1500 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0167] The memory 1506 includes a main memory 1514, a static memory 1516, and a storage unit 1518, which are all accessible by the processor 1504 via a bus 1540. The main memory 1506, the static memory 1516, and the storage unit 1518 store instructions 1510 that implement any one or more of the methods or functions described herein. The instructions 1510 may also reside, completely or partially, within the main memory 1514, within the static memory 1516, within the machine-readable medium 1520 within the storage unit 1518, within at least one of the processors 1504 (e.g., within a cache memory of a processor), or any suitable combination thereof during execution thereof by the machine 1500.

[0168] I / O components 1502 may include various components that receive input, provide output, generate output, send information, exchange information, capture measurements, etc. The specific I / O components 1502 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will be less likely to include such a touch input device. It should be appreciated that I / O components 1502 may include Fig.151502. In various examples, the I / O components 1502 may include a user output component 1526 and a user input component 1528. The user output component 1526 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 1528 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0169] In other examples, the I / O component 1502 may include a biometric component 1530, a motion component 1532, an environmental component 1534, or a position component 1536, as well as a wide range of other components. For example, the biometric component 1530 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1532 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0170] Environmental components 1534 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., an infrared sensor that detects nearby objects), gas sensors (e.g., a gas detection sensor for detecting concentrations of hazardous gases for safety purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0171] With respect to cameras, client device 102 may have a camera system including, for example, a front-facing camera on a front surface of client device 102 and a rear-facing camera on a rear surface of client device 102. The front-facing camera may, for example, be used to capture still images and videos of a user of client device 102 (e.g., a "selfie"), which may then be enhanced with the enhancement data (e.g., filters) described above. The rear-facing camera may, for example, be used to capture still images and videos in a more traditional camera mode, where the images are similarly enhanced with the enhancement data. In addition to the front-facing camera and the rear-facing camera, client device 102 may also include a 360° camera for capturing 360° photos and videos.

[0172] Additionally, the camera system of the client device 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of the client device 102. For example, these multi-camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0173] The location component 1536 includes a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure, from which the altitude can be obtained), an orientation sensor component (e.g., a magnetometer), etc.

[0174] A variety of technologies may be used to achieve communication. The I / O component 1502 also includes a communication component 1538 that is operable to couple the machine 1500 to the network 1522 or device 1524 via a corresponding coupling or connection. For example, the communication component 1538 may include a network interface component or other suitable device that interfaces with the network 1522. In other examples, the communication component 1538 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Parts (e.g. Low energy consumption), Components, and other communication components for providing communication via other modalities. Device 1524 can be any peripheral device (e.g., a peripheral device coupled via USB) from other machines or a variety of peripheral devices.

[0175] In addition, the communication component 1538 can detect an identifier or include a component operable to detect an identifier. For example, the communication component 1538 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as universal product codes (UPC) bar codes, multi-dimensional bar codes such as quick response (QR) codes, Aztec codes, data matrix, data symbols (Dataglyph), MaxiCode, PDF417, UltraCode, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be obtained via the communication component 1538, such as obtaining a location via Internet Protocol (IP) geolocation, ... and obtaining a location via Internet Protocol (IP) geolocation. Positioning is obtained through signal triangulation, positioning is obtained via detection of NFC beacon signals that can indicate a specific position, etc.

[0176] Various memories (e.g., main memory 1514, static memory 1516, and memory of processor 1504) and storage unit 1518 may store one or more sets of instructions and data structures (e.g., software) used by or implementing any one or more of the methods or functions described herein. When executed by processor 1504, these instructions (e.g., instructions 1510) cause various operations to implement the disclosed examples.

[0177] The instructions 1510 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 1538) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 1522. Similarly, the instructions 1510 may be sent or received via a coupling (e.g., a peer-to-peer coupling) to the device 1524 using a transmission medium.

[0178] Software Architecture

[0179] Fig.161600 is a block diagram illustrating a software architecture 1604 that may be installed on any one or more of the devices described herein. The software architecture 1604 is supported by hardware such as a machine 1602 including a processor 1620, a memory 1626, and an I / O component 1638. In this example, the software architecture 1604 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1604 includes layers such as an operating system 1612, a library 1610, a framework 1608, and an application 1606. In operation, the application 1606 invokes an API call 1650 through the software stack and receives a message 1652 in response to the API call 1650.

[0180] The operating system 1612 manages hardware resources and provides public services. The operating system 1612 includes, for example, a kernel 1614, services 1616, and drivers 1622. The kernel 1614 serves as an abstraction layer between the hardware and other software layers. For example, the kernel 1614 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. Services 1616 can provide other public services to other software layers. Drivers 1622 are responsible for controlling or interfacing with the underlying hardware. For example, drivers 1622 may include display drivers, camera drivers, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.

[0181] The libraries 1610 provide a common low-level infrastructure used by the applications 1606. The libraries 1610 may include a system library 1618 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1610 may include an API library 1624, such as a media library (e.g., a library for supporting presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for rendering in two dimensions (2D) and three dimensions (3D) in graphics content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1610 may also include various other libraries 1628 to provide many other APIs to the application 1606 .

[0182] The framework 1608 provides a common high-level infrastructure used by the applications 1606. For example, the framework 1608 provides various graphical user interface (GUI) functions, high-level resource management, and high-level positioning services. The framework 1608 can provide a wide range of other APIs that can be used by the applications 1606, some of which can be specific to a particular operating system or platform.

[0183] In an example, applications 1606 may include home applications 1636, contact applications 1630, browser applications 1632, book reader applications 1634, positioning applications 1642, media applications 1644, messaging applications 1646, game applications 1648, and a broad category of other applications such as third-party applications 1640. The autonomous drone management 1641 system manages autonomous drones as disclosed herein and in conjunction with the autonomous drone management system 216. Applications 1606 are programs that perform functions defined in the programs. Various programming languages ​​may be used to create one or more of the applications 1606 structured in various ways, such as object-oriented programming languages ​​(e.g., Objective-C, Java, or C++) or procedural programming languages ​​(e.g., C or assembly language). In a specific example, third-party applications 1640 (e.g., provided by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used for mobile operating systems, such as IOS TM ANDROID TM , Phone, or other mobile operating system running on the mobile software. In this example, the third-party application 1640 can activate the API call 1650 provided by the operating system 1612 to facilitate the functions described in this article.

[0184] Processing components

[0185] Now go to Fig.17 , a diagrammatic representation of a processing environment 1700 is shown, which includes a processor 1702, a processor 1706, and a processor 1708 (e.g., a GPU, a CPU, or a combination thereof).

[0186] Processor 1702 is shown coupled to power source 1704, and is shown to include modules (permanently configured or temporarily instantiated), namely, takeoff component 1710, navigation component 1712, and landing component 1714. Takeoff component 1710 controls takeoff of the autonomous drone. For example, according to some examples, takeoff component 1710 performs the functions described in conjunction with takeoff module 966, including responding to detection of gestures. Navigation component 1712 performs functions related to navigating the autonomous drone according to flight plan 910. Landing component 1714 manages landing of the autonomous drone and performs the functions disclosed in conjunction with landing module 964. Landing component 1714 detects hovering and detects when a hand or object is placed under the autonomous drone 710. According to some examples, processor 1702 is a dedicated processor 1702 designed specifically for autonomous drone 710. In some examples, processor 1702 is a processor having functions such as running a program such as a controller. The processor 1702 is part of the motherboard of the real-time operating system of the autonomous drone 710. The processor 1702 communicates with other processing circuit systems (such as component 600) included in the autonomous drone 710.

[0187] Glossary

[0188] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communication signals or other intangible media that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

[0189] "Client device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0190] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate for GSM evolution (EDGE) technology, including the third generation partnership project (3GPP) of 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0191] "Component" refers to a device, a physical entity, or logic with boundaries defined by function or subroutine calls, branch points, APIs, or other technologies that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be packaged functional hardware units designed for use with other components and can be part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., applications or application parts) to operate to perform certain operations described herein. Hardware components can also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include a dedicated circuit system or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It should be understood that it can be decided whether to mechanically implement the hardware component in a dedicated and permanently configured circuit system or in a temporarily configured (e.g., configured by software) circuit system for cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in some way or perform certain operations described herein. Considering an example in which a hardware component is temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each of the hardware components at any one time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be respectively configured as different special-purpose processors (e.g., including different hardware components) at different times. Software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time, and to constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Accordingly, the described hardware components can be considered to be coupled in communication.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components in the hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled to it in communication. Then, other hardware components can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described herein can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some of the operations in the operation of the method can be performed by one or more processors or components implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some of the operations in the operation can be performed by a group of computers (as an example of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of certain operations in the operation can be distributed between processors, not only can reside in a single machine, but also can be deployed across multiple machines. In some examples, a processor or a component implemented by a processor can be located in a single geographic location (e.g., in a home environment, an office environment, or a server cluster). In other examples, a processor or a component implemented by a processor can be distributed across multiple geographic locations.

[0192] "Computer-readable storage media" refers to both machine storage media and transmission media. Therefore, these terms include both storage devices / media and carrier / modulated data signals. The terms "machine-readable medium", "computer-readable medium" and "device-readable medium" mean the same thing and can be used interchangeably in this disclosure.

[0193] "Transient message" refers to a message that is accessible for a time-limited duration. Transient messages can be text, images, videos, etc. The access time for transient messages can be set by the message sender. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.

[0194] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices, such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage media", "device storage media", and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media", "computer storage media", and "device storage media" expressly exclude carrier waves, modulated data signals, and other such media (at least some of which are encompassed by the term "signal media").

[0195] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.

[0196] "Signal media" refers to any intangible medium that is capable of storing, encoding or carrying instructions executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" means a signal that has one or more of its various characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

Claims

1. An autonomous drone device comprising: processor; as well as a memory storing instructions that, when executed by the processor, configure the processor to perform operations comprising: capturing an image using an image capture device of the autonomous drone; processing the image to recognize a face; Navigate according to the flight plan; and The autonomous drone is navigated to land.

2. The device according to claim 1, wherein: The operations also include: After processing the image, taking off from the hand, and wherein navigating the autonomous drone to land further comprises: The autonomous drone is navigated to land on the hand.

3. The device according to claim 2, wherein: The image capture device is a first image capture device, the image is a first image, and wherein the operations further comprise: After causing the autonomous drone to take off from the hand, capturing a second image using a second image capture device; and The second image is processed to identify the hand.

4. The device according to claim 3, wherein: The first image capture device is mounted horizontally relative to an axis of a propeller of the autonomous drone, and the second image capture device is mounted vertically relative to the axis of the propeller and is oriented downward.

5. The device according to claim 1, wherein: Navigating the autonomous drone to land further comprises: causing the autonomous drone to hover in front of a person associated with the face; identifying an open hand of the person; and The autonomous drone is navigated to land on the open hand.

6. The device according to any one of claims 1 to 5, wherein: The operations also include: Video is captured while navigating the flight plan, and wherein navigating according to the flight plan further comprises directing the image capture device toward a person associated with the face.

7. The device according to any one of claims 1 to 5, wherein: The operations also include: Prior to said capturing said image, an indication of a selection of flight instructions is received.

8. The device according to claim 7, wherein: The operations also include: It is determined that no additional instructions are received from the remote device before navigating the autonomous drone to land.

9. The device according to claim 8, wherein: The flight instruction is a selection of a flight plan via an input device on the autonomous drone, wherein the input device is a knob or a flight button.

10. The apparatus according to any one of claims 1 to 5, wherein: The operations also include: The flight plan is determined based on a position of the face relative to the autonomous drone.

11. The apparatus according to any one of claims 1 to 5, wherein: The operations also include: After processing the image, take off in the space between the palm of the hand associated with the face and the face.

12. The apparatus according to any one of claims 1 to 5, wherein: The operations also include: The flight plan is determined based on a setting of user interface items accessible externally of the autonomous drone.

13. The apparatus according to claim 1, wherein: The flight plan is based on identifying the face or other object in subsequent images captured by the image capture device, or based on determining the positioning of the autonomous drone in space.

14. The apparatus according to any one of claims 1 to 5, wherein: The operations also include: In response to navigating according to the flight plan, all wireless connections to the autonomous drone are shut down.

15. The apparatus according to any one of claims 1 to 5, wherein: The operations also include: After processing the image, it is determined that no additional instructions are received before navigating the autonomous drone to land.

16. The apparatus according to any one of claims 1 to 5, wherein: The flight plan indicates a target distance to a person associated with the face and a target altitude above the ground for the autonomous drone, and wherein the operations further include: recognizing the face using a neural network; uploading the image of the face to a server; and Weights are downloaded from the server for the neural network to recognize the face.

17. A method performed on a device of an autonomous drone, the method comprising: capturing an image using an image capture device of the autonomous drone; processing the image to recognize a face; navigating according to a flight plan, wherein the flight plan is based on recognizing the face in subsequent images captured by the image capture device; and The autonomous drone is navigated to land.

18. The method according to claim 17, further comprising: receiving an indication of a selection of flight instructions prior to capturing the image; as well as It is determined that no additional instructions are received from the remote device before navigating the autonomous drone to land.

19. A non-transitory computer-readable storage medium comprising instructions that, when executed by at least one processor of a device of an autonomous drone, cause the at least one processor to perform operations comprising: capturing an image using an image capture device of the autonomous drone; processing the image to recognize a face; navigating according to a flight plan, wherein the flight plan is based on recognizing the face in subsequent images captured by the image capture device; and The autonomous drone is navigated to land.

20. The non-transitory computer readable storage medium of claim 19, wherein: The operations also include: Prior to capturing the image, receiving an indication of a selection of flight instructions; and Determining that no additional instructions are received before navigating the autonomous drone to land.