Browse Prior Art Database

System and Method to Recommend Software Update Disclosure Number: IPCOM000228806D
Publication Date: 2013-Jul-08
Document File: 2 page(s) / 39K

Publishing Venue

The Prior Art Database


This article describes a system and method to recommend software update by leveraging software used by the user's social network contacts and the interactions the user has with other users.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 45% of the total text.

Page 01 of 2

System and Method to Recommend Software Update

Users live in a computer, internet centralized world, almost every family have at least one computer these days. On each computer, it has not only operation systems but also various software that satisfies the user's needs and wants on the computer, examples of software, traditional email, web based emails, documents, etc. Some software requires purchase, while some software are open source and completely free. The characteristics of open source software are they could be very good and popular, or they could be poor and lack decent quality or even malware which causes troubles on a user's computer. While these open source software are free to download, and free support from the open source community, they may charge a monthly or yearly fee for premium support.

It is often to a user or company's best interest to replace commercial software with open source software without impacting user's productivity. Moreover, it is even helpful to determine which level of the particular software to be using to ensure best performance and better computability with other software on the local system and files that are shared by other people in the social connections.

Scenario 1: Within a big corporation like IBM*, system uses social network contacts software usage and software level to provide recommendation and refined recommendation based on the activities on the computer and similar activities or document creators from the peers. Details on how this can be implemented:

- Corporate workstation look, for example IBM Work Station Tool (WST) records each user's computer operation system level, operation system fixpack level, each installed software and its level

- WST also records each computer's history every time when WST scans the computer on a fixed interval, for example, every month.

- System can leverage each computer's history in WST to determine software usage trends for each user, examples: User John has updated to JDK 1.6 update 31 in July and updated to JDK 1.6 update 32 in April. John also

has switched to mark Open Office** as his primary office software, replacing the prior Microsoft*** office in March.

User Ally has been using OpenOffice and she has updated her open office from 3.4 to 3.4 fixpack 1 in Jan and

to 3.4 fixpack 2 in April.

Examples of WST recorded data that can be used for our system:

Users Software updates April,

Software updates March, 2013

Software updates Feb, 2013

Software updates Jan, 2013

John JDK 1.6 update 31 -> 32 Microsoft office is removed
(key expiring too)

Microsoft office seldom used

Start to use Open office

Ally open office 3.4.1 update to

3.4.2 n/a


open office 3.4 update to 3.4.1

Mary n/a



Lotus Notes 8.5 update to 8.5.1

Peter open office 3.4 update to

3.4.1 n/a

Lotus Notes* 8.5 update to 8.5.1 n/a

Joyce n/a


Lotus Notes 8.5 update to 8.5.1 n/a

Nate open office 3.4.1 update to

3.4.2 n/a

open office 3.4 update to

3.4.1 n/a

- Social network...