RU2791630C2 - Provision of access to unmanned aerial vehicles - Google Patents

Abstract

FIELD: communication.

SUBSTANCE: invention relates to exchange of data related to operation of drones, assessment of this data by a third party, and provision of a third party with access to a drone via a cellular communication system. The invention implements a method allowing a mobile mechanism to provide information to a receiver device, including transmission of information by the mobile mechanism via the second radio interface for provision the receiver device with access, via an interface of mobile cellular communication, to control of this mobile mechanism.

EFFECT: provision of information exchange between unmanned aerial vehicles.

11 cl, 5 dwg, 3 tbl

Description

Technical field

The present invention relates to the exchange of data related to the operation of drones, the evaluation of this data by a third party and the provision of access to the drone to a third party through a cellular communication system, for example, through the objects and protocols used in a cellular communication system in accordance with a set of specifications LTE and LTE- Advanced Consortium 3GPP. These methods can also be implemented in the upcoming 5G communication standards.

State of the art

The number of drones (or unmanned aerial vehicles, UAVs) is on the rise. There is already a wide range of drones on the market, from light quadcopters (weighing about 20 g and dimensions 10-15 cm), mainly used as toys, to heavy octocopters (weighing about 400 g and dimensions 50-60 cm), equipped with special cameras for amateur photography. Most of these drones can be controlled by remote controllers under line-of-sight conditions using radio signals in the 2.4GHz frequency band. Larger, heavier drones are also available for commercial purposes, which can use other radio signals to control flight. In some cases, for larger drones, the line-of-sight condition may not apply.

Examples of the use of drones are, among others, package delivery, search and rescue, monitoring of critical infrastructure, wildlife conservation, flying cameras (for example, for sports events or video surveillance). Most likely, these use cases will continue to appear in the coming years. In many of the aforementioned drone use cases, there are benefits to be gained from connecting drones to cellular systems (such as LTE networks) as User Equipment (UEs). Therefore, more and more of these drones are (or will be) equipped with the functionality of UE devices.

This trend is also known to the 3GPP consortium. RAN Plenary #75 in March 2017 reviewed and approved in RP-170779 a new subject of study for RAN Working Groups, Extended Aircraft Support. The desirability of including this subject of study within the purview of 3GPP stems from the desire to better prepare 3GPP wireless technology to deal with the new types of interference that are expected to emerge due to the ever-increasing number of drones.

It can be assumed that the mobile operator (MNO, Mobile Network Operator) always controls the operation of the cellular modem (as far as cellular communication standards, for example, LTE allow today), if the wireless communication between the base station and the UE device (or cellular modem) built into drone or mounted on a drone is not infringed.

However, it should not be assumed that the MNO operator also controls the navigation and flight control functions of drones equipped with the functionality of UE devices. To do this, an interface between the cellular modem and the drone flight control unit must be organized, and the drone control commands must be standardized (or the drone control commands must be known on the infrastructure side).

It is desirable to identify drones when they are in the air and define a method for requesting and/or verifying identifiers and/or certificates provided by drones, for example, to third parties.

It can be expected that some form of classification will be introduced as part of the certification process in order to recognize different types of drones. The first criterion for recognizing drones may be whether the drone has the functionality of the UE device, and the second criterion may be whether the drone is certified for flight control handover. Such a classification can be presented in tabular form, for example, in the form of Table 1 below.

Table 1 Drone equipped
functionality of the UE device Drone not equipped
functionality of the UE device Drone capable of handover
flight control Class 1 drone Class 2 drone Drone not supporting
handover
flight control Class 3 drone Class 4 drone

Currently, there are no defined means of transmitting information such as that presented in Table 1 from a drone to its potential recipients. Table 1 is just an example. If necessary, it can be easily expanded and extended to more than two criteria for drones.

In addition, it is highly desirable to ensure the exchange of information between a third party and the drone via a cellular network. At the present level of development of technology, there is no detailed information on the procedure for performing such actions. In addition, drone traffic may require special settings to ensure the quality of service on the network, for example in terms of data transfer rate and/or data transfer latency, as well as a separate billing method.

In an article by Kyung-Nam Park et al. "Handover Management of Net-Drones for Future Internet Platforms", Int. J. Distributed Sensor Networks, 2016, ID 5760245 (Kyun Nam Park et al. "Handover Management of Network Drones for Advanced Internet Platforms", International Journal of Distributed Sensor Networks, 2016, ID 5760245), describes drones that provide a WiFi hotspot and support communication with the base station.

Document WO2016210432A1 describes a drone security management system using a short message service. It is proposed to use a single radio interface, which can be organized on the basis of cellular, WiFi, Bluetooth or satellite communications.

US20160140851A1 describes an aircraft with a communication interface in which flight plan information is transmitted in the downlink and flight control commands and route data are transmitted in the uplink.

Document EP1475610A1 describes a remote controlled vehicle. This vehicle is connected to a remote sending and receiving device using infrared, Bluetooth, wireless LAN, or cellular.

The present invention implements a method for allowing a mobile mechanism to transmit information to a receiving device. This method includes the mobile mechanism transmitting information via the second air interface to allow the recipient device to access control of the mobile mechanism via the cellular mobile communication interface.

This mobile mechanism can be, for example, an unmanned aerial vehicle, commonly referred to as a drone.

In general, this invention describes how a data set distributed by drones can be used and analyzed by a third party (eg, air traffic control, authorities, police, etc.). In addition, it considers the interaction between a third party and a mobile operator (MNO) based on the received data set and defines two new interfaces for transmitting data related to the operation of the drone over the cellular network. The first new interface is the interface between the cellular modem and the flight control unit inside the drone, and the second new interface is the interface between the third party server and the core network of the cellular communication system.

The first aspect of the present invention is the structure of the data set distributed by the drone ("digital license plate"). The amount and content of the data distributed by the drone may be at least partially dynamic, depending on the situation in which the drone is located and / or on certain parameters, such as the mass of cargo carried by the drone, the location (height) of the drone, predicted or the actual drone trajectory, flight history, etc. The data set may be broadcast (eg, periodically) over a second air interface (eg, operating on a first frequency). The data set may contain information (eg, access information) related to the third radio interface, in particular, activation of the third radio interface (eg, operating on a second frequency) provided by the mobile operator. The data set may constitute information or be part of information that may serve as the equivalent of a registration plate (or license plate) used by vehicles in surface traffic. Essentially, the data set may contain the registration number of the drone. In addition, the data set may contain information related to the internal interface of the aircraft, which provides data exchange between the UE device (cellular modem) and the flight control unit of the aircraft.

The second aspect of the present invention is the analysis of a data set received from a drone by a third party. In the context of the present invention, a third party may be, for example, an official body (such as police, fire brigade, air traffic control, military, government organization, etc.). The analysis of the data set may include the selection of a cellular network. In particular, it may include selecting an appropriate interface on the MNO's cellular network for the purpose of exchanging drone-related information between a third party and that drone using the selected radio access technology or cellular network (i.e. via a third radio interface) .

A third aspect of the present invention is a method for implementing a flight control handover to an MNO or a third party. The flight control handover may include the exchange of flight control commands and navigation data over the MNO's cellular network (ie, over a third radio interface). The flight control handover may also include the exchange of (temporary) flight rules (such as restrictions and policies) to control the drone (eg in a given region) over the MNO's cellular network. For the correct implementation of the flight control handover, it is proposed to select an appropriate set of flight control commands and/or appropriate protocols.

The fourth aspect of the present invention relates to the quality of service (QoS, Quality of Service) settings and the creation of charging records (CDR, Charging Data Record) in the MNO operator domain, so that a third party and / or drone owner can be provided with the required quality of service, and the corresponding a person or organization could be billed for the use of the infrastructure and for the connection provided by the MNO operator.

Ideally, pieces of information are included in a data set distributed by drones in the form of "digital license plates". This set of data may be broadcast over the air interface according to a regularly repeating timing pattern. The information contained in the data set can then be used to perform the following tasks (at least one of them):

- identify the drone;

- identify the owner of the drone;

- receive information about the type of drone and / or supported functions;

- receive information about the possibilities of joint operation of the drone with a cellular modem (a functional element of the UE device) installed on board the drone;

- choose a mobile communication network that offers connection to the drone through the third air interface;

- to exchange information between a third party and the drone (drone flight control unit) through:

- the selected interface for accessing the cellular network,

- objects and protocols provided by the cellular network, and

- a functional element of the UE device, implemented inside the drone.

Information to be exchanged may relate to flight control commands.

Thus, a third party (for example, air traffic control, authorities, police, etc.) can influence the flight maneuvering of drones (perhaps overriding flight control commands received through another air interface). The third party may be billed and the MNO operator may be compensated for providing infrastructure and establishing a connection between the third party and the drone.

Brief description of the drawings

Hereinafter, by way of example only, preferred embodiments of the invention are described with reference to the accompanying drawings.

In FIG. 1 is a diagram of the drone architecture with communication interfaces.

In FIG. 2 is a general view of the network architecture, including the interface between the authorized receiver device and the core network that can be connected to the aircraft.

In FIG. 3 is a diagram of a connection between an aircraft and a mobile communication network, including the internal interface of the aircraft between the functional elements of the UE device and the flight control unit.

In FIG. 4 shows the procedure for obtaining a data set via the mobile network interface.

In FIG. 5 shows an example of a set of messages transmitted over the air interface Uu of an LTE network.

Implementation of the invention

In FIG. 1 shows an example architecture of a drone 10 containing six functional blocks 12-17. These functional units include a battery 12; chamber 13; a transmission module (Tx) 14 for distributing the data set (eg via the second radio interface 30); a receiving module (Rx) 15 for receiving flight control commands from a user (for example, via the first radio interface 20); flight control unit 16, necessary for navigation and control of the drone in the air; and a functional element 17 of the UE for connecting the drone to a cellular communication system (for example, via a third air interface 40, which may be an LTE Uu air interface). There may be more functional blocks or modules inside the drone, but they are not shown in Fig. 1 for brevity.

Drone 10 has several communication interfaces which, as shown in FIG. 1 can be configured as follows. The first air interface 20 may be an air interface between the remote control 22 and the drone 10 operating in license-free frequency bands (eg, the 2.4 GHz frequency band). It can support unidirectional transmission of flight control commands from the remote control to the aircraft. In one embodiment of the invention, data transmission can be carried out in two directions.

The second air interface 30 is the air interface between the drone 10 and the third party receiver 32. Although FIG. 1 receiver 32 is represented as a police car, this receiver can be any fixed or mobile receiver of any size and weight. Authorities can even use handheld devices to scan the data set distributed by the drone over this air interface. In addition, the second air interface may support a repetitive unidirectional transmission (ideally in broadcast mode) from the drone to one or more third party receivers located on the ground (or near the surface of the ground).

The third air interface 40 may be a radio interface of a cellular communication system (eg, an LTE Uu air interface in an LTE system). It supports bi-directional transmission of information (including flight control commands in one embodiment of the invention) from a third party to an aircraft using entities and protocols permitted for use in a cellular communication system.

The functional modules shown in the example of FIG. 1 inside the aircraft can be connected to each other (and to other functional modules not shown), for example, using one or more wired connections, in particular using a serial or parallel bus system. Links between functional modules in fig. 1 are omitted for simplicity.

An example of the structure of the data set transmitted by the drone as its "digital license plate", for example, via the second air interface (ideally in broadcast mode), is as follows. The amount and content of the data distributed by the drone may vary, for example, in part, depending on the use case or the situation in which the drone is located. Therefore, the number and order of the information elements (IE, information element) may differ from that indicated in the example below. The data set can be transmitted in encrypted form, and only recipients capable of decrypting this information can work with its contents.

For example, the "Access Credentials" information element can be used to inform a third party which MNO to contact if the third party intends to communicate with this drone over the air interface offered by the cellular system. This information element may contain the recipient's IP address, authentication data such as a username or password, and other such parameters.

For example, the “Collaboration Capabilities” information element can be used to inform a third party that the drone is currently connected or that it is in principle capable of connecting to a cellular network and that the aircraft’s parameters (for example, flight control parameters) can be changed via the cellular network. With the help of infrastructure elements provided by the MNO operator, a third party can change, set and control, for example, the following parameters:

- the height of the drone (i.e. the third party can decrease or increase the height of the drone, thereby possibly canceling the flight control commands transmitted by the user over the first radio interface);

- the trajectory of the drone (i.e. a third party can cause the drone to deviate from the current route or return to a previous location, for example, to one of the locations indicated in the "Archive of coordinates of coordinates");

- turn on and off the cameras built into the drone or installed on it.

In one embodiment of the present invention, the set of data transmitted by the drone as its "digital license plate" is fully or partially digitally signed (ideally in a secure processing environment) implemented with a private key (ideally stored in a tamper-resistant memory) inside the drone. This may be done in order to ensure the integrity and authenticity of the dataset (or its relevant parts).

In one embodiment of the present invention, the secure processing environment and/or tamper-resistant memory may be implemented in a Universal Subscriber Identity Module U(SIM) located on a UICC integrated circuit card (or any other smart card) associated with the cellular modem, or in a Trusted Platform Module (TPM).

Table 2 shows an example of the structure of a data set that serves as a “digital license plate” for drones. One or more of the information elements contained in this table can be read directly from memory located in the (U)SIM or UE, or retrieved from parameters stored therein. For example, the Aircraft Identifier information element may contain all or part of an IMEI or IMEI-SV (Cellular Modem Equipment Identifier), an IMSI (Subscriber Identifier), or both. Alternatively, the "Drone Identifier" information element is the actual identifier (registration number) of the drone's equipment.

table 2 Information element Description Availability general information > Drone ID Registration number (Drone-ID) Necessarily > Manufacturer ID Drone manufacturer Not necessary > Drone owner The company or person who owns the drone Not necessary > Drone operator The company or person flying the drone Not necessary > Drone type The purpose of the drone for which the license was issued, for example:
• delivery of parcels,
• search and rescue operations,
• monitoring of critical infrastructure,
• communication with wildlife,
• flying cameras,
• sports events,
• CCTV
• etc. Not necessary > License type License type, for example:
• time limited,
• unlimited in time,
• special state license
etc. Not necessary > Place of issue (nationality) Country in which the registration number was issued Not necessary > issued by whom Name or identifier of the authority that issued the drone license Not necessary > Date of issue Drone license issue time and date Not necessary > Valid until Drone license expiration date Not necessary Information about time and coordinates > Mark coordinates The current 3D coordinates of the aircraft location (such as latitude, longitude, and altitude) at the time specified below. May also include drone speed and heading Necessarily > Timestamp Time of marking the coordinates indicated above Necessarily > Archive of coordinates marks List of n records corresponding to n previous coordinates (may be correlated with the Time Stamps Archive information element below) Not necessary > Time stamp archive List of n records corresponding to n previous timestamps (may be correlated with the "Points Archive" information element above) Not necessary > Estimated trajectory A list of m entries informing about the estimated trajectory of the drone (for example, its future route, upcoming stops, and/or final destination). This information element can be correlated with the "Settlement schedule" information element below. Not necessary > Settlement schedule A list of m records informing about the expected time of arrival at the points indicated above in the information element "Calculated trajectory" Not necessary Collaboration features > MNO operator connection Tells a third party that this drone is currently connected (or alternatively, in principle connected) to a cellular network:
• Yes
• No Necessarily > Flight control handover Notifies a third party of the aircraft's ability to support flight control handover (via cellular network):
• Yes
• No Necessarily > Camera control handover Notifies a third party of the drone's ability to support camera control handover (via cellular network):
• Yes
• No Not necessary > Command sets Tells the third party which command sets or protocols to use if the third party wishes to influence, change, adjust, control the flight parameters of the drone or other functions (via the cellular network):
• set #1 (for example, preset) / protocol #1
• set #2 (for example, preset) / protocol #2
• etc. Not necessary > Supported Authorities Specifies which third party is allowed to take over flight control of the drone (via a connection provided by the cellular network):
• air traffic control service
• police
• fire brigade
• …
• any of the above
• none Not necessary > Drone class As an alternative to the "MNO operator connection" and "Flight control handover" information elements, the drone class can be specified here in accordance with Table 1. Not necessary Access credentials > Operator ID MNO Which mobile operator should be contacted for data exchange between a third party and a specific aircraft, for example, based on the ITU E.212 standard using:
• Country code in the mobile network (MCC, Mobile Country Code)
• Mobile Network Code (MNC, Mobile Network Code) Necessarily > IP address IP address of the gateway providing access to the MNO operator domain for third parties Necessarily > port number Port number for accessing the MNO operator domain Necessarily > Username #1 The username that will be used by the third party to access the MNO operator's domain Not necessary > Password #1 The password that will be used by the third party to access the MNO operator's domain Not necessary > Username #2 The username that will be used by the third party to gain access to the drone's flight control unit Not necessary > Password #2 The password that will be used by a third party to gain access to the drone's flight control unit Not necessary Digital signature > Signature Data for digital signature Necessarily > Hashing Specifies whether a hash function is applied to the signed data (and which one, if there is more than one) Not necessary …

The following describes the mechanism by which a third party (for example, an official body) is able to analyze the data set received from the drone through the second air interface.

A third party receiver, which can be any fixed or mobile receiver of any size and weight (the police car in Figure 1 is just an example), receives the data set serving as the drone's "digital license plate" and begins to analyze its contents.

With the help of the “Drone ID” information element, a third party can identify this drone. If necessary (if there are additional information elements in the data set), a third party can learn more about the newly identified flying object, in particular:

- who is the owner of this drone, for example, from the "Drone Owner" information element;

- who controls this drone, for example, from the information element "Drone Operator";

- what is the main purpose of the drone, for example, from the information element "Drone type";

- what type of license is issued to this drone, for example, from the "License type" information element, etc.

In addition, a third party may obtain information about the presence or absence of UE device functionality on board the aircraft and (if available) details about the capabilities of the aircraft to work together with a cellular modem, for example:

- does the drone have an active cellular connection, for example, from the information element “Connection of the MNO operator”, and if there is no connection, then is there a fundamental possibility of a cellular connection of the drone, for example, from the same information element;

- whether the drone supports handover of flight control to an authority, for example from the "Flight control handover" information element;

- whether the drone supports camera control handover to an official authority, for example from the "Camera control handover" information element;

- what command sets or protocols are supported by the aircraft, for example from the "Command sets" information element, etc.

All of these pieces of information help a third party (i.e. an authority) decide whether to attempt to establish a connection with a newly identified flying object over a cellular network, for example if the third party (i.e. an authority) wishes to influence, change, adjust, control current or future flight parameters or drone settings (including changing altitude, speed, heading, trajectory, etc.) or any other drone functions, such as turning off or on the built-in camera.

In one embodiment of the present invention, the first air interface is a bi-directional interface, and the user controlling the drone is informed that a third party is taking control of the drone.

Based on the MNO Identifier information element, a third party can identify the MNO operating the cellular network that can be used to access the drone through the third air interface. Alternatively, the MNO Identifier information element indicates the MNO whose subscriber is the UE inside the drone. If necessary (and also if there are additional information elements in the data set), the third party can learn more about how to access the newly identified flying object through the infrastructure elements provided by the MNO operator, for example:

- what IP address should be used to access the MNO operator's domain, for example, from the "IP address" information element;

- what username should be used, for example from the information element "Username #1";

- what password should be used, for example from the "Password #1" information element.

Finally, a third party (i.e. an official body) can exchange information (including flight control commands, camera control commands, etc.) between its servers and the drone (drone flight control unit) via a selected cellular network and functional a UE device element implemented within the aircraft, whereby a third party may use command sets and/or protocols actually supported by the aircraft.

In FIG. 2 shows the entities that can be involved in the method according to the invention: a drone, a third party receiver, a third party network, an MNO core network, and an MNO radio access network with at least one base station. The interface for accessing the MNO's domain is the IF _NW interface between the third party network and the MNO's core network.

In FIG. 3 shows the IF _Drone interface between the UE device functional element 17 and the flight control unit 16 within the drone 10. The UE device functional element 17 is connected to the core network 50 via the radio access network 52 and via the third radio interface 40, which may be an LTE Uu interface.

As mentioned above, the third aspect of the present invention is a negotiation method for handover control of a drone to an MNO or a third party based on a data set received from the drone. The control handover may, for example, be dependent on certain capabilities (e.g., specified using the Flight Control Handover and Camera Control Handover information elements as described above) and/or certain conditions (e.g., coordinates, altitude, drone heading, and etc., the owner of the drone, such as a third party, etc.). Drone control handover may, for example, include handover of only a portion of the drone control functions (eg, associated with flight control, camera control, etc.) or handover of the entire range of control functions.

The flight control handover may include the exchange of flight control commands and navigation data over the MNO's cellular network (ie, over a third radio interface). Flight control commands may be issued by a third party or by the MNO.

Turning on and off a camera built into or mounted on an aircraft may involve exchanging camera control commands over the MNO's cellular network (i.e., through a third radio interface). Camera control commands may be given by a third party or by the MNO.

The two control options - "Flight Control" and "Camera Control" - should not be considered limiting. On the contrary, these two terms serve only as examples of the wide range of drone control options.

In order for the control handover to be performed properly, a corresponding group of command sets and/or corresponding protocols is selected from a plurality of predetermined command sets and/or protocols. If these protocols are not implemented or the control commands are unknown to one side (for example, the drone or the infrastructure side), the drone control handover may be terminated. As stated above, the MNO and/or a third party can learn from the data set received from the drone which command sets or protocols are supported by the drone.

The fourth aspect of the present invention, mentioned above, is to determine the settings of the quality of service (QoS, Quality of Service) and the formation of billing records (CDR).

The processing of traffic exchanged between the third party network and the aircraft (so-called "third party traffic") may differ from the processing of "traditional" traffic, for example, in terms of QoS settings and/or the number and type of entities involved in the data exchange, and /or generating CDR records, etc.

In one embodiment of the invention, "third party traffic" is given a higher priority than "legacy traffic" in the MNO operator's domain. In another embodiment of the invention, entities in the MNO operator domain are configured for a particular QoS class (e.g., in accordance with the QoS Class Identifier (QCI) values defined in 3GPP TS 23.203) to provide fast and/or highly reliable connectivity. for "third party traffic" data.

For example, a trio of parameters, including priority, packet delay, and packet error/loss ratio, defining a particular QoS class, can be configured as follows: the priority level can be set to 2.5, the packet transmission delay can be approximately 50 ms, and the packet error/loss ratio can be approximately 10 ^-3 for a new QoS class called "XY" (see Table 3 for standardized QCI characteristics modified for drone operation, see Table 6.1.7 in the 3GPP TS document 23.203).

Table 3 QCI Resource type Priority level Packet transmission delay
(note 13) Relative size of missed packets
(note 2 Service examples 1
GBR 2 100ms ^10-2 Voice transmission during a conversation 2 4 150ms ^10-3 Video transmission with conversation (live broadcast) 3 3 50ms ^10-3 Real-time games, V2X messages XY 2.5 50ms ^10-3 Drone Messages 4 5 300ms ^10-6 Transfer video without talking (buffered streaming) 65 0.7 75 ms
^10-2 Push To Talk voice (e.g. MCPTT) mission-critical user layer 66
2 100ms
^10-2 Non-critical user-level Push To Talk voice communication 75 2.5 50ms ^10-2 V2X messages

In yet another embodiment of the invention, separate charge records (CDRs) are generated in the MNO's domain to bill a third party, rather than the subscriber, for third party traffic (with the potential for additional service charges).

The drawings show the transmission of a data set through the second radio interface. Alternatively, the data set may be transmitted via a third air interface, or upon request from a mobile operator (see arrows 1 and 2 in FIG. 4), which in turn may respond to a request received from a third party via the IF _NW interface ( see arrow 0), or initiated by a UE device functional element implemented inside the drone (in this case, arrow 2 is not a response to arrow 1, but arrow 1 may be an acknowledgment of the transmission of the data set on arrow 2). The contents of the dataset ("digital license plate") can be forwarded to a third party (arrow 3).

For a request-response message pair used on a third radio interface (e.g., the LTE Uu interface in the case of LTE), a new message pair may need to be defined, such as Radio Resource Control (RRC) messages, or an existing message pair may be improved. . In FIG. 5 shows the first option: RRC message "Request data set" corresponds to arrow 1, and RRC message "Response with data set", which may contain information about the "digital license plate" according to table 2 (in whole or in part), corresponds to arrow 2 .

The Drone Identifier information element shown in Table 2 may contain (or may be derived from) identifiers used in the mobile communications system. For example, according to 3GPP, in a mobile communication system, a drone identifier may partially or completely contain or include IMEI or IMEI-SV (cellular modem equipment identifier) or IMSI (subscriber identifier).

It should be noted that the names and encodings of messages and/or information elements (IEs) described herein should be understood as examples only. There are many other options for the exchange of information between the involved objects, as well as options for encoding parameters and their value fields. The present invention is in no way limited to the coding examples described here.

The order of actions performed in the various processes described herein in actual developments may differ from those set forth within the scope of the invention.

In addition, the parameters proposed for use can be redistributed in one way or another. For example, they may be collected in a new or existing hierarchical structure, or grouped with other information elements, such as in a list.

Various aspects of the invention may be considered separately, jointly or in combination with each other.

Moreover, the teachings of the present invention are not limited to drones, but can be applied to any other type of moving objects, including land and water vehicles.

Claims (16)

1. A method for ensuring the provision of information by a mobile mechanism to a recipient device, including the transmission by the mobile mechanism through the second radio interface of information to provide access to the recipient device to control this mobile mechanism via a cellular mobile communication interface, while the second radio interface is different from the first radio interface used to control the mobile mechanism by its operator. 2. The method according to claim 1, in which the information is used to perform at least one of the following actions, optionally, in any combination of them: - identification of the mobile mechanism; - identification of the owner of the mobile mechanism; - identification of the type of mobile mechanism and the capabilities supported by the mobile mechanism; - identification of the possibilities of joint work of the mobile mechanism with the cellular modem; - selection of a mobile communication network to enable connection to the mobile mechanism. 3. The method according to claim 1 or 2, wherein the information is transmitted in a broadcast mode. 4. A method according to any one of the preceding claims, wherein the information is of such a nature that it may change over time. 5. The method according to any one of paragraphs. 1-3, in which the information contains a registered mobile mechanism identifier that allows the recipient to obtain information for managing the mobile mechanism from the protected area. 6. A method according to any one of the preceding claims, wherein the mobile mechanism is an unmanned aerial vehicle and the information is used to perform a handover control negotiation procedure by the recipient device. 7. The method according to any one of paragraphs. 1-5, in which the mobile mechanism is an unmanned aerial vehicle, and the information is used to perform a negotiation procedure by the recipient device to handover control of the camera associated with this unmanned aerial vehicle. 8. The method according to claim 6 or 7, wherein the information includes a mobile operator identifier for identifying a mobile network operator operating a cellular network that can be used to access the unmanned aerial vehicle via a mobile cellular interface, while exchanging commands between the recipient device and the unmanned aerial vehicle are carried out through a mobile cellular communication interface and a functional element of the user device located inside the unmanned aerial vehicle. 9. The method according to any one of paragraphs. 6-8, wherein the information includes at least one of vehicle height information, vehicle trajectory information, and activity information of a camera associated with the vehicle. 10. A method according to any one of the preceding claims, wherein the information is used to specify a quality of service for communication between the mobile mechanism and the recipient device. 11. A method according to any one of the preceding claims, wherein the information is used to generate billing records for communication between the mobile mechanism and the recipient's device.

Images