Source: http://www.google.com/patents/US20060100972?dq=6,460,050
Timestamp: 2016-10-28 03:06:49
Document Index: 412862154

Matched Legal Cases: ['arts 26', 'arts 26', 'art 26', 'art 28', 'art 26', 'arts 26', 'art 26', 'arts 26', 'art 26']

Patent US20060100972 - Automated software-based hardware tracking system - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA hardware tracking system includes memory storage devices on tracked parts containing unique serial numbers, part numbers, revision numbers, and firmware versions. At power up and after a reset, a host computer or real-time subsystem downloads this information and compares it to the information stored...http://www.google.com/patents/US20060100972?utm_source=gb-gplus-sharePatent US20060100972 - Automated software-based hardware tracking systemAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20060100972 A1Publication typeApplicationApplication numberUS 10/904,001Publication dateMay 11, 2006Filing dateOct 19, 2004Priority dateOct 19, 2004Publication number10904001, 904001, US 2006/0100972 A1, US 2006/100972 A1, US 20060100972 A1, US 20060100972A1, US 2006100972 A1, US 2006100972A1, US-A1-20060100972, US-A1-2006100972, US2006/0100972A1, US2006/100972A1, US20060100972 A1, US20060100972A1, US2006100972 A1, US2006100972A1InventorsJoseph Chianese, William Peterson, Erik Peterson, Philip BylsmaOriginal AssigneeGe Medical Systems Technology LlcExport CitationBiBTeX, EndNote, RefManPatent Citations (9), Referenced by (29), Classifications (6), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetAutomated software-based hardware tracking system
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT [0019] The present invention is illustrated with respect to a hardware tracking system 10, particularly suited for Magnetic Resonance machines. The present invention is, however, applicable to various other uses that may require hardware tracking, as will be understood by one skilled in the art. [0020] Referring to FIG. 1, a hardware tracking system 10, including a host computer 12, is illustrated. The host computer 12 includes a host process unit 14, a logger 16, a parser 18, and a viewer 20. Coupled to the host computer 12 are: a central database 22 and a service browser 24 and remote computer 23. [0021] Generally, the host computer 12 or real-time subsystem downloads information from a plurality of parts 26, 28 having individual memory storage devices 30, 32 and compares this with information stored in the central database 22. A user accesses the information in the central database 22 through the viewer 20 and parser 18 from the service browser 24. [0022] The host computer 12 downloads part information during, for example, power up and after reset. Information downloaded includes, but is not limited to, location, firmware revision, serial number, part number, and hardware revision. The host computer 12 includes a host process receiver 14 that downloads the aforementioned information. The logger 16 receives signals from the host process receiver 14 and generates a logger 16 signal therefrom to log the received information. The logger 16 automatically updates when new parts are added and when the part location is unique. The logger 16 signal is received in the central database 22. The parser 18 parses information in the central database 22 and generates a parser 18 signal for the individual pieces of information. The viewer 20 receives the parser 18 signals and generates viewer 20 signals, which are received in remote computers through service browsers 24. [0023] The parts 26, 28, illustrated as a first part 26 and a second part 28, are representative of a plurality of parts that are tracked by the present invention. Each part 26, 28 includes a memory storage device 30, 32 including such programmed information as location, firmware revision, serial number, part number, and hardware revision information. The embodied parts 26, 28 are circuit boards included in Magnetic resonance systems (MR), however, the present invention is applicable to any system including interchangeable parts, as will be understood by one skilled in the art. [0024] The central database 22 is embodied as a separate unit to the host computer 12; however, alternate embodiments include the central database 22 as a component of the host computer 12, as will be understood by one skilled in the art. The central database 22 receives the logger 16 signals and stores the log files contained therein. Each log file ideally includes date and time information for each part. The central database 22 shares information with the parser 18 and viewer 20 such that user input and comments can be added to each log file, as will be discussed later. [0025] The service browser 24 and remote computer 23 is embodied as a typical computer downloading information through the World-Wide-Web from the viewer 20. The host computer 12 is accessible to the remote computer 23 via the web service browser 24 or by retrieving the database records via file transfers protocol (FTP) from storage in the central database 22. [0026] Referring to FIG. 2, a logic flow 38 diagram of the logger 16 operations of the hardware tracking system 10, in accordance with another embodiment of the present invention, is illustrated. Logic starts in operation block 40 when a host process sends a hardware change message to the host computer 12 for logging. [0027] In operation block 42, one or more hardware specific software or host process 14 logs a message, and a logging Application Program Interface within the logger 16 activates. In other words, the logger receives a first unit of configuration information, such as a part serial number. [0028] In inquiry block 44, a check is made whether the current status file is present. The current status file is the section of a log file in the central database 22 having current part information, whereas a history file is a section of a log file including part change history information. Either the current status file or the history file is a second unit of configuration information to which the first unit of configuration information is compared. [0029] For a negative response, in operation block 46, when a log file is not present during message logging, e.g. the first time the logger 16 is called in a new remote computer 23; the logger 16 generates a new log file (either a current status file or a history file). The logger 16 then initializes the newly created log file by writing header information, and, in operation block 48, logs the message to the current status file. Otherwise, in operation block 48 the logger 16 logs the message to the current status file without generating a new current status file. [0030] In inquiry block 50, the logger 16 detects changes to the hardware configuration with reference to the contents of the current status file and an inquiry is made whether the current event is a history triggering event. For a positive response, if there is any change in the hardware configuration, the logger 16 appends a new hardware change message to the history file in operation block 52. The logger 16 also provides a file locking mechanism to sync with the system 10, thereby preventing multiple processes writing to the same log file simultaneously. [0031] Referring to FIG. 3, a logic flow diagram 58 of viewer 20 and parser 18 operations of a hardware tracking system 10, in accordance with another aspect of the present invention, is illustrated. Logic starts in operation block 60 where a service browser 24 is used to gather information from the central database 22 or host computer 12. The viewer 20 is invoked through a component, e.g. a button, from the service browser 24. [0032] In operation block 62, the viewer 20 is invoked through activation of component, e.g. a button, from the service browser 24. The viewer 20 displays an appropriate error message if the required log file is not present in the system 10. [0033] In inquiry block 64, a check is made whether the required software is present. For a negative response, in operation block 66, the viewer 20 displays an appropriate error message if the required log file is found to be corrupt. [0034] Otherwise, in inquiry block 68, a check is made whether the service key is present. For a negative response, a check is made in inquiry block 70 whether the user is a remote user from OCL. The viewer 20 provides the necessary searching capabilities based on, for example, board type and date range. The viewer 20 addends comments to specific entries through the service browser 24. For a negative response in operation block 66, the viewer 20 displays an appropriate error message. [0035] For a positive response to either blocks 68 or 70, in operation block 72, parser 18 operations activate. In other words, when a user views a log file, the viewer 20 invokes the parser 18 routines to read the contents from the corresponding log file. [0036] In inquiry block 74, a check is made whether the required log file is absent or corrupt. For a positive response in operation block 66, the parser 18 returns an appropriate error condition signal to the viewer 20 when a log file is not found or found to be corrupt. The parser 18 logs a message to the central database 22 if a log file is found to be corrupt. The log file is backed up and the logger 16 initializes a fresh log file. The parser 18 parses a log file into a header and individual log messages, which in turn will be used by the viewer 20. Otherwise, in operation block 76, the log file is displayed on the viewer 20 or the remote computer 24. [0037] In operation block 66, the viewer 20 displays an appropriate error message if the required log file is not present in the system 10. The viewer 20 displays an appropriate error message if the required log file is found to be corrupt. The viewer 20 displays the contents of a log file if it is correctly parsed. [0038] When a log file grows to a predetermined maximum size, a back-up file is generated. Any existing back-up is over-written. After the back-up for a log file is generated, a fresh log file is initiated. The log files are maintained in encrypted form in the system 10. [0039] One example of a possible sequence for user interfacing includes: a user at a remote computer 23 connects to the host computer 12 through the service browser 24. The service browser 24 includes a user interface (UI), e.g. a button, to view the log files in a browser page. The service browser 24 displays the common service desktop of the host computer 12. The user chooses (e.g. presses the button) to view the error log files, and a current status log is displayed on a service browser window. The web server interface (service browser 24) executes the industry standard Common Gateway Interfaces (CGIs) and Hyper Text Markup Language (HTML) to display dynamic screens. Information is displayed on the remote computer 23 in two forms: present configuration and configuration history. Information is also displayed on any additional computer or remote server that supports a web browser (UNIX, Microsoft Windows, etc.). The system 10 handles an unlimited number of variations in configuration. Additional hardware is added or removed from the system 10 without requiring maintenance on the central database 22 or user interface. [0040] Access to the central database 22 is via the world-wide-web (WWW), making the host computer 12 remotely accessible. Information is displayed in two forms. The first form is an HTML page containing the present configuration data. This information is used to determine what hardware is present and the revisions of hardware installed. [0041] The second form of displayed information is a history HTML page. The history page contains one line for each change detected for any given part. Comments are added to each line giving a detailed record of why the replacement occurred and any miscellaneous information needed for future reference. [0042] In operation, the system 10 requires that all tracked parts include a memory storage device 30, 32 containing a unique serial number, part number, revision number, and firmware version for the part. At power up and after a reset, the host computer 12 or real-time subsystem downloads this information and compares it to the information stored in a central database 22. Changes in data indicate a replacement or update of the part 26, 28, which is then used to automatically update the central database 22. Each change causes creation of a new record along with appended date and time information. These records are scanned to determine the evolution of the MR system and MR parts 26, 28. They are also compared with the error log and diagnostic history information to generate a cause and effect of what transpired during troubleshooting. This information is crucial in determining the number of false positives and negatives associated with a diagnostic MR test. In addition, the system 10 tracks the number of times a board or part 26, 28 is removed and re-inserted, indicating the field engineer is shot-gunning the MR system. This is automatically recorded to provide information on problem MR systems where this type of inefficient trouble-shooting is occurring. [0043] While the invention has been described in connection with one or more embodiments, it should be understood that the invention is not limited to those embodiments. On the contrary, the invention is intended to cover all alternatives, modifications, and equivalents, as may be included within the spirit and scope of the appended claims. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6039430 *Sep 3, 1998Mar 21, 2000Hewlett-Packard CompanyMethod and apparatus for storing and retrieving information on a replaceable printing componentUS6240169 *May 6, 1999May 29, 2001Mediacom Telesystems, Inc.Communications protocol for least cost call routing systemUS6282175 *Apr 23, 1998Aug 28, 2001Hewlett-Packard CompanyMethod for tracking configuration changes in networks of computer systems through historical monitoring of configuration status of devices on the network.US7003434 *Sep 24, 2003Feb 21, 2006Jean-Patrick AzpitarteElectronic maintenance record file system for equipment such as a elevatorsUS20020107837 *Feb 23, 1999Aug 8, 2002Brian OsborneMethod and apparatus for logically reconstructing incomplete records in a database using a transaction logUS20020198997 *Jun 20, 2001Dec 26, 2002Linthicum Steven EricSystem and method for on board maintenance instructions and recordsUS20030158703 *May 16, 2001Aug 21, 2003Lumme Veli ErkkiMethod in monitoring the condition of machinesUS20030209601 *Apr 7, 2003Nov 13, 2003Chung Kevin Kwong-TaiArticle tracking system and methodUS20030237022 *Jun 21, 2002Dec 25, 2003Thayer Jennifer J.System and mehod for providing a service log for processor-based devices* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7698545 *Apr 24, 2006Apr 13, 2010Hewlett-Packard Development Company, L.P.Computer configuration chronology generatorUS7805675 *May 19, 2006Sep 28, 2010International Business Machines CorporationMethods, systems, and computer program products for recreating events occurring within a web applicationUS7870441 *Mar 18, 2008Jan 11, 2011International Business Machines CorporationDetermining an underlying cause for errors detected in a data processing systemUS7937370Feb 21, 2007May 3, 2011Axeda CorporationRetrieving data from a serverUS7966418Feb 20, 2004Jun 21, 2011Axeda CorporationEstablishing a virtual tunnel between two computer programsUS7992044 *Dec 5, 2008Aug 2, 2011Oracle America, Inc.Method and system for platform independent fault managementUS8055758Aug 14, 2006Nov 8, 2011Axeda CorporationReporting the state of an apparatus to a remote computerUS8060886Feb 12, 2007Nov 15, 2011Axeda CorporationXML scripting of SOAP commandsUS8065397Dec 26, 2006Nov 22, 2011Axeda Acquisition CorporationManaging configurations of distributed devicesUS8108543Apr 17, 2002Jan 31, 2012Axeda CorporationRetrieving data from a serverUS8271454Dec 18, 2007Sep 18, 2012Microsoft CorporationCircular log amnesia detectionUS8291039May 11, 2011Oct 16, 2012Axeda CorporationEstablishing a virtual tunnel between two computer programsUS8370479Oct 3, 2006Feb 5, 2013Axeda Acquisition CorporationSystem and method for dynamically grouping devices based on present device conditionsUS8406119Sep 29, 2006Mar 26, 2013Axeda Acquisition CorporationAdaptive device-initiated pollingUS8478861Jul 6, 2007Jul 2, 2013Axeda Acquisition Corp.Managing distributed devices with limited connectivityUS8752074Oct 4, 2011Jun 10, 2014Axeda CorporationScripting of soap commandsUS8762497Dec 19, 2011Jun 24, 2014Axeda CorporationRetrieving data from a serverUS8769095Dec 26, 2012Jul 1, 2014Axeda Acquisition Corp.System and method for dynamically grouping devices based on present device conditionsUS8788632Oct 4, 2011Jul 22, 2014Axeda Acquisition Corp.Managing configurations of distributed devicesUS8898294Oct 3, 2011Nov 25, 2014Axeda CorporationReporting the state of an apparatus to a remote computerUS9002980Sep 13, 2012Apr 7, 2015Axeda CorporationEstablishing a virtual tunnel between two computer programsUS9170902Feb 20, 2013Oct 27, 2015Ptc Inc.Adaptive device-initiated pollingUS9213328 *Jul 31, 2012Dec 15, 2015Hong Fu Jin Precision Industry (Shenzhen) Co., Ltd.Computing device and method for detecting defective hardware of image measurement machineUS20070271273 *May 19, 2006Nov 22, 2007International Business Machines CorporationMethods, systems, and computer program products for recreating events occurring within a web applicationUS20080195750 *Feb 9, 2007Aug 14, 2008Microsoft CorporationSecure cross platform auditingUS20090157767 *Dec 18, 2007Jun 18, 2009Microsoft CorporationCircular log amnesia detectionUS20090240990 *Mar 18, 2008Sep 24, 2009International Business Machines CorporationDetermining an underlying cause for errors detected in a data processing systemUS20100146342 *Dec 5, 2008Jun 10, 2010Sun Microsystems, Inc.Method and system for platform independent fault managementUS20130158930 *Jul 31, 2012Jun 20, 2013Hon Hai Precision Industry Co., Ltd.Computing device and method for detecting defective hardware of image measurement machine* Cited by examinerClassifications U.S. Classification1/1, 714/E11.207, 707/999.001International ClassificationG06F17/30Cooperative ClassificationG06Q10/087European ClassificationG06Q10/087Legal EventsDateCodeEventDescriptionOct 19, 2004ASAssignmentOwner name: GE MEDICAL SYSTEMS TECHNOLOGY, LLC, WISCONSINFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHIANESE, JOSEPH;PETERSON, WILLIAM;PETERSON, ERIK;AND OTHERS;REEL/FRAME:015267/0233;SIGNING DATES FROM 20030423 TO 20030505RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services