System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation

• US 10,122,607 B2
• Filed: 01/28/2015
• Issued: 11/06/2018
• Est. Priority Date: 12/06/2011
• Status: Active Grant

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Luna, Michael, Bott, Ross
• Primary Examiner(s): Chang, Jungwon
• Application Number:
  US14/608,181
• Publication Number:
  US 20150149626A1
• Time in Patent Office: 1,378 Days
• Field of Search: 709224, 709226, 709203, 709220, 709208, 4554561, 714 13, 4454141
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: H04L 41/0663 Performing the actions predefined by failover planning, e.g. switching to standby network elements
• CPC Class Codes: H04L 41/0863 by rolling back to previous configuration versions
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04W 40/248 Connectivity information update

Abstract

A method for providing fault tolerance in mobile traffic management services is provided. The method includes detecting, at a mobile device, that one component of multiple components for providing mobile traffic management services is non-operational, at capacity, or near capacity, identifying the mobile device serviced by the one component, retrieving information for the mobile device serviced by the one component, from a repository coupled to the one component and the multiple components, re-assigning the mobile device originally serviced by the one component to another one of the multiple components for servicing, and communicating with the another one of the multiple components for servicing communication requests of the mobile device.

Claims

1. A method for providing fault tolerance in mobile traffic management services, the method, comprising:

detecting that a first component of a set of multiple redundantly clustered components for providing mobile traffic management services is non-operational, at capacity, or near capacity;

identifying a mobile device serviced by the first component;

retrieving information for the mobile device serviced by the first component, from a repository coupled to each of the multiple redundantly clustered components (“

common repository node”

);

re-assigning the mobile device originally serviced by the first component to a second component of the set of the multiple redundantly clustered components for servicing;

in response to detecting that the first component is non-operational, at capacity, or near capacity, communicating, via the common repository node, with the second component of the multiple redundantly clustered components to service communication requests of the mobile device such that mobile traffic is optimized using subscription information for the mobile device,

wherein the subscription information includes at least one of user information, user behavior information, device information, and information regarding mobile applications on the mobile device, and

wherein mobile traffic is optimized by performing at least one of batching requests originated from the mobile device, categorizing the mobile traffic based on whether it is foreground or background traffic, prioritizing the mobile traffic based on time criticality, aligning or delaying polling requests from the mobile device, monitoring application behavior on the mobile device, and monitoring user behavior on the device.

2. The method of claim 1, wherein, when it is detected that the first component is non-operational, at capacity, or near capacity, sending invalidations of cache entries on the mobile device to the mobile device originally serviced by the first component from one of the remaining components of the set of multiple redundantly clustered components.

3. The method of claim 2, wherein sending invalidations of cache entries includes sending the invalidations of cache entries in clear text and not encrypted form.

4. The method of claim 1, wherein the mobile traffic is optimized by a local proxy.

5. The method of claim 1, wherein the mobile traffic is optimized by a proxy remote from the mobile device.

6. A mobile device, comprising:

a processor, wherein the processor is configured to;

detect an operability health status of a first component of a set of multiple redundantly clustered components for providing mobile traffic management services;

receive communications in response to a request from the mobile device serviced by a second component of the set of multiple redundantly clustered components when the detected operability status is not within acceptable ranges,

wherein the second component is associated with the first component; and

in response to detecting that the operability status is not within acceptable ranges, optimize mobile traffic using subscription information for the mobile device, wherein the subscription information includes at least one of user information, user behavior information, device information, and information regarding mobile applications on the mobile device,

wherein mobile traffic is optimized by performing at least one of batching requests originated from the mobile device, categorizing the mobile traffic based on whether it is foreground or background traffic, prioritizing the mobile traffic based on time criticality, aligning or delaying polling requests from the mobile device, monitoring application behavior on the mobile device, and monitoring user behavior on the device.

7. The mobile device of claim 6, wherein the second component is associated with the first component based on subscription information of either of the first component or the second component.

8. The mobile device of claim 6, wherein the operability health status includes a determination that the first component is non-operational.

9. The mobile device of claim 6, wherein the operability health status includes a determination that the first component is at capacity.

10. The mobile device of claim 6, wherein the operability health status includes a determination that the first component is near capacity.

11. The mobile device of claim 6, wherein the device is further configured to receive invalidations of cached entries in clear text and not encrypted form.

12. The mobile device of claim 6, wherein the device is configured for optimizing traffic by a local proxy on the device.