Patent Grant
9965347
During a manufacture of a data storage device, manufacturing data may be useful for the manufacturing process or failure analysis. The manufacturing data may be transferred between manufacturing devices. However, if the manufacturing devices are connected to a network, they may be exposed to viruses or other undesirable risks, which may compromise the manufacture of the data storage device. However, if the manufacturing devices are not connected to a network, then users may have to manually collect the manufacturing data, which may be cumbersome and cost-prohibitive.
The features and advantages of the present embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the drawings, wherein:
In an embodiment, a manufacturing system 100 for a data storage device is shown in
While the description herein refers to solid state memory generally, it is understood that solid state memory may comprise one or more of various types of solid state non-volatile memory devices such as flash integrated circuits, Chalcogenide RAM (C-RAM), Phase Change Memory (PC-RAM or PRAM), Programmable Metallization Cell RAM (PMC-RAM or PMCm), Ovonic Unified Memory (OUM), Resistance RAM (RRAM), NAND memory (e.g., single-level cell (SLC) memory, multi-level cell (MLC) memory, or any combination thereof), NOR memory, EEPROM, Ferroelectric Memory (FeRAM), Magnetoresistive RAM (MRAM), other discrete NVM (non-volatile memory) chips, or any combination thereof
In an embodiment shown in
Referring back to the embodiment shown in
For example, in an embodiment shown in
In an embodiment shown in
Referring back to the embodiment shown in
In an embodiment, during a manufacture of the data storage device 106, the data storage device 106 moves through one or more non-networked manufacturing devices 102a, 102b, or 102c. In addition, the data storage device 106 moves through the networked manufacturing device 104.
At the non-networked manufacturing devices 102, manufacturing operations are performed on the data storage device 106. For example, non-networked manufacturing device 102a (initializer device) can load firmware onto the data storage device 106. The non-networked manufacturing device 102a can enable or disable different settings or features in the data storage device such as encryption or virtual compact disc (“CD”).
Furthermore, in the non-networked manufacturing device 102b (duplicator device), a formatting operation, partition operations, and/or file system setting operations can be performed on the data storage device 106.
In an embodiment, the non-networked manufacturing device 102c (audit device) is utilized to selectively test some of the data storage devices 106 to ensure that the data storage devices 106 were correctly manufactured. Thus, not all of the data storage device 106 may be tested by the non-networked manufacturing device 102c.
In an embodiment, the non-networked manufacturing devices 102a, 102b, and 102c are configured to store manufacturing data 132 in the data storage device reliability log 116 as shown in
In an embodiment, manufacturing metrics may include, for example, a time stamp, a counter, identification data of the data storage device 106, identification data of components of the data storage device 106, identification data of the one or more non-networked manufacturing devices 102, identification data of the manufacturing system 100, identification data of the location where the data storage device 106 is being manufactured, temperature of the data storage device 106, humidity of the data storage device 106, or other data which may impact the manufacturing of the data storage device 106.
For example, the non-networked manufacturing device 102a (initializer device) may store manufacturing data related to the operations performed by the non-networked manufacture device 102a such as initializer device data. In an embodiment, the initializer device data can comprise information such as revision of software loaded onto the data storage device 106, version of firmware loaded onto the data storage device 106, product identification, vendor identification, world wide name, and/or one or more of the manufacturing metrics.
Similarly, the non-networked manufacturing device 102b (duplicator device) may store manufacturing data related to the operations performed by the non-networked manufacturing device 102b such as duplicator device data. In an embodiment, the duplicator device data can comprise a globally unique ID (“GUID”) of the data storage device 106 and/or one or more of the manufacturing metrics.
In an embodiment, the non-networked manufacturing device 102c (audit device) may also optionally store manufacturing data related to the operations performed by the non-networked manufacturing device 102c such as audit device data. The audit device data can include statistics related to failure rate of the data storage device 106, which data storage devices 10 were sampled, or one or more of the manufacturing metrics.
In an embodiment, only some of the non-networked manufacturing devices 102 may store manufacturing data in the data storage device reliability log 116 of the data storage device 106. In an embodiment, all of the non-networked manufacturing devices 102 store manufacturing data in the data storage device reliability log 116 of the data storage device 106.
In an embodiment, this can allow the manufacturing data for some or all of the non-networked manufacturing devices to be stored without the non-networked manufacturing devices 102 being connected to a network. This can increase security since the non-networked manufacturing devices 102 will be less prone to any attacks or viruses on the network 118. Furthermore, since the manufacturing data is written to the data storage device reliability log 116, the manufacturing data is stored in a location which does not ordinarily store user data (e.g. non-user data section). In addition, since the data storage device reliability log 116 is already being utilized, this can reduce a manufacturing cost of the data storage device 106.
Furthermore, manufacturing costs can also be reduced since the cost of providing networking equipment for the non-networked manufacturing devices 102 can be avoided or reduced. Also, accuracy of manufacturing data can be improved since the manufacturing data will be collected and written by the non-networked manufacturing devices 102 instead of manually by manufacturing personnel.
In an embodiment, to further increase security, some or all of the manufacturing data may be encrypted. In an embodiment, the manufacturing data may be encrypted using some or all of a portion of the serial number for the data storage device 106, other data unique to the specific data storage device 106, or other identifier of the data storage device 106.
In an embodiment, the manufacturing data may be uniquely encrypted for each non-networked manufacturing device 102. For example, the non-networked manufacturing device 102a may encrypt the manufacturing data using a first encryption key, while the non-networked manufacturing device 102b may encrypt the manufacturing data using a second encryption key different than the first encryption key.
In an embodiment, each of the manufacturing data for each of the non-networked manufacturing devices 102 may be uniquely encrypted. That is, the non-networked manufacturing device 102a may encrypt a first manufacturing data using a first encryption key, while the non-networked manufacturing device 102b may encrypt a second manufacturing data using a second encryption key different than the first encryption key. In an embodiment, additional or different encryption schemes may be employed to protect the manufacturing data. In an embodiment, encryption of the manufacturing data reduces the likelihood that the manufacturing data is tampered or altered in an unauthorized or undesirable manner.
In an embodiment, the networked manufacturing device 104 tests each of the data storage devices 106 to ensure that they are manufactured correctly. For example, the networked manufacturing device 104 (verification device) verifies that each of data storage devices 106 is manufactured correctly. In an embodiment, the networked manufacturing device 104 may utilize the manufacturing data to verify that each of the data storage devices 106 is manufactured correctly. In an embodiment, the networked manufacturing device 104 may also provide additional manufacturing data. The additional manufacturing data may indicate whether the data storage device passed or failed the networked manufacturing device 104, and some or all of the other types of manufacturing data previously indicated for the non-networked manufacturing devices 102 which may be pertinent for the networked manufacturing device 104.
In an embodiment, the networked manufacturing device is configured to compile the manufacturing data into a manufacturing data log for a single data storage device 106 or multiple data storage devices 106. Should the manufacturing data be encrypted, the networked manufacturing device 104 may decrypt the manufacturing data. Thus, the networked manufacturing device 104 may comprise decryption keys to decrypt the manufacturing data. In an embodiment, the networked manufacturing device 104 is configured to transmit the manufacturing data, the manufacturing data log, or any combination thereof to another location where the manufacturing data, the manufacturing data log, or any combination thereof, may be analyzed.
The analysis of the manufacturing data or the manufacturing data log may be useful for failure analysis, trouble shooting, improvements towards the manufacturing system 100, cost benefit analysis, statistical compilations, or other analysis which may be useful based on the manufacturing data and/or the manufacturing data log. In an embodiment, the manufacturing data log may also be encrypted using some or all of the processes indicated for encryption of the manufacturing data.
In an embodiment, the networked manufacturing device 104 may also be configured to erase the manufacturing data from the data storage device reliability log 116. In an embodiment, this can further reduce the likelihood of unauthorized access to the manufacturing data. For example, this can prevent a user from accessing the manufacturing data after the data storage device 106 has been shipped or given to the user.
In an embodiment, the manufacturing of the data storage devices 106 may occur in stages. For example, operations performed by the non-networked manufacturing devices 102 may be considered to be a first stage of the manufacturing process. Furthermore, operations performed by the networked manufacturing device 104 may be considered to be a second stage of the manufacturing process.
In an embodiment, a process for manufacturing the data storage device 106 is shown in
In block S704, the manufacturing data is read from the data storage device reliability log 116 using the networked manufacturing device 104. In block S706, the networked manufacturing device 104 analyzes the manufacturing data and passes or fails the data storage device 106 based on the manufacturing data.
In block S708, the networked manufacturing device 104 can connect to the network 118 using the network connection unit 128. In block S710, the networked manufacturing device 104 can transmit the manufacturing log to the network 118 using the network connection unit 128.
In an embodiment, optional or additional blocks for a process for manufacturing the data storage device 106 are shown in
Those of ordinary skill would appreciate that the various illustrative logical blocks, modules, and algorithm parts described in connection with the examples disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. Furthermore, the embodiments can also be embodied on a non-transitory machine readable medium causing a processor or computer to perform or execute certain functions.
To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and process parts have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed apparatus and methods.
The parts of a method or algorithm described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The parts of the method or algorithm may also be performed in an alternate order from those provided in the examples. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, an optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuit (ASIC).
The previous description of the disclosed examples is provided to enable any person of ordinary skill in the art to make or use the disclosed methods and apparatus. Various modifications to these examples will be readily apparent to those skilled in the art, and the principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosed method and apparatus. The described embodiments are to be considered in all respects only as illustrative and not restrictive and the scope of the disclosure is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application claims the benefit of U.S. Provisional Application No. 61/917,826, filed on Dec. 18, 2013, entitled “MANUFACTURING DATA LOGGING WITHOUT A NETWORK,” which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5675622 | Hewitt et al. | Oct 1997 | A |
| 5982899 | Probst | Nov 1999 | A |
| 6499054 | Hesselink et al. | Dec 2002 | B1 |
| 6732158 | Hesselink et al. | May 2004 | B1 |
| 6895500 | Rothberg | May 2005 | B1 |
| 7120692 | Hesselink et al. | Oct 2006 | B2 |
| 7454443 | Ram et al. | Nov 2008 | B2 |
| 7467187 | Hesselink et al. | Dec 2008 | B2 |
| 7546353 | Hesselink et al. | Jun 2009 | B2 |
| 7587467 | Hesselink et al. | Sep 2009 | B2 |
| 7600036 | Hesselink et al. | Oct 2009 | B2 |
| 7788404 | Hesselink et al. | Aug 2010 | B2 |
| 7861122 | Cornwell et al. | Dec 2010 | B2 |
| 7917628 | Hesselink et al. | Mar 2011 | B2 |
| 7934251 | Hesselink et al. | Apr 2011 | B2 |
| 8004791 | Szeremeta et al. | Aug 2011 | B2 |
| 8255661 | Karr et al. | Aug 2012 | B2 |
| 8285965 | Karr et al. | Oct 2012 | B2 |
| 8341117 | Ram et al. | Dec 2012 | B2 |
| 8341275 | Hesselink et al. | Dec 2012 | B1 |
| 8352567 | Hesselink et al. | Jan 2013 | B2 |
| 8526798 | Hesselink | Sep 2013 | B2 |
| 8631284 | Stevens | Jan 2014 | B2 |
| 8646054 | Karr et al. | Feb 2014 | B1 |
| 8661507 | Hesselink et al. | Feb 2014 | B1 |
| 8688797 | Hesselink et al. | Apr 2014 | B2 |
| 20030028486 | Nakamura | Feb 2003 | A1 |
| 20050144195 | Hesselink et al. | Jun 2005 | A1 |
| 20050144200 | Hesselink et al. | Jun 2005 | A1 |
| 20070047125 | Tsukada | Mar 2007 | A1 |
| 20090037654 | Allison | Feb 2009 | A1 |
| 20110119686 | Chen | May 2011 | A1 |
| 20120036041 | Hesselink | Feb 2012 | A1 |
| 20130212401 | Lin | Aug 2013 | A1 |
| 20130266137 | Blankenbeckler et al. | Oct 2013 | A1 |
| 20130268749 | Blankenbeckler et al. | Oct 2013 | A1 |
| 20130268759 | Blankenbeckler et al. | Oct 2013 | A1 |
| 20130268771 | Blankenbeckler et al. | Oct 2013 | A1 |
| 20130339756 | Nagai et al. | Dec 2013 | A1 |
| 20140059278 | Schuh et al. | Feb 2014 | A1 |
| 20140164779 | Hartley | Jun 2014 | A1 |
| 20140205092 | Hartley | Jul 2014 | A1 |
| 20150039895 | Ho et al. | Feb 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 2005022321 | Mar 2005 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 61917826 | Dec 2013 | US |
