Mobile Pull Client Grouping for Network Resource Conservation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices experience significant resource overhead due to the frequent establishment and re-establishment of traffic channels for periodic data updates with servers, leading to increased network and communication resource usage.

Innovation Solution

Implementing a pull client on mobile devices that groups applications with similar timing requirements for data updates, allowing them to share a single traffic channel and reduce the need for consecutive network-resource-intensive sessions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If mobile devices establish separate traffic channels for each application's periodic updates, then each application receives timely data updates, but network resource overhead and signaling complexity increase significantly

Engineering Contradiction:
Improvedata update timelinessVSAvoidnetwork signaling overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple separate traffic channels into a single shared channel. Multiple applications with different update timing requirements are merged into one consolidated data communication session, allowing all applications to access data through a single channel rather than requiring individual dedicated channels for each application.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements preliminary grouping of applications before data retrieval. Applications are pre-grouped based on their timing requirements and data needs, allowing the system to prepare and coordinate data requests in advance, thereby reducing the need for frequent channel establishment and re-establishment.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If traffic channels are established for each application update, then data is reliably delivered to each application, but authentication and validation processes consume excessive network resources

Engineering Contradiction:
Improvedata delivery reliabilityVSAvoidnetwork resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple authentication and validation processes into a single centralized authentication event. Instead of authenticating each application separately when it needs data, the system performs one authentication event that serves all applications in the grouped session, significantly reducing the cumulative resource consumption of repeated authentication cycles.

Inventive Principle:
Principle #5Merging (Combining)

3Productivity

If separate traffic channels are used for each application, then application-specific data can be delivered efficiently, but the number of sessions increases leading to higher overhead

Engineering Contradiction:
Improvedata update efficiencyVSAvoidnumber of sessions
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The patent consolidates multiple data sessions into a single unified session. Instead of maintaining separate sessions for each application's data requests, the system merges all application data communications into one shared session, thereby reducing the total quantity of sessions from multiple to one while maintaining efficient data delivery to all applications.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8943204B2Method and system for conserving network resources when sending information to mobile devices
Publication Date: 2015.01.27 CELLCO PARTNERSHIP INC
  • US8943204B2 patent drawing
  • US8943204B2 patent drawing
  • US8943204B2 patent drawing

AI summary

Information is provided to a mobile device while reducing the number of traffic channels established over a predetermined time period. A pull client on a mobile device receives requests for information from applications on the mobile device. The pull client creates a timing list which includes the timing requirements for each application. Applications that have overlapping timing requirements are grouped together into the same timing group. Once the time for creating a traffic channel for one of the groups arrives, a traffic channel is created between the mobile device and a carrier gateway. Information for each respective application within the same timing group is obtained through the network using the same traffic channel. When the requested information is provided to all applications within the same timing group, the traffic channel is released after a predetermined time. The method is repeated for a next timing group entry.