Remote lifecycle monitoring of electronic boards/software routines

[0002] This case is related to co-pending U.S. patent application Ser. No. 09/201,378 “Remote Assistant” by Lawrence P. Zale, assigned to the present assignee.

[0003] 1. Field of the Invention

[0004] The present invention related to identifying electronic boards/software routines configurations over time at a plurality of remote sites.

[0005] 2. Discussion of Prior Art

[0006] Many large, industrial machines such as steam turbines, generators, locomotives, ships, oil refineries, iron mills, stamping mills, factory tools are either impossible or impractical to bring into a shop for in-house measurements. These remote sites are now connected to a base by a remote link. Measurements and other data may be transmitted via the remote link between the remote site and the base.

[0007] This remote link may be hardwired, such as an dedicated phone line, Internet connection, or may be by a radio link. The remote link is typically used to perform remote diagnostics of the equipment.

[0008] Typically the remote link is used to identify a current configuration, and inventory of the types of boards in a device to provide accurate service advice. Each machine may use many different types of boards and software, and certain types may not be compatible.

[0009] Patents, Copyrights and Trademarks may cover certain electronic boards and software routines (‘protected property’). These may be licensed (by a Licensor) to a customer (Licensee) for a specified period of time, area of use, or conditions of use. Conditions of use may be contrary to a warranty and is important for the licensee to know. It is very difficult to discern if the protected inventions are being implemented according to their prescribed use. If is very difficult to try to discern their use since many are typically, on-site devices, and inaccessible. It may also be embarrassing to check up on customers, who are actually using the products according to the license.

[0010] Currently, there is the need for a system that automatically determines unauthorized boards and routines residing in a machine at a remote site, and also aids in determining the life cycle of boards and routines.

[0011] A remote inventory system monitors electronic boards/software routines in a machine situated at a remote site. The boards/routines are marked with a unique serial number that is machine-readable. A monitor program operates at the remote site to collect the serial numbers and other corresponding information and send this information to a base site.

[0012] The base is connected to the remote site through a remote link.

[0013] A processor located in the base runs a base program which looks up the serial numbers in a database and indicates remote sites which are using protected property that they are not authorized to use. The base program also may create a report of length of use of each board/routine and performance history of a specified board/routine over time. By entering information of the date, location and vendor a board/routine is sold to, allows the base to create a report of vendor activity.

[0014] It is an object of the present invention to provide a remote means of determining presence of protected property in a remote machine.

[0015] It is another object of the present invention to provide a means of remotely determining the performance history of boards/routines implemented over a period of time.

[0016] It is another object of the present invention to track the location of the boards/routines over a period of time.

[0017] Is another object of the present invention to identify boards/routines having a larger than acceptable number of errors in a predetermined time period.

[0018] While the novel features of the invention are set forth with particulars in the appended claims, the invention, both as to organization and content, will be better understood and appreciated, along with other objects and features thereof, from the following detailed description taken in conjunction with the drawings, in which:

[0019] FIG. 1 is one embodiment of the present invention monitoring boards/routines of several remote sites.

[0020] As discussed above, it is difficult to enter a remote site to determine the hardware and software configuration of complex machines. If one were to enter the site, many of the boards/routines are inside the machines. Even if one were to extract the boards/routines it would be difficult to tell two boards of the same type apart without the presence of optical bar codes.

[0021] Apart from identifying the types of electronics boards and/or versions of software programs used, as was the case and the prior art, only the types of boards/routines and their version numbers were identified for diagnostic purposes.

[0022] Unlike the prior art, it is now necessary to identify the exact board/routine for tracking the location, performance/maintenance/upgrade history, and presence of ‘protected property’ of a specific board/routine.

[0023] With the advent of Remote Service and Diagnostics, a whole world of automated possibilities for Intellectual Property (IP) tracking and enforcement opens. By marking each electronic board with a unique serial number, such as by burning it in a programmable read only memory (PROM), or ROM, each may be uniquely identified.

[0024] Each software routine in each software package, is uniquely identified by a machine readable unique serial number in the program object code or data section. This serial number will appear in a PROM, ROM location of a board. These will not be easy to discern to those not familiar with it. They would appear to be obscure words determined to be part of the required executable code, or a hardware status word.

[0025] The serial number can be encoded with information such as when and where it was created, hardware/software version, and patents or trade secrets which covers the device. This information may also be linked to the serial number had some locations such as the database at the base.

[0026] Auto Downloading

[0027] During system remote maintenance connections, this serial number is downloaded to a main location. Downloading has become common with the advent of Internet broadcasting “push” software, and Java applets which can automatically contact another site and send specified information, without requiring the operators of the remote equipment to initiate the download, and in many cases, the operators are unaware of the download.

[0028] The download of serial numbers may also occur upon request from the base. This is standard “pull” technology.

[0029] Remote Maintenance

[0030] The program running at the base receives the serial numbers and processes them. The base program has access to a database with a history of serial numbers for that site, the types of board/routine pertaining to each serial number, a performance history for that serial number, a list of locations the serial number has been, information about the original purchaser of the board/routine, date/location of purchase, a list of authorized users, and other pertinent information. From this information the base program may perform many different functions.

[0031] Change in Configuration

[0032] The serial numbers may be compared to previous inventory of serial numbers of boards/software for this device. By determining which boards/software have changed, and comparing it to previous stored configuration for this site, one can determine what has been modified. By also examining the performance of the boards, one may discern of the change improved or hurt performance.

[0033] Service Contracts

[0034] By tracking the serial number of the newly added boards software, and comparing these to the original serial number inventory, one may discern if the boards/software were modified, possibly invalidating the service contract, or warranties.

[0035] Software Use Licenses

[0036] By periodically downloading the serial numbers for the device, a determination of which software/boards are being used during given time periods may be determined. Licenses that are keyed upon the number of uses are now feasible. This may also be used as evidence to show use when use is denied. It may be a powerful tool since this information may periodically be provided to a main base.

[0037] Monitoring Competitors

[0038] A sales log may be maintained which keeps track of sales of boards/software, their serial numbers, date of sale, parties sold to, their locations, etc. A comparison of the sales log with the current serial numbers of a machine may be used to determine service competitor patterns of where, how much work is being done, when it was done, and in what geographic areas it was done. This will provide a map of occurrences of competitors servicing these machines.

[0039] Imprinting

[0040] A check for multiple or duplicate serial numbers from different sites should indicate “black market” knock-offs” or counterfeited boards/software. Since, as described above, the serial number each serial number is unique, boards/routines that a copied, will have the same serial number. As stated above, if the the serial numbers are not discernable to those who are unaware of them, they may assumed to be part of the required executable code, or hardware status words and copied wholesale by counterfeiters. Therefore, one copying the board/software will copy literally to retain functionality, and result in an exact copy with a duplicate serial number. A quick check as to the authorized party by the base program will result in the authorized Licensee, with the duplicate site having unauthorized copies. This should aid in licensing/infringement matters.

[0041] Identification of Boards/Routines

[0042] A serial number is stored in the ROM or within a software routine allows a monitor program at the remote site periodically read the serial number at the remote site and report it to a main base. The monitor routine may also send a stored datablock which has a performance log. Serial numbers may be easily appended to software, and data, even if they are “off-the-shelf”. For example, several words may be appended to a conventional program, with a new “end-of-file” marker added, and a new checksum or parity word calculated on the extended file.

[0043] This would operate in the same manner by replacing a ROM, with another having the embedded serial number.

[0044] Therefore, for ‘off-the-shelf” hardware, a ROM chip may to be removed, the code downloaded to a disk. The code is then has the additional words appended, an end of file marker is added, and a new checksum calculated. This extended code is then burned into a blank ROM chip and then used to replace the original ROM.

[0045] The monitor program knows the predetermined locations of the serial words in each board/routine, reads them and sends them across the remote link to the base for analysis. That monitor program may initiate this process by itself based upon some internal trigger event, such as an internal clock reaching a specified date/time, or may be triggered by a request from the base.

[0046] Reporting routine could also be set up on a schedule to “wake up” at a certain time, read serial numbers, then report to the GE main base.

[0047] In FIG. 1, a simplified block diagram of the present invention is shown. At least one remote site 40, 50, 60 is shown connected to a main base 20. Each remote site is connected to base 20 with a remote link 100 which may be either hard wired, a radio link, or a combination of the two.

[0048] A complex machine 10 is situated at remote site 40 has at least one electronic board 13 and/or software routine desired to be monitored.

[0049] Board 13 has a means 15 for storing a unique, machine-readable serial number. This may be in the form of dedicated electronic circuitry, a ROM, EPROM, or PROM.

[0050] For software routines, a unique serial number is embedded in the software routine and is stored on a storage device 53 such as a hard disk. The microprocessor 51 at remote site 40 reads the routine and the serial number.

[0051] A monitor program is accessible by microprocessor 51. This monitor program may be fed to the remote site 40 from base 20, be prestored on disk 53, ROM 21, or RAM 19 of remote site 40.

[0052] The monitor program may “wake-up” on its own, triggered by an internal clock at remote site 40, or be triggered by a request from a microprocessor 31 in base 20.

[0053] The monitor program takes an inventory of machine 10 and provides the required information over remote link 100 to base 20.

[0054] Microprocessor 31 of base 20 runs a base program which may be stored in a storage device 33, ROM 32, or RAM 25.

[0055] The base program may perform a number of functions as set forth above some of which require a database for storage of current information and retrieval of past information for a given site or serial number. This database is stored in storage device 33.

[0056] Base program being run by microprocessor 31 may interact with a base user 2 through an input device 21 and provides its output to monitor 29. Therefore the current boards/routines in a given site may be displayed. The past history or performance of a specific board/routine may be displayed.

[0057] An indication of the locations the board 13/routine has been, where it was purchased, and the group that purchased the board/routine may also be displayed.

[0058] Base program running on microprocessor 31 may create map of activity of third party service organizations by identifying boards/routines which where sold to a specified group and tracking the location of these boards/routines over time.

[0059] While specific embodiments of the invention have been illustrated and described herein, it is realized that modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit and scope of the invention.