SOFTWARE DISTRIBUTION TO MEDICAL DEVICES VIA AN INTERMEDIARY WHICH ENFORCES MAINTENANCE OF A TRANSACTION LOG

• US 20130036415A1
• Filed: 08/02/2011
• Published: 02/07/2013
• Est. Priority Date: 08/02/2011
• Status: Abandoned Application

• Current Assignee: Roche Diabetes Care Inc. (Roche Holding AG)
• Original Assignee: Roche Diagnostics Operations Incorporated (Roche Holding AG)
• Inventors: Birtwhistle, Daniel P.
• Application Number:
  US13/195,893
• Publication Number:
  US 20130036415A1
• Time in Patent Office: Days
• US Class Current: 717/173
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A software configuration device is provided for distributing product updates offline to a plurality of end user medical devices. The configuration device includes: a download manager, in selective data communication with an update interface residing at a server, that downloads product updates from the update interface and stores the product updates on a data store residing on the device; and an update distributor configured to capture identifying information for a user and operable by the user to distribute product updates to one or more end user medical devices. The update distributor further maintains distribution data for each of the distributed product updates, including identifying information for the user, in a transaction log residing on the configuration device. The download manager can subsequently upload the transaction log to the server while in data communication with the server.

Claims

1. A software configuration device for distributing product updates to a plurality of end user devices, comprising:

a transaction log operable to store distribution data for product updates;

a download manager in selective data communication with an update interface residing at a server, the download manager operable to download product updates from the update interface and store the product updates on a data store residing on the device; and

an update distributor configured to capture identifying information for a user and operable by the user to distribute product updates to one or more end user devices, the update distributor maintains distribution data, including identifying information for the user, in the transaction log for each of the distributed product updates, the download manager subsequently uploads the transaction log to the server while in data communication with the server, where the user of the update distributor differs from a user associated with at least one of the end user devices receiving a product update from the update distributor.

2. The software configuration device of claim 1 wherein the update distributor is operable to distribute product updates when offline from the update interface.

3. The software configuration device of claim 1 wherein the download manager, during registration of itself with the update interface, provides identifying information for an owner of the configuration device, including an address for the owner, and identifying information for the configuration device.

4. The software configuration device of claim 3 wherein the owner of the configuration device is different from an owner of at least one of the end user devices receiving a product update from the update distributor.

5. The software configuration device of claim 1 wherein the update distributor is operable by a plurality of different users to distribute product updates and logs a transaction for each product update in the transaction log, including identifying information for the respective user who distributed a given product update.

6. The software configuration device of claim 1 wherein the update distributor, upon distributing a product update to a given end user device, captures identifying information for a given end user device and logs a transaction for the product update in the transaction log, including the identifying information for the given end user device.

7. The software configuration device of claim 1 wherein the update distributor, upon distributing a product update to a given end user device, captures identifying information for an owner of the given end user device and logs a transaction for the product update in the transaction log, including the identifying information for the given end user device.

8. The software configuration device of claim 1 wherein the download manager queries the update interface for latest version of a given product update and receives the latest version of the given product update in response to the query.

9. The software configuration device of claim 8 wherein the download manager requests an upgrade for the given product update and receives a download of the given product update in response to the upgrade request.

10. The software configuration device of claim 1 further comprises

a dependency file operable to store one or more dependencies for a given product update that must be met before the product update can be downloaded;

and

an update distributor configured to receive a request to download the given product update from a requesting end user device and, in response to the download request, retrieve the one or more dependencies for the given product update from the dependency file, where at least one of the dependencies for the given product update specifies a version of software that resides on a device which is interoperable with the requesting end user device;

the update distributor further configured to receive a listing of peer devices that are interoperable with the requesting end user device and, in response to the download request, compares the at least one dependency with software residing on each peer device in the listing of peer devices and distributes the given product update to the requesting end user device when the at least one dependency is met.

11. The configuration device of claim 10 wherein the download manager further retrieves the dependency file from the server.

12. The configuration device of claim 10 wherein the update distributor is configured to receive the listing of peer devices from the requesting end user device, the listing includes an enumeration of software residing on each peer device in the listing.

13. The configuration device of claim 10 wherein the update distributor operates to distribute the given product update to the requesting end user device when the software residing on the each peer device has a version as recent as the version of software specified by the at least one dependency.

14. The configuration device of claim 10 wherein the update distributor is configured to receive an identifier for the geographic region associated with the requesting end user device from the requesting end user device, the update distributor operable to compare the identifier to another dependency and distribute the given product update to the requesting end user device when the another dependency is met, such that the another dependency specifies an intended geographic area of use for the product update.

15. The configuration device of claim 10 wherein the update distributor is operable to determine one or more dependencies that specify a version of software that resides on the requesting end user device and distribute the given product update to the requesting end user device when each of the one or more dependencies are met.

16. The configuration device of claim 10 wherein the update distributor is operable to determine a first dependency that specifies a version of a first software entity and a second dependency that specifies a version of a second software entity, and distribute the given product update to the requesting end user device when the first and second dependencies are met, where the first and second software entities reside on different peer devices.

17. A method for distributing product updates from a software configuration device to a plurality of medical devices, comprising:

downloading a product update from a server over a computer network to the software configuration device;

capturing identifying information for a user of the software configuration device;

distributing the product update by the user of the software configuration device to a requesting medical device when the software configuration device is offline from the server; and

maintaining distribution data for the product update, including identifying information for the user, in a transaction log residing on the software configuration device.

18. The method of claim 17 further comprises subsequently uploading the transaction log from the configuration device to the server.

19. The method of claim 17 further comprises capturing identifying information for an owner of the configuration device, including an address for the owner, during registration of the configuration device with the server.

20. The method of claim 17 further comprises capturing identifying information for a given medical and logging a transaction for the product update in the transaction log, including the identifying information for the given medical device upon distributing the product update to the given medical device.

21. The method of claim 17 further comprises capturing identifying information for an owner of a given medical device and logging a transaction for the product update in the transaction log, including the identifying information for the given medical device upon distributing the product update to the given medical device.