Failover for mobile devices

• US 9,848,019 B2
• Filed: 05/30/2013
• Issued: 12/19/2017
• Est. Priority Date: 05/30/2013
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Kotecha, Lalit R., Gudlavenkatasiva, Bhaskar R.
• Primary Examiner(s): Dennison, Jerry
• Application Number:
  US13/905,472
• Publication Number:
  US 20140358985A1
• Time in Patent Office: 1,664 Days
• CPC Class Codes: H04L 65/1053 IP private branch exchange [PBX] functionality entities or arrangements circuit switched PBXs H04M3/00
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1093 by adding participants; by removing participants

Abstract

A device may receive information that identifies a failover configuration associated with a user device. The failover configuration may identify a backup user device. The device may receive information indicating that a failover condition, identified in the failover configuration, has been satisfied. The device may identify the backup user device based on receiving the information indicating that the failover condition has been satisfied. The device may contact the backup user device based on identifying the backup user device. The device may determine that a service request, associated with a service and intended for the user device, is to be forwarded to the backup user device based on contacting the backup user device. The service may be identified by the failover configuration. The device may forward the service request to the backup user device to permit the backup user device to obtain the service rather than the user device.

Claims

1. A device, comprising:

one or more processors to;

receive information that identifies a failover configuration associated with a user device,

the failover configuration indicating;

the user device associated with a first failover condition,

a first backup user device associated with a first service and a second failover condition, and

a second backup user device associated with a second service and a third failover condition,

 

the first service being different than the second service, and

 

the first backup user device being different than the second backup user device;

receive information, from the user device, indicating that the first failover condition, identified in the failover configuration, has been satisfied;

identify the first backup user device and the second backup user device based on the failover configuration and receiving the information indicating that the first failover condition has been satisfied;

contact the first backup user device based on identifying the first backup user device;

contact the second backup user device based on identifying the second backup user device;

determine that a first service request, associated with the first service and intended for the user device, is to be forwarded to the first backup user device based on contacting the first backup user device and the second failover condition,

the first service including at least one of a messaging service, an application service, or a video conferencing service,

forward the first service request to the first backup user device to permit the first backup user device to obtain the first service rather than the user device;

determine that a second service request, associated with the second service and intended for the user device, is to be forwarded to the second backup user device based on contacting the second backup user device and based on the third failover condition,

the second service including at least one different one of the messaging service, the application service, or the video conferencing service than the first service; and

forward the second service request to the second backup user device to permit the second backup user device to obtain the second service rather than the user device.

2. The device of claim 1, where the one or more processors are further to:

receive information, associated with a user input, identifying the first backup user device, the first failover condition, or the first service; and

where the one or more processors, when receiving the information that identifies the failover configuration associated with the user device, are to;

receive the information that identifies the failover configuration based on receiving the information associated with the user input.

3. The device of claim 1, where the first failover condition identifies at least one of:

a threshold power level associated with the user device;

a threshold signal strength associated with the user device;

an indication that the user device is outside of a coverage area of a service provider network;

or

an indication that the user device is connected to a roaming network.

4. The device of claim 1, where the one or more processors are further to:

identify a first failover priority associated with the first backup user device;

identify a second failover priority associated with a third backup user device; and

compare the first failover priority to the second failover priority;

where the one or more processors, when identifying the first backup user device, are to;

identify the first backup user device based on comparing the first failover priority to the second failover priority.

5. The device of claim 1, where the one or more processors, when forwarding the first service request to the first backup user device, are to:

provide user information, associated with the first service, to the first backup user device.

6. The device of claim 1, where the first service includes the video conferencing service, and

where the one or more processors, when forwarding the first service request to the first backup user device, are to:

forward an existing first service request, associated with an in progress video call session of the video conferencing service between the user device and a third party device, from the user device to the first backup user device without initiating a new video call session between the first backup user device and the third party device.

7. The device of claim 1, where the one or more processors, are further to:

receive information, from the first backup user device, indicating that the second failover condition, associated with the first backup user device, has been satisfied;

identify a third backup user device based on detecting that the second failover condition has been satisfied;

determine that a third service request is to be forwarded to the third backup user device; and

forward the third service request, associated with the first service, to the third backup user device.

19. The device of claim 1, where the second failover condition identified by the failover configuration associated with the user device, identifies a threshold power level associated with the first backup user device.

20. The device of claim 1, where the second failover condition identified by the failover configuration associated with the user device, identifies a threshold signal strength associated with the first backup user device.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors, cause the one or more processors to;

receive information that identifies a failover configuration associated with a user device,

the failover configuration indicating a first service request intended for the user device is to be provided to a first backup user device when the user device is unreachable and a second service request intended for the user device to be provided to a second backup user device when the user device is unreachable,

the failover configuration indicating a first failover condition for the first backup user device and a second failover condition for the second backup user device,

the first service request including at least one of a messaging service request, an application service request, or a video conferencing service request,

the second service request including at least one different one of the messaging service request, the application service request, of the video conferencing service request, and

the first backup user device being different than the second backup user device;

receive, from a device associated with a service provider network, information indicating that the user device is unreachable;

identify the first backup user device and the second backup user device based on the failover configuration and receiving the information indicating that the user device is unreachable;

contact the first backup user device based on identifying the first backup user device and determine whether the first failover condition is satisfied;

contact the second backup user device based on identifying the second backup user device and determine whether the second failover condition is satisfied;

receive the first service request associated with a first service and intended for the user device,

provide, based on the failover configuration, the first service request to the first backup user device to permit the first backup user device to receive a first service rather than the user device;

receive the second service request, associated with a second service and intended for the user device; and

provide, based on the failover configuration, the second service request to the second backup user device to permit the second backup user device to obtain the second service rather than the user device.

9. The non-transitory computer-readable medium of claim 8, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive information, associated with a user input, identifying the first backup user device, a failover condition associated with the user device, or the first service; and

where the one or more instructions, that cause the one or more processors to receive the information that identifies the failover configuration, cause the one or more processors to;

receive the information that identifies the failover configuration based on receiving the information associated with the user input.

10. The non-transitory computer-readable medium of claim 8, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

identify a first failover priority associated with the first backup user device;

identify a second failover priority associated with a third backup user device; and

compare the first failover priority to the second failover priority;

where the one or more instructions, that cause the one or more processors to identify the first backup user device, cause the one or more processors to;

identify the first backup user device based on comparing the first failover priority to the second failover priority.

11. The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to provide the first service request to the first backup user device, cause the one or more processors to:

provide user information, associated with the first service, to the first backup user device.

12. The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to provide the first service request to the first backup user device, cause the one or more processors to:

provide an existing first service request, associated with an in progress session of the first service, from the user device to the first backup user device without terminating the in progress session.

13. The non-transitory computer-readable medium of claim 8, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

receive information, from the first backup user device, indicating that the first failover condition, associated with the first backup user device, has been satisfied;

identify a third backup user device based on detecting that the first failover condition has been satisfied;

determine that a third service request is to be forwarded to the third backup user device; and

provide the third service request, associated with the first service, to the third backup user device.

14. The non-transitory computer-readable medium of claim 13, where the first failover condition identifies an indication that the first backup user device is connected to a roaming network.

15. A method, comprising:

receiving, by a device, information that identifies a failover configuration associated with a user device and a backup user device

the failover configuration indicating;

the user device associated with a first failover condition,

a first backup user device associated with a first service and a second failover condition, and

a second backup user device associated with a second service and a third failover condition,

the first service being different than the second service, and

the first backup user device being different than the second backup user device;

obtaining, by the device, information, from the user device, indicating that the first failover condition, associated with the user device identified in the failover configuration, has been satisfied;

identifying, by the device, the first backup user device and the second backup user device based on receiving the information indicating that the first failover condition has been satisfied;

interacting, by the device, with the first backup user device based on identifying the first backup user device;

interacting, by the device, with the second backup user device based on identifying the second backup user device;

determining, by the device, that a first service request, associated with flail the first service and intended for the user device, is to be forwarded to the first backup user device based on interacting with the first backup user device and the second failover condition,

the first service including at least one of a messaging service, an application service, or a video conferencing service,

the first service being identified by the failover configuration; and

forwarding, by the device, the first service request to the first backup user device to permit the first backup user device to obtain the first service rather than the user device;

determining, by the device, that a second service request, associated with the second service and intended for the user device, is to be forwarded to the second backup user device based on interacting with the second backup user device and the third failover condition,

the second service including at least one different one of the messaging service, the application service, or the video conferencing service than the first service; and

forwarding, by the device, the second service request to the second backup user device to permit the second backup user device to obtain the second service rather than the user device.

16. The method of claim 15, further comprising:

receiving information, associated with a user input, identifying the first backup user device, the first failover condition, or the first service; and

where receiving the information that identifies the failover configuration associated with the user device comprises;

receiving the information that identifies the failover configuration based on receiving the information associated with the user input.

17. The method of claim 15, further comprising:

identifying a first failover priority associated with the first backup user device;

identifying a second failover priority associated with a third backup user device; and

comparing the first failover priority to the second failover priority;

where identifying the first backup user device comprises;

identifying the first backup user device based on comparing the first failover priority to the second failover priority.

18. The method of claim 15, further comprising:

receiving information, from the first backup user device, indicating that the second failover condition, associated with the first backup user device, has been satisfied;

identifying a third backup user device based on detecting that the second failover condition has been satisfied;

determining that a third service request is to be forwarded to the third backup user device; and

forwarding the third service request, associated with the first service, to the third backup user device.