A system and method for out-of-band management of solid-state drives

By using a serial bus link between the device card and the control chip, the problem of ordinary computers being unable to manage NVMe solid-state drives out of band is solved, enabling low-cost NVMe-MI over PCIe VDM message conversion and expanding the range of computers that can be managed.

CN123115022APending Publication Date: 2026-11-17LUANQI TECH (SUZHOU) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611309051.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-27
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In the current technology, ordinary computers cannot perform out-of-band management of NVMe solid-state drives through NVMe-MI over PCIe VDM, and there is a lack of low-cost solutions that do not rely on BMC.

Method used

By using a device card and control chip, transaction layer data packets are directly transmitted to the solid-state drive via a serial bus link, replacing the BMC and realizing bidirectional conversion of NVMe-MI over PCIe VDM messages.

Benefits of technology

This reduces hardware costs and enables ordinary computers with serial bus interfaces to perform out-of-band management, with the transmission path not passing through host memory, thus achieving extensive management capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123115022A_ABST
    Figure CN123115022A_ABST
Patent Text Reader

Abstract

This application relates to a system and method for out-of-band management of solid-state drives (SSDs). The system includes a controller, a device card, and a control chip mounted on the device card. The device card is communicatively connected to the SSD via a serial bus link. The control chip is configured to encapsulate out-of-band management messages into transaction layer data packets based on a target identifier, and transmit the transaction layer data packets to the SSD via the serial bus link; and / or, receive completion messages returned by the SSD and restore them to management response messages, and transmit the management response messages to the controller via the serial bus link. The device card can replace a dedicated BMC, enabling bidirectional conversion of NVMe-MI over PCIe VDM messages, thus reducing hardware costs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of out-of-band management technology for solid-state drives (SSDs), and in particular to a system and method for out-of-band management of SSDs. Background Technology

[0002] MCTP (Management Component Transport Protocol) is used for management communication between a computer host and external devices. It can be carried over various physical media such as SMBus (System Management Bus) and PCIe (Peripheral Component Interconnect Express) bus. In server architectures, the BMC (Baseboard Management Controller) typically serves as the management endpoint of MCTP, performing out-of-band management operations on NVMe solid-state drives (NVMe-MI, Non-Volatile Memory Express Management Interface) via the PCIe Bus.

[0003] Standard desktop and laptop computers do not integrate a BMC module, making it impossible to manage NVMe SSDs out of band via the PCIe Bus. Even on some server motherboards that integrate a BMC, the firmware may not support the NVMe-MI protocol stack, thus preventing the aforementioned management operations. Currently, there is a lack of a low-cost, plug-and-play solution on the market that does not rely on a BMC, allowing any computer to manage NVMe SSDs out of band via NVMe-MI over PCIe VDM (Non-Volatile Memory Express Management Interface over Peripheral Component Interconnect ExpressBus). Summary of the Invention

[0004] The technical problem to be solved by the embodiments of this application is to provide a system and method for out-of-band management of solid-state drives (SSDs). The device card transmits transaction layer data packets directly to the SSD via a serial bus link in a point-to-point manner. The transmission path does not pass through the host memory of the controller. The device card can replace the dedicated BMC to realize bidirectional conversion of NVMe-MI over PCIeVDM messages, reduce hardware costs, and enable ordinary computers with serial bus interfaces to perform out-of-band management of SSDs.

[0005] To address the aforementioned technical problems, the present invention provides a system for out-of-band management of solid-state drives, comprising a controller, a device card, and a control chip mounted on the device card, wherein the device card and the solid-state drive are connected via a serial bus link. The control chip is configured to encapsulate out-of-band management messages into transaction layer data packets based on a target identifier, and transmit the transaction layer data packets to the solid-state drive via the serial bus link; and / or, receive a completion message returned by the solid-state drive and restore it to a management response message, and transmit the management response message to the controller via the serial bus link.

[0006] In one embodiment, the controller includes a command processing module configured to encapsulate management commands into command messages; and / or parse completion messages into result commands.

[0007] In one embodiment, the controller further includes a driver module, which is communicatively connected to the command processing module. The driver module is configured to encapsulate the command message into the out-of-band management message; and / or parse the management response message into the completion message and return the completion message to the command processing module.

[0008] In one embodiment, the out-of-band management message and the management response message are both NVMe-MI overPCIe VDM messages, and the transaction layer data packet is a PCIe VDM message.

[0009] In one embodiment, both the command message and the completion message are NVMe-MI messages.

[0010] In one embodiment, the control unit further includes a switch configured to perform port forwarding based on the destination identifier of the transaction layer data packet, so that the transaction layer data packet is transmitted to the solid-state drive.

[0011] In one embodiment, the target identifier is the bus device function number address of the solid-state drive, which includes the bus number, device number, and function number.

[0012] In one embodiment, the device card is packaged in either a PCIe through-hole form or an M.2 through-hole form.

[0013] In one embodiment, the control chip is an FPGA chip, and the serial bus link is a PCIe link.

[0014] Accordingly, this application also relates to a method for out-of-band management of solid-state drives (SSDs), applied to the aforementioned system for out-of-band management of SSDs, including, The out-of-band management message is encapsulated into a transaction layer data packet according to the target identifier, and the transaction layer data packet is transmitted to the solid-state drive using a serial bus link. The device card is connected to the solid-state drive through the serial bus link. And / or, The system receives the completion message returned by the solid-state drive and restores it to the management response message, then transmits the management response message to the controller via the serial bus link.

[0015] The control chip of this application can encapsulate out-of-band management messages into transaction layer data packets according to the target identifier, and transmit the transaction layer data packets to the solid-state drive (SSD) via a serial bus link; it receives the completion message returned by the SSD and restores it into a management response message, and then transmits the management response message to the controller via the serial bus link. In this way, the device card realizes the direct transmission of transaction layer data packets to the SSD via the serial bus link in a point-to-point manner, and the transmission path does not pass through the host memory of the controller. The device card can replace the dedicated BMC to realize bidirectional conversion of NVMe-MI over PCIe VDM messages, reduce hardware costs, and enable ordinary computers with serial bus interfaces to perform out-of-band management of SSDs.

[0016] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the accompanying drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are merely some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained from these drawings without any creative effort.

[0018] Figure 1 This is a schematic diagram of a system for out-of-band management of a solid-state drive in one embodiment of this application; Figure 2 This is a schematic diagram of a system for out-of-band management of a solid-state drive in one embodiment of this application; Figure 3 This is a flowchart illustrating the steps of an out-of-band management method for a solid-state drive in one embodiment of this application.

[0019] In the attached diagram: 100, controller; 110, command processing module; 120, driver module; 130, root complex; 200, device card; 300, solid-state drive; 400, switch. Detailed Implementation

[0020] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the specific embodiments of this application are described in detail below with reference to the accompanying drawings. Many specific details are set forth in the following description to provide a thorough understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar modifications without departing from the spirit of this application. Therefore, this application is not limited to the specific embodiments disclosed below.

[0021] It should be noted that when a component is said to be "fixed to" another component, it can be directly attached to the other component or there may be an intervening component. When a component is said to be "connected to" another component, it can be directly connected to the other component or there may be an intervening component. The terms "vertical," "horizontal," "left," "right," and similar expressions used in this document are for illustrative purposes only.

[0022] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed items.

[0023] For NVMe SSD management, in-band and out-of-band refer to two different management data transmission paths. In-band management means that management commands and user data are transmitted via the same physical link. Out-of-band management means that management commands are transmitted via a dedicated transmission channel (i.e., a PCIe link) independent of the aforementioned link.

[0024] Reference Figure 1 , Figure 1 This is a schematic diagram of a system for out-of-band management of a solid-state drive in one embodiment. The system includes a controller 100, a device card 200, and a control chip disposed on the device card 200. The device card 200 is connected to the solid-state drive 300 via a serial bus link. The control chip is configured to encapsulate out-of-band management messages into transaction layer data packets based on the target identifier, and transmit the transaction layer data packets to the solid-state drive 300 via a serial bus link; and / or, receive completion messages returned by the solid-state drive 300 and restore them to management response messages, and transmit the management response messages to the controller 100 via a serial bus link.

[0025] In some embodiments, the controller 100 can be an electronic device such as a desktop computer, laptop computer, or industrial control computer. The electronic device may or may not have a standard PCIe expansion slot, and it does not require a Baseboard Management Controller (BMC). The device card 200 serves as the protocol bridging hardware carrier. One end of the device card 200 is physically connected to the solid-state drive 300, and the other end is connected to the controller 100 via an expansion slot or slot. The solid-state drive 300 can be an NVMe-enabled solid-state drive. The in-band data channel is used for high-speed data read / write transmission between the controller 100 and the solid-state drive 300; the out-of-band management channel is used to perform management operations on the solid-state drive 300. Input management commands include at least one of the following: SMART log read command, device temperature read command, Identify command, and custom management commands. This management operation is independent of the data read / write operation. The system of this application manages the solid-state drive 300 only through the out-of-band management channel and does not rely on the in-band data channel.

[0026] Compared to the traditional path where the host CPU sends management messages, the P2P method is closer to the out-of-band management channel defined by the NVMe-MI specification, reducing interference between the host storage stack and CPU load, and enabling the device card 200 to perform out-of-band management on any computer with a PCIe interface.

[0027] Figure 1 The point-to-point (P2P) transmission in this context can be understood as the method of message transmission between device card 200 and solid-state drive 300. Device card 200 is a PCIe endpoint device that directly sends Transaction Layer Packets (TLPs) to another PCIe endpoint device (solid-state drive 300) within the same PCIe topology without using the controller's CPU or memory as a data relay, thus achieving direct transmission of out-of-band management messages. The transaction layer packets are VDM type TLPs conforming to the PCIe protocol specification.

[0028] In other words, within a PCIe topology, device card 200 acts as one PCIe endpoint device, and solid-state drive 300 acts as another PCIe endpoint device. Point-to-point transmission is the method of transmitting transaction layer data packets between the two PCIe endpoint devices. This transmission path does not pass through the host memory of controller 100. Device card 200 can replace a dedicated BMC to achieve bidirectional conversion of NVMe-MI over PCIe VDM messages, reducing hardware costs and enabling ordinary computers with serial bus interfaces to perform out-of-band management of solid-state drive 300.

[0029] Furthermore, device card 200 is a PHXFLYS card, and it implements functions based on a control chip, such as... Figure 1 The transmission is handled by an FPGA (Field-Programmable Gate Array) chip. Device Card 200 connects to the FPGA via a high-speed serial bus link (i.e., a PCIe link). Figure 2 The root complex 130 establishes a connection, and the device card 200 and the solid-state drive 300 are within the same high-speed serial bus domain. The root complex 130 is the hardware root node in the PCIe topology, responsible for allocating BDF addresses, handling memory read / write requests, I / O requests, and message requests from PCIe endpoint devices, and performing P2P routing between PCIe endpoint devices. Therefore, the root complex 130 can be understood as a hardware-level bus management unit.

[0030] The logic circuitry within the aforementioned field-programmable gate array (FPGA) is used to perform packet assembly, transmission, reception, and parsing operations for transaction layer data packets. The peripheral circuitry of device card 200 provides the FPGA with an operating clock, power supply, and a high-speed serial bus differential signal interface.

[0031] In one embodiment, such as Figure 2 The controller 100 shown includes a command processing module 110, which is configured to encapsulate management commands into command messages; and / or parse completion messages into result commands.

[0032] In one embodiment, the controller 100 further includes a drive module 120, which is communicatively connected to the command processing module 110. The drive module 120 is configured to encapsulate command messages into out-of-band management messages; and / or parse management response messages into completion messages and return the completion messages to the command processing module 110.

[0033] For example, the following is a complete process of interaction between the controller 100, device card 200, and solid-state drive: After receiving a management command input by the user, the controller 100 encapsulates the input management command into an NVMe-MI command message according to the NVMe-MI protocol. The NVMe-MI command message is the command message mentioned above. The driver module 120 encapsulates the NVMe-MI command message into an NVMe-MI over PCIe VDM message, which is the out-of-band management message mentioned above. After the driver module 120 transmits the NVMe-MI over PCIe VDM message to the device card 200, the device card 200 retrieves the BDF number of the solid-state drive 300. The BDF number is the target identifier mentioned above. Based on the BDF number, the NVMe-MI over PCIe VDM message is encapsulated into a PCIe VDM message, which is the transaction layer data packet mentioned above. The device card 200 transmits the PCIe data packet through P2P transmission over the PCIe link. The VDM message is transmitted to the solid-state drive 300. The solid-state drive 300 can process the received PCIe VDM message according to the NVMe-MI protocol to obtain an NVMe-MI message, which is the completion message mentioned above. The device card 200 receives the NVMe-MI message and parses it into an NVMe-MI over PCIe VDM message, which is the management response message mentioned above. The device card 200 transmits the NVMe-MI over PCIe VDM message to the driver module 120. The driver module 120 parses the NVMe-MI over PCIe VDM message into an NVMe-MI message, which is the completion message mentioned above. Then, the command processing module 110 parses the NVMe-MI message into a result command and finally returns the result command to the user.

[0034] The input management commands include, but are not limited to: SMART log read command, which is used to obtain the operating status information of the solid-state drive 300; device temperature read command, which is used to read the current operating temperature of the solid-state drive 300; Identify command, which is used to obtain the identification information and capability parameters of the solid-state drive 300; and manufacturer-defined management commands.

[0035] In one embodiment, the controller 100 further includes a switch 400, which has an uplink port and multiple downlink ports. The uplink port is connected to the root complex 130, and the multiple downlink ports are respectively connected to the device card 200 and the solid-state drive 300. The switch 400 is used to forward transaction layer data packets from the uplink port to the corresponding downlink port connected to the target port based on the destination identifier carried in the transaction layer data packet header, thereby enabling point-to-point transmission between the device card and the solid-state drive.

[0036] In one embodiment, the target identifier is the bus device function number (BDF) address of the solid-state drive (SSD) 300, which includes the bus number, device number, and function number. The BDF (Bus, Device, Function) is a unique address identifier assigned to each device on the bus by the PCIe protocol. Here, Bus is the bus number, Device is the device number, and Function is the function number. Before forwarding NVMe-MI over PCIe VDM management messages, the PHXFLYS card needs to determine the BDF address of the SSD 300 in the PCIe topology. The retrieval process can be executed by the FPGA during initialization or upon receiving a management command. Retrieval methods include, but are not limited to: listening to PCIe configuration space enumeration information; reading the target device identifier provided by the host; and scanning endpoint devices within the known bus range that conform to the NVMe Class Code.

[0037] In some embodiments, retrieving the BDF is to obtain the PCIe address of the solid-state drive 300. The obtained PCIe address can be used to encapsulate a PCIe VDM packet. Then, this address is filled into the Destination BDF field of the TLP header, and the NVMe-MIover PCIe VDM payload is filled into the VDM payload area before being sent to the solid-state drive 300 via P2P. It should be noted that the system also has a detection module, configured to: if P2P routing fails (e.g., BDF unreachable, ACS blocking P2P), the PHXFLYS card can report the error to the driver module, outputting a prompt to rescan the device or check the topology configuration. Under normal circumstances, the detection module can complete the detection task in milliseconds, consistent with the standard PCIe TLP transmission latency.

[0038] In one embodiment, the device card 200 is packaged in either a PCIe through-hole form or an M.2 through-hole form. Both the PCIe through-hole and M.2 through-hole forms connect to the controller 100 via a gold finger interface. The M.2 through-hole form can be designed in different sizes according to actual needs. The dimensions of the M.2 through-hole form can be 22mm (width) × 30mm (length), 22mm (width) × 42mm (length), 22mm (width) × 50mm (length), 22mm (width) × 60mm (length), or 22mm (width) × 80mm (length).

[0039] For example, the M.2 through-hole form factor is used to insert into systems with only M.2 slots, such as laptops, compact desktops, or embedded platforms. This form factor is suitable for portable testing scenarios where installation space is limited and the solid-state drive 300 needs to be on the same or adjacent serial bus topology. The PCIe through-hole form factor uses a standard serial bus gold finger interface and is used to insert into the PCIe expansion slot of a desktop, workstation, or server motherboard. This form factor is suitable for scenarios with standard PCIe expansion slots where out-of-band management of the solid-state drive 300 on the motherboard or connected via an adapter is required. Through these two forms factors, this application can access the serial bus on various computer platforms in a physically adapted manner without relying on a specific host form factor or board management controller hardware, thus overcoming the shortcomings of the prior art where only servers have limited out-of-band management capabilities and ordinary computers cannot easily implement related out-of-band management.

[0040] Regardless of the physical packaging form, the device card 200 serves as a message relay and forwarding node between the controller 100 and the solid-state drive 300. It receives messages sent by the controller 100, converts them into transaction layer data packets, and then transmits them to the solid-state drive 300 in a point-to-point manner, thus enabling out-of-band management of the solid-state drive 300 on any computer system.

[0041] Accordingly, this application also relates to a method for out-of-band management of solid-state drives (SSDs), applied to a system for out-of-band management of SSDs, including, The out-of-band management message is encapsulated into a transaction layer data packet according to the target identifier, and the transaction layer data packet is transmitted to the solid-state drive (SSD) via a serial bus link. The device card communicates with the SSD via the serial bus link; and / or, the completion message returned by the SSD is received and restored into a management response message, and the management response message is transmitted to the controller via the serial bus link.

[0042] Before encapsulating out-of-band management messages into transaction layer data packets based on the target identifier, the method further includes: encapsulating management commands into command messages through the command processing module, and then encapsulating the command messages into out-of-band management messages through the driver module; after transmitting the management response message to the controller via the serial bus link, the method further includes: parsing the management response message into a completion message through the driver module, and finally returning the completion message to the command processing module. It should be noted that in the out-of-band management method for solid-state drives (SSDs), the message encapsulation and transmission behavior and the monitoring return message transmission behavior can be parallel or serial. The message encapsulation and transmission behavior refers to the above-mentioned: encapsulating out-of-band management messages into transaction layer data packets based on the target identifier, transmitting the transaction layer data packets to the SSD via the serial bus link, and the device card communicating with the SSD via the serial bus link. The monitoring return message transmission behavior is the above-mentioned: receiving the completion message returned by the SSD and restoring it into a management response message, and transmitting the management response message to the controller via the serial bus link. The following explanation uses a serial approach: Reference Figure 3 , Figure 3 This is a step diagram of a method for out-of-band management of a solid-state drive in one embodiment of this application. The method includes: step S100, encapsulating the out-of-band management message into a transaction layer data packet according to the target identifier; In step S200, the transaction layer data packet is transmitted to the solid-state drive using a serial bus link, and the device card communicates with the solid-state drive through the serial bus link. Step S300: Receive the completion message returned by the solid-state drive and restore it to a management response message; In step S400, the management response message is transmitted to the controller via a serial bus link.

[0043] The control chip of this application can encapsulate out-of-band management messages into transaction layer data packets according to the target identifier, and transmit the transaction layer data packets to the solid-state drive 300 via a serial bus link; it receives the completion message returned by the solid-state drive 300 and restores it into a management response message, and then transmits the management response message to the controller 100 via a serial bus link. In this way, the device card 200 realizes the direct transmission of transaction layer data packets to the solid-state drive 300 via a serial bus link in a point-to-point manner. The transmission path does not pass through the host memory of the controller 100. The device card 200 can replace the dedicated BMC to realize bidirectional conversion of NVMe-MI overPCIe VDM messages, reduce hardware costs, and enable ordinary computers with serial bus interfaces to perform out-of-band management on the solid-state drive 300.

[0044] In the description of this specification, the references to "one embodiment," "an embodiment," and / or "some embodiments," "some embodiments," "other embodiments," "ideal embodiments," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of the present invention. In this specification, the illustrative descriptions of the above terms do not necessarily refer to the same embodiment or example; certain features, structures, or characteristics in one or more embodiments of this specification can be appropriately combined. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described; however, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0045] The above embodiments merely illustrate several implementation methods of the present invention, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the protection scope of the present invention. Therefore, the protection scope of this invention patent should be determined by the appended claims.

[0046] The basic concepts have been described herein. It is obvious that the detailed disclosure above is merely illustrative and does not constitute a limitation of this specification. Although not explicitly stated herein, various modifications, improvements, and corrections may be made to this specification by those skilled in the art. Such modifications, improvements, and corrections are suggested in this specification and therefore remain within the spirit and scope of the exemplary embodiments described herein.

[0047] Furthermore, unless expressly stated in the claims, the order of elements and sequences, the use of numbers and letters, or other names in this specification are not intended to limit the order of the processes and methods described herein. Although various examples have been discussed in the foregoing disclosure of some embodiments of the invention that are currently considered useful, it should be understood that such details are for illustrative purposes only, and the appended claims are not limited to the disclosed embodiments; rather, the claims are intended to cover all modifications and equivalent combinations that conform to the spirit and scope of the embodiments described herein. For example, while the system components described above can be implemented using hardware devices, they can also be implemented solely using software solutions, such as installing the described system on an existing server or mobile device.

[0048] Similarly, it should be noted that, in order to simplify the description disclosed herein and thus aid in the understanding of one or more embodiments of the invention, the foregoing description of embodiments in this specification may sometimes combine multiple features into a single embodiment, drawing, or description thereof. However, this method of disclosure does not imply that the subject matter of this specification requires more features than those mentioned in the claims. In fact, the embodiments contain fewer features than all the features of a single embodiment disclosed above.

[0049] In some embodiments, numbers describing the quantity of components and attributes are used. It should be understood that such numbers used in the description of embodiments are sometimes modified by the terms "approximately," "approximately," or "generally." Unless otherwise stated, "approximately," "approximately," or "generally" indicates that the numbers are allowed to vary. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may be changed depending on the characteristics required by individual embodiments. In some embodiments, numerical parameters are taken into account a specified number of significant digits and employ a general method of digit reservation. Although the numerical ranges and parameters used to confirm their breadth of range in some embodiments of this specification are approximate values, in specific embodiments, such values ​​are set as precisely as feasible.

[0050] In an exemplary embodiment, a computer device is provided, which may be a terminal. The computer device includes a processor, memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface of the computer device is used for exchanging information between the processor and external devices. The communication interface of the computer device is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a method for out-of-band management of a solid-state drive. The display unit of the computer device is used to form a visually visible image and may be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0051] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0052] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps in the above method embodiments.

[0053] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0054] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0055] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0056] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0057] The embodiments described above are merely illustrative of several implementations of the present invention, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the protection scope of the present invention. Therefore, the protection scope of this invention patent should be determined by the appended claims.

Claims

1. A system for out-of-band management of solid-state drives, characterized in that, It includes a controller, a device card, and a control chip mounted on the device card. The device card is connected to the solid-state drive via a serial bus link. The control chip is configured to encapsulate out-of-band management messages into transaction layer data packets according to a target identifier, and transmit the transaction layer data packets to the solid-state drive using the serial bus link; And / or, receive the completion message returned by the solid-state drive and restore it to a management response message, and transmit the management response message to the controller using the serial bus link.

2. The system for out-of-band management of solid-state drives according to claim 1, characterized in that, The controller includes a command processing module configured to encapsulate management commands into command messages; and / or parse completion messages into result commands.

3. The system for out-of-band management of solid-state drives according to claim 2, characterized in that, The controller further includes a drive module, which is communicatively connected to the command processing module. The drive module is configured to encapsulate the command message into the out-of-band management message. And / or, parse the management response message into the completion message, and return the completion message to the command processing module.

4. The system for out-of-band management of solid-state drives according to claim 1 or 3, characterized in that, The out-of-band management message and the management response message are both NVMe-MI over PCIe VDM messages, and the transaction layer data packet is a PCIe VDM message.

5. The system for out-of-band management of solid-state drives according to claim 3, characterized in that, Both the command message and the completion message are NVMe-MI messages.

6. The system for out-of-band management of solid-state drives according to claim 3, characterized in that, The control unit also includes a switch configured to perform port forwarding based on the destination identifier of the transaction layer data packet, so that the transaction layer data packet is transmitted to the solid-state drive.

7. The system for out-of-band management of solid-state drives according to claim 1 or 6, characterized in that, The target identifier is the bus device function number address of the solid-state drive, which includes the bus number, device number, and function number.

8. The system for out-of-band management of solid-state drives according to claim 1, characterized in that, The device card is packaged in either PCIe through-hole or M.2 through-hole form.

9. The system for out-of-band management of solid-state drives according to claim 1, characterized in that, The control chip is an FPGA chip, and the serial bus link is a PCIe link.

10. A method for out-of-band management of a solid-state drive, characterized in that, The system for out-of-band management of solid-state drives as described in any one of claims 1-9 includes, The out-of-band management message is encapsulated into a transaction layer data packet according to the target identifier, and the transaction layer data packet is transmitted to the solid-state drive using a serial bus link. The device card is connected to the solid-state drive through the serial bus link. And / or, The system receives the completion message returned by the solid-state drive and restores it to the management response message, then transmits the management response message to the controller via the serial bus link.