Out-of-band signal negotiation method, out-of-band signal negotiation device, SAS controller and SATA disk

Abstract

The application relates to an out-of-band signal negotiation method, an out-of-band signal negotiation device, a SAS controller and a SATA disk. The method comprises the following steps: sending a first communication initialization message to the SATA disk; receiving a second communication initialization message sent by the SATA disk; the second communication initialization message is sent in response to power-on of the SATA disk; if the waiting time after sending the first communication initialization message is greater than a preset interval, sending a third communication initialization message to the SATA disk; wherein the communication initialization message is used for informing the opposite end device that the local side is ready. By using the method, it can be ensured that the SATA disk will send a device signature to the SAS controller after OOB negotiation, and a successful link is established.

Description

Technical Field

[0001] This application relates to the field of disk connectivity technology, and in particular to an out-of-band signal negotiation method, an out-of-band signal negotiation device, a SAS controller, and a SATA disk. Background Technology

[0002] Serial Attached SCSI (SAS) is an enterprise-grade storage interface controller, while Serial Advanced Technology Attachment (SATA) drives are consumer-grade hard drives. While their physical interfaces are compatible, their protocols differ. The SPL-4R13 protocol specifies scenarios where the SAS controller actively initiates out-of-band (OOB) negotiation, and the SATA drive passively responds. However, it does not cover the scenario where the SATA drive actively initiates COMINIT after power-on.

[0003] The SATA 3.4 protocol stipulates that after a SATA drive is powered on, it will actively send a COMINIT message, requiring the SAS controller to respond with a COMRESET message. Only after receiving the COMRESET response can the SATA drive send a device signature to the SAS controller to complete the connection establishment.

[0004] However, if the SAS controller has just sent COMINIT and the SATA disk subsequently powers on and actively sends COMINIT, from the SATA disk's perspective, it does not receive the COMINIT sent by the SAS controller after powering on and actively sending COMINIT. In this case, the SATA disk will inevitably not send the device signature to the SAS controller after OOB negotiation, thus causing the connection establishment to fail. Summary of the Invention

[0005] Therefore, it is necessary to provide an out-of-band signal negotiation method, an out-of-band signal negotiation device, a SAS controller, and a SATA disk that can ensure successful link establishment between the SATA disk and the SAS controller when the SAS controller finishes sending COMINIT and the SATA disk subsequently powers on and actively sends COMINIT.

[0006] Firstly, this application provides an out-of-band signal negotiation method applied to a SAS controller, comprising:

[0007] Send the first communication initialization message to the SATA drive;

[0008] Receive the second communication initialization message sent by the SATA disk; the second communication initialization message is sent in response to the SATA disk power-on.

[0009] If the waiting time after sending the first communication initialization message is longer than the preset interval, a third communication initialization message is sent to the SATA disk.

[0010] The communication initialization message is used to inform the peer device that the local side is ready.

[0011] In one embodiment, the method further includes:

[0012] Received the fourth communication initialization message sent by the SATA disk in response to the third communication initialization message.

[0013] In one embodiment, the method further includes:

[0014] Send a device type identification message to the SATA disk; the device type identification message is used to identify the disk type.

[0015] In one embodiment, the method further includes:

[0016] Send a communication wake-up message to the SATA drive; the communication wake-up message is used to restore the SATA drive from a low-power state to an active state.

[0017] Secondly, this application provides an out-of-band signal negotiation method for SATA drives, including:

[0018] After receiving the first communication initialization message from the SAS controller, the SATA disk powers on and sends a second communication initialization message to the SAS controller.

[0019] Receive the third communication initialization message sent by the SAS controller; the third communication initialization message is sent by the SAS controller if the waiting time after sending the first communication initialization message is longer than the preset interval.

[0020] The communication initialization message is used to inform the peer device that the local side is ready.

[0021] In one embodiment, the method further includes:

[0022] Based on the third communication initialization message, a fourth communication initialization message is sent to the SAS controller.

[0023] Thirdly, this application also provides an out-of-band signal negotiation device for use in a SAS controller, comprising:

[0024] The first sending module is used to send the first communication initialization message to the SATA disk;

[0025] The first receiving module is used to receive the second communication initialization message sent by the SATA disk; the second communication initialization message is sent in response to the SATA disk being powered on.

[0026] The second sending module is used to send a third communication initialization message to the SATA disk if the waiting time after sending the first communication initialization message is longer than a preset interval.

[0027] The communication initialization message is used to inform the peer device that the local side is ready.

[0028] Fourthly, this application also provides an out-of-band signal negotiation device for use in SATA drives, comprising:

[0029] The third sending module is used to power on the SATA disk and send a second communication initialization message to the SAS controller after receiving the first communication initialization message sent by the SAS controller.

[0030] The second receiving module is used to receive the third communication initialization message sent by the SAS controller; the third communication initialization message is sent by the SAS controller when the waiting time after sending the first communication initialization message is longer than a preset interval.

[0031] The communication initialization message is used to inform the peer device that the local side is ready.

[0032] Fifthly, this application also provides a SAS controller that executes the steps of the method described in the first aspect above during link establishment.

[0033] Sixthly, this application also provides a SATA disk that performs the steps of the method described in the second aspect above when establishing a connection.

[0034] The aforementioned out-of-band (OOB) signal negotiation method, OOB signal negotiation device, SAS controller, and SATA disk, after the SAS controller sends a first communication initialization message to the SATA disk, receive a second communication initialization message sent by the SATA disk after power-on. For the SAS controller, this completes a full communication initialization interaction with the SATA disk. Furthermore, if the waiting time after the first communication initialization message exceeds a preset interval, the SAS controller sends a third communication initialization message to the SATA disk. For the SATA disk, through the second and third communication initialization messages, a full communication initialization interaction with the SAS controller is completed. Therefore, the SATA disk will inevitably send a device signature to the SAS controller after OOB negotiation to successfully establish a link. Attached Figure Description

[0035] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0036] Figure 1 This is a diagram illustrating the application environment of an out-of-band signal negotiation method in one embodiment.

[0037] Figure 2 This is a diagram illustrating the application environment of an out-of-band signal negotiation method in one embodiment.

[0038] Figure 3 This is a flowchart illustrating an out-of-band signal negotiation method in one embodiment;

[0039] Figure 4 This is a flowchart illustrating the out-of-band signal negotiation method in another embodiment;

[0040] Figure 5 This is a flowchart illustrating an out-of-band signal negotiation method in one embodiment;

[0041] Figure 6 This is a flowchart illustrating an out-of-band signal negotiation method in one embodiment;

[0042] Figure 7 This is a flowchart illustrating an out-of-band signal negotiation method in one embodiment;

[0043] Figure 8 This is a flowchart illustrating an out-of-band signal negotiation method in one embodiment;

[0044] Figure 9 This is a flowchart illustrating an out-of-band signal negotiation method in one embodiment;

[0045] Figure 10 This is a structural block diagram of an out-of-band signal negotiation device in one embodiment;

[0046] Figure 11 This is a structural block diagram of an out-of-band signal negotiation device in another embodiment. Detailed Implementation

[0047] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0048] Serial Attached SCSI (SAS) is an enterprise-grade storage interface controller, while Serial Advanced Technology Attachment (SATA) drives are consumer-grade hard drives. While their physical interfaces are compatible, their protocols differ. The SPL-4R13 protocol specifies scenarios where the SAS controller actively initiates out-of-band (OOB) negotiation, and the SATA drive passively responds. However, it does not cover the scenario where the SATA drive actively initiates COMINIT after power-on.

[0049] The SATA 3.4 protocol stipulates that after a SATA drive is powered on, it will actively send a COMINIT message, requiring the SAS controller to respond with a COMRESET message. Only after the SATA drive receives the COMRESET response can it send a device signature to complete the connection establishment.

[0050] However, if the SAS controller has just sent COMINIT and the SATA disk subsequently powers on and actively sends COMINIT, from the SATA disk's perspective, it does not receive the COMINIT sent by the SAS controller after powering on and actively sending COMINIT. In this case, the SATA disk will inevitably not send the device signature to the SAS controller after OOB negotiation, thus causing the connection establishment to fail.

[0051] For example, see Figure 1This protocol provides a method for out-of-band (OOB) signal negotiation between the SATA drive and the SAS controller. The SAS controller first sends COMINIT1 to the SATA drive (Step 1). Upon receiving COMINIT1, the SATA drive replies with COMINIT2 (Step 2). Then, the SAS controller sends COMSAS to the SATA drive (Step 3). If no response is received from the SATA drive within a preset time period after sending COMSAS, the SAS controller sends COMWAKE to the SATA drive (Step 4), completing the OOB signal negotiation between the SATA drive and the SAS controller. However, if the SATA drive powers on after Step 1 but before Step 2, it will proactively send COMINIT2 to the SAS controller (Step 2). If the SAS controller then sends COMSAS directly instead of replying with COMINIT, the SATA drive will inevitably fail to send a device signature to the SAS controller after OOB negotiation, resulting in connection failure.

[0052] Based on this, this application provides an out-of-band signal negotiation method, which aims to solve the above problems.

[0053] Having described the background technology of the out-of-band signal negotiation method provided in the embodiments of this application, the implementation environment involved in the out-of-band signal negotiation method provided in the embodiments of this application will be briefly described below. The out-of-band signal negotiation method provided in the embodiments of this application can be applied to, for example... Figure 2 In the application environment shown, there is a host (i.e., SAS controller) and a SATA disk. The SATA disk can be connected to the host. Before the SATA disk and the host can interact with each other, out-of-band signal negotiation is required to establish a link between the SATA disk and the host.

[0054] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0055] In one embodiment, an out-of-band signal negotiation method is provided, which is applied to... Figure 2 Taking the SAS controller (i.e., the host) as an example, the explanation is as follows: Figure 3 As shown, it includes the following steps:

[0056] S201, Send the first communication initialization message to the SATA disk.

[0057] The communication initialization message is used to inform the peer device that the local machine is connected and ready. During the OOB negotiation process between the SAS controller and the SATA disk, the communication initialization message can be Communication Initialize (COMINIT).

[0058] In this embodiment, after the SAS controller is ready, it will send a first communication initialization message to the connected SATA disk to inform the SATA disk that the local side is ready.

[0059] S202, Receive the second communication initialization message sent by the SATA disk; the second communication initialization message is sent in response to the SATA disk being powered on.

[0060] In this embodiment, after sending the first communication initialization message to the SATA drive, there are two possibilities. First, the SATA drive sends a second communication initialization message to the SAS controller based on the first communication initialization message; that is, the second communication initialization message is the SATA drive's response to the first communication initialization message. Second, after the SAS controller sends the first communication initialization message to the SATA drive, the SATA drive powers on and actively sends the second communication initialization message to the SAS controller; that is, the second communication initialization message is actively sent to the SAS controller by the SATA drive after power-on. It should be noted that this application pertains to the second possibility.

[0061] In this embodiment, for the SAS controller, a device handshake is successfully completed after sending a first communication initialization message to the SATA disk and receiving a second communication initialization message sent by the SATA disk (regardless of whether the second communication initialization message is a response from the SATA disk to the first communication initialization message or is actively sent by the SATA disk to the SAS controller after power-on).

[0062] S203. If the waiting time after sending the first communication initialization message is longer than the preset interval, send the third communication initialization message to the SATA disk.

[0063] In this embodiment, after receiving the second communication initialization message sent by the SATA disk, the SAS controller can send a third communication initialization message to the SATA disk when the time since the first communication initialization message was sent is greater than a preset interval.

[0064] Optionally, there are two scenarios. First, the third communication initialization message can be sent proactively by the SAS controller to the SATA disk after the waiting time following the first communication initialization message exceeds a preset interval. In this case, for the SAS controller, since S202 has already successfully completed a device handshake, only an extra communication initialization message is sent, having almost no impact on link establishment. Second, the third communication initialization message can be a response from the SAS controller to the second communication initialization message sent by the SATA disk. It should be noted that this application addresses the second scenario.

[0065] In this embodiment, for a SATA drive, after powering on, it sends a second communication initialization message to the SAS controller and receives a third communication initialization message from the SAS controller (regardless of whether the third communication initialization message is a response from the SAS controller to the second communication initialization message or is sent by the SAS controller when the waiting time exceeds a preset interval). This completes a device handshake.

[0066] It should be noted that, for the SAS controller, as long as the waiting time after sending the previous communication initialization message is longer than the preset interval, it can send another communication initialization message to the SATA disk. In other words, the scope of protection of this application is not limited to the SAS controller sending the first and third communication initialization messages to the SATA disk. It can also further send a fifth communication initialization message to the SATA disk if the waiting time after sending the third communication initialization message is longer than the preset interval, and so on.

[0067] In this embodiment, after the SAS controller sends the first communication initialization message to the SATA disk, it receives the second communication initialization message sent by the SATA disk after power-on. For the SAS controller, a complete communication initialization interaction with the SATA disk is completed. Furthermore, if the waiting time after the first communication initialization message is longer than a preset interval, the SAS controller sends a third communication initialization message to the SATA disk. For the SATA disk, through the second and third communication initialization messages, a complete communication initialization interaction with the SAS controller is completed. Therefore, the SATA disk will inevitably send a device signature to the SAS controller after OOB negotiation, thus successfully establishing a connection.

[0068] In this embodiment, in the above Figure 3 Based on the illustrated embodiment, after sending a third communication initialization message to the SATA disk, see [link to example]. Figure 4 The above methods also include:

[0069] S204. Received the fourth communication initialization message sent by the SATA disk in response to the third communication initialization message.

[0070] In this embodiment, after the SAS controller sends a third communication initialization message to the SATA disk, the SATA disk will send a communication initialization message to the SAS controller in response to the third communication initialization message sent by the SAS controller.

[0071] In this embodiment, after the SAS controller sends a first communication initialization message to the SATA disk and receives a second communication initialization message sent after the SATA disk is powered on, the SAS controller has completed the initial confirmation of the existence of the SATA disk. Furthermore, if the waiting time after the first communication initialization message is longer than the preset interval, the SAS controller sends a third communication initialization message to the SATA disk and receives the corresponding fourth communication initialization message. For the SATA disk, the readiness status of the other end is confirmed through two independent communication initialization interactions. Therefore, the SATA disk will inevitably send a device signature to the SAS controller after OOB negotiation, thereby successfully establishing a stable communication link.

[0072] In this embodiment, in the above Figure 4 Based on the illustrated embodiment, after receiving the fourth communication initialization message sent by the SATA disk in response to the third communication initialization message, see [link to example]. Figure 5 The above methods also include:

[0073] S205. Send a device type identification message to the SATA disk; the device type identification message is used to identify the disk type.

[0074] Among them, the device type identification message is used by the SAS controller to identify the type of disk it is connected to. During the OOB negotiation process between the SAS controller and the SATA disk, the device type identification message can be used for link interaction and identity verification between SAS devices (Communication SAS, COMSAS).

[0075] In this embodiment, after receiving the fourth communication initialization message sent by the SATA disk, it indicates that the SATA disk is successfully ready. At this time, a device type identification message can be sent to the SATA disk to identify the type of disk connected to the SAS controller.

[0076] It should be noted that if the SAS controller sends a device type identification message to the disk connected to it, and the disk does not send a response message back to the SAS controller, then the disk connected to it is a SATA disk. If the SAS controller sends a device type identification message to the disk connected to it, and the disk connected to it sends a response message back to the SAS controller, then the disk connected to it is not a SATA disk, but may be a SAS disk.

[0077] In this implementation, the SAS controller can identify the type of disk it is connected to by sending a device type identification message to the SATA disk. This serves as part of the OOB negotiation and provides a data foundation for subsequent chain establishment.

[0078] In this embodiment, in the above Figure 4 Based on the illustrated embodiment, after receiving the fourth communication initialization message sent by the SATA disk in response to the third communication initialization message, see [link to example]. Figure 6 The above methods also include:

[0079] S206. Send a communication wake-up message to the SATA disk; the communication wake-up message is used to restore the state of the SATA disk from the low power state to the active state.

[0080] The communication wake-up message is used to restore the SATA disk from a low-power state to an active state. During the OOB negotiation process between the SAS controller and the SATA disk, the communication wake-up message can be a communication wake-up (COMWAKE).

[0081] In this embodiment, after receiving the fourth communication initialization message sent by the SATA disk, it indicates that the SATA disk has been successfully prepared. At this time, a communication wake-up message can be sent to the SATA disk to restore the SATA disk from the low-power state to the active state.

[0082] In this implementation, the SAS controller can restore the SATA disk from a low-power state to an active state by sending a device communication wake-up message to the SATA disk. This serves as part of the OOB negotiation and provides a data foundation for subsequent chain establishment.

[0083] In one embodiment, an out-of-band signal negotiation method is provided, which is applied to... Figure 2 Let's take a SATA drive as an example to illustrate, such as... Figure 7 As shown, it includes the following steps:

[0084] S301. After receiving the first communication initialization message sent by the SAS controller, the SATA disk powers on and sends a second communication initialization message to the SAS controller.

[0085] The communication initialization message is used to inform the peer device that the local machine is connected and ready. During the OOB negotiation process between the SAS controller and the SATA disk, the communication initialization message can be Communication Initialize (COMINIT).

[0086] In this embodiment, after the SAS controller is ready, it sends a first communication initialization message to the connected SATA drive to inform the SATA drive that the local side is ready. Further, after sending the first communication initialization message to the SATA drive, two scenarios exist: First, the SATA drive sends a second communication initialization message to the SAS controller based on the first communication initialization message; that is, the second communication initialization message is the SATA drive's response to the first communication initialization message. Second, after the SAS controller sends the first communication initialization message to the SATA drive, the SATA drive powers on and actively sends the second communication initialization message to the SAS controller; that is, the second communication initialization message is actively sent to the SAS controller by the SATA drive after power-on. It should be noted that this application addresses the second scenario.

[0087] In this embodiment, for the SAS controller, a device handshake is successfully completed after sending a first communication initialization message to the SATA disk and receiving a second communication initialization message sent by the SATA disk (regardless of whether the second communication initialization message is a response from the SATA disk to the first communication initialization message or is actively sent by the SATA disk to the SAS controller after power-on).

[0088] S302, Receive the third communication initialization message sent by the SAS controller; the third communication initialization message is sent by the SAS controller when the waiting time after sending the first communication initialization message is longer than the preset interval.

[0089] In this embodiment, after the SAS controller receives the second communication initialization message sent by the SATA disk, the SAS controller can send a third communication initialization message to the SATA disk when the time since the first communication initialization message was sent is greater than a preset interval.

[0090] Optionally, there are two scenarios. First, the third communication initialization message can be sent proactively by the SAS controller to the SATA disk after the waiting time following the first communication initialization message exceeds a preset interval. In this case, for the SAS controller, since S202 has already successfully completed a device handshake, only an extra communication initialization message is sent, having almost no impact on link establishment. Second, the third communication initialization message can be a response from the SAS controller to the second communication initialization message sent by the SATA disk. It should be noted that this application addresses the second scenario.

[0091] In this embodiment, for a SATA drive, after powering on, it sends a second communication initialization message to the SAS controller and receives a third communication initialization message from the SAS controller (regardless of whether the third communication initialization message is a response from the SAS controller to the second communication initialization message or is sent by the SAS controller when the waiting time exceeds a preset interval). This completes a device handshake.

[0092] It should be noted that, for the SAS controller, as long as the waiting time after sending the previous communication initialization message is longer than the preset interval, it can send another communication initialization message to the SATA disk. In other words, the scope of protection of this application is not limited to the SAS controller sending the first and third communication initialization messages to the SATA disk. It can also further send a fifth communication initialization message to the SATA disk if the waiting time after sending the third communication initialization message is longer than the preset interval, and so on.

[0093] In this embodiment, after the SAS controller sends the first communication initialization message to the SATA disk, it receives the second communication initialization message sent by the SATA disk after power-on. For the SAS controller, a complete communication initialization interaction with the SATA disk is completed. Furthermore, if the waiting time after the first communication initialization message is longer than a preset interval, the SAS controller sends a third communication initialization message to the SATA disk. For the SATA disk, through the second and third communication initialization messages, a complete communication initialization interaction with the SAS controller is completed. Therefore, the SATA disk will inevitably send a device signature to the SAS controller after OOB negotiation, thus successfully establishing a connection.

[0094] In this embodiment, in the above Figure 7 Based on the illustrated embodiment, after receiving the third communication initialization message sent by the SAS controller, see [link to example]. Figure 8 The above methods also include:

[0095] S303. Based on the third communication initialization message, send the fourth communication initialization message to the SAS controller.

[0096] In this embodiment, after the SAS controller sends a third communication initialization message to the SATA disk, the SATA disk will send a communication initialization message to the SAS controller in response to the third communication initialization message sent by the SAS controller.

[0097] In this embodiment, after the SAS controller sends a first communication initialization message to the SATA disk and receives a second communication initialization message sent after the SATA disk is powered on, the SAS controller has completed the initial confirmation of the existence of the SATA disk. Furthermore, if the waiting time after the first communication initialization message is longer than the preset interval, the SAS controller sends a third communication initialization message to the SATA disk and receives the corresponding fourth communication initialization message. For the SATA disk, the readiness status of the other end is confirmed through two independent communication initialization interactions. Therefore, the SATA disk will inevitably send a device signature to the SAS controller after OOB negotiation, thereby successfully establishing a stable communication link.

[0098] In this embodiment, see Figure 9 It also provides an out-of-band signal negotiation method, including:

[0099] T1 (SAS controller) sends the first communication initialization message to the SATA disk;

[0100] T2 (SATA disk) receives the first communication initialization message sent by the SAS controller;

[0101] T3 and SATA disks are powered on and send a second communication initialization message to the SAS controller;

[0102] T4 (SAS controller) receives the second communication initialization message sent by the SATA disk;

[0103] T5. If the waiting time after sending the first communication initialization message is longer than the preset interval, send the third communication initialization message to the SATA disk.

[0104] T6 (SATA disk) sends a fourth communication initialization message to the SAS controller based on the third communication initialization message;

[0105] T7 (SAS controller) receives the fourth communication initialization message sent by the SATA disk in response to the third communication initialization message;

[0106] T8. Sends a device type identification message to the SATA disk; the device type identification message is used to identify the disk type.

[0107] T9. Send a communication wake-up message to the SATA disk; the communication wake-up message is used to restore the SATA disk from a low-power state to an active state.

[0108] It should be noted that the descriptions of T1-T9 above can be found in the relevant descriptions in the above embodiments, and their effects are similar, so they will not be repeated here.

[0109] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0110] Based on the same inventive concept, this application also provides an out-of-band signal negotiation apparatus for implementing the out-of-band signal negotiation method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more out-of-band signal negotiation apparatus embodiments provided below can be found in the limitations of the out-of-band signal negotiation method described above, and will not be repeated here.

[0111] In one exemplary embodiment, such as Figure 10 As shown, an out-of-band signal negotiation device is provided, comprising: a first transmitting module 10, a first receiving module 11, and a second transmitting module 12, wherein:

[0112] The first sending module 10 is used to send a first communication initialization message to the SATA disk.

[0113] The first receiving module 11 is used to receive the second communication initialization message sent by the SATA disk; the second communication initialization message is sent in response to the SATA disk being powered on.

[0114] The second sending module 12 is used to send a third communication initialization message to the SATA disk if the waiting time after sending the first communication initialization message is longer than a preset interval; wherein the communication initialization message is used to inform the peer device that the local side is ready.

[0115] In one exemplary embodiment, the above-described apparatus further includes:

[0116] The second receiving module is used to receive the fourth communication initialization message sent by the SATA disk in response to the third communication initialization message.

[0117] In one exemplary embodiment, the above-described apparatus further includes:

[0118] The third sending module is used to send device type identification messages to the SATA disk; the device type identification messages are used to identify the disk type.

[0119] In one exemplary embodiment, the above-described apparatus further includes:

[0120] The fourth sending module is used to send a communication wake-up message to the SATA disk; the communication wake-up message is used to restore the state of the SATA disk from a low-power state to an active state.

[0121] In one exemplary embodiment, such as Figure 11 As shown, an out-of-band signal negotiation device is provided, comprising: a fifth transmitting module 20 and a third receiving module 21, wherein:

[0122] The fifth sending module 20 is used to power on the SATA disk and send a second communication initialization message to the SAS controller after receiving the first communication initialization message sent by the SAS controller.

[0123] The third receiving module 21 is used to receive the third communication initialization message sent by the SAS controller. The third communication initialization message is sent by the SAS controller when the waiting time after sending the first communication initialization message is longer than the preset interval. The communication initialization message is used to inform the peer device that the local side is ready.

[0124] In one exemplary embodiment, the above-described apparatus further includes:

[0125] The sixth sending module is used to send the fourth communication initialization message to the SAS controller based on the third communication initialization message.

[0126] Each module in the aforementioned out-of-band signal negotiation device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the SAS controller in hardware form, or stored in the SAS controller's memory in software form, so that the processor can call and execute the operations corresponding to each module.

[0127] In one exemplary embodiment, a SAS controller is provided that performs the following steps during link establishment:

[0128] Send the first communication initialization message to the SATA drive;

[0129] Receive the second communication initialization message sent by the SATA disk; the second communication initialization message is sent in response to the SATA disk power-on.

[0130] If the waiting time after sending the first communication initialization message is longer than the preset interval, a third communication initialization message is sent to the SATA disk.

[0131] The communication initialization message is used to inform the peer device that the local side is ready.

[0132] In one exemplary embodiment, the following steps are performed during chain establishment:

[0133] Received the fourth communication initialization message sent by the SATA disk in response to the third communication initialization message.

[0134] In one exemplary embodiment, the following steps are performed during chain establishment:

[0135] Send a device type identification message to the SATA disk; the device type identification message is used to identify the disk type.

[0136] In one exemplary embodiment, the following steps are performed during chain establishment:

[0137] Send a communication wake-up message to the SATA drive; the communication wake-up message is used to restore the SATA drive from a low-power state to an active state.

[0138] In one exemplary embodiment, a SATA drive is provided that performs the following steps during link establishment:

[0139] After receiving the first communication initialization message from the SAS controller, the SATA disk powers on and sends a second communication initialization message to the SAS controller.

[0140] Receive the third communication initialization message sent by the SAS controller; the third communication initialization message is sent by the SAS controller if the waiting time after sending the first communication initialization message is longer than the preset interval.

[0141] The communication initialization message is used to inform the peer device that the local side is ready.

[0142] In one exemplary embodiment, the following steps are performed during chain establishment:

[0143] Based on the third communication initialization message, a fourth communication initialization message is sent to the SAS controller.

[0144] 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 application.

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

Claims

1. An out-of-band signal negotiation method, characterized in that, Applied to SAS controllers, the method includes: Send the first communication initialization message to the SATA drive; Receive a second communication initialization message sent by the SATA disk; the second communication initialization message is sent in response to the SATA disk being powered on. If the waiting time after sending the first communication initialization message is longer than the preset interval, a third communication initialization message is sent to the SATA disk. The communication initialization message is used to inform the peer device that the local side is ready.

2. The method according to claim 1, characterized in that, The method further includes: The fourth communication initialization message sent by the SATA disk in response to the third communication initialization message is received.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Send a device type identification message to the SATA disk; the device type identification message is used to identify the disk type.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Send a communication wake-up message to the SATA disk; the communication wake-up message is used to restore the state of the SATA disk from a low-power state to an active state.

5. An out-of-band signal negotiation method, characterized in that, Applied to SATA drives, the method includes: After receiving the first communication initialization message from the SAS controller, the SATA disk powers on and sends a second communication initialization message to the SAS controller. The system receives a third communication initialization message from the SAS controller; the third communication initialization message is sent by the SAS controller after the waiting time following the sending of the first communication initialization message exceeds a preset interval. The communication initialization message is used to inform the peer device that the local side is ready.

6. The method according to claim 5, characterized in that, The method further includes: Based on the third communication initialization message, a fourth communication initialization message is sent to the SAS controller.

7. An out-of-band signal negotiation device, characterized in that, Applied to a SAS controller, the device includes: The first sending module is used to send the first communication initialization message to the SATA disk; The first receiving module is configured to receive a second communication initialization message sent by the SATA disk; the second communication initialization message is sent in response to the SATA disk being powered on. The second sending module is used to send a third communication initialization message to the SATA disk if the waiting time after sending the first communication initialization message is longer than a preset interval. The communication initialization message is used to inform the peer device that the local side is ready.

8. An out-of-band signal negotiation device, characterized in that, The device, applied to SATA hard drives, includes: The third sending module is used to power on the SATA disk and send a second communication initialization message to the SAS controller after receiving the first communication initialization message sent by the SAS controller. The second receiving module is used to receive a third communication initialization message sent by the SAS controller; the third communication initialization message is sent by the SAS controller when the waiting time after sending the first communication initialization message is longer than a preset interval. The communication initialization message is used to inform the peer device that the local side is ready.

9. A SAS controller that implements the steps of the method according to any one of claims 1 to 4 during link establishment.

10. A SATA hard drive that implements the steps of the method described in claim 5 or 6 when establishing a connection.

Images