Browse Prior Art Database

Process by Which Usage and Networking Characteristics Determine Dating of Pervasive Devices Updating of PvC Devices with Software Loads

IP.com Disclosure Number: IPCOM000123502D
Original Publication Date: 1998-Dec-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 2 page(s) / 76K

Publishing Venue

IBM

Related People

Fletcher, JC: AUTHOR [+3]

Abstract

Pervasive computing devices are occasionally disconnected from their network. These devices occasionally require software updates (executables) or data updates (deemed essential by an enterprise). The problem is, how to determine when to provide such updates (or information about the existance of these updates) to such a device.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Process by Which Usage and Networking Characteristics Determine Dating
of Pervasive Devices Updating of PvC Devices with Software Loads

   Pervasive computing devices are occasionally disconnected
from their network.  These devices occasionally require software
updates (executables) or data updates (deemed essential by an
enterprise).  The problem is, how to determine when to provide such
updates (or information about the existance of these updates) to such
a device.

   This process uses information about the connection type,
and optionally the device itself, in conjunction with network events
(such as the availability of new SW for this device) to determine if
a "pushed" download should occur.

   The advantage is shorter exposure to the device running
with out-of-date software; optimal use of its connection to the
network.

   When a device is used in such a way as to drive a
connection to the network, the controlling middleware (software at a
server) detects the device that is connected.  It checks a directory
of available software, and optionally compares it against a directory
of what is installed on the device (or queries the device dynamically
for this information).  If it determines that there is software to
download, it determines if that download should occur on this
instance of a connection, based on connection type (synch cord,
wireless low-bandwidth, dial-in moderate bandwidth, LAN) and usage
(e.g., time of day -- not doing a download if this is the busiest
time of day on the business usage period for this device -- unless
the update is marked as so essential as to violate this base
assumption).  This process is illustrated in Figure 1.

   Example 1 - Updating a SmartCard.

   SmartCard connection to the network via a reader, to query
information or...