Patent Grant
10681746
The present disclosure relates to the drive management, and more particularly, to establishing a wireless connection with a drive environment that may be used to management the drive.
A storage drive typically includes a high-capacity, self-contained storage device containing a read/write mechanism which has access to memory included within a sealed unit. A solid state drive (SSD) is a solid-state type of storage drive which uses integrated circuit assemblies as memory to store data therein. SSD technology primarily uses electronic interfaces compatible with other types of storage drives.
SSDs have no moving mechanical components, which distinguishes them from traditional electromechanical magnetic disks such as hard disk drives (HDDs) or floppy disks. The latter contain spinning disks and movable read/write heads. Compared with electromechanical disks, SSDs are typically more resistant to physical shock, run silently, have lower access time, and lower latency.
The management of storage drives involves implementing formatting changes, and in some instances, removing a drive altogether, e.g., for replacement. Conventionally, storage drive management is performed using host operating systems which require being physically logged into the operating system of the storage drive itself in order to make any such changes. However, this is undesirable, as the operating system may not be configured to receive drive management commands from a user physically at the storage location. For instance, the operating system may not include a keyboard, a display screen, a mouse, etc.
Thus, it would be beneficial to provide systems, methods, computer program products and the like which overcome the storage drive management shortcomings. Accordingly, the ability to perform storage drive management operations via a wireless connection to the storage drive is desirable.
A method, according to one embodiment, includes: establishing a wireless connection between a wireless receiver in a solid state drive and a mobile device, receiving configuration instructions from the mobile device via the wireless connection, sending the received configuration instructions to a processor in a second device via a physical electrical connection coupling the second device to the solid state drive, receiving data from the second device via the physical electrical connection coupling the second device to the solid state drive, and storing the data in a memory of the solid state drive according to the received configuration instructions.
A method, according to another embodiment, includes: establishing a wireless connection between a wireless receiver in a solid state drive and a mobile device, and sending configuration instructions to the wireless receiver in the solid state drive via the wireless connection. Moreover, the wireless connection between the wireless receiver in the solid state drive and the mobile device is only usable to send configuration instructions.
A system, according to yet another embodiment, includes: a solid state drive which includes: a wireless receiver, and a physical connection port. The physical connection port of the solid state drive establishes a physical electrical connection between the wireless receiver and a processor in a second device. Moreover, the solid state drive establishes a wireless connection with an electrical device, and the solid state drive sends configuration instructions received by the wireless receiver from the electrical device to the processor in the second device. Furthermore, the solid state drive receives data from the second device physically connected to the solid state drive via the physical connection port.
Other aspects and advantages of the present invention will become apparent from the following detailed description, which, when taken in conjunction with the drawings, illustrate by way of example the principles of the invention.
The following description is made for the purpose of illustrating the general principles of the present invention and is not meant to limit the inventive concepts claimed herein. Further, particular features described herein can be used in combination with other described features in each of the various possible combinations and permutations.
Unless otherwise specifically defined herein, all terms are to be given their broadest possible interpretation including meanings implied from the specification as well as meanings understood by those skilled in the art and/or as defined in dictionaries, treatises, etc.
It must also be noted that, as used in the specification and the appended claims, the singular forms “a,” “an” and “the” include plural referents unless otherwise specified.
The following description discloses several preferred embodiments of improved storage drive management, and/or related systems and methods. Accordingly, some of the embodiments described herein may be able to increase the ease of access for verified users and thereby increase task efficiency by implementing wireless storage drive management, as will be described in further detail below.
In one general embodiment, a method includes: establishing a wireless connection between a wireless receiver in a solid state drive and a mobile device, receiving configuration instructions from the mobile device via the wireless connection, sending the received configuration instructions to a processor in a second device via a physical electrical connection coupling the second device to the solid state drive, receiving data from the second device via the physical electrical connection coupling the second device to the solid state drive, and storing the data in a memory of the solid state drive according to the received configuration instructions.
In another general embodiment, a method includes: establishing a wireless connection between a wireless receiver in a solid state drive and a mobile device, and sending configuration instructions to the wireless receiver in the solid state drive via the wireless connection. Moreover, the wireless connection between the wireless receiver in the solid state drive and the mobile device is only usable to send configuration instructions.
In yet another general embodiment, a system includes: a solid state drive which includes: a wireless receiver, and a physical connection port. The physical connection port of the solid state drive establishes a physical electrical connection between the wireless receiver and a processor in a second device. Moreover, the solid state drive establishes a wireless connection with an electrical device, and the solid state drive sends configuration instructions received by the wireless receiver from the electrical device to the processor in the second device. Furthermore, the solid state drive receives data from the second device physically connected to the solid state drive via the physical connection port.
General Computing Concepts
The description herein is presented to enable any person skilled in the art to make and use the invention and is provided in the context of particular applications of the invention and their requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
In particular, various embodiments of the invention discussed herein are implemented using the Internet as a means of communicating among a plurality of computer systems. One skilled in the art will recognize that the present invention is not limited to the use of the Internet as a communication medium and that alternative methods of the invention may accommodate the use of a private intranet, a Local Area Network (LAN), a Wide Area Network (WAN) or other means of communication. In addition, various combinations of wired, wireless (e.g., radio frequency) and optical communication links may be utilized.
The program environment in which one embodiment of the invention may be executed illustratively incorporates one or more general-purpose computers or special-purpose devices such hand-held computers. Details of such devices (e.g., processor, memory, and data storage, input and output devices) are well known and are omitted for the sake of clarity.
It should also be understood that the techniques of the present invention might be implemented using a variety of technologies. For example, the methods described herein may be implemented in software running on a computer system, or implemented in hardware utilizing one or more processors and logic (hardware and/or software) for performing operations of the method, application specific integrated circuits, programmable logic devices such as Field Programmable Gate Arrays (FPGAs), and/or various combinations thereof. In one illustrative approach, methods described herein may be implemented by a series of computer-executable instructions residing on a storage medium such as a physical (e.g., non-transitory) computer-readable medium. In addition, although specific embodiments of the invention may employ object-oriented software programming concepts, the invention is not so limited and is easily adapted to employ other forms of directing the operation of a computer.
The invention can also be provided in the form of a computer program product comprising a computer readable storage or signal medium having computer code thereon, which may be executed by a computing device (e.g., a processor) and/or system. A computer readable storage medium can include any medium capable of storing computer code thereon for use by a computing device or system, including optical media such as read only and writeable CD and DVD, magnetic memory or medium (e.g., hard disk drive, tape), semiconductor memory (e.g., FLASH memory and other portable memory cards, etc.), firmware encoded in a chip, etc.
A computer readable signal medium is one that does not fit within the aforementioned storage medium class. For example, illustrative computer readable signal media communicate or otherwise transfer transitory signals within a system, between systems e.g., via a physical or virtual network, etc.
As shown in
In use, the gateway 101 serves as an entrance point from the remote networks 102 to the proximate network 108. As such, the gateway 101 may function as a router, which is capable of directing a given packet of data that arrives at the gateway 101, and a switch, which furnishes the actual path in and out of the gateway 101 for a given packet.
Further included is at least one data server 114 coupled to the proximate network 108, and which is accessible from the remote networks 102 via the gateway 101. It should be noted that the data server(s) 114 may include any type of computing device/groupware. Coupled to each data server 114 is a plurality of user devices 116. Such user devices 116 may include a desktop computer, laptop computer, hand-held computer, printer or any other type of logic. It should be noted that a user device 111 may also be directly coupled to any of the networks, in one embodiment.
A peripheral 120 or series of peripherals 120, e.g. facsimile machines, printers, networked storage units, etc., may be coupled to one or more of the networks 104, 106, 108. It should be noted that databases, servers, and/or additional components may be utilized with, or integrated into, any type of network element coupled to the networks 104, 106, 108. In the context of the present description, a network element may refer to any component of a network.
According to some approaches, methods and systems described herein may be implemented with and/or on virtual systems and/or systems which emulate one or more other systems, such as a UNIX system which emulates a MAC OS environment, a UNIX system which virtually hosts a MICROSOFT WINDOWS environment, a MICROSOFT WINDOWS system which emulates a MAC OS environment, etc. This virtualization and/or emulation may be enhanced through the use of VMWARE software, in some embodiments.
In more approaches, one or more networks 104, 106, 108, may represent a cluster of systems commonly referred to as a “cloud.” In cloud computing, shared resources, such as processing power, peripherals, software, data processing and/or storage, servers, etc., are provided to any system in the cloud, preferably in an on-demand relationship, thereby allowing access and distribution of services across many computing systems. Cloud computing typically involves an Internet or other high speed connection (e.g., 4G LTE, fiber optic, etc.) between the systems operating in the cloud, but other techniques of connecting the systems may also be used.
The workstation shown in
The workstation may have resident thereon an operating system such as the Microsoft WINDOWS Operating System (OS), a MAC OS, a UNIX OS, etc. It will be appreciated that a preferred embodiment may also be implemented on platforms and operating systems other than those mentioned. A preferred embodiment may be written using JAVA, XML, C, and/or C++ language, or other programming languages, along with an object oriented programming methodology. Object oriented programming (OOP), which has become increasingly used to develop complex applications, may be used.
Moreover, a system according to various embodiments may include a processor and logic integrated with and/or executable by the processor, the logic being configured to perform one or more of the process steps recited herein. By integrated with, what is meant is that the processor has logic embedded therewith as hardware logic, such as an application specific integrated circuit (ASIC), a FPGA, etc. By executable by the processor, what is meant is that the logic is hardware logic; software logic such as firmware, part of an operating system, part of an application program; etc., or some combination of hardware and software logic that is accessible by the processor and configured to cause the processor to perform some functionality upon execution by the processor. Software logic may be stored on local and/or remote memory of any memory type, as known in the art. Any processor known in the art may be used, such as a software processor module and/or a hardware processor such as an ASIC, a FPGA, a central processing unit (CPU), an integrated circuit (IC), a graphics processing unit (GPU), etc.
As previously mentioned, management of storage drives involves implementing formatting changes, and in some instances, removing a drive altogether, e.g., for replacement. Conventionally, storage drive management is performed using host operating systems which require being physically logged into the operating system of the storage drive itself in order to make any such changes. However, this is undesirable, as the operating system may not be configured to receive drive management commands from a user at the storage location. For instance, the operating system may not include a keyboard, a display screen, a mouse, etc. Thus, the ability to perform storage drive management operations via a wireless connection to the storage drive is desirable.
In sharp contrast to the conventional shortcomings described above, various embodiments described herein enable storage drive management without actually being logged into the physical operating system of the storage drive itself. Thus, storage drive management may be performed without physically being at a terminal of the storage drive. In other words, storage drive management may be enabled using a wireless interface into a server associated with one or more storage drives, as will be described in further detail below.
Looking to
Computer system 300 includes a storage drive 302 and a server 304. The storage drive 302 and server 304 are preferably electrically coupled to each other, e.g., such that electrical signals may be transmitted therebetween when the storage drive 302 is engaged with the server 304. In some approaches, the storage drive 302 and server 304 may be electrically coupled via a physical connection formed when a physical connection port 316 (e.g., interface connector) of the storage drive 302 is coupled to a corresponding receiving physical connection port 318 of the server 304. Although the storage drive 302 and server 304 are illustrated in the present embodiment as having a small separation between their respective physical connection ports 316, 318, the two may be physically coupled together by engaging the physical connection ports 316, 318, as would be apparent by one skilled in the art. However a physical connection between the storage drive 302 and the server 304 may be formed by a cable, a wire, a physical network connection (e.g., an Ethernet cable), etc., in other approaches.
It should also be noted that the server 304 may also be coupled to a wireless network 306. Network 306 may be a wireless personal area network (WPAN), a LAN, a WAN, a global area network (GAN), etc., or other types of wireless networks. In addition, various combinations of wired, wireless (e.g., radio frequency) and optical communication links may be utilized to form the overall network 306. Thus, network 306 may be electrically coupled to various other components of computer system 300 and/or other systems physically separated therefrom.
The storage drive 302 is also preferably configured such that it may establish a wireless connection with an electrical device 308, e.g., when in close enough proximity. The wireless device may establish a wireless connection with the storage drive 302 by performing the steps of a predetermined protocol (e.g., see method 600 below). According to various approaches, the wireless connection may be established between the electrical device 308 and storage drive 302 using any desired protocol, e.g., including Bluetooth, near field communication (NFC), WiFi Direct, etc.
It should also be noted that the storage drive 302 may be of any desired type. According to some approaches, the storage drive 302 may be a SSD, but in other approaches, the storage drive 302 may be a hard disk drive (HDD), a random access memory (RAM) drive, etc. To provide a context, and solely to assist the reader, various embodiments may be described with reference to a SSD. This has been done by way of example only, and should not be deemed limiting on the invention. Furthermore, it should be noted that more than one storage drive may be implemented in other embodiments. For example, at least a second storage drive may be included in the computer system 300. Accordingly, the second storage drive, along with any others, may be coupled to the server 304, e.g., using supplemental physical connection ports. Moreover, the second storage drive, along with any other storage drives, would preferably be configured to establish a wireless connection with an electrical device 308 according to any of the approaches described herein.
Referring still to
Looking momentarily to
Returning to computer system 300 of
In some approaches the processor 312 may be configured to perform configuration instructions received by the wireless receiver 310. In other approaches, a processor on the storage drive 302 (e.g., see controller chip 408 of
Referring still to
The components included in the computer system 300 of
Although
As shown in
In some approaches, the SSD may continuously search for the presence of a nearby electrical device when powered on. However, in other approaches, the detecting capability of the SSD may be deactivated (e.g., turned off) as desired, e.g., to save power, while operating conditions are normal, during periods of high storage drive throughput, etc.
The effective detection range of the SSD may vary depend on a signal strength of a wireless receiver included therein, a wireless signal protocol type being used to make the detection, surrounding conditions, predetermined settings, etc. Moreover, as previously mentioned, the electrical device may include a type of mobile device, e.g., such as a cell phone, a tablet with wireless capability, a laptop with a wireless antenna and/or card, etc., depending on the desired approach.
Once a detection has been made, operation 504 includes establishing a wireless connection between a wireless receiver in the SSD and the detected electrical device nearby. For reference, refer back to wireless receiver 310 of
With continued reference to
Once received, operation 508 includes sending the received configuration instructions to a processor in a second device via a physical electrical connection coupling the second device to the SSD. Furthermore, operation 510 includes using a processor electrically coupled to the wireless receiver to perform the received configuration instructions. The processor used to perform the received configuration instructions may be positioned in a server to which the SSD is physically coupled, e.g., as shown in
The processor in the server may be physically coupled to the wireless receiver in the SSD by a serial bus path (e.g., see 310-314 of
The processor in the server may also be coupled to various other components in the server itself, or a backplane of the system. Accordingly, the processor may be integrated with the operating system of a storage system managing the SSD, among other things. It follows that the configuration instructions received by the processor from the SSD (which in turn received them wirelessly from the electronic device) may be implemented successfully, and the operating system may also be updated accordingly, e.g., depending on the particular configuration instruction being performed.
Configuration instructions may vary in type depending on the approach. For instance, in one approach, the received configuration instructions may include a drive capability inquiry instruction. According to such an approach, the processor in the server may be configured to provide the electrical device access to vital product data associated with the SSD in response to receiving the drive capability inquiry instruction as would be appreciated by one skilled in the art upon reading the present description.
Vital product data may include information about the SSD that allows the SSD to be administered at a system and/or network level. According to various approaches, vital product data may include a product model number, a unique serial number, product release level, maintenance level, etc., and/or other information specific to the SSD type. Vital product data may also include user-defined information, e.g., such as the building and department location of the SSD. The collection and use of vital product data allows the status of a network or computer system to be understood and service provided more quickly. In other words, the capabilities of a storage drive may be determined by accessing the vital product data associated therewith, and presented to a user accordingly. Vital product data may be stored in memory of the SSD to which it corresponds, a designated location in memory in the server, in memory at a remote location, etc., depending on the desired approach.
In another approach, the received configuration instructions may include a physical remove instruction for a given SSD. As previously mentioned, more than one SSD may be implemented in a given system. For instance, more than one storage drive may be coupled to a server in a given embodiment. Accordingly, removal and/or replacement of certain storage drives may be desired during the lifetime of the server. However, physically removing a storage drive during use may result in data loss, storage drive corruption, system failure, etc., particularly in systems without data retention measures such as redundant array of independent disks (RAID) protection. Accordingly, the processor in the server electrically coupled to the wireless receiver may be configured to power down one or more specific SSDs in response to receiving a physical remove instruction corresponding thereto. Powering down the one or more specific SSDs allow the SSDs to subsequently be physically removed from the system (e.g., detached from a server) without resulting in any data errors and/or damage to the SSD itself.
However, the processor in the server may also be able to delay and/or reject a physical remove instruction in response to determining that the instruction may not be successfully performed. In some approaches, the system may not be configured to remove and/or replace a SSD during normal operation. Thus, the physical remove instruction may be denied outright, or postponed until the system returns to an idle state, is powered down, etc. In other approaches, the SSD specified by the physical remove instruction may currently be in use. Thus, the physical remove instruction may be postponed until the SSD is no longer in use, e.g., currently performing operations. A user may be informed that the physical remove instruction has been denied and/or delayed.
In a further approach, upon receiving the physical remove instruction, the processor in the server may further identify which SSD is to be removed and/or replaced, preferably such that a user (e.g., drive technician) is properly informed. A specific SSD may be identified by activating a light emitting source positioned on the specific SSD, activating an audio source (e.g., speaker) coupled to the specific SSD, displaying a unique identification number corresponding to the specific SSD on the mobile device, etc.
In still other approaches, the configuration instructions received from the electrical device via the wireless connection may include a command to reconfigure the storage structure of the SSD, a request to determine a relative status of the SSD, an order to return a running failure event counter, etc.
Referring again to
As described above, it is preferred that configuration instructions are only transferred between the electrical device and the SSD via the wireless connection therebetween, while data is received by the SSD via a wired (physical) connection. In other words, the wireless receiver of an SSD may not be able (e.g., may not be configured) to receive data to be stored in the SSD at all. Moreover, configuration instructions may only be wirelessly received at the SSD from an electrical device without establishing and/or using a physical connection therebetween, e.g., such as a wire, bus, cable, etc. However, an SSD may also be coupled to a second device via a physical electrical connection. For example, see physical connection ports 316, 318 coupling storage drive 302 and server 304 in
It should also be noted that although operation 512 includes receiving data from a second device to be stored in the SSD, data may also be sent to the second device from the SSD along the physical electrical connection therebetween, e.g., according to a read request. However, again the physical electrical connection coupling the SSD and the second device may not be able to transfer information other than data therebetween. Thus, in preferred approaches, configuration instructions may not be transmitted between the SSD and the second device using the physical electrical connection therebetween.
As mentioned above, the components included in the computer system 300 of
Referring now to
Each of the steps of the method 600 may be performed by any suitable component of the operating environment. For example, in various embodiments, the method 600 may be partially or entirely performed by a controller, a processor, etc., or some other device having one or more processors therein. The processor, e.g., processing circuit(s), chip(s), and/or module(s) implemented in hardware and/or software, and preferably having at least one hardware component may be utilized in any device to perform one or more steps of the method 600. Illustrative processors include, but are not limited to, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc., combinations thereof, or any other suitable computing device known in the art.
As shown in
Moreover optional operation 604 includes selectively initiating a program configured to establish a wireless connection. In some approaches, the program configured to establish the wireless connection may be an application which is selectively launched by a user. However, in other approaches, the program may automatically launch when the mobile device is powered on.
Optional operation 606 includes alerting a user when a potential wireless connection has been detected. The alert may preferably provide basic information related to the storage device with which the potential wireless connection would be made. According to different approaches, the basic information may include a unique identifier corresponding to the storage device, configuration information corresponding to the storage device, status information corresponding to the storage device, etc. The alert may be displayed in visual form on a display screen of the mobile device, and may be accompanied by an audio signal and/or light signal emitted from the mobile device as well.
Method 600 further includes establishing a wireless connection between a wireless receiver in the SSD and the mobile device nearby upon receiving a user's permission to do so. See operation 608. As mentioned above, a user may be alerted when a potential wireless connection has been detected. In some approaches, the wireless connection may only be established upon receiving the user's permission. Thus, a user may form a wireless connection between a mobile device and a select one of the storage drives in a system. According to an example, which is in no way intended to limit the invention, a server may have three SSDs coupled thereto, each of the three SSDs being configured to establish a wireless connection with a mobile device nearby. Although each of the three SSDs may be detected by the mobile device as a potential wireless connection, only one of the SSDs may actually be selected by the user, thereby establishing a wireless connection therebetween.
Security measures may also be implemented during the process of establishing the wireless connection between the wireless receiver in the SSD and the detected mobile device nearby. For example, a password may be required before the wireless receiver in the SSD engages in a wireless handshake with the mobile device. The number and type of security measures implemented in a given embodiment may vary depending on the importance of the data included in the storage drive, user preference, operating procedures, etc.
Moreover, according to various approaches, the wireless connection may be established using any desired protocol, e.g., including Bluetooth, near field communication (NFC), WiFi Direct, etc.
Furthermore, operation 610 includes sending configuration instructions to the wireless receiver in the SSD via the wireless connection. Once the wireless connection between the mobile device and the SSD has been established, configuration information may be sent to the SSD from the mobile device. Once again, it is preferred that the wireless connection between the wireless receiver in the SSD and the mobile device is only usable to send configuration instructions. Thus, data read and/or write requests may not be sent to the wireless receiver in the SSD via the wireless connection. Similarly, the configuration instructions are wirelessly sent to the SSD from the mobile device without using a physical connection between the SSD and the mobile device (e.g., a wire, bus, cable, etc.).
The configuration instructions sent to the SSD from the mobile device may include any of those configuration instructions included herein. Moreover, the configuration instructions may be performed according to any one or more of the processes described herein. For example, the configuration instructions sent to the SSD may include a drive capability inquiry instruction which causes the mobile device to gain access to vital product data associated with the SSD, a physical remove instruction which causes the SSD to be powered down for removal, a SSD storage structure reconfigure instruction, etc., depending on the desired embodiment.
It follows that various embodiments described herein may enable an improved process of managing storage drives, e.g., such as enterprise class SSDs, over conventional implementations which can only perform management functions after establishing host access. Again, any of the processes herein may be implemented in order to establish a wireless connection between an electrical device (e.g., a mobile device) and a storage drive, preferably such that the electrical device may be used to wirelessly configure the storage drive depending on the desired embodiment. As a result, the improved storage drive management processes described herein are able to increase the ease of access for verified users and thereby increase task efficiency by implementing wireless storage drive management. Moreover, the processes described herein are able to provide the improvements of assuring communication with a particular drive, while enabling drive capability detection and/or removal.
The inventive concepts disclosed herein have been presented by way of example to illustrate the myriad features thereof in a plurality of illustrative scenarios, embodiments, and/or implementations. It should be appreciated that the concepts generally disclosed are to be considered as modular, and may be implemented in any combination, permutation, or synthesis thereof. In addition, any modification, alteration, or equivalent of the presently disclosed features, functions, and concepts that would be appreciated by a person having ordinary skill in the art upon reading the instant descriptions should also be considered within the scope of this disclosure.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of an embodiment of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
| Number | Name | Date | Kind |
|---|---|---|---|
| 8046504 | Feinberg | Oct 2011 | B2 |
| 8966601 | Green | Feb 2015 | B2 |
| 9118887 | Okuhara | Aug 2015 | B2 |
| 9686436 | Sato | Jun 2017 | B2 |
| 9888451 | Ido | Feb 2018 | B2 |
| 20160179424 | Sato | Jun 2016 | A1 |
| 20160321011 | Sato | Nov 2016 | A1 |
| 20170017428 | Salessi | Jan 2017 | A1 |
| 20170099646 | Ido | Apr 2017 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20180165028 A1 | Jun 2018 | US |
