CN106100721A

CN106100721A - Method, server, remote controller and the system that unmanned plane and remote controller are matched

Info

Publication number: CN106100721A
Application number: CN201610486132.9A
Authority: CN
Inventors: 刘波; 李文超; 萧延强
Original assignee: GUANGZHOU XAIRCRAFT ELECTRONIC TECHNOLOGY Co Ltd
Current assignee: Guangzhou Xaircraft Technology Co Ltd
Priority date: 2016-06-24
Filing date: 2016-06-24
Publication date: 2016-11-09
Anticipated expiration: 2036-06-24
Also published as: CN106100721B

Abstract

Embodiments provide a kind of method, server, remote controller and system that unmanned plane and remote controller are matched, wherein said system at least includes: server, remote controller and unmanned plane, wherein, described server is in the unmanned plane binding judging described remote controller and need pairing, then obtain the pairing parameter corresponding with pairing request, and return described pairing parameter to described remote controller；Described remote controller is used for generating pairing request, and sends described pairing request to server, and, the communication configuration of device it is remotely controlled according to pairing parameter；Described unmanned plane, for obtaining pairing parameter from server or remote controller, and carries out the communication configuration of described unmanned plane according to described pairing parameter.The embodiment of the present invention can improve the pairing accuracy rate of unmanned plane and remote controller, and reduces the environmental requirement of pairing process.

Description

Method for pairing unmanned aerial vehicle and remote controller, server, remote controller and system

Technical Field

The invention relates to the technical field of unmanned aerial vehicles, in particular to a pairing system for pairing unmanned aerial vehicles, a server for pairing unmanned aerial vehicles, a remote controller for controlling unmanned aerial vehicles, an unmanned aerial vehicle and a method for pairing the unmanned aerial vehicles and the remote controller.

Background

An Unmanned Aerial Vehicle (UAV) is an Unmanned Aerial Vehicle operated by a radio remote control device and a self-contained program control device. The unmanned aerial vehicle has wide application and is often applied to the industries of city management, agriculture, geology, meteorology, electric power, emergency and disaster relief, video shooting and the like. For example, drones may be used in agriculture to spray agricultural products with pesticides (or fertilizers).

At present, a remote controller can be adopted to control the unmanned aerial vehicle. However, if the remote controller is to control the drone, the pairing between the drone and the remote controller must be completed first. In the prior art, the pairing of the drone and the remote controller is usually accomplished in the following manner:

the user usually needs to transfer the remote controller to a dedicated pairing communication channel, and after the unmanned aerial vehicle is powered on, the user transfers the unmanned aerial vehicle to the same pairing communication channel as the remote controller, so that the remote controller and the unmanned aerial vehicle enter a pairing state at the same time.

The user enables the remote controller to send a pairing request in a broadcast mode through operating the buttons, and the pairing request comprises pairing parameters such as a communication channel number, a remote controller address and an unmanned aerial vehicle address.

And after the unmanned aerial vehicle corresponding to the address of the unmanned aerial vehicle receives the pairing request, recording the pairing parameters and returning pairing confirmation information to the remote controller.

And after the remote controller receives the confirmation information, the pairing is finished, and the two parties reset the communication setting according to the pairing parameters to recover normal communication.

However, when the inventor carries out the prior art, the following defects exist in the prior art:

when having many remote controllers or many unmanned aerial vehicles to get into the state of pairing simultaneously in the region, the communication configuration of multiunit remote controller and unmanned aerial vehicle appears repeatedly easily in the region to form communication channel and interfere with each other, lead to pairing to make mistakes, influence and pair the success rate. In addition, the communication channel interferes with each other, so that the unmanned aerial vehicle cannot operate, and even safety accidents occur.

Further, among the prior art, the remote controller all need carry out the above-mentioned pairing process of pairing the parameter at every turn controlling unmanned aerial vehicle and controlling different unmanned aerial vehicle at every turn, to utilizing unmanned aerial vehicle to carry out the plant protection operation, because unmanned aerial vehicle's operation frequency is high, prior art will seriously influence the holistic operating efficiency of unmanned aerial vehicle.

Disclosure of Invention

In view of the above, embodiments of the present invention are proposed in order to provide a pairing system for pairing drones, which overcomes or at least partially solves the above problems, and a corresponding server for pairing drones, a remote controller for controlling drones, a drone and a method for pairing a drone and a remote controller.

In order to solve the above problem, an embodiment of the present invention discloses a pairing system for pairing an unmanned aerial vehicle, where the pairing system at least includes: a server, a remote control, and a drone, wherein,

the server is used for acquiring a pairing parameter corresponding to the pairing request and returning the pairing parameter to the remote controller if the remote controller is judged to be bound with the unmanned aerial vehicle needing pairing after receiving the pairing request sent by the remote controller;

the remote controller is used for generating a pairing request, sending the pairing request to a server, carrying out communication configuration on the remote controller according to received pairing parameters corresponding to the pairing request, sending confirmation information to the unmanned aerial vehicle needing to be paired after the communication configuration is finished, and judging that the unmanned aerial vehicle needing to be paired is successfully paired after receiving confirmation response information returned by the unmanned aerial vehicle needing to be paired;

the unmanned aerial vehicle is used for obtaining pairing parameters from the server or the remote controller, carrying out communication configuration of the unmanned aerial vehicle according to the pairing parameters, and returning corresponding confirmation response information to the remote controller if confirmation information sent by the remote controller is received after the communication configuration is completed.

Preferably, the system further comprises a registration terminal;

the registration terminal is used for acquiring unmanned aerial vehicle identifications of a plurality of unmanned aerial vehicles and/or remote controller identifications of a plurality of remote controllers and sending the unmanned aerial vehicle identifications and/or the remote controller identifications to the server;

the server is further used for receiving the unmanned aerial vehicle identification and/or the remote controller identification and registering the unmanned aerial vehicle and/or the remote controller.

Preferably, the server includes:

the registration relation judging module is used for judging whether the unmanned aerial vehicle identification and/or the remote controller identification exist in a preset registration relation database or not, and if the unmanned aerial vehicle identification and/or the remote controller identification exist, the first prompting module is called; if not, calling a registration module; the preset registration relation database stores at least one unmanned aerial vehicle identifier and/or remote controller identifier registered by the server;

the registration module is used for recording the unmanned aerial vehicle identification in the registration relation database so as to register the unmanned aerial vehicle, and/or recording the remote controller identification in the registration relation database so as to register the remote controller;

the first prompting module is used for generating first error prompting information, returning the first error prompting information to a registration terminal, and displaying the first error prompting information by the registration terminal, wherein the first error prompting information is used for prompting that the unmanned aerial vehicle and/or the remote controller are registered.

Preferably, the registration terminal is integrated in the same device as the remote controller.

Preferably, the server is further configured to assign a unique communication address to the drone and/or remote control.

Preferably, the server is further configured to organize the drone identities of the drones to which the communication addresses have been assigned into a drone pairing list, and send the drone pairing list to the remote controller, and the method includes:

the first startup information receiving module is used for receiving startup information sent by the remote controller, and the startup information comprises a remote controller identifier of the remote controller;

the download judging module is used for judging whether the remote controller has a download record aiming at the unmanned aerial vehicle pairing list or not based on the remote controller identification, if so, the update confirming module is called, and if not, the list sending module is called;

the list sending module is used for sending the unmanned aerial vehicle pairing list which is latest at the current moment to the remote controller;

the updating confirmation module is used for acquiring the downloading time of the unmanned aerial vehicle pairing list which is downloaded last time by the remote controller corresponding to the remote controller identification, judging whether the unmanned aerial vehicle pairing list is updated or not in the time range from the downloading time to the current time, and calling the list sending module if the unmanned aerial vehicle pairing list is updated; and if not, generating a determination instruction, and sending the determination instruction to the remote controller corresponding to the remote controller identification.

Preferably, the remote controller includes:

the list display module is used for displaying the unmanned aerial vehicle pairing list to a user;

the command detection module is used for detecting the unmanned aerial vehicle identification which is selected by the user from the unmanned aerial vehicle pairing list and needs to be paired, and receiving a pairing command initiated by the user according to the unmanned aerial vehicle identification which needs to be paired;

and the pairing request generating module is used for generating a pairing request based on the pairing instruction and sending the pairing request to a server, wherein the pairing request comprises the unmanned aerial vehicle identification needing to be paired and the remote controller identification.

Preferably, the pairing request further includes current location information of the remote controller, and the pairing parameters include a communication address of the unmanned aerial vehicle to be paired, a communication address of the remote controller, and a communication channel number for the unmanned aerial vehicle to be paired to communicate with the remote controller;

the server further comprises:

the pairing judgment module is used for judging whether the unmanned aerial vehicle identification needing to be paired has a binding relationship with other remote controller identifications based on the pairing request; if yes, calling a second prompting module, and if not, calling a binding module;

the second prompt module is used for generating second error prompt information and returning the second error prompt information to the remote controller;

the binding module is used for generating a binding relationship between the unmanned aerial vehicle identification needing to be paired and the remote controller identification so as to bind the remote controller and the unmanned aerial vehicle needing to be paired, and determining a communication channel number for communication between the unmanned aerial vehicle corresponding to the unmanned aerial vehicle identification needing to be paired and the remote controller according to the current position information of the remote controller; and sending the communication address of the unmanned aerial vehicle needing to be paired, the communication address of the remote controller and the communication channel number to the remote controller.

Preferably, the server further comprises:

the second starting-up information receiving module is used for receiving starting-up information sent by the unmanned aerial vehicles needing to be paired, and the starting-up information comprises the identification of the unmanned aerial vehicles needing to be paired;

and the pairing parameter acquisition module is used for acquiring the pairing parameters corresponding to the unmanned aerial vehicle identification needing to be paired and sending the pairing parameters to the unmanned aerial vehicle needing to be paired.

The embodiment of the invention also discloses a server for pairing the unmanned aerial vehicles, wherein the server is the server in the pairing system.

The embodiment of the invention also discloses a remote controller for controlling the unmanned aerial vehicle, wherein the remote controller is the remote controller in the pairing system.

The embodiment of the invention also discloses an unmanned aerial vehicle, which is the unmanned aerial vehicle in the pairing system.

The embodiment of the invention also discloses a method for pairing the unmanned aerial vehicle and the remote controller, wherein the unmanned aerial vehicle is controlled by the remote controller, and the unmanned aerial vehicle and the remote controller are connected with the server, and the method comprises the following steps:

the server receives a pairing request sent by the remote controller;

if the remote controller is judged to be bound with the unmanned aerial vehicle needing to be paired, acquiring pairing parameters corresponding to the pairing request;

and returning the pairing parameters to the remote controller, wherein the remote controller is used for carrying out communication configuration on the remote controller according to the pairing parameters.

Preferably, the method further comprises:

and receiving an unmanned aerial vehicle identifier and/or the remote controller identifier sent by a registration terminal, and registering the unmanned aerial vehicle and/or the remote controller.

Preferably, said registering said drone and/or said remote control comprises:

judging whether the unmanned aerial vehicle identification and/or the remote controller identification exist in a preset registration relation database, wherein at least one unmanned aerial vehicle identification and/or remote controller identification registered by a server is stored in the preset registration relation database;

if the unmanned aerial vehicle identification does not exist, recording the unmanned aerial vehicle identification in the registration relation database so as to register the unmanned aerial vehicle, and/or recording the remote controller identification in the registration relation database so as to register the remote controller;

and if the unmanned aerial vehicle and/or the remote controller exist, generating first error prompt information, returning the first error prompt information to a registration terminal, and displaying the first error prompt information by the registration terminal, wherein the first error prompt information is used for prompting that the unmanned aerial vehicle and/or the remote controller have been registered.

Preferably, the method further comprises:

assigning a unique communication address to the drone and/or remote control.

Preferably, the method further comprises:

organizing unmanned aerial vehicle identifications of unmanned aerial vehicles with allocated communication addresses into an unmanned aerial vehicle pairing list, and sending the unmanned aerial vehicle pairing list to the remote controller.

Preferably, the step of organizing the drone identities of the drones to which the communication addresses have been assigned into a drone pairing list, and the step of sending the drone pairing list to the remote controller includes:

receiving startup information sent by the remote controller, wherein the startup information comprises a remote controller identifier of the remote controller;

determining whether the remote control has a download record for the pairing list of unmanned aerial vehicles based on the remote control identification;

if not, sending the latest unmanned aerial vehicle pairing list at the current moment to the remote controller;

if yes, obtaining the downloading time of the remote controller corresponding to the remote controller identification for downloading the unmanned aerial vehicle pairing list for the last time, judging whether the unmanned aerial vehicle pairing list is updated or not within the time range from the downloading time to the current time, and if yes, sending the latest unmanned aerial vehicle pairing list at the current moment to the remote controller; and if not, generating a determination instruction, and sending the determination instruction to the remote controller corresponding to the remote controller identification.

Preferably, the pairing request includes current location information of the remote controller, and the pairing parameters include a communication address of the unmanned aerial vehicle to be paired, a communication address of the remote controller, and a communication channel number for the unmanned aerial vehicle to be paired to communicate with the remote controller;

the method further comprises the following steps:

based on the pairing request, judging whether the unmanned aerial vehicle identification needing to be paired has a binding relationship with other remote controller identifications;

if so, generating second error prompt information and returning the second error prompt information to the remote controller;

if not, generating a binding relationship between the unmanned aerial vehicle identification needing to be paired and the remote controller identification so as to bind the remote controller and the unmanned aerial vehicle needing to be paired, and determining a communication channel number for communication between the unmanned aerial vehicle corresponding to the unmanned aerial vehicle identification needing to be paired and the remote controller according to the current position information of the remote controller; and sending the communication address of the unmanned aerial vehicle needing to be paired, the communication address of the remote controller and the communication channel number to the remote controller.

Preferably, the method further comprises:

receiving starting-up information sent by the unmanned aerial vehicles needing to be paired, wherein the starting-up information comprises the identification of the unmanned aerial vehicles needing to be paired;

and acquiring a pairing parameter corresponding to the identification of the unmanned aerial vehicle needing to be paired, and sending the pairing parameter to the unmanned aerial vehicle needing to be paired, wherein the unmanned aerial vehicle is used for carrying out communication configuration on the unmanned aerial vehicle according to the pairing parameter.

the remote controller generates a pairing request and sends the pairing request to a server;

receiving pairing parameters corresponding to the pairing request returned by a server, wherein the pairing parameters are acquired by the server after the server receives the pairing request sent by the remote controller and the remote controller is judged to be bound with the unmanned aerial vehicle to be paired, and the pairing parameters correspond to the pairing request;

and carrying out communication configuration on the remote controller according to the pairing parameters, sending confirmation information to the unmanned aerial vehicles needing to be paired after the communication configuration is finished, and judging that the unmanned aerial vehicles needing to be paired are successfully paired after receiving confirmation response information returned by the unmanned aerial vehicles needing to be paired.

Preferably, before the step of generating a pairing request by the remote controller and sending the pairing request to the server, the method further includes:

and acquiring an unmanned aerial vehicle pairing list, wherein the unmanned aerial vehicle pairing list is a list formed by organizing unmanned aerial vehicle identifications of unmanned aerial vehicles with assigned communication addresses after the server assigns unique communication addresses to the unmanned aerial vehicles and/or the remote controllers.

Preferably, the step of obtaining a pairing list of drones includes:

when a remote controller is powered on and started, sending startup information to a server, wherein the startup information comprises a remote controller identifier of the remote controller;

receiving a pairing list of the unmanned aerial vehicle which is sent by the server and is latest at the current moment; or receiving a determining instruction returned by the server, and obtaining the unmanned aerial vehicle pairing list downloaded last time according to the determining instruction.

Preferably, the method further comprises:

and selecting the unmanned aerial vehicle identification needing pairing from the unmanned aerial vehicle pairing list.

Preferably, the step of selecting the identity of the drone to be paired from the pairing list of drones comprises:

displaying the unmanned aerial vehicle pairing list to a user;

detecting an unmanned aerial vehicle identifier which is selected by a user from the unmanned aerial vehicle pairing list and needs to be paired, and receiving a pairing instruction initiated by the user according to the unmanned aerial vehicle identifier which needs to be paired;

generating a pairing request based on the pairing instruction, and sending the pairing request to a server, wherein the pairing request comprises the unmanned aerial vehicle identification needing to be paired and the remote controller identification.

Preferably, the pairing parameters include a communication address of the unmanned aerial vehicle to be paired, a communication address of the remote controller, and a communication channel number for the unmanned aerial vehicle to be paired to communicate with the remote controller.

The embodiment of the invention has the following advantages:

in the embodiment of the invention, the server is adopted to register the unmanned aerial vehicle and/or the remote controller, so that the possibility that the unmanned aerial vehicle is controlled by an unknown remote controller is avoided, the possibility that the remote controller controls the unknown unmanned aerial vehicle by mistake is also avoided, and the flight safety of the unmanned aerial vehicle is greatly ensured.

Further, the server distributes communication addresses for the unmanned aerial vehicle and/or the remote controller, pairing parameters are returned to the remote controller according to pairing requests of the remote controller, the remote controller is used for carrying out communication configuration, the unmanned aerial vehicle can obtain the pairing parameters from the server or the remote controller, the unmanned aerial vehicle is subjected to communication configuration according to the pairing parameters, the pairing requests are not required to be directly broadcasted by the remote controller, when multiple unmanned aerial vehicles and multiple remote controllers work simultaneously in an area, the problem of communication channel interference and the problem of pairing errors are avoided, and similarly, the environmental requirements in the pairing process are also reduced.

Drawings

Fig. 1 is a block diagram of a first embodiment of a pairing system for pairing unmanned aerial vehicles according to the present invention;

fig. 2 is a block diagram of a second embodiment of a pairing system for pairing unmanned aerial vehicles according to the present invention;

fig. 3 is a schematic structural diagram of a server in a second embodiment of the pairing system for pairing the drones according to the present invention;

fig. 4 is a schematic structural diagram of a remote controller in a second embodiment of the pairing system for pairing the unmanned aerial vehicles according to the present invention;

fig. 5 is a flowchart illustrating steps of a first embodiment of a method for pairing a drone and a remote control according to the present invention;

fig. 6 is a flowchart illustrating steps of a second embodiment of a method for pairing an unmanned aerial vehicle and a remote controller according to the present invention.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.

One of the core ideas of the embodiment of the invention is that the server is adopted to distribute communication addresses and communication channel numbers for the unmanned aerial vehicles and the remote controllers, the remote controllers are not required to directly broadcast pairing requests, when a plurality of unmanned aerial vehicles and a plurality of remote controllers in an area operate simultaneously, the problems of interference and pairing errors of the original pairing are avoided, and similarly, the environmental requirements of the pairing process are also reduced.

Referring to fig. 1, a block diagram of a first embodiment of a pairing system for pairing drones according to the present invention is shown. In an embodiment of the present invention, the pairing system may include at least: a server 10, a remote control 20, and a drone 30, wherein,

the server 10 is configured to, after receiving the pairing request sent by the remote controller 20, if it is determined that the remote controller 20 is bound to the unmanned aerial vehicle 30 that needs to be paired, obtain a pairing parameter corresponding to the pairing request, and return the pairing parameter to the remote controller 20;

the remote controller 20 is configured to generate a pairing request, send the pairing request to the server 10, perform communication configuration on the remote controller 20 according to received pairing parameters corresponding to the pairing request, send confirmation information to the unmanned aerial vehicle 30 to be paired after the communication configuration is completed, and determine that the pairing with the unmanned aerial vehicle 30 to be paired is successful after receiving confirmation response information returned by the unmanned aerial vehicle 30 to be paired;

the unmanned aerial vehicle 30 is configured to obtain pairing parameters from the server 10 or the remote controller 20, perform communication configuration of the unmanned aerial vehicle 30 according to the pairing parameters, and return corresponding confirmation response information to the remote controller 20 if confirmation information sent by the remote controller 20 is received after the communication configuration is completed.

In the embodiment of the invention, the server is adopted to complete the pairing of the unmanned aerial vehicle and the remote controller, so that when a plurality of unmanned aerial vehicles and a plurality of remote controllers in an area operate simultaneously, the problems of communication channel interference and pairing error are avoided, the possibility that the unmanned aerial vehicle is controlled by an unknown remote controller is eliminated, the possibility that the remote controller controls the unknown unmanned aerial vehicle mistakenly is also eliminated, and the flight safety of the unmanned aerial vehicle is greatly ensured.

Referring to fig. 2, a block diagram of a second embodiment of the pairing system for pairing the drones according to the present invention is shown. In an embodiment of the present invention, the pairing system may include at least: server 10, remote control 20, drone 30 and registration terminal 40.

In a specific implementation, the server 10, the registration terminal 40, the remote controller 20, and the drone 30 may communicate with each other, and the communication manner may include, but is not limited to: wireless communication protocols (e.g., WIFI, GPRS, 3G/4G), bluetooth, wireless waves, etc.

The registration terminal 40 is configured to acquire the unmanned aerial vehicle identifiers of multiple unmanned aerial vehicles 30 and/or the remote controller identifiers of multiple remote controllers 20, and send the unmanned aerial vehicle identifiers and/or the remote controller identifiers to the server 10;

the server 10 is configured to allocate a communication address to the unmanned aerial vehicle 30 and/or the remote controller 20, receive the unmanned aerial vehicle identifier and/or the remote controller identifier, register the unmanned aerial vehicle 30 and/or the remote controller 20, organize the unmanned aerial vehicle identifier of the unmanned aerial vehicle 30 to which the communication address has been allocated into an unmanned aerial vehicle pairing list, send the unmanned aerial vehicle pairing list to the remote controller 20, and, after receiving a pairing request sent by the remote controller 20, if it is determined that the remote controller 20 is bound to an unmanned aerial vehicle 30 that needs to be paired, obtain a pairing parameter corresponding to the pairing request, and return the pairing parameter to the remote controller 20;

the remote controller 20 is configured to select an unmanned aerial vehicle identifier to be paired from the unmanned aerial vehicle pairing list, generate a pairing request according to the unmanned aerial vehicle identifier to be paired, send the pairing request to the server 10, perform communication configuration of the remote controller 20 according to received pairing parameters corresponding to the pairing request, send confirmation information to the unmanned aerial vehicle 30 to be paired after the communication configuration is completed, and determine that the pairing with the unmanned aerial vehicle 30 to be paired is successful after receiving confirmation response information returned by the unmanned aerial vehicle 30 to be paired;

The pairing system can comprise a registration terminal 40, and the unmanned aerial vehicle 30 and the remote controller 20 can be registered to the server 10 by adopting the registration terminal 40.

In practice, when the unmanned aerial vehicle 30 is used to perform a job, the job may include a plurality of job groups, and the registration terminals 40 correspond to the job groups for performing the job using the unmanned aerial vehicle 30, that is, one job group corresponds to one or more registration terminals 40, or one registration terminal 40 corresponds to one or more job groups. In the pairing system, the correspondence relationship of the job group identification of the job group and the identification of the registration terminal 40 may be saved.

An operator having a designated authority in the work group (for example, a group leader of the work group) may use the registration terminal 40, acquire the drone identification of the drone 30 and/or the remote controller identification of the remote controller 20 that currently needs to be paired with the registration terminal 40, and then the registration terminal 40 may transmit the acquired drone identification and/or the remote controller identification to the server 10.

It should be noted that the above-mentioned unmanned aerial vehicle identification is the only identification of the identity of mark unmanned aerial vehicle 30, and the above-mentioned remote controller identification is the only identification of the identity of mark remote controller 20.

In a specific implementation, the registration terminal 40 may obtain the drone identifier of the drone 30 and/or the remote controller identifier of the remote controller 20 in various manners, for example, taking the drone 30 as an example, the drone identifier of the current drone 30 may be obtained in several manners as follows:

the first method is as follows: set up the data plate on unmanned aerial vehicle 30, this data plate has recorded this unmanned aerial vehicle 30's unmanned aerial vehicle sign. The registration terminal 40 has an identification input interface, and a user (i.e., an operator having an operation authority) can input the identification of the drone recorded on the nameplate of the drone 30 in the identification input interface of the registration terminal 40.

The second method comprises the following steps: the unmanned aerial vehicle 30 is provided with an image recorded with an unmanned aerial vehicle identifier, the registration terminal 40 is provided with a camera, and an operator can read the unmanned aerial vehicle identifier in the image of the unmanned aerial vehicle 30 by adopting the camera on the registration terminal 40 in an image recognition mode.

The third method comprises the following steps: an NFC (Near Field Communication) tag is set on the drone 30, which is a short-range high-frequency radio technology and operates within a distance of 20 cm at a frequency of 13.56MHz, an drone identifier of the drone 30 is stored in the NFC tag, an NFC card reader is set on the registration terminal 40, and an operator reads the NFC tag on the drone 30 through the NFC card reader on the registration terminal 40 to obtain the drone identifier of the drone 30.

The method is as follows: set up one-dimensional code or two-dimensional code label on unmanned aerial vehicle 30, this one-dimensional code or two-dimensional code label carry unmanned aerial vehicle sign of unmanned aerial vehicle 30, set up one-dimensional code and two-dimensional code reading device on registration terminal 40, operating personnel reads one-dimensional code or two-dimensional code label in unmanned aerial vehicle 30 through this reading device, obtains the unmanned aerial vehicle sign.

It should be noted that the above-mentioned manner is only an exemplary illustration of the embodiment of the present invention, and those skilled in the art may also use other manners to obtain the drone identifier of the drone 30 through the registration terminal 40, for example, the registration terminal 40 may read the drone identifier of the drone 30 through bluetooth, sound wave, and the like, which is not limited in the embodiment of the present invention.

In addition, it should be noted that, the above-mentioned manner in which the registration terminal 40 acquires the drone identifier of the drone 30 is merely exemplarily described, and for the manner in which the registration terminal 40 acquires the remote controller identifier of the remote controller 20, similar to the above-mentioned manner in which the drone identifier of the drone 30 is acquired, reference may be specifically made to the above-mentioned manner in which the drone identifier of the drone 30 is acquired.

In the embodiment of the present invention, in order to simplify the device, the registration terminal 40 and the remote controller 20 may be integrated into the same device, that is, both the functions of the registration terminal 40 and the remote controller 20 are provided in one device, but the functions of the registration terminal 40 can be used only by an operator with a designated authority.

After the registration terminal 40 obtains the drone identifier and/or the remote controller identifier, the drone identifier and/or the remote controller identifier may be sent to the server 10, so as to register the drone 30 corresponding to the drone identifier and/or the remote controller 20 corresponding to the remote controller identifier in the server 10.

In a preferred embodiment of the present invention, referring to the schematic structural diagram of the server shown in fig. 3, the server 10 may call the registration relation determining module 101, the registration module 102, or the first prompting module 103 to register the drone and/or the remote controller:

the registration relation judging module 101 is configured to judge whether the unmanned aerial vehicle identifier and/or the remote controller identifier exist in a preset registration relation database, and if the unmanned aerial vehicle identifier and/or the remote controller identifier exist in the preset registration relation database, call the first prompting module 103; if not, calling the registration module 102;

in a specific implementation, a registration relation database may be preset in the server 10, and at least one drone identifier and/or remote controller identifier registered by the server may be stored in the registration relation database.

In practical applications, the server-registered drone identifier and/or the remote controller identifier exist in a registration relationship database, and in one aspect, the registration relationship of the drone may be an association relationship between the drone identifier of the registered drone and the corresponding operation group identifier, and the registration relationship of the remote controller may be an association relationship between the remote controller identifier of the registered remote controller and the corresponding operation group identifier.

A registration module 102, configured to record the drone identifier in the registration relation database to perform registration of the drone, and/or record the remote controller identifier in the registration relation database to perform registration of the remote controller;

the first prompting module 103 is configured to generate first error prompting information, return the first error prompting information to a registration terminal, and display the first error prompting information by the registration terminal, where the first error prompting information is used to prompt that the unmanned aerial vehicle and/or the remote controller have been registered.

Specifically, after the server 10 receives the drone identifier and/or the remote controller identifier, the registration relationship determination module 101 may search for an identifier consistent with the drone identifier and/or the remote controller identifier in the registration relationship database, and if the search is successful, it indicates that the drone 30 corresponding to the drone identifier is already registered in the server, and/or that the remote controller 20 corresponding to the remote controller identifier is already registered in the server, that is, the registration relationship of the drone identifier and/or the remote controller identifier exists in the server, at this time, a first error prompt message may be generated by the first prompt module 103, and the first error prompt message is returned to the registration terminal 40, and the registration terminal 40 displays the first error prompt message to an operator with a specified authority, so as to prompt the operator that the drone 30 corresponding to the drone identifier and/or the remote controller 20 corresponding to the remote controller identifier are already registered for performing the warning And the operator can be prompted to cancel the original registration relationship of the unmanned aerial vehicle 30 or the remote controller 20 before the next operation can be performed.

If the search is unsuccessful, it indicates that the drone 30 corresponding to the drone identifier is not registered in the server, and/or the remote controller 20 corresponding to the remote controller identifier is not registered in the server, and at this time, the registration module 102 may be invoked to record the drone identifier and/or the remote controller identifier in the registration relation database.

In one embodiment, the registration module 102 may be invoked to generate an association relationship between the drone identifier and a job group identifier corresponding to the currently registered terminal 40 to register the current drone 30, and/or generate an association relationship between the remote controller identifier and a job group identifier corresponding to the currently registered terminal 40 to register the current remote controller 20, and store the association relationship (the association relationship between the drone identifier and the job group identifier corresponding to the currently registered terminal 40 and/or the association relationship between the remote controller identifier and the job group identifier corresponding to the currently registered terminal 40) in a preset registration relationship database.

In the embodiment of the invention, the unmanned aerial vehicle 30 and the remote controller 20 are registered in the server before being paired, so that the possibility that the unmanned aerial vehicle 30 is controlled by the unknown remote controller 20 is avoided, the possibility that the remote controller 20 controls the unknown unmanned aerial vehicle 30 mistakenly is also avoided, and the flight safety of the unmanned aerial vehicle is greatly ensured.

In embodiments of the present invention, the server 10 may also be used to assign unique communication addresses to the drones 30 and/or the remote control 20.

In one embodiment, the server 10 may assign a communication address to the drone 30 or remote control 20 after registering it. Specifically, after the server finishes registering the drone 30 and the remote controller 20, the drone 30 and the remote controller 20 may be further assigned with corresponding communication addresses, where the communication addresses are addresses uniquely identifying the respective nodes on the communication network. The nodes need to know their communication addresses to transmit and receive data to and from each other. The communication network in the embodiment of the invention comprises the following nodes: unmanned aerial vehicle 30, remote controller 20.

In another embodiment, the server 10 may also assign a communication address to the drone 30 or the remote control 20 when the drone 30 or the remote control 20 is shipped, i.e., automatically assign a communication address unique to the drone 30 or the remote control 20 when the drone 30 or the remote control 20 is produced.

It should be noted that, in the embodiment of the present invention, the communication address of the drone 30 corresponds to the drone identifier of the drone 30, and the communication address of the remote controller 20 corresponds to the remote controller identifier of the remote controller 20.

The embodiment of the present invention does not limit the generation manner of the communication address, as long as it is guaranteed that the communication address is a communication address unique to the whole network. The following describes an exemplary manner of generating the communication address of the drone 30 or the remote controller 20 by using a specific embodiment, but it should be understood that the embodiment of the present invention is not limited thereto.

In one embodiment, an unoccupied device number may be selected from a plurality of pre-assigned device numbers as the device number of the registered drone and/or remote controller; and organizing the equipment number of the unmanned aerial vehicle and/or the remote controller and preset characteristic attribute information into a communication address of the unmanned aerial vehicle and/or the remote controller.

In specific implementation, the server may further allocate a plurality of device numbers for each operation group, may query a plurality of device numbers corresponding to the operation group according to the operation group identifier, and select an unoccupied device number from the plurality of device numbers as the device number of the current unmanned aerial vehicle 30 and/or the remote controller 20, so as to ensure that all the device numbers of the unmanned aerial vehicle and the remote controller in the current operation area are unique in the current operation area.

As a preferred example of the embodiment of the present invention, the preset characteristic attribute information may be attribute information of a current job group, and the attribute information of the job group may be queried according to a job group identifier of the current job group, where the attribute information of the job group may include but is not limited to: job group code, job team code (each job group has a job team to which it belongs, each job team has a job team code), and area code (each job group has a job area to which it belongs, and each job area has an area code).

After the device number and the characteristic attribute information of the unmanned aerial vehicle and/or the remote controller are obtained, the communication address of the unmanned aerial vehicle and/or the remote controller can be organized. In one embodiment, the communication addresses of the drone 30 and the remote control 20 may each include four bytes. For the drone 30, the four bytes contained in the communication address of the drone are, in order: the area code, the team code, and the device number of the drone 30 corresponding to the operation group registered by the drone 30. For the remote control 20, the four bytes contained in the communication address of the remote control are: the area code, the team code, the job group code, and the device number of the remote controller 20 corresponding to the job group registered by the remote controller 20.

After the server 10 assigns the communication addresses to the drone 30 and the remote controller 20, the drone identifier of the drone 30 to which the communication address has been assigned may be written into a drone pairing list, and the drone pairing list may be sent to the remote controller 20 after the remote controller 20 is powered on.

In a preferred embodiment of the present invention, as shown in fig. 3, the server 10 may further include the following modules:

a first startup information receiving module 104, configured to receive startup information sent by the remote controller, where the startup information includes a remote controller identifier of the remote controller;

a download judgment module 105, configured to judge whether the remote controller has a download record for the unmanned aerial vehicle pairing list based on the remote controller identifier, if yes, invoke an update confirmation module 107, and if not, invoke a list sending module 106;

the list sending module 106 is configured to send the latest human-computer pairing list at the current time to the remote controller;

an update confirmation module 107, configured to obtain a download time, for the remote controller corresponding to the remote controller identifier, of the last downloading of the pairing list of the unmanned aerial vehicle, and determine whether the pairing list of the unmanned aerial vehicle is updated within a time range from the download time to the current time, if yes, invoke the list sending module 106; and if not, generating a determination instruction, and sending the determination instruction to the remote controller corresponding to the remote controller identification.

Specifically, after the remote controller 20 is powered on and started, the power-on information may be sent to the server 10, where the power-on information includes a remote controller identifier of the remote controller 20. The server 10 calls the first power-on information receiving module 104 to receive the power-on information sent by the remote controller 20, and after the first power-on information receiving module 104 obtains the remote controller identifier from the power-on information, the remote controller identifier is sent to the download determining module 105.

The download judgment module 105 queries the identifier of the remote controller from a previously generated download log record, and if the search is successful, it may be judged that the remote controller 20 has downloaded the pairing list of the unmanned aerial vehicle, and at this time, the download judgment module 105 may generate a positive judgment result and send the positive judgment result to the update confirmation module 107; if the search fails, it may be determined that the remote controller 20 has not downloaded the pairing list of the unmanned aerial vehicle, and at this time, the download determining module 105 may generate a negative determination result and send the negative determination result to the list sending module 106.

After receiving the positive determination result, the update confirmation module 107 queries, from the previously generated download log record, the download time at which the remote controller 20 has downloaded the pairing list of the unmanned aerial vehicle the latest time, and queries whether the pairing list of the unmanned aerial vehicle has been updated within a time range from the download time to the current time, and if the pairing list of the unmanned aerial vehicle has been updated within the time range, the update confirmation module 107 may generate an update message and send the update message to the list sending module 106; if the drone pairing list has not been updated within the time frame, the update confirmation module 107 may generate a confirmation instruction (or may not generate anything) and send the confirmation instruction to the remote control 20.

When the list sending module 106 receives a negative determination result or an update message, the unmanned aerial vehicle pairing list which is latest at the current time may be sent to the remote controller 20.

In a preferred embodiment of the present invention, as shown in the schematic diagram of the remote controller structure shown in fig. 4, the remote controller 20 may include the following modules:

a list presentation module 201, configured to present the pairing list of the unmanned aerial vehicles to a user;

when the remote controller 20 receives the pairing list of drones sent by the list sending module 107, the received pairing list of drones can be presented to the user (i.e., the operator) through the list presenting module 201.

Or,

when the remote controller receives a confirmation instruction sent by the update confirmation module 107, or any message returned by the server is not received within a preset time period, the pairing list of the recently obtained unmanned aerial vehicle may be obtained, and the pairing list of the recently obtained unmanned aerial vehicle is displayed to the operator through the list display module 201.

The command detection module 202 is configured to detect an unmanned aerial vehicle identifier, which is selected by a user from the unmanned aerial vehicle pairing list and needs to be paired, and receive a pairing command initiated by the user according to the unmanned aerial vehicle identifier needing to be paired;

the operator can select the unmanned aerial vehicle identification needing to be paired from the unmanned aerial vehicle pairing list displayed on the screen of the remote controller. In a specific implementation, an operator may select an unmanned aerial vehicle identifier that needs to be paired from an unmanned aerial vehicle pairing list in multiple ways, for example, the unmanned aerial vehicle identifier that needs to be paired may be selected in the following way, but the embodiment of the present invention is not limited to this: unmanned aerial vehicle identifications needing to be paired can be selected from the unmanned aerial vehicle pairing list through point touch operation, and when the remote controller detects point touch operation of an operator for a certain unmanned aerial vehicle identification in the unmanned aerial vehicle pairing list, the unmanned aerial vehicle identification corresponding to the point touch operation is used as the unmanned aerial vehicle identification needing to be paired; or, the unmanned aerial vehicle identifier can also be read through NFC or scanning of a one-dimensional code or a two-dimensional code, and the like, and the read unmanned aerial vehicle identifier is matched in the unmanned aerial vehicle pairing list, and if the matching is successful, the successfully matched unmanned aerial vehicle identifier is used as the unmanned aerial vehicle identifier to be paired.

When the remote control 20 detects that the operator selects the identity of the drone to be paired from the drone pairing list, a "pairing" dialog box may be presented to the operator, which may include a "pairing" button and an "unpairing" button. If it is detected that the operator clicks the "pairing" button, it may be determined that the operator initiates a pairing instruction for the identifier of the unmanned aerial vehicle that needs to be paired, and at this time, the instruction detection module 202 may send the pairing instruction to the pairing request generation module 203. And if the condition that the operator clicks the unpaired button is detected, finishing the pairing process.

A pairing request generating module 203, configured to generate a pairing request based on the pairing instruction, and send the pairing request to a server, where the pairing request includes the identity of the unmanned aerial vehicle to be paired and the identity of the remote controller.

After receiving the pairing instruction, the pairing request generation module 203 may generate a pairing request based on the pairing instruction, and send the pairing request to the server 10, where the pairing request may include the identity of the unmanned aerial vehicle and the identity of the remote controller that need to be paired.

After the server 10 receives the pairing request, the pairing of the remote controller 20 and the drone 30 to be paired can be completed.

the pairing judgment module 108 is configured to judge whether the unmanned aerial vehicle identifier to be paired has a binding relationship with other remote controller identifiers based on the pairing request; if yes, the second prompting module 109 is called, and if not, the binding module 110 is called;

the second prompting module 109 is configured to generate second error prompting information, and return the second error prompting information to the remote controller;

a binding module 110, configured to generate a binding relationship between the identifier of the unmanned aerial vehicle to be paired and the identifier of the remote controller, so as to bind the remote controller and the unmanned aerial vehicle to be paired, and determine, according to current location information of the remote controller, a communication channel number for communication between the unmanned aerial vehicle corresponding to the identifier of the unmanned aerial vehicle to be paired and the remote controller; and sending the communication address of the unmanned aerial vehicle needing to be paired, the communication address of the remote controller and the communication channel number to the remote controller.

After receiving the pairing request, the server 10 may determine, through the pairing determination module 108, whether the identifier of the unmanned aerial vehicle that needs to be paired in the pairing request is in a binding relationship with the identifiers of other remote controllers, in a specific implementation, a pairing relationship database may be preset in the server, and the pairing relationship database may store the binding relationship between the identifier of the unmanned aerial vehicle that has been paired and the identifier of the corresponding remote controller. The pairing determination module 108 may search the identity of the unmanned aerial vehicle to be paired in the pairing relationship database, and if the search is successful, it may be determined that the identity of the unmanned aerial vehicle to be paired has been paired and bound with the identity of the other remote controller, and at this time, a search success message may be generated, and the search success message is sent to the second prompt module 109; if the search is unsuccessful, it may be determined that the identity of the unmanned aerial vehicle to be paired is not paired and bound with the identity of the other remote controller, and at this time, search failure information may be generated and sent to the invoking and binding module 110.

After the second prompt module 109 receives the search success information, it may generate a second error prompt message, and return the second error prompt message to the remote controller 20, so as to prompt the remote controller 20 that the unmanned aerial vehicle corresponding to the unmanned aerial vehicle identifier to be paired has a binding relationship with other remote controllers, that is, the unmanned aerial vehicle corresponding to the unmanned aerial vehicle identifier to be paired has been paired by other remote controllers.

After receiving the search failure information, the binding module 110 generates a binding relationship between the identity of the unmanned aerial vehicle to be paired and the identity of the remote controller based on the search failure information, so as to bind the remote controller and the unmanned aerial vehicle to be paired.

After the binding relationship is generated, the binding module 110 may further determine, according to the current location information of the remote controller carried in the pairing request, a communication channel number for the communication between the unmanned aerial vehicle 30 to be paired and the corresponding remote controller 20. In a specific implementation, the server allocates a certain number of communication channels to each working area, may query, according to the working group identifier, a plurality of communication channel numbers corresponding to the working group, and obtain, according to the current location information of the remote controller, whether there are other remote controllers and the unmanned aerial vehicle paired within a preset range (e.g., within a range of radius 2 km), if so, select, from the plurality of communication channel numbers, a plurality of communication channel numbers that are not occupied within a current working area as the communication channel numbers for the unmanned aerial vehicle 30 that needs to be paired to communicate with the corresponding remote controller 20, so as to avoid interference between the communication channels.

Subsequently, the binding module 110 obtains the communication address of the unmanned aerial vehicle 30 to be paired and the communication address of the remote controller 20 corresponding to the unmanned aerial vehicle 30, and sends the communication address of the unmanned aerial vehicle to be paired, the communication address of the remote controller and the communication channel number of the remote controller 20 to the remote controller.

On the remote controller 20 side, after receiving pairing parameters such as the communication address of the unmanned aerial vehicle to be paired, the communication address of the remote controller, and the communication channel numbers of the two, the pairing parameters may be stored, and communication configuration of the remote controller may be performed according to the received pairing parameters.

From now on, remote controller 20 has just obtained the communication address of the unmanned aerial vehicle that needs to pair and the communication channel number that both sides used, has accomplished the pairing work of remote controller end.

Next, pairing work at the unmanned aerial vehicle end is performed.

a second startup information receiving module 111, configured to receive startup information sent by the unmanned aerial vehicle that needs to be paired, where the startup information includes an identification of the unmanned aerial vehicle;

a pairing parameter obtaining module 112, configured to obtain a pairing parameter corresponding to the identity of the unmanned aerial vehicle that needs to be paired, and send the pairing parameter to the unmanned aerial vehicle that needs to be paired.

Specifically, after the unmanned aerial vehicle 30 is powered on and started, the startup information may be sent to the server 10, where the startup information includes the unmanned aerial vehicle identifier of the unmanned aerial vehicle 30. The server 10 calls a second startup information receiving module 111 to receive startup information sent by the unmanned aerial vehicle 30, after the second startup information receiving module 111 obtains an unmanned aerial vehicle identifier from the startup information, the unmanned aerial vehicle identifier is sent to a pairing parameter obtaining module 112, after the pairing parameter obtaining module 112 obtains the unmanned aerial vehicle identifier, the unmanned aerial vehicle identifier is searched in all pairing parameters, and if the unmanned aerial vehicle identifier is successfully searched, pairing parameters such as a communication address of the unmanned aerial vehicle corresponding to the unmanned aerial vehicle identifier, a communication address of a corresponding remote controller, communication channel numbers of the two and the like are sent to the unmanned aerial vehicle 30; if the search fails, an error prompt message is returned to the unmanned aerial vehicle 30.

It should be noted that the above-mentioned method is only one embodiment of obtaining the pairing parameters by the drone 30, and those skilled in the art may also use other methods to make the drone 30 obtain the pairing parameters, for example, the remote controller 20 transmits the communication address of the remote controller 20, the communication address of the drone, and the communication channel number of the two to the drone 30 through NFC, bluetooth, sound wave, and the like.

At the unmanned aerial vehicle 30 side, after pairing parameters such as the communication address of this unmanned aerial vehicle, the communication address of the remote controller that corresponds and communication channel number between them are received, this pairing parameter can be stored to carry out unmanned aerial vehicle's communication configuration according to this received pairing parameter.

From this point on, the drone 30 obtains the communication address of the remote control 20 and the communication channel number used by both parties, and completes pairing work at the drone end.

Subsequently, the remote controller 20 may send confirmation information to the unmanned aerial vehicle 30 that needs to be paired, after the unmanned aerial vehicle 30 that needs to be paired receives the confirmation information, the confirmation response information may be returned to the remote controller 20, after the remote controller 20 receives the confirmation response information returned by the unmanned aerial vehicle that needs to be paired, it is determined that the unmanned aerial vehicle that needs to be paired is successfully paired, and at this time, the remote controller 20 may communicate with the unmanned aerial vehicle 30.

In the embodiment of the present invention, since the pairing parameters (the communication address of the drone 30, the communication address of the remote controller 20, and the communication channel number between the two) are allocated by the server 10, there is no need for the remote controller 20 to directly broadcast the pairing request, and when a plurality of drones 30 and a plurality of remote controllers 20 in an area operate simultaneously, the distance between two sets of drones is increased compared to the prior art in order to avoid channel interference, the embodiment of the present invention can reduce the environmental requirement of the pairing process,

moreover, the communication address and the communication channel number are allocated through the server 10, so that the problem of channel interference and pairing error can be avoided, the unmanned aerial vehicle cluster can be managed in a unified mode, and the management cost is reduced.

In addition, for the operator, when the remote controller 20 needs to be paired with the unmanned aerial vehicle 30, the unmanned aerial vehicle identifier that needs to be paired is selected from the unmanned aerial vehicle pairing list displayed by the remote controller 20, and thus the pairing between the remote controller 20 and the unmanned aerial vehicle 30 can be realized. And excessive operation is not needed, so that the operation required to be executed by the pairing is greatly simplified, and the time required by the pairing is saved.

Referring to fig. 5, a flowchart illustrating a first step of a first method embodiment of pairing an unmanned aerial vehicle and a remote controller according to the present invention is shown, where the unmanned aerial vehicle is controlled by the remote controller, and the unmanned aerial vehicle and the remote controller are connected to a server, and the first method embodiment of the present invention may include the following steps:

step 501, receiving a pairing request sent by the remote controller;

step 502, if the remote controller is determined to be bound with the unmanned aerial vehicle needing to be paired, acquiring pairing parameters corresponding to the pairing request;

step 503, returning the pairing parameters to the remote controller.

The remote controller is used for carrying out communication configuration on the remote controller according to the pairing parameters.

In a preferred embodiment of the present invention, the method may further include the following steps: and receiving an unmanned aerial vehicle identifier and/or the remote controller identifier sent by a registration terminal, and registering the unmanned aerial vehicle and/or the remote controller.

In a preferred embodiment of the present invention, the registering the drone and/or the remote controller may include the following sub-steps:

substep S11, determining whether the unmanned aerial vehicle identifier and/or the remote controller identifier exist in a preset registration relation database, and if so, executing substep S13; if not, go to substep S12;

and the preset registration relation database stores at least one unmanned aerial vehicle identifier and/or remote controller identifier registered by the server.

Substep S12, recording the identity of the drone in the registration relationship database for registration of the drone and/or recording the identity of the remote control in the registration relationship database for registration of the remote control;

and a substep S13, generating a first error prompt message, returning the first error prompt message to a registration terminal, and displaying the first error prompt message by the registration terminal, wherein the first error prompt message is used for prompting that the unmanned aerial vehicle and/or the remote controller have been registered.

In a preferred embodiment of the present invention, the method may further include the following steps:

the server allocates a unique communication address for the unmanned aerial vehicle and/or the remote controller.

In a preferred embodiment of the present invention, the step of organizing the drone id of the drone to which the communication address has been assigned into a drone pairing list, and the step of sending the drone pairing list to the remote controller further includes the substeps of:

In a preferred embodiment of the present invention, the pairing request further includes current location information of the remote controller, and the pairing parameters include a communication address of the unmanned aerial vehicle to be paired, a communication address of the remote controller, and a communication channel number through which the unmanned aerial vehicle to be paired communicates with the remote controller; the step 503 may comprise the following sub-steps:

substep S31, determining whether the identity of the unmanned aerial vehicle needing pairing and the identity of other remote controllers have a binding relationship based on the pairing request; if yes, go to substep S32; if not, go to substep S33;

a substep S32, generating a second error prompt message, and returning the second error prompt message to the remote controller;

a substep S33, generating a binding relationship between the identity of the unmanned aerial vehicle to be paired and the identity of the remote controller, so as to bind the remote controller and the unmanned aerial vehicle to be paired, and determining a communication channel number for communication between the unmanned aerial vehicle corresponding to the identity of the unmanned aerial vehicle to be paired and the remote controller according to the current position information of the remote controller; and sending the communication address of the unmanned aerial vehicle needing to be paired, the communication address of the remote controller and the communication channel number to the remote controller.

In a preferred embodiment of the embodiments of the present invention, the method may further include the steps of:

and acquiring a pairing parameter corresponding to the identification of the unmanned aerial vehicle needing to be paired, and sending the pairing parameter to the unmanned aerial vehicle needing to be paired.

The unmanned aerial vehicle is used for carrying out communication configuration of the unmanned aerial vehicle according to the pairing parameters.

Referring to fig. 6, a flowchart illustrating steps of a second embodiment of a method for pairing an unmanned aerial vehicle and a remote controller according to the present invention is shown, where the unmanned aerial vehicle is controlled by the remote controller, and the unmanned aerial vehicle and the remote controller are connected to a server, and the embodiment of the present invention is described from the perspective of the remote controller, and may include the following steps:

601, generating a pairing request, and sending the pairing request to a server;

step 602, receiving pairing parameters corresponding to the pairing request returned by the server;

step 603, performing communication configuration of the remote controller according to the pairing parameters.

In a preferred embodiment of the present invention, before step 601, the following steps may be further included:

and acquiring an unmanned aerial vehicle pairing list.

The unmanned aerial vehicle pairing list is a list formed by organizing unmanned aerial vehicle identifications of unmanned aerial vehicles with the communication addresses allocated by the server after the server allocates the communication addresses to the unmanned aerial vehicles and/or the remote controllers.

In a preferred embodiment of the present invention, the step of acquiring the pairing list of the unmanned aerial vehicle by the remote controller includes:

sending startup information to a server, wherein the startup information comprises a remote controller identifier of the remote controller;

and receiving the latest unmanned aerial vehicle pairing list sent by the server at the current moment, or receiving a determination instruction returned by the server, and obtaining the latest downloaded unmanned aerial vehicle pairing list according to the determination instruction.

In a preferred embodiment of the embodiments of the present invention, the method further comprises:

In a preferred embodiment of the present invention, the step of selecting, by the remote controller, an identity of a drone to be paired from the paired list of drones includes the following substeps:

substep S41, presenting the drone pairing list to a user;

substep S42, detecting the unmanned aerial vehicle identifier which needs to be paired and is selected by the user from the unmanned aerial vehicle pairing list, and receiving a pairing instruction initiated by the user according to the unmanned aerial vehicle identifier which needs to be paired;

and a substep S43, generating a pairing request based on the pairing instruction, and sending the pairing request to a server, where the pairing request includes the identity of the unmanned aerial vehicle to be paired and the identity of the remote controller.

In a preferred embodiment of the present invention, the pairing parameters include a communication address of the drone to be paired, a communication address of the remote controller, and a communication channel number through which the drone to be paired communicates with the remote controller.

In order to enable those skilled in the art to better understand the embodiments of the present invention, the following description illustrates the embodiments of the present invention by way of a specific example, but it should be understood that the embodiments of the present invention are not limited thereto:

1. the remote controller a requests the server to pair a certain unmanned aerial vehicle UAV1, and the request information includes: identity a of the drone a itself, identity UAV1 of the unmanned UAV1, current location (e.g., GPS coordinates) of the drone a;

2. the server judges whether the remote controller A is bound with the unmanned aerial vehicle UAV1, if not, pairing is refused, meanwhile, the server judges whether the unmanned aerial vehicle UAV1 is paired by other remote controllers, and if yes, the server can prompt that the unmanned aerial vehicle UAV1 is paired by other remote controllers;

3. if the remote controller A has the pairing qualification with the unmanned aerial vehicle UAV1, the server judges whether other remote controllers and the unmanned aerial vehicle are paired within the radius of 2KM (or other range values) according to the position reported by the remote controller A, and if the remote controllers and the unmanned aerial vehicle are paired, an unused communication channel number is searched;

4. the server respectively sends the communication address of the remote controller A, the communication address of the unmanned aerial vehicle UAV1 and the channel number of the pairing to the remote controller A and the unmanned aerial vehicle UAV 1;

5. the unmanned aerial vehicle UAV1 sets a communication module thereof according to the communication address of the remote controller A sent by the server, the communication address of the unmanned aerial vehicle UAV1 and the channel number of the pairing;

6. the remote controller A sets a communication module thereof according to the communication address of the remote controller A, the communication address of the unmanned aerial vehicle UAV1 and the channel number of the pairing sent by the server;

7. after the remote controller a sets the communication module, the remote controller a sends confirmation information to the unmanned aerial vehicle UAV1, waits for the unmanned aerial vehicle UAV1 to return confirmation response information, and if the confirmation response information is received, the pairing is successful.

It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.

The embodiment of the invention also discloses a server for pairing the unmanned aerial vehicles, wherein the server is the server in the pairing system shown in the figure 1 or the figure 2.

The embodiment of the invention also discloses a remote controller for controlling the unmanned aerial vehicle, wherein the remote controller is the remote controller in the pairing system shown in the figure 1 or the figure 2.

The embodiment of the invention also discloses an unmanned aerial vehicle, which is the unmanned aerial vehicle in the pairing system shown in the figure 1 or the figure 2.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

While preferred embodiments of the present invention have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the invention.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.

The method, the server, the remote controller and the system for pairing the unmanned aerial vehicle and the remote controller are introduced in detail, specific examples are applied in the text to explain the principle and the implementation mode of the invention, and the description of the above embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A pairing system for pairing unmanned aerial vehicles, the pairing system comprising at least: a server, a remote control, and a drone, wherein,

2. The system of claim 1, further comprising a registration terminal;

3. The system of claim 2, wherein the server comprises:

4. A system according to claim 2 or 3, characterized in that the registration terminal is integrated in the same device as the remote control.

5. The system of claim 1, 2 or 3, wherein the server is further configured to assign a unique communication address to the drone and/or remote control.

6. The system of claim 5, wherein the server is further configured to organize drone identities of drones having assigned communication addresses into a drone pairing list, and to send the drone pairing list to the remote controller, including:

7. The system of claim 6, wherein the remote control comprises:

8. The system of claim 7, wherein the pairing request further includes current location information of the remote controller, and the pairing parameters include a communication address of the drone to be paired, a communication address of the remote controller, and a communication channel number of the drone to be paired for communicating with the remote controller;

the server further comprises:

9. The system of claim 8, wherein the server further comprises:

10. A server for pairing drones, characterized in that it is a server in the pairing system according to any one of claims 1 to 9.

11. A remote control for controlling an unmanned aerial vehicle, wherein the remote control is the remote control in the pairing system of any one of claims 1 to 9.

12. A drone, characterized in that it is a drone in the pairing system of any one of claims 1 to 9.

13. A method of pairing an unmanned aerial vehicle and a remote control, wherein the unmanned aerial vehicle is controlled by the remote control, the unmanned aerial vehicle and the remote control are connected to a server, the method comprising:

receiving a pairing request sent by the remote controller;

14. The method of claim 13, further comprising:

15. The method of claim 14, wherein the registering the drone and/or the remote control comprises:

16. The method of claim 13, 14 or 15, further comprising:

assigning a unique communication address to the drone and/or remote control.

17. The method of claim 16, further comprising:

18. The method of claim 17, wherein organizing drone identities of drones having assigned communication addresses into a drone pairing list, the step of sending the drone pairing list to the remote controller comprises:

19. The method according to claim 17 or 18, wherein the pairing request includes current location information of the remote controller, and the pairing parameters include a communication address of the drone to be paired, a communication address of the remote controller, and a communication channel number of the drone to be paired for communicating with the remote controller;

the method further comprises the following steps:

20. The method of claim 19, further comprising:

21. A method of pairing an unmanned aerial vehicle and a remote control, wherein the unmanned aerial vehicle is controlled by the remote control, the unmanned aerial vehicle and the remote control are connected to a server, the method comprising:

generating a pairing request and sending the pairing request to a server;

22. The method of claim 21, further comprising, prior to the step of generating a pairing request by the remote control and sending the pairing request to a server:

23. The method of claim 22, wherein the step of obtaining a pairing list of drones comprises:

24. The method of claim 22 or 23, further comprising:

25. The method of claim 24, wherein the step of selecting from the pairing list of drones the identity of the drone to be paired comprises:

displaying the unmanned aerial vehicle pairing list to a user;

26. The method of claim 22, 23 or 25, wherein the pairing parameters include a communication address of the drone to be paired, a communication address of the remote control, and a communication channel number for the drone to be paired to communicate with the remote control.