Removable storage device and method for identifying drive letter of the removable storage device

1. Technical Field

Embodiments of the present disclosure generally relate to storage devices, and more particularly to a removable storage device and a method for identifying an assigned drive letter of the removable storage device.

2. Description of Related Art

Usually, if more than one removable storage device are connected to a computing device, it is difficult to identify associations of the storage devices and drive letters assigned to the storage devices. For example, if there are four removable storage devices connected to the computing device, and the drive letters assigned by an operating system of the computing device are “E”, “F”, “G”, and “H”, without drive letters being displayed on the devices, it is difficult to easily identify which device corresponds to which drive letter.

FIG. 1 is a block diagram of a first embodiment of a removable storage device including an identifying unit.

FIG. 2 is a block diagram of a second embodiment of a removable storage device including an identifying unit.

FIG. 3 is a block diagram of one embodiment of function modules of the identifying unit.

FIG. 4 is a flowchart of one embodiment of a method for identifying an assigned drive letter of the removable storage device.

The application is illustrated by way of examples and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean at least one.

In general, the word “module”, as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language, such as, Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware, such as in an EPROM. The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of non-transitory computer-readable medium or other storage device. Some non-limiting examples of non-transitory computer-readable media include CDs, DVDs, BLU-RAY, flash memory, and hard disk drives.

FIG. 1 is a block diagram of a first embodiment of a removable storage device 1 (hereinafter “the device 1 ”) and FIG. 2 is a block diagram of a second embodiment of the device 1 . The difference between the first embodiment and the second embodiment is that the first embodiment of FIG. 1 includes a screen 30 built into the device 1 , and in the second embodiment, the screen 30 is omitted, but a peripheral display device 3 is connected to the device 1 . In both embodiments the device 1 includes an identifying unit 10 for identifying an assigned drive letter of the device 1 . One or more of the device 1 can be electrically connected to a computing device 2 through a universal serial bus (USB) port (not shown), for example. The device 1 may be a USB flash disk, a mobile hard disk, or similar removable device. The device 1 further includes a storage unit 20 and a processor 40 .

The drive letter is assigned to the device 1 by an operating system of the computing device 2 when the device 1 is connected to the computing device 2 . The drive letter, as an example, may be A, B, C.

In one embodiment, the identifying unit 10 may include one or more function modules (detailed description is given in FIG. 3 ). The one or more function modules may comprise computerized code in the form of one or more programs that are stored in the storage unit 20 , and executed by the processor 40 of the device 1 to provide the functions of the identifying unit 10 described later. The storage unit 20 may be a cache or a memory, such as an EPROM or flash memory.

FIG. 3 is a block diagram of one embodiment of the function modules of the identifying unit 10 . In one embodiment, the identifying unit 10 includes an acquirement module 100 , an analysis module 200 , and a display module 300 .

The acquirement module 100 is operable to acquire information about the device 1 from the computing device 2 . The information about the device 1 may include a name, an identification (ID), and the drive letter assigned by the operating system of the computing device 2 . In one embodiment, device drivers of the operating system that correspond to the USB ports start when the computing device 2 starts. The device drivers monitor the computing device 2 and acquire the assigned drive letter of the device 1 when the device 1 is connected to the computing device 2 . The drivers package the assigned drive letter, the name, and the ID in a data structure, and then send the data structure to the acquirement module 100 . The data structure is an organizational form of data transmitted between the drivers and the device 1 . Any data can be packaged and written into the data structure.

The analysis module 200 is operable to analyze the received data structure to retrieve the drive letter assigned to the device 1 . In one embodiment, the received data structure may comprise definitions as shown below:

where the above definition “drive_letter[2]” is regarding the drive letter assigned to the device 1 .

The display module 300 is operable to display the drive letter of the device 1 on the screen 30 or the display device 3 .

FIG. 4 is a flowchart of one embodiment of a method for identifying an assigned drive letter of the device 1 . Depending on the embodiment, additional blocks may be added, others removed, and the ordering of the blocks may be changed.

In block S 10 , the acquirement module 100 acquires information about the device 1 from the computing device 2 . The information about the device 1 may include a name, an ID, and the drive letter assigned by the operating system of the computing device 2 . In one embodiment, device drivers of the operating system that correspond to the USB ports start when the computing device 2 starts. The device drivers monitor the computing device 2 and acquire the assigned drive letter of the device 1 when the device 1 is connected to the computing device 2 . The drivers package the assigned drive letter, the name, and the ID in a data structure, and then send the data structure to the acquirement module 100 .

In block S 12 , the analysis module 200 analyzes the received data structure to retrieve the drive letter assigned to the device 1 .

In block S 14 , the display module 300 displays the drive letter of the device 1 on the screen 30 or the display device 3 .

Although certain inventive embodiments of the present disclosure have been specifically described, the present disclosure is not to be construed as being limited thereto. Various changes or modifications may be made to the present disclosure beyond departing from the scope and spirit of the present disclosure.