Mobile Content Scheduling via Server Congestion Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Mobile devices face challenges in streaming multimedia content due to limited computing resources, memory, and network bandwidth, leading to inconsistent user experiences, especially when network congestion occurs, as they cannot utilize the same efficient content loading strategies as larger devices.

Innovation Solution

A rules-based just-in-time multimedia content servicing system, implemented through an RBJIT engine, which collects device and network data to optimize content delivery by learning server congestion patterns and scheduling software updates and content downloads during less busy times, ensuring efficient use of resources and improved user experience.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If mobile devices stream multimedia content over network, then user can access multimedia content, but network bandwidth and computing resources are limited causing inconsistent user experience

Engineering Contradiction:
Improveuser experience consistencyVSAvoidnetwork bandwidth
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system performs preliminary actions by monitoring server congestion patterns and scheduling content downloads during off-peak hours before users need the content. The RBJIT engine analyzes historical server load data and proactively downloads multimedia content when network conditions are favorable, ensuring content is ready before user requests, thus improving reliability without requiring constant high bandwidth during usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service by enabling mobile devices to autonomously monitor their own resource usage patterns, network conditions, and content access behavior. The RBJIT engine on each device independently schedules downloads based on local analysis of server congestion patterns and device resource availability, allowing devices to optimize their own content delivery without requiring centralized resource allocation, thereby improving reliability under limited bandwidth conditions.

Inventive Principle:
Principle #25Self-service

2Loss of time

If mobile devices download content during high traffic times, then content is available when needed, but network congestion increases leading to slower download speeds

Engineering Contradiction:
Improvedownload timingVSAvoiddownload speed
Core Design Contradiction:
Loss of timeVSSpeed

Solution Approach 1:

The system performs preliminary actions by downloading content in advance during periods of low network traffic. The RBJIT engine monitors server congestion patterns and schedules downloads during off-peak hours when network bandwidth is more abundant, so content is already available by the time users need it, eliminating both download timing delays and speed issues during high-traffic periods.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements periodic action by scheduling content downloads during specific time windows when server congestion is lowest. The RBJIT engine analyzes historical data to identify optimal download periods and repeatedly applies this scheduling strategy, creating a periodic pattern of downloads during low-congestion intervals and usage during high-congestion intervals, thus resolving both timing and speed contradictions.

Inventive Principle:
Principle #19Periodic action

3Reliability

If mobile devices pre-load multimedia content, then playback is smooth, but device memory and computing resources are consumed

Engineering Contradiction:
Improveplayback smoothnessVSAvoiddevice memory
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system applies local quality by downloading and caching only the specific portions of multimedia content that each user is most likely to access, based on their individual usage patterns and preferences. The RBJIT engine analyzes user behavior data to identify which segments or files each device should prioritize, allocating device memory selectively rather than uniformly, thus maintaining playback smoothness for each user while optimizing overall memory utilization across the system.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements partial action by downloading only the necessary portions of content rather than complete files. The RBJIT engine determines the minimum required content based on user behavior analysis and downloads only those specific segments needed for smooth playback, avoiding unnecessary memory consumption while ensuring adequate content availability for each user's specific needs.

Inventive Principle:
Principle #16Partial or excessive action

4Quantity of substance

If mobile devices use data-on-demand strategies, then memory usage is reduced, but loading times increase during playback

Engineering Contradiction:
Improvememory usageVSAvoidloading time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-downloading content during off-peak hours when network bandwidth is abundant and device memory is less constrained. The RBJIT engine schedules downloads in advance based on predicted user needs, so content is already cached and ready when users request it, eliminating loading delays during playback while maintaining efficient memory usage through selective pre-loading based on usage patterns.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11395314B2Optimal scheduling of access events on mobile devices
Publication Date: 2022.07.19 T MOBILE US INC
  • US11395314B2 patent drawing
  • US11395314B2 patent drawing
  • US11395314B2 patent drawing

AI summary

Described herein are techniques for optimizing scheduling of access events (e.g., downloads) on mobile devices based on server congestion. In some embodiments, response times are monitored for a number of servers at various times to establish availability patterns for those servers. An indication of a number of software applications installed upon a mobile device is used to identify a number of access events to be associated with that mobile device. The servers associated with those access events are identified and an access schedule is generated based on the availability patterns. The access schedule is then provided to the mobile device, which initiates execution of the access events according to the access schedule.