CA2542786A1 - System and method for providing computer upgrade information - Google Patents
System and method for providing computer upgrade information Download PDFInfo
- Publication number
- CA2542786A1 CA2542786A1 CA002542786A CA2542786A CA2542786A1 CA 2542786 A1 CA2542786 A1 CA 2542786A1 CA 002542786 A CA002542786 A CA 002542786A CA 2542786 A CA2542786 A CA 2542786A CA 2542786 A1 CA2542786 A1 CA 2542786A1
- Authority
- CA
- Canada
- Prior art keywords
- client computer
- hardware configuration
- computer
- task
- motherboard
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/64—Retargetable
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
Systems and methods to provide upgrade information for a computer. Detection of a current hardware configuration of the computer is facilitated by: 1) reading serial presence detect (SPD) data from the computer; 2) reading motherboard parameters from the computer; and/or 3) identifying the SPD write-protect status of the SPD chip on the computer. Detection may be facilitated by: 4) reading other OS data such as system name and/or operating system version, and/or 5) performing tests to determine certain computer characteristics such as memory utilization and/or CPU speed. The information gathered may be cross-referenced with a database of product specifications to confirm the current hardware configuration of the computer within specified parameters, which is then compared to a target hardware configuration to identify an upgrade package for upgrading the computer to the target hardware configuration. A recommendation is provided to use the upgrade package for upgrading the computer.
Description
SYSTEM AND METHOD FOR PROVIDING COMPUTER UPGRADE
INFORMATION
TECHNICAL FIELD
The present invention relates generally to computer systems and computer networks. More particularly, the present invention relates to a system and method for providing computer upgrade information based upon component-related data present on a client computer.
INCORPORATION BY REFERENCE
The contents of each U.S, patent or other reference, if any, cited in this application, are hereby incorporated herein by reference.
BACKGROUND ART
The computer has become a permanent fixture in society. Computers are used to facilitate data communications and electronic commerce between businesses, and to gather various types of data such as news, stock market quotes, research facts, sport scores, etc.
Furthermore, computers serve as a source of entertainment through audio and/or visual output display. Just about every aspect of daily life is affected by computers.
The high technology environment of computers is constantly changing.
Typically, staying current with evolving computer technology requires the user to choose between the economics of a computer system replacement or a computer system upgrade. In a computer system upgrade, users attempt to choose upgrade hardware most appropriate for their particular needs and operating environment. For example, common upgrade hardware considerations include faster processor speed, enhanced video capabilities, increased memory, network capabilities, particular I/O devices, etc. For a vendor to provide a meaningful computer upgrade recommendation, the vendor must typically gather information from the user regarding the hardware and software configuration of the user's client computer.
Such data gathering methods include phone or mail surveys, and registration packets filled out by the user after purchase of the computer components or system.
Another data gathering method involves electronic transfer of data from the user to the vendor. For example, the user enters information about the user's computer via on-screen menus, and the information is transmitted to a server computer generally via the Internet, regarding the model of the users computer. The user is then presented with information about their system including upgrade products and paths. Although this method offers upgrade options and is viewed by many as an improvement over prior methods, its success is dependent on the user's knowledge of the client computer's current configuration.
Another method described in U.S. Patent No. 6,370,578, issued April 9, 2002 and titled "Active Marketing Based On Client Computer Configurations", uses a product information database which contains product signatures. The client's system is scanned (e.g., by server software) for the presence of the product signatures corresponding to each product in the product information database to determine if each product is present on the client computer. This method relies less on the user's actual knowledge of his or her client computer than does the previously-described methods, but nonetheless this method is very inefficient because most of the products scanned for are typically not present on the client's computer. Further, the data gathered from such scanning is not always accurate and/or complete enough to allow the vendor to make an optimal upgrade recommendation.
This is due to inherent limitations in the manner in which industry-standard SMBIOS
(System Management Basic Input/output System) and SPD (Serial Presence Detect) data is created, reported, accessed, and/or used in combination with other data to determine the true system state of a client computer.
Since optimizing the accuracy of an upgrade recommendation results in enhanced product reliability and component compatibility, an accurate upgrade recommendation should be based on the most reliable data in determining the current system configuration.
Accordingly, there is a need for a system and method of providing upgrade information for a computer that is more accurate, efficient, and reliable than known methods.
DISCLOSURE OF INVENTION
Systems and methods are disclosed which provide upgrade information for a client computer. The detection of a current hardware configuration of the client computer is facilitated by: 1) reading serial presence detect (SPD) data from the client computer; 2) reading motherboard parameters (such as the product ID and manufacturer ID of the motherboard); and/or 3) identifying the SPD write-protect status of the SPD
chip on the client computer. Additionally or alternatively, detection of the current hardware configuration may be facilitated by: 4) reading other OS data such as system name and operating system version and/or performing tests to determine certain computer characteristics such as memory utilization or CPU speed. In most instances, the information gathered is cross-referenced with a proprietary database of product specifications, to confirm the information is accurate.
The current hardware configuration of the client computer is then compared to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration, and a recommendation is provided to use the upgrade package for upgrading the client computer. Identification of the upgrade package is based at least partially upon the information gathered.
The method of the present invention may be carned out by a system of the present invention embodied in computer software. Conceptually, the software includes various modules to accomplish discrete tasks. The modules may be wholly or partially combined, or split into more discrete sub-modules as desired. In general, the system includes: a detect module for detecting a current hardware configuration of the client computer;
a compare module for comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration; and a recommend module for providing a recommendation to use the upgrade package for upgrading the client computer. An optional cross-reference module is used for cross-referencing information about the current configuration of the client computer, gathered by the detect module, with a product information database.
The detect module detects the hardware configuration of the client computer by performing at least one task from the group of tasks consisting of (a, b, c), or at least one task from the group of tasks consisting of (a, b, c, d, e), to gather information associated with the client computer. Task "a" refers to accessing SPD data from an SPD
chip of the client computer. Task "b" refers to accessing motherboard parameters from the memory of the client computer, such as a manufacturer ID and a product ID of the motherboard. Task "c" refers to determining a write-protect status of the serial presence detect chip of the client computer. Task "d" refers to reading OS data such as system name and/or operating system version. Task "e" refers to performing a test or tests to determine certain computer characteristics such as memory utilization and/or CPU speed. The compare module identifies the upgrade package based at least partially upon the information gathered by the detect module.
The method of detecting the current hardware configuration of a client computer, as describe herein, detects the presence or absence of a limited number of target hardware components, as opposed to scanning for each of hundreds or thousands of components within a proprietary product information database. The method of the present invention thus eliminates the time-consuming use of scanning for each item in a product information database. Furthermore, by cross-referencing the information gathered with product specifications in a proprietary product database, the current hardware configuration of the client computer may be determined more accurately than with known methods.
Upgrade recommendations may then be made for compatible components with a higher degree of success than with known methods.
The present invention as described herein thus provides a system and method of recommending an upgrade package for a computer that is more accurate, efficient, and reliable than known systems or methods. Further objects and advantages of the present invention will be apparent in the detailed description which follows, read in conjunction with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates a typical computer and motherboard configuration.
FIG. 2 illustrates a typical network system for facilitating execution of a method of the present invention, along with block diagrams of an upgrade program used in accordance with the present invention, and relevant features of a typical memory module.
FIG. 3 is a flow chart illustrating a method of providing upgrade information for upgrading a computer according to the present invention.
MODES FOR CARRYING OUT THE INVENTION
The present invention describes a system and method of providing a computer upgrade recommendation that is more accurate, efficient, and reliable than known systems and methods. The current hardware configuration of a client computer is detected by reading serial presence detect (SPD) data, reading motherboard parameters (such as the product ID and manufacturer ID of the motherboard), and/or identifying the SPD
write protect status of the SPD chip of the computer. Additionally or alternatively, detection of the current hardware configuration may be facilitated by reading other OS
data, and/or performing tests to determine certain computer characteristics. In most instances, the information gathered is cross-referenced with a proprietary database of product specifications, to confirm the information is accurate.
The current hardware configuration of the client computer is then compared to a target hardware configuration which has been established, to identify an upgrade package for upgrading the client computer to the target hardware configuration.
Typically, the target hardware configuration is based on industry standards or user preferences. A
recommendation is provided to use the upgrade package for upgrading the client computer to the target configuration.
If the user's needs change after the target hardware configuration has been determined, or even after the upgrade package has been determined, the target hardware configuration may be reestablished accordingly, and the current hardware configuration may then be compared to the reestablished target hardware configuration to identify a reestablished upgrade package for upgrading the client computer to the reestablished target hardware configuration, based at least partially upon the information previously gathered regarding the current hardware configuration. The reestablished upgrade package may then be recommended for upgrading the client computer. Thus, as described more fully herein, the present invention provides for systems and methods that recommend upgrade packages for a computer.
Turning now to Figure 1, a typical client computer 5 and motherboard configuration is shown for reference, and is well-known in the art.
Motherboard 10 is sometimes referred to as the rnainboaxd, system board, logicboard, or even maincard or mothercard. Typically, all of the basic circuitry and components required for a computer to function are either contained on or attached to motherboard 10, such as microprocessor or CPU 15, controller or chipset 20, memory modules 25, serial and parallel ports (not shown), expansion slots 30, power supply 35, internal cache 40, external cache 45, and various cards 50 such as a modem card, video card, and sound card. Memory module 25 includes memory chips 55, an SPD chip 60 (typically an EPROM), and an SMBIOS
area 65 of RAM for storing SMBIOS data (see Figure 2). External hardware components (not show) are also well-known in the art, and may include for example, a monitor, keyboard, mouse, printer, scanner, or any temporarily connected device such as a camera, personal digital assistant (PDA), or data storage device.
When computer 5 is first powered up, CPU 15 passes control to the basic input/out system (BIOS) program located in ROM. Boot-up and BIOS processing are well-known in the art. Briefly, BIOS determines whether the computer's components are operational, and then loads OS files from the computer's hard drive or disk drive into the computer's RAM.
BIOS takes an inventory of equipment and resources, and loads SMBIOS data such as configuration information and drivers into SMBIOS area 65. For example, the SMBIOS
data contains data from chipset 20 regarding the memory module capacity of chipset 20.
Additional SMBIOS data includes motherboard parameters 75 such as the manufacturer ID
and product ID of motherboard 10. As described herein, the present invention uses some of the data from SMBIOS to determine the current hardware configuration of the client computer 5, and make a proper hardware upgrade recommendation.
Turning now to Figure 2, a typical computer network system 80 for facilitating execution of a method of the present invention is shown. Also shown in Figure 2 is a block diagram of upgrade program 85, as well as a block diagram of a memory module 25. In computer network system 80, a plurality of server computers 90 are connected via a communication network 95, such as the Internet, to a client computer 5. One or more servers 90 hosts upgrade program 85, comprised of detect, compare, and recommend modules, 100, 105, and 110, respectively. Upgrade program 85 optionally further comprises cross-reference module 115. Upgrade program 85 is typically embodied in executable computer software, which may run from client computer 5 or server 90, and which may be partially or fully downloaded from server 90 via network 95 to client computer 5.
Detect module 100 is programmed to detect a current hardware configuration of client computer 5, by performing at least one task from the group of tasks consisting of (a, b, c), or at least one task from the group of tasks consisting of (a, b, c, d, e), to gather information associated with client computer 5. Task "a" refers to accessing SPD data 120 from SPD chip 60 of client computer 5. Task "b" refers to accessing motherboard parameters 75 from the memory of client computer 5, for example a manufacturer ID and a product ID of motherboard 10. Task "c" refers to determining a write-protect status (represented by 70) of SPD chip 60 of client computer 5. Task "d" refers to accessing OS
data such as system name andlor operating system version. Task "e" refers to performing a test or tests to determine certain computer characteristics such as memory utilization and/or CPU speed.
Compare module 105 is programmed to compare the current hardware configuration of client computer 5 to a target hardware configuration (previously established), to identify an upgrade package for upgrading client computer 5 to the target hardware configuration. Identification of the upgrade package is based at least partially upon the information gathered by detect module 100. Recommend module 110 is programmed to provide a recommendation to use the upgrade package for upgrading client computer 5. Optional cross-reference module 115 is programmed to cross-reference the information gathered by detect module 100, with product specifications in a product information database 90a. Each of the detect, compare, recommend, and cross-reference modules 100, 105, 110, and 115 are described herein in more detail in connection with Figure 3.
Still referring to Figure 2, a block diagram of a typical memory module 25 is shown, illustrating relevant features. Memory module 25 contains multiple memory chips 55 (e.g., SDRAM andlor RAMBUS), an SPD chip 60 which is typically an EPROM, and an SMBIOS area 65 of RAM for storing SMBIOS data such as motherboard parameters 75 obtained directly from motherboard 10 during boot-up, as well as chipset data 125 obtained from chipset 20 during boot-up. SPD chip 60 contains SPD data 120, and may be write-protected (indicated by write-protect status 70). Use of the aforementioned components and data of memory module 25 will be discussed more fully herein.
Turning now to Figure 3, a flowchart is shown illustrating methods of providing upgrade information for upgrading a computer according to the present invention. The process begins at step 300. At step 310, a current hardware configuration of the client computer is detected. The detection may include one or more of tasks 310a, 310b, 310c, 310d, and 3 10e discussed more fully herein. At step 320, a target hardware configuration for the client computer is established. The current configuration is then compared to the target configuration at step 330, and a recommendation for an upgrade is provided based upon the results of the comparison, as seen at step 340. The process ends at step 350. Each step will now be discussed in more detail.
Referring now to step 310 in more detail, the current hardware configuration of the client computer is detected. Step 310 may include any combination of one or more of steps 310a, 310b, 310c, 310d, and 310e. In one embodiment of the present invention, step 310 includes at least one of the tasks from the group of tasks consisting of "a", "b", and "c", represented by steps 310a, 310b, and 310c respectively. That is, step 310 may include only step "a", only step "b", only step "c", only steps "a" and "b", only steps "a"
and "c", only steps "b" and "c", or all three steps "a", "b", and "c".
In those instances which include step "a", preferably SPD data 120 is cross referenced with product specifications in database 90a. Similarly, in those instances which include step "b", preferably motherboard parameters 75 are cross-referenced with product specifications in database 90a. Such cross-referencing may be performed by cross-reference module 115, and the benefits thereof are discussed more fully herein.
Detection of the current hardware configuration of the client computer at step may be initiated in various ways. For example, an individual user may request detection through an active link on a website. In that case, upgrade program 85 may run wholly or partially from a server computer over the Internet, or may be downloaded to the client computer at that time to run locally. Or upgrade program 85 may be resident on the client computer or accessible over a local or other computer network. These and other variations are well-known in the art. In any case, the detecting may be performed automatically in response to a single user request. Similarly, the entire process of detecting (310), comparing (330), and recommending (340) may be performed automatically in response to the single user request, which may be received at a computer server over a computer netwoxk. Detect, compare, and recommend modules (100, 145, and i 10 respectively) may be embodied in an executable computer program 85 as seen in Figure 2. The entire process may also be programmed to initiate automatically at specified time intervals.
The present invention is useful not only for providing an upgrade recommendation for a single client computer 5, but also for providing project-based or network-based upgrade recommendations. In this manner, the process may be performed on an entire network automatically or by a single manual request at substantially the same time. If a single user request is initiated to run upgrade program 85 on a network /
project, the process preferably includes steps 300-350 for each client computer. That is, if client computer 5 is part of a network comprising additional client computers, the process may:
detect the current hardware configurations of each of the additional client computers;
establish corresponding target hardware configurations for each of the additional client computers; compare the current hardware configurations of each of the additional client computers to the corresponding target hardware configurations of each of the additional client computers to identify corresponding upgrade packages for upgrading each of the additional client computers to the corresponding target hardware configurations; and recommend use of the corresponding upgrade packages for upgrading each of the additional client computers.
If a particular client computer in the project has not had its current hardware configuration detected (310), and/or not had its target hardware configuration established (320), those'steps may be executed on that particular client computer. On the other hand, if the current hardware configuration has been detected (310), and/or the target hardware configuration has been established (320), those steps may be skipped for that particular client computer. This may be accomplished using basic programming logic. The process may proceed on a project basis by performing steps 300-350 consecutively for each client computer, or by performing 310 on each computer, then 320 on each computer, then 330 on each computer, then 340 on each computer. It is simply a matter of preference as to what order the steps of the process are performed when a project-based upgrade recommendation is being executed.
For example, when the present invention is used with project-based upgrade recommendations, the detection step (310) may be executed at various times either individually by particular client computer users, or by a network administrator for multiple client computers on the network. The current hardware configurations of the detected client computers may be stored in a database for future reference. If an individual manually reconfigures his or her client computer (e.g., adding memory), then that user can request re-detection of that client computer, and the updated current hardware configuration may be stored at the database until such time as it is needed for completion of the process.
Similarly, the target hardware configurations of each client computer in a project-based upgrade may be reestablished (320), as needed. The compare step (330) may also be accomplished individually, or on a project-based scale. While each client computer within a project may have its current hardware configuration detected (310) and its corresponding target hardware configuration established (320) individually, in one embodiment of the present invention all client computers in the project will have had their current and target hardware configurations loaded into a project-based database prior to the compare step (330) being performed. In this manner, upgrade program 85 may operate on the entire project based on a single request, with the comparing (330) and recommending (340) steps being performed on each client computer within the project, substantially simultaneously.
Still referring to step 310, the present invention "detects" the presence or absence of specific hardware components on a client computer, as opposed to "scanning"
for the presence or absence of those components. Scanning refers to checking each product signature in a product information database against the client computer, to determine the presence or absence of the product. Scanning is described in U.S. Patent No.
6,370,578, previously discussed in the Background Section of the pxesent application.
Scanning is extremely inefficient because the server or upgrade program scans for many items that are not present on the client's computer. The present invention, on the other hand, detects the presence or absence of only a limited number of hardware components of concern, mostly related to memory as described herein (see steps 310a-310e), thereby eliminating the time-consuming use of scanning for each product in a product information database.
Refernng now specifically to task "a", represented by step 310a, and with reference to Figure 2 as well, SPD data 120 such as the capacity, data width, speed, number of row and column addresses, and/or voltage characteristics of memory module 25, may be read directly from SPD chip 60. BIOS uses this information during the power-on self test (POST) routine to properly configure memory module 25 to optimize reliability and performance. If a memory module 25 does not have an SPD chip 55, BIOS will assume the memory module's information. With some memory, this does not cause problems, but SDRAM typically must have an SPD chip 60 for the computer to successfully boot up.
Known utilities are capable of reading and reporting on SPD data 120. One such known utility is HWINFO available at http:l/www.hwinfo.com. Such utilities are used as diagnostic tools to verify reported system data, and SPD data 120 is not used to assist in providing an upgrade recommendation, as is done in the present invention. Such utilities are thus typically limited to reading SPD data 120 from only a single make of chipset 20, and doing so is sufficient for the purpose of the utility.
The present invention, on the other hand, contemplates an SPD data reader (e.g., a software utility) capable of reading SPD data from various makes of chipsets 20. This may be accomplished by first detecting~the make of the chipset 20 using low-level commands known in the art, then invoking the appropriate subroutine programmed according to specifications of the specific manufacturer of the chipset 20. This is advantageous because the present invention would be of limited value otherwise. Specifically, the present invention anticipates reading SPD data 120 from various makes of chipsets 20 because in practice the diversity of potential client computers to use the present invention would have various makes of SPD chips 60.
Task "b", represented by step 310b, is accessing motherboard parameters 75 from SMBIOS. Motherboard parameters 75 preferably include manufacturer ID and product ID.
For example, manufacturer ID may correspond to "Compaq", and product ID may correspond to "Presario 5340". But motherboard parameters 75 may be any parameters that provide sufficient information to match up motherboard 10 with an entry in product specification database 90a during cross-referencing, as described herein. In fact, motherboard parameters 75 may be only a single parameter.
Task "c", represented by step 310c~ is identification of the write-protect status (represented by 70 in Figure 2) of an SPD chip located on memory module 25.
For purposes of this discussion, the write-protect status is either "read/write"
or "read only".
"Read/write" means SPD chip is not write-protected, whereas "read only" means that the SPD chip is write-protected. Many SPD chips are "read/write", and are thus subject to malicious invasion by unwanted computer viruses.
Write-protect status 70 of a given SPD chip 60 is defined by the existence or non-existence of a certain pin or pin combination associated with SPD chip 60, as is well known in the art. To determine the write-protect status 70 of SPD chip 60 without performing a physical examination thereof, a low-level command may be issued to the operating system of the client computer, such as a command to open a specified area of SPD chip 60 for writing thereto. The return code received by the issuing command will indicate whether the SPD chip 60 is write protected. Typically, if SPD chip 60 is not write-protected (i.e., it has a "read/write status), the upgrade package recommended will include a memory module comprising a write-protected SPD chip. The specific SPD chip recommended may be based upon compatibility considerations identified during cross-referencing of SPD data 120 gathered at step 310a.
Task "d", represented by step 310d, is reading OS data such as system name /
node ID, and/or OS version. Other OS data may be read, and such data may be chosen from a group of data consisting of a system name and an operating system version.
Both system name and OS version may be obtained using low-level commands known in the art.
This information may be used in various ways by implementation of the present invention. For example, if it is determined that the OS version on client computer 5 is Windows XP, and it is also determined that the RAM on client computer 5 is 64MB, the recommended upgrade package could include additional RAM because industry or manufacturer standards require more than 64MB RAM to run Windows XP. This may occur even if doing so might exceed the target hardware configuration.
The system name may be helpful for project management. For example, if a user is using the present invention to obtain hardware upgrade recommendations for multiple computers on a network, and the user is viewing reports related to the hardware upgrade recommendations, having the system name associated with each recommendation will allow the user to efficiently associate the report with the system / node at issue.
Additionally, the physical components ordered by the user may be efficiently sorted, packaged, and labeled according to system name, so when the boxes / containers of components arrive at the installation location, they may be efficiently unpacked and properly allocated.
Task "e" refers to performing a test or tests to determine certain computer characteristics such as memory utilization andlor CPU speed. Other tests may be performed, but in one embodiment of the present invention the tests) islare from the group of tests consisting of a memory utilization test and a CPU speed test. This information may be used in various ways by implementation of the present invention. For example, if it is determined that the amount of memory on computer 5 is already equal to or greater than the amount of memory associated with the target hardware configuration, but results of memory utilization tests nonetheless show the installed memory is 85%
utilized, the recommended upgrade package may include additional memory above the target amount.
In another example, if CPU 15 is tested and is not running at the speed SMBIOS
suggests is achievable, there may be a problem in the configuration of the system. The problem could be as simple as a Turbo button found on many older systems not being activated.
Reporting this to the user as part of the recommended upgrade package may result in the problem being easily addressed by the user, who may then experience an immediate increase in system performance.
Turning now to step 320, upgrade program 85 establishes a target hardware configuration of client computer 5. The target hardware configuration may be based on industry standards, user preferences, vendor recommendations, or any other information. A
target hardware configuration may be manually input into upgrade program 85, or it may be downloaded or read from a data source. Factors that may be considered in establishing a target hardware configuration include economic factors, the computer's intended application, product availability, and operating system characteristics and parameters. For example, in a network-based use of the present invention, target hardware configurations may be established for all computers on the network substantially simultaneously. This may occur in a situation in which corporate guidelines require each computer on the network to have a minimum amount of RAM, such as 512MB, Thus, the target configuration for each computer will be the same, namely to have 512MB of RAM.
As used herein, "establishing" a target hardware configuration may occur by identifying, obtaining, reading, creating, receiving, calculating, determining, or simply verifying information. The target hardware configuration may even be open-ended or qualitative, such as "the maximum power, speed, and memory capacity possible", in which case program 85 can quantify the target configuration based on known parameters. In each instance, the target hardware configuration thus defines parameters within which the upgrade package should be identified.
Once the current hardware configuration of client computer 5 and the target hardware configuration of client computer 5 are known, the two configurations are compared at step 330 to determine the difference and identify an upgrade package for upgrading client computer 5 to the target hardware configuration. For example, if the current configuration of client computer is 128MB of RAM, and the target configuration requires 512MB of RAM, then the difference between the two is 384MB of RAM. In this example, an upgrade package may be identified which includes three 128MB
memory modules to add to client computer 5. Alternatively, the upgrade package may be identified which includes two 256MB memory modules to replace the already existing 128MB
module. The different options may take into consideration cost, physical restraints of client computer 5, product availability or promotions, or other information.
An upgrade package may be simply a single new component, or a single replacement component. An upgrade package may also include multiple components. The package may include specific components that may be ordered using a one-click confirmation. Upgrade packages may be sorted, boxed, and shipped, such that each package is identified by the computer name, network name, or other identifying indicia, to facilitate convenient installation of the upgrade components.
At step 340, a recommendation is provided to use the upgrade package for upgrading client computer 5. Conceptually, recommending the upgrade package may be accomplished by recommend module 110. Typically, the recommendation is provided via a display monitor associated with client computer 5. Recommendations may also be provided through direct mailings, telephone or email notification, and/or any other convenient means of information transmission. The recommendation is based at least partially upon information gathered by detect module 100 at step 310, and may involve cross-referencing the information with product specifications in a database 90a, to ensure a high degree of accuracy and component compatibility. The information may include any or all of; 1) SPD data 120 from SPD chip 60 of client computer 5; 2)motherboard parameters 75; 3) a write-protect status 70 of SPD chip 60; 4) other OS data, such as system name and/or operating system version; and 5) results of tests to determine certain computer characteristics such as memory utilization and/or CPU speed. The process ends at step 350.
As previously stated, as part of or in addition to detecting step 310 and/or recommending step 340, in many instances the data gathered by detect module 100 will be cross-referenced with a product specification database 90a to more accurately determine the current hardware configuration of client computer 5. Product specification database 90a stores specifications for many or all known hardware components, including compatibility restrictions with other hardware components. In this manner, a particular product with exacting specifications may be recommended based upon the current hardware configuration of client computer 5 as accurately determined by the present invention.
For example, when cross-referencing the data gathered related to motherboard 10, the memory expansion slot capability of motherboard 10 may be determined from database 90a. Since such determination is based on the product specifications of the specific motherboard, and not on chipset data 125 stored in SMBIOS area 65, the information is accurate and may be relied upon in providing an upgrade recommendation. Cross-referencing may be accomplished by cross-reference module 115 of upgrade program 85, using programming logic well-known in the art.
For example, assume the user desires to have RAM upgraded in client computer 5.
Generally, hardware suppliers stock RAM modules from a variety of manufacturers having wide variations in their working specifications or parameters. Any number of the RAM
modules may fit the general requirements of the user's upgrade request, but only a few of the available RAM modules will provide the most compatible, accurate, efficient, and reliable hardware component upgrade. Referring to step 310b, in which SPD data 120 is accessed, SPD data 120 is cross-referenced to product database 90a to ensure the recommended RAM not only meets the general requirements of the target configuration (i.e., capacity), but also the compatibility with the current hardware of client computer.
A further consideration in the same example may be whether client computer 5 actually has the physical capacity to accept the target configuration. For example, the target configuration of client computer 5 may call for increasing RAM. Assume motherboard 10 of client computer 5 was designed with three memory module slots capable of a predetermined amount of memory capacity. Further assume chipset 20 of client computer 5 was designed to support a memory capacity greater than that of motherboard 10.
This is not uncommon, because chipsets 20 cannot be matched to every possible computer configuration available. Thus, generally, a computer manufacturer will find it more economical to produce a general chipset 20 that can be easily installed in a wide range of computer configurations.
Since chipset data 125 relates to chipset 20's own memory module capacity, not the memory module capacity of motherboard 10, if a memory module upgrade recommendation is based on chipset data 120, the upgrade package may include a memory module that motherboard 10 cannot physically receive. The present invention solves this problem by accessing motherboard parameters 75 from SMBIOS, and cross-referencing the parameters 75 with product specification database 90a, to determine the true memory module capacity of motherboard 10. Using motherboard parameters 75 of motherboard 10 (typically manufacturer ID and product ID), instead of chipset data 120, a more compatible, accurate, efficient, and reliable determination of an upgrade package is accomplished.
Referring back to Figure 2, a block diagram of upgrade program 85 is shown.
The method as previously described in connection with Figure 3 may be implemented by a system including: a detect module 100 for detecting a current hardware configuration of client computer 5; a compare module I05 for comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading client computer 5 to the target hardware configuration; and a recommend module 110 for providing a recommendation to use the upgrade package for upgrading client computer 5. An optional cross-reference module 115 is used for cross-referencing information about the current configuration of client computer 5, gathered by the detect module 100, with a product information database 90a.
In one embodiment of the present invention, detect module 100 performs at least one task from the group of tasks consisting of (a, b, c) to gather information associated with client computer 5, wherein "a" is accessing SPD data 120 from SPD chip 60 of client computer 5, "b" is accessing motherboard parameters 75 from the memory of client computer 5, said parameters 75 comprising a manufacturer ID and a product ID
of motherboard I0, and "c" is determining a write-protect status (represented by 70) of SPD
chip 60. Compare module 105 compares the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading client computer 5 to the target hardware configuration, said identification being based at least partially upon the information gathered from detect module 100. Recommend module 110 recommends use of the upgrade package for upgrading client computer 5. Optional cross-reference module 115 cross-references the information gathered by detect module 100, with product specifications in database 90a. Modules 100, 105, 110, and 115 are typically embodied in an executable computer program. Modules 100, 1 O5, 110, and 115 perform tasks as described herein in connection with Figure 3.
In certain situations, it may be desirable to reestablish the target hardware configuration, after establishing the target hardware configuration initially at step 320. In such situations, step 320 may be repeated as often as necessary, and step 330 is performed by comparing the current hardware configuration with the reestablished target configuration. Similarly, the current hardware configuration may need to be re-detected multiple times. For example, after initial detection at step 310, the user may xemove or install hardware components of the client computer, so the "current"
configuration previously detected is no longer accurate.
Thus, prior to performing the compare at step 330, the update program may confirm that the current configurations) detected at step 310 and the target configurations) established at step 320 are still valid. This may be accomplished, for example, manually, or by issuing reminders or confirmation queries to the client computers) or a project management computer and waiting a designated time for a response. Alternatively, the program may automatically re-detect the current configuration just prior to performing the compare at step 330, if a designated amount of time has elapsed since the previous "current hardware configuration" was detected. Once the confirmation is complete, the current hardware configurations) (or reestablished current hardware configuration(s)) may be compared to the target hardware configurations) (or reestablished target hardware configuration(s)) to identify an upgrade package or packages (or reestablished upgrade package(s)) for upgrading the client computers) to the target hardware configurations) (or reestablished target hardware configuration(s)).
The upgrade packages) (or reestablished upgrade package(s)) is l are then recommended at step 340, still based at least partially upon the information gathered at the detecting step 310.
While certain embodiments are illustrated in the drawings and axe described herein, including preferred embodiments, it will be apparent to those skilled in the art that the specific embodiments described herein may be modified without departing from the inventive concepts described. For example, though processes of the present invention are illustrated andlor described herein with steps occurring in certain orders, the specific order of the steps is not necessarily required, because certain steps are not dependent on certain other steps. For example, referring to Figure 3, step 320 may occur before or simultaneously with step 310, as the two steps are independent of each other.
Also fox example, while the present invention has been described as providing hardware upgrade recommendations, the present invention may also be used in combination with providing software upgrade recommendations. Accordingly, Applicant's invention as described herein is not to be restricted, except in accordance with the law by the claims which follow.
INFORMATION
TECHNICAL FIELD
The present invention relates generally to computer systems and computer networks. More particularly, the present invention relates to a system and method for providing computer upgrade information based upon component-related data present on a client computer.
INCORPORATION BY REFERENCE
The contents of each U.S, patent or other reference, if any, cited in this application, are hereby incorporated herein by reference.
BACKGROUND ART
The computer has become a permanent fixture in society. Computers are used to facilitate data communications and electronic commerce between businesses, and to gather various types of data such as news, stock market quotes, research facts, sport scores, etc.
Furthermore, computers serve as a source of entertainment through audio and/or visual output display. Just about every aspect of daily life is affected by computers.
The high technology environment of computers is constantly changing.
Typically, staying current with evolving computer technology requires the user to choose between the economics of a computer system replacement or a computer system upgrade. In a computer system upgrade, users attempt to choose upgrade hardware most appropriate for their particular needs and operating environment. For example, common upgrade hardware considerations include faster processor speed, enhanced video capabilities, increased memory, network capabilities, particular I/O devices, etc. For a vendor to provide a meaningful computer upgrade recommendation, the vendor must typically gather information from the user regarding the hardware and software configuration of the user's client computer.
Such data gathering methods include phone or mail surveys, and registration packets filled out by the user after purchase of the computer components or system.
Another data gathering method involves electronic transfer of data from the user to the vendor. For example, the user enters information about the user's computer via on-screen menus, and the information is transmitted to a server computer generally via the Internet, regarding the model of the users computer. The user is then presented with information about their system including upgrade products and paths. Although this method offers upgrade options and is viewed by many as an improvement over prior methods, its success is dependent on the user's knowledge of the client computer's current configuration.
Another method described in U.S. Patent No. 6,370,578, issued April 9, 2002 and titled "Active Marketing Based On Client Computer Configurations", uses a product information database which contains product signatures. The client's system is scanned (e.g., by server software) for the presence of the product signatures corresponding to each product in the product information database to determine if each product is present on the client computer. This method relies less on the user's actual knowledge of his or her client computer than does the previously-described methods, but nonetheless this method is very inefficient because most of the products scanned for are typically not present on the client's computer. Further, the data gathered from such scanning is not always accurate and/or complete enough to allow the vendor to make an optimal upgrade recommendation.
This is due to inherent limitations in the manner in which industry-standard SMBIOS
(System Management Basic Input/output System) and SPD (Serial Presence Detect) data is created, reported, accessed, and/or used in combination with other data to determine the true system state of a client computer.
Since optimizing the accuracy of an upgrade recommendation results in enhanced product reliability and component compatibility, an accurate upgrade recommendation should be based on the most reliable data in determining the current system configuration.
Accordingly, there is a need for a system and method of providing upgrade information for a computer that is more accurate, efficient, and reliable than known methods.
DISCLOSURE OF INVENTION
Systems and methods are disclosed which provide upgrade information for a client computer. The detection of a current hardware configuration of the client computer is facilitated by: 1) reading serial presence detect (SPD) data from the client computer; 2) reading motherboard parameters (such as the product ID and manufacturer ID of the motherboard); and/or 3) identifying the SPD write-protect status of the SPD
chip on the client computer. Additionally or alternatively, detection of the current hardware configuration may be facilitated by: 4) reading other OS data such as system name and operating system version and/or performing tests to determine certain computer characteristics such as memory utilization or CPU speed. In most instances, the information gathered is cross-referenced with a proprietary database of product specifications, to confirm the information is accurate.
The current hardware configuration of the client computer is then compared to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration, and a recommendation is provided to use the upgrade package for upgrading the client computer. Identification of the upgrade package is based at least partially upon the information gathered.
The method of the present invention may be carned out by a system of the present invention embodied in computer software. Conceptually, the software includes various modules to accomplish discrete tasks. The modules may be wholly or partially combined, or split into more discrete sub-modules as desired. In general, the system includes: a detect module for detecting a current hardware configuration of the client computer;
a compare module for comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration; and a recommend module for providing a recommendation to use the upgrade package for upgrading the client computer. An optional cross-reference module is used for cross-referencing information about the current configuration of the client computer, gathered by the detect module, with a product information database.
The detect module detects the hardware configuration of the client computer by performing at least one task from the group of tasks consisting of (a, b, c), or at least one task from the group of tasks consisting of (a, b, c, d, e), to gather information associated with the client computer. Task "a" refers to accessing SPD data from an SPD
chip of the client computer. Task "b" refers to accessing motherboard parameters from the memory of the client computer, such as a manufacturer ID and a product ID of the motherboard. Task "c" refers to determining a write-protect status of the serial presence detect chip of the client computer. Task "d" refers to reading OS data such as system name and/or operating system version. Task "e" refers to performing a test or tests to determine certain computer characteristics such as memory utilization and/or CPU speed. The compare module identifies the upgrade package based at least partially upon the information gathered by the detect module.
The method of detecting the current hardware configuration of a client computer, as describe herein, detects the presence or absence of a limited number of target hardware components, as opposed to scanning for each of hundreds or thousands of components within a proprietary product information database. The method of the present invention thus eliminates the time-consuming use of scanning for each item in a product information database. Furthermore, by cross-referencing the information gathered with product specifications in a proprietary product database, the current hardware configuration of the client computer may be determined more accurately than with known methods.
Upgrade recommendations may then be made for compatible components with a higher degree of success than with known methods.
The present invention as described herein thus provides a system and method of recommending an upgrade package for a computer that is more accurate, efficient, and reliable than known systems or methods. Further objects and advantages of the present invention will be apparent in the detailed description which follows, read in conjunction with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates a typical computer and motherboard configuration.
FIG. 2 illustrates a typical network system for facilitating execution of a method of the present invention, along with block diagrams of an upgrade program used in accordance with the present invention, and relevant features of a typical memory module.
FIG. 3 is a flow chart illustrating a method of providing upgrade information for upgrading a computer according to the present invention.
MODES FOR CARRYING OUT THE INVENTION
The present invention describes a system and method of providing a computer upgrade recommendation that is more accurate, efficient, and reliable than known systems and methods. The current hardware configuration of a client computer is detected by reading serial presence detect (SPD) data, reading motherboard parameters (such as the product ID and manufacturer ID of the motherboard), and/or identifying the SPD
write protect status of the SPD chip of the computer. Additionally or alternatively, detection of the current hardware configuration may be facilitated by reading other OS
data, and/or performing tests to determine certain computer characteristics. In most instances, the information gathered is cross-referenced with a proprietary database of product specifications, to confirm the information is accurate.
The current hardware configuration of the client computer is then compared to a target hardware configuration which has been established, to identify an upgrade package for upgrading the client computer to the target hardware configuration.
Typically, the target hardware configuration is based on industry standards or user preferences. A
recommendation is provided to use the upgrade package for upgrading the client computer to the target configuration.
If the user's needs change after the target hardware configuration has been determined, or even after the upgrade package has been determined, the target hardware configuration may be reestablished accordingly, and the current hardware configuration may then be compared to the reestablished target hardware configuration to identify a reestablished upgrade package for upgrading the client computer to the reestablished target hardware configuration, based at least partially upon the information previously gathered regarding the current hardware configuration. The reestablished upgrade package may then be recommended for upgrading the client computer. Thus, as described more fully herein, the present invention provides for systems and methods that recommend upgrade packages for a computer.
Turning now to Figure 1, a typical client computer 5 and motherboard configuration is shown for reference, and is well-known in the art.
Motherboard 10 is sometimes referred to as the rnainboaxd, system board, logicboard, or even maincard or mothercard. Typically, all of the basic circuitry and components required for a computer to function are either contained on or attached to motherboard 10, such as microprocessor or CPU 15, controller or chipset 20, memory modules 25, serial and parallel ports (not shown), expansion slots 30, power supply 35, internal cache 40, external cache 45, and various cards 50 such as a modem card, video card, and sound card. Memory module 25 includes memory chips 55, an SPD chip 60 (typically an EPROM), and an SMBIOS
area 65 of RAM for storing SMBIOS data (see Figure 2). External hardware components (not show) are also well-known in the art, and may include for example, a monitor, keyboard, mouse, printer, scanner, or any temporarily connected device such as a camera, personal digital assistant (PDA), or data storage device.
When computer 5 is first powered up, CPU 15 passes control to the basic input/out system (BIOS) program located in ROM. Boot-up and BIOS processing are well-known in the art. Briefly, BIOS determines whether the computer's components are operational, and then loads OS files from the computer's hard drive or disk drive into the computer's RAM.
BIOS takes an inventory of equipment and resources, and loads SMBIOS data such as configuration information and drivers into SMBIOS area 65. For example, the SMBIOS
data contains data from chipset 20 regarding the memory module capacity of chipset 20.
Additional SMBIOS data includes motherboard parameters 75 such as the manufacturer ID
and product ID of motherboard 10. As described herein, the present invention uses some of the data from SMBIOS to determine the current hardware configuration of the client computer 5, and make a proper hardware upgrade recommendation.
Turning now to Figure 2, a typical computer network system 80 for facilitating execution of a method of the present invention is shown. Also shown in Figure 2 is a block diagram of upgrade program 85, as well as a block diagram of a memory module 25. In computer network system 80, a plurality of server computers 90 are connected via a communication network 95, such as the Internet, to a client computer 5. One or more servers 90 hosts upgrade program 85, comprised of detect, compare, and recommend modules, 100, 105, and 110, respectively. Upgrade program 85 optionally further comprises cross-reference module 115. Upgrade program 85 is typically embodied in executable computer software, which may run from client computer 5 or server 90, and which may be partially or fully downloaded from server 90 via network 95 to client computer 5.
Detect module 100 is programmed to detect a current hardware configuration of client computer 5, by performing at least one task from the group of tasks consisting of (a, b, c), or at least one task from the group of tasks consisting of (a, b, c, d, e), to gather information associated with client computer 5. Task "a" refers to accessing SPD data 120 from SPD chip 60 of client computer 5. Task "b" refers to accessing motherboard parameters 75 from the memory of client computer 5, for example a manufacturer ID and a product ID of motherboard 10. Task "c" refers to determining a write-protect status (represented by 70) of SPD chip 60 of client computer 5. Task "d" refers to accessing OS
data such as system name andlor operating system version. Task "e" refers to performing a test or tests to determine certain computer characteristics such as memory utilization and/or CPU speed.
Compare module 105 is programmed to compare the current hardware configuration of client computer 5 to a target hardware configuration (previously established), to identify an upgrade package for upgrading client computer 5 to the target hardware configuration. Identification of the upgrade package is based at least partially upon the information gathered by detect module 100. Recommend module 110 is programmed to provide a recommendation to use the upgrade package for upgrading client computer 5. Optional cross-reference module 115 is programmed to cross-reference the information gathered by detect module 100, with product specifications in a product information database 90a. Each of the detect, compare, recommend, and cross-reference modules 100, 105, 110, and 115 are described herein in more detail in connection with Figure 3.
Still referring to Figure 2, a block diagram of a typical memory module 25 is shown, illustrating relevant features. Memory module 25 contains multiple memory chips 55 (e.g., SDRAM andlor RAMBUS), an SPD chip 60 which is typically an EPROM, and an SMBIOS area 65 of RAM for storing SMBIOS data such as motherboard parameters 75 obtained directly from motherboard 10 during boot-up, as well as chipset data 125 obtained from chipset 20 during boot-up. SPD chip 60 contains SPD data 120, and may be write-protected (indicated by write-protect status 70). Use of the aforementioned components and data of memory module 25 will be discussed more fully herein.
Turning now to Figure 3, a flowchart is shown illustrating methods of providing upgrade information for upgrading a computer according to the present invention. The process begins at step 300. At step 310, a current hardware configuration of the client computer is detected. The detection may include one or more of tasks 310a, 310b, 310c, 310d, and 3 10e discussed more fully herein. At step 320, a target hardware configuration for the client computer is established. The current configuration is then compared to the target configuration at step 330, and a recommendation for an upgrade is provided based upon the results of the comparison, as seen at step 340. The process ends at step 350. Each step will now be discussed in more detail.
Referring now to step 310 in more detail, the current hardware configuration of the client computer is detected. Step 310 may include any combination of one or more of steps 310a, 310b, 310c, 310d, and 310e. In one embodiment of the present invention, step 310 includes at least one of the tasks from the group of tasks consisting of "a", "b", and "c", represented by steps 310a, 310b, and 310c respectively. That is, step 310 may include only step "a", only step "b", only step "c", only steps "a" and "b", only steps "a"
and "c", only steps "b" and "c", or all three steps "a", "b", and "c".
In those instances which include step "a", preferably SPD data 120 is cross referenced with product specifications in database 90a. Similarly, in those instances which include step "b", preferably motherboard parameters 75 are cross-referenced with product specifications in database 90a. Such cross-referencing may be performed by cross-reference module 115, and the benefits thereof are discussed more fully herein.
Detection of the current hardware configuration of the client computer at step may be initiated in various ways. For example, an individual user may request detection through an active link on a website. In that case, upgrade program 85 may run wholly or partially from a server computer over the Internet, or may be downloaded to the client computer at that time to run locally. Or upgrade program 85 may be resident on the client computer or accessible over a local or other computer network. These and other variations are well-known in the art. In any case, the detecting may be performed automatically in response to a single user request. Similarly, the entire process of detecting (310), comparing (330), and recommending (340) may be performed automatically in response to the single user request, which may be received at a computer server over a computer netwoxk. Detect, compare, and recommend modules (100, 145, and i 10 respectively) may be embodied in an executable computer program 85 as seen in Figure 2. The entire process may also be programmed to initiate automatically at specified time intervals.
The present invention is useful not only for providing an upgrade recommendation for a single client computer 5, but also for providing project-based or network-based upgrade recommendations. In this manner, the process may be performed on an entire network automatically or by a single manual request at substantially the same time. If a single user request is initiated to run upgrade program 85 on a network /
project, the process preferably includes steps 300-350 for each client computer. That is, if client computer 5 is part of a network comprising additional client computers, the process may:
detect the current hardware configurations of each of the additional client computers;
establish corresponding target hardware configurations for each of the additional client computers; compare the current hardware configurations of each of the additional client computers to the corresponding target hardware configurations of each of the additional client computers to identify corresponding upgrade packages for upgrading each of the additional client computers to the corresponding target hardware configurations; and recommend use of the corresponding upgrade packages for upgrading each of the additional client computers.
If a particular client computer in the project has not had its current hardware configuration detected (310), and/or not had its target hardware configuration established (320), those'steps may be executed on that particular client computer. On the other hand, if the current hardware configuration has been detected (310), and/or the target hardware configuration has been established (320), those steps may be skipped for that particular client computer. This may be accomplished using basic programming logic. The process may proceed on a project basis by performing steps 300-350 consecutively for each client computer, or by performing 310 on each computer, then 320 on each computer, then 330 on each computer, then 340 on each computer. It is simply a matter of preference as to what order the steps of the process are performed when a project-based upgrade recommendation is being executed.
For example, when the present invention is used with project-based upgrade recommendations, the detection step (310) may be executed at various times either individually by particular client computer users, or by a network administrator for multiple client computers on the network. The current hardware configurations of the detected client computers may be stored in a database for future reference. If an individual manually reconfigures his or her client computer (e.g., adding memory), then that user can request re-detection of that client computer, and the updated current hardware configuration may be stored at the database until such time as it is needed for completion of the process.
Similarly, the target hardware configurations of each client computer in a project-based upgrade may be reestablished (320), as needed. The compare step (330) may also be accomplished individually, or on a project-based scale. While each client computer within a project may have its current hardware configuration detected (310) and its corresponding target hardware configuration established (320) individually, in one embodiment of the present invention all client computers in the project will have had their current and target hardware configurations loaded into a project-based database prior to the compare step (330) being performed. In this manner, upgrade program 85 may operate on the entire project based on a single request, with the comparing (330) and recommending (340) steps being performed on each client computer within the project, substantially simultaneously.
Still referring to step 310, the present invention "detects" the presence or absence of specific hardware components on a client computer, as opposed to "scanning"
for the presence or absence of those components. Scanning refers to checking each product signature in a product information database against the client computer, to determine the presence or absence of the product. Scanning is described in U.S. Patent No.
6,370,578, previously discussed in the Background Section of the pxesent application.
Scanning is extremely inefficient because the server or upgrade program scans for many items that are not present on the client's computer. The present invention, on the other hand, detects the presence or absence of only a limited number of hardware components of concern, mostly related to memory as described herein (see steps 310a-310e), thereby eliminating the time-consuming use of scanning for each product in a product information database.
Refernng now specifically to task "a", represented by step 310a, and with reference to Figure 2 as well, SPD data 120 such as the capacity, data width, speed, number of row and column addresses, and/or voltage characteristics of memory module 25, may be read directly from SPD chip 60. BIOS uses this information during the power-on self test (POST) routine to properly configure memory module 25 to optimize reliability and performance. If a memory module 25 does not have an SPD chip 55, BIOS will assume the memory module's information. With some memory, this does not cause problems, but SDRAM typically must have an SPD chip 60 for the computer to successfully boot up.
Known utilities are capable of reading and reporting on SPD data 120. One such known utility is HWINFO available at http:l/www.hwinfo.com. Such utilities are used as diagnostic tools to verify reported system data, and SPD data 120 is not used to assist in providing an upgrade recommendation, as is done in the present invention. Such utilities are thus typically limited to reading SPD data 120 from only a single make of chipset 20, and doing so is sufficient for the purpose of the utility.
The present invention, on the other hand, contemplates an SPD data reader (e.g., a software utility) capable of reading SPD data from various makes of chipsets 20. This may be accomplished by first detecting~the make of the chipset 20 using low-level commands known in the art, then invoking the appropriate subroutine programmed according to specifications of the specific manufacturer of the chipset 20. This is advantageous because the present invention would be of limited value otherwise. Specifically, the present invention anticipates reading SPD data 120 from various makes of chipsets 20 because in practice the diversity of potential client computers to use the present invention would have various makes of SPD chips 60.
Task "b", represented by step 310b, is accessing motherboard parameters 75 from SMBIOS. Motherboard parameters 75 preferably include manufacturer ID and product ID.
For example, manufacturer ID may correspond to "Compaq", and product ID may correspond to "Presario 5340". But motherboard parameters 75 may be any parameters that provide sufficient information to match up motherboard 10 with an entry in product specification database 90a during cross-referencing, as described herein. In fact, motherboard parameters 75 may be only a single parameter.
Task "c", represented by step 310c~ is identification of the write-protect status (represented by 70 in Figure 2) of an SPD chip located on memory module 25.
For purposes of this discussion, the write-protect status is either "read/write"
or "read only".
"Read/write" means SPD chip is not write-protected, whereas "read only" means that the SPD chip is write-protected. Many SPD chips are "read/write", and are thus subject to malicious invasion by unwanted computer viruses.
Write-protect status 70 of a given SPD chip 60 is defined by the existence or non-existence of a certain pin or pin combination associated with SPD chip 60, as is well known in the art. To determine the write-protect status 70 of SPD chip 60 without performing a physical examination thereof, a low-level command may be issued to the operating system of the client computer, such as a command to open a specified area of SPD chip 60 for writing thereto. The return code received by the issuing command will indicate whether the SPD chip 60 is write protected. Typically, if SPD chip 60 is not write-protected (i.e., it has a "read/write status), the upgrade package recommended will include a memory module comprising a write-protected SPD chip. The specific SPD chip recommended may be based upon compatibility considerations identified during cross-referencing of SPD data 120 gathered at step 310a.
Task "d", represented by step 310d, is reading OS data such as system name /
node ID, and/or OS version. Other OS data may be read, and such data may be chosen from a group of data consisting of a system name and an operating system version.
Both system name and OS version may be obtained using low-level commands known in the art.
This information may be used in various ways by implementation of the present invention. For example, if it is determined that the OS version on client computer 5 is Windows XP, and it is also determined that the RAM on client computer 5 is 64MB, the recommended upgrade package could include additional RAM because industry or manufacturer standards require more than 64MB RAM to run Windows XP. This may occur even if doing so might exceed the target hardware configuration.
The system name may be helpful for project management. For example, if a user is using the present invention to obtain hardware upgrade recommendations for multiple computers on a network, and the user is viewing reports related to the hardware upgrade recommendations, having the system name associated with each recommendation will allow the user to efficiently associate the report with the system / node at issue.
Additionally, the physical components ordered by the user may be efficiently sorted, packaged, and labeled according to system name, so when the boxes / containers of components arrive at the installation location, they may be efficiently unpacked and properly allocated.
Task "e" refers to performing a test or tests to determine certain computer characteristics such as memory utilization andlor CPU speed. Other tests may be performed, but in one embodiment of the present invention the tests) islare from the group of tests consisting of a memory utilization test and a CPU speed test. This information may be used in various ways by implementation of the present invention. For example, if it is determined that the amount of memory on computer 5 is already equal to or greater than the amount of memory associated with the target hardware configuration, but results of memory utilization tests nonetheless show the installed memory is 85%
utilized, the recommended upgrade package may include additional memory above the target amount.
In another example, if CPU 15 is tested and is not running at the speed SMBIOS
suggests is achievable, there may be a problem in the configuration of the system. The problem could be as simple as a Turbo button found on many older systems not being activated.
Reporting this to the user as part of the recommended upgrade package may result in the problem being easily addressed by the user, who may then experience an immediate increase in system performance.
Turning now to step 320, upgrade program 85 establishes a target hardware configuration of client computer 5. The target hardware configuration may be based on industry standards, user preferences, vendor recommendations, or any other information. A
target hardware configuration may be manually input into upgrade program 85, or it may be downloaded or read from a data source. Factors that may be considered in establishing a target hardware configuration include economic factors, the computer's intended application, product availability, and operating system characteristics and parameters. For example, in a network-based use of the present invention, target hardware configurations may be established for all computers on the network substantially simultaneously. This may occur in a situation in which corporate guidelines require each computer on the network to have a minimum amount of RAM, such as 512MB, Thus, the target configuration for each computer will be the same, namely to have 512MB of RAM.
As used herein, "establishing" a target hardware configuration may occur by identifying, obtaining, reading, creating, receiving, calculating, determining, or simply verifying information. The target hardware configuration may even be open-ended or qualitative, such as "the maximum power, speed, and memory capacity possible", in which case program 85 can quantify the target configuration based on known parameters. In each instance, the target hardware configuration thus defines parameters within which the upgrade package should be identified.
Once the current hardware configuration of client computer 5 and the target hardware configuration of client computer 5 are known, the two configurations are compared at step 330 to determine the difference and identify an upgrade package for upgrading client computer 5 to the target hardware configuration. For example, if the current configuration of client computer is 128MB of RAM, and the target configuration requires 512MB of RAM, then the difference between the two is 384MB of RAM. In this example, an upgrade package may be identified which includes three 128MB
memory modules to add to client computer 5. Alternatively, the upgrade package may be identified which includes two 256MB memory modules to replace the already existing 128MB
module. The different options may take into consideration cost, physical restraints of client computer 5, product availability or promotions, or other information.
An upgrade package may be simply a single new component, or a single replacement component. An upgrade package may also include multiple components. The package may include specific components that may be ordered using a one-click confirmation. Upgrade packages may be sorted, boxed, and shipped, such that each package is identified by the computer name, network name, or other identifying indicia, to facilitate convenient installation of the upgrade components.
At step 340, a recommendation is provided to use the upgrade package for upgrading client computer 5. Conceptually, recommending the upgrade package may be accomplished by recommend module 110. Typically, the recommendation is provided via a display monitor associated with client computer 5. Recommendations may also be provided through direct mailings, telephone or email notification, and/or any other convenient means of information transmission. The recommendation is based at least partially upon information gathered by detect module 100 at step 310, and may involve cross-referencing the information with product specifications in a database 90a, to ensure a high degree of accuracy and component compatibility. The information may include any or all of; 1) SPD data 120 from SPD chip 60 of client computer 5; 2)motherboard parameters 75; 3) a write-protect status 70 of SPD chip 60; 4) other OS data, such as system name and/or operating system version; and 5) results of tests to determine certain computer characteristics such as memory utilization and/or CPU speed. The process ends at step 350.
As previously stated, as part of or in addition to detecting step 310 and/or recommending step 340, in many instances the data gathered by detect module 100 will be cross-referenced with a product specification database 90a to more accurately determine the current hardware configuration of client computer 5. Product specification database 90a stores specifications for many or all known hardware components, including compatibility restrictions with other hardware components. In this manner, a particular product with exacting specifications may be recommended based upon the current hardware configuration of client computer 5 as accurately determined by the present invention.
For example, when cross-referencing the data gathered related to motherboard 10, the memory expansion slot capability of motherboard 10 may be determined from database 90a. Since such determination is based on the product specifications of the specific motherboard, and not on chipset data 125 stored in SMBIOS area 65, the information is accurate and may be relied upon in providing an upgrade recommendation. Cross-referencing may be accomplished by cross-reference module 115 of upgrade program 85, using programming logic well-known in the art.
For example, assume the user desires to have RAM upgraded in client computer 5.
Generally, hardware suppliers stock RAM modules from a variety of manufacturers having wide variations in their working specifications or parameters. Any number of the RAM
modules may fit the general requirements of the user's upgrade request, but only a few of the available RAM modules will provide the most compatible, accurate, efficient, and reliable hardware component upgrade. Referring to step 310b, in which SPD data 120 is accessed, SPD data 120 is cross-referenced to product database 90a to ensure the recommended RAM not only meets the general requirements of the target configuration (i.e., capacity), but also the compatibility with the current hardware of client computer.
A further consideration in the same example may be whether client computer 5 actually has the physical capacity to accept the target configuration. For example, the target configuration of client computer 5 may call for increasing RAM. Assume motherboard 10 of client computer 5 was designed with three memory module slots capable of a predetermined amount of memory capacity. Further assume chipset 20 of client computer 5 was designed to support a memory capacity greater than that of motherboard 10.
This is not uncommon, because chipsets 20 cannot be matched to every possible computer configuration available. Thus, generally, a computer manufacturer will find it more economical to produce a general chipset 20 that can be easily installed in a wide range of computer configurations.
Since chipset data 125 relates to chipset 20's own memory module capacity, not the memory module capacity of motherboard 10, if a memory module upgrade recommendation is based on chipset data 120, the upgrade package may include a memory module that motherboard 10 cannot physically receive. The present invention solves this problem by accessing motherboard parameters 75 from SMBIOS, and cross-referencing the parameters 75 with product specification database 90a, to determine the true memory module capacity of motherboard 10. Using motherboard parameters 75 of motherboard 10 (typically manufacturer ID and product ID), instead of chipset data 120, a more compatible, accurate, efficient, and reliable determination of an upgrade package is accomplished.
Referring back to Figure 2, a block diagram of upgrade program 85 is shown.
The method as previously described in connection with Figure 3 may be implemented by a system including: a detect module 100 for detecting a current hardware configuration of client computer 5; a compare module I05 for comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading client computer 5 to the target hardware configuration; and a recommend module 110 for providing a recommendation to use the upgrade package for upgrading client computer 5. An optional cross-reference module 115 is used for cross-referencing information about the current configuration of client computer 5, gathered by the detect module 100, with a product information database 90a.
In one embodiment of the present invention, detect module 100 performs at least one task from the group of tasks consisting of (a, b, c) to gather information associated with client computer 5, wherein "a" is accessing SPD data 120 from SPD chip 60 of client computer 5, "b" is accessing motherboard parameters 75 from the memory of client computer 5, said parameters 75 comprising a manufacturer ID and a product ID
of motherboard I0, and "c" is determining a write-protect status (represented by 70) of SPD
chip 60. Compare module 105 compares the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading client computer 5 to the target hardware configuration, said identification being based at least partially upon the information gathered from detect module 100. Recommend module 110 recommends use of the upgrade package for upgrading client computer 5. Optional cross-reference module 115 cross-references the information gathered by detect module 100, with product specifications in database 90a. Modules 100, 105, 110, and 115 are typically embodied in an executable computer program. Modules 100, 1 O5, 110, and 115 perform tasks as described herein in connection with Figure 3.
In certain situations, it may be desirable to reestablish the target hardware configuration, after establishing the target hardware configuration initially at step 320. In such situations, step 320 may be repeated as often as necessary, and step 330 is performed by comparing the current hardware configuration with the reestablished target configuration. Similarly, the current hardware configuration may need to be re-detected multiple times. For example, after initial detection at step 310, the user may xemove or install hardware components of the client computer, so the "current"
configuration previously detected is no longer accurate.
Thus, prior to performing the compare at step 330, the update program may confirm that the current configurations) detected at step 310 and the target configurations) established at step 320 are still valid. This may be accomplished, for example, manually, or by issuing reminders or confirmation queries to the client computers) or a project management computer and waiting a designated time for a response. Alternatively, the program may automatically re-detect the current configuration just prior to performing the compare at step 330, if a designated amount of time has elapsed since the previous "current hardware configuration" was detected. Once the confirmation is complete, the current hardware configurations) (or reestablished current hardware configuration(s)) may be compared to the target hardware configurations) (or reestablished target hardware configuration(s)) to identify an upgrade package or packages (or reestablished upgrade package(s)) for upgrading the client computers) to the target hardware configurations) (or reestablished target hardware configuration(s)).
The upgrade packages) (or reestablished upgrade package(s)) is l are then recommended at step 340, still based at least partially upon the information gathered at the detecting step 310.
While certain embodiments are illustrated in the drawings and axe described herein, including preferred embodiments, it will be apparent to those skilled in the art that the specific embodiments described herein may be modified without departing from the inventive concepts described. For example, though processes of the present invention are illustrated andlor described herein with steps occurring in certain orders, the specific order of the steps is not necessarily required, because certain steps are not dependent on certain other steps. For example, referring to Figure 3, step 320 may occur before or simultaneously with step 310, as the two steps are independent of each other.
Also fox example, while the present invention has been described as providing hardware upgrade recommendations, the present invention may also be used in combination with providing software upgrade recommendations. Accordingly, Applicant's invention as described herein is not to be restricted, except in accordance with the law by the claims which follow.
Claims (20)
1. A method of providing upgrade information for a client computer having a motherboard, a memory, and a serial presence detect chip, comprising the steps:
detecting a current hardware configuration of the client computer;
establishing a target hardware configuration for the client computer;
comparing the current hardware configuration to the target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration; and recommending use of the upgrade package for upgrading the client computer;
wherein the detection of the current hardware configuration of the client computer includes performing at least one task from the group of tasks consisting of (a, b, c) to gather information associated with the client computer, in which: task "a" is accessing serial presence detect data from a serial presence detect chip of the client computer; task "b" is accessing motherboard parameters from the memory of the client computer, said parameters comprising a manufacturer ID and a product ID of the motherboard;
and task "c" is determining a write-protect status of the serial presence detect chip of the client computer; and wherein the identification of the upgrade package is based at least partially upon the information gathered.
detecting a current hardware configuration of the client computer;
establishing a target hardware configuration for the client computer;
comparing the current hardware configuration to the target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration; and recommending use of the upgrade package for upgrading the client computer;
wherein the detection of the current hardware configuration of the client computer includes performing at least one task from the group of tasks consisting of (a, b, c) to gather information associated with the client computer, in which: task "a" is accessing serial presence detect data from a serial presence detect chip of the client computer; task "b" is accessing motherboard parameters from the memory of the client computer, said parameters comprising a manufacturer ID and a product ID of the motherboard;
and task "c" is determining a write-protect status of the serial presence detect chip of the client computer; and wherein the identification of the upgrade package is based at least partially upon the information gathered.
2. The method of Claim 1, wherein task "a" is performed, and wherein the serial presence detect data is cross-referenced with product specifications in a database.
3. The method of Claim 2, wherein task "b" is performed, and wherein the motherboard parameters are cross-referenced with product specifications in a database.
4. The method of Claim 3, wherein task "c" is performed.
5. The method of Claim 2, wherein task "c" is performed.
6. The method of Claim 1, Wherein task "b" is performed, and wherein the motherboard parameters are cross-referenced with product specifications in a database.
7. The method of Claim 6, wherein the cross-referencing step comprises determining a memory expansion slot capability of the motherboard.
8. The method of Claim 6, wherein task "c" is performed.
9. The method of Claim 1, wherein task "c" is performed.
10. The method of Claim 9, wherein the write-protect status of the serial presence detect chip is "read/write", and wherein the upgrade package includes a memory module comprising a serial presence detect chip having a write-protect status of "read only".
11. The method of Claim 1, wherein the target hardware configuration is based upon industry standards.
12. The method of Claim 1, further comprising the steps of:
reestablishing the target hardware configuration, after establishing the target hardware configuration;
comparing the current hardware configuration to the reestablished target hardware configuration to identify a reestablished upgrade package for upgrading the client computer to the reestablished target hardware configuration; and recommending use of the reestablished upgrade package for upgrading the client computer;
wherein the identification of the reestablished upgrade package is based at least partially upon the information gathered.
reestablishing the target hardware configuration, after establishing the target hardware configuration;
comparing the current hardware configuration to the reestablished target hardware configuration to identify a reestablished upgrade package for upgrading the client computer to the reestablished target hardware configuration; and recommending use of the reestablished upgrade package for upgrading the client computer;
wherein the identification of the reestablished upgrade package is based at least partially upon the information gathered.
13. The method of Claim 1, wherein the detecting, comparing, and recommending steps are performed by detect, compare, and recommend modules respectively, automatically in response to a single user request.
14. The method of Claim 13, wherein the single user request is received at a computer server over a computer network, and wherein the detect, compare, and recommend modules are embodied in an executable computer program.
15. The method of Claim 1, wherein the client computer is part of a network comprising additional client computers, and further comprising the steps of:
detecting current hardware configurations of each of the additional client computers;
establishing corresponding target hardware configurations for each of the additional client computers;
comparing the current hardware configurations of each of the additional client computers to the corresponding target hardware configurations of each of the additional client computers to identify corresponding upgrade packages for upgrading each of the additional client computers to the corresponding target hardware configurations; and recommending use of the corresponding upgrade packages for upgrading each of the additional client computers.
detecting current hardware configurations of each of the additional client computers;
establishing corresponding target hardware configurations for each of the additional client computers;
comparing the current hardware configurations of each of the additional client computers to the corresponding target hardware configurations of each of the additional client computers to identify corresponding upgrade packages for upgrading each of the additional client computers to the corresponding target hardware configurations; and recommending use of the corresponding upgrade packages for upgrading each of the additional client computers.
16. A method of providing upgrade information for a client computer having a motherboard, a memory, and a serial presence detect chip, comprising the steps:
detecting a current hardware configuration of the client computer;
comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration; and recommending use of the upgrade package for upgrading the client computer;
wherein the detection of the current hardware configuration of the client computer includes performing at least one task from the group of tasks consisting of (a, b, c, d, e) to gather information associated with the client computer, in which: task "a" is accessing serial presence detect data from a serial presence detect chip of the client computer; task "b" is accessing motherboard parameters from the memory of the client computer, said parameters comprising a manufacturer ID and a product ID of the motherboard;
task "c" is determining a write-protect status of the serial presence detect chip of the client computer;
task "d" is accessing OS data from a group of data consisting of a system name and an operating system version; and task "e" is performing a test from the group of tests consisting of a memory utilization test and a CPU speed test; and wherein the identification of the upgrade package is based at least partially upon the information gathered.
detecting a current hardware configuration of the client computer;
comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration; and recommending use of the upgrade package for upgrading the client computer;
wherein the detection of the current hardware configuration of the client computer includes performing at least one task from the group of tasks consisting of (a, b, c, d, e) to gather information associated with the client computer, in which: task "a" is accessing serial presence detect data from a serial presence detect chip of the client computer; task "b" is accessing motherboard parameters from the memory of the client computer, said parameters comprising a manufacturer ID and a product ID of the motherboard;
task "c" is determining a write-protect status of the serial presence detect chip of the client computer;
task "d" is accessing OS data from a group of data consisting of a system name and an operating system version; and task "e" is performing a test from the group of tests consisting of a memory utilization test and a CPU speed test; and wherein the identification of the upgrade package is based at least partially upon the information gathered.
17. A system of providing upgrade information for a client computer having a motherboard, a memory, and a serial presence detect chip, comprising:
a detect module for detecting a current hardware configuration of the client computer by performing at least one task from the group of tasks consisting of (a, b, c) to gather information associated with the client computer, wherein "a" is accessing serial presence detect data from a serial presence detect chip of the client computer, "b" is accessing motherboard parameters from the memory of the client computer, said parameters comprising a manufacturer ID and a product ID of the motherboard, and "c" is determining a write-protect status of the serial presence detect chip;
a compare module for comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration, said identification being based at least partially upon the information; and a recommend module for recommending use of the upgrade package for upgrading the client computer.
a detect module for detecting a current hardware configuration of the client computer by performing at least one task from the group of tasks consisting of (a, b, c) to gather information associated with the client computer, wherein "a" is accessing serial presence detect data from a serial presence detect chip of the client computer, "b" is accessing motherboard parameters from the memory of the client computer, said parameters comprising a manufacturer ID and a product ID of the motherboard, and "c" is determining a write-protect status of the serial presence detect chip;
a compare module for comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration, said identification being based at least partially upon the information; and a recommend module for recommending use of the upgrade package for upgrading the client computer.
18. The system of Claim 17, further comprising a cross-reference module for cross-referencing the information gathered with product specifications in a database.
19. The system of Claim 18, wherein the detect, compare, recommend, and cross-reference modules are embodied in an executable computer program.
20. A system of providing upgrade information for a client computer having a motherboard, a memory, and a serial presence detect chip, comprising:
a detect module for detecting a current hardware configuration of the client computer by performing at least one task from the group of tasks consisting of (a, b, c, d, e) to gather information associated with the client computer, wherein "a" is accessing serial presence detect data from a serial presence detect chip of the client computer, "b" is accessing motherboard parameters from the memory of the client computer, said parameters comprising a manufacturer ID and a product ID of the motherboard, "c" is determining a write-protect status of the serial presence detect chip, "d" is accessing OS
data from a group of data consisting of a system name and an operating system version, and "e" is performing a test from the group of tests consisting of a memory utilization test and a CPU speed test;
a compare module for comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration, said identification being based at least partially upon the information; and a recommend module for recommending use of the upgrade package for upgrading the client computer;
wherein the identification of the upgrade package is based at least partially upon the information gathered.
a detect module for detecting a current hardware configuration of the client computer by performing at least one task from the group of tasks consisting of (a, b, c, d, e) to gather information associated with the client computer, wherein "a" is accessing serial presence detect data from a serial presence detect chip of the client computer, "b" is accessing motherboard parameters from the memory of the client computer, said parameters comprising a manufacturer ID and a product ID of the motherboard, "c" is determining a write-protect status of the serial presence detect chip, "d" is accessing OS
data from a group of data consisting of a system name and an operating system version, and "e" is performing a test from the group of tests consisting of a memory utilization test and a CPU speed test;
a compare module for comparing the current hardware configuration to a target hardware configuration to identify an upgrade package for upgrading the client computer to the target hardware configuration, said identification being based at least partially upon the information; and a recommend module for recommending use of the upgrade package for upgrading the client computer;
wherein the identification of the upgrade package is based at least partially upon the information gathered.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/271,101 US6711676B1 (en) | 2002-10-15 | 2002-10-15 | System and method for providing computer upgrade information |
| US10/271,101 | 2002-10-15 | ||
| PCT/US2003/020756 WO2004036445A1 (en) | 2002-10-15 | 2003-07-02 | System and method for providing computer upgrade information |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2542786A1 true CA2542786A1 (en) | 2004-04-29 |
Family
ID=31977995
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002542786A Abandoned CA2542786A1 (en) | 2002-10-15 | 2003-07-02 | System and method for providing computer upgrade information |
Country Status (4)
| Country | Link |
|---|---|
| US (2) | US6711676B1 (en) |
| AU (1) | AU2003301359A1 (en) |
| CA (1) | CA2542786A1 (en) |
| WO (1) | WO2004036445A1 (en) |
Families Citing this family (79)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6453347B1 (en) * | 1999-10-29 | 2002-09-17 | Mcafee.Com, Inc. | Active marketing based on client computer configurations |
| US7366685B2 (en) * | 2001-05-25 | 2008-04-29 | International Business Machines Corporation | Method and apparatus upgrade assistance using critical historical product information |
| US6952767B1 (en) * | 2001-10-26 | 2005-10-04 | Hewlett-Packard Development Company, L.P. | System and method for maintaining a predetermined price/performance level of technology on a computer system during a subscription |
| US9009698B2 (en) * | 2002-10-15 | 2015-04-14 | Rpx Corporation | System and method for providing computer upgrade information |
| US6711676B1 (en) * | 2002-10-15 | 2004-03-23 | Zomaya Group, Inc. | System and method for providing computer upgrade information |
| US7577948B2 (en) * | 2003-07-02 | 2009-08-18 | Upgradedetect, Inc. | System and method for providing computer upgrade information |
| US7647254B2 (en) * | 2002-11-20 | 2010-01-12 | Acer Incorporated | Method and system for providing customized computer solutions |
| US7810128B2 (en) * | 2003-02-14 | 2010-10-05 | Sony Corporation | Information management system and method, center processing apparatus and method, program and recording medium used therewith, and information processing apparatus and method, and program and recording medium used therewith |
| US20040199518A1 (en) * | 2003-04-04 | 2004-10-07 | Shoobe Howard A. | System and method for transition of information handling system configuration |
| US7743365B2 (en) * | 2003-06-26 | 2010-06-22 | Microsoft Corporation | Determining and using capabilities of a computer system |
| US7117348B2 (en) * | 2003-06-27 | 2006-10-03 | American Megatrends, Inc. | Method and system for detecting the validity of configuration data |
| US7506051B2 (en) * | 2003-09-30 | 2009-03-17 | International Business Machines Corporation | Method and apparatus for automatically conducting hardware inventories of computers in a network |
| KR100594747B1 (en) * | 2003-12-05 | 2006-06-30 | 삼성전자주식회사 | Device, system and method of managing module |
| GB2409735A (en) * | 2003-12-30 | 2005-07-06 | Ibm | Method and system for change management of interfaces in distributed computer systems |
| US7797525B2 (en) * | 2004-07-01 | 2010-09-14 | Hewlett-Packard Development Company, L.P. | Operating system installation |
| CN100530146C (en) * | 2004-08-26 | 2009-08-19 | 鸿富锦精密工业（深圳）有限公司 | BIOS on-line rewriting method |
| US20060047576A1 (en) * | 2004-08-30 | 2006-03-02 | Nokia Corporation | Automated memory and accessory purchasing agent for use in a mobile terminal |
| US20060064563A1 (en) * | 2004-09-23 | 2006-03-23 | Hobson Louis B | Caching presence detection data |
| AU2005304792B2 (en) * | 2004-11-05 | 2010-07-08 | Drobo, Inc. | Storage system condition indicator and method |
| US20060106806A1 (en) * | 2004-11-12 | 2006-05-18 | Smith Micro Software, Inc. | Software update for a plurality of mobile devices |
| US7640423B2 (en) * | 2005-02-14 | 2009-12-29 | Red Hat, Inc. | System and method for verifying compatibility of computer equipment with a software product |
| US20060218649A1 (en) * | 2005-03-22 | 2006-09-28 | Brickell Ernie F | Method for conditional disclosure of identity information |
| US20060224874A1 (en) * | 2005-03-30 | 2006-10-05 | Inventec Corporation | Method for updating system management basic input output system (SMBIOS) data |
| US20060230097A1 (en) * | 2005-04-08 | 2006-10-12 | Caterpillar Inc. | Process model monitoring method and system |
| US8209156B2 (en) * | 2005-04-08 | 2012-06-26 | Caterpillar Inc. | Asymmetric random scatter process for probabilistic modeling system for product design |
| US7877239B2 (en) * | 2005-04-08 | 2011-01-25 | Caterpillar Inc | Symmetric random scatter process for probabilistic modeling system for product design |
| US20060229753A1 (en) * | 2005-04-08 | 2006-10-12 | Caterpillar Inc. | Probabilistic modeling system for product design |
| US7565333B2 (en) * | 2005-04-08 | 2009-07-21 | Caterpillar Inc. | Control system and method |
| US8364610B2 (en) | 2005-04-08 | 2013-01-29 | Caterpillar Inc. | Process modeling and optimization method and system |
| US20060229854A1 (en) * | 2005-04-08 | 2006-10-12 | Caterpillar Inc. | Computer system architecture for probabilistic modeling |
| US20060229852A1 (en) * | 2005-04-08 | 2006-10-12 | Caterpillar Inc. | Zeta statistic process method and system |
| US7546472B2 (en) * | 2005-04-15 | 2009-06-09 | Dell Products L.P. | Information handling system that supplies power to a memory expansion board |
| US20070061144A1 (en) * | 2005-08-30 | 2007-03-15 | Caterpillar Inc. | Batch statistics process model method and system |
| US7487134B2 (en) * | 2005-10-25 | 2009-02-03 | Caterpillar Inc. | Medical risk stratifying method and system |
| US20070118487A1 (en) * | 2005-11-18 | 2007-05-24 | Caterpillar Inc. | Product cost modeling method and system |
| US7499842B2 (en) | 2005-11-18 | 2009-03-03 | Caterpillar Inc. | Process model based virtual sensor and method |
| TW200720941A (en) * | 2005-11-18 | 2007-06-01 | Inventec Corp | Host computer memory configuration data remote access method and system |
| US7505949B2 (en) * | 2006-01-31 | 2009-03-17 | Caterpillar Inc. | Process model error correction method and system |
| US20070203810A1 (en) * | 2006-02-13 | 2007-08-30 | Caterpillar Inc. | Supply chain modeling method and system |
| US8387038B2 (en) * | 2006-08-14 | 2013-02-26 | Caterpillar Inc. | Method and system for automatic computer and user migration |
| US8478506B2 (en) | 2006-09-29 | 2013-07-02 | Caterpillar Inc. | Virtual sensor based engine control system and method |
| US20080155240A1 (en) * | 2006-10-04 | 2008-06-26 | Bagwell Derek P | Increasing performance of the creation of upgrade configurations based on heuristics |
| US20080108435A1 (en) * | 2006-11-03 | 2008-05-08 | Igt | Monitoring and controlling gaming-environments |
| US7483774B2 (en) * | 2006-12-21 | 2009-01-27 | Caterpillar Inc. | Method and system for intelligent maintenance |
| US20080154811A1 (en) * | 2006-12-21 | 2008-06-26 | Caterpillar Inc. | Method and system for verifying virtual sensors |
| US20080168167A1 (en) * | 2007-01-04 | 2008-07-10 | Calrson Michael P | Service provided by a single entity for all applications |
| US20080183852A1 (en) * | 2007-01-26 | 2008-07-31 | Pramer David M | Virtual information technology assistant |
| US8539473B2 (en) * | 2007-01-30 | 2013-09-17 | Microsoft Corporation | Techniques for providing information regarding software components for a user-defined context |
| US7787969B2 (en) * | 2007-06-15 | 2010-08-31 | Caterpillar Inc | Virtual sensor system and method |
| US7831416B2 (en) * | 2007-07-17 | 2010-11-09 | Caterpillar Inc | Probabilistic modeling system for product design |
| US7788070B2 (en) * | 2007-07-30 | 2010-08-31 | Caterpillar Inc. | Product design optimization method and system |
| US7542879B2 (en) * | 2007-08-31 | 2009-06-02 | Caterpillar Inc. | Virtual sensor based control system and method |
| US7593804B2 (en) * | 2007-10-31 | 2009-09-22 | Caterpillar Inc. | Fixed-point virtual sensor control system and method |
| US8224468B2 (en) | 2007-11-02 | 2012-07-17 | Caterpillar Inc. | Calibration certificate for virtual sensor network (VSN) |
| US8036764B2 (en) | 2007-11-02 | 2011-10-11 | Caterpillar Inc. | Virtual sensor network (VSN) system and method |
| US8055887B2 (en) * | 2008-03-07 | 2011-11-08 | International Business Machines Corporation | Dynamically updating barcode data |
| US7904460B2 (en) * | 2008-04-23 | 2011-03-08 | Microsoft Corporation | Determining computer information from processor properties |
| US8707334B2 (en) * | 2008-05-20 | 2014-04-22 | Microsoft Corporation | Computer system event detection and targeted assistance |
| US20090293457A1 (en) * | 2008-05-30 | 2009-12-03 | Grichnik Anthony J | System and method for controlling NOx reactant supply |
| US8086640B2 (en) * | 2008-05-30 | 2011-12-27 | Caterpillar Inc. | System and method for improving data coverage in modeling systems |
| US8204969B2 (en) * | 2008-08-05 | 2012-06-19 | Canon Kabushiki Kaisha | Method for retrieving updates via the internet |
| US7917333B2 (en) * | 2008-08-20 | 2011-03-29 | Caterpillar Inc. | Virtual sensor network (VSN) based control system and method |
| US8612737B2 (en) * | 2008-09-04 | 2013-12-17 | Hewlett-Packard Development Company, L.P. | System and method for supporting multiple hardware platforms with a single disk image |
| EP2508991B1 (en) * | 2011-04-07 | 2016-01-06 | BlackBerry Limited | Device for distribution of content |
| WO2012159097A2 (en) * | 2011-05-18 | 2012-11-22 | Positioniq, Inc. | Reference object information system |
| US8793004B2 (en) | 2011-06-15 | 2014-07-29 | Caterpillar Inc. | Virtual sensor system and method for generating output parameters |
| US20130174042A1 (en) * | 2011-12-30 | 2013-07-04 | Samsung Electronics Co., Ltd. | Display apparatus, upgrading apparatus, display system and control method thereof |
| US8881136B2 (en) | 2012-03-13 | 2014-11-04 | International Business Machines Corporation | Identifying optimal upgrade scenarios in a networked computing environment |
| CN103971070A (en) * | 2013-01-24 | 2014-08-06 | 鸿富锦精密工业（深圳）有限公司 | System memory protecting method and device |
| USD728722S1 (en) | 2013-04-29 | 2015-05-05 | Ashbury International Group, Inc. | Forend for modular tactical firearms |
| USD728723S1 (en) | 2013-04-29 | 2015-05-05 | Ashbury International Group, Inc. | Forend for modular tactical firearms |
| DE102014016402B4 (en) * | 2014-11-05 | 2022-09-15 | Abb Schweiz Ag | Method and system for externally replacing or updating a device |
| KR102469758B1 (en) | 2015-09-02 | 2022-11-22 | 삼성전자주식회사 | Server apparatus, user terminal apparatus, contorl method thereof and electronic system |
| CN107315664A (en) * | 2016-04-26 | 2017-11-03 | 神讯电脑(昆山)有限公司 | Video card automatic checkout system and method |
| US10372434B1 (en) | 2016-07-22 | 2019-08-06 | Amdocs Development Limited | Apparatus, computer program, and method for communicating an update to a subset of devices |
| US10768948B2 (en) * | 2018-07-23 | 2020-09-08 | Dell Products, L.P. | Apparatus and method for dynamic modification of machine branding of information handling systems based on hardware inventory |
| US10891140B1 (en) * | 2018-09-27 | 2021-01-12 | Amazon Technologies, Inc. | Dynamic configuration management |
| US11455676B2 (en) * | 2019-05-03 | 2022-09-27 | EMC IP Holding Company LLC | Data-driven hardware configuration recommendation system based on user satisfaction rating |
| CN114995848B (en) * | 2021-12-08 | 2023-04-28 | 荣耀终端有限公司 | IoT device upgrade method, ioT device, and computer-readable storage medium |
Family Cites Families (64)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US3969723A (en) | 1974-07-03 | 1976-07-13 | General Electric Company | On-line modification of computer programs |
| US4558413A (en) | 1983-11-21 | 1985-12-10 | Xerox Corporation | Software version management system |
| US4714992A (en) | 1985-11-26 | 1987-12-22 | International Business Machines Corporation | Communication for version management in a distributed information service |
| GB8602964D0 (en) | 1986-02-06 | 1986-03-12 | Metaforth Computer Systems Ltd | Computer architecture |
| US5109484A (en) | 1986-04-09 | 1992-04-28 | International Business Machines Corporation | Self configuring terminal which polls loop network and generates list of connected devices for use in selectively downloading control programs |
| JP2535976B2 (en) | 1987-11-17 | 1996-09-18 | 株式会社日立製作所 | Form connection configuration automatic creation system |
| JPH06131478A (en) | 1992-10-16 | 1994-05-13 | Japan Radio Co Ltd | Multi-data-flow-processor device |
| US5870549A (en) | 1995-04-28 | 1999-02-09 | Bobo, Ii; Charles R. | Systems and methods for storing, delivering, and managing messages |
| US5787246A (en) | 1994-05-27 | 1998-07-28 | Microsoft Corporation | System for configuring devices for a computer system |
| US5530753A (en) | 1994-08-15 | 1996-06-25 | International Business Machines Corporation | Methods and apparatus for secure hardware configuration |
| US5586304A (en) * | 1994-09-08 | 1996-12-17 | Compaq Computer Corporation | Automatic computer upgrading |
| US5826102A (en) | 1994-12-22 | 1998-10-20 | Bell Atlantic Network Services, Inc. | Network arrangement for development delivery and presentation of multimedia applications using timelines to integrate multimedia objects and program objects |
| US6282712B1 (en) | 1995-03-10 | 2001-08-28 | Microsoft Corporation | Automatic software installation on heterogeneous networked computer systems |
| US5913040A (en) | 1995-08-22 | 1999-06-15 | Backweb Ltd. | Method and apparatus for transmitting and displaying information between a remote network and a local computer |
| US5845077A (en) | 1995-11-27 | 1998-12-01 | Microsoft Corporation | Method and system for identifying and obtaining computer software from a remote computer |
| KR100286008B1 (en) | 1995-12-30 | 2001-04-16 | 윤종용 | Method for automatically updating software program |
| US5665951A (en) | 1996-02-08 | 1997-09-09 | Newman; Gary H. | Customer indicia storage and utilization system |
| US5918211A (en) | 1996-05-30 | 1999-06-29 | Retail Multimedia Corporation | Method and apparatus for promoting products and influencing consumer purchasing decisions at the point-of-purchase |
| US6151643A (en) | 1996-06-07 | 2000-11-21 | Networks Associates, Inc. | Automatic updating of diverse software products on multiple client computer systems by downloading scanning application to client computer and generating software list on client computer |
| US5758071A (en) | 1996-07-12 | 1998-05-26 | Electronic Data Systems Corporation | Method and system for tracking the configuration of a computer coupled to a computer network |
| US5796633A (en) | 1996-07-12 | 1998-08-18 | Electronic Data Systems Corporation | Method and system for performance monitoring in computer networks |
| US6006034A (en) | 1996-09-05 | 1999-12-21 | Open Software Associates, Ltd. | Systems and methods for automatic application version upgrading and maintenance |
| US5948061A (en) | 1996-10-29 | 1999-09-07 | Double Click, Inc. | Method of delivery, targeting, and measuring advertising over networks |
| US6347398B1 (en) | 1996-12-12 | 2002-02-12 | Microsoft Corporation | Automatic software downloading from a computer network |
| US6018710A (en) | 1996-12-13 | 2000-01-25 | Siemens Corporate Research, Inc. | Web-based interactive radio environment: WIRE |
| WO1998035468A2 (en) | 1997-01-27 | 1998-08-13 | Benjamin Slotznick | System for delivering and displaying primary and secondary information |
| US6009409A (en) | 1997-04-02 | 1999-12-28 | Lucent Technologies, Inc. | System and method for scheduling and controlling delivery of advertising in a communications network |
| US6014698A (en) | 1997-05-19 | 2000-01-11 | Matchlogic, Inc. | System using first banner request that can not be blocked from reaching a server for accurately counting displays of banners on network terminals |
| US5948104A (en) | 1997-05-23 | 1999-09-07 | Neuromedical Systems, Inc. | System and method for automated anti-viral file update |
| US5999989A (en) * | 1997-06-17 | 1999-12-07 | Compaq Computer Corporation | Plug-and-play |
| US5864823A (en) | 1997-06-25 | 1999-01-26 | Virtel Corporation | Integrated virtual telecommunication system for E-commerce |
| US6009410A (en) | 1997-10-16 | 1999-12-28 | At&T Corporation | Method and system for presenting customized advertising to a user on the world wide web |
| US6170065B1 (en) | 1997-11-14 | 2001-01-02 | E-Parcel, Llc | Automatic system for dynamic diagnosis and repair of computer configurations |
| US6119165A (en) | 1997-11-17 | 2000-09-12 | Trend Micro, Inc. | Controlled distribution of application programs in a computer network |
| US6035423A (en) | 1997-12-31 | 2000-03-07 | Network Associates, Inc. | Method and system for providing automated updating and upgrading of antivirus applications using a computer network |
| US6202207B1 (en) | 1998-01-28 | 2001-03-13 | International Business Machines Corporation | Method and a mechanism for synchronized updating of interoperating software |
| US6052531A (en) | 1998-03-25 | 2000-04-18 | Symantec Corporation | Multi-tiered incremental software updating |
| US6101485A (en) | 1998-03-26 | 2000-08-08 | International Business Machines Corporation | Electronic solicitations for internet commerce |
| US6101486A (en) | 1998-04-20 | 2000-08-08 | Nortel Networks Corporation | System and method for retrieving customer information at a transaction center |
| EP0984338A1 (en) * | 1998-05-11 | 2000-03-08 | Xeikon Nv | Method of using an image forming apparatus |
| US6330715B1 (en) | 1998-05-19 | 2001-12-11 | Nortel Networks Limited | Method and apparatus for managing software in a network system |
| US6167407A (en) | 1998-06-03 | 2000-12-26 | Symantec Corporation | Backtracked incremental updating |
| US6338149B1 (en) | 1998-07-31 | 2002-01-08 | Westinghouse Electric Company Llc | Change monitoring system for a computer system |
| US6301612B1 (en) | 1998-08-12 | 2001-10-09 | Microsoft Corporation | Establishing one computer as a replacement for another computer |
| US6578198B2 (en) | 1998-08-13 | 2003-06-10 | Koninklijke Philips Electronics N.V. | Personal computer upgrade |
| US6405327B1 (en) | 1998-08-19 | 2002-06-11 | Unisys Corporation | Apparatus for and method of automatic monitoring of computer performance |
| US5995405A (en) * | 1998-10-27 | 1999-11-30 | Micron Technology, Inc. | Memory module with flexible serial presence detect configuration |
| US6195750B1 (en) | 1999-03-09 | 2001-02-27 | Amdhal Corporation | Method and apparatus for dynamic CPU reconfiguration in a system employing logical processors |
| US6469742B1 (en) | 1999-04-12 | 2002-10-22 | Koninklijke Philips Electronics N.V. | Consumer electronic devices with adaptable upgrade capability |
| US6377987B1 (en) | 1999-04-30 | 2002-04-23 | Cisco Technology, Inc. | Mechanism for determining actual physical topology of network based on gathered configuration information representing true neighboring devices |
| US6467088B1 (en) | 1999-06-30 | 2002-10-15 | Koninklijke Philips Electronics N.V. | Reconfiguration manager for controlling upgrades of electronic devices |
| US6636961B1 (en) | 1999-07-09 | 2003-10-21 | International Business Machines Corporation | System and method for configuring personal systems |
| US7251618B2 (en) * | 1999-10-18 | 2007-07-31 | Micron Technology, Inc. | Method and system for purchasing a memory upgrade for a computer system |
| US6230199B1 (en) | 1999-10-29 | 2001-05-08 | Mcafee.Com, Inc. | Active marketing based on client computer configurations |
| US6453347B1 (en) | 1999-10-29 | 2002-09-17 | Mcafee.Com, Inc. | Active marketing based on client computer configurations |
| US6529784B1 (en) * | 2000-02-29 | 2003-03-04 | Caldera Systems, Inc. | Method and apparatus for monitoring computer systems and alerting users of actual or potential system errors |
| US6633978B1 (en) * | 2000-03-31 | 2003-10-14 | Hewlett-Packard Development Company, L.P. | Method and apparatus for restoring computer resources |
| US7293268B2 (en) | 2000-04-17 | 2007-11-06 | Fujitsu Limited | Installation method, activation method, execution apparatus and medium of application program |
| JP2001337835A (en) | 2000-05-25 | 2001-12-07 | Hitachi Ltd | Method for renewing program of control program built-in device and control program built-in device |
| US20020004935A1 (en) | 2000-07-03 | 2002-01-10 | Huotari Allen Joseph | System for remote automated installation and configuration of digital subscriber line modems |
| JP2002073954A (en) * | 2000-08-24 | 2002-03-12 | Nec Corp | Sales promotion system and method for computer peripheral device |
| US6711738B1 (en) | 2000-11-27 | 2004-03-23 | Siemens Aktiengesellschaft | Method for replacing technologically aging sub-systems in a system |
| US7574492B2 (en) | 2002-09-12 | 2009-08-11 | Broadcom Corporation | Optimizing network configuration from established usage patterns of access points |
| US6711676B1 (en) | 2002-10-15 | 2004-03-23 | Zomaya Group, Inc. | System and method for providing computer upgrade information |
-
2002
- 2002-10-15 US US10/271,101 patent/US6711676B1/en not_active Expired - Lifetime
-
2003
- 2003-07-02 WO PCT/US2003/020756 patent/WO2004036445A1/en not_active Application Discontinuation
- 2003-07-02 CA CA002542786A patent/CA2542786A1/en not_active Abandoned
- 2003-07-02 AU AU2003301359A patent/AU2003301359A1/en not_active Abandoned
-
2004
- 2004-08-10 US US10/914,927 patent/US7117355B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| US20050010749A1 (en) | 2005-01-13 |
| US7117355B2 (en) | 2006-10-03 |
| AU2003301359A1 (en) | 2004-05-04 |
| WO2004036445A1 (en) | 2004-04-29 |
| US6711676B1 (en) | 2004-03-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7117355B2 (en) | System and method for providing computer upgrade information | |
| US7577948B2 (en) | System and method for providing computer upgrade information | |
| US9009698B2 (en) | System and method for providing computer upgrade information | |
| US7360211B2 (en) | System for automated generation of config to order software stacks | |
| US7698406B2 (en) | Method and apparatus for identifying and classifying network-based distributed applications | |
| US8332817B2 (en) | Certifying a software application based on identifying interface usage | |
| US6963908B1 (en) | System for transferring customized hardware and software settings from one computer to another computer to provide personalized operating environments | |
| US8799854B2 (en) | Reusing software development assets | |
| US8035490B2 (en) | Communication and filtering of events among peer controllers in the same spatial region of a sensor network | |
| US20100049838A1 (en) | Methods and systems for automatically registering new machines in a software provisioning environment | |
| US20070169116A1 (en) | Method and system for automated installation of system specific drivers | |
| US20090063563A1 (en) | Common configuration framework for applications to configure database objects and resources | |
| CN1987923B (en) | Method and the device of license activation is carried out for preloaded software | |
| WO2006099634A2 (en) | Software and hardware analysis test | |
| CN1964356A (en) | Method and system for data processing | |
| KR100872247B1 (en) | Method of using feature flags to determine compatibility between bios revisions and installed hardware during flash update | |
| US20050216519A1 (en) | Access point that monitors guest usage | |
| US20060112379A1 (en) | Method and system for on demand java resources | |
| JP2022100301A (en) | Method for determining potential impact on computing device by software upgrade, computer program, and update recommendation computer server (recommendation of stability of software upgrade) | |
| GB2442355A (en) | Dynamic loading of protocol adapters on a client | |
| US20040015499A1 (en) | System and method for transaction access control | |
| US20220171608A1 (en) | Intelligent provisioning management | |
| US9495367B2 (en) | System and method for performing a software comparison | |
| US20140131437A1 (en) | Automatic and Dynamic Information Handling System Personalization | |
| AU2003295528A1 (en) | Information handling system for custom image manufacture |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |