AUTOMATED RETURN OF TELEOPERATED VEHICLES
A method includes obtaining, from an operator of a robot, a return execution lease associated with one or more commands for controlling the robot that is scheduled within a sequence of execution leases. The robot is configured to execute commands associated with a current execution lease that is an earliest execution lease in the sequence of execution leases that is not expired. The method includes obtaining an execution lease expiration trigger triggering expiration of the current execution lease. After obtaining the trigger, the method includes determining that the return execution lease is a next current execution lease in the sequence. While the return execution lease is the current execution lease, the method includes executing the one or more commands for controlling the robot associated with the return execution lease which cause the robot to navigate to a return location remote from a current location of the robot.
1 . Data processing hardware for controlling a robot, the data processing hardware configured to:
receive commands for controlling the robot from an operator;
confirm that the received commands are associated with a current execution lease within a queue of execution leases;
control the robot based on the received commands that are associated with the current execution lease;
receive a lease expiration trigger;
generate a return trigger based on the lease expiration trigger; and
generate a return command for controlling the robot to navigate to a return location based on the return trigger.
2 . The data processing hardware of claim 1 , further configured to:
receive, from the operator, a return execution lease associated with a future execution lease within the queue of execution leases;
expire the current execution lease in response to receiving the lease expiration trigger; and
determine that the return execution lease is a next current execution lease in the queue of execution leases based on the expiration of the previous current execution lease,
wherein generating the return trigger is in response to determining that the return execution lease is the next current execution lease in the queue of execution leases.
3 . The data processing hardware of claim 1 , further configured to:
determine that at least one of the received commands is not associated with the current execution lease; and
in response to determining that at least one of the received commands is not associated with the current execution lease, disregard the at least one of the received commands.
4 . The data processing hardware of claim 1 , further configured to:
determine that at least one of the received commands is associated with a future execution lease; and
in response to determining that at least one of the received commands is associated with the future execution lease, queue the at least one of the received commands for execution with the future execution lease.
5 . The data processing hardware of claim 1 , wherein receiving the lease expiration trigger comprises determining that the robot has lost communication with the operator of the robot.
6 . The data processing hardware of claim 1 , wherein receiving the lease expiration trigger comprises receiving a lease expiration command from the operator of the robot.
7 . The data processing hardware of claim 1 , wherein the return command comprises one or more parameters defining the robot's movement as the robot executes the return command, the one or more parameters including: a first parameter that define how fast the robot moves, a second parameter that defines how close the robot can get to obstacles, and/or a third parameter that defines whether the robot can step into terrain that is not clearly visible by sensors of the robot.
8 . The data processing hardware of claim 1 , wherein the return command is configured to prevent the robot from travelling further than a predetermined distance from a location of the robot when the lease expiration trigger is received.
9 . The data processing hardware of claim 1 , wherein the return location comprises a location previously visited by the robot.
10 . The data processing hardware of claim 1 , further configured to:
receive a request for a root lease from the operator; and
provide the root least to the operator,
wherein the received commands are associated with the root lease.
11 . A method comprising:
receiving, by data processing hardware of a robot from an operator, commands for controlling the robot;
confirming, by the data processing hardware, that the received commands are associated with a current execution lease within a queue of execution leases;
controlling, by the data processing hardware, the robot based on the received commands that are associated with the current execution lease;
receiving, by the data processing hardware, a lease expiration trigger;
generating, by the data processing hardware, a return trigger based on the lease expiration trigger; and
generating, by the data processing hardware, a return command for controlling the robot to navigate to a return location based on the return trigger.
12 . The method of claim 11 , further comprising:
receiving, from the operator, a return execution lease associated with a future execution lease within the queue of execution leases;
expiring the current execution lease in response to receiving the lease expiration trigger; and
determining that the return execution lease is a next current execution lease in the queue of execution leases based on the expiration of the previous current execution lease,
wherein generating the return trigger is in response to determining that the return execution lease is the next current execution lease in the queue of execution leases.
13 . The method of claim 11 , further comprising:
determining that at least one of the received commands is not associated with the current execution lease; and
in response to determining that at least one of the received commands is not associated with the current execution lease, disregarding the at least one of the received commands.
14 . The method of claim 11 , further comprising:
determining that at least one of the received commands is associated with a future execution lease; and
in response to determining that at least one of the received commands is associated with the future execution lease, queueing the at least one of the received commands for execution with the future execution lease.
15 . The method of claim 11 , wherein receiving the lease expiration trigger comprises determining that the robot has lost communication with the operator of the robot.
16 . The method of claim 11 , wherein receiving the lease expiration trigger comprises receiving a lease expiration command from the operator of the robot.
17 . The method of claim 11 , wherein the return command comprises one or more parameters defining the robot's movement as the robot executes the return command, the one or more parameters including: a first parameter that define how fast the robot moves, a second parameter that defines how close the robot can get to obstacles, and/or a third parameter that defines whether the robot can step into terrain that is not clearly visible by sensors of the robot.
18 . The method of claim 11 , wherein the return command is configured to prevent the robot from travelling further than a predetermined distance from a location of the robot when the lease expiration trigger is received.
19 . The method of claim 11 , wherein the return location comprises a location previously visited by the robot.
20 . The method of claim 11 , further comprising:
receiving a request for a root lease from the operator; and
providing the root least to the operator,
wherein the received commands are associated with the root lease.