Network Event Triggered Software Updates for Client Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Multiple system operators face inefficiencies in updating software on a large number of client devices, as conventional polling methods consume significant network resources and processing time, leading to outdated software being updated too slowly, potentially becoming outdated before completion.

Innovation Solution

A system that identifies network events, such as configuration parameter requests, to trigger software updates, reducing the need for extensive polling by comparing software versions and communicating updates only when necessary, using a configuration server and update server to manage software updates efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the MSO server polls each client device to check for software updates, then the software can be updated, but extensive network resources and processing time are consumed

Engineering Contradiction:
Improvesoftware up-to-datenessVSAvoidnetwork resources
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

Instead of the server actively polling each client device to check for updates, the system inverts the approach by having client devices autonomously report their software version information to the server. This reversal of the information flow eliminates the need for extensive polling while maintaining accurate tracking of software up-to-dateness across the network.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

Client devices are equipped with the capability to self-report their software version status to the MSO server. This self-service mechanism allows devices to proactively provide update information without requiring external polling, thereby reducing server processing time and network resource consumption while ensuring reliable software version tracking.

Inventive Principle:
Principle #25Self-service

2Reliability

If the MSO server polls each client device to check for software updates, then the software can be updated, but significant processing time is consumed

Engineering Contradiction:
Improvesoftware up-to-datenessVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system inverts the traditional polling mechanism by having client devices autonomously report their software version information to the server. This reversal eliminates the time-consuming polling process while maintaining accurate and timely tracking of software updates across all client devices.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

Client devices perform preliminary action by proactively reporting their software version status to the server before being prompted. This advance reporting mechanism allows the server to maintain an up-to-date inventory of software versions across the network without investing significant processing time in active polling operations.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If extensive polling is performed to update software on all client devices, then software updates can be distributed, but the updated software may already be out of date by the time all devices are updated

Engineering Contradiction:
Improvesoftware consistencyVSAvoidupdate completion time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Client devices perform preliminary action by autonomously reporting their software version status to the server in advance. This allows the server to immediately identify which devices need updates and distribute them without delay, ensuring that all devices receive current software versions before they become outdated.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback mechanism where client devices continuously report their software version information to the server. This real-time feedback loop enables the server to maintain accurate knowledge of software status across the network and promptly distribute updates, ensuring software consistency without time delays.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10656931B2Network event triggered software updates
Publication Date: 2020.05.19 COMCAST CABLE COMM LLC
  • US10656931B2 patent drawing
  • US10656931B2 patent drawing
  • US10656931B2 patent drawing

AI summary

Systems and methods may provide for identifying a network event trigger generated in response to a network event being identified due to receipt of a message, from a client device, comprising a request for or to extend a configuration parameter. The systems and methods may further provide for identifying a software update for software of the client device in response to the network event trigger, and communicating a software update message comprising the software update to cause updating of the software of the client device.