# US 2017/0285633 A1 · Drone control registration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0285633 A1
- Document ID: US20170285633A1
- Status: Published application
- Kind: A1
- Application number: 15/088,949
- Filed: 2016-04-01
- Published: 2017-10-05
- Earliest claimed: 2016-04-01
- Assignees: lntel Corporation
- Applicants: Intel Corporation
- Inventors: RAJESH POORNACHANDRAN; NED M. SMITH
- Web page: https://patentgrep.com/patent/US20170285633A1

## CPC

- G05D 1/0022: {characterised by the communication link (data switching networks in general H04L12/00)}
- G08G 5/55: for a single aircraft
- G08G 5/57: for unmanned aircraft
- B64U 50/37: Charging when not in flight
- B64U 2201/10: autonomous, i.e. by navigating independently from ground or air stations, e.g. by using inertial navigation systems [INS]
- B64U 2201/20: Remote controls
- H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- G05D: SYSTEMS FOR CONTROLLING OR REGULATING NON-ELECTRIC VARIABLES
- G08G: TRAFFIC CONTROL SYSTEMS (guiding railway traffic, ensuring the safety of railway traffic B61L; arrangement of road signs or traffic signals E01F9/00; radar or analogous systems, sonar systems, lidar systems specially adapted for traffic control G01S13/91, G01S15/88, G01S17/88; {radar or analogous systems, sonar systems, lidar systems specially adapted for anti-collision purposes G01S13/93, G01S15/93, G01S17/93})
- B64U: UNMANNED AERIAL VEHICLES [UAV]; EQUIPMENT THEREFOR
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A drone includes technology for tracking controllers. A controller registration module (CRM) in the drone enables the drone to receive a first controller identifier from a first remote device. In response to receiving the first controller identifier, the CRM registers the first remote device as the current controller for the drone. Registering comprises adding the first controller identifier to a drone control registration record (DCRR) in the drone. Also, the DCRR is added to a block chain in remote storage. The CRM then receives a second controller identifier from a second remote device. In response, the CRM registers the second remote device as the current controller. Registering comprises creating an updated DCRR that identifies the second controller as the current controller. The updated DCRR is then added to the block chain. Other embodiments are described and claimed.

## Claims

### Claim 1

A drone with technology for tracking controllers, the drone comprising:
a communications subsystem which enables the drone to receive data from remote devices; and
a controller registration module which enables the drone to:
receive a first controller identifier from a first remote device, via the communications subsystem;
in response to receiving the first controller identifier, register the first remote device as a current controller for the drone, wherein registering the first remote device comprises adding the first controller identifier to a drone control registration record (DCRR) in the drone;
after adding the first controller identifier to the DCRR, cause the DCRR to be added to a block chain in remote storage;
after adding the first controller identifier to the DCRR, receive a second controller identifier from a second remote device;
in response to receiving the second controller identifier, register the second remote device as the current controller for the drone, wherein registering the second remote device comprises creating an updated DCRR that identifies the second remote device as the current controller; and
after creating the updated DCRR, cause the updated DCRR to be added to the block chain in remote storage.

### Claim 2 (depends on 1)

A drone according to claim 1, further comprising:
technology to establish a trusted execution environment (TEE) within the drone, wherein the technology to establish the TEE comprises protected storage; and
wherein the controller registration module is configured to:
receive the controller identifiers from the first and second remote devices while executing in the TEE;
create the updated DCRR while executing in the TEE; and
save the DCRR in the protected storage while executing in the TEE.

### Claim 3 (depends on 1)

A drone according to claim 1, wherein:
the first controller identifier comprises a first flight control key; and
the second controller identifier comprises a second flight control key.

### Claim 4 (depends on 1)

A drone according to claim 1, wherein the controller registration module enables the drone to:
receive autonomous flight instructions for the drone from the first remote device; and
save at least some of the autonomous flight instructions in the DCRR before causing the DCRR to be added to the block chain in remote storage.

### Claim 5 (depends on 4)

A drone according to claim 4, wherein the controller registration module enables the drone to:
after receiving autonomous flight instructions at the drone from the first remote device, travel outside of a coverage area of the first remote device; and
follow the autonomous flight instructions while traveling outside of the coverage area of the first remote device.

### Claim 6 (depends on 5)

A drone according to claim 5, wherein, when the autonomous flight instructions prescribe a flight path from the coverage area of the first remote device to the coverage area of the second remote device, the controller registration module enables the drone to:
after following the autonomous flight instructions while traveling outside of the coverage area of the first remote device, enter a coverage area of the second remote device; and
receive the second controller identifier from the second remote device after entering the coverage area of the second remote device.

### Claim 7 (depends on 1)

A drone according to claim 1, wherein, when the second device comprises a cellular base station (CBS), the controller registration module enables the drone to:
receive flight instructions from the CBS directing the drone to a recharging base station associated with the CBS;
follow the flight instructions from the CBS directing the drone to the recharging base station; and
use the recharging base station to recharge the drone.

### Claim 8 (depends on 1)

A drone according to claim 1, wherein the controller registration module enables the drone to:
receive the first controller identifier from a cellular base station (CBS); and
receive the second controller identifier from a satellite.

### Claim 9 (depends on 8)

A drone according to claim 8, wherein the controller registration module enables the drone to send telemetry data from the drone to the satellite after registering the satellite as the current controller for the drone.

### Claim 10

An apparatus to enable a drone to track controllers, the apparatus comprising:
at least one non-transitory machine-accessible storage medium; and
a controller registration module in the machine-accessible storage medium which, when executed by a processor of a drone, enables the drone to:
receive a first controller identifier from a first remote device;
in response to receiving the first controller identifier, register the first remote device as a current controller for the drone, wherein registering the first remote device comprises adding the first controller identifier to a drone control registration record (DCRR) in the drone;
after adding the first controller identifier to the DCRR, cause the DCRR to be added to a block chain in remote storage;
after adding the first controller identifier to the DCRR, receive a second controller identifier from a second remote device;
in response to receiving the second controller identifier, register the second remote device as the current controller for the drone, wherein registering the second remote device comprises creating an updated DCRR that identifies the second remote device as the current controller; and
after creating the updated DCRR, cause the updated DCRR to be added to the block chain in remote storage.

### Claim 11 (depends on 10)

An apparatus according to claim 10, wherein the controller registration module is configured to:
execute in a trusted execution environment (TEE) in the drone, wherein the TEE comprises protected storage;
receive the controller identifiers from the first and second remote devices while executing in the TEE;
create the updated DCRR while executing in the TEE; and
save the DCRR in the protected storage while executing in the TEE.

### Claim 12 (depends on 10)

An apparatus according to claim 10, wherein the controller registration module enables the drone to:
receive autonomous flight instructions for the drone from the first remote device; and
save at least some of the autonomous flight instructions in the DCRR before causing the DCRR to be added to the block chain in remote storage.

### Claim 13 (depends on 10)

An apparatus according to claim 10, wherein the controller registration module enables the drone to:
after receiving autonomous flight instructions at the drone from the first remote device, travel outside of a coverage area of the first remote device; and
follow the autonomous flight instructions while traveling outside of the coverage area of the first remote device.

### Claim 14 (depends on 13)

An apparatus according to claim 13, wherein, when the autonomous flight instructions prescribe a flight path from the coverage area of the first remote device to the coverage area of the second remote device, the controller registration module enables the drone to:
after following the autonomous flight instructions while traveling outside of the coverage area of the first remote device, enter a coverage area of the second remote device; and
receive the second controller identifier from the second remote device after entering the coverage area of the second remote device.

### Claim 15 (depends on 10)

An apparatus according to claim 10, wherein, when the second device comprises a cellular base station (CBS), the controller registration module enables the drone to:
receive flight instructions from the CBS directing the drone to a recharging base station associated with the CBS;
follow the flight instructions from the CBS directing the drone to the recharging base station; and
use the recharging base station to recharge the drone.

### Claim 16 (depends on 10)

An apparatus according to claim 10, wherein the controller registration module enables the drone to:
receive the first controller identifier from a cellular base station (CBS); and
receive the second controller identifier from a satellite.

### Claim 17 (depends on 16)

An apparatus according to claim 16, wherein the controller registration module enables the drone to send telemetry data from the drone to the satellite after registering the satellite as the current controller for the drone.

### Claim 18

A method for tracking drone controllers, the method comprising:
at a drone, receiving a first controller identifier from a first remote device;
in response to receiving the first controller identifier, registering the first remote device as a current controller for the drone, wherein registering the first remote device comprises adding the first controller identifier to a drone control registration record (DCRR) in the drone;
after adding the first controller identifier to the DCRR, causing the DCRR to be added to a block chain in remote storage;
after adding the first controller identifier to the DCRR, receiving a second controller identifier from a second remote device;
in response to receiving the second controller identifier, registering the second remote device as the current controller for the drone, wherein registering the second remote device comprises creating an updated DCRR that identifies the second remote device as the current controller; and
after creating the updated DCRR, causing the updated DCRR to be added to the block chain in remote storage.

### Claim 19 (depends on 18)

A method according to claim 18, further comprising:
saving the DCRR in protected storage in the drone.

### Claim 20 (depends on 18)

A method according to claim 18, further comprising:
establishing a trusted execution environment (TEE) in the drone, wherein the TEE provides security for the protected storage; and
executing a controller registration module in the TEE; and
wherein the operations of receiving controller identifiers from the first and second remote devices are performed by the controller registration module while executing in the TEE;
wherein the operation of creating the updated DCRR is performed by the controller registration module while executing in the TEE; and
wherein the controller registration module saves the DCRR in the protected storage in the TEE while executing in the TEE.

### Claim 21 (depends on 18)

A method according to claim 18, further comprising:
at the drone, receiving autonomous flight instructions for the drone from the first remote device; and
saving at least some of the autonomous flight instructions in the DCRR before causing the DCRR to be added to the block chain in remote storage.

### Claim 22 (depends on 18)

A method according to claim 18, wherein:
the second device comprises a cellular base station (CBS); and
the method further comprises:
receiving flight instructions from the CBS directing the drone to a recharging base station associated with the CBS;
following the flight instructions from the CBS directing the drone to the recharging base station; and
using the recharging base station to recharge the drone.

### Claim 23

A method for determining drone ownership, the method comprising:
obtaining a copy of at least part of a block chain containing at least one drone control registration record (DCRR) for a drone; and
using the DCRR to determine which device is registered as a controller of the drone.

### Claim 24 (depends on 23)

A method according to claim 23, wherein the operation of using the DCRR to determine which device is registered as a controller of the drone is performed when the drone is located in an area of overlapping coverage involving a first coverage area from a first potential drone controller and a second coverage area from a second potential drone controller.
