IP Library Granted Patent US 10,666,705
Granted Patent B2
US 10,666,705 · App. 16/136,443 · Granted May 26, 2020

Data restoration for datacenter failover

Inventors: Nikunj Aggarwal (San Francisco, CA); Joshua Corbin (San Francisco, CA)
Assignee: Uber Technologies, Inc.
H04L67/02H04L63/0428H04L69/40H04L63/061H04L2463/062
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,666,705
App. No.
16/136,443
Granted
May 26, 2020
Kind
B2
Abstract

A failover system can receive active data from user devices running an application specific to a service entity providing an application service. For each user device, the active data can indicate a current status. The failover system can transmit restoration data to the user devices for storage to restore the current status of the user devices in the case of a failover event. When a failover event occurs, the failover system can recover the restoration data from a first user device to restore the current status of the application service for the first user device.

Claims (35)

1. A method for restoring data in a datacenter failover, the method performed by at least one processor of a failover system and comprising:

receiving, at the failover system, active data from a user device executing an application associated with a service entity, the service entity providing an application service using an active data center;

identifying, by the failover system, a first portion of the active data associated with a service state change, and a second portion of the active data associated with a device ping;

storing, by the failover system, first restoration data associated with the first portion of the active data at a backup datacenter; and

instructing, by the failover system, the user device to store second restoration data associated with the second portion of the active data.

2. The method of claim 1 , further comprising:

identifying, by the failover system, a failover event indicating a failure of the active datacenter;

responsive to the identification of the failover event, retrieving, by the failover system, the second restoration data from the user device; and

providing, by the failover system, the retrieved second restoration data to the backup datacenter.

3. The method of claim 2 wherein identifying the failover event further comprises detecting a failure of the active datacenter to respond to a periodic heartbeat message.

4. The method of claim 1 wherein the application service facilitates transportation services between riders and drivers, and the service state change includes a trip transition.

5. The method of claim 4 wherein a trip transition includes beginning a trip, making a pickup, or making a drop-off.

6. The method of claim 1 wherein the device ping indicates a location of the user device.

7. A failover system for restoring autonomous vehicle data in a datacenter failover, the system comprising:

a real time replication system, adapted to identify a failover event of an active datacenter;

a replication module, executed by the real time replication system, and adapted to:

receive active data from an autonomous vehicle computer, the autonomous vehicle computer in communication with the active datacenter, the active data indicating a current status of the autonomous vehicle;

transmit to the autonomous vehicle computer, restoration data for the autonomous vehicle computer, the restoration data usable to restore the current status of the autonomous vehicle computer;

responsive to an indication from the real time replication system that the active datacenter has failed, recover the restoration data from the autonomous vehicle computer; and

provide the recovered restoration data to a backup datacenter.

8. The failover system of claim 7 wherein the real time replication system is adapted to identify the failover event by detecting a failure of the active datacenter to respond to a periodic heartbeat message.

9. The failover system of claim 7 , wherein the active data includes a first portion associated with a service state change, and a second portion associated with a device ping.

10. The failover system of claim 9 , wherein the restoration data that the replication module is adapted to transmit to the autonomous vehicle computer is the second portion; and

wherein the replication module is further adapted to transmit the first portion to the backup datacenter.

11. A computer-implemented method for restoring data in a datacenter failover, the method performed by one or more processors of a failover system and comprising:

receiving, at the failover system, active data from a user device running an application specific to a service entity, the service entity providing an application service using an active datacenter, the active data indicating a current status of the user device;

transmitting, to the user device, restoration data for the user device, the restoration data usable to restore the current status of the user device;

responsive to identifying, by the failover system, a failover event indicating a failure of the active datacenter, recovering the restoration data from the user device to restore the current status of the user device; and

providing, by the failover system, the recovered restoration data to a backup datacenter.

12. The method of claim 11 , wherein the service entity comprises a transportation facilitation system that facilitates transportation services between requesting riders and available drivers.

13. The method of claim 12 , wherein the user device is a driver device.

14. The method of claim 12 , wherein the user device is a rider device.

15. The method of claim 11 , further comprising:

encrypting a set of keys from the active data;

wherein the restoration data comprises the encrypted set of keys.

Assignments (7)
RELEASE OF SECURITY INTEREST Recorded Oct 3, 2024
From: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 069110/0508 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT (TERM LOAN) AT REEL 050767, FRAME 0076 Recorded Sep 11, 2024
From: MORGAN STANLEY SENIOR FUNDING, INC. AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 069133/0167 →
RELEASE OF SECURITY INTEREST Recorded Mar 10, 2021
From: CORTLAND CAPITAL MARKET SERVICES LLC, AS ADMINISTRATIVE AGENT
To: UBER TECHNOLOGIES, INC.
Reel/Frame 055547/0404 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Oct 24, 2019
From: UBER TECHNOLOGIES, INC.
To: CORTLAND CAPITAL MARKET SERVICES LLC
Reel/Frame 050817/0600 →
SECURITY INTEREST Recorded Oct 18, 2019
From: UBER TECHNOLOGIES, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 050767/0109 →
SECURITY INTEREST Recorded Oct 18, 2019
From: UBER TECHNOLOGIES, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 050767/0076 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 20, 2018
From: AGGARWAL, NIKUNJ; CORBIN, JOSHUA
To: UBER TECHNOLOGIES, INC.
Reel/Frame 046923/0780 →