Data processing: software development – installation – and managem – Software program development tool – Translation of code
Reexamination Certificate
1997-10-27
2001-03-20
Lintz, Paul R. (Department: 2762)
Data processing: software development, installation, and managem
Software program development tool
Translation of code
C717S152000, C707S793000
Reexamination Certificate
active
06205579
ABSTRACT:
BACKGROUND OF THE INVENTION
The present invention relates to a method for providing software technical support from a remote location via, for example, the Internet. More specifically, the present invention provides a method by which software upgrades and fixes for software bugs may be incorporated into a customer's software from the remote location.
Once a software producing company has sold a software product to its customer, it is extremely important to keep track of these customers and to update the software periodically. No software program is ever bug free; in fact, the software industry is quite accustomed to re-releasing newer versions of software programs on a periodic basis in order to correct errors in the software. These later releases may add new features to the software, may correct minor problems, or often correct critical errors in the software. Because the performance of a software program is important for customers, it is in a software company's best interest to release these later versions of software to its customers and to insure that the newer software versions are received and installed correctly.
However, numerous obstacles are present that thwart even the best efforts of a conscientious software company to periodically update its software products with newer versions for all of its customers. One problem is that few customers who buy a software program go through the formalities of registering the program and sending the registration back to the software company. A registration form allows a software company to keep track of purchasers of its software, their addresses, contact persons, the version purchased, etc. However, few such software registration forms are received by software vendors. This makes it extremely difficult for a software company to determine to whom regular updates should be sent. For those software companies that update software regularly (such as quarterly) or may need to correct critical software bugs, this lack of software registration presents a real problem. And even if a registration form has been received, it is often difficult to figure out exactly to whom the new software version should be directed. Individuals change roles within an organization, organizations merge, engineers leave, etc., all making it extremely difficult to figure out to whom within an organization a new software version should be sent. It is also important that new versions of software be sent to a responsible person within the organization to ensure that all computers running the software are updated with the new version, and that the installation is done correctly. However, even with such competent individuals, errors in installation.
Another problem with releasing new versions of software to customers is the problem of distribution. In order to release a new version of the software, the vendor must purchase floppy or compact disks to hold the software, copy the software onto the disks, label the disks, determine who the appropriate customers and contacts are, and label and mail these disks to the correct individual. But as mentioned above, even if these disks containing the latest software version arrive at the correct location, there is no guarantee that the software will be installed correctly. Any problems encountered with the software, either due to bugs or incorrect installation will undoubtedly be blamed upon the software company that has sold the software program.
It is clearly in the best interests of a software company to ensure that updated versions of its software are timely received by the correct individuals within one of its customers, and correctly installed.
Another problem encountered by software companies is the identification and correction of software bugs encountered by customers in the course of using their software.
Typically, a customer receiving an error message while using software will call the software company and relate the circumstances surrounding the problem. Such a user may be able to relate generally what he was doing at the time, describe the problem that occurred, and report any error ID number that was produced. However, it is rare that specific details involving computer configuration, other programs running, and the status of internal variables are reported. Essentially, the problem is that the customer is in a location isolated from the software company when the problem occurs and has no means of transferring a “snapshot” of his system at the time the error occurs.
Of course, if the customer discontinues use of the software, ignores the problem, or otherwise chooses not to contact the software company with news of the error, the software company is put at a disadvantage. In these situations, because the vendor does not hear about the occurrence of the problem, it is not given the opportunity to correct it. Because errors in software can be extremely complex and subtle, it is very important for a software company to know exactly the circumstances under which the problem occurred in order to be able to reproduce the problem and to solve it. For customers using the software at a remote location on a remote computer, it is unlikely and extremely difficult that a customer will be able to transfer all of the information concerning such a problem back to the software company.
It is therefore desirable that a technique be provided by which a software vendor can track customers, upgrade customer software with newer versions, and correct software bugs from remote locations.
SUMMARY OF THE INVENTION
According to the present invention, techniques are provided by which a software vendor may provide software technical support to its customers from a remote location via the Internet. When the end user begins operating the vendor's software, dialog boxes give the user the opportunity to register the software with the vendor. If the user decides to register the software, a connection between the user's platform and the vendor is established via the Internet to effect registration. Moreover, each time thereafter that the user begins operating the software, an Internet connection to the vendor is established for the purpose of determining whether a software upgrade is necessary. Version data for each of the software's modules as well as any critical bug data known by the vendor are downloaded to the user's platform for comparison to the user's current version of the software. Where the downloaded version data agree with the user's module versions, and where there are no known bugs, the user's software remains unchanged. However, if the comparison reveals that one or more of the user's software modules are outdated or infected with a critical bug, dialog boxes are presented to the user for each such module requesting whether an upgrade is desired. A list is maintained of the modules for which an upgrade is requested. When all of the modules have been checked in this manner, the latest version of the modules in the upgrade list are downloaded from the vendor and written over the corresponding outdated modules on the user's platform.
According to another embodiment of the invention, a method is provided by which a vendor may effectively troubleshoot errors in the operation of its software from a remote location via the Internet. When a user encounters an error in the operation of the vendor's software, operation of the software is suspended and an Internet connection to the vendor is established by which the error is reported and known critical bug data are downloaded to the user's platform. The critical bug data are compared to the state of the user's software to determine whether the error corresponds to any known bugs previously documented by the vendor. Where the error corresponds to a known bug, the user is given the option, e.g., via a dialog box, to download a software fix from the vendor. This may be, for example, a replacement module to overwrite the module with the bug. Where, however, the error does not correspond to any known bug, software on the vend
Altera Corporation
Beyer Weaver & Thomas LLP
Khatri Anil
Lintz Paul R.
LandOfFree
Method for providing remote software technical support does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method for providing remote software technical support, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method for providing remote software technical support will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2438941