CN115705146A - Storage device - Google Patents

Abstract

The present disclosure provides a storage device including a control unit and a storage unit. The control unit is electrically connected to a host. The storage unit is connected with the control unit and comprises a first naming space and a second naming space which are arranged independently. Wherein the first namespace is controlled by the control unit to store a data. Wherein the second namespace includes a small operating system controlled by the control unit to configure and execute a boot operation of the host and execute an operation function on the data of the first namespace.

Description

Storage device

Technical Field

The present disclosure relates to a storage device, and more particularly, to a storage device with a related small operating system that can be independently booted and executed, and can perform an operation function of the storage device, thereby implementing multiple applications of the storage device.

Background

With the development of computer technology, memory devices have become indispensable components. The storage device can also be used for planning multiple applications according to different operating systems or personalized requirements of users. For example, a Solid-state disk (SSD) of Non-Volatile Memory express (NVMe) is taken as an example, more than one logical space can be executed in the same physical disk space through a specification of a namespace (namespace), and the logical spaces shown in the specification can be regarded as individual storage devices for users to use more variously.

The recovery and backup of data are very important for users, and when data is lost or damaged, if the storage device can support the function of recovering data, it will help the system to return to normal operation situation as soon as possible. Generally, the storage device mainly has two triggering modes for backup and restore, which are respectively triggered by hardware or software, and if the triggering mode is a hardware mode, additional design must be performed on the system, which increases cost unnecessarily; if the system software command is adopted for triggering, the system can not be used when the system is crashed, and the backup or recovery function can not be further completed.

In view of the above, it is necessary to provide a storage device, which utilizes the existing namespace function to implement a small operating system with related independent booting execution and to execute the operating function of the storage device, so as to implement multi-application of the storage device, and to solve the drawbacks of the prior art.

Disclosure of Invention

An object of the present disclosure is to provide a storage device. Two namespaces are designed in a storage unit of the storage device, wherein one space is a capacity magnetic area which normally runs, and the other space is a preset bootable small operating system such as an Extensible Firmware Interface (EFI) or Windows PE (WinPE), and can issue commands to a control unit of the storage device to execute, including backup, restoration, detection, reading of storage device information, firmware updating and the like. When the storage device is connected to a host through, for example, peripheral component interconnect Express (PCI Express, PCIe), the control unit of the storage device may receive an instruction from the host to perform an access operation on data on the storage device, and the storage device may also receive a trigger instruction to start a preset small operating system, thereby implementing multiple applications of the storage device. The small operation system is preset in the other name space of the memory device, so that the capacity of normally storing data is not affected, and when the operation system of the host computer is broken down, the user can still provide an instruction to start the small operation system through cold boot to execute the operation function of the memory device, and the user does not need to additionally increase hardware and install software.

Another object of the present disclosure is to provide a memory device. Two namespaces are planned by combining the function of a Non-Volatile Memory quick interface (NVMe) namespace, wherein one is a user space for storing data of a user, and the other is preset with a small operating system such as an EFI or WinPE operating system and the like, and can independently execute startup and run related software functions. Thus, the storage device can be self-contained with an associated independently bootable execution system. The memory device can execute the relevant specific functions by its own system, thereby reducing the number of Out-of-Band (OOB) modules or additional hardware designs of the external device, and eliminating the need to prepare an external USB flash disk as a boot system to execute the relevant functions. The control unit of the storage device can identify the received command, automatically select to access data in the first naming space, or trigger and start a small-sized operating system preset in the second naming space, execute the starting operation of the host and execute an operation function on the storage device. The user can completely execute the special application or the firmware setting through the interface provided by the small operating system of the second namespace without adding extra burden on hardware or software, namely, without installing any software or adding any hardware. Moreover, each file in the second namespace is, for example, a read-only file and is write-resistant, so that the second namespace can safely and stably exert the performance of the small operating system. If the control unit does not receive the trigger instruction to start the small operating system in the second namespace, the small operating system in the second namespace does not interfere the user to access the first namespace through the control unit, and does not affect the access operation of the data in the storage device.

To achieve the foregoing objective, the present disclosure provides a memory device including a control unit and a memory unit. The control unit is electrically connected to a host. The storage unit is connected with the control unit and comprises a first naming space and a second naming space which are arranged independently. Wherein the first namespace is controlled by the control unit to store a data. Wherein the second namespace includes a small operating system controlled by the control unit to configure and execute a boot operation of the host and execute an operation function on the data of the first namespace.

In one embodiment, the small operating system includes an Extensible Firmware Interface (EFI) or Windows PE (WinPE) operating system.

In one embodiment, the storage device and the host are connected by a communication transport that conforms to the peripheral component interconnect Express (PCIe) specification.

In one embodiment, the operation function is one selected from the group consisting of a storage device backup function, a storage device restore function, a storage device detect function, a storage device write protect function, a storage device de-write protect function, and a storage device firmware update function.

In one embodiment, the first namespace has a data access partition and a data hiding partition, the data is disposed in the data access partition for the control unit to access, and the data hiding partition is used for backing up the data in the data access partition.

In one embodiment, the space size of the data access partition is equal to the space size of the data hiding partition.

In one embodiment, each file in the second namespace is a read-only file.

In one embodiment, the control unit executes the mini operating system when receiving a trigger command transmitted from the host, wherein the trigger command is one selected from the group consisting of a general purpose input output signal, a cold boot signal, an application trigger signal, and a hot plug signal.

In one embodiment, the first namespace is a user space and the second namespace is a reserved space.

In one embodiment, the storage device is a Non-Volatile Memory Express (NVMe) solid state drive.

Drawings

Fig. 1 is a schematic diagram of a storage device connected to a host according to a first embodiment of the disclosure.

Fig. 2 is a schematic diagram of a storage device connected to a host according to a second embodiment of the disclosure.

Description of reference numerals:

1. 1a: storage device

10: control unit

20: memory cell

21: first name space

211: data access partition

212: data hidden partition

22: second namespace

31: data

32: small-sized operation system

33: backing up data

2: main unit

Detailed Description

Some exemplary embodiments that incorporate the features and advantages of the present disclosure will be described in detail in the specification which follows. It is to be understood that the disclosure is capable of various modifications in various embodiments without departing from the scope of the disclosure, and that the description and drawings are to be regarded as illustrative in nature, and not as restrictive. For example, the following description of the present disclosure describes the placement of a first feature over or on a second feature, including embodiments in which the first and second features are placed in direct contact, and also includes embodiments in which additional features can be placed between the first and second features, such that the first and second features may not be in direct contact. In addition, repeated reference characters and/or designations may be used in various embodiments of the disclosure. These repetitions are for simplicity and clarity and are not intended to limit the relationship between the various embodiments and/or the appearance structures. Furthermore, spatially relative terms, such as "under", "below", "lower", "above", "upper" and the like, may be used herein for convenience in describing the relationship of one element or feature to another element(s) or feature(s) in the figures. Spatially relative terms are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. The device may also be otherwise positioned (e.g., rotated 90 degrees or at other orientations) and the spatially relative descriptors used should be interpreted accordingly. Further, when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the disclosure are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. In addition, it is to be understood that although the terms "first", "second", "third", etc. may be used in the claims to describe various elements, these elements should not be limited by these terms, and the elements described in the embodiments are denoted by different reference numerals. These terms are for the respective different components. For example: a first component may be termed a second component, and similarly, a second component may be termed a first component without departing from the scope of embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. Except in the operating/working examples, or unless explicitly stated otherwise, all numerical ranges, amounts, values and percentages disclosed herein (e.g., those percentages of angles, time durations, temperatures, operating conditions, ratios of amounts, and the like) are to be understood as modified in all embodiments by the term "about" or "substantially". Accordingly, unless indicated to the contrary, the numerical parameters set forth in the present disclosure and attached claims are approximations that may vary as desired. For example, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding principles. Ranges may be expressed herein as from one end point to the other end point or between the two end points. All ranges disclosed herein are inclusive of the endpoints unless otherwise specified.

Fig. 1 is a schematic diagram of a storage device connected to a host according to a first embodiment of the disclosure. The storage device 1 comprises a control unit 10 and a storage unit 20. The control unit 10 is electrically connected to a host 2. The storage unit 20 is connected to the control unit 10 and includes a first namespace 21 and a second namespace 22, the first namespace 21 is, for example, a user space, and the second namespace 22 is, for example, a reserved space and is independent of each other. In the present embodiment, the first namespace 21 is controlled by the control unit 10 to store a data 31. In the present embodiment, the second namespace 22 includes a small operating system 32 controlled by the control unit 10, configured to perform a boot operation of the host 2 and perform an operation function on the data 31 in the first namespace 21.

In the embodiment, the storage device 1 and the host 2 can be connected through communication transmission such as peripheral component interconnect Express (PCI Express, PCIe), and the control unit 10 can receive an operation command from the host 2 to access the first namespace 21 in the storage unit 20, and can also receive a trigger command from the host 2 to start executing the mini os 32 in the second namespace 22, execute the boot operation of the host 2, and execute an operation function on the data 31 in the first namespace 21.

To be further described, in the embodiment, the storage unit 20 of the storage device 1 is divided into a first namespace 21 for storing the data 31 and a second namespace 22 for installing the small operating system 32, wherein the first namespace 21 and the second namespace 22 are controlled by the control unit 10. In an embodiment, under a normal condition, when the host 2 transmits an operation command to the control unit 10 of the storage device 1, the control unit 10 only needs to access the data 31 in the first namespace 21, and on the other hand, since the mini os 32 is preset in the second namespace 22 of the storage device 1, the user can start to execute the function operation or special setting of the mini os 32 by providing a trigger command through a manner such as, but not limited to, a cold boot, or select to enter the second namespace 22 through a Basic Input/Output System (BIOS) on the host 2, so that the mechanism of starting the mini os 32 preset in the second namespace 22 to perform the function operation or special setting is triggered, which does not need to increase the cost of hardware, and can reduce the development time and labor power of the special application software/firmware.

In the embodiment, the storage device 1 is, for example, a Solid-state disk (SSD) of Non-Volatile Memory Express (NVMe). The first namespace 21 of the storage unit 20 is, for example, a user space with a capacity of 1TB, and is used for storing the data 31. The second namespace 22 of the storage unit 20 is, for example, a reserved space with a capacity of 100MB, i.e. a mini operating system 32 including a Windows PE (WinPE) operating system or an Extensible Firmware Interface (EFI) can be preset. In other embodiments, the size and the ratio of the first namespace 21 and the second namespace 22 can be varied according to the actual application requirement, and the disclosure is not limited thereto.

In addition, in the present embodiment, the control unit 10 of the storage device 1 executes the mini operating system 32 of the second namespace 22 when receiving the trigger command transmitted by the host 2. The trigger command may be, for example, one selected from a group consisting of a General Purpose Input/Output (GPIO) signal, a cold boot signal, an application trigger signal, and a hot plug signal, but the disclosure is not limited thereto. In another embodiment, the trigger command may also include a trigger signal generated by a software application executing on the host 2. In the embodiment, when the user performs a cold boot of the host 2 while using the storage device 1, a cold boot signal is generated, wherein the cold boot signal can be triggered by a system of the host 2 during the cold boot. Then, the control unit 10 of the storage apparatus 1 receives a cold boot signal from the system of the host 2. Thereafter, the control unit 10 loads the mini-OS 32 and reports back a portion of the second namespace 22 of the host 2 for system utilization by the host 2. The mini os 32 may include, for example and without limitation, an Extensible Firmware Interface (EFI) or a WinPE os, and through a tool or an interface provided by the mini os 32, a user may execute the host 2 and send a support command to the control unit 10 to trigger the control unit 10 to perform a functional operation on the data 31 in the first namespace 21, for example, an Extensible Firmware Interface (EFI) is taken as an example, and the implementation manner thereof may be through an EFI Shell of the EFI, so as to achieve the purpose of interaction between the user and the control unit 10, and the command and operation manner of the EFI Shell are well known to those skilled in the relevant art, and thus, will not be described herein again.

In the present embodiment, the operation function executed by the control unit 10 includes one selected from the group consisting of a storage device backup function, a storage device restore function, a storage device check function, a storage device write protect function, and a storage device firmware update function. The user can perform different operation functions on the first namespace 21 in the storage unit 20 by performing operation functions through a command string provided in the second namespace 22, for example, provided by EFI Shell. When the operation functions are completed, the small operating system 32 is exited, and the system of the host 2 is re-entered to warm boot. After the warm boot is completed, the storage device 1 reports the first namespace 21 of 1TB for the user to access the data 31. In a preferred embodiment, each file in the second namespace 22, including related files of the small OS 32, is a read-only file, and the second namespace 22 is more write-protected relative to the user of the host 2, so as to ensure that the second namespace 22 can safely and stably perform the performance of the small OS 32.

Fig. 2 is a schematic diagram of a storage device connected to a host according to a second embodiment of the disclosure. In the present embodiment, the memory device 1a is similar to the memory device 1 shown in fig. 1, and the same reference numerals denote the same elements, structures and functions, which are not described herein again. In this embodiment, the storage device 1a is, for example, a NVMe solid state disk. The first namespace 21 of the storage unit 20 is, for example, a user space with a capacity of 1TB for a user to store data 31. The second namespace 22 of the storage unit 20 is, for example, a reserved space with a capacity of 100MB, i.e. the mini-OS 32 can be set up in advance. The small os 32 may include an extensible firmware interface or a WinPE os, and the small os 32 is pre-installed in the second namespace 22 of the storage device 1a before the factory. The original factory can choose to develop a software application under the familiar mini os 32 and install the software application into the second namespace 22, and the disclosure is not limited to the type of the mini os 32, and any device capable of executing the boot operation of the host 2 and performing the operation function on the data 31 of the first namespace 21 is suitable for the disclosure. In a preferred embodiment, each file in the second namespace 22 is a read-only file, which ensures that the second namespace 22 can safely and stably perform the functions of the small OS 32.

In the embodiment, the storage device 1a and the host 2 are connected through a communication transmission such as PCIe specification, and the control unit 10 of the storage device 1a is connected to the storage unit 20, and can receive an operation command from the host 2 to access the first namespace 21 in the storage unit 20, and also can receive a trigger command from the host 2 to start executing the mini-os 32 in the second namespace 22, so as to execute a boot operation of the host 2, and execute an operation function on the data 31 in the first namespace 21.

In the embodiment, the mini os 32 is preset in the second namespace 22 of the storage device 1a, and the user can provide a trigger command of the mini os 32 by, but not limited to, a cold boot of the host 2 to execute a boot operation of the host 2, and start executing the mini os 32 to perform an operation function on the data 31 in the first namespace 21, such as a storage device backup function, a storage device recovery function, a storage device detection function, a storage device write protection function, or a storage device firmware update function, etc., without adding additional hardware or installing additional software to the host 2 or the storage device 1a. In the present embodiment, the trigger command provided to the small os 32 may be a general purpose input/output signal, for example. The user turns on the system connection storage device 1a through the cold boot of the host 2.

In one embodiment, when the system of the host 2 is to be idle for a specific time, for example, 5 seconds, if the user enters the warm boot program without any action, the operating system in the host 2 is executed to complete the boot. After the boot is completed, the host 2 can form a communication connection with the storage apparatus 1a through the PCIe specification, and transmit an operation command to the control unit 10 of the storage apparatus 1a.

In another embodiment, if the user touches any key or specific key connected to the host 2 within a specific time period to generate the general purpose input/output signal, the control unit 10 of the storage device 1a can receive the general purpose input/output signal from the system of the host 2 as the trigger command of the mini os 32. Thereafter, the control unit 10 loads the mini-OS 32 to perform booting operation of the host 2, and reports a portion of the second namespace 22 of the host 2 for the user to utilize. Through the EFI Shell interface or a plurality of software applications in the second namespace 22, for example, the user may control the control unit 10 of the storage device 1 to perform a special operation function, such as a storage device backup function, a storage device restore function, a storage device detection function, a storage device write protection function, or a storage device firmware update function with respect to the first namespace 21, which is not limited by the disclosure. When the user finishes the application of the operation function, the user can exit the small operating system 32, and the system enters warm boot. After the warm boot is completed, the storage device 1a can report the first namespace 21 of 1TB for the user to access the data 31. At this time, the second namespace 22 and the small operating system 32 are in the write-protected state, and each file in the second namespace 22 is a read-only file and does not interfere the user to access the first namespace 21 in the storage unit 20 through the control unit 10. In other words, the small operating system 32 will not affect the user's access operation to the data 31 of the storage device 1a when it is not triggered to boot.

As can be seen from the above, the present disclosure provides the first namespace 21 for accessing the data 31 and the second namespace 22 independent of the first namespace 21, so that the original side of the storage device 1a can pre-install the mini-os 32 and the software applications required by the related applications by using the second namespace 22 in the simplest manner. When the storage node 1a needs to add a function to the firmware to operate the data 31 in the first namespace 21, the small os 32 in the second namespace 22 is triggered by the trigger command, and the firmware needs only a very low modification, which can greatly reduce the development labor and time. For the software application in the storage device 1a, a software engineer can develop and execute the relevant application in the familiar mini-os 32 without having to release versions of different os in comparison with the os used by the host 2 or the user, thereby greatly reducing the development labor and time of the software application. On the other hand, for the user of the storage device 1a, no hardware modification or additional software installation is required during the use, and even if the operating system of the user is damaged and cannot be started, the small operating system 32 of the storage device 1a can be executed to perform special operations, so as to greatly improve the user acceptance. Moreover, each file in the second namespace 22 including the small operating system 32 is, for example, a read-only file, which further ensures that the second namespace 22 can safely and stably perform the performance of the small operating system 32. If the small operating system 32 is not activated, the second namespace 22 does not interfere the user accessing the first namespace 21 through the control unit 10, and does not affect the accessing operation of the storage device 1a to the data 31.

In the present embodiment, the first namespace 21 further has a data access partition 211 and a data hiding partition 212. Wherein the data 31 is disposed in the data access partition 211 for being accessed by the control unit 10, and the data hiding partition 212 is used for backing up the data 31 in the data access partition 211 to form the backup data 33. In this embodiment, the space size of the data access partition 211 is equal to the space size of the data hiding partition 212. In one embodiment, when the user starts the mini operating system 32 pre-installed in the second namespace 22 by the host 2 through a trigger command, the control unit 10 of the storage device 1a executes the booting operation of the host 2 through the mini operating system 32 of the second namespace 22 and executes the backup function of the storage device 1a, the control unit 10 backs up the data 31 in the data access partition 211 in the first namespace 21 to the data hiding partition 212 to form the backup data 33 of the data hiding partition 212. In another embodiment, when the user uses the host 2 to activate the mini os 32 pre-configured in the second namespace 22 by a trigger command, the control unit 10 of the storage device 1a executes the booting operation of the host 2 through the mini os 32 of the second namespace 22, and executes the recovery function of the storage device 1, the control unit 10 recovers the data 31 in the data access partition 211 or the initial state of the data access partition 211 based on the backup data 33 in the data hiding partition 212. In the present embodiment, the first namespace 21 is, for example, a user space with a capacity of 1TB, and the space size of the data access partition 211 is equal to the space size of the data hiding partition 212, for example, 500MB respectively. When the small OS 32 in the second namespace 22 is not activated and the host 2 sends an operation command to the control unit 10 of the storage device 1a, the control unit 10 reports the data access partition 211 of the first namespace 21 for the user to access the data 31. At this time, the backup data 33 in the hidden data partition 212 is hidden, so that the existence of the second namespace 22, the mini os 32 and the hidden data partition 212, which are the data access partition 211 for the host 2 to access the first namespace 21 in the storage unit 20 through the control unit 10, will not be interfered, and the access operation of the user to the data 31 of the storage device 1a will not be affected. Of course, the disclosure is not limited thereto and will not be described in detail.

In summary, the present disclosure provides a storage device. Two namespaces are designed in a storage unit of the storage device, one of the namespaces is a capacity magnetic area which runs normally, and the other space is a small-sized operation system which can be started up in a preset mode, such as an EFI or WinPE operation system, and commands can be issued to a control unit of the storage device to execute the commands, including backup, restoration, detection, reading of information of the storage device, firmware updating and the like. When the storage device is connected to a host through PCIe specification, the control unit of the storage device can receive the command of the host to perform the access operation of the data on the storage device, and the storage device can also receive the trigger command to start the preset small operating system to realize the multi-application of the storage device. Because the small-sized operation system is preset in another name space of the storage device, the capacity of normally storing data is not influenced, and when the operation system of the host computer is crashed, a user can still provide an instruction to start the small-sized operation system by cold starting for example to execute the operation function of the storage device, and the user does not need to additionally increase hardware and install software. A naming space function is specified by combining a quick interface of a nonvolatile memory, two naming spaces are planned, one is a user space for storing data by a user, and the other naming space is preset with a small-sized operating system such as an EFI or WinPE operating system and the like, so that the functions of starting and running related software can be independently executed. Therefore, the storage device can be provided with the relevant independent startup execution system. The self-contained system of the storage device can execute the related specific functions, so that the external OOB module or the additional hardware design is reduced, and an external USB flash disk does not need to be prepared additionally to be used as a starting system to execute the related functions. The control unit of the storage device can identify the received command, automatically select to access data in the first naming space, or trigger and start a small-sized operating system preset in the second naming space, execute the starting operation of the host and execute an operation function on the storage device. The user can completely execute the special application or firmware setting through the interface provided by the small operating system of the second namespace without adding extra burden on hardware or software, namely without installing any software and adding any hardware. Moreover, each file in the second namespace is, for example, a read-only file and is write-resistant, so that the second namespace can safely and stably exert the performance of the small operating system. If the control unit does not receive the trigger instruction to start the small operating system in the second namespace, the small operating system in the second namespace does not interfere the user to access the first namespace through the control unit, and does not affect the access operation of the basic data of the storage device.

Various modifications, changes, variations, and alterations may be made by those skilled in the art without departing from the scope of the present disclosure, which is defined by the claims appended hereto.

Claims (10)

1. A memory device, comprising:

a control unit electrically connected to a host; and

and the storage unit is connected with the control unit and comprises a first naming space and a second naming space which are arranged independently, wherein the first naming space is controlled by the control unit and is used for storing data in a matched mode, the second naming space comprises a small operating system which is controlled by the control unit and is used for executing startup operation of the host computer in a matched mode, and an operation function is executed on the data in the first naming space.

2. The storage device of claim 1, wherein the mini-os comprises an extensible firmware interface or a Windows PE os.

3. The storage device of claim 1, wherein the storage device and the host are connected by a communication transport that conforms to the peripheral component interconnect express specification.

4. The storage device of claim 1, wherein the operation function is one selected from the group consisting of a storage device backup function, a storage device restore function, a storage device detect function, a storage device write protect function, a storage device de-write protect function, and a storage device firmware update function.

5. The storage device as claimed in claim 1, wherein the first namespace has a data access partition and a hidden data partition, the data is located in the data access partition for the control unit to access, the hidden data partition is used to backup the data in the data access partition.

6. The memory device of claim 5, wherein the spatial size of the data access partition is equal to the spatial size of the data hidden partition.

7. The storage device of claim 1, wherein each file in the second namespace is a read-only file.

8. The memory device according to claim 1, wherein the control unit executes the operating system when receiving a trigger command from the host, wherein the trigger command is selected from a group consisting of a general purpose input output signal, a cold boot signal, an application trigger signal, and a hot plug signal.

9. The storage device of claim 1, wherein the first namespace is a user space and the second namespace is a reserved space.

10. The storage device of claim 1, wherein the storage device is a solid state drive of the non-volatile memory express interface specification.

Images