WO2017167230A1 - 飞行标签的获取方法和终端及服务器 - Google Patents

飞行标签的获取方法和终端及服务器 Download PDF

Info

Publication number
WO2017167230A1
WO2017167230A1 PCT/CN2017/078805 CN2017078805W WO2017167230A1 WO 2017167230 A1 WO2017167230 A1 WO 2017167230A1 CN 2017078805 W CN2017078805 W CN 2017078805W WO 2017167230 A1 WO2017167230 A1 WO 2017167230A1
Authority
WO
WIPO (PCT)
Prior art keywords
drone
geographic location
takeoff
server
take
Prior art date
Application number
PCT/CN2017/078805
Other languages
English (en)
French (fr)
Inventor
黎凯锋
魏嘉
李家伦
张向昕
黄秋丽
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2017167230A1 publication Critical patent/WO2017167230A1/zh
Priority to US15/991,872 priority Critical patent/US10957205B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0004—Transmission of traffic-related information to or from an aircraft
    • G08G5/0013—Transmission of traffic-related information to or from an aircraft with a ground station
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01S—RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S5/00—Position-fixing by co-ordinating two or more direction or position line determinations; Position-fixing by co-ordinating two or more distance determinations
    • G01S5/0009—Transmission of position information to remote stations
    • G01S5/0018—Transmission from mobile station to base station
    • G01S5/0027—Transmission from mobile station to base station of actual mobile position, i.e. position determined on mobile
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/29—Geographical information databases
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0043—Traffic management of multiple aircrafts from the ground
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
    • G08G5/0047—Navigation or guidance aids for a single aircraft
    • G08G5/0069—Navigation or guidance aids for a single aircraft specially adapted for an unmanned aircraft
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]

Definitions

  • the present application relates to the field of computers, and in particular to a method and a terminal for acquiring a flight tag and a server.
  • the embodiment of the present application provides a method for acquiring a flight tag, a terminal, and a server, so as to at least solve the technical problem that the flight tag of the UAV cannot be acquired by using the prior art.
  • a method for acquiring a flight tag including: acquiring a take-off geographic location of the first drone when the first drone takes off; and taking off the first drone The geographical location is sent to the server; the flight label returned by the server is obtained, wherein the flight label is used to indicate whether the first drone is the first drone that takes off on the take-off geographical position of the first drone.
  • a method for acquiring a flight tag including: Receiving, by the client, a take-off geographic location of the first drone when the first drone takes off, wherein the client runs on the control terminal, and controls the take-off of the first drone; Whether there is a take-off geographic location in the stored take-off geographic location that is the same as the take-off geographic location of the first drone; if present, sending a first flight tag to the client, wherein the first flight tag is used to indicate The first drone is not the first drone to take off in the take-off position of the first drone; if not, the second flight tag is sent to the client, wherein the second flight tag is used The first drone is the first drone that is indicated to be taken off in the take-off position of the first drone described above.
  • a acquiring terminal of a flight tag including: a first acquiring unit, configured to acquire a take-off geographic location of the first drone when the first drone takes off; a first sending unit, configured to send the take-off geographic location of the first drone to the server, and a second acquiring unit, configured to acquire a flight tag returned by the server, where the flight tag is used to indicate that the first Whether the first drone above is the first drone to take off in the geographical position of the man-machine.
  • a server for acquiring a flight tag comprising: a receiving unit, configured to receive a takeoff geography of the first drone when the first drone is taken by the client a location, wherein the client runs on the control terminal, and is used to control the takeoff of the first drone; and the determining unit is configured to determine whether the stored first flight location has the same Taking off a take-off geographic location having the same geographical position; the first sending unit is configured to send a first flight label to the client when there is a take-off geographic location that is the same as the take-off geographic location of the first drone, wherein the first a flight tag for indicating that the first drone is not the first take-off drone in the take-off geographical position of the first drone; the second transmitting unit is configured to not exist with the first drone Sending a second flight tag to the client when the takeoff geographical position is the same, wherein the second flight tag is used to indicate the first The take-off of the first man-machine location UAV
  • the client running on the control terminal acquires the takeoff geographic location of the first drone when the first drone takes off, and sends the takeoff geographic location to the server, and then obtains the returned flight from the server.
  • the tag wherein the flight tag is used to indicate whether the first drone is the first take-off drone in the takeoff geographic location of the first drone. Sending the takeoff geographic location acquired when the drone takes off to the server, so that the server can take advantage of the takeoff location of the acquired drone.
  • the purpose of returning the flight label corresponding to the drone to the control terminal is to solve the technical problem that the flight label of the drone cannot be obtained by the prior art. To achieve the effect of sharing the flight label of the above drone on the client's community space.
  • FIG. 1 is a schematic diagram of an application environment of an optional method for acquiring a flight tag according to an embodiment of the present application
  • FIG. 2 is a flow chart of an optional method for acquiring a flight tag according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of an optional method for acquiring a flight tag according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of another optional method for acquiring a flight tag according to an embodiment of the present application.
  • FIG. 5 is a flowchart of another optional method for acquiring a flight tag according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of still another optional method for acquiring a flight tag according to an embodiment of the present application.
  • FIG. 7 is a flow chart of still another optional method for acquiring a flight tag according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of an optional flight tag acquisition terminal according to an embodiment of the present application.
  • FIG. 9 is a schematic diagram of an optional flight tag acquisition server in accordance with an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of an optional flight tag acquisition terminal according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of an optional flight tag acquisition server according to an embodiment of the present application.
  • an embodiment of a method for acquiring a flight tag is provided.
  • the method for acquiring the flight tag may be, but is not limited to, being applied to an application environment as shown in FIG.
  • the takeoff location of the first drone when the aircraft (such as the drone 102 shown in FIG. 1) takes off sends the takeoff geographic location to the server 106, and then retrieves the returned flight tag from the server 106, wherein the flight tag is used for Indicates whether the first drone (such as the drone 102 shown in FIG. 1) is the first take-off drone in the takeoff geographic position of the first drone (such as the drone 102 shown in FIG. 1).
  • a database common to the drone is established at the server, so that the database can be used to implement the effect of returning the flight label of the drone to the control terminal, thereby achieving The purpose of sharing the flight labels of the aforementioned drones in the community space.
  • the foregoing control terminal may include, but is not limited to, at least one of the following: a mobile terminal, a wristband, and a handle.
  • the mobile terminal may include, but is not limited to, at least one of the following: a mobile phone, a tablet computer, and a notebook computer. The above is only an example, and the embodiment does not limit this.
  • the foregoing terminal may be, but is not limited to, interacting with a server through a network
  • the foregoing network may include, but is not limited to, at least one of the following: a wide area network, a metropolitan area network, and a local area network.
  • the above terminal may be, but is not limited to, data interaction with the drone through a wireless connection.
  • the wireless connection may include, but is not limited to, at least one of the following: wireless Bluetooth, wireless WIFI. The above is only an example, and the embodiment does not limit this.
  • a method for acquiring a flight tag includes:
  • S204 Send the takeoff geographic location of the first drone to the server;
  • the method for acquiring the flight tag may be, but is not limited to, being applied to a process of acquiring a flight tag of the drone on a client running on the control terminal, where the client running on the control terminal The end is used to control the takeoff of the drone.
  • the client running the terminal displays the flight label of the drone returned by the server.
  • the flight label returned by the server includes: flight label_1 and flight label_2.
  • the flight tag can be "first occupied (first occupied)", "passed over”. The above is only an example, and is not limited in this embodiment.
  • the client running on the control terminal acquires the takeoff geographic location of the first drone when the first drone takes off, and sends the takeoff geographic location to the server, and then from the server. Obtaining the returned flight tag, wherein the flight tag is used to indicate whether the first drone is the first take-off drone on the takeoff geographic location of the first drone.
  • the method further includes: determining, by the server, whether the stored takeoff geographic location exists The takeoff geographic location is the same as the takeoff geographic location of the received first drone; and the corresponding flight tag is sent according to the judgment result.
  • the flight tag may include, but is not limited to, at least one of the following: for indicating that the first drone is not the first frame in the takeoff geographical position of the first drone The first flight tag of the flying drone is used to indicate that the first drone is the second flight tag of the first drone in the takeoff geographic location of the first drone.
  • the flight tag may be, but is not limited to, indicating at least one of: a geographic name corresponding to a take-off geographic location of the first drone, and a take-off when the first drone takes off. Date, the departure time of the first drone when taking off.
  • the first drone is controlled by a client running on the control terminal (user name: ID_01), and after the first drone has passed multiple flights, the obtained flight tag displayed on the client can be as shown in FIG.
  • the location of the first flight label (marked by the “First Place”) is as follows: “Eiffel Tower (15.09.24)”, “Madrid (15.07.17)”, “Hokkaido, Japan (15.06.04) "” and “Maldives Paradise Island (15.04.30)”;
  • the second flight label (marked by “Sweeping") includes the following geographical locations: “French Arc de Triomphe (15.09.23)", “Barcelona, Spain (15.07. 19)", “Tokyo, Japan (15.06.06)”.
  • the takeoff geographic location of the first drone may include, but is not limited to, one of the following: 1) a geographic location of the first drone when the first drone takes off; 2) The geographic location of the terminal is controlled when the first drone takes off.
  • the take-off geographic location of the first drone is the geographic location of the first drone when the first drone takes off
  • the take-off geographic location may be acquired by at least one of the following methods: 1) controlling the terminal Obtaining a geographic location of the first drone collected by the first drone when the first drone takes off; 2) obtaining, by detecting, the geographic location of the first drone when the first drone takes off.
  • sending the takeoff geographic location of the first drone to the server includes one of the following:
  • the take-off geographic location of the first drone is sent to the server in real time, so that the server realizes real-time comparison, real-time.
  • Feedback so that the client running on the control terminal can obtain the flight tag matched by the first drone in time, so that the community space of the client can update and display the obtained flight tag in real time.
  • the data recorded in the server database can be updated in real time, thereby ensuring the accuracy and update efficiency of the database, and the multi-user simultaneously calls the data in the database to realize the feasibility of multi-user interaction.
  • the take-off geographical position of the first drone can be sent to the server, so that after the interval time, the acquisition will be acquired.
  • the first drone's takeoff location is synchronized to the server. Splitting the synchronization process of sending the takeoff geographic location of the first drone to the server, that is, sending the multiple takeoff geographic locations acquired in a certain time interval to the server together, reducing the number of transmissions, thereby improving the server The effect of sending the transmission efficiency of the takeoff location.
  • sending the takeoff geographic location of the first drone to the server includes one of the following:
  • the first drone's take-off geographic location may be sent to the server in response to the obtained sending command, or the acquired first drone may be sent at the preset sending moment.
  • the takeoff location gives the server.
  • the sending command may be, but is not limited to, a sending command triggered by a user through an input operation, where the input operation may include, but is not limited to, at least one of: clicking a predetermined trigger button, and collecting a predetermined order. Voice, get a predetermined somatosensory gesture.
  • the preset transmission time may include, but is not limited to, at least one of the following: a time when the predetermined condition is met, and a preset period end time.
  • the predetermined condition may be detecting a preset network signal, such as a 4G signal, a WIFI signal, or the like.
  • the following example is used to illustrate, as shown in FIG. 5 , in this example, taking the take-off geographic location of the first drone as an example of the geographic location of the first drone when the first drone takes off.
  • the client 504 running on the control terminal acquires the geographic location of the first drone collected by the first drone 502 when the first drone takes off;
  • the client 504 running on the control terminal sends the takeoff geographic location of the first drone to the server 506;
  • the server 506 determines whether there is a take-off geographic location that is the same as the take-off geographic location of the received first drone in the stored take-off geographic location; and obtains a corresponding flight tag according to the determination result;
  • the server 506 returns a flight tag to the client 504 running on the control terminal.
  • the client 504 running on the control terminal displays the flight tag.
  • the takeoff geographic location acquired when the drone takes off is sent to the server, so that the server establishes a common database of the drone on the server by using the acquired geographical position of the unmanned aerial vehicle. Further, the database is used to establish an interaction between the client running on the control terminal and the server, so as to realize the take-off geographic location of the shared drone, thereby returning the drone corresponding to the control terminal according to the take-off geographic location of the drone.
  • the purpose of the flight tag is to achieve the effect of sharing the flight label of the above-mentioned drone in the community space of the client to solve the technical problem that the flight tag of the drone cannot be obtained by the prior art.
  • sending the takeoff geographic location of the first drone to the server includes one of the following:
  • the sending timing of transmitting the takeoff geographic location of the first drone to the server may include: when the first drone takes off, or after the first drone takes off. That is to say, the take-off geographic location can be synchronously sent to the server in real time, so that the server can realize real-time comparison and real-time feedback, thereby ensuring that the client running on the control terminal can acquire the flight label matched for the first drone in time, so that The community space of the client can update and display the obtained flight tags in real time.
  • the synchronous sending process can also be split, and multiple takeoff geographic locations acquired within a certain time interval are stored first, and then sent to the server together to reduce the number of transmissions. Improve the effect of sending the sending efficiency of the takeoff location to the server.
  • the take-off geographic location of the first drone may be saved on the control terminal first, or may be stored in other third-party storage media. This embodiment does not limit this.
  • the take-off geographic location of the first drone is sent, so that different sending occasions are selected according to different application scenarios to ensure Get timely and accurate flight tags corresponding to the takeoff location.
  • sending the takeoff geographic location of the first drone to the server includes one of the following:
  • the takeoff geographic location of the first drone may be sent to the server in response to the obtained sending instruction.
  • the sending command may be, but is not limited to, a sending command triggered by the user through an input operation, where the input operation may include, but is not limited to, at least one of: clicking a predetermined trigger button, acquiring a predetermined voice, and acquiring a predetermined somatosensory gesture.
  • the control interface of the client running on the control terminal to the first drone can be controlled as shown in FIG. 6, and the first drone can be controlled to perform different "return to landing", "emergency hover” and “follow mode”. Operate, or control the first drone to move in the direction indicated by the arrow.
  • the "control button" is used to trigger a sending instruction to send the first drone's takeoff geographic location to the server.
  • the acquired takeoff geographic location of the first drone may also be sent to the server at a preset sending moment.
  • the preset transmission time may include, but is not limited to, at least one of the following: a time when the predetermined condition is met, and a preset period end time.
  • the predetermined condition may be detecting a preset network signal, such as a 4G signal, a WIFI signal, or the like.
  • control terminal is triggered to send the takeoff geographic location of the first drone to the server in different manners, thereby diversifying operations, facilitating user operations, and improving the user experience.
  • obtaining the take-off geographic location of the first drone when the first drone takes off includes one of the following:
  • obtaining the geographic location of the first drone when the first drone takes off may pass, but is not limited to, at least one of the following manners: 1) controlling the terminal to acquire the first drone to take off The geographic location of the first drone collected by the first drone; 2) the control terminal acquires the geographic location of the first drone when the first drone takes off.
  • the client running on the control terminal can acquire the take-off geographic location of the first drone collected by the first drone during take-off, and can also obtain the first drone by self-detection.
  • the takeoff location of the first drone at the time of takeoff.
  • the take-off geographic location of the first drone is obtained in different ways to meet the actual needs of different users, thereby ensuring the accuracy of the obtained flight tags.
  • S1 displaying a flight tag in a client running on the control terminal, wherein the client controls the takeoff of the first drone, and the flight tag is further used to indicate at least one of: a departure geography with the first drone The geographical name corresponding to the location, the departure date of the first drone when it takes off, and the departure time of the first drone when it takes off.
  • the flight tag may include, but is not limited to, at least one of the following: a drone for indicating that the first drone is not the first takeoff in the takeoff geographic position of the first drone a first flight tag for indicating that the first drone is the second flight tag of the first drone in the takeoff geographic position of the first drone.
  • the above flight tag may also be, but is not limited to, indicating at least one of: a geographic name (eg, a place name) corresponding to a takeoff geographic location (eg, location coordinates) of the first drone, the first drone The departure date at the time of takeoff and the departure time of the first drone when taking off.
  • the flight tag acquired by the first drone after multiple flights can be displayed.
  • the first flight tag (with "first”
  • the location of the take-off included under the logo is as follows: “Eiffel Tower (15.09.24)”, “Madrid (15.07.17)”, “Hokkaido (15.06.04)” and “Paradise Island Maldives (15.04.30))
  • the second flight label (marked by the "Sweep” logo) includes the following locations: "Arc de Triomphe (15.09.23)", “Barcelona Barcelona (15.07.19)", “Tokyo, Japan (15.06.06) ".
  • the obtained flight tag is displayed by the client running on the control terminal, so that different users can share the flight tag in the community space, so that different users share different flights through the flight tag.
  • the client running on the control terminal so that different users can share the flight tag in the community space, so that different users share different flights through the flight tag.
  • the method further includes:
  • the server receives the takeoff geographic location
  • S2 The server determines whether there is a take-off geographic location in the taken-off geographical location that is the same as the take-off geographic location of the first drone;
  • the server sends a first flight tag, wherein the first flight tag is used to indicate that the first drone is not the first take-off drone in the takeoff geographic location of the first drone, and the flight tag includes : the first flight tag;
  • the server sends a second flight tag, wherein the second flight tag is used to indicate that the first drone is the first drone to take off at the takeoff geographic location of the first drone, the flight tag Includes: second flight tag.
  • the server determines whether there is a take-off of the first drone in the database established in the server by comparing the stored takeoff geographic location with the takeoff geographic location of the first drone. The geographical location of the same takeoff location, so that different flight labels are sent according to the judgment result.
  • the client running on the control terminal obtains an accurate flight tag.
  • determining whether there is a take-off geographic location in the stored take-off geographic location that is the same as the take-off geographic location of the first drone includes at least one of the following:
  • the judgment principle of the same takeoff geographic location may include, but is not limited to, at least one of the following: the location information is completely consistent, and the area indication information (part of the location information) for indicating the area is consistent.
  • sending the first flight tag to the client includes: acquiring a geographic name corresponding to a takeoff geographic location of the first drone, transmitting a first flight tag including at least a geographic name; and transmitting to the client
  • Sending the second flight tag includes: acquiring a geographic name corresponding to the takeoff geographic location of the first drone, storing a correspondence between the takeoff geographic location of the first drone and the acquired geographic name, and transmitting the at least the geographic name Two flight labels.
  • the foregoing server may, but is not limited to, adjust a taken-off geographic location stored in the server database according to the acquired geographic location of the drone. Specifically, after obtaining the second flight tag for indicating that the first drone is the first take-off of the drone in the take-off geographical position of the first drone, acquiring the take-off with the first drone The geographic name corresponding to the geographical location, and the corresponding relationship between the takeoff geographic location of the first drone and the acquired geographic name is stored, so as to achieve the effect of adding a new takeoff geographic location in the database.
  • the take-off geographic location acquired when the drone takes off is sent to the server, so that the server establishes a common database of the drone at the server by using the taken-off geographic location of the obtained drone. Further, the database is used to establish an interaction between the client running on the control terminal and the server, so as to realize the take-off geographic location of the shared drone, thereby returning the drone corresponding to the control terminal according to the take-off geographic location of the drone.
  • the purpose of the flight tag is to achieve the effect of sharing the flight label of the above-mentioned drone on the client's community space.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a plurality of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the apparatus described in the various embodiments of the present application.
  • a method for acquiring a flight tag is further provided. As shown in FIG. 7, the method includes:
  • S702 Receive a departure geographic location of the first drone that is sent by the client when the first drone takes off, where the client runs on the control terminal, and is used to control the takeoff of the first drone;
  • the method for acquiring the flight tag may be, but is not limited to, being applied to a process of acquiring a flight tag of the drone on a client running on the control terminal, where the client running on the control terminal The end is used to control the takeoff of the drone.
  • the server receives the take-off geographic location of the first drone that is sent by the client when the first drone takes off, it is determined whether the stored take-off geographic location has the same geographical position as the take-off of the first drone. Taking off the geographical location, and then transmitting different first flight tags or second flight tags to the client according to different judgment results, wherein the client runs on the control terminal for controlling the takeoff of the first drone. As shown in FIG.
  • the flight label of the drone returned by the server is displayed on the client (user name: ID_01) running on the control terminal.
  • the flight label returned by the server includes: flight label_1 and flight label_2.
  • the flight tag can be "first" or "passed”. The above is just an example, and nothing is done in this embodiment. limited.
  • the server receives a takeoff geographic location of the first drone that is sent by the client when the first drone takes off, wherein the client runs on the control terminal for the first Controlling the take-off of the drone; determining whether there is a take-off geographic location in the stored take-off geographic location that is the same as the take-off geographic location of the first drone; if present, transmitting a first flight tag to the client, where a flight tag is used to indicate that the first drone is not the first take-off drone in the take-off geographical position of the first drone; if not, the second flight tag is sent to the client, wherein the second flight The tag is used to indicate that the first drone is the first take-off drone in the take-off geographical position of the first drone, wherein the flight tag is used to indicate that the first drone is first in the take-off geographical position Whether the man-machine is the first drone to take off.
  • the server obtains the corresponding flight tag through the acquired take-off geographic location, and sends the flight tag to the client, so that the server uses the acquired departure location of the drone to establish a common database of the drone at the server, and further,
  • the database is used to establish an interaction between the client running on the control terminal and the server to realize the take-off geographic location of the shared drone, thereby returning the flight label corresponding to the drone to the control terminal according to the take-off geographic location of the drone.
  • the purpose is to achieve the effect of sharing the flight labels of the above drones on the client's community space.
  • the flight tag may include, but is not limited to, at least one of the following: for indicating that the first drone is not the first drone of the drone in the takeoff geographic position of the first drone
  • the first flight tag is configured to indicate that the first drone is the second flight tag of the first drone in the takeoff geographic location of the first drone.
  • the flight tag may be, but is not limited to, indicating at least one of: a geographic name corresponding to a take-off geographic location of the first drone, and a take-off when the first drone takes off. Date, the departure time of the first drone when taking off.
  • the first drone is controlled by a client running on the control terminal (user name: ID_01), and after the first drone has passed multiple flights, the obtained flight tag displayed on the client can be as shown in FIG.
  • the location of the first flight label (marked by the “First Place”) is as follows: “Eiffel Tower (15.09.24)”, “Madrid (15.07.17)”, “Hokkaido, Japan (15.06.04) "” and “Maldives Paradise Island (15.04.30)”;
  • the second flight label (marked by “Sweeping") includes the following geographical locations: “French Arc de Triomphe (15.09.23)", “Barcelona, Spain (15.07. 19)", “Tokyo, Japan (15.06.06)”.
  • the takeoff geographic location of the first drone may include but is not limited to In one of the following: 1) the geographic location of the first drone when the first drone takes off; 2) the geographic location of the control terminal when the first drone takes off.
  • the take-off geographic location of the first drone is the geographic location of the first drone when the first drone takes off
  • the take-off geographic location may be acquired by at least one of the following methods: 1) controlling the terminal Obtaining a geographic location of the first drone collected by the first drone when the first drone takes off; 2) obtaining, by detecting, the geographic location of the first drone when the first drone takes off.
  • determining whether there is a take-off geographic location in the stored take-off geographic location that is the same as the take-off geographic location of the first drone includes at least one of the following:
  • the judgment principle of the same takeoff geographic location may include, but is not limited to, at least one of the following: the location information is completely consistent, and the area indication information (part of the location information) for indicating the area is consistent.
  • sending the first flight tag to the client includes: acquiring a geographic name corresponding to a takeoff geographic location of the first drone, transmitting a first flight tag including at least a geographic name; and transmitting to the client
  • Sending the second flight tag includes: acquiring a geographic name corresponding to the takeoff geographic location of the first drone, storing a correspondence between the takeoff geographic location of the first drone and the acquired geographic name, and transmitting the at least the geographic name Two flight labels.
  • the foregoing server may, but is not limited to, adjust a taken-off geographic location stored in the server database according to the acquired geographic location of the drone. Specifically, after obtaining the second flight tag for indicating that the first drone is the first take-off of the drone in the take-off geographical position of the first drone, acquiring the take-off with the first drone The geographic name corresponding to the geographical location, and the corresponding relationship between the takeoff geographic location of the first drone and the acquired geographic name is stored, so as to achieve the effect of adding a new takeoff geographic location in the database.
  • the server obtains the corresponding location by acquiring the takeoff geographic location. Flying the tag and sending the flight tag to the client, so that the server utilizes the take-off geographic location of the acquired drone to establish a common database of the drone at the server, and further, utilizes the database to run the client on the control terminal with
  • the interaction between the servers is established to realize the take-off geographic location of the shared drone, thereby achieving the purpose of returning the flight label corresponding to the drone according to the take-off geographic location of the drone, thereby realizing sharing in the community space of the client.
  • the effect of the flight label of the above drone is established to realize the take-off geographic location of the shared drone, thereby achieving the purpose of returning the flight label corresponding to the drone according to the take-off geographic location of the drone, thereby realizing sharing in the community space of the client.
  • determining whether there is a take-off geographic location in the stored take-off geographic location that is the same as the take-off geographic location of the first drone includes at least one of the following:
  • the judgment principle of the same takeoff geographic location may include, but is not limited to, at least one of the following: the location information is completely consistent, and the area indication information (part of the location information) for indicating the area is consistent.
  • Sending the first flight tag to the client includes: acquiring a geographic name corresponding to the takeoff geographic location of the first drone, and transmitting a first flight tag including at least the geographic name;
  • Sending the second flight label to the client includes: acquiring a geographic name corresponding to the takeoff geographic location of the first drone, storing a correspondence between the takeoff geographic location of the first drone and the acquired geographic name, and transmitting at least A second flight tag that includes a geographic name.
  • the foregoing server may, but is not limited to, adjust a taken-off geographic location stored in the server database according to the acquired geographic location of the drone. Specifically, after obtaining the second flight tag for indicating that the first drone is the first take-off of the drone in the take-off geographical position of the first drone, acquiring the take-off with the first drone The geographic name corresponding to the geographical location, and the corresponding relationship between the takeoff geographic location of the first drone and the acquired geographic name is stored, so as to achieve the effect of adding a new takeoff geographic location in the database.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a plurality of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the apparatus described in the various embodiments of the present application.
  • a flight terminal acquisition terminal including:
  • a first obtaining unit 802 configured to acquire a take-off geographic location of the first drone when the first drone takes off;
  • the first sending unit 804 is configured to send the takeoff geographic location of the first drone to the server;
  • the second obtaining unit 806 is configured to acquire a flight tag returned by the server, wherein the flight tag is used to indicate whether the first drone is the first drone to take off at the take-off geographic location of the first drone.
  • the acquiring terminal of the flight tag may be, but is not limited to, being applied to a process of acquiring a flight tag of the drone on a client running on the control terminal, wherein the client running on the control terminal The end is used to control the takeoff of the drone.
  • the client running the terminal displays the flight label of the drone returned by the server.
  • the flight label returned by the server includes: flight label_1 and flight label_2.
  • the flight tag can be "first" or "passed". The above is only an example, and is not limited in this embodiment.
  • the client running on the control terminal acquires the takeoff geographic location of the first drone when the first drone takes off, and sends the takeoff geographic location to the server, and then from the server. Obtaining the returned flight tag, wherein the flight tag is used to indicate whether the first drone is the first take-off drone on the takeoff geographic location of the first drone.
  • the method further includes: determining, by the server, whether the stored takeoff geographic location exists The takeoff geographic location is the same as the takeoff geographic location of the received first drone; and the corresponding flight tag is sent according to the judgment result.
  • the flight tag may include, but is not limited to, at least one of the following: a first flight tag for indicating that the first drone is not the first takeoff in the takeoff geographic position of the first drone, for indicating The first drone is the second flight tag of the first take-off drone in the take-off position of the first drone.
  • the flight tag may be, but is not limited to, indicating at least one of: a geographic name corresponding to a take-off geographic location of the first drone, and a take-off when the first drone takes off. Date, the departure time of the first drone when taking off.
  • the first drone is controlled by a client running on the control terminal (user name: ID_01), and after the first drone has passed multiple flights, the obtained flight tag displayed on the client can be as shown in FIG.
  • the location of the first flight label (marked by the “First Place”) is as follows: “Eiffel Tower (15.09.24)”, “Madrid (15.07.17)”, “Hokkaido, Japan (15.06.04) "” and “Maldives Paradise Island (15.04.30)”;
  • the second flight label (marked by “Sweeping") includes the following geographical locations: “French Arc de Triomphe (15.09.23)", “Barcelona, Spain (15.07. 19)", “Tokyo, Japan (15.06.06)”.
  • the takeoff geographic location of the first drone may include, but is not limited to, one of the following: 1) a geographic location of the first drone when the first drone takes off; 2) The geographic location of the terminal is controlled when the first drone takes off.
  • the take-off geographical position of the first drone is at least one of the following manners when the first drone is in the geographical position of the first drone when the first drone takes off Acquiring the take-off geographic location: 1) controlling the terminal to obtain the geographic location of the first drone collected by the first drone when the first drone takes off; 2) controlling the terminal to obtain the first drone when the first drone takes off The location of a drone.
  • sending the takeoff geographic location of the first drone to the server includes one of the following:
  • the take-off geographic location of the first drone is sent to the server in real time, so that the server realizes real-time comparison, real-time.
  • Feedback so that the client running on the control terminal can obtain the flight tag matched by the first drone in time, so that the community space of the client can update and display the obtained flight tag in real time.
  • the data recorded in the server database can be updated in real time, thereby ensuring the accuracy and update efficiency of the database, and the multi-user simultaneously calls the data in the database to realize the feasibility of multi-user interaction.
  • the take-off geographical position of the first drone can be sent to the server, so that after the interval time, the acquisition will be acquired.
  • the first drone's takeoff location is synchronized to the server. Splitting the synchronization process of sending the takeoff geographic location of the first drone to the server, that is, sending the multiple takeoff geographic locations acquired in a certain time interval to the server together, reducing the number of transmissions, thereby improving the server The effect of sending the transmission efficiency of the takeoff location.
  • sending the takeoff geographic location of the first drone to the server includes one of the following:
  • the first drone's take-off geographic location may be sent to the server in response to the obtained sending command, or the acquired first drone may be sent at the preset sending moment.
  • the takeoff location gives the server.
  • the sending command may be, but is not limited to, a sending command triggered by a user through an input operation, where the input operation may include, but is not limited to, at least one of: clicking a predetermined trigger button, and collecting a predetermined order. Voice, get a predetermined somatosensory gesture.
  • the preset transmission time may include, but is not limited to, at least one of the following: a time when the predetermined condition is met, and a preset period end time.
  • the predetermined condition may be detecting a preset network signal, such as a 4G signal, a WIFI signal, or the like.
  • the take-off geographic location of the first drone is taken as an example of the geographic location of the first drone when the first drone takes off.
  • the client 504 running on the control terminal acquires the geographic location of the first drone collected by the first drone 502 when the first drone takes off;
  • the client 504 running on the control terminal sends the takeoff geographic location of the first drone to the server.
  • the server 506 determines whether there is a take-off geographic location that is the same as the take-off geographic location of the received first drone in the stored take-off geographic location; and obtains a corresponding flight tag according to the determination result;
  • the server 506 returns a flight tag to the client 504 running on the control terminal.
  • the client 504 running on the control terminal displays the flight tag.
  • the takeoff geographic location acquired when the drone takes off is sent to the server, so that the server establishes a common database of the drone on the server by using the acquired geographical position of the unmanned aerial vehicle. Further, the database is used to establish an interaction between the client running on the control terminal and the server, so as to realize the take-off geographic location of the shared drone, thereby returning the drone corresponding to the control terminal according to the take-off geographic location of the drone.
  • the purpose of the flight tag is to achieve the effect of sharing the flight label of the above-mentioned drone in the community space of the client to solve the technical problem that the flight tag of the drone cannot be obtained by the prior art.
  • the first sending unit 804 includes one of the following:
  • a first sending module configured to send a takeoff geographic location of the first drone to the server when the first drone takes off;
  • the second sending module is configured to send the takeoff geographic location of the first drone to the server after the first drone takes off.
  • the sending timing of transmitting the takeoff geographic location of the first drone to the server may include: when the first drone takes off, or after the first drone takes off . That is to say, the take-off geographic location can be synchronously sent to the server in real time, so that the server can realize real-time comparison and real-time feedback, thereby ensuring that the client running on the control terminal can acquire the flight label matched for the first drone in time, so that The community space of the client can update and display the obtained flight tags in real time.
  • the synchronous sending process can also be split, and multiple takeoff geographic locations acquired within a certain time interval are stored first, and then sent to the server together to reduce the number of transmissions. Improve the effect of sending the sending efficiency of the takeoff location to the server.
  • the take-off geographic location of the first drone may be saved on the control terminal first, or may be stored in other third-party storage media. This embodiment does not limit this.
  • the take-off geographic location of the first drone is sent, so that different sending occasions are selected according to different application scenarios to ensure Get timely and accurate flight tags corresponding to the takeoff location.
  • the second sending module includes one of the following:
  • a first sending submodule configured to: after the first drone takes off, acquire a sending instruction, and send a takeoff geographic location of the first drone to the server in response to the sending instruction;
  • the second sending sub-module is configured to determine whether the preset sending time is reached after the first drone takes off, and send the take-off geographic location of the first drone to the server when determining that the sending time is reached.
  • the takeoff geographic location of the first drone may be sent to the server in response to the obtained sending instruction.
  • the sending command may be, but is not limited to, a sending command triggered by the user through an input operation, where the input operation may include, but is not limited to, at least one of: clicking a predetermined trigger button, acquiring a predetermined voice, and acquiring a predetermined somatosensory gesture.
  • the control interface of the client running on the control terminal to the first drone can be controlled as shown in FIG. 6, and the first drone can be controlled to perform different "return to landing", "emergency hover” and “follow mode”. Operation, Or control the first drone to move in the direction indicated by the arrow.
  • the "control button" is used to trigger a sending instruction to send the first drone's takeoff geographic location to the server.
  • the acquired takeoff geographic location of the first drone may also be sent to the server at a preset sending moment.
  • the preset transmission time may include, but is not limited to, at least one of the following: a time when the predetermined condition is met, and a preset period end time.
  • the predetermined condition may be detecting a preset network signal, such as a 4G signal, a WIFI signal, or the like.
  • control terminal is triggered to send the takeoff geographic location of the first drone to the server in different manners, thereby diversifying operations, facilitating user operations, and improving the user experience.
  • the first obtaining unit 802 includes one of the following:
  • a third acquiring module configured to acquire a geographic location of the first drone when the first drone takes off, wherein the geographic location of the first drone is taken as a take-off geographic location of the first drone;
  • a fourth obtaining module configured to acquire a geographic location of the control terminal when the first drone takes off, wherein the client running on the control terminal controls the takeoff of the first drone, and controls the geographic location of the terminal As the takeoff location of the first drone.
  • obtaining the geographic location of the first drone when the first drone takes off may pass, but is not limited to, at least one of the following manners: 1) controlling the terminal to acquire the first drone to take off The geographic location of the first drone collected by the first drone; 2) the control terminal acquires the geographic location of the first drone when the first drone takes off.
  • the client running on the control terminal can acquire the take-off geographic location of the first drone collected by the first drone during take-off, and can also obtain the first drone by self-detection.
  • the takeoff location of the first drone at the time of takeoff.
  • the take-off geographic location of the first drone is obtained in different ways to meet the actual needs of different users, thereby ensuring the accuracy of the obtained flight tags.
  • the terminal further includes:
  • a display unit for running on the control terminal after acquiring the flight tag returned by the server The flight label is displayed in the client, wherein the client controls the takeoff of the first drone, and the flight tag is further used to indicate at least one of the following: a geographical name corresponding to the takeoff geographic location of the first drone, The departure date of a drone when it takes off, and the departure time of the first drone when it takes off.
  • the flight tag may include, but is not limited to, at least one of the following: a drone for indicating that the first drone is not the first takeoff in the takeoff geographic position of the first drone a first flight tag for indicating that the first drone is the second flight tag of the first drone in the takeoff geographic position of the first drone.
  • the above flight tag may also be, but is not limited to, indicating at least one of: a geographic name (eg, a place name) corresponding to a takeoff geographic location (eg, location coordinates) of the first drone, the first drone The departure date at the time of takeoff and the departure time of the first drone when taking off.
  • the flight tag acquired by the first drone after multiple flights can be displayed.
  • the first flight label (identified by the "First” logo) has the following geographical locations: "Eiffel Tower (15.09.24)", “Madrid (15.07.17)", “Hokkaido, Japan (15.06.04) "” and “Maldives Paradise Island (15.04.30)”;
  • the second flight label (marked by "Sweeping") includes the following geographical locations: “French Arc de Triomphe (15.09.23)", “Barcelona, Spain (15.07. 19)", “Tokyo, Japan (15.06.06)”.
  • the obtained flight tag is displayed by the client running on the control terminal, so that different users can share the flight tag in the community space, so that different users share different flights through the flight tag.
  • the client running on the control terminal so that different users can share the flight tag in the community space, so that different users share different flights through the flight tag.
  • an acquisition server for a flight tag including:
  • the receiving unit 902 is configured to receive a take-off geographic location of the first drone that is sent by the client when the first drone takes off, where the client runs on the control terminal and is used for the first drone Take off for control;
  • determining unit 904 configured to determine whether there is a take-off geographic location in the stored take-off geographic location that is the same as the take-off geographic location of the first drone;
  • a first sending unit 906 configured to send a first flight tag to the client when there is a takeoff geographic location that is the same as the takeoff geographic location of the first drone, wherein the first flight tag is used to indicate the first The first drone on the takeoff location of the drone is not the first drone to take off;
  • the second sending unit 908 is configured to send a second flight tag to the client when there is no take-off geographic location that is the same as the take-off geographic location of the first drone, wherein the second flight tag is used to indicate The first drone on the takeoff location of a drone is the first drone to take off.
  • the foregoing acquisition server of the flight tag may be, but is not limited to, being applied to a process of acquiring a flight tag of the drone on a client running on the control terminal, wherein the client running on the control terminal The end is used to control the takeoff of the drone.
  • the server receives the take-off geographic location of the first drone that is sent by the client when the first drone takes off, it is determined whether the stored take-off geographic location has the same geographical position as the take-off of the first drone. Taking off the geographical location, and then transmitting different first flight tags or second flight tags to the client according to different judgment results, wherein the client runs on the control terminal for controlling the takeoff of the first drone. As shown in FIG.
  • the flight label of the drone returned by the server is displayed on the client (user name: ID_01) running on the control terminal.
  • the flight label returned by the server includes: flight label_1 and flight label_2.
  • the flight tag can be "first" or "passed”. The above is only an example, and is not limited in this embodiment.
  • the server receives a takeoff geographic location of the first drone that is sent by the client when the first drone takes off, wherein the client runs on the control terminal for the first Controlling the take-off of the drone; determining whether there is a take-off geographic location in the stored take-off geographic location that is the same as the take-off geographic location of the first drone; if present, transmitting a first flight tag to the client, where a flight tag is used to indicate that the first drone is not the first take-off drone in the take-off geographical position of the first drone; if not, the second flight tag is sent to the client, wherein the second flight The tag is used to indicate that the first drone is the first take-off drone in the take-off geographical position of the first drone, wherein the flight tag is used to indicate that the first drone is first in the take-off geographical position Whether the man-machine is the first drone to take off.
  • the server obtains the corresponding flight tag through the acquired take-off geographic location, and sends the flight tag to the client, so that the server uses the acquired departure location of the drone to establish a common database of the drone at the server, and further, Using the database to establish an interaction between the client running on the control terminal and the server to achieve the take-off geographic position of the shared drone Therefore, the purpose of returning the flight label corresponding to the drone to the control terminal according to the take-off geographic location of the drone is achieved, thereby realizing the effect of sharing the flight label of the drone on the community space of the client.
  • the flight tag may include, but is not limited to, at least one of the following: for indicating that the first drone is not the first drone of the drone in the takeoff geographic position of the first drone
  • the first flight tag is configured to indicate that the first drone is the second flight tag of the first drone in the takeoff geographic location of the first drone.
  • the flight tag may be, but is not limited to, indicating at least one of: a geographic name corresponding to a take-off geographic location of the first drone, and a take-off when the first drone takes off. Date, the departure time of the first drone when taking off.
  • the first drone is controlled by a client running on the control terminal (user name: ID_01), and after the first drone has passed multiple flights, the obtained flight tag displayed on the client can be as shown in FIG.
  • the location of the first flight label (marked by the “First Place”) is as follows: “Eiffel Tower (15.09.24)”, “Madrid (15.07.17)”, “Hokkaido, Japan (15.06.04) "” and “Maldives Paradise Island (15.04.30)”;
  • the second flight label (marked by “Sweeping") includes the following geographical locations: “French Arc de Triomphe (15.09.23)", “Barcelona, Spain (15.07. 19)", “Tokyo, Japan (15.06.06)”.
  • the takeoff geographic location of the first drone may include, but is not limited to, one of the following: 1) a geographic location of the first drone when the first drone takes off; 2) The geographic location of the terminal is controlled when the first drone takes off.
  • the take-off geographic location of the first drone is the geographic location of the first drone when the first drone takes off
  • the take-off geographic location may be acquired by at least one of the following methods: 1) controlling the terminal Obtaining a geographic location of the first drone collected by the first drone when the first drone takes off; 2) obtaining, by detecting, the geographic location of the first drone when the first drone takes off.
  • determining whether there is a take-off geographic location in the stored take-off geographic location that is the same as the take-off geographic location of the first drone includes at least one of the following:
  • the judgment principle of the same takeoff geographic location may include, but is not limited to, at least one of the following: the location information is completely consistent, and the area indication information (part of the location information) for indicating the area is consistent.
  • sending the first flight tag to the client includes: acquiring a geographic name corresponding to a takeoff geographic location of the first drone, transmitting a first flight tag including at least a geographic name; and transmitting to the client
  • Sending the second flight tag includes: acquiring a geographic name corresponding to the takeoff geographic location of the first drone, storing a correspondence between the takeoff geographic location of the first drone and the acquired geographic name, and transmitting the at least the geographic name Two flight labels.
  • the foregoing server may, but is not limited to, adjust a taken-off geographic location stored in the server database according to the acquired geographic location of the drone. Specifically, after obtaining the second flight tag for indicating that the first drone is the first take-off of the drone in the take-off geographical position of the first drone, acquiring the take-off with the first drone The geographic name corresponding to the geographical location, and the corresponding relationship between the takeoff geographic location of the first drone and the acquired geographic name is stored, so as to achieve the effect of adding a new takeoff geographic location in the database.
  • the server obtains the corresponding flight tag through the acquired take-off geographic location, and sends the flight tag to the client, so that the server establishes the server using the taken-off geographic location of the obtained drone.
  • the common database of human and machine further, the database is used to establish an interaction between the client running on the control terminal and the server, so as to realize the take-off geographic location of the shared drone, thereby reaching the control terminal according to the takeoff geographic location of the drone.
  • the determining unit 904 includes at least one of the following:
  • a first determining module configured to determine whether the location information of the takeoff geographic location of the first drone is consistent with the location information of the stored takeoff geographic location
  • a second judging module configured to determine whether the area indication information in the location information of the takeoff geographic location of the first drone is consistent with the area indication information in the location information of the stored takeoff geographic location, wherein the area indication information As part of the location information.
  • the judgment principle of the same takeoff geographic location may include, but is not limited to, at least one of the following: the location information is completely consistent, and the area indication information (part of the location information) for indicating the area is consistent.
  • the first sending unit 906 includes: a first sending module, configured to acquire a geographic name corresponding to a takeoff geographic location of the first drone, and send a first flight tag including at least a geographic name;
  • the second sending unit 908 includes: a second sending module, configured to acquire a geographic name corresponding to the takeoff geographic location of the first drone, and store a correspondence between the takeoff geographic location of the first drone and the acquired geographic name Relationship, sending a second flight tag including at least a geographic name.
  • the foregoing server may, but is not limited to, adjust a taken-off geographic location stored in the server database according to the acquired geographic location of the drone. Specifically, after obtaining the second flight tag for indicating that the first drone is the first take-off of the drone in the take-off geographical position of the first drone, acquiring the take-off with the first drone The geographic name corresponding to the geographical location, and the corresponding relationship between the takeoff geographic location of the first drone and the acquired geographic name is stored, so as to achieve the effect of adding a new takeoff geographic location in the database.
  • an acquisition terminal for a flight tag for implementing the above method for acquiring a flight tag is further provided.
  • the terminal includes:
  • the processor 1002 is configured to acquire a takeoff geographic location of the first drone when the first drone takes off.
  • a communication interface 1004 connected to the processor 1002, configured to send the takeoff geographic location of the first drone to the server; and obtain a flight tag returned by the server, wherein the flight tag is used to indicate the first drone Whether the first drone is the first drone to take off in the geographical position.
  • the memory 1006 is connected to the memory 1002 and the communication interface 1004, and is configured to store the take-off geographic location of the first drone and the flight tag returned by the server.
  • an acquisition server for a flight tag for implementing the above method for acquiring a flight tag.
  • the server includes:
  • the communication interface 1102 is configured to receive, by the client, a take-off geographic location of the first drone when the first drone takes off, wherein the client runs on the control terminal and is used for the first drone Take off for control;
  • the processor 1104 is connected to the communication interface 1102, and is configured to determine whether there is a take-off geographic location that is the same as the take-off geographic location of the first drone in the stored take-off geographic location; if yes, send the first to the client a flight tag, wherein the first flight tag is used to indicate that the first drone is not the first drone on the takeoff geographic location of the first drone; if not, the second flight tag is sent to the client The second flight tag is configured to indicate that the first drone is the first drone to take off at the take-off geographic location of the first drone.
  • the memory 1106 is connected to the communication interface 1102 and the processor 1104, and is configured to store the takeoff geographic location of the first drone and the flight tag returned by the server.
  • Embodiments of the present application also provide a storage medium.
  • the storage medium is arranged to store program code for performing the following steps:
  • the storage medium is further arranged to store program code for performing the following steps:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the integrated unit in the above embodiment if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in the above-described computer readable storage medium.
  • the technical solution of the present application in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product, which is stored in a storage medium.
  • a number of instructions are included to cause one or more computer devices (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the disclosed client may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, unit or module, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Databases & Information Systems (AREA)
  • Signal Processing (AREA)
  • Remote Sensing (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Traffic Control Systems (AREA)
  • User Interface Of Digital Computer (AREA)
  • Navigation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种飞行标签的获取方法和终端及服务器，该方法包括：获取在第一无人机起飞时第一无人机的起飞地理位置（S202）；将第一无人机的起飞地理位置发送给服务器（S204）；获取服务器返回的飞行标签，其中，飞行标签用于指示第一无人机是否是首架在第一无人机的起飞地理位置上起飞的无人机（S206）。解决了现有技术无法获取无人机的飞行标签的技术问题。

Description

飞行标签的获取方法和终端及服务器
本申请要求于2016年4月1日提交中国专利局、申请号201610203591.1，发明名称为“飞行标签的获取方法和终端及服务器”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机领域，具体而言，涉及一种飞行标签的获取方法和终端及服务器。
背景技术
目前，现有的无人机通常是将飞行数据保存在无人机本地，其中，飞行数据用于记录飞行过程中的飞行参数或追踪飞行故障，供无人机自身使用。但是采用这样的方式时，由于缺乏交互而无法得知其他无人机的飞行记录，从而导致无法共享各个无人机的飞行数据，对多个无人机的飞行数据进行处理，例如，无法进行多个无人机之间的竞赛，学习，模仿，收集等。
针对上述的问题，目前尚未提出有效的解决方案。
发明内容
本申请实施例提供了一种飞行标签的获取方法和终端及服务器，以至少解决采用现有技术无法获取无人机的飞行标签的技术问题。
根据本申请实施例的一个方面，提供了一种飞行标签的获取方法，包括：获取在第一无人机起飞时上述第一无人机的起飞地理位置；将上述第一无人机的起飞地理位置发送给服务器；获取上述服务器返回的飞行标签，其中，上述飞行标签用于指示上述第一无人机是否是首架在上述第一无人机的起飞地理位置上起飞的无人机。
根据本申请实施例的另一方面，还提供了一种飞行标签的获取方法，包括： 接收客户端发送的在第一无人机起飞时上述第一无人机的起飞地理位置，其中，上述客户端运行在控制终端上，用于对上述第一无人机的起飞进行控制；判断已存储的起飞地理位置中是否存在与上述第一无人机的起飞地理位置相同的起飞地理位置；若存在，则向上述客户端发送第一飞行标签，其中，上述第一飞行标签用于指示在上述第一无人机的起飞地理位置上上述第一无人机不是首架起飞的无人机；若不存在，则向上述客户端发送第二飞行标签，其中，上述第二飞行标签用于指示在上述第一无人机的起飞地理位置上上述第一无人机是首架起飞的无人机。
根据本申请实施例的又一方面，还提供了一种飞行标签的获取终端，包括：第一获取单元，用于获取在第一无人机起飞时上述第一无人机的起飞地理位置；第一发送单元，用于将上述第一无人机的起飞地理位置发送给服务器；第二获取单元，用于获取上述服务器返回的飞行标签，其中，上述飞行标签用于指示在上述第一无人机的起飞地理位置上上述第一无人机是否是首架起飞的无人机。
根据本申请实施例的又一方面，还提供了一种飞行标签的获取服务器，包括：接收单元，用于接收客户端发送的在第一无人机起飞时上述第一无人机的起飞地理位置，其中，上述客户端运行在控制终端上，用于对上述第一无人机的起飞进行控制；判断单元，用于判断已存储的起飞地理位置中是否存在与上述第一无人机的起飞地理位置相同的起飞地理位置；第一发送单元，用于在存在与上述第一无人机的起飞地理位置相同的起飞地理位置时，向上述客户端发送第一飞行标签，其中，上述第一飞行标签用于指示在上述第一无人机的起飞地理位置上上述第一无人机不是首架起飞的无人机；第二发送单元，用于在不存在与上述第一无人机的起飞地理位置相同的起飞地理位置时，向上述客户端发送第二飞行标签，其中，上述第二飞行标签用于指示在上述第一无人机的起飞地理位置上上述第一无人机是首架起飞的无人机。
在本申请实施例中，控制终端上运行的客户端获取在第一无人机起飞时第一无人机的起飞地理位置，并将该起飞地理位置发送给服务器，然后从服务器获取返回的飞行标签，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。通过将在无人机起飞时获取到的起飞地理位置发送给服务器，以使服务器利用获取到的无人机的起飞地理位置在服 务器上建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而解决了采用现有技术无法获取无人机的飞行标签的技术问题。以实现在客户端的社区空间上共享上述无人机的飞行标签的效果。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据本申请实施例的一种可选的飞行标签的获取方法的应用环境示意图；
图2是根据本申请实施例的一种可选的飞行标签的获取方法的流程图；
图3是根据本申请实施例的一种可选的飞行标签的获取方法的示意图；
图4是根据本申请实施例的另一种可选的飞行标签的获取方法的示意图；
图5是根据本申请实施例的另一种可选的飞行标签的获取方法的流程图；
图6是根据本申请实施例的又一种可选的飞行标签的获取方法的示意图；
图7是根据本申请实施例的又一种可选的飞行标签的获取方法的流程图；
图8是根据本申请实施例的一种可选的飞行标签的获取终端的示意图；
图9是根据本申请实施例的一种可选的飞行标签的获取服务器的示意图；
图10是根据本申请实施例的一种可选的飞行标签的获取终端的结构示意图；以及
图11是根据本申请实施例的一种可选的飞行标签的获取服务器的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所 描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
实施例1
根据本申请实施例，提供了一种飞行标签的获取方法的实施例，该飞行标签的获取方法可以但不限于应用于如图1所示的应用环境中，控制终端104获取在第一无人机(如图1所示无人机102)起飞时第一无人机的起飞地理位置，将该起飞地理位置发送给服务器106，然后从服务器106获取返回的飞行标签，其中，飞行标签用于指示在第一无人机(如图1所示无人机102)的起飞地理位置上第一无人机(如图1所示无人机102)是否是首架起飞的无人机。通过将无人机的飞行数据(如起飞地理位置)发送给服务器，从而实现在服务器建立无人机共同的数据库，以利用该数据库实现向控制终端返回无人机的飞行标签的效果，进而达到在社区空间上共享上述无人机的飞行标签的目的。
可选地，在本实施例中，上述控制终端可以包括但不限于以下至少之一：移动终端、手环、手柄。其中，移动终端可以包括但不限于以下至少之一：手机、平板电脑、笔记本电脑。上述只是一种示例，本实施例对此不做任何限定。
可选地，在本实施例中，上述终端可以但不限于通过网络与服务器进行交互，其中，上述网络可以包括但不限于以下至少之一：广域网、城域网、局域网。上述终端可以但不限于通过无线连接与无人机进行数据交互。其中，上述无线连接可以包括但不限于以下至少之一：无线蓝牙、无线WIFI。上述只是一种示例，本实施例对此不做任何限定。
根据本申请实施例，提供了一种飞行标签的获取方法，如图2所示，该方法包括：
S202，获取在第一无人机起飞时第一无人机的起飞地理位置；
S204，将第一无人机的起飞地理位置发送给服务器；
S206，获取服务器返回的飞行标签，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。
可选地，在本实施例中，上述飞行标签的获取方法可以但不限于应用于在控制终端运行的客户端上获取无人机的飞行标签的过程中，其中，上述控制终端上运行的客户端用于控制无人机的起飞。例如，在将获取到的第一无人机起飞时的第一无人机的起飞地理位置发送给服务器后，获取服务器返回的第一无人机的飞行标签，并如图3所示，在控制终端运行的客户端(用户名为：ID_01)上显示服务器返回的无人机的飞行标签，如服务器返回的飞行标签包括：飞行标签_1和飞行标签_2。例如，飞行标签可以为“首占(首次占领)”、“掠过”。上述仅是一种示例，本实施例中对此不做任何限定。
需要说明的是，在本实施例中，控制终端上运行的客户端获取在第一无人机起飞时第一无人机的起飞地理位置，并将该起飞地理位置发送给服务器，然后从服务器获取返回的飞行标签，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。通过将在无人机起飞时获取到的起飞地理位置发送给服务器，以使服务器利用获取到的无人机的起飞地理位置在服务器建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果。
可选地，在本实施例中，在将第一无人机的起飞地理位置发送给服务器之后，且在获取服务器返回的飞行标签之前，还包括：服务器判断已存储的起飞地理位置中是否存在与接收到的第一无人机的起飞地理位置相同的起飞地理位置；根据判断结果发送对应的飞行标签。其中，飞行标签可以但不限于包括以下至少之一：用于指示在第一无人机的起飞地理位置上第一无人机不是首架起 飞的无人机的第一飞行标签、用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签。
可选地，在本实施例中，上述飞行标签还可以但不限于用于指示以下至少之一：与第一无人机的起飞地理位置对应的地理名称、第一无人机起飞时的起飞日期、第一无人机起飞时的起飞时间。例如，第一无人机受控制终端上运行的客户端(用户名为：ID_01)控制，该第一无人机经过多次飞行后，在客户端显示获取到的飞行标签可以如图4所示，第一飞行标签(用“首占”标识)下包括的起飞地理位置如下：“法国埃菲尔铁塔(15.09.24)”、“西班牙马德里(15.07.17)”、“日本北海道(15.06.04)”及“马尔代夫天堂岛(15.04.30)”；第二飞行标签(用“掠过”标识)下包括的起飞地理位置如下：“法国凯旋门(15.09.23)”、“西班牙巴塞罗那(15.07.19)”、“日本东京(15.06.06)”。
可选地，在本实施例中，上述第一无人机的起飞地理位置可以包括但不限于以下之一：1)在第一无人机起飞时第一无人机的地理位置；2)在第一无人机起飞时控制终端的地理位置。其中，在第一无人机的起飞地理位置为在第一无人机起飞时第一无人机的地理位置时，可以通过但不限于以下至少一种方式获取起飞地理位置：1)控制终端获取在第一无人机起飞时第一无人机采集的第一无人机的地理位置；2)控制终端通过检测获取在第一无人机起飞时第一无人机的地理位置。
可选地，在本实施例中，将第一无人机的起飞地理位置发送给服务器包括以下之一：
1)在第一无人机起飞时，将第一无人机的起飞地理位置发送给服务器；
2)在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器。
需要说明的是，在本实施例的上述方式1)中，通过在第一无人机起飞时，将第一无人机的起飞地理位置实时发送给服务器，以使服务器实现实时比对，实时反馈，从而保证控制终端上运行的客户端可以及时获取为第一无人机匹配的飞行标签，使客户端的社区空间可以实时更新显示获取的飞行标签。进一步，还可以实现实时更新服务器数据库中记录的数据，从而保证数据库的准确性及更新效率，进而多用户同时调用数据库中的数据，实现多用户互动的可行性。
此外，在本实施例的上述方式2)中，还可以通过在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器，从而实现在间隔时间后，再将获取到的第一无人机的起飞地理位置同步到服务器上。通过将向服务器发送第一无人机的起飞地理位置的同步过程拆分，也就是说，将一定时间间隔内获取的多个起飞地理位置一起发送给服务器，减少发送次数，从而实现提高向服务器发送起飞地理位置的发送效率的效果。
可选地，在本实施例中，上述方式2)中在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器包括以下之一：
(1)在第一无人机起飞之后，获取到发送指令，响应发送指令将第一无人机的起飞地理位置发送给服务器；
(2)在第一无人机起飞之后，判断是否到达预设的发送时刻，在判断出到达发送时刻时，将第一无人机的起飞地理位置发送给服务器。
也就是说，在第一无人机起飞之后，可以响应获取到的发送指令发送第一无人机的起飞地理位置给服务器，也可以在预设的发送时刻发送获取到的第一无人机的起飞地理位置给服务器。
需要说明的是，在本实施例中，上述发送指令可以但不限于为用户通过输入操作触发的发送指令，其中，上述输入操作可以包括但不限于以下至少之一：点击预定触发按钮、采集预定语音、获取预定体感手势。
此外，在本实施例中，上述预设的发送时刻可以包括但不限于以下至少之一：满足预定条件的时刻、预设周期结束时刻。例如，预定条件可以为检测到预置的网络信号，如4G信号，WIFI信号等。
具体结合以下示例进行说明，如图5所示，在该示例中，以第一无人机的起飞地理位置为第一无人机起飞时第一无人机的地理位置为例。
S502，控制终端上运行的客户端504获取在第一无人机起飞时第一无人机502采集的第一无人机的地理位置；
S504，控制终端上运行的客户端504将第一无人机的起飞地理位置发送给服务器506；
S506，服务器506判断已存储的起飞地理位置中是否存在与接收到的第一无人机的起飞地理位置相同的起飞地理位置；根据判断结果获取对应的飞行标签；
S508，服务器506向控制终端上运行的客户端504返回飞行标签；
S510，控制终端上运行的客户端504显示飞行标签。
通过本申请提供的实施例，通过将在无人机起飞时获取到的起飞地理位置发送给服务器，以使服务器利用获取到的无人机的起飞地理位置在服务器上建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果，以解决采用现有技术无法获取无人机的飞行标签的技术问题。
作为一种可选的方案，将第一无人机的起飞地理位置发送给服务器包括以下之一：
1)在第一无人机起飞时，将第一无人机的起飞地理位置发送给服务器；或者
2)在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器。
需要说明的是，在本实施例中，将第一无人机的起飞地理位置发送给服务器的发送时机可以包括：在第一无人机起飞时，或者，在第一无人机起飞之后。也就是说，可以将起飞地理位置实时同步发送到服务器，以使服务器实现实时比对，实时反馈，从而保证控制终端上运行的客户端可以及时获取为第一无人机匹配的飞行标签，使客户端的社区空间可以实时更新显示获取的飞行标签；也可以将同步发送过程拆分，先存储一定时间间隔内获取的多个起飞地理位置，然后再一起发送给服务器，以减少发送次数，从而实现提高向服务器发送起飞地理位置的发送效率的效果。
可选地，在本实施例中，在上述方式2)中，上述第一无人机的起飞地理位置可以先保存在控制终端上，也可以保存在其他第三方存储介质中。本实施例中对此不做任何限定。
通过本申请提供的实施例，在第一无人机起飞时或第一无人机起飞之后，发送第一无人机的起飞地理位置，从而实现根据不同应用场景选择不同的发送时机，以保证及时准确地获取到与起飞地理位置对应的飞行标签。
作为一种可选的方案，在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器包括以下之一：
1)在第一无人机起飞之后，获取到发送指令，响应发送指令将第一无人机的起飞地理位置发送给服务器；或者
2)在第一无人机起飞之后，判断是否到达预设的发送时刻，在判断出到达发送时刻时，将第一无人机的起飞地理位置发送给服务器。
可选地，在本实施例中，在第一无人机起飞之后，可以响应获取到的发送指令发送第一无人机的起飞地理位置给服务器。其中，上述发送指令可以但不限于为用户通过输入操作触发的发送指令，其中，上述输入操作可以包括但不限于以下至少之一：点击预定触发按钮、采集预定语音、获取预定体感手势。例如，在控制终端上运行的客户端对第一无人机的控制界面如图6所示，可以控制第一无人机执行“返回降落”、“紧急悬停”及“跟随模式”的不同操作，或者控制第一无人机按照箭头指示的方向移动。此外，还可以在第一无人机起飞后(或者在第一无人机起飞时)，通过“控制按钮”触发向服务器发送第一无人机的起飞地理位置的发送指令。
可选地，在本实施例中，在第一无人机起飞之后，还可以在预设的发送时刻发送获取到的第一无人机的起飞地理位置给服务器。其中，上述预设的发送时刻可以包括但不限于以下至少之一：满足预定条件的时刻、预设周期结束时刻。例如，预定条件可以为检测到预置的网络信号，如4G信号，WIFI信号等。
通过本申请提供的实施例，通过不同方式触发控制终端向服务器发送第一无人机的起飞地理位置，实现操作的多样化，更便于用户操作，改善了用户体验。
作为一种可选的方案，获取在第一无人机起飞时第一无人机的起飞地理位置包括以下之一：
S1，获取在第一无人机起飞时第一无人机的地理位置，其中，将第一无人机的地理位置作为第一无人机的起飞地理位置；
S2，获取在第一无人机起飞时控制终端的地理位置，其中，控制终端上运行的客户端对第一无人机的起飞进行控制，将控制终端的地理位置作为第一无人机的起飞地理位置。
可选地，在本实施例中，获取在第一无人机起飞时第一无人机的地理位置可以通过但不限于以下至少一种方式：1)控制终端获取在第一无人机起飞时第一无人机采集的第一无人机的地理位置；2)控制终端通过检测获取在第一无人机起飞时第一无人机的地理位置。
通过本申请提供的实施例，控制终端上运行的客户端可以获取第一无人机在起飞时采集到的第一无人机的起飞地理位置，也可以通过自身检测获取第一无人机在起飞时的第一无人机的起飞地理位置。通过不同方式获取第一无人机的起飞地理位置，从而满足不同用户的实际需求，进而保证所获取到的飞行标签的准确性。
作为一种可选的方案，在获取服务器返回的飞行标签之后，还包括：
S1，在控制终端上运行的客户端中显示飞行标签，其中，客户端对第一无人机的起飞进行控制，飞行标签还用于指示以下至少之一：与第一无人机的起飞地理位置对应的地理名称、第一无人机起飞时的起飞日期、第一无人机起飞时的起飞时间。
可选地，在本实施例中，上述飞行标签可以但不限于包括以下至少之一：用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机的第一飞行标签、用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签。此外，上述飞行标签还可以但不限于用于指示以下至少之一：与第一无人机的起飞地理位置(例如，位置坐标)对应的地理名称(例如，地点名称)、第一无人机起飞时的起飞日期、第一无人机起飞时的起飞时间。
具体结合图4所示进行说明，在控制终端上运行的客户端中，可以显示第一无人机在多次飞行之后获取到的飞行标签。例如，第一飞行标签(用“首占” 标识)下包括的起飞地理位置如下：“法国埃菲尔铁塔(15.09.24)”、“西班牙马德里(15.07.17)”、“日本北海道(15.06.04)”及“马尔代夫天堂岛(15.04.30)”；第二飞行标签(用“掠过”标识)下包括的起飞地理位置如下：“法国凯旋门(15.09.23)”、“西班牙巴塞罗那(15.07.19)”、“日本东京(15.06.06)”。
通过本申请提供的实施例，通过在控制终端上运行的客户端显示获取到的飞行标签，以实现使不同用户可以在社区空间共享该飞行标签，从而使不同用户通过该飞行标签分享不同的飞行经历，进而满足不同用户的不同实际需求。
作为一种可选的方案，在将第一无人机的起飞地理位置发送给服务器之后，且在获取服务器返回的飞行标签之前，还包括：
S1，服务器接收起飞地理位置；
S2，服务器判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置；
S3，若存在，则服务器发送第一飞行标签，其中，第一飞行标签用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机，飞行标签包括：第一飞行标签；
S4，若不存在，则服务器发送第二飞行标签，其中，第二飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机，飞行标签包括：第二飞行标签。
可选地，在本实施例中，上述服务器通过比对已存储的起飞地理位置与第一无人机的起飞地理位置，以判断服务器中建立的数据库中是否存在与第一无人机的起飞地理位置相同的起飞地理位置，从而根据判断结果向发送不同的飞行标签。进而保证控制终端上运行的客户端获取到准确的飞行标签。
可选地，在本实施例中，判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置包括以下至少之一：
1)判断第一无人机的起飞地理位置的位置信息与已存储的起飞地理位置的位置信息是否一致；
2)判断第一无人机的起飞地理位置的位置信息中的区域指示信息与已存储的起飞地理位置的位置信息中的区域指示信息是否一致，其中，区域指示信息为位置信息的一部分。
也就是说，相同的起飞地理位置的判断原则可以包括但不限于以下至少之一：位置信息完全一致、用于指示所在区域的区域指示信息(位置信息中的一部分)一致。
可选地，在本实施例中，向客户端发送第一飞行标签包括：获取与第一无人机的起飞地理位置对应的地理名称，发送至少包括地理名称的第一飞行标签；向客户端发送第二飞行标签包括：获取与第一无人机的起飞地理位置对应的地理名称，存储第一无人机的起飞地理位置与获取到的地理名称的对应关系，发送至少包括地理名称的第二飞行标签。
可选地，在本实施例中，上述服务器可以但不限于根据获取到的无人机的起飞地理位置调整服务器数据库中已存储的起飞地理位置。具体而言，在获取到用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签，则获取与第一无人机的起飞地理位置对应的地理名称，并存储该第一无人机的起飞地理位置与获取到的地理名称的对应关系，以实现在数据库中添加新增的起飞地理位置的效果。
通过本申请提供的实施例，通过将在无人机起飞时获取到的起飞地理位置发送给服务器，以使服务器利用获取到的无人机的起飞地理位置在服务器建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本申请所必须的。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例所述的装置。
实施例2
根据本申请实施例，还提供了一种飞行标签的获取方法，如图7所示，该方法包括：
S702，接收客户端发送的在第一无人机起飞时第一无人机的起飞地理位置，其中，客户端运行在控制终端上，用于对第一无人机的起飞进行控制；
S704，判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置；
S706，若存在，则向客户端发送第一飞行标签，其中，第一飞行标签用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机；
S708，若不存在，则向客户端发送第二飞行标签，其中，第二飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机。
可选地，在本实施例中，上述飞行标签的获取方法可以但不限于应用于在控制终端运行的客户端上获取无人机的飞行标签的过程中，其中，上述控制终端上运行的客户端用于控制无人机的起飞。例如，在服务器接收客户端发送的在第一无人机起飞时第一无人机的起飞地理位置后，判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置，进而实现根据不同的判断结果向客户端发送不同的第一飞行标签或第二飞行标签，其中，客户端运行在控制终端上，用于对第一无人机的起飞进行控制。如图3所示，在控制终端运行的客户端(用户名为：ID_01)上显示服务器返回的无人机的飞行标签，如服务器返回的飞行标签包括：飞行标签_1和飞行标签_2。例如，飞行标签可以为“首占”、“掠过”。上述仅是一种示例，本实施例中对此不做任何 限定。
需要说明的是，在本实施例中，服务器接收客户端发送的在第一无人机起飞时第一无人机的起飞地理位置，其中，客户端运行在控制终端上，用于对第一无人机的起飞进行控制；判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置；若存在，则向客户端发送第一飞行标签，其中，第一飞行标签用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机；若不存在，则向客户端发送第二飞行标签，其中，第二飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。通过服务器通过获取到的起飞地理位置获取对应的飞行标签，并将该飞行标签发送客户端，以使服务器利用获取到的无人机的起飞地理位置在服务器建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果。
可选地，在本实施例中，飞行标签可以但不限于包括以下至少之一：用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机的第一飞行标签、用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签。
可选地，在本实施例中，上述飞行标签还可以但不限于用于指示以下至少之一：与第一无人机的起飞地理位置对应的地理名称、第一无人机起飞时的起飞日期、第一无人机起飞时的起飞时间。例如，第一无人机受控制终端上运行的客户端(用户名为：ID_01)控制，该第一无人机经过多次飞行后，在客户端显示获取到的飞行标签可以如图4所示，第一飞行标签(用“首占”标识)下包括的起飞地理位置如下：“法国埃菲尔铁塔(15.09.24)”、“西班牙马德里(15.07.17)”、“日本北海道(15.06.04)”及“马尔代夫天堂岛(15.04.30)”；第二飞行标签(用“掠过”标识)下包括的起飞地理位置如下：“法国凯旋门(15.09.23)”、“西班牙巴塞罗那(15.07.19)”、“日本东京(15.06.06)”。
可选地，在本实施例中，上述第一无人机的起飞地理位置可以包括但不限 于以下之一：1)在第一无人机起飞时第一无人机的地理位置；2)在第一无人机起飞时控制终端的地理位置。其中，在第一无人机的起飞地理位置为在第一无人机起飞时第一无人机的地理位置时，可以通过但不限于以下至少一种方式获取起飞地理位置：1)控制终端获取在第一无人机起飞时第一无人机采集的第一无人机的地理位置；2)控制终端通过检测获取在第一无人机起飞时第一无人机的地理位置。
可选地，在本实施例中，判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置包括以下至少之一：
1)判断第一无人机的起飞地理位置的位置信息与已存储的起飞地理位置的位置信息是否一致；
2)判断第一无人机的起飞地理位置的位置信息中的区域指示信息与已存储的起飞地理位置的位置信息中的区域指示信息是否一致，其中，区域指示信息为位置信息的一部分。
也就是说，相同的起飞地理位置的判断原则可以包括但不限于以下至少之一：位置信息完全一致、用于指示所在区域的区域指示信息(位置信息中的一部分)一致。
可选地，在本实施例中，向客户端发送第一飞行标签包括：获取与第一无人机的起飞地理位置对应的地理名称，发送至少包括地理名称的第一飞行标签；向客户端发送第二飞行标签包括：获取与第一无人机的起飞地理位置对应的地理名称，存储第一无人机的起飞地理位置与获取到的地理名称的对应关系，发送至少包括地理名称的第二飞行标签。
可选地，在本实施例中，上述服务器可以但不限于根据获取到的无人机的起飞地理位置调整服务器数据库中已存储的起飞地理位置。具体而言，在获取到用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签，则获取与第一无人机的起飞地理位置对应的地理名称，并存储该第一无人机的起飞地理位置与获取到的地理名称的对应关系，以实现在数据库中添加新增的起飞地理位置的效果。
通过本申请提供的实施例，服务器通过获取到的起飞地理位置获取对应的 飞行标签，并将该飞行标签发送客户端，以使服务器利用获取到的无人机的起飞地理位置在服务器建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果。
作为一种可选的方案，判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置包括以下至少之一：
1)判断第一无人机的起飞地理位置的位置信息与已存储的起飞地理位置的位置信息是否一致；
2)判断第一无人机的起飞地理位置的位置信息中的区域指示信息与已存储的起飞地理位置的位置信息中的区域指示信息是否一致，其中，区域指示信息为位置信息的一部分。
也就是说，相同的起飞地理位置的判断原则可以包括但不限于以下至少之一：位置信息完全一致、用于指示所在区域的区域指示信息(位置信息中的一部分)一致。
作为一种可选的方案，
1)向客户端发送第一飞行标签包括：获取与第一无人机的起飞地理位置对应的地理名称，发送至少包括地理名称的第一飞行标签；
2)向客户端发送第二飞行标签包括：获取与第一无人机的起飞地理位置对应的地理名称，存储第一无人机的起飞地理位置与获取到的地理名称的对应关系，发送至少包括地理名称的第二飞行标签。
可选地，在本实施例中，上述服务器可以但不限于根据获取到的无人机的起飞地理位置调整服务器数据库中已存储的起飞地理位置。具体而言，在获取到用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签，则获取与第一无人机的起飞地理位置对应的地理名称，并存储该第一无人机的起飞地理位置与获取到的地理名称的对应关系，以实现在数据库中添加新增的起飞地理位置的效果。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本申请所必须的。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例所述的装置。
实施例3
根据本申请实施例，提供了一种飞行标签的获取终端，如图8所示，包括：
1)第一获取单元802，用于获取在第一无人机起飞时第一无人机的起飞地理位置；
2)第一发送单元804，用于将第一无人机的起飞地理位置发送给服务器；
3)第二获取单元806，用于获取服务器返回的飞行标签，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。
可选地，在本实施例中，上述飞行标签的获取终端可以但不限于应用于在控制终端运行的客户端上获取无人机的飞行标签的过程中，其中，上述控制终端上运行的客户端用于控制无人机的起飞。例如，在将获取到的第一无人机起飞时的第一无人机的起飞地理位置发送给服务器后，获取服务器返回的第一无人机的飞行标签，并如图3所示，在控制终端运行的客户端(用户名为：ID_01)上显示服务器返回的无人机的飞行标签，如服务器返回的飞行标签包括：飞行标签_1和飞行标签_2。例如，飞行标签可以为“首占”、“掠过”。上述仅是一种示例，本实施例中对此不做任何限定。
需要说明的是，在本实施例中，控制终端上运行的客户端获取在第一无人机起飞时第一无人机的起飞地理位置，并将该起飞地理位置发送给服务器，然后从服务器获取返回的飞行标签，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。通过将在无人机起飞时获取到的起飞地理位置发送给服务器，以使服务器利用获取到的无人机的起飞地理位置在服务器建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果。
可选地，在本实施例中，在将第一无人机的起飞地理位置发送给服务器之后，且在获取服务器返回的飞行标签之前，还包括：服务器判断已存储的起飞地理位置中是否存在与接收到的第一无人机的起飞地理位置相同的起飞地理位置；根据判断结果发送对应的飞行标签。其中，飞行标签可以但不限于包括以下至少之一：用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机的第一飞行标签、用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签。
可选地，在本实施例中，上述飞行标签还可以但不限于用于指示以下至少之一：与第一无人机的起飞地理位置对应的地理名称、第一无人机起飞时的起飞日期、第一无人机起飞时的起飞时间。例如，第一无人机受控制终端上运行的客户端(用户名为：ID_01)控制，该第一无人机经过多次飞行后，在客户端显示获取到的飞行标签可以如图4所示，第一飞行标签(用“首占”标识)下包括的起飞地理位置如下：“法国埃菲尔铁塔(15.09.24)”、“西班牙马德里(15.07.17)”、“日本北海道(15.06.04)”及“马尔代夫天堂岛(15.04.30)”；第二飞行标签(用“掠过”标识)下包括的起飞地理位置如下：“法国凯旋门(15.09.23)”、“西班牙巴塞罗那(15.07.19)”、“日本东京(15.06.06)”。
可选地，在本实施例中，上述第一无人机的起飞地理位置可以包括但不限于以下之一：1)在第一无人机起飞时第一无人机的地理位置；2)在第一无人机起飞时控制终端的地理位置。其中，在第一无人机的起飞地理位置为在第一无人机起飞时第一无人机的地理位置时，可以通过但不限于以下至少一种方式 获取起飞地理位置：1)控制终端获取在第一无人机起飞时第一无人机采集的第一无人机的地理位置；2)控制终端通过检测获取在第一无人机起飞时第一无人机的地理位置。
可选地，在本实施例中，将第一无人机的起飞地理位置发送给服务器包括以下之一：
1)在第一无人机起飞时，将第一无人机的起飞地理位置发送给服务器；
2)在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器。
需要说明的是，在本实施例的上述方式1)中，通过在第一无人机起飞时，将第一无人机的起飞地理位置实时发送给服务器，以使服务器实现实时比对，实时反馈，从而保证控制终端上运行的客户端可以及时获取为第一无人机匹配的飞行标签，使客户端的社区空间可以实时更新显示获取的飞行标签。进一步，还可以实现实时更新服务器数据库中记录的数据，从而保证数据库的准确性及更新效率，进而多用户同时调用数据库中的数据，实现多用户互动的可行性。
此外，在本实施例的上述方式2)中，还可以通过在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器，从而实现在间隔时间后，再将获取到的第一无人机的起飞地理位置同步到服务器上。通过将向服务器发送第一无人机的起飞地理位置的同步过程拆分，也就是说，将一定时间间隔内获取的多个起飞地理位置一起发送给服务器，减少发送次数，从而实现提高向服务器发送起飞地理位置的发送效率的效果。
可选地，在本实施例中，上述方式2)中在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器包括以下之一：
(1)在第一无人机起飞之后，获取到发送指令，响应发送指令将第一无人机的起飞地理位置发送给服务器；
(2)在第一无人机起飞之后，判断是否到达预设的发送时刻，在判断出到达发送时刻时，将第一无人机的起飞地理位置发送给服务器。
也就是说，在第一无人机起飞之后，可以响应获取到的发送指令发送第一无人机的起飞地理位置给服务器，也可以在预设的发送时刻发送获取到的第一无人机的起飞地理位置给服务器。
需要说明的是，在本实施例中，上述发送指令可以但不限于为用户通过输入操作触发的发送指令，其中，上述输入操作可以包括但不限于以下至少之一：点击预定触发按钮、采集预定语音、获取预定体感手势。
此外，在本实施例中，上述预设的发送时刻可以包括但不限于以下至少之一：满足预定条件的时刻、预设周期结束时刻。例如，预定条件可以为检测到预置的网络信号，如4G信号，WIFI信号等。
具体结合以下示例进行说明，如图5所示，在该示例中，第一无人机的起飞地理位置以在第一无人机起飞时第一无人机的地理位置为例。
S502，控制终端上运行的客户端504获取在第一无人机起飞时第一无人机502采集的第一无人机的地理位置；
S504，控制终端上运行的客户端504将第一无人机的起飞地理位置发送给服务器；
S506，服务器506判断已存储的起飞地理位置中是否存在与接收到的第一无人机的起飞地理位置相同的起飞地理位置；根据判断结果获取对应的飞行标签；
S508，服务器506向控制终端上运行的客户端504返回飞行标签；
S510，控制终端上运行的客户端504显示飞行标签。
通过本申请提供的实施例，通过将在无人机起飞时获取到的起飞地理位置发送给服务器，以使服务器利用获取到的无人机的起飞地理位置在服务器上建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果，以解决采用现有技术无法获取无人机的飞行标签的技术问题。
作为一种可选的方案，第一发送单元804包括以下之一：
1)第一发送模块，用于在第一无人机起飞时，将第一无人机的起飞地理位置发送给服务器；
2)第二发送模块，用于在第一无人机起飞之后，将第一无人机的起飞地理位置发送给服务器。
需要说明的是，在本实施例中，将第一无人机的起飞地理位置发送给服务器的发送时机可以包括：在第一无人机起飞时，或者，在在第一无人机起飞之后。也就是说，可以将起飞地理位置实时同步发送到服务器，以使服务器实现实时比对，实时反馈，从而保证控制终端上运行的客户端可以及时获取为第一无人机匹配的飞行标签，使客户端的社区空间可以实时更新显示获取的飞行标签；也可以将同步发送过程拆分，先存储一定时间间隔内获取的多个起飞地理位置，然后再一起发送给服务器，以减少发送次数，从而实现提高向服务器发送起飞地理位置的发送效率的效果。
可选地，在本实施例中，在上述方式2)中，上述第一无人机的起飞地理位置可以先保存在控制终端上，也可以保存在其他第三方存储介质中。本实施例中对此不做任何限定。
通过本申请提供的实施例，在第一无人机起飞时或第一无人机起飞之后，发送第一无人机的起飞地理位置，从而实现根据不同应用场景选择不同的发送时机，以保证及时准确地获取到与起飞地理位置对应的飞行标签。
作为一种可选的方案，第二发送模块包括以下之一：
1)第一发送子模块，用于在第一无人机起飞之后，获取到发送指令，响应发送指令将第一无人机的起飞地理位置发送给服务器；
2)第二发送子模块，用于在第一无人机起飞之后，判断是否到达预设的发送时刻，在判断出到达发送时刻时，将第一无人机的起飞地理位置发送给服务器。
可选地，在本实施例中，在第一无人机起飞之后，可以响应获取到的发送指令发送第一无人机的起飞地理位置给服务器。其中，上述发送指令可以但不限于为用户通过输入操作触发的发送指令，其中，上述输入操作可以包括但不限于以下至少之一：点击预定触发按钮、采集预定语音、获取预定体感手势。例如，在控制终端上运行的客户端对第一无人机的控制界面如图6所示，可以控制第一无人机执行“返回降落”、“紧急悬停”及“跟随模式”的不同操作， 或者控制第一无人机按照箭头指示的方向移动。此外，还可以在第一无人机起飞后(或者在第一无人机起飞时)，通过“控制按钮”触发向服务器发送第一无人机的起飞地理位置的发送指令。
可选地，在本实施例中，在第一无人机起飞之后，还可以在预设的发送时刻发送获取到的第一无人机的起飞地理位置给服务器。其中，上述预设的发送时刻可以包括但不限于以下至少之一：满足预定条件的时刻、预设周期结束时刻。例如，预定条件可以为检测到预置的网络信号，如4G信号，WIFI信号等。
通过本申请提供的实施例，通过不同方式触发控制终端向服务器发送第一无人机的起飞地理位置，实现操作的多样化，更便于用户操作，改善了用户体验。
作为一种可选的方案，第一获取单元802包括以下之一：
1)第三获取模块，用于获取在第一无人机起飞时第一无人机的地理位置，其中，将第一无人机的地理位置作为第一无人机的起飞地理位置；
2)第四获取模块，用于获取在第一无人机起飞时控制终端的地理位置，其中，控制终端上运行的客户端对第一无人机的起飞进行控制，将控制终端的地理位置作为第一无人机的起飞地理位置。
可选地，在本实施例中，获取在第一无人机起飞时第一无人机的地理位置可以通过但不限于以下至少一种方式：1)控制终端获取在第一无人机起飞时第一无人机采集的第一无人机的地理位置；2)控制终端通过检测获取在第一无人机起飞时第一无人机的地理位置。
通过本申请提供的实施例，控制终端上运行的客户端可以获取第一无人机在起飞时采集到的第一无人机的起飞地理位置，也可以通过自身检测获取第一无人机在起飞时的第一无人机的起飞地理位置。通过不同方式获取第一无人机的起飞地理位置，从而满足不同用户的实际需求，进而保证所获取到的飞行标签的准确性。
作为一种可选的方案，终端还包括：
1)显示单元，用于在获取服务器返回的飞行标签之后，在控制终端上运行 的客户端中显示飞行标签，其中，客户端对第一无人机的起飞进行控制，飞行标签还用于指示以下至少之一：与第一无人机的起飞地理位置对应的地理名称、第一无人机起飞时的起飞日期、第一无人机起飞时的起飞时间。
可选地，在本实施例中，上述飞行标签可以但不限于包括以下至少之一：用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机的第一飞行标签、用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签。此外，上述飞行标签还可以但不限于用于指示以下至少之一：与第一无人机的起飞地理位置(例如，位置坐标)对应的地理名称(例如，地点名称)、第一无人机起飞时的起飞日期、第一无人机起飞时的起飞时间。
具体结合图4所示进行说明，在控制终端上运行的客户端中，可以显示第一无人机在多次飞行之后获取到的飞行标签。例如，第一飞行标签(用“首占”标识)下包括的起飞地理位置如下：“法国埃菲尔铁塔(15.09.24)”、“西班牙马德里(15.07.17)”、“日本北海道(15.06.04)”及“马尔代夫天堂岛(15.04.30)”；第二飞行标签(用“掠过”标识)下包括的起飞地理位置如下：“法国凯旋门(15.09.23)”、“西班牙巴塞罗那(15.07.19)”、“日本东京(15.06.06)”。
通过本申请提供的实施例，通过在控制终端上运行的客户端显示获取到的飞行标签，以实现使不同用户可以在社区空间共享该飞行标签，从而使不同用户通过该飞行标签分享不同的飞行经历，进而满足不同用户的不同实际需求。
实施例4
根据本申请实施例，提供了一种飞行标签的获取服务器，如图9所示，包括：
1)接收单元902，用于接收客户端发送的在第一无人机起飞时第一无人机的起飞地理位置，其中，客户端运行在控制终端上，用于对第一无人机的起飞进行控制；
2)判断单元904，用于判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置；
3)第一发送单元906，用于在存在与第一无人机的起飞地理位置相同的起飞地理位置时，向客户端发送第一飞行标签，其中，第一飞行标签用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机；
4)第二发送单元908，用于在不存在与第一无人机的起飞地理位置相同的起飞地理位置时，向客户端发送第二飞行标签，其中，第二飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机。
可选地，在本实施例中，上述飞行标签的获取服务器可以但不限于应用于在控制终端运行的客户端上获取无人机的飞行标签的过程中，其中，上述控制终端上运行的客户端用于控制无人机的起飞。例如，在服务器接收客户端发送的在第一无人机起飞时第一无人机的起飞地理位置后，判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置，进而实现根据不同的判断结果向客户端发送不同的第一飞行标签或第二飞行标签，其中，客户端运行在控制终端上，用于对第一无人机的起飞进行控制。如图3所示，在控制终端运行的客户端(用户名为：ID_01)上显示服务器返回的无人机的飞行标签，如服务器返回的飞行标签包括：飞行标签_1和飞行标签_2。例如，飞行标签可以为“首占”、“掠过”。上述仅是一种示例，本实施例中对此不做任何限定。
需要说明的是，在本实施例中，服务器接收客户端发送的在第一无人机起飞时第一无人机的起飞地理位置，其中，客户端运行在控制终端上，用于对第一无人机的起飞进行控制；判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置；若存在，则向客户端发送第一飞行标签，其中，第一飞行标签用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机；若不存在，则向客户端发送第二飞行标签，其中，第二飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。通过服务器通过获取到的起飞地理位置获取对应的飞行标签，并将该飞行标签发送客户端，以使服务器利用获取到的无人机的起飞地理位置在服务器建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位 置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果。
可选地，在本实施例中，飞行标签可以但不限于包括以下至少之一：用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机的第一飞行标签、用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签。
可选地，在本实施例中，上述飞行标签还可以但不限于用于指示以下至少之一：与第一无人机的起飞地理位置对应的地理名称、第一无人机起飞时的起飞日期、第一无人机起飞时的起飞时间。例如，第一无人机受控制终端上运行的客户端(用户名为：ID_01)控制，该第一无人机经过多次飞行后，在客户端显示获取到的飞行标签可以如图4所示，第一飞行标签(用“首占”标识)下包括的起飞地理位置如下：“法国埃菲尔铁塔(15.09.24)”、“西班牙马德里(15.07.17)”、“日本北海道(15.06.04)”及“马尔代夫天堂岛(15.04.30)”；第二飞行标签(用“掠过”标识)下包括的起飞地理位置如下：“法国凯旋门(15.09.23)”、“西班牙巴塞罗那(15.07.19)”、“日本东京(15.06.06)”。
可选地，在本实施例中，上述第一无人机的起飞地理位置可以包括但不限于以下之一：1)在第一无人机起飞时第一无人机的地理位置；2)在第一无人机起飞时控制终端的地理位置。其中，在第一无人机的起飞地理位置为在第一无人机起飞时第一无人机的地理位置时，可以通过但不限于以下至少一种方式获取起飞地理位置：1)控制终端获取在第一无人机起飞时第一无人机采集的第一无人机的地理位置；2)控制终端通过检测获取在第一无人机起飞时第一无人机的地理位置。
可选地，在本实施例中，判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置包括以下至少之一：
1)判断第一无人机的起飞地理位置的位置信息与已存储的起飞地理位置的位置信息是否一致；
2)判断第一无人机的起飞地理位置的位置信息中的区域指示信息与已存储的起飞地理位置的位置信息中的区域指示信息是否一致，其中，区域指示信息 为位置信息的一部分。
也就是说，相同的起飞地理位置的判断原则可以包括但不限于以下至少之一：位置信息完全一致、用于指示所在区域的区域指示信息(位置信息中的一部分)一致。
可选地，在本实施例中，向客户端发送第一飞行标签包括：获取与第一无人机的起飞地理位置对应的地理名称，发送至少包括地理名称的第一飞行标签；向客户端发送第二飞行标签包括：获取与第一无人机的起飞地理位置对应的地理名称，存储第一无人机的起飞地理位置与获取到的地理名称的对应关系，发送至少包括地理名称的第二飞行标签。
可选地，在本实施例中，上述服务器可以但不限于根据获取到的无人机的起飞地理位置调整服务器数据库中已存储的起飞地理位置。具体而言，在获取到用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签，则获取与第一无人机的起飞地理位置对应的地理名称，并存储该第一无人机的起飞地理位置与获取到的地理名称的对应关系，以实现在数据库中添加新增的起飞地理位置的效果。
通过本申请提供的实施例，通过服务器通过获取到的起飞地理位置获取对应的飞行标签，并将该飞行标签发送客户端，以使服务器利用获取到的无人机的起飞地理位置在服务器建立无人机共同的数据库，进一步，利用该数据库在控制终端上运行的客户端与服务器之间建立交互，以实现共享无人机的起飞地理位置，从而达到根据无人机的起飞地理位置向控制终端返回无人机对应的飞行标签的目的，进而实现在客户端的社区空间上共享上述无人机的飞行标签的效果。
作为一种可选的方案，判断单元904包括以下至少之一：
1)第一判断模块，用于判断第一无人机的起飞地理位置的位置信息与已存储的起飞地理位置的位置信息是否一致；
2)第二判断模块，用于判断第一无人机的起飞地理位置的位置信息中的区域指示信息与已存储的起飞地理位置的位置信息中的区域指示信息是否一致，其中，区域指示信息为位置信息的一部分。
也就是说，相同的起飞地理位置的判断原则可以包括但不限于以下至少之一：位置信息完全一致、用于指示所在区域的区域指示信息(位置信息中的一部分)一致。
作为一种可选的方案，
1)第一发送单元906包括：第一发送模块，用于获取与第一无人机的起飞地理位置对应的地理名称，发送至少包括地理名称的第一飞行标签；
2)第二发送单元908包括：第二发送模块，用于获取与第一无人机的起飞地理位置对应的地理名称，存储第一无人机的起飞地理位置与获取到的地理名称的对应关系，发送至少包括地理名称的第二飞行标签。
可选地，在本实施例中，上述服务器可以但不限于根据获取到的无人机的起飞地理位置调整服务器数据库中已存储的起飞地理位置。具体而言，在获取到用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机的第二飞行标签，则获取与第一无人机的起飞地理位置对应的地理名称，并存储该第一无人机的起飞地理位置与获取到的地理名称的对应关系，以实现在数据库中添加新增的起飞地理位置的效果。
实施例5
根据本申请实施例，还提供了一种用于实施上述飞行标签的获取方法的飞行标签的获取终端，如图10所示，该终端包括：
1)处理器1002，设置为获取在第一无人机起飞时第一无人机的起飞地理位置。
2)通讯接口1004，与处理器1002连接，设置为将第一无人机的起飞地理位置发送给服务器；并获取服务器返回的飞行标签，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。
3)存储器1006，与存储器1002及通讯接口1004连接，设置为存储第一无人机的起飞地理位置及服务器返回的飞行标签。
可选地，本实施例中的具体示例可以参考上述实施例1和实施例2中所描 述的示例，本实施例在此不再赘述。
实施例6
根据本申请实施例，还提供了一种用于实施上述飞行标签的获取方法的飞行标签的获取服务器，如图11所示，该服务器包括：
1)通讯接口1102，设置为接收客户端发送的在第一无人机起飞时第一无人机的起飞地理位置，其中，客户端运行在控制终端上，用于对第一无人机的起飞进行控制；
2)处理器1104，与通讯接口1102连接，设置为判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置；若存在，则向客户端发送第一飞行标签，其中，第一飞行标签用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机；若不存在，则向客户端发送第二飞行标签，其中，第二飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机。
3)存储器1106，与通讯接口1102及处理器1104连接，设置为存储第一无人机的起飞地理位置及服务器返回的飞行标签。
可选地，本实施例中的具体示例可以参考上述实施例1和实施例2中所描述的示例，本实施例在此不再赘述。
实施例7
本申请的实施例还提供了一种存储介质。可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：
S1，获取在第一无人机起飞时第一无人机的起飞地理位置；
S2，将第一无人机的起飞地理位置发送给服务器；
S3，获取服务器返回的飞行标签，其中，飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是否是首架起飞的无人机。
可选地，在本实施例中，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，接收客户端发送的在第一无人机起飞时第一无人机的起飞地理位置， 其中，客户端运行在控制终端上，用于对第一无人机的起飞进行控制；
S2，判断已存储的起飞地理位置中是否存在与第一无人机的起飞地理位置相同的起飞地理位置；
S3，若存在，则向客户端发送第一飞行标签，其中，第一飞行标签用于指示在第一无人机的起飞地理位置上第一无人机不是首架起飞的无人机；
S4，若不存在，则向客户端发送第二飞行标签，其中，第二飞行标签用于指示在第一无人机的起飞地理位置上第一无人机是首架起飞的无人机。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例1和实施例2中所描述的示例，本实施例在此不再赘述。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
上述实施例中的集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在上述计算机可读取的存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在存储介质中，包括若干指令用以使得一台或多台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。
在本申请的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的客户端，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
以上所述仅是本申请的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本申请的保护范围。

Claims (17)

  1. 一种飞行标签的获取方法，其特征在于，包括：
    获取在第一无人机起飞时所述第一无人机的起飞地理位置；
    将所述第一无人机的起飞地理位置发送给服务器；以及
    获取所述服务器返回的飞行标签，其中，所述飞行标签用于指示所述第一无人机是否是首架在所述第一无人机的起飞地理位置上起飞的无人机。
  2. 根据权利要求1所述的方法，其特征在于，所述将所述第一无人机的起飞地理位置发送给服务器包括：
    在所述第一无人机起飞时，将所述第一无人机的起飞地理位置发送给所述服务器；或
    在所述第一无人机起飞之后，将所述第一无人机的起飞地理位置发送给所述服务器。
  3. 根据权利要求2所述的方法，其特征在于，在所述第一无人机起飞之后，将所述第一无人机的起飞地理位置发送给所述服务器包括：
    在所述第一无人机起飞之后，获取到发送指令，响应所述发送指令将所述第一无人机的起飞地理位置发送给所述服务器；或
    在所述第一无人机起飞之后，判断是否到达预设的发送时刻，在判断出到达所述发送时刻时，将所述第一无人机的起飞地理位置发送给所述服务器。
  4. 根据权利要求1所述的方法，其特征在于，获取在第一无人机起飞时所述第一无人机的起飞地理位置包括：
    获取在所述第一无人机起飞时所述第一无人机的地理位置，其中，将所述第一无人机的地理位置作为所述第一无人机的起飞地理位置；或
    获取在所述第一无人机起飞时控制终端的地理位置，其中，所述控制终端上运行的客户端对所述第一无人机的起飞进行控制，将所述控制终端的地理位置作为所述第一无人机的起飞地理位置。
  5. 根据权利要求1所述的方法，其特征在于，在获取所述服务器返回的飞行标签之后，还包括：
    在控制终端上运行的客户端中显示所述飞行标签，其中，所述客户端对所述第一无人机的起飞进行控制，所述飞行标签还用于指示以下至少之一：与所述第一无人机的起飞地理位置对应的地理名称、所述第一无人机起飞时的起飞日期、所述第一无人机起飞时的起飞时间。
  6. 根据权利要求1所述的方法，其特征在于，在将所述第一无人机的起飞地理位置发送给服务器之后，且在获取所述服务器返回的飞行标签之前，还包括：
    所述服务器接收所述第一无人机的起飞地理位置；
    所述服务器判断已存储的起飞地理位置中是否存在与所述第一无人机的起飞地理位置相同的起飞地理位置；
    若存在，则所述服务器发送第一飞行标签，其中，所述第一飞行标签用于指示在所述第一无人机的起飞地理位置上所述第一无人机不是首架起飞的无人机，所述飞行标签包括：所述第一飞行标签；以及
    若不存在，则所述服务器发送第二飞行标签，其中，所述第二飞行标签用于指示在所述第一无人机的起飞地理位置上所述第一无人机是首架起飞的无人机，所述飞行标签包括：所述第二飞行标签。
  7. 一种飞行标签的获取方法，其特征在于，包括：
    接收客户端发送的在第一无人机起飞时所述第一无人机的起飞地理位置，其中，所述客户端运行在控制终端上，用于对所述第一无人机的起飞进行控制；
    判断已存储的起飞地理位置中是否存在与所述第一无人机的起飞地理 位置相同的起飞地理位置；
    若存在，则向所述客户端发送第一飞行标签，其中，所述第一飞行标签用于指示在所述第一无人机的起飞地理位置上所述第一无人机不是首架起飞的无人机；以及
    若不存在，则向所述客户端发送第二飞行标签，其中，所述第二飞行标签用于指示在所述第一无人机的起飞地理位置上所述第一无人机是首架起飞的无人机。
  8. 根据权利要求7所述的方法，其特征在于，所述判断已存储的起飞地理位置中是否存在与所述第一无人机的起飞地理位置相同的起飞地理位置包括：
    判断所述第一无人机的起飞地理位置的位置信息与所述已存储的起飞地理位置的位置信息是否一致；或
    判断所述第一无人机的起飞地理位置的位置信息中的区域指示信息与所述已存储的起飞地理位置的位置信息中的区域指示信息是否一致，其中，所述区域指示信息为所述位置信息的一部分。
  9. 根据权利要求7所述的方法，其特征在于，
    所述向所述客户端发送第一飞行标签包括：获取与所述第一无人机的起飞地理位置对应的地理名称，发送至少包括所述地理名称的所述第一飞行标签；
    所述向所述客户端发送第二飞行标签包括：获取与所述第一无人机的起飞地理位置对应的地理名称，存储所述第一无人机的起飞地理位置与获取到的所述地理名称的对应关系，发送至少包括所述地理名称的所述第二飞行标签。
  10. 一种飞行标签的获取终端，其特征在于，包括：
    第一获取单元，用于获取在第一无人机起飞时所述第一无人机的起飞地理位置；
    第一发送单元，用于将所述第一无人机的起飞地理位置发送给服务器； 以及
    第二获取单元，用于获取所述服务器返回的飞行标签，其中，所述飞行标签用于指示在所述第一无人机的起飞地理位置上所述第一无人机是否是首架起飞的无人机。
  11. 根据权利要求10所述的终端，其特征在于，所述第一发送单元包括：
    第一发送模块，用于在所述第一无人机起飞时，将所述第一无人机的起飞地理位置发送给所述服务器；或
    第二发送模块，用于在所述第一无人机起飞之后，将所述第一无人机的起飞地理位置发送给所述服务器。
  12. 根据权利要求11所述的终端，其特征在于，所述第二发送模块包括：
    第一发送子模块，用于在所述第一无人机起飞之后，获取到发送指令，响应所述发送指令将所述第一无人机的起飞地理位置发送给所述服务器；或
    第二发送子模块，用于在所述第一无人机起飞之后，判断是否到达预设的发送时刻，在判断出到达所述发送时刻时，将所述第一无人机的起飞地理位置发送给所述服务器。
  13. 根据权利要求10所述的终端，其特征在于，所述第一获取单元包括：
    第三获取模块，用于获取在所述第一无人机起飞时所述第一无人机的地理位置，其中，将所述第一无人机的地理位置作为所述第一无人机的起飞地理位置；或
    第四获取模块，用于获取在所述第一无人机起飞时控制终端的地理位置，其中，所述控制终端上运行的客户端对所述第一无人机的起飞进行控制，将所述控制终端的地理位置作为所述第一无人机的起飞地理位置。
  14. 根据权利要求10所述的终端，其特征在于，还包括：
    显示单元，用于在获取所述服务器返回的飞行标签之后，在控制终端上运行的客户端中显示所述飞行标签，其中，所述客户端对所述第一无人 机的起飞进行控制，所述飞行标签还用于指示以下至少之一：与所述第一无人机的起飞地理位置对应的地理名称、所述第一无人机起飞时的起飞日期、所述第一无人机起飞时的起飞时间。
  15. 一种飞行标签的获取服务器，其特征在于，包括：
    接收单元，用于接收客户端发送的在第一无人机起飞时所述第一无人机的起飞地理位置，其中，所述客户端运行在控制终端上，用于对所述第一无人机的起飞进行控制；
    判断单元，用于判断已存储的起飞地理位置中是否存在与所述第一无人机的起飞地理位置相同的起飞地理位置；
    第一发送单元，用于在存在与所述第一无人机的起飞地理位置相同的起飞地理位置时，向所述客户端发送第一飞行标签，其中，所述第一飞行标签用于指示在所述第一无人机的起飞地理位置上所述第一无人机不是首架起飞的无人机；以及
    第二发送单元，用于在不存在与所述第一无人机的起飞地理位置相同的起飞地理位置时，向所述客户端发送第二飞行标签，其中，所述第二飞行标签用于指示在所述第一无人机的起飞地理位置上所述第一无人机是首架起飞的无人机。
  16. 根据权利要求15所述的服务器，其特征在于，所述判断单元至少包括：
    第一判断模块，用于判断所述第一无人机的起飞地理位置的位置信息与所述已存储的起飞地理位置的位置信息是否一致；或
    第二判断模块，用于判断所述第一无人机的起飞地理位置的位置信息中的区域指示信息与所述已存储的起飞地理位置的位置信息中的区域指示信息是否一致，其中，所述区域指示信息为所述位置信息的一部分。
  17. 根据权利要求15所述的服务器，其特征在于，
    所述第一发送单元包括：第一发送模块，用于获取与所述第一无人机的起飞地理位置对应的地理名称，发送至少包括所述地理名称的所述第一飞行标签；
    所述第二发送单元包括：第二发送模块，用于获取与所述第一无人机的起飞地理位置对应的地理名称，存储所述第一无人机的起飞地理位置与获取到的所述地理名称的对应关系，发送至少包括所述地理名称的所述第二飞行标签。
PCT/CN2017/078805 2016-04-01 2017-03-30 飞行标签的获取方法和终端及服务器 WO2017167230A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/991,872 US10957205B2 (en) 2016-04-01 2018-05-29 Flight tag obtaining method, terminal, and server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610203591.1A CN105677930B (zh) 2016-04-01 2016-04-01 飞行标签的获取方法和终端及服务器
CN201610203591.1 2016-04-01

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/991,872 Continuation US10957205B2 (en) 2016-04-01 2018-05-29 Flight tag obtaining method, terminal, and server

Publications (1)

Publication Number Publication Date
WO2017167230A1 true WO2017167230A1 (zh) 2017-10-05

Family

ID=56225234

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/078805 WO2017167230A1 (zh) 2016-04-01 2017-03-30 飞行标签的获取方法和终端及服务器

Country Status (3)

Country Link
US (1) US10957205B2 (zh)
CN (1) CN105677930B (zh)
WO (1) WO2017167230A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105677930B (zh) * 2016-04-01 2018-07-03 腾讯科技（深圳）有限公司 飞行标签的获取方法和终端及服务器
CN105979146B (zh) * 2016-06-22 2019-12-10 韦程耀 无人机的航拍控制系统
JP6757026B2 (ja) * 2018-02-28 2020-09-16 株式会社ナイルワークス ドローン、操作機、ドローンの制御方法、操作機の制御方法、および、ドローン制御プログラム
KR102511260B1 (ko) * 2018-08-21 2023-03-21 엘지전자 주식회사 차량용 사용자 인터페이스 장치 및 서비스 정보 제공 시스템
US11355022B2 (en) * 2019-09-13 2022-06-07 Honeywell International Inc. Systems and methods for computing flight controls for vehicle landing
US11817000B2 (en) * 2020-12-10 2023-11-14 Rockwell Collins, Inc. System and method to reduce runway occupancy time using pseudo threshold
CN113407926B (zh) * 2021-06-04 2022-10-21 北京三快在线科技有限公司 设备匹配方法、装置、设备及计算机可读存储介质
CN113246136B (zh) * 2021-06-07 2021-11-16 深圳市普渡科技有限公司 机器人、地图构建方法、装置和存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014146169A1 (en) * 2013-03-19 2014-09-25 Tushare Australia Pty Ltd Systems and methods for managing sending of items
CN104679873A (zh) * 2015-03-09 2015-06-03 深圳市道通智能航空技术有限公司 一种飞行器追踪方法和系统
CN104950903A (zh) * 2015-06-10 2015-09-30 杨珊珊 一种具有飞行任务模式的飞行器、飞行器控制方法及系统
CN105206114A (zh) * 2015-08-10 2015-12-30 华为技术有限公司 飞行控制、许可、安全维护方法和装置、服务器、飞行器
CN105398571A (zh) * 2015-12-21 2016-03-16 谭圆圆 基于无人飞行器的点对点送达系统及其送达方法
CN105677930A (zh) * 2016-04-01 2016-06-15 腾讯科技（深圳）有限公司 飞行标签的获取方法和终端及服务器

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014115139A1 (en) * 2013-01-23 2014-07-31 Iatas (Automatic Air Traffic Control) Ltd System and methods for automated airport air traffic control services
US10586464B2 (en) * 2015-07-29 2020-03-10 Warren F. LeBlanc Unmanned aerial vehicles
WO2017100579A1 (en) * 2015-12-09 2017-06-15 Dronesense Llc Drone flight operations

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014146169A1 (en) * 2013-03-19 2014-09-25 Tushare Australia Pty Ltd Systems and methods for managing sending of items
CN104679873A (zh) * 2015-03-09 2015-06-03 深圳市道通智能航空技术有限公司 一种飞行器追踪方法和系统
CN104950903A (zh) * 2015-06-10 2015-09-30 杨珊珊 一种具有飞行任务模式的飞行器、飞行器控制方法及系统
CN105206114A (zh) * 2015-08-10 2015-12-30 华为技术有限公司 飞行控制、许可、安全维护方法和装置、服务器、飞行器
CN105398571A (zh) * 2015-12-21 2016-03-16 谭圆圆 基于无人飞行器的点对点送达系统及其送达方法
CN105677930A (zh) * 2016-04-01 2016-06-15 腾讯科技（深圳）有限公司 飞行标签的获取方法和终端及服务器

Also Published As

Publication number Publication date
CN105677930B (zh) 2018-07-03
US10957205B2 (en) 2021-03-23
CN105677930A (zh) 2016-06-15
US20180276997A1 (en) 2018-09-27

Similar Documents

Publication Publication Date Title
WO2017167230A1 (zh) 飞行标签的获取方法和终端及服务器
US11566915B2 (en) Method, device and system for processing a flight task
US11182609B2 (en) Method and apparatus for recognition and matching of objects depicted in images
US20190287311A1 (en) Coarse relocalization using signal fingerprints
CN109756787B (zh) 虚拟礼物的生成方法、装置及虚拟礼物的赠送系统
TWI787183B (zh) 終端、應用資訊的顯示方法及裝置
US11496778B2 (en) Methods, systems, and devices for identifying viewed action of a live event and adjusting a group of resources to augment presentation of the action of the live event
US20190251719A1 (en) System and method for augmented reality map
CN110703913B (zh) 对象交互方法和装置、存储介质及电子装置
US20220382051A1 (en) Virtual reality interaction method, device and system
WO2017124987A1 (zh) 运动轨迹的分享方法、装置和存储介质
RU2019113320A (ru) Многопользовательское взаимодействие в рамках автономной услуги на основе дополненной реальности
WO2021180104A1 (zh) 消息推送方法和系统、客户端、存储介质及处理器
US20140248588A1 (en) Portable device to control simulated aircraft in air traffic control training system
WO2017054327A1 (zh) 确定图像的待叠加区域、叠加图像、图片呈现方法和装置
TW201823983A (zh) 移動物件的虛擬訊息建立方法、搜尋方法與應用系統
CN113327343B (zh) 一种飞行日志上传方法、装置及移动终端、无人机
US11308674B2 (en) Dynamic image compositing method and apparatus, terminal and storage medium
WO2017143896A1 (zh) 线路信息互动方法、电子设备和计算机存储介质
US20200358940A1 (en) Following control method, control terminal, and unmanned aerial vehicle
US20220124143A1 (en) System for providing synchronized sharing of augmented reality content in real time across multiple devices
CN104244075A (zh) 一种媒体信息分享方法和系统
CN103927780B (zh) 一种多显卡渲染的方法与三维显示系统
CN113596488B (zh) 直播间的展示方法、装置、电子设备和存储介质
US20170223416A1 (en) Method and apparatus for digital media control rooms

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17773260

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17773260

Country of ref document: EP

Kind code of ref document: A1