|Publication number||US6314338 B1|
|Application number||US 09/477,682|
|Publication date||Nov 6, 2001|
|Filing date||Jan 6, 2000|
|Priority date||Jan 6, 2000|
|Publication number||09477682, 477682, US 6314338 B1, US 6314338B1, US-B1-6314338, US6314338 B1, US6314338B1|
|Inventors||Robert L. Billington|
|Original Assignee||Storage Technology Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (3), Non-Patent Citations (2), Referenced by (15), Classifications (28), Legal Events (5)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention is related to the field of automatic configuration detection and methods of operation for robotic data library systems
Very large robotic library systems are formed by linking two or more stand-alone libraries together. Each stand-alone library consists of a library storage module having hundreds to thousands of cells for storing data cartridges, one or more read/write cartridge drives, one or more robotic arms for moving the data cartridges between the cells and read/write cartridge drives, and one or more library controllers. Inter-library data cartridge transfers are accomplished by a device called a pass through port. Each pass through port has the ability to move one or more data cartridges at a time between the two library that it couples together. Coordination of data cartridge movement through a pass through port is usually accomplished in a master/slave relationship. One library controls the pass through port as a master, the other library operates as a slave.
In very large robotic library systems, each library is often coupled to several of its neighbor libraries by the pass through ports. This is done to provide multiple paths entering and exiting each library. This also results in multiple paths between any two given libraries in the robotic library system. Should one path fail or become busy with other tasks, a data cartridge can be transferred between libraries by an alternative path.
Coordination of inter-library data cartridge transfers is accomplished by one or more library management units. Each library management unit is aware of the configuration of the robotic library system, and has the ability to communicate with all, or at least some of the libraries. The library management unit is thus given the responsibility of instructing individual libraries when and where to move a given data cartridge in order to move that data cartridge from a source library to a destination library.
Problems can arise when the library management units have the wrong information about the configuration of the robotic library system. Incorrect information is currently introduced at installation and expansion times. Installers manually enter configuration data into the library management unit since the hardware lacks a capability for self-discovery. Existing installations have included as many as sixteen libraries interconnected by up to twenty-nine pass through ports. Manual configuration entry becomes even more prone to manually induced error when the robotic library system has multiple library management units. The installers must enter the exact same information into all of the library management units to insure proper operations.
Another source of manually induced error comes from the clients who use the very large robotic library systems. Client generated code that is dependent upon the robotic library system configuration must have the exact same information that the installer entered into the library management units. Any mismatch between the client generated code and the library management unit concerning the configuration can result in unwanted and unexpected operations.
The present invention is a robotic library system, and methods of operation for automatic configuration discovery and subsequent movements of data cartridges within the system. The robotic library system has multiple libraries connected by one or more pass through ports. Each library is capable of storing a plurality of data cartridges. Each pass through port is capable of moving one or more data cartridges at a time between the two libraries that it connects together. Unique identifiers are associated with each library and are adapted to be readable by identifier readers disposed in adjoining libraries coupled by the pass through ports.
The identifiers may be in the form of memory devices, optical patterns, or the like. Memory device type identifiers may be disposed within the associated library and transferred to the adjoining libraries through communications channels. The communications channels may be functionally and/or physically routed through the pass through ports. Alternatively, the memory device type identifiers may be disposed within the adjoining library by the installer at installation time. Likewise, optical pattern based identifiers of one library may be mounted in the adjoining libraries, preferably near the appropriate pass through port.
In operation, the identifier readers of one library read the identifiers of each adjoining library connected by a pass through port. This information is then combined in a library management unit to produce an inter-library connectivity model for the robotic library system. The library management unit may use this model to select an appropriate path through one or more pass through ports and libraries to move a data cartridge from a sending library to a destination library.
Knowledge of the identity of interconnected libraries allows interlibrary paths to be determined by the libraries themselves, instead of by the library management unit. The sending library may query its adjoining libraries through the communication channels in search of the destination library. If the source and destination libraries are not directly connected by a pass through port, then those libraries adjoining the source library query their adjoining libraries, and so on, until the destination library is queried. The destination library responds to each query received with an answer. News of all paths found is relayed back to the source library where one path is selected. Finally, the data cartridge is sent on its way to the destination library through the selected path.
In another method of operation, the source library queries its adjoining libraries seeking the destination library. If the destination library is not directly connected to the source library, then the source library may move a data storage cartridge to one of its adjoining libraries along with the destination library's identity. The libraries receiving the data cartridge will then repeat the process, moving the data cartridge to other adjoining libraries, until the data cartridge reaches the destination library.
Intelligence in the pass through port allows data cartridge movements between connected libraries to take place with the libraries acting as peers to each other. Here, the source library will request a pass through port to position itself to receive a data cartridge with the source library. Once the pass through port indicates that it is positioned, the source library moves the data cartridge into the pass through port. After the source library has informed the pass through port that it is finished loading the data cartridge, the pass through port repositions the data cartridge to give it to the destination library. When ready to unload the data cartridge, the pass through port notifies the destination library that the data cartridge is available. The destination library then unloads the data cartridge from the pass through port.
Accordingly, it is an object of the present invention to provide a robotic library system having multiple libraries wherein each library has a unique identifier and an identifier reader mechanism capable of reading the identifiers associated with adjoining libraries connected through a pass through port. The identifiers and identifier readers provide the robotic library system with a configuration self-discovery capability.
Another object of the present invention is a method of operating a robotic library system where the individual libraries use the self-discovered configuration information and inter-library communications to move data cartridges between libraries.
These and other objects, features and advantages will be readily apparent upon consideration of the following detailed description in conjunction with the accompanying drawings.
FIG. 1 is a schematic diagram of a robotic library system that implements the present invention;
FIG. 2 is a schematic diagram of a robotic library system having multiple library management units;
FIG. 3 is a schematic diagram showing the identifiers in communication with identifier readers in adjoining libraries;
FIG. 4 is a schematic diagram showing the communication channel between the identifiers and identifier readers physically routed through a pass through port;
FIG. 5 is a schematic diagram showing the communications between the identifiers and identifier readers functionally routed through a pass through port;
FIG. 6 is a schematic diagram where the identifiers are memory devices disposed in the adjoining libraries;
FIG. 7 is a schematic diagram where the identifiers are optical patterns and the identifier readers are optical cameras;
FIG. 8 is a flow diagram of a method for creating an inter-library connectivity model for the robotic library system;
FIG. 9 is a flow diagram of a first method for moving a data cartridge from a source library to a destination library;
FIG. 10 is a flow diagram or a second method for moving a data cartridge from a source library to a destination library; and
FIG. 11 is a flow diagram of a peer-to-peer method for moving a data cartridge between two connected libraries.
FIG. 1 is a schematic diagram of a robotic library system 100 implementing the present invention. The robotic library system 100 consists of multiple libraries 102 a-f interconnected by multiple pass through ports 104 a-i. Each library 102 a-f includes a library storage modules (LSM) 106 a-f and a library control unit (LCU) 108 a-f respectively. Inside each LSM 106 a-f are multiple storage cells 110 for storing data cartridges 112, and a robotic mechanism 114 a-f for moving the data cartridges about inside the LSMs 106 a-f. The pass through ports 104 a-i are attached to the LSMs 106 a-f to enable adjoining libraries 102 a-f to exchange data cartridges. Each LSM 106 a-f is typically, although not necessarily, interconnected with between two to four adjacent LSMs 106 a-f through the pass through ports 104 a-i.
Control of the robotic mechanisms 114 a-f is provided by the LCUs 108 a-f respectively. The LCUs 108 a-f instruct the robotic mechanisms 114 a-f when and how to insert and remove data cartridges from the storage cells 110, and insert and remove the data cartridges from the pass through ports 104 a-i. To coordinate the overall activities of the robotic library system 100, each LCU 108 a-f is in communication with a library management unit (LMU) 116. The LSU 116 provides a uniform interface to a client 200 making all six libraries 102 a-f appear as one larger library from the client's 200 point of view.
FIG. 2 is a schematic diagram of an alternative embodiment of the robotic library system 100. In this embodiment, the robotic library system 100 appears to the client 200 as two logical robotic library systems 118 a and 118 b. One logical robotic library system 118 a consists of three libraries 102 a-c, that are in communication with a first LMU 116 a. The second logical robotic library system 118 b consists of the other three libraries 120 d-f, in communication with a second LMU 116 b. Pass through ports 104 a-i interconnecting the various libraries 102 a-f allowing the two logical robotic library systems 118 a and 118 b to exchange data cartridges.
In order to pass a data cartridge between libraries 102 a-f, for example from library 102 a to library 102 f, the inter-library connectivity of the robotic library system 100 must be known. Traditionally, it has been the responsibility of either the installer or the client to manually enter this connectivity information into the LMUs 116 a-b. The present invention provides for automatic self-discovery of the inter-library library connectivity. Self-discovery may be performed automatically upon power up, it may be performed periodically, it may be initiated manually, and it may be performed as required to move the data cartridges between libraries.
Referring to FIG. 3, self-discovery is accomplished by providing each library 302 a-b with a unique identifier 320 a-b (ID A and ID B). These identifiers 320 a-b are adapted to be readable by identifier readers 322 a-b associated with adjoining libraries 302 a-b connected by the pass through port 304. In the example shown in FIG. 3, the identifier A 320 a mounted inside the left LCU 308 a of the left library 302 a is readable by the right identifier reader 322 b mounted inside the right LCU 308 b of the right library 302 b. Likewise, the identifier B 320 b mounted inside the right LCU 308 b of the right library 302 b is readable by the left identifier reader 322 a mounted inside the left LCU 308 a of the left library 302 a. As read, the identifiers 320 a-b may appear as numbers, characters, symbols, combinations of numbers, characters and/or symbols, and the like. Physically, the identifiers 320 a-b may be in the form of an optical media, electrical media, or other suitable media.
Consider an example where the identifiers 320 a-b and the identifier readers 322 a-b are implemented electronically. Here, the identifiers 320 a-b may be PROMs containing unique binary numbers for each library 302 a-b respectively. Identifier readers 322 a-b are microprocessors capable of reading the binary information stored in the PROMS 320 a-b. The identifiers 320 a-b are adapted to be readable by the identifier readers 322 a-b by electrically linking the PROMs 320 a-b to the microprocessors 322 a-b using a communication channel 324 made of discrete wires.
In another example, the identifiers 322 a-b may be in the form of optical light sources that repeatedly blink a unique pattern for each library 302 a-b. Identifier readers 322 a-b are light sensors sensitive to the light emitted by the light sources 320 a-b. Communication channel 324 is a pair of fiber optical cables, where each fiber optical cable is coupled to a light source 320 a-b at on end and the corresponding light sensor 322 a-b at the other end. Many other forms of identifiers 320 a-b, identifier readers 322 a-b, and communication channels 324 are possible within the scope of the present invention. The examples listed are provided as illustrations, and are not meant to be limitations.
FIG. 4 shows the preferred embodiment of the present invention. Here, the communication channel 424 is a serial digital bus routed through the pass through port 404 that connects a pair of libraries, the left library 403 a and the right library 402 b. The communications channel 424 is linked to the LCUs 408 a-b at each end. Communications channel 424 transfers the two identifiers 420 a-b between both libraries of the pair of libraries 402 a-b. In operation, identifier A 420 a (ID A) for the left library 420 a is copied into the communication channel 424 by way of a bus interface circuit 426 a. Identifier A 420 a is removed from the communication channel 424 inside the right LCU 408 b by another bus interface circuit 426 b, and then stored in memory 428 b. In an identical fashion, identifier B 420 b (ID B) associated with the right library 402 b is copied into the communication channel 424 by the right bus interface circuit 426 b. Identifier B 420 b is then transferred through the pass through port 404, removed from the communication channel 424 by the left bus interface circuit 426 a, and stored in memory 428 a. The identifier readers 422 a-b are coupled to the memories 428 a-b respectively allowing them to read the identifier 420 a-b of the opposite library 420 a-b.
Use of a bus type of communication channel 424 in the preferred embodiment has additional advantages that will be discussed in more detail later. In particular, a general purpose bus linking the left library 402 a with the right library 420 b allows the two libraries 402 a and 402 b to communicate other information in addition to the respective identifiers 420 a-b.
FIG. 5 is a schematic diagram of another embodiment of the present invention. In this embodiment the pass through port 504 plays an active role in transferring the identifiers 420 a-b between connected libraries 402 a-. Identifier A 420 a (ID A) is placed into a first communication channel 524 a and transferred to the pass through port 504. At the pass through port 504, identifier A 420 a is removed from the first communication channel 524 a by another bus interface circuit 550 a and buffered in memory 552 a. From memory 552 a, identifier A 402 a is placed into a second communication channel 524 b by another bus interface circuit 550 b and transferred to the right library 402 b. Once at the right library 402 b, identifier A 402 a is removed from the second communication channel 524 b by bus interface circuit 426 b where it is available to be read by the microprocessor 422 b. Likewise, identifier B 420 b(ID B) is transferred from the right library 402 b, to the pass through port 504 in the second communication channel 524 b. The pass through port 504 relays identifier B 402 b from the second communication channel 524 b, through a memory buffer 552 b, then into the first communication channel 524 a. From the first communication channel 524 a, the identifier B 402 b is stored in memory 428 a where it is available to be read by microprocessor 422 a.
FIG. 6 shows a third embodiment of the present invention that does not require a communication channel running between libraries 602 a-c. In this embodiment, the identifiers 620 a-c are memory devices that are physically separate from their associated libraries 602 a-c. As this robotic library system 600 is being assembled, the installer transfers the identifiers 620 a-c into the LCUs 608 a-c of the adjoining libraries 602 a-c connected by pass through ports 604 a-b. Now the microprocessors 622 a-c within each LCU 608 a-c can directly read the identifiers 620 a-c of the adjoining libraries 602 a-c. As shown in FIG. 6, LSM A 606 a is connected to LSM B 606 b by pass through port 604 a. LSM B 606 b is connected to LSM A 606 a and LSM C 606 c. LSM C 606 c is only connected with LSM B 606 b by pass through port 604 b. The identifier A 620 a for the left library 602 a is installed within LCU B 608 b where it is readable by the LCU B's microprocessor 622 b. Likewise, identifier C 620 c associated with the right library 602 c is installed within LCU B 608 b where it is also readable by the microprocessor 622 b. The center library 602 b has two associated copies of its identifier B 620 b, one is installed within LCU A 608 a, the other installed within LCU C 608 c. Note that since LSM A 606 a and LSM C 606 c are not directly connected by a pass through port, so they do not have copies of their respective identifiers 620 a and 620 c installed within each other's LCUs 608 c and 607 a respectively.
FIG. 7 shows an example where the identifiers 720 a-c are made of an optical media. In particular, the identifiers 720 a-c are bar codes similar to those used on the data cartridges. This approach allows the identifiers 720 a-c to be read by the bar code (identifier) readers 722 a-c mounted on the robotic mechanisms 714 a-c. The bar code readers 722 a-c read the identifiers 720 a-c and then provided the information to LCUs 708 a-c respectively. In this example, LSM A 706 a is interconnected to LSM B 706 b, LSM B 706 b is interconnected with LSM A 706 a and LSM C 706 c, and LSM C 706 c is interconnected only with LSM B 706 b. During assembly of the robotic library system 700, the installer physically mounts the bar code identifier A 720 a associated with the left library 702 a within LSM B 706 b where it is readable by bar code reader B 722 b. Likewise, the bar code identifier C 720 c associated with the right library 702 c is also mounted within LSM 706 b where it is readable by the bar code reader B 722 b. Central library 702 b has two associated bar code identifiers 720 b. One of these bar code identifiers B 720 b is physically mounted inside LSM A 706 a where the bar code reader A 722 a can read it. The other bar code identifier B 720 b is physically mounted within LSM C 706 c where the bar code reader C 722 c can access it. For ease of installation, the bar code identifiers 720 a-c may be mounted adjacent the corresponding pass through ports 704 a-b.
FIG. 8 is a flow diagram of a method for creating a configuration model for the robotic library system. The method starts by providing a unique identifier for each library, as shown in block 800. The identifiers are then adapted to be readable by libraries connected together by a pass through port, as shown in block 802. Adaptation may be accomplished by transferring a logical copy of the identifiers between connected libraries using communication channels, see for example FIGS. 4 and 5. Adaptation may also be accomplished by physically placing, mounting or coupling the identifiers of one library within each adjoining connected library, see for example FIGS. 6 and 7. Identifier readers in the adjoining libraries read the identifiers and make that information available to the associated LCUs, as shown in block 804. Each LCU then transfers the information to the LMU, as shown in block 806. Once the LMU has the connectivity information from each LCU, it combines all this data to create an inter-library connectivity model, as shown in block 808. The LMU now knows the identity of each library within the robotic library system, and which pairs of libraries are connected by pass through ports.
Knowledge of the inter-library connectivity allows the LCUs to handle data cartridge transfers between LSMs, a role traditionally reserved for the LMUs. FIG. 9 is a flow chart of a method for moving data cartridges from one library to another wherein inter-library transfers and routing are controlled by the LCUs. This operation begins when the LMU receives a command from the client to move a specific data cartridge from a source library to a destination library, as shown in block 900. The LMU then relays this command to the LCU of the source library holding the specific data cartridge, as shown in block 902. Next, the LCU in the source library queries all LCUs of adjoining libraries connected by a pass through port to see if one of them is the destination library, as shown in block 904. Each library receiving the query that is not the destination library will repeat the query to its adjoining libraries, the NO branch of decision block 906. This process is repeated until the destination library is queried, the YES branch of decision block 906.
The destination library responds to each query with an answer, as shown in block 908. This means that the destination library may generate multiple answers to multiple queries. Each library receiving an answer will append the status (e.g. busy, idle) of the pass through port through which the answer was received, as shown in block 910. The libraries then relay the appended answers to all other adjoining libraries connected by the pass through ports, as shown in block 912. This same process is then repeated by each library receiving an answer, the NO branch of decision block 914, until all answers are relayed back to the source library, the YES branch of decision block 914. The source library then examines all answers and the appended pass through port statuses to determine the best path through which the data cartridge should be transferred to the destination library, as shown in block 916.
Criteria for determining the best path to transfer a data cartridge may vary within the scope of the present invention. For example, the best path may be the path having the fewest number of pass through ports between the source library and the destination library, as determined by the identifiers along that path. In another example, the best path may be the path wherein all of the pass through ports are currently idle. Other criteria which may be considered includes whether or not the pass through port is currently operational, any anticipated activity in the near future, the quickness by which the path can be traveled, and the status of the robotic mechanisms along the paths under consideration.
Once the source library has determined the best path by which to move the data cartridge, it will transfer the data cartridge along with the chosen path to the next library on the path, as shown in block 918. The library receiving the data cartridge and path will transfer the data cartridge to the next library on the path, the NO branch of decision block 920 back to block 918. This process is continued until the data cartridge reaches the destination library, the YES branch of decision block 920. This ability of the LCUs to handle data cartridge transfers between LSMs make it possible to construct robotic library systems without the LMUs.
Self-discovery of inter-library connectivity allows for other methods of transferring data cartridges between the libraries. FIG. 10 is a flow diagram of a second method of transferring a data cartridge from the source library to the destination library. This method starts with the client sending the LMU a command to move the selected cartridge to the destination library, as shown in block 1000. The LMU responds by relaying this command to the source library currently holding the selected data cartridge, as shown in block 1002. The source library will then look at the identifiers read from its adjoining libraries, as shown by decision block 1004. If the destination library is directly connected to the source library through a pass through port, the YES branch of decision block 1004, then the source library will transfer the desired data cartridge directly to the destination library, as shown in block 1006. If the destination library is not connected directly to the source library, the NO branch of decision block 1004, then the source library will choose another library from among those that it is directly connected. The choice of the other library may be at random, chosen in accordance with some preset pattern, or by any other suitable method.
When the source and destination libraries are not directly connected, the source library transfers the desired data cartridge and the identifier of the destination library to the chosen library, as shown in block 1008. The chosen library then repeats the process just performed by the source library. In other words, it will check the identifiers of all adjoining libraries seeking the destination library. If the destination library resides at the other side of a pass through port, then the data cartridge will be sent to the destination library directly. Otherwise, the library will choose yet another adjacent library, pass the data cartridge and the identifier of the destination library.
Referring momentarily back to FIG. 5, the presence of an intelligent pass through port along with an ability to communicate with the LCUs on either side of the pass through port, allow data cartridges to be transferred between libraries in a peer to peer fashion. Peer to peer type data cartridge transfers have an advantage over master/slave-type data cartridge transfers in that the source library is not dependent upon the destination library to initiate the data cartridge transfer. By contrast, in a master/slave relationship, the slave library cannot initiate a data cartridge transfer until the master library is ready to control the pass through port. FIG. 11 is a flow diagram of a peer to peer type method of transferring the data cartridge between libraries. The operation starts when the source library, currently holding the data cartridge, receives a command to move the data cartridge to the destination library, as shown in block 1100. Using the communication channel, the source library can request the pass through port to position itself to receive the data cartridge from the source library, as shown in block 1102. The pass through port eventually responds to this request by position itself to receive the data cartridge, as shown in block 1104.
Once the pass through port is ready to receive a data cartridge from the source library, it notifies the source library, as shown in block 1106. The source library then moves the data cartridge into the pass through port, as shown in block 1108. In block 1110, the source library notifies the pass through port when the transfer is complete.
Next, the pass through port repositions the data cartridge to be received by the destination library, as shown in block 1112. The pass through port notifies the destination library when the data cartridge is available, as shown in block 1114. Some time after receiving notification, the destination library removes the data cartridge from the pass through port, as shown in block 1116, and then notifies the pass through port that it has completed its operation, as shown in block 1118. One advantage of this method is that it involves little to no interaction from the LMU. Another advantage is that the source library can initiate and proceed with the transferring the data cartridge as far as the pass through port, even when the destination library is not ready.
While embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5506986 *||May 16, 1995||Apr 9, 1996||Electronic Data Systems Corporation||Media management system using historical data to access data sets from a plurality of data storage devices|
|US5546366 *||Jun 16, 1994||Aug 13, 1996||International Business Machines Corporation||Cartridge picker assembly and modular library system|
|US6175466 *||Aug 7, 1998||Jan 16, 2001||Fujitsu Limited||Library unit having a cartridge transfer robot with a rotatable picker section|
|1||Beccari et al., A real-time library for the design of hybrid robot control architectures, 1998, IEEE, pp. 1145-1150.*|
|2||*||Kendall, Cimarron user experience, 1988, IEEE, pp. 93-97.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6732010 *||Dec 24, 2002||May 4, 2004||Storage Technology Corporation||Method, system, and product for associating subcomponents with a particular storage library|
|US6808353||Dec 19, 2001||Oct 26, 2004||Storage Technology Corporation||Method of non-disruptive capacity scaling for a data storage library|
|US6895300||Feb 3, 2003||May 17, 2005||International Business Machines Corporation||Use of cartridge memory for storing logical library association information|
|US6898480||Feb 3, 2003||May 24, 2005||International Business Machines Corporation||Use of cartridge memory for storing logical library association information|
|US7021883||Mar 18, 2003||Apr 4, 2006||Storage Technology Corporation||System and method for transporting media cartridges|
|US7685377||Jul 12, 2006||Mar 23, 2010||Storage Technology Corporation||Piecewise logical data management|
|US7707596||Jul 14, 2005||Apr 27, 2010||Storage Technology Corporation||Queue hand|
|US8176505||May 8, 2012||Oracle America, Inc.||Method of manipulating data storage elements|
|US8687315||May 11, 2011||Apr 1, 2014||International Business Machines Corporation||Data storage system using a media mobility unit (MMU), the MMU, and methods of use thereof|
|US9156615||Jan 7, 2014||Oct 13, 2015||International Business Machines Corporation||Methods of use of a media mobility unit (MMU)|
|US9242797||Nov 12, 2013||Jan 26, 2016||International Business Machines Corporation||Media mobility unit (MMU) and methods of use thereof|
|US20030138929 *||Feb 3, 2003||Jul 24, 2003||Council For Scientific And Industrial Research (Csir)||Novel strain of Streptomyces sp. and a process for the preparation of an alkaline protease inhibitor|
|US20040153206 *||Feb 3, 2003||Aug 5, 2004||International Business Machines Corporation||Use of cartridge memory for storing logical library association information|
|US20100165506 *||Mar 4, 2010||Jul 1, 2010||Storage Technology Corporation||Method of manipulating data storage elements|
|WO2003054872A1 *||Dec 17, 2002||Jul 3, 2003||Storage Technology Corporation||Method of non-disruptive capacity scaling for a data storage library|
|U.S. Classification||700/245, G9B/27.001, G9B/27.052, 701/23, 700/215, 701/50, 700/260, 901/6, 360/92.1, 901/1|
|International Classification||G11B27/00, G06F3/06, G11B27/36, G11B17/22, G11B15/68|
|Cooperative Classification||G11B15/68, G06F3/0607, G11B27/36, G11B17/22, G11B2220/41, G06F3/0686, G11B27/002, G06F3/0632|
|European Classification||G06F3/06A2A4, G06F3/06A6L4L, G06F3/06A4C2, G11B27/00A, G11B27/36|
|Jan 6, 2000||AS||Assignment|
Owner name: STORAGE TECHNOLOGY CORPORATION, COLORADO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BILLINGTON, ROBERT L.;REEL/FRAME:010489/0369
Effective date: 20000105
|May 6, 2005||FPAY||Fee payment|
Year of fee payment: 4
|Apr 29, 2009||FPAY||Fee payment|
Year of fee payment: 8
|Mar 7, 2013||FPAY||Fee payment|
Year of fee payment: 12
|Feb 4, 2016||AS||Assignment|
Owner name: ORACLE AMERICA, INC., CALIFORNIA
Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:SUN MICROSYSTEMS, INC.;ORACLE USA, INC.;ORACLE AMERICA, INC.;REEL/FRAME:037692/0970
Effective date: 20100212
Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA
Free format text: MERGER;ASSIGNOR:STORAGE TECHNOLOGY CORPORATION;REEL/FRAME:037695/0339
Effective date: 20061222