Push-Pull Content Delivery with Automatic Retry

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content delivery systems for wireless communication devices often fail to reliably complete the delivery of content from a content server to a client device, particularly due to network coverage issues, storage limitations, and connectivity failures.

Innovation Solution

The system employs a content delivery mechanism that includes a content server, a mobile content player on the client device, and a mobile connector, which uses push and pull delivery methods, along with caching servers, to ensure content is delivered and stored reliably, with automatic retry and user notification for failed deliveries.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If push delivery method is used to automatically send content from server to client, then content delivery automation is improved, but delivery reliability deteriorates due to network coverage issues and connectivity failures

Engineering Contradiction:
Improvecontent delivery automationVSAvoiddelivery reliability
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The system implements a feedback mechanism where the client device sends delivery status information back to the content server. The server maintains a record of delivered content and compares it with the content that should have been delivered, automatically identifying and retrying failed deliveries based on this feedback loop.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The content server proactively pushes content to the client device before the client needs it, rather than waiting for a request. The server attempts delivery in advance and uses the feedback mechanism to ensure completion, performing the delivery action beforehand and correcting any failures that occur.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If automatic retry mechanism is implemented for failed deliveries, then delivery reliability is improved, but system complexity increases

Engineering Contradiction:
Improvedelivery reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The content server autonomously manages the retry process without requiring manual intervention. The server automatically identifies failed deliveries, retries them, and notifies users only when necessary. The system serves itself by maintaining delivery records and comparing expected versus actual delivery status, eliminating the need for complex manual monitoring and retry management.

Inventive Principle:
Principle #25Self-service

3Reliability

If content delivery status monitoring is implemented, then content loss is reduced, but information processing requirements increase

Engineering Contradiction:
Improvecontent delivery assuranceVSAvoidcontent loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system monitors delivery status by implementing a feedback loop where the client reports received content back to the server. The server compares this feedback against its records of what should have been delivered, automatically identifying any content that was lost or failed to deliver, and triggering retry operations for missing items.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2507963B1Reliable delivery of content to a push-state aware client device
Publication Date: 2017.01.25 BLACKBERRY LTD
  • EP2507963B1 patent drawingFigure 1
  • EP2507963B1 patent drawingFigure 2
  • EP2507963B1 patent drawingFigure 3

AI summary

There are provided methods, systems, devices and computer program products for reliable delivery of content packages to a client device. Push delivery of content packages is combined with pull delivery when a push delivery fails. When a client device participates in a push delivery but fails to complete, a recommendation for corrective action may be notified and, following such corrective action, the client device pulls delivery. Respective content listings are maintained by server and client device for reconciliation to prompt pull delivery by the client device.