Peer-to-Peer Software Update Propagation in Medical Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Medical facility equipment with embedded software faces challenges in timely and cost-effective software updates due to the large number of devices that need to be individually upgraded, leading to issues like malfunctioning equipment, security vulnerabilities, and inefficiencies.

Innovation Solution

A peer-to-peer automatic software update system where one device with updated software connects to others within range using Wi-Fi Direct or similar protocols, transferring the updates to propagate throughout the facility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual equipment is manually updated with new software versions, then software reliability is improved, but time consumption and operational complexity increase significantly

Engineering Contradiction:
Improvesoftware reliabilityVSAvoidtime consumption
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables equipment to automatically update their own software by having them periodically check for updates and self-install when available, eliminating the need for manual intervention on each device while maintaining high reliability through automated update deployment

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The update process is segmented into independent steps: update detection, download, installation, and verification. Each piece of equipment can independently execute these segments at its own pace, allowing parallel updates across multiple devices without requiring centralized coordination for each individual update action

Inventive Principle:
Principle #1Segmentation

2Reliability

If individual equipment is manually updated with new software versions, then software security is improved, but operational complexity increases

Engineering Contradiction:
Improvesoftware securityVSAvoidoperational complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

A universal update management system is implemented that can handle multiple functions: detecting updates across different equipment types, downloading software packages, managing installation processes, and verifying updates. This single system serves all equipment in the facility, reducing operational complexity despite improved security through comprehensive update management

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of operation

If equipment is not updated timely, then operational simplicity is maintained, but vulnerability to security threats increases

Engineering Contradiction:
Improveoperational simplicityVSAvoidsecurity vulnerabilities
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by proactively detecting available updates and preparing installation packages before security threats can exploit vulnerabilities. Equipment automatically checks for updates at scheduled intervals and pre-downloads necessary software, ensuring security patches are applied before threats become problematic while maintaining operational simplicity through automated scheduling

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4155907B1Systems and methods for peer-to-peer automatic software updates
Publication Date: 2025.04.09 HILL ROM SERVICES INC
  • EP4155907B1 patent drawingFigure 1
  • EP4155907B1 patent drawingFigure 2
  • EP4155907B1 patent drawingFigure 3

AI summary

A method to be performed by a processor of a first computing device includes detecting one or more computing devices remote from the first computing device, establishing a peer-to-peer connection with a second computing device from among the one or more computing devices, comparing a first version of a software program installed on the first computing device to a second version of the software program installed on the second computing device, and upon determination that the second version of the software program is more recent than the first version of the software program, receiving second installation software associated with the second version of the software program and executing the second installation software to install the second version of the software program onto the first computing device.