ELECTRONIC COMPONENT HAVING REDUNDANT PRODUCT DATA STORED EXTERNALLY

Abstract

Embodiments include methods for redundantly storing product data for an electronic component on an external device. Aspects include determining that product data stored in a primary storage device is corrupted and determining whether the product data is available on the external device that is in communication with the electronic component. Based on a determination that the product data stored in the primary storage device is corrupted and that the product data is available on the external device, aspects include obtaining product data from the external device to continue operation of the electronic component.

Description

DOMESTIC PRIORITY

This application is a continuation application of the legally related U.S. Ser. No. 14/833,158 filed Aug. 24, 2015, the contents of which are incorporated by reference herein in their entirety.

BACKGROUND

The present disclosure relates to computer system maintenance and more specifically, to methods, systems and computer program products for redundantly storing product data for electronic components on an external device.

Computer systems are composed of many components, namely, circuit boards or parts that can be easily removed from the computer system and replaced, even by someone lacking in-depth product knowledge of the computer system. These components typically include one or more of power supply units, motherboards, socketed microprocessors, primary storage modules (e.g., Random Access Memories, or RAMs), secondary storage devices (e.g., hard drives and optical drives), video cards, sound cards, and peripherals such as keyboards, mice and printers.

Many of these components have Vital Product Data (VPD) stored thereon that is used during the setup or configuration of the computer system. The VPD is a collection of configuration and informational data associated with a particular set of hardware (e.g., a component), to allow for the component to be administered at a system or network level. VPD may include product model numbers, unique serial numbers, product release levels, maintenance levels, and other information specific to the hardware, as well as user-defined information, such as the building and department location of the hardware.

Currently, if the VPD of a component is corrupted, the component cannot be used even if the physical hardware of the component is functioning properly. In addition, since the VPD is not replaceable, users need to buy a new component if the VPD becomes corrupted. While existing mechanisms to protect VPD are available, most require the addition of redundant hardware to the component that increases the cost of the component.

SUMMARY

In accordance with an embodiment, a method for redundantly storing product data for an electronic component on an external device is provided. The method includes determining that product data stored in a primary storage device is corrupted and determining whether the product data is available on the external device that is in communication with the electronic component. Based on a determination that the product data stored in the primary storage device is corrupted and that the product data is available on the external device, the method also includes obtaining product data from the external device to continue operation of the electronic component.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The forgoing and other features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

FIG. 1 is a block diagram illustrating one example of a processing system for practice of the teachings herein;

FIG. 2 is a block diagram illustrating a system for redundantly storing product data for an electronic component on an external device in accordance with an exemplary embodiment;

FIG. 3 is a flow diagram of a method for redundantly storing product data for an electronic component on an external device in accordance with an exemplary embodiment; and

FIG. 4 is a flow diagram of another method for redundantly storing product data for an electronic component on an external device in accordance with an exemplary embodiment.

DETAILED DESCRIPTION

In accordance with exemplary embodiments of the disclosure, methods, systems and computer program products for redundantly storing product data for an electronic component on an external device are provided. In exemplary embodiments, a primary copy of the product data is stored in a primary storage device disposed on the electronic component. As used herein the term product data includes VPD and/or first failure data capture (FFDC). The product data is typically stored on a non-volatile memory of the electronic component, such as electrically erasable read-only memory (EEROM). In exemplary embodiments, the product data is also stored on an external device that is configured to communicate, either via a wired or wireless communications channel, with the electronic component. In exemplary embodiments, upon determining that the product data stored on the primary storage device is corrupt, the electronic component can access the product data stored on the external device to allow the continued use of the electronic component. Having a secondary source to access product data allows for the use of an electronic component with corrupt product data in the primary storage device until the product data in the primary storage device can be repaired.

Referring to FIG. 1, there is shown an embodiment of a processing system 100 for implementing the teachings herein. In this embodiment, the system 100 has one or more central processing units (processors) 101a, 101b, 101c, etc. (collectively or generically referred to as processor(s) 101). In one embodiment, each processor 101 may include a reduced instruction set computer (RISC) microprocessor. Processors 101 are coupled to system memory 114 and various other components via a system bus 113. Read only memory (ROM) 102 is coupled to the system bus 113 and may include a basic input/output system (BIOS), which controls certain basic functions of system 100.

FIG. 1 further depicts an input/output (I/O) adapter 107 and a network adapter 106 coupled to the system bus 113. I/O adapter 107 may be a small computer system interface (SCSI) adapter that communicates with a hard disk 103 and/or tape storage drive 105 or any other similar component. I/O adapter 107, hard disk 103, and tape storage device 105 are collectively referred to herein as mass storage 104. Operating system 120 for execution on the processing system 100 may be stored in mass storage 104. A network adapter 106 interconnects bus 113 with an outside network 116 enabling data processing system 100 to communicate with other such systems. A screen (e.g., a display monitor) 115 is connected to system bus 113 by display adaptor 112, which may include a graphics adapter to improve the performance of graphics intensive applications and a video controller. In one embodiment, adapters 107, 106, and 112 may be connected to one or more I/O busses that are connected to system bus 113 via an intermediate bus bridge (not shown). Suitable I/O buses for connecting peripheral devices such as hard disk controllers, network adapters, and graphics adapters typically include common protocols, such as the Peripheral Component Interconnect (PCI). Additional input/output devices are shown as connected to system bus 113 via user interface adapter 108 and display adapter 112. A keyboard 109, mouse 110, and speaker 111 all interconnected to bus 113 via user interface adapter 108, which may include, for example, a Super I/O chip integrating multiple device adapters into a single integrated circuit.

In exemplary embodiments, the processing system 100 includes a graphics processing unit 130. Graphics processing unit 130 is a specialized electronic circuit designed to manipulate and alter memory to accelerate the creation of images in a frame buffer intended for output to a display. In general, graphics processing unit 130 is very efficient at manipulating computer graphics and image processing, and has a highly parallel structure that makes it more effective than general-purpose CPUs for algorithms where processing of large blocks of data is done in parallel.

Thus, as configured in FIG. 1, the system 100 includes processing capability in the form of processors 101, storage capability including system memory 114 and mass storage 104, input means such as keyboard 109 and mouse 110, and output capability including speaker 111 and display 115. In one embodiment, a portion of system memory 114 and mass storage 104 collectively store an operating system such as the AIX® operating system from IBM Corporation to coordinate the functions of the various components shown in FIG. 1.

Referring now to FIG. 2, a system 200 for redundantly storing product data for an electronic component on an external device is illustrated. As illustrated, the system 200 includes an electronic component 202 which has a processor 204, a primary storage device 206, a transceiver 208 and a secondary storage device 212. In exemplary embodiments, the primary storage device 206 is a non-volatile memory that is configured to store product data that corresponds to the electronic component 202. The product data may include Vital Product Data (VPD) and/or First Failure Data Capture (FFDC) that can be generated by the failure of the electronic component 202. In exemplary embodiments, during initialization, or startup of the electronic component 202 the processor 204 reads the product data from the primary storage device 206 and uses the product data to configure or provision the electronic component 202. In exemplary embodiments, configuring or provisioning the electronic component 202 may include providing the product data to other electronic components.

In exemplary embodiments, when the processor 204 is unable to read the product data from the primary storage device 206 because the product data has become corrupted, the processor 204 is configured to communicate with the external device 210 via the transceiver 208 to obtain the product data. In one embodiment, the product data can be backed up from the electronic component 202 to the external device 210 when the product data is not corrupted. In another embodiment, the product data can be loaded onto the external device 210 when it is discovered that the product data is not corrupted. For example, the external device 210 may be configured to access a product data repository maintained by a manufacturer of the electronic component 202. Optionally, the electronic component 202 may be configured to store a temporary copy of the received product data from the external device 210 in the secondary storage device 212.

In exemplary embodiments, the external device 210 may be a smartphone, a tablet, a laptop computer or the like. In exemplary embodiments, the external device 210 and the transceiver 208 may be configured to communicate with each other via any suitable wireless communications protocol including, but not limited to, near field communications (NFC), Bluetooth, WiFi, or the like. The external device 210 may be configured to store product data received from a plurality of electronic components 202 and may be configured to download product data for identified electronic components 202 from the Internet. In exemplary embodiments, the communications between the external device 210 and the transceiver 208 is secured, i.e., encrypted, and access to the external device 210 may be restricted, i.e., the external device 210 may be password protected.

In exemplary embodiments, upon a determination that the product data stored in the primary storage device 206 is corrupted, the processor 204 may provide an indication that the product data is corrupted, which in turn can be used to initiate a service call to repair or replace the electronic component 202. In exemplary embodiments, the electronic component 202 can continue to be operated by accessing the redundantly stored product data until a new part is available or until a repair is performed. In exemplary embodiments, the use of the redundantly stored product data may be limited to a temporary use. For example, the processor 204 may be configured to only allow the operation of the electronic component 202 based on the use of the product data received from the external device 210 for a predetermined time period, i.e., one week, ten days, one month, or the like since it was determined that the product data in the primary storage device 206 was corrupted.

In exemplary embodiments, when an electronic component 202 fails it is desirable to obtain First Failure Data Capture (FFDC) from the electronic component 202. In exemplary embodiments, the electronic component 202 may be configured to store FFDC in the secondary storage device 212, which may accessible by the external device 210 via the transceiver 208 after the failure of the electronic component 202. The FFDC may include, but is not limited to, boot traces, core dumps, stack traces, registers and registries.

Referring now to FIG. 3, a flow diagram of a method 300 for redundantly storing product data for an electronic component on an external device in accordance with an exemplary embodiment is shown. As shown at block 302, the method 300 includes determining that product data stored in a primary storage device is corrupted. Next, as shown at decision block 304, the method 300 includes determining if the product data available on an external device. If the product data is available on an external device, the method 300 proceeds to decision block 306. If the product data is not available on an external device, the method 300 proceeds to block 308 and initiates a service call to repair or replace the electronic component and halts operation of the electronic component. As shown at decision block 306, the method 300 includes determining if the product data stored on the external device corrupted. If the product data stored on the external device is corrupted, the method 300 proceeds to block 308 and initiates a service call to repair or replace the electronic component and halts operation of the electronic component. Otherwise, the method 300 proceeds to block 310 and obtains product data from the external device to continue operation of the electronic component.

Referring now to FIG. 4, a flow diagram of another method 400 for redundantly storing product data for an electronic component on an external device in accordance with an exemplary embodiment is shown. As shown at block 402, the method 400 includes determining that product data stored in a primary storage device is corrupted. Next, as shown at decision block 404, the method 400 includes determining if the product data available on an external device. If the product data is available on an external device, the method 400 proceeds to decision block 406. If the product data is not available on an external device, the method 400 proceeds to block 408 and initiates a service call to repair or replace the electronic component and halts operation of the electronic component. As shown at decision block 406, the method 400 includes determining if the product data stored on the external device corrupted. If the product data stored on the external device is corrupted, the method 400 proceeds to block 408 and initiates a service call to repair or replace the electronic component and halts operation of the electronic component. Next, as shown at block 410, the method includes obtaining a replacement product data by the external device. As shown at block 412 the method 400 includes retrieving and storing the product data from the external device in a secondary storage device of the electronic component. The method 400 also includes scheduling a repair or replacement of the electronic component and continuing operation of the electronic component with the product data stored in the secondary storage device for a maximum time period.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

Claims

1. A method for redundantly storing product data for an electronic component on an external device, the method comprising:

determining that product data stored in a primary storage device is corrupted;

determining whether the product data is available on the external device that is in communication with the electronic component;

based on a determination that the product data stored in the primary storage device is corrupted and that the product data is available on the external device, obtaining product data from the external device to continue operation of the electronic component.

2. The method of claim 1, further comprising determining whether the product data stored on the external device is corrupted.

3. The method of claim 2, further comprising initiating a service call to replace the electronic component and halting operation of the electronic component based on a determination that the product data stored on the external device is corrupted.

4. The method of claim 1, further comprising initiating a service call to replace the electronic component and halting operation of the electronic component based on a determination that the product data stored in the primary storage device is corrupted and that the product data is not available on the external device.

5. The method of claim 2, further comprising obtaining replacement product data by the external device based on a determination that the product data stored on the external device is corrupted.

6. The method of claim 1, further comprising storing the product data obtained from the external device in a secondary storage device disposed on the electronic component.

7. The method of claim 1, wherein the continued operation of the electronic component with the product data obtained from the external device is limited to a maximum time period.