P
US10666705B2ActiveUtilityPatentIndex 47

Data restoration for datacenter failover

Assignee: UBER TECHNOLOGIES INCPriority: Sep 14, 2015Filed: Sep 20, 2018Granted: May 26, 2020
Est. expirySep 14, 2035(~9.2 yrs left)· nominal 20-yr term from priority
Inventors:AGGARWAL NIKUNJCORBIN JOSHUA
H04L 69/40H04L 67/02H04L 2463/062H04L 63/061H04L 63/0428
47
PatentIndex Score
0
Cited by
9
References
15
Claims

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

exact text as granted — not AI-modified
What is claimed is: 
     
       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.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.