CN113674795B - Testing system and testing method for solid state disk - Google Patents

Abstract

The embodiment of the present invention provides a test system and a test method for a solid-state hard disk. The test system includes: at least one network device; at least one debugging device; at least one solid-state hard disk, wherein: each solid-state hard disk is connected to a network device and a debugging device; at least one network device is connected to a server system through a network, so that the server system operates at least one solid-state hard disk via at least one network device, and the server system is the final application environment of the solid-state hard disk; each debugging device is configured to: monitor the real-time operating status of the solid-state hard disk connected to the debugging device, and generate log data representing the real-time operating status of the solid-state hard disk.

Description

Test system and test method for solid state drive

Technical Field

In general, embodiments of the present invention relate to the field of storage technology, and in particular to a test system and a test method for a solid state drive.

Background technique

SSDs are also called solid-state drives, and usually refer to hard disks made using solid-state electronic storage chip arrays. SSDs have been widely used in various fields because of their advantages such as fast read and write speeds, low damage resistance, low power consumption, and small size.

Usually, before a solid-state drive leaves the factory, it needs to be tested to ensure that it can operate normally after leaving the factory. Therefore, how to test the solid-state drive efficiently and comprehensively has become one of the problems that need to be solved urgently.

Summary of the invention

In view of this, embodiments of the present invention provide a testing system and a testing method for a solid state drive.

On the one hand, an embodiment of the present invention provides a test system for a solid-state hard disk, comprising: at least one network device; at least one debugging device; at least one solid-state hard disk, wherein: each solid-state hard disk is connected to one network device in the at least one network device, and is connected to one debugging device in the at least one debugging device; the at least one network device is connected to a server system through a network, so that the server system operates the at least one solid-state hard disk via the at least one network device, and the server system is the final application environment of the solid-state hard disk; each debugging device is configured to: monitor the real-time operating status of the solid-state hard disk connected to the debugging device, and generate log data representing the real-time operating status of the solid-state hard disk.

In some embodiments, for the first network device, the first network device is any one of the at least one network device: the first network device is a content distribution network device dedicated to the server system or a computer with a network connection function.

In some embodiments, when the first network device is a content distribution network device, the first network device is connected to a corresponding solid-state hard disk in the at least one solid-state hard disk via a universal serial bus interface; when the first network device is a computer, the first network device is connected to a corresponding solid-state hard disk in the at least one solid-state hard disk via a PCIe interface.

In some embodiments, each debugging device is connected to a corresponding solid-state drive of the at least one solid-state drive via a serial interface or a JTAG interface.

In some embodiments, for the first solid-state hard drive, the first solid-state hard drive is any one of the at least one solid-state hard drive: the first solid-state hard drive is configured to have a first storage area and a second storage area, the first storage area can be operated by the server system, and the second storage area cannot be operated by the server system, but can be operated by other devices different from the server system.

In some embodiments, the first solid-state drive is connected to a first debugging device among the at least one debugging device, and the first debugging device is configured to: monitor the real-time operating status of the first storage area, and generate first log data representing the real-time operating status of the first storage area; synchronously monitor the real-time operating status of the second storage area, and generate second log data representing the real-time operating status of the second storage area.

In some embodiments, the server system's operation on the at least one solid-state drive includes at least one of the following: checking the solid-state drive status; formatting the solid-state drive; performing a solid-state drive write operation; performing a solid-state drive read operation; and performing a solid-state drive erase operation.

On the other hand, an embodiment of the present invention provides a testing method implemented by a testing system for a solid-state hard disk, wherein the testing system includes at least one network device, at least one debugging device and at least one solid-state hard disk, wherein each solid-state hard disk is connected to one network device in the at least one network device and to one debugging device in the at least one debugging device, and the at least one network device is connected to a server system via a network, so that the server system operates the at least one solid-state hard disk via the at least one network device, and the server system is the final application environment of the solid-state hard disk, and the method includes: using each debugging device in the at least one debugging device to perform the following operations: monitoring the real-time operating status of the solid-state hard disk connected to the debugging device; generating log data representing the real-time operating status of the solid-state hard disk.

In some embodiments, for the first network device, the first network device is any one of the at least one network device: the first network device is a content distribution network device dedicated to the server system or a computer with a network connection function.

In some embodiments, when the first network device is a content distribution network device, the first network device is connected to a corresponding solid-state hard disk in the at least one solid-state hard disk via a universal serial bus interface; when the first network device is a computer, the first network device is connected to a corresponding solid-state hard disk in the at least one solid-state hard disk via a PCIe interface.

In some embodiments, each debugging device is connected to a corresponding solid-state drive of the at least one solid-state drive via a serial interface or a JTAG interface.

In some embodiments, for the first solid-state hard drive, the first solid-state hard drive is any one of the at least one solid-state hard drive: the first solid-state hard drive is configured to have a first storage area and a second storage area, the first storage area can be operated by the server system, and the second storage area cannot be operated by the server system, but can be operated by other devices different from the server system.

In some embodiments, the first solid-state drive is connected to a first debugging device among the at least one debugging device, and the method further includes: using the first debugging device to monitor the real-time operating status of the first storage area, and generating first log data representing the real-time operating status of the first storage area; using the first debugging device to synchronously monitor the real-time operating status of the second storage area, and generating second log data representing the real-time operating status of the second storage area.

In some embodiments, the server system's operation on the at least one solid-state drive includes at least one of the following: checking the solid-state drive status; formatting the solid-state drive; performing a solid-state drive write operation; performing a solid-state drive read operation; and performing a solid-state drive erase operation.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other objects, features and advantages of the embodiments of the present invention will become more apparent through a more detailed description of the embodiments of the present invention in conjunction with the accompanying drawings, wherein like reference numerals generally represent like elements in the embodiments of the present invention.

FIG. 1 is a schematic block diagram of an application scenario of a test system for a solid state drive according to some embodiments.

FIG. 2 is a schematic block diagram of an example of an application scenario of a test system for a solid state drive.

FIG. 3 is a schematic block diagram of another example of an application scenario of a test system for a solid state drive.

FIG. 4 is a schematic flow chart of a testing method implemented by a testing system for a solid state drive according to some embodiments.

Detailed ways

The subject matter described herein will now be discussed with reference to various embodiments. It should be understood that the discussion of these embodiments is only to enable those skilled in the art to better understand and implement the subject matter described herein, and is not intended to limit the scope of protection, applicability or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of protection of the claims. Various embodiments may omit, replace or add various processes or components as needed.

As used herein, the term "including" and its variations are open terms, meaning "including but not limited to". The term "based on" means "based at least in part on". The terms "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other definitions may be included below, whether explicit or implicit, and the definition of a term is consistent throughout the specification unless the context clearly indicates otherwise.

Generally, solid-state drives need to undergo a series of tests before leaving the factory to ensure normal operation after leaving the factory. At present, when testing solid-state drives, the customer's application environment is usually simulated as much as possible so as to solve the faults and anomalies that may occur in the actual application of the solid-state drive in a targeted manner. However, this test may have some defects. For example, since it may not be possible to fully simulate the customer's application environment, the traditional test process for solid-state drives often stays at a simple functional level and some classic test situations. In addition, when the customer's application environment is updated, updating the corresponding simulated test environment may be difficult to achieve in time on the one hand, and may require a lot of costs on the other hand. Therefore, in some cases, although the solid-state drive has undergone the traditional test process, because the test is not comprehensive enough, there may still be many problems when it is actually used in the customer's application environment, which may not only increase the cost of later maintenance and repair, but also affect the customer's experience.

In view of this, an embodiment of the present invention provides a testing solution for a solid state drive, which will be described below in conjunction with a specific embodiment.

FIG. 1 is a schematic block diagram of an application scenario of a test system for a solid state drive according to some embodiments.

In an embodiment of the present invention, the test system may include at least one network device, at least one debugging device, and at least one solid state hard disk.

Specifically, each SSD can be connected to one of the at least one network device and to one of the at least one debugging device. Then, it can be understood that each network device can be connected to one or more SSDs, and each debugging device can also be connected to one or more SSDs.

At least one network device can be connected to the server system via a network, so that the server system can manipulate at least one solid-state drive via the at least one network device. Here, the server system can be a final application environment of the solid-state drive.

Each debugging device can be configured to monitor the real-time operating status of the solid-state drive connected to the debugging device, and generate log data representing the real-time operating status of the solid-state drive. For example, when the solid-state drive is abnormal, the log data can be used by R&D personnel to analyze the abnormality of the solid-state drive to determine the cause of the abnormality and then resolve the abnormality (e.g., repair the firmware, update the firmware, etc.). Repairing or updating the firmware of the solid-state drive can be achieved through other appropriate devices.

For ease of understanding, in the example of FIG1 , K network devices, M solid state drives, and N debugging devices are shown. Here, K, M, and N may be positive integers. Generally speaking, M may be greater than or equal to K, or greater than or equal to N. In other words, the number of solid state drives may be greater than or equal to the number of network devices, or greater than or equal to the number of debugging devices.

In some implementations, the number of SSDs may be equal to the number of network devices, so each network device may be connected to a SSD. In addition, there may be only one debugging device, so that all SSDs may be connected to the debugging device. This implementation is relatively simple and easy.

As shown in FIG. 1 , the test system 110 may include: network devices 102 - 1 , 102 - 2 , ... , 102 -K; solid state drives 104 - 1 , 104 - 2 , 104 - 3 , ... 104 -M; and debugging devices 106 - 1 , ... , 106 -N.

In addition, for ease of understanding, it is assumed here that solid-state drive 104-1 is connected to network device 102-1 and to debugging device 106-1; it is assumed that solid-state drive 104-2 is connected to network device 102-2 and to debugging device 106-1; it is assumed that solid-state drive 104-3 is connected to network device 102-2 and to debugging device 106-1; it is assumed that solid-state drive 104-M is connected to network device 102-K and to debugging device 106-N.

However, it should be understood that the connection relationship shown here is only an example and does not limit the scope of the present invention. In specific implementation, various connection relationships can be used to achieve the connection between these devices. For example, each network device can be connected to a different number of solid-state hard disks, and each debugging device can also be connected to a different number of solid-state hard disks.

In addition, the network devices 102-1, 102-2, ..., 102-K can be connected to the server system 120 through a network. For example, the network devices 102-1, 102-2, ..., 102-K can be connected to a router via Ethernet, and then the router is connected to the server system 120 via the Internet. The server system 120 can be an application environment of a client, which can generally include multiple servers. It can be understood that the server system 120 is also the final application environment of the solid state drive.

As can be seen from the above, since each solid-state drive 104-1 to 104-M is respectively connected to one of the network devices 102-1 to 102-K, and the network devices 102-1 to 102-K are connected to the server system 120 via the network, the server system 120 can directly operate the solid-state drives 104-1 to 104-M.

The debugging device 106-1 can monitor the real-time operation status of the SSDs 104-1 to 104-3 and generate log data indicating the real-time operation status of the SSDs 104-1 to 104-3. These log data can be used to analyze the cause of the abnormality when an abnormality occurs in the SSDs 104-1 to 104-3.

It can be seen that in the embodiments of the present invention, by using a network device to connect the solid-state drive to the server system where it is ultimately to be used, it is possible to accurately and effectively discover problems that may occur in the solid-state drive during the final application, and then promptly repair the fault or abnormality. It can be seen that this method can comprehensively and efficiently implement solid-state drive testing. In addition, when the customer's server system is updated, the solid-state drive will also run in the updated application environment, which can greatly save the cost of building the application environment compared to the current simulated application environment.

In some embodiments, any one of the network devices 102-1 to 102-K may be implemented using different devices. For ease of description, the network device is referred to as a first network device. The first network device may be a content delivery network (CDN) device dedicated to the server system 120, or the first network device may be an ordinary computer with a network connection function.

In some implementations, the CDN device typically has a Universal Serial Bus (USB) interface. Therefore, when the first network device is a CDN device, it can be connected to a corresponding solid-state hard disk via a USB interface (e.g., a USB 3.0 interface). It should be understood here that the solid-state hard disk can have various types of interfaces, which can be connected to the USB interface of the CDN device through an applicable connection cable.

Of course, the USB interface here is only an example, and the CDN device may also have various interfaces known in the art or new interfaces that may appear in the future to connect with the solid state drive.

In other implementations, if the first network device is an ordinary computer, the first network device can be connected to the corresponding solid-state hard disk via a PCIe (Peripheral Component Interconnect express) interface. It should also be understood here that the solid-state hard disk can have various types of interfaces, which can be connected to the PCIe interface of an ordinary computer through an applicable connection line. Of course, the PCIe interface here is only an example, and the first network device can also be connected to the solid-state hard disk through other types of interfaces.

It can be understood from the above that in some implementations, the at least one network device mentioned above may all be CDN devices dedicated to the server system, that is, the network devices 102 - 1 to 102 -K may all be CDN devices dedicated to the server system 120 .

In some other implementations, the at least one network device may all be ordinary computers with network connection functions, that is, the network devices 102 - 1 to 102 -K may all be ordinary computers.

In other implementations, one or more of the at least one network device may be a CDN device dedicated to the server system, and the remaining network devices may be ordinary computers. That is, one or more of the network devices 102-1 to 102-K may be a CDN device dedicated to the server system 120, and the remaining network devices may be ordinary computers.

When the test system is specifically implemented, these methods may be selected according to various factors such as actual requirements, cost, etc. It can be seen that the embodiments of this document can provide implementation flexibility.

In some embodiments, each debugging device 106-1 to 106-N may be connected to a corresponding solid state drive via various applicable interfaces. For example, each debugging device in the debugging devices 106-1 to 106-N may be connected to a corresponding solid state drive via a serial interface or a JTAG interface.

In some cases, the SSD may be divided into different storage areas. For example, one or more storage areas may be configured to be operable by the server system, while the remaining storage areas may be configured to be inoperable by the server system, so that the storage areas can be tested separately, making the test more comprehensive.

Specifically, any one of the solid state drives 104 - 1 to 104 -M may be tested in a region-by-region manner. For ease of description, it is referred to as the first solid state drive hereinafter.

The first solid-state drive may be configured to have a first storage area and a second storage area. The first storage area may be operated by the server system 120. The second storage area may not be operated by the server system 120, but may be operated by other devices different from the server system 120, such as various operations such as writing, erasing, and uploading of large data (e.g., high-quality multimedia files, etc.).

The configuration of the first solid-state drive can be implemented through appropriate control software. For example, if the network device connected to the first solid-state drive is a CDN device, the first solid-state drive can be configured through CDN software. CDN software can be installed on any smart device, such as a desktop computer, a mobile phone, a tablet device, etc.

Further, assuming that the first solid-state drive is connected to the first debugging device, the first debugging device can monitor the real-time operating status of the first storage area and synchronously monitor the real-time operating status of the second storage area. In addition, the first debugging device can generate first log data representing the real-time operating status of the first storage area, and generate second log data representing the real-time operating status of the second storage area. The first log data can be used to analyze the abnormality of the first storage area, and the second log data can be used to analyze the abnormality of the second storage area.

In some implementations, when an abnormality occurs in the solid-state drive, the network device connected thereto may generate an alarm signal, such as an indicator light turning on, an error message displayed on the screen (if there is a display screen), etc. In addition, the debugging device may also generate an alarm signal, thereby enabling the technician to be informed of the abnormality of the solid-state drive and then resolve the abnormality.

In addition, although in the testing phase, the server system 120 can operate the solid state drives 104-1 to 104-M according to normal usage scenarios. For example, the server system 120 can perform various operations on the solid state drives 104-1 to 104-M, such as checking the state of the solid state drives, formatting the solid state drives, reading setting parameters, performing solid state drive write operations, performing solid state drive read operations, performing solid state drive erase operations, etc.

For ease of understanding, the following description will be given in conjunction with specific examples. It should be understood that the following examples do not limit the scope of protection of the present invention.

FIG. 2 is a schematic block diagram of an example of an application scenario of a test system for a solid state drive.

In the example of FIG2 , the network device is implemented using a CDN device. As shown in FIG2 , the test system 210 may include CDN devices 202 - 1 to 202 -M, solid state drives 204 - 1 to 204 -M, and a debugging device 206 .

It can be seen that in this example, the number of CDN devices is the same as the number of SSDs. In this case, each SSD can be connected to one CDN device. For example, each CDN device can have a USB interface (e.g., a USB 3.0 interface) for connecting a SSD. In addition, SSDs 204-1 to 204-M can all be connected to a debugging device 206. For example, debugging device 206 can have a serial interface or a JTAG interface for connecting SSDs 204-1 to 204-M. It can be understood here that the SSD itself can have multiple types of interfaces, and the connection between it and the CDN device or the debugging device can be achieved through various adapted connection lines.

CDN devices 202-1 to 202-M may be connected to routers 208-1 to 208-X (X may be a positive integer) via Ethernet. Routers 208-1 to 208-X may be connected to server system 220 via the Internet. Server system 220 may be the final application environment of the solid state drive. Server system 220 may include multiple servers. In some cases, server system 220 may include a cloud data center that may control multiple servers. Server system 220 may be implemented in any known manner, and the present invention is not limited thereto.

In this example, CDN devices 202-1 to 202-M may be dedicated to server system 220. As can be seen from the example of Figure 2, server system 220 may operate SSDs 204-1 to 204-M via the Internet, routers 208-1 to 208-X, and CDN devices 202-1 to 202-M. For example, server system 220 may check the status of SSDs 204-1 to 204-M, format these SSDs, perform write operations, read operations, erase operations, and the like.

The debugging device 206 can monitor the real-time operating status of these solid-state drives and generate log data representing the real-time operating status of each solid-state drive.

It can be seen that during the testing process, the solid-state drives 204-1 to 204-M can be regarded as already working in their final application environment. Therefore, problems that may arise in actual use of the solid-state drives can be solved during the testing phase, thereby making the test more comprehensive and enhancing the final product performance of the solid-state drives and improving the customer experience.

FIG. 3 is a schematic block diagram of another example of an application scenario of a test system for a solid state drive.

The example of FIG. 3 is similar to the example of FIG. 2 , except that in the example of FIG. 3 , the network device is implemented using a computer with a network connection function.

For example, as shown in FIG. 3 , the test system 310 may include computers 302 - 1 to 302 -M, solid state drives 304 - 1 to 304 -M, and a debugging device 306 .

Similarly, the number of computers and the number of solid-state drives may be the same. Each solid-state drive may be connected to one computer. For example, computers 302-1 to 302-M may have a PCIe interface for connecting to solid-state drives. Solid-state drives 304-1 to 304-M may all be connected to a debugging device 306. For example, debugging device 306 may have a serial interface or a JTAG interface for connecting to solid-state drives 304-1 to 304-M.

Computers 302-1 to 302-M can be connected to routers 308-1 to 308-X (X can be a positive integer) via Ethernet. Routers 308-1 to 308-X can be connected to server system 320 via the Internet. Server system 320 can be the final application environment of the solid state drive. Server system 320 is similar to server 220 and will not be described in detail here.

The server system 320 can operate the solid state drives 304-1 to 304-M via the Internet, the routers 308-1 to 308-X, and the computers 302-1 to 302-M. For example, the server system 320 can check the status of the solid state drives 304-1 to 304-M, format the solid state drives, perform write operations, read operations, erase operations, etc.

The debugging device 306 can monitor the real-time operating status of these solid-state drives and generate log data representing the real-time operating status of these solid-state drives.

It can be seen that during the testing process, the solid-state drives 304-1 to 304-M can be regarded as already working in their future final application environment. Therefore, problems that may arise when the solid-state drives are actually used can be solved during the testing phase, thereby making the test more comprehensive, enhancing the final product performance of the solid-state drives, and improving the customer experience.

Fig. 4 is a schematic flow chart of a test method implemented by a test system for a solid state drive according to some embodiments. For example, the test method 400 of Fig. 4 may be performed in conjunction with the test system 100 of Fig. 1 .

First, the test system may include at least one network device, at least one debugging device and at least one solid-state drive. Each solid-state drive may be connected to a network device and to a debugging device. At least one network device may be connected to a server system via a network, so that the server system operates at least one solid-state drive via at least one network device. The server system may be the final application environment of the solid-state drive.

As shown in FIG. 4 , in step 402 , each debugging device in at least one debugging device may be used to monitor the real-time operating status of the solid state drive connected to the debugging device.

In step 404, the debugging device may be used to generate log data representing the real-time operating status of the solid state drive.

In some embodiments, for the first network device, the first network device may be any one of the at least one network device: the first network device may be a content distribution network device dedicated to the server system or a computer with a network connection function.

In some embodiments, when the first network device is a content distribution network device, the first network device can be connected to a corresponding solid-state hard disk in at least one solid-state hard disk via a universal serial bus interface. When the first network device is a computer, the first network device can be connected to a corresponding solid-state hard disk in at least one solid-state hard disk via a PCIe interface.

In some embodiments, each debugging device may be connected to a corresponding solid-state drive of the at least one solid-state drive via a serial interface or a JTAG interface.

In some embodiments, for the first solid-state drive, the first solid-state drive may be any one of the at least one solid-state drive:

The first solid state drive may be configured to have a first storage area and a second storage area. The first storage area may be operated by the server system. The second storage area may not be operated by the server system, but may be operated by other devices different from the server system.

In some embodiments, the first solid-state drive may be connected to a first debugging device in at least one debugging device. Method 400 may include: using the first debugging device to monitor the real-time operating status of the first storage area, and generating first log data representing the real-time operating status of the first storage area; using the first debugging device to synchronously monitor the real-time operating status of the second storage area, and generating second log data representing the real-time operating status of the second storage area.

In some embodiments, the server system's operation on at least one solid-state drive may include at least one of the following: checking the solid-state drive status; formatting the solid-state drive; performing a solid-state drive write operation; performing a solid-state drive read operation; and performing a solid-state drive erase operation.

The specific implementation details of method 400 may refer to the embodiments described above with respect to FIGS. 1-3 , and will not be described again here to avoid repetition.

It should be noted that not all steps and units in the above-mentioned processes and system structure diagrams are necessary, and some steps or units can be ignored according to actual needs. The execution order of each step is not fixed and can be determined as needed. The device structure described in the above-mentioned embodiments can be a physical structure or a logical structure, that is, some units may be implemented by the same physical entity, or some units may be implemented by multiple physical entities, or some components in multiple independent devices may be implemented together.

Control unit has been described in conjunction with various devices and methods. The control unit can be implemented using electronic hardware, computer software or any combination thereof. Whether the control unit is implemented as hardware or software will depend on specific application and the overall design constraints imposed on the system. As an example, the control unit provided in the present disclosure, any part of the control unit or any combination of the control unit can be implemented as a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic, a discrete hardware circuit and other suitable processing components configured to perform the various functions described in the present disclosure. The function of the control unit provided in the present disclosure, any part of the control unit or any combination of the control unit can be implemented as software performed by a microprocessor, a microcontroller, a DSP or other suitable platforms.

The above description of the present disclosure is provided to enable any person of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of protection of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is consistent with the widest range of principles and novel features disclosed herein.

Claims (12)

1. A test system for a solid state disk, comprising:

at least one network device;

At least one commissioning device;

at least one solid state disk, wherein:

each solid state disk is connected with one network device in the at least one network device and one debugging device in the at least one debugging device;

The at least one network device is connected with a server system through a network, so that the server system operates the at least one solid state disk through the at least one network device, and the server system is a final application environment of the solid state disk;

each commissioning device is configured to: monitoring the real-time running condition of the solid state disk connected with the debugging equipment, and generating log data representing the real-time running condition of the solid state disk;

For a first solid state disk, the first solid state disk is any one of the at least one solid state disk:

the first solid state disk is configured to have a first storage area and a second storage area,

The first storage area is operable by the server system,

The second storage area may not be operated by the server system, but may be operated by other devices different from the server system.

2. The test system of claim 1, wherein, for a first network device, the first network device is any one of the at least one network device:

The first network device is a content distribution network device dedicated to the server system or a computer having a network connection function.

3. The test system of claim 2, wherein,

When the first network device is a content distribution network device, the first network device is connected with a corresponding solid state disk in the at least one solid state disk through a universal serial bus interface;

and under the condition that the first network equipment is a computer, the first network equipment is connected with the corresponding solid state disk in the at least one solid state disk through a PCIe interface.

4. A test system according to any one of claims 1 to 3, wherein each debug device is connected to a respective solid state disk of the at least one solid state disk via a serial interface or JTAG interface.

5. The test system of claim 1, wherein the first solid state disk is connected to a first one of the at least one debug device,

The first commissioning device is configured to:

Monitoring a real-time operating condition of the first storage area and generating first log data representing the real-time operating condition of the first storage area;

the real-time operating condition of the second storage area is synchronously monitored and second log data representing the real-time operating condition of the second storage area is generated.

6. The test system of any of claims 1-3, wherein operation of the server system on the at least one solid state disk comprises at least one of:

Checking the state of the solid state disk;

Formatting the solid state disk;

executing the writing operation of the solid state disk;

executing a solid state disk reading operation;

And executing the erasing operation of the solid state disk.

7. A test method implemented by a test system for solid state drives, wherein the test system comprises at least one network device, at least one commissioning device, and at least one solid state drive, wherein each solid state drive is connected to one of the at least one network device and to one of the at least one commissioning device, the at least one network device being connected to a server system over a network such that the server system operates the at least one solid state drive via the at least one network device, the server system being a final application environment for the solid state drive, the method comprising:

Using each of the at least one commissioning device:

Monitoring the real-time running condition of a solid state disk connected with the debugging equipment;

Generating log data representing real-time running conditions of the solid state disk;

For a first solid state disk, the first solid state disk is any one of the at least one solid state disk:

the first solid state disk is configured to have a first storage area and a second storage area,

The first storage area is operable by the server system,

The second storage area may not be operated by the server system, but may be operated by other devices different from the server system.

8. The test method of claim 7, wherein, for a first network device, the first network device is any one of the at least one network device:

The first network device is a content distribution network device dedicated to the server system or a computer having a network connection function.

9. The test method according to claim 8, wherein,

When the first network device is a content distribution network device, the first network device is connected with a corresponding solid state disk in the at least one solid state disk through a universal serial bus interface;

and under the condition that the first network equipment is a computer, the first network equipment is connected with the corresponding solid state disk in the at least one solid state disk through a PCIe interface.

10. The test method of any of claims 7-9, wherein each debug device is connected to a respective solid state disk of the at least one solid state disk via a serial interface or a JTAG interface.

11. The test method of claim 7, wherein the first solid state disk is connected to a first debug device of the at least one debug device, the method further comprising:

Monitoring, with the first commissioning device, a real-time operating condition of the first storage region and generating first log data representing the real-time operating condition of the first storage region;

The real-time operating condition of the second storage area is synchronously monitored with the first debug apparatus and second log data representing the real-time operating condition of the second storage area is generated.

12. The test method of any of claims 7-9, wherein the operation of the server system on the at least one solid state disk comprises at least one of:

Checking the state of the solid state disk;

Formatting the solid state disk;

executing the writing operation of the solid state disk;

executing a solid state disk reading operation;

And executing the erasing operation of the solid state disk.