Method for managing low-power state and apparatus

Abstract

The present application relates to the field of communications and provides a method for managing a low-power state and an apparatus, which implement flexible low-power state management supporting various scenarios. The method comprises: sending a first low-power request message to a second device, the first low-power request message comprising a first low-power request mode, a first low-power request direction and a low-power request setting, the first low-power request mode referring to entering low power, and the first low-power request direction comprising unidirectional or bidirectional; and receiving from the second device response information corresponding to the first low-power request message.

Description

Method and device for managing low power consumption state Technical Field

[0001] The present application relates to the field of communications, and in particular to a method and apparatus for managing a low power consumption state. Background Art

[0002] With the development of ultra-high-definition technologies (such as 4K / 8K), ultra-high-definition transmission interfaces need to support increasingly higher rates. Higher rates require higher power consumption. Therefore, how to enter a low-power state when services are idle and how to exit this state when services are busy are common technical solutions in the industry to reduce the power consumption of ultra-high-definition transmission interfaces.

[0003] Flexible low-power state management that supports various scenarios is an issue that the industry urgently needs to solve.

[0004] Summary of the Invention

[0005] The method and device for managing low power consumption states provided in this application implement flexible low power consumption state management that supports various scenarios.

[0006] To achieve the above objectives, the present invention adopts the following technical solutions:

[0007] In a first aspect, a method for managing a low power consumption state is provided, which is applied to a first device or a chip in the first device. The method may include: sending a first low power consumption request message to a second device, the first low power consumption request message including a first low power consumption request mode, a first low power consumption request direction, and a low power consumption request gear; the first low power consumption request mode is to enter low power consumption; the first low power consumption request direction includes unidirectional or bidirectional; and receiving response information corresponding to the first low power consumption request message from the second device.

[0008] Through the solution provided by this application, the devices at both ends of the link negotiate to enter low power consumption through a low-power request message; the low-power state to be entered is indicated by the low-power request gear, and the link direction of entering the low-power state is indicated by the low-power request solution. This solution for managing low power consumption can realize the entry into multiple different low-power states through one request message, and can be applied to low-power management in different link directions, realizing flexible low-power state management that supports various scenarios.

[0009] The response information is used to instruct the second device to confirm the first low power request message, that is, the second device agrees that all channels in the link in the direction of the first low power request enter the low power state indicated by the low power request gear.

[0010] In one possible implementation, the link between the first device and the second device includes a main link and an auxiliary link, the main link being a unidirectional transmission link from the first device to the second device, and the auxiliary link being a bidirectional link; receiving a response message from the second device includes: receiving the response message from the second device via the auxiliary link. In a scenario where the main link is a unidirectional transmission link (a pure unidirectional transmission link, where the main link of the first device only has a transmission link, i.e., there is no main link for the second device to send service data to the first device, i.e., there is no receiving link for the first device), low-power management of the unidirectional transmission link is achieved by feeding back a response message to the low-power request message via the auxiliary link.

[0011] The transmission rate of the service data transmitted by the main link is greater than that of the auxiliary link.

[0012] In another possible implementation, the method provided in the present application may further include: the transmitting link in the main link of the first device enters the low power state indicated by the low power request gear position. After the first device receives the above-mentioned response information, the negotiation with the second device is completed, and the first device can complete the transmitting link in the main link of the first device entering the low power state indicated by the low power request gear position.

[0013] The primary link of the first device refers to the set of channels in the primary link between the first and second devices, which include the channels through which the first device sends data to the second device and the channels through which the first device receives data from the second device. The sending link in the primary link of the first device, i.e., the channel through which the first device sends data to the second device, can also be referred to as the port sending link of the first device.

[0014] In another possible implementation, the direction of the first low power request is bidirectional, and the method provided in the present application may further include: the receiving link in the main link of the first device enters a low power state indicated by the low power request gear position.

[0015] Another possible implementation method, the low power request gear, may include one or more of the following: the receiving end does not support the low power gear based on the control frame wake-up capability; or the receiving end supports the low power gear based on the control frame wake-up capability.

[0016] In another possible implementation, the first low power request message is encapsulated as a logic layer main link management message, or a logic layer auxiliary link management message is transmitted.

[0017] Another possible implementation method is that the low-power request gear is a low-power gear in which the receiving end does not support the ability to wake up based on a control frame. The link between the first device and the second device includes a main link and an auxiliary link. The method provided in this application may also include: on the auxiliary link, sending a second low-power request message to the second device, the second low-power request message including a second low-power request mode and a second low-power request direction; the second low-power request mode is to exit low power; the second low-power request direction includes unidirectional or bidirectional; on the auxiliary link, receiving a response message corresponding to the second low-power request message from the second device. In a low-power scenario that does not support wake-up by a wake-up frame, the low-power state has been exited by transmitting the low-power request message through the auxiliary link, thereby achieving more flexible low-power state management.

[0018] In another possible implementation, the method provided in this application may further include: exiting the low-power state of the transmitting link in the main link of the first device; and after exiting the low-power state, continuously sending the first control frame to perform link recovery. After the first device receives the response information corresponding to the request to exit low-power, the negotiation with the second device is completed, and the first device can complete the exit of the transmitting link in the main link of the first device from the low-power state and perform link recovery.

[0019] In another possible implementation, the method provided in the present application may further include: exiting the low-power state for a receiving link in the main link of the first device. When the request message to exit low-power indicates bidirectionality, the request is for the port to exit the low-power state, and therefore, the receiving link in the main link of the first device also exits the low-power state.

[0020] In another possible implementation, the first low power request direction is unidirectional, and the second low power request direction is unidirectional.

[0021] In another possible implementation, the first low power request direction is bidirectional, and the second low power request direction is unidirectional.

[0022] In another possible implementation, the first low power request direction is bidirectional, and the second low power request direction is bidirectional.

[0023] In another possible implementation, the first low-power request direction is bidirectional, the low-power request gear is a low-power gear in which the receiving end does not support the ability to wake up based on a control frame, and the link between the first device and the second device includes a main link and an auxiliary link. The method provided in this application may also include: receiving a third low-power request message from the second device on the auxiliary link, the third low-power request message including a third low-power request mode and a third low-power request direction; the third low-power request mode is to exit low power; the third low-power request direction is bidirectional; and sending a response message corresponding to the third low-power request message to the second device on the auxiliary link. The low-power state management of the port can be completed by either end device, which improves the flexibility and application scenarios of low-power management.

[0024] In another possible implementation, the method provided in the present application may further include: the sending link and the receiving link in the main link of the first device exit the low power consumption state; after exiting the low power consumption state, continuously sending the first control frame to perform link recovery.

[0025] In another possible implementation, the method provided in the present application may also include: the transmitting link in the main link of the first device exits the low-power state; one or more second control frames are sent to the second device; the second control frame is used to wake up the transmitting end through the high-speed link line, that is, all TX channels of the transmitting end send LLCF_EIE to the RX channel of the receiving end to wake up the RX channel of the receiving end; different channel rates correspond to different second control frame payloads; and the first control frame is continuously sent for link recovery. For a low-power state that supports wake-up by a wake-up frame, the first device can exit low power by sending a wake-up frame; and different payloads of the second control frame for wake-up are configured at different channel rates, so that the other end can determine the channel rate based on the payload of the control frame, complete channel recovery more quickly based on the channel rate, and exit the low-power state, thereby improving the efficiency of low-power management.

[0026] Another possible implementation method is that the method provided in the present application may also include: receiving one or more second control frames from a second device, the second control frame being used to wake up the transmitting end through a high-speed link line; different channel rates correspond to different second control frame payloads; and the receiving link in the main link of the first device exits the low power consumption state.

[0027] In another possible implementation, at channel rate HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed at 0x0000_FFFF repeated four times. At channel rate HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed at 0x0000_0000_FFFF_FFFF repeated four times. At channel rate HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed at 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated four times. The channel rate is HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed to: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

[0028] In another possible implementation, the first control frame is a logic layer training sequence 2 (Control Frame, Training Sequence 2, LLCF_TS2), and LLCF_TS2 is used for sending and receiving confirmation of synchronization status.

[0029] Another possible implementation manner is to continuously send the first control frame to perform link recovery, including: continuously sending the first control frame to lock the channel; and performing multi-channel alignment after the channel is successfully locked.

[0030] In another possible implementation, a specified number of first control frames are used to indicate that the channel is locked successfully.

[0031] In a second aspect, another method for managing a low-power state is provided, which is applied to a second device or a chip in the second device. The method may include: receiving a first low-power request message from a first device, the first low-power request message including a first low-power request mode, a first low-power request direction, and a low-power request gear; the first low-power request mode is to enter low power consumption; the first low-power request direction includes unidirectional or bidirectional; and sending a response message corresponding to the first low-power request message to the first device.

[0032] Through the solution provided by this application, the devices at both ends of the link negotiate to enter low power consumption through a low-power request message; the low-power state to be entered is indicated by the low-power request gear, and the link direction of entering the low-power state is indicated by the low-power request solution. This solution for managing low power consumption can realize the entry into multiple different low-power states through one request message, and can be applied to low-power management in different link directions, realizing flexible low-power state management that supports various scenarios.

[0033] In one possible implementation, the link between the first device and the second device includes a main link and an auxiliary link, the main link is a unidirectional transmission link from the first device to the second device, and the auxiliary link is a bidirectional link. Sending response information corresponding to the first low-power request message to the first device includes: sending the response information through the auxiliary link. In the scenario where the main link is a unidirectional transmission link (a pure unidirectional transmission link, that is, there is no main link for the second device to send data to the first device), the response message of the low-power request message is fed back through the auxiliary link, thereby realizing low-power management of the unidirectional transmission link.

[0034] In another possible implementation, the method provided in the present application may further include: the receiving link in the main link of the second device entering the low power state indicated by the low power request gear position. After the second device sends the above-mentioned response information, the negotiation with the first device is completed, and the second device can complete the receiving link in the main link of the second device entering the low power state indicated by the low power request gear position.

[0035] In another possible implementation, the direction of the first low power request is bidirectional, and the method provided in the present application may further include: the sending link in the main link of the second device enters a low power state indicated by the low power request gear.

[0036] Another possible implementation method, the low power request gear, may include one or more of the following: the receiving end does not support the low power gear based on the control frame wake-up capability; or the receiving end supports the low power gear based on the control frame wake-up capability.

[0037] In another possible implementation, the first low power request message is encapsulated as a logic layer main link management message, or a logic layer auxiliary link management message is transmitted.

[0038] Another possible implementation method is that the low-power request gear is a low-power gear in which the receiving end does not support the ability to wake up based on a control frame. The link between the first device and the second device includes a main link and an auxiliary link. The method provided in this application may also include: receiving a second low-power request message from the first device on the auxiliary link, the second low-power request message including a second low-power request mode and a second low-power request direction; the second low-power request mode is to exit low power; the second low-power request direction includes unidirectional or bidirectional; and sending a response message corresponding to the second low-power request message to the first device on the auxiliary link. In a low-power scenario that does not support wake-up by a wake-up frame, the low-power state has been exited by transmitting the low-power request message through the auxiliary link, thereby achieving more flexible low-power state management.

[0039] In another possible implementation, the method provided in the present application may further include: exiting the low-power state of the receiving link in the main link of the second device. After the second device sends the response information corresponding to the request to exit low-power, the negotiation with the first device is completed, and the second device can then complete the exit of the low-power state of the transmitting link in the main link of the first device.

[0040] In another possible implementation, the method provided herein may further include: exiting the low-power state for a transmitting link in a primary link of the second device; and, after exiting the low-power state, continuously sending the first control frame for link recovery. When the request message to exit low-power indicates bidirectionality, the request is for the port to exit the low-power state, and therefore, the transmitting link in the primary link of the second device also exits the low-power state.

[0041] In another possible implementation, the first low power request direction is unidirectional, and the second low power request direction is unidirectional.

[0042] In another possible implementation, the first low power request direction is bidirectional, and the second low power request direction is unidirectional.

[0043] In another possible implementation, the first low power request direction is bidirectional, and the second low power request direction is bidirectional.

[0044] In another possible implementation, the first low-power request direction is bidirectional, the low-power request gear is a low-power gear in which the receiving end does not support the ability to wake up based on a control frame, and the link between the first device and the second device includes a main link and an auxiliary link. The method provided in this application may also include: sending a third low-power request message to the first device on the auxiliary link, the third low-power request message including a third low-power request mode and a third low-power request direction; the third low-power request mode is to exit low power; the third low-power request direction is bidirectional; and receiving a response message corresponding to the third low-power request message from the first device on the auxiliary link. The low-power state management of the port can be completed by either end device, thereby improving the flexibility and application scenarios of low-power management.

[0045] In another possible implementation, the method provided in the present application may further include: the sending link and the receiving link in the main link of the second device exit the low power consumption state; after exiting the low power consumption state, continuously sending the first control frame to recover the link.

[0046] In another possible implementation, the method provided in the present application may further include: receiving one or more second control frames from the first device, the second control frames being used to wake up the transmitting end via a high-speed link; different channel rates corresponding to different second control frame payloads; and the receiving link in the main link of the second device exiting the low-power state. For a low-power state that supports wake-up by a wake-up frame, the first device can exit low power by sending a wake-up frame; and different payloads of the second control frame for wake-up are configured at different channel rates, so that the other end can determine the channel rate based on the payload of the control frame, complete channel recovery based on the channel rate more quickly, and exit the low-power state, thereby improving the efficiency of low-power management.

[0047] In another possible implementation, the method provided in the present application may further include: the sending link in the main link of the second device exits the low power consumption state; sending one or more second control frames to the first device; and continuously sending the first control frame for link recovery.

[0048] In another possible implementation, at channel rate HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed at 0x0000_FFFF repeated four times. At channel rate HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed at 0x0000_0000_FFFF_FFFF repeated four times. At channel rate HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed at 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated four times. The channel rate is HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed to: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

[0049] In another possible implementation, the first control frame is LLCF_TS2, and LLCF_TS2 is used for sending and receiving confirmation of synchronization status.

[0050] Another possible implementation manner is to continuously send the first control frame to perform link recovery, including: continuously sending the first control frame to lock the channel; and performing multi-channel alignment after the channel is successfully locked.

[0051] In another possible implementation, a specified number of first control frames are used to indicate that the channel is locked successfully.

[0052] On the third aspect, another method for managing a low power consumption state is provided, which is applied to a first device or a chip in the first device, and the link between the first device and the second device includes a main link and an auxiliary link. The method may include: in the auxiliary link, sending a second low power consumption request message to the second device, the second low power consumption request message including a second low power consumption request mode and a second low power consumption request direction; the second low power consumption request mode is to exit low power consumption; the second low power consumption request direction includes unidirectional or bidirectional; in the auxiliary link, receiving response information corresponding to the second low power consumption request message from the second device.

[0053] Through the solution provided in this application, in a scenario where wake-up frame wake-up is not supported, the low-power state is exited by transmitting a low-power request message through an auxiliary link, thereby achieving more flexible low-power state management.

[0054] The sending link of the main link of the first device is in a low power consumption mode that does not support the capability of waking up based on a control frame.

[0055] In another possible implementation, the method provided in this application may further include: exiting the low-power state of the transmitting link in the main link of the first device; and after exiting the low-power state, continuously sending the first control frame to perform link recovery. After the first device receives the response information corresponding to the request to exit low-power, the negotiation with the second device is completed, and the first device can complete the exit of the transmitting link in the main link of the first device from the low-power state and perform link recovery.

[0056] In another possible implementation, the method provided in the present application may further include: exiting the low-power state for a receiving link in the main link of the first device. When the request message to exit low-power indicates bidirectionality, the request is for the port to exit the low-power state, and therefore, the receiving link in the main link of the first device also exits the low-power state.

[0057] In another possible implementation, the main link between the first device and the second device is a unidirectional transmission link (pure unidirectional link), and the second low power consumption request direction is unidirectional or multidirectional.

[0058] In another possible implementation, the main link between the first device and the second device is a bidirectional transceiver link, and the second low power consumption request direction is bidirectional.

[0059] In another possible implementation, the first control frame is LLCF_TS2, and LLCF_TS2 is used for sending and receiving confirmation of synchronization status.

[0060] Another possible implementation manner is to continuously send the first control frame to perform link recovery, including: continuously sending the first control frame to lock the channel; and performing multi-channel alignment after the channel is successfully locked.

[0061] In another possible implementation, a specified number of first control frames are used to indicate that the channel is locked successfully.

[0062] In a fourth aspect, another method for managing a low power state is provided, which is applied to a second device or a chip in the second device. The link between the first device and the second device includes a main link and an auxiliary link. The method may include: in the auxiliary link, receiving a second low power request message from the first device, the second low power request message including a second low power request mode and a second low power request direction; the second low power request mode is to exit low power; the second low power request direction includes unidirectional or bidirectional; in the auxiliary link, sending a response information corresponding to the second low power request message to the first device.

[0063] Through the solution provided in this application, in a scenario where wake-up frame wake-up is not supported, the low-power state is exited by transmitting a low-power request message through an auxiliary link, thereby achieving more flexible low-power state management.

[0064] The receiving link of the main link of the second device is in a low power consumption mode that does not support the capability of waking up based on a control frame.

[0065] In another possible implementation, the method provided in the present application may further include: exiting the low-power state of the receiving link in the main link of the second device. After the second device sends the response information corresponding to the request to exit low-power, the negotiation with the first device is completed, and the second device can then complete the exit of the low-power state of the transmitting link in the main link of the first device.

[0066] In another possible implementation, the method provided herein may further include: exiting the low-power state for a transmitting link in a primary link of the second device; and, after exiting the low-power state, continuously sending the first control frame for link recovery. When the request message to exit low-power indicates bidirectionality, the request is for the port to exit the low-power state, and therefore, the transmitting link in the primary link of the second device also exits the low-power state.

[0067] In another possible implementation, the main link between the first device and the second device is a unidirectional transmission link (pure unidirectional link), and the second low power consumption request direction is unidirectional or multidirectional.

[0068] In another possible implementation, the main link between the first device and the second device is a bidirectional transceiver link, and the second low power consumption request direction is bidirectional.

[0069] In another possible implementation, the first control frame is LLCF_TS2, and LLCF_TS2 is used for sending and receiving confirmation of synchronization status.

[0070] Another possible implementation manner is to continuously send the first control frame to perform link recovery, including: continuously sending the first control frame to lock the channel; and performing multi-channel alignment after the channel is successfully locked.

[0071] In another possible implementation, a specified number of first control frames are used to indicate that the channel is locked successfully.

[0072] In the fifth aspect, another method for managing a low-power state is provided, which is applied to a first device or a chip in the first device. The method provided in this application may also include: the sending link in the main link of the first device exits the low-power state; one or more second control frames are sent to the second device; the second control frame is used to wake up the sending end through the high-speed link line; different channel rates correspond to different second control frame payloads; and the first control frame is continuously sent for link recovery.

[0073] Through the solution provided by the present application, for a low-power state that supports awakening by a wake-up frame, the first device can exit low power consumption by sending a wake-up frame; and configure different payloads of the second control frame for awakening at different channel rates, so that the other end can determine the channel rate based on the payload of the control frame, complete channel recovery more quickly based on the channel rate, exit the low-power state, and improve the efficiency of low-power management.

[0074] In another possible implementation, the method provided in the present application may further include: receiving one or more second control frames from the second device; and exiting the low power consumption state of the receiving link in the main link of the first device.

[0075] In another possible implementation, at channel rate HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed at 0x0000_FFFF repeated four times. At channel rate HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed at 0x0000_0000_FFFF_FFFF repeated four times. At channel rate HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed at 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated four times. The channel rate is HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed to: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

[0076] In another possible implementation, the first control frame is LLCF_TS2, and LLCF_TS2 is used for sending and receiving confirmation of synchronization status.

[0077] Another possible implementation manner is to continuously send the first control frame to perform link recovery, including: continuously sending the first control frame to lock the channel; and performing multi-channel alignment after the channel is successfully locked.

[0078] In another possible implementation, a specified number of first control frames are used to indicate that the channel is locked successfully.

[0079] In the sixth aspect, another method for managing a low power consumption state is provided, which is applied to a second device or a chip in the second device. The method provided in this application may also include: receiving one or more second control frames from the first device, the second control frame being used to wake up the sending end through a high-speed link line; different channel rates correspond to different second control frame payloads; and the receiving link in the main link of the second device exits the low power consumption state.

[0080] Through the solution provided by the present application, for a low-power state that supports awakening by a wake-up frame, the first device can exit low power consumption by sending a wake-up frame; and configure different payloads of the second control frame for awakening at different channel rates, so that the other end can determine the channel rate based on the payload of the control frame, complete channel recovery more quickly based on the channel rate, exit the low-power state, and improve the efficiency of low-power management.

[0081] In another possible implementation, the method provided in the present application may further include: the sending link in the main link of the second device exits the low power consumption state; sending one or more second control frames to the first device; and continuously sending the first control frame for link recovery.

[0082] In another possible implementation, at channel rate HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed at 0x0000_FFFF repeated four times. At channel rate HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed at 0x0000_0000_FFFF_FFFF repeated four times. At channel rate HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed at 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated four times. The channel rate is HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed to: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

[0083] In another possible implementation, the first control frame is LLCF_TS2, and LLCF_TS2 is used for sending and receiving confirmation of synchronization status.

[0084] Another possible implementation manner is to continuously send the first control frame to perform link recovery, including: continuously sending the first control frame to lock the channel; and performing multi-channel alignment after the channel is successfully locked.

[0085] In another possible implementation, a specified number of first control frames are used to indicate that the channel is locked successfully.

[0086] In a seventh aspect, a device for managing a low power consumption state is provided, which is deployed in a first device or a chip in the first device. The device may include: a sending unit and a receiving unit.

[0087] A sending unit is used to send a first low power request message to the second device, where the first low power request message includes a first low power request mode, a first low power request direction, and a low power request gear; the first low power request mode is to enter low power consumption; the first low power request direction includes unidirectional or bidirectional.

[0088] A receiving unit is configured to receive response information corresponding to a first low power consumption request message from a second device.

[0089] It should be noted that the device for managing low power consumption state provided in the seventh aspect is used to implement the method for managing low power consumption state provided in the above-mentioned first aspect or any possible implementation method. Its specific implementation can refer to the first aspect or any possible implementation method of the first aspect, and will not be repeated here.

[0090] In an eighth aspect, another apparatus for managing a low power consumption state is provided, which is applied to a second device or a chip in the second device. The apparatus may include: a receiving unit and a sending unit.

[0091] A receiving unit is used to receive a first low power request message from a first device, where the first low power request message includes a first low power request mode, a first low power request direction, and a low power request gear; the first low power request mode is to enter low power consumption; the first low power request direction includes unidirectional or bidirectional.

[0092] The sending unit is configured to send response information corresponding to the first low power consumption request message to the first device.

[0093] It should be noted that the device for managing low power consumption state provided in the eighth aspect is used to implement the method for managing low power consumption state provided in the above-mentioned second aspect or any possible implementation method. Its specific implementation can refer to the second aspect or any possible implementation method of the second aspect, and will not be repeated here.

[0094] In a ninth aspect, another apparatus for managing a low power state is provided, which is deployed in a first device or a chip in the first device. The apparatus may include: a sending unit and a receiving unit.

[0095] The sending unit is used to send a second low power request message to the second device in the auxiliary link, where the second low power request message includes a second low power request mode and a second low power request direction; the second low power request mode is to exit low power; the second low power request direction includes unidirectional or bidirectional.

[0096] The receiving unit is configured to receive, on the auxiliary link, response information corresponding to the second low power consumption request message from the second device.

[0097] It should be noted that the device for managing low power consumption state provided in the ninth aspect is used to implement the method for managing low power consumption state provided in the third aspect or any possible implementation method. Its specific implementation can refer to the third aspect or any possible implementation method of the third aspect, and will not be repeated here.

[0098] In a tenth aspect, another apparatus for managing a low power consumption state is provided, which is applied to a second device or a chip in the second device. The apparatus may include: a receiving unit and a sending unit.

[0099] The receiving unit is used to receive a second low-power request message from the first device in the auxiliary link, where the second low-power request message includes a second low-power request mode and a second low-power request direction; the second low-power request mode is to exit low power consumption; and the second low-power request direction includes unidirectional or bidirectional.

[0100] The sending unit is configured to send response information corresponding to the second low power consumption request message to the first device over the auxiliary link.

[0101] It should be noted that the device for managing low power consumption state provided in the tenth aspect is used to implement the method for managing low power consumption state provided in the above-mentioned fourth aspect or any possible implementation method. Its specific implementation can refer to the fourth aspect or any possible implementation method of the fourth aspect, and will not be repeated here.

[0102] In an eleventh aspect, another apparatus for managing a low power state is provided, which is deployed in a first device or a chip in the first device. The apparatus may include: a management unit, a sending unit, and a recovery unit.

[0103] The management unit is configured to control the sending link in the main link of the first device to exit the low power consumption state.

[0104] The sending unit is used to send one or more second control frames to the second device; the second control frame is used to wake up the sending end through the high-speed link line; different channel rates correspond to different second control frame payloads.

[0105] The recovery unit is configured to continuously send the first control frame to perform link recovery.

[0106] It should be noted that the device for managing low power consumption state provided in the eleventh aspect is used to implement the method for managing low power consumption state provided in the above-mentioned fifth aspect or any possible implementation method. Its specific implementation can refer to the fifth aspect or any possible implementation method of the fifth aspect, and will not be repeated here.

[0107] In a twelfth aspect, another apparatus for managing a low power consumption state is provided, which is applied to a second device or a chip in the second device. The apparatus may include: a receiving unit and a management unit.

[0108] The receiving unit is used to receive one or more second control frames from the first device, where the second control frames are used to wake up the transmitting end through the high-speed link line; different channel rates correspond to different second control frame payloads.

[0109] The management unit is configured to control the receiving link in the main link of the second device to exit the low power consumption state.

[0110] It should be noted that the device for managing low power consumption state provided in the twelfth aspect is used to implement the method for managing low power consumption state provided in the above-mentioned sixth aspect or any possible implementation method. Its specific implementation can refer to the sixth aspect or any possible implementation method of the sixth aspect, and will not be repeated here.

[0111] In the thirteenth aspect, a computing device is provided, which includes a memory and at least one processor, the memory being used to store a set of computer instructions; when the processor executes this set of computer instructions, it performs the operations of the method described in any one of the above-mentioned aspects one to six, or any possible implementation method.

[0112] In a fourteenth aspect, a chip is provided, comprising one or more interface circuits and one or more processors; the interface circuits are configured to receive signals from a memory of an electronic device and transmit the received signals to the processors, the signals comprising computer instructions stored in the memory. When the processors execute the computer instructions, the electronic device performs the steps of the method described in any one of aspects one to six, or any possible implementation thereof.

[0113] In the fifteenth aspect, a computer-readable storage medium is provided, comprising: computer software instructions; when the computer software instructions are executed in a computer, the computer executes the operations of the method described in any one of the first to sixth aspects, or any possible implementation method.

[0114] In the sixteenth aspect, a computer program product, when running on a computer, enables the computer to execute the operating steps of the method described in any one of the above-mentioned aspects one to six, or any possible implementation method.

[0115] In the seventeenth aspect, a data transmission system is provided, which includes a data sending device and a data receiving device, the data sending device includes the device for managing the low power consumption state as described in any one of the above-mentioned seventh aspect, and the data receiving device includes the device for managing the low power consumption state as described in the above-mentioned eighth aspect.

[0116] In the eighteenth aspect, a data transmission system is provided, which includes a data sending device and a data receiving device, the data sending device includes the device for managing the low power consumption state as described in any one of the above-mentioned ninth aspect, and the data receiving device includes the device for managing the low power consumption state as described in the above-mentioned tenth aspect.

[0117] In the nineteenth aspect, a data transmission system is provided, which includes a data sending device and a data receiving device, the data sending device includes the device for managing the low power consumption state as described in any one of the above-mentioned eleventh aspects, and the data receiving device includes the device for managing the low power consumption state as described in the above-mentioned twelfth aspect.

[0118] The solutions provided in the seventh to nineteenth aspects are used to implement the methods provided in any one of the first to sixth aspects, and therefore can achieve the same beneficial effects as any one of the first to sixth aspects, and will not be repeated here.

[0119] It should be noted that various possible implementations of any of the above aspects can be combined under the premise that the solutions are not contradictory. BRIEF DESCRIPTION OF THE DRAWINGS

[0120] FIG1 is a schematic structural diagram of a data transmission system provided in an embodiment of the present application;

[0121] FIG2 is a schematic diagram of the structure of another data transmission system provided in an embodiment of the present application;

[0122] FIG3 is a schematic diagram of basic components of an electronic device provided in an embodiment of the present application;

[0123] FIG4 is a schematic diagram of inter-interface transmission provided in an embodiment of the present application;

[0124] FIG5 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application;

[0125] FIG6 is a flow chart of a method for managing a low power consumption state according to an embodiment of the present application;

[0126] FIG7 is a flow chart of another method for managing a low power consumption state provided in an embodiment of the present application;

[0127] FIG8 is a flow chart of another method for managing a low power consumption state provided in an embodiment of the present application;

[0128] FIG9 is a flow chart of another method for managing a low power consumption state provided in an embodiment of the present application;

[0129] FIG10 is a flow chart of another method for managing a low power consumption state according to an embodiment of the present application;

[0130] FIG11 is a flow chart of another method for managing a low power consumption state according to an embodiment of the present application;

[0131] FIG12 is a flow chart of another method for managing a low power consumption state according to an embodiment of the present application;

[0132] FIG13 is a flow chart of another method for managing a low power consumption state according to an embodiment of the present application;

[0133] FIG14 is a schematic diagram of the structure of an LLMMP provided in an embodiment of the present application;

[0134] FIG15 is a schematic structural diagram of an LLSMP provided in an embodiment of the present application;

[0135] FIG16 is a schematic diagram of a main link differential channel signal provided in an embodiment of the present application;

[0136] FIG17 is a schematic diagram of a channel status management model provided in an embodiment of the present application;

[0137] FIG18 is a schematic diagram of a channel state transition according to an embodiment of the present application;

[0138] FIG19 is a schematic diagram of another channel state transition according to an embodiment of the present application;

[0139] FIG20A is a schematic diagram of another channel state transition according to an embodiment of the present application;

[0140] FIG20B is a schematic diagram of a link architecture corresponding to a TYPE-C MDP port according to an embodiment of the present application;

[0141] FIG20C is a schematic diagram of a link architecture corresponding to a TYPE-C MUP port according to an embodiment of the present application;

[0142] FIG20D is a schematic diagram of a link architecture corresponding to a TYPE-C DRD port provided in an embodiment of the present application;

[0143] FIG21 is a flow chart of another method for managing a low power consumption state according to an embodiment of the present application;

[0144] FIG22 is a flow chart of another method for managing a low power consumption state according to an embodiment of the present application;

[0145] FIG23 is a flow chart of another method for managing a low power consumption state according to an embodiment of the present application;

[0146] FIG24 is a flow chart of another method for managing a low power consumption state according to an embodiment of the present application;

[0147] FIG25 is a flow chart of another method for managing a low power consumption state provided in an embodiment of the present application;

[0148] FIG26 is a schematic structural diagram of a device for managing a low power consumption state provided by an embodiment of the present application;

[0149] FIG27 is a schematic structural diagram of another apparatus for managing a low power consumption state provided by an embodiment of the present application;

[0150] FIG28 is a schematic structural diagram of another apparatus for managing a low power consumption state provided in an embodiment of the present application;

[0151] FIG29 is a schematic structural diagram of another apparatus for managing a low power consumption state provided in an embodiment of the present application;

[0152] Figure 30 is a structural diagram of another device for managing low power consumption state provided in an embodiment of the present application. DETAILED DESCRIPTION

[0153] In the embodiments of the present application, in order to clearly describe the technical solutions of the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity or execution order, and words such as "first" and "second" do not necessarily mean different. There is no order of precedence or priority between the technical features described by "first" and "second".

[0154] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0155] In the embodiments of the present application, at least one can also be described as one or more, and multiple can be two, three, four or more, which is not limited in this application.

[0156] In addition, the network architecture and scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0157] To facilitate understanding, the relevant terms involved in the embodiments of this application are first explained.

[0158] Lane: refers to the circuit used to transmit signals. A single-ended channel consists of one line, and a high-speed differential channel consists of a pair of lines.

[0159] Link: A link is used to transmit data signals or power, and is generally composed of one or more channels. A link is a collection of channels or a conductor line used for power supply.

[0160] Main Link: A point-to-point link consisting of one or more channels based on high-speed differential signaling. It is used to transmit high-speed business data (also known as "high-speed data"), such as audio and video signals, third-party protocol data, and other high-speed data. A main link can be bidirectional, meaning that channels in different directions exist within the main link, or unidirectional, meaning that channels in the main link have the same direction.

[0161] Sideband link (SL): A point-to-point link consisting of one transmit and one receive channel based on low-speed single-ended signaling. It is used to transmit low-speed data, such as device management signals, port management signals, bandwidth management signals, and power management signals. It is also used to transmit control messages. A sideband link is bidirectional.

[0162] Transmitter Side / Receiver Side: The two sides of a link (usually consisting of multiple channels) are called the transmitter and receiver, respectively. Data flows from the transmitter to the receiver.

[0163] If the port main link only includes a unidirectional link, the main link of the port has only a transmitting end or a receiving end. If the port main link is a bidirectional link, the main link of the port has both a transmitting end and a receiving end.

[0164] Logical layer control frame (LLCF): A special code pattern used to implement link management functions such as link training and status update. In the present invention, LLCF is also referred to as CF, so LLCF_TS1 is equivalent to CF_TS1, and LLCF_TS2 is equivalent to CF_TS2.

[0165] The technical solution provided in this application can be applied to a data transmission system including multiple data transmission devices, which can be devices, chips applied to devices, or interface devices, etc. In this data transmission system, a data transmission device (for example, a data sending device) and a data transmission device (for example, a data receiving device) can be directly connected, or indirectly connected through a switching device such as a router, that is, the multiple data transmission devices can all be connected to the switching device. In this application, data transmission can be performed between the multiple data transmission devices in a wired manner or in a wireless manner. In addition, when data transmission is performed between the multiple data transmission devices, signals can be transmitted directly or through an interface device.

[0166] When the data transmission device is a chip in a device, the chips in the data transmission system can be interconnected via wired or wireless means. The chip can be a chip in the device, a chip in a docking station, or a chip in an adapter, etc. The docking station can be connected to a Gigabit Ethernet port, a video graphics array (VGA), an HDMI port, a flash memory (TF) card, a secure digital (SD) card, a charging port, and a USB port, etc.

[0167] Optionally, when the data transmission device is a chip, the chip may further include an interface module, that is, the present application may be applied to an interface module for interconnecting chips. The interface module may be understood as an intellectual property (IP) module integrated inside the chip. Alternatively, the interface module may also be sold separately as an IP module. For example, the chip may be a system on chip (SoC), a central processing unit (CPU), or a graphics processing unit (GPU), etc., and the above-mentioned interface module may be an interface module in the SoC, CPU, or GPU, etc. Optionally, the interface module may be a transmitting circuit and / or a receiving circuit.

[0168] The following uses the data transmission system including multiple devices as an example to illustrate the structure of the data transmission device.

[0169] FIG1 is a schematic diagram of the structure of a data transmission system provided in an embodiment of the present application. The data transmission system includes a first device 110 and a second device 120, which are connected to each other via a wired or wireless method, such as a cable. Signals can be transmitted between the first device 110 and the second device 120, such as audio and video data or charging signals.

[0170] In an example, the first device 110 may be a set-top box, and the second device 120 may be a television. The set-top box and the television may be connected via a cable, and the set-top box may transmit audio and video data to the television via the cable.

[0171] In another example, the first device 110 is a display, and the second device 120 is a game controller. The display and the game controller can be connected via a cable, and the game controller can transmit control information to the display via the cable.

[0172] Optionally, the first device 110 may include interface A, and the second device may include interface B. The connection between the first device 110 and the second device 120 can be specifically a connection between interface A of the first device 110 and interface B of the second device 120. For example, interface A of the first device 110 and interface B of the second device 120 are connected via a cable.

[0173] Figure 2 is a schematic diagram of the structure of another data transmission system provided in an embodiment of the present application. The data transmission system includes multiple devices 210 and a router 220. The multiple devices 210 can be connected to the router 220 via a wired or wireless manner. For example, the multiple devices 210 can all be connected to the router 220 via a cable. Among them, any two devices in the multiple devices 210 can transmit signals through the router 220, for example, to transmit audio and video data or charging signals.

[0174] In one example, the multiple devices 210 may include a display 211, a set-top box 212, and an audio player (e.g., MP3 (Moving Picture Experts Group Audio Layer-3)) 213. The set-top box 212 may transmit audio and video data to the display 211 via the router 220. The set-top box 212 may also transmit audio data to the audio player 213 via the router 220. In addition, the multiple devices 210 may include two interconnected devices. For example, the multiple devices 210 may also include a game controller 214. The game controller 214 may be connected to the display 211 and transmit control information to the display 211.

[0175] Optionally, each of the multiple devices 210 may include an interface, and the router 220 may include multiple interfaces, and the interface of each of the multiple devices 210 may be connected to one of the multiple interfaces of the router 220. For example, the multiple devices 210 include a display, a set-top box, a game controller, and an audio player, and the multiple interfaces of the router 220 include a first interface to a fourth interface, the interface of the display is connected to the first interface of the router 220 via a cable, the interface of the set-top box is connected to the second interface of the router 220 via a cable, the interface of the game controller is connected to the third interface of the router 220 via a cable, and the interface of the audio player is connected to the fourth interface of the router 220 via a cable.

[0176] The devices in the above-mentioned system with data transmission capabilities can be referred to as communication devices. The communication devices can be deployed on land, including indoors or outdoors, and can be handheld or vehicle-mounted. The communication devices can also be deployed on water (such as ships) or in the air (such as aircraft, balloons, and satellites). The communication devices can be applied in different scenarios. Exemplarily, the communication device may include, but is not limited to: a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a camera, a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), an audio device, an audio and video player, a set-top box, a game console, a printer, a mouse, a keyboard, an in-vehicle device (such as a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed train, etc.), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (such as a refrigerator, a television, an air conditioner, an electric meter, etc.), an intelligent robot, a workshop device, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, or a wireless terminal in a smart home, a flying device (such as an intelligent robot, a hot air balloon, Optionally, the signals transmitted between the above communication devices may include but are not limited to: audio and video signals, radio frequency signals, Internet of Things data and charging signals.

[0177] In this application, the interface specifications used for signal transmission between devices in a data transmission system may include, but are not limited to, the Universal Serial Bus (USB) interface specification, the High Definition Multimedia Interface (HDMI) interface specification, the DisplayPort (DP) interface specification, the Unified Multimedia Interconnection (UMI) interface specification, and the Peripheral Component Interconnect Express (PCI-Express) interface specification. Accordingly, the interface may be an HDMI interface, a Type-C interface, or the like.

[0178] For example, in the above examples, the interface connection method between the set-top box and the TV, or the interface connection method between the game console and the monitor can be connected through a USB cable, and the interface standard followed is the USB interface specification, or the connection method can be connected through an HDMI cable, and the interface standard followed is the HDMI interface specification.

[0179] It will be understood that the interface specifications used for signal transmission between the above-mentioned devices are merely exemplary. In actual applications, the interface specifications may also include other or any interface specifications that may appear in the future, such as a unified media interconnection (UMI) interface, etc., and the embodiments of the present application are not specifically limited to this.

[0180] In this application, when the above-mentioned device is an electronic device, FIG3 is a schematic diagram of the basic components of an electronic device. The electronic device includes an interface chip 300 (Uniform Multimedia Interconnect Interface), which includes one or more adapters 301, a management and control adapter 302, and one or more ports 303. Alternatively, when the electronic device is a routing device, the interface chip 300 only includes one or more ports 303. Each of the one or more adapters 301 can be coupled to an external component of the interface chip 300. The management and control adapter 302 can be coupled to a component outside the interface chip 300 for management and control. The port 303 can be coupled to a connector 304 of the electronic device, which is used to couple to external devices of the electronic device. One or more adapters 301 can be a transmit / receive adapter. For example, when the adapter 301 is used to adapt audio and video formats, the adapter 301 can be an audio and video transmit / receive adapter. When the adapter 301 is used to adapt a third-party protocol, the adapter 301 can be a third-party protocol adapter.

[0181] The basic components of different electronic devices can be combined to form a variety of different device types. For example, an electronic device may include a source device with at least one downstream port and at least one audio and video transmitter adapter, or a source device with at least one upstream port and an audio and video receiver adapter, or a docking station device with at least one upstream port, at least one audio and video receiver adapter, and at least one traditional audio and video interface, or a routing device with at least one downstream port and at least one upstream port but without an audio and video transmitter adapter or an audio and video receiver adapter, or a composite device with both an upstream port and a downstream port.

[0182] A link channel model provided by an embodiment of the present application is shown in Figure 4. Links between devices may include a primary link and an auxiliary link.

[0183] In one possible embodiment, the main link may include multiple channels, each of which may support unidirectional transmission; the auxiliary link may include two unidirectional channels in different directions. In other possible embodiments, the main link may include multiple channels, and the directions of the channels may be different. Exemplarily, a main link may include multiple channels, for example, the number of the multiple channels may be 4 or 8, etc. The more channels the main link includes, the faster the corresponding data transmission speed. Exemplarily, as shown in FIG4 , the main link may include n transmitting channels TX0-TXn and m receiving channels RX0-RXm, and the auxiliary link may include a transmitting channel SBTX and a receiving channel SBRX, where n and m are positive integers.

[0184] Furthermore, a power-bus link (PL) and a cable-information link (CL) may be included between devices. The cable-information link can be used to transmit cable information, such as cable model and cable capability information. The power-bus link and the cable-information link are not shown in the figure.

[0185] Exemplarily, the main link mainly realizes the transmission of ultra-high-definition audio and video signals and high-speed data (such as USB3). The main link can support bidirectional transmission, and each direction includes multiple differential channels (Lane). Each differential channel consists of 1 pair (2) differential lines, and each channel only supports unidirectional transmission. Each differential line includes a transmitter TX and a receiver RX. In this application, TX refers to the main link transmitter by default, and RX refers to the main link receiver by default. The main link can also support unidirectional transmission. Each differential channel is a high-speed channel, and the supported rate is generally above 1Gbps, such as 2Gbps, 4Gbps, 8Gbps, 10Gbps, 12Gbps, 16Gbps, 20Gbps, 24Gbps, etc.

[0186] In the link channel model shown in Figure 4, the high-speed main link of a device port consists of a transmit link (the link at the transmit end of the port), used to send data to the peer end, and a receive link (the link at the receive end of the port), used to receive data from the peer end. The port transmit link (also known as the logical sublayer transmit link, TX_Link) includes all TX channels of the port, and the port receive link (also known as the logical sublayer receive link, RX_Link) includes all RX channels of the port.

[0187] The auxiliary link supports bidirectional transmission and consists of two single-ended channels in different directions. Each single-ended channel includes a line, each of which includes an auxiliary link transmitter (SLTX) and an auxiliary link receiver (SLRX). The auxiliary link transmits low-speed data (such as control data, used for inter-device management and control, such as device discovery, capability query, device configuration, and device control) through the single-ended channel. Each single-ended channel is a low-speed channel, generally supporting a rate of less than 1 Gbps, such as 12.5 Mbps. Due to the relatively low rate supported, the auxiliary link consumes less power and can be kept in a normally open state.

[0188] The terms "high-speed channel," "high-speed differential channel," and "differential channel" in this application are synonymous and refer to the high-speed channel of the primary link. The terms "low-speed channel," "single-ended channel," and "low-speed single-ended channel" in this application are synonymous and refer to the low-speed channel of the auxiliary link. This will not be elaborated on in detail in the following sections.

[0189] It should be noted that the entry / exit of the low power state described in this application refers to the entry / exit of the channel in the main link into the low power state. Further, during data transmission, when the main link is available, the main link is used to transmit data first.

[0190] The solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0191] In one aspect, an embodiment of the present application provides a schematic structural diagram of a computing device 50. The computing device 50 can implement the functions of the first device 110 or the second device 120 shown in FIG1 .

[0192] 5 , the computing device 50 may include a processor 5010 , a bus 5020 , a memory 5030 , and a communication interface 5040 . The processor 5010 , the memory 5030 , and the communication interface 5040 are connected via the bus 5020 .

[0193] It should be understood that in this embodiment, the processor 5010 may be a central processing unit (CPU), and the processor 3010 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0194] The processor 5010 may also be a graphics processing unit (GPU), a neural network processing unit (NPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the program of the present application.

[0195] The communication interface 5040 is used to implement communication between the computing device 50 and external devices or components.

[0196] The bus 5020 may include a path for transmitting information between the above-mentioned components (such as the processor 5010 and the memory 5030). In addition to the data bus, the bus 5020 may also include a power bus, a control bus, and a status signal bus. However, for the sake of clarity, various buses are labeled as bus 5020 in the figure. The bus 5020 may be a peripheral component interconnect express (PCIe) bus, an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a computer express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The bus 5020 can be divided into an address bus, a data bus, a control bus, etc.

[0197] As an example, computing device 50 may include multiple processors. The processor may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and / or computing units for processing data (e.g., computer program instructions).

[0198] It is worth noting that FIG5 only takes the computing device 50 including one processor 5010 and one memory 5030 as an example. Here, the processor 5010 and the memory 5030 are respectively used to indicate a type of device or equipment. In a specific embodiment, the number of each type of device or equipment can be determined according to business requirements.

[0199] The memory 5030 may be a volatile memory pool or a non-volatile memory pool, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0200] For example, the processor 5010 may perform the following functions by running or executing the software programs and / or modules stored in the memory 5030:

[0201] A first low power request message is sent to a second device, where the first low power request message includes a first low power request mode, a first low power request direction, and a low power request gear; the first low power request mode is to enter low power consumption; the first low power request direction includes one-way or two-way; and a response message corresponding to the first low power request message is received from the second device.

[0202] For example, the processor 5010 may perform the following functions by running or executing the software programs and / or modules stored in the memory 5030:

[0203] Receive a first low power request message from a first device, where the first low power request message includes a first low power request mode, a first low power request direction, and a low power request gear; the first low power request mode is to enter low power consumption; the first low power request direction includes one-way or two-way; and send response information corresponding to the first low power request message to the first device.

[0204] For example, the processor 5010 may perform the following functions by running or executing the software programs and / or modules stored in the memory 5030:

[0205] In the auxiliary link, a second low-power request message is sent to the second device, where the second low-power request message includes a second low-power request mode and a second low-power request direction; the second low-power request mode is to exit low power consumption; the second low-power request direction includes unidirectional or bidirectional; in the auxiliary link, a response information corresponding to the second low-power request message from the second device is received.

[0206] For example, the processor 5010 may perform the following functions by running or executing the software programs and / or modules stored in the memory 5030:

[0207] In the auxiliary link, a second low-power request message is received from the first device, where the second low-power request message includes a second low-power request mode and a second low-power request direction; the second low-power request mode is to exit low power consumption; the second low-power request direction includes unidirectional or bidirectional; in the auxiliary link, a response information corresponding to the second low-power request message is sent to the first device.

[0208] For example, the processor 5010 may perform the following functions by running or executing the software programs and / or modules stored in the memory 5030:

[0209] Control the sending link in the main link of the first device to exit the low power consumption state; send one or more second control frames to the second device; the second control frame is used to wake up the sending end through the high-speed link line; different channel rates correspond to different second control frame payloads; continue to send the first control frame for link recovery.

[0210] For example, the processor 5010 may perform the following functions by running or executing the software programs and / or modules stored in the memory 5030:

[0211] Receive one or more second control frames from the first device, where the second control frames are used to wake up the transmitter through a high-speed link line; different channel rates correspond to different second control frame payloads; and control the receiving link in the main link of the second device to exit a low power consumption state.

[0212] On the other hand, embodiments of the present application provide a method for managing a low-power state, the method being used to enter a low-power state, and the method being applicable to a data transmission system including a first device and a second device. For example, the method can be applied to the data transmission system illustrated in FIG1 or FIG2 . The method is used to enter a low-power state.

[0213] Furthermore, the management of the low power state described in this application refers to the process of managing the low power state of the main link (ML) between devices.

[0214] As shown in FIG6 , the method for managing a low power consumption state for entering a low power consumption state provided by the present application may include:

[0215] S601: A first device sends a first low power consumption request message to a second device.

[0216] The first low power request message includes a first low power request mode, a first low power request direction, and a low power request gear.

[0217] Specifically, the low power request mode is used to indicate whether the purpose of the low power request message is to enter low power or exit low power. Exemplarily, the first low power request mode is to enter low power.

[0218] The low power request direction is used to indicate whether the low power request message is used to request the transmit link of the primary link of the first device (unidirectional) to enter low power consumption, or to request both the transmit link and receive link of the primary link of the first device (bidirectional) to enter low power consumption. The first low power request direction includes unidirectional or bidirectional.

[0219] Among them, the first low-power request direction is unidirectional, used to request the unidirectional link (the sending link of the first device) to enter a low-power state; the first low-power request direction is bidirectional, used to request the port to enter a low-power state, that is, the sending link and the receiving link of the port enter a low-power state.

[0220] Low power request gear, used to indicate the low power state requested to enter. Low power state refers to the link state that can reduce power consumption.

[0221] Exemplarily, the low-power request level may include one or more of the following: the receiving end does not support the low-power level for the control frame wakeup capability; or the receiving end supports the low-power level for the control frame wakeup capability. The low-power level can be configured based on actual needs, and the present embodiment does not limit the content of the low-power level.

[0222] Furthermore, in order for the receiving link to support the ability to wake up based on a wake-up frame, a related circuit needs to be designed, which can sense low-amplitude signals. The embodiments of the present application do not limit the specific implementation of this circuit.

[0223] Specifically, when the first device determines that its service is idle, it can execute the process of S601. During the execution of S601, the process of determining the low power state to enter and the low power request direction can be configured according to actual needs and is not limited in the embodiment of the present application.

[0224] Exemplarily, the first device determines that the service of the sending link (or the sending link and the receiving link) of the first device is idle, and can enter a low-power state of a certain gear to reduce power consumption. At this time, the first device executes the process of S601, and the first low-power request direction is the direction of the link with idle service, and the low-power gear is the low-power state corresponding to the service volume.

[0225] Furthermore, the first low power consumption request message may be encapsulated as a logic layer main link management message, or transmitted in a logic layer auxiliary link management message.

[0226] Exemplarily, the first low-power request message can be packaged as a logical layer main link management message, or a logical layer auxiliary link management message, and then transmitted in accordance with the method of transmitting the logical layer main link management message, or the logical layer auxiliary link management message in the interface protocol. The embodiment of the present application does not limit the transmission process.

[0227] It should be noted that the request messages (such as low power request messages) and response messages described in this application can be packaged as logical layer main link management messages, or logical layer auxiliary link management messages for transmission.

[0228] S602: The second device receives a first low power consumption request message from the first device.

[0229] The first low power request message received by the second device in S602 is the first low power request message sent by the first device to the second device in S601, which will not be described in detail here.

[0230] S603: The second device sends response information corresponding to the first low power consumption request message to the first device.

[0231] The response information corresponding to the first low power request message is used to instruct the second device to confirm the first low power request message, that is, the second device agrees with the content requested by the first low power request message.

[0232] Exemplarily, when the target link (the link requested by the first low-power request message to enter a low-power state) supports the low-power gear in the first low-power request message, the second device executes S603 and sends a response message corresponding to the first low-power request message to the first device. The embodiment of the present application does not limit the content and format of the response information and can be configured according to actual needs.

[0233] S604: The first device receives response information corresponding to the first low power consumption request message from the second device.

[0234] The response information corresponding to the first low power request message received by the first device in S604, that is, the response information corresponding to the first low power request message sent by the second device to the first device in S603, will not be repeated here.

[0235] Through the solution provided by this application, the devices at both ends of the link negotiate to enter low power consumption through a low-power request message; the low-power state to be entered is indicated by the low-power request gear, and the link direction of entering the low-power state is indicated by the low-power request solution. This solution for managing low power consumption can realize the entry into multiple different low-power states through one request message, and can be applied to low-power management in different link directions, realizing flexible low-power state management that supports various scenarios.

[0236] Furthermore, the link between the first device and the second device includes a main link and an auxiliary link; the main link is a bidirectional link from the first device to the second device, or the main link is a unidirectional transmission link from the first device to the second device, and the auxiliary link is a bidirectional link. The transmission rate of the main link for transmitting business data is greater than that of the auxiliary link. During the interaction between the first device and the second device, when the main link between the two is available, the main link is used to transmit data first.

[0237] In a possible implementation, the primary link between the first device and the second device is a bidirectional transceiver link, and the above processes from S601 to S604 are all performed in the primary link.

[0238] In another possible implementation, the primary link between the first device and the second device is a unidirectional transmission link, that is, a purely unidirectional link through which the first device transmits data to the second device. The above-mentioned processes S601 and S602 are performed on the primary link. In S603, the second device transmits response information corresponding to the first low-power request message via the auxiliary link. In S604, the first device receives the response information from the second device via the auxiliary link. This implements low-power state management of the unidirectional link.

[0239] Furthermore, based on the method for managing the low power consumption state illustrated in Figure 6, since the second device sends a response message of the first low power consumption request to the first device, indicating that the second device has agreed to the request to enter low power consumption, the link corresponding to the request to enter the low power consumption state can enter the low power consumption state.

[0240] In one possible implementation, the direction of the first low-power request is unidirectional. After S604, the sending link in the main link of the first device and the receiving link in the main link of the second device enter a low-power state. As shown in Figure 7, the method for managing the low-power state provided in an embodiment of the present application may also include S605 and S606.

[0241] S605: The sending link in the main link of the first device enters a low power consumption state indicated by the low power consumption request gear position.

[0242] S606: The receiving link in the main link of the second device enters a low power consumption state indicated by the low power consumption request gear position.

[0243] Specifically, when a link enters the low power consumption state, it means that all channels in the link enter the low power consumption state.

[0244] Furthermore, for a channel to enter a low-power state, the power supply of the transmitter (TX) or receiver (RX) of the channel can be adjusted to the power supply mode corresponding to the low-power state to be entered. The specific process of the channel entering the low-power state is not described in detail in the embodiment of the present application.

[0245] Furthermore, if the direction of the first low-power request is bidirectional, then after S604, the sending link and receiving link in the main link of the first device and the sending link and receiving link in the main link of the second device all enter a low-power state. As shown in FIG7 , the method for managing a low-power state provided in an embodiment of the present application may also include S607 and S608.

[0246] S607: The receiving link in the main link of the first device enters a low power consumption state indicated by the low power consumption request gear position.

[0247] S608: The sending link in the main link of the second device enters a low power consumption state indicated by the low power consumption request gear position.

[0248] On the other hand, an embodiment of the present application provides a method for managing a low-power state for exiting a low-power state, the method being used to exit a low-power state in which a receiving end does not support a control frame-based wake-up capability. The method can be applied to a data transmission system including a first device and a second device. For example, the method can be applied to the data transmission system illustrated in FIG1 or FIG2. The link between the first device and the second device includes a primary link and an auxiliary link.

[0249] Among them, in the low power state corresponding to the low power gear that does not support the receiving end based on the control frame wake-up capability, the main link between the devices does not support data transmission, and data transmission between the two devices can be carried out in the auxiliary link.

[0250] Specifically, when the first device determines that its business requires more link transmission, it needs to restore some links in a low-power state. The TX end device of the link that needs to be restored (such as the first device, or the second device) can execute the method for managing the low-power state for exiting the low-power state provided in the embodiment of the present application.

[0251] In one possible implementation, the method for managing a low power state for exiting a low power state provided in an embodiment of the present application can be applied to a low power state entered by any scheme for entering a low power state, and is not limited to the process illustrated in Figures 6 or 7 above.

[0252] In another possible implementation, the method for managing a low power consumption state for exiting a low power consumption state provided in an embodiment of the present application can be applied after the process illustrated in Figure 6 or Figure 7 above, and can be used to exit the low power consumption state entered by the process illustrated in Figure 6 or Figure 7 above.

[0253] As shown in FIG8 , the method for managing a low power consumption state for exiting a low power consumption state provided in an embodiment of the present application may include:

[0254] S801: A first device sends a second low power consumption request message to a second device in an auxiliary link.

[0255] The second low power request message includes a second low power request mode and a second low power request direction. The second low power request mode is to exit low power consumption. The second low power request direction may be unidirectional or bidirectional.

[0256] Among them, the second low-power request direction is unidirectional, used to request the unidirectional link (the sending link of the first device) to exit the low-power state; the second low-power request direction is bidirectional, used to request the port to exit the low-power state, that is, the sending link and receiving link of the port exit the low-power state.

[0257] The second low power consumption request direction may be determined by business requirements. During the execution of S801 , the process of determining the request direction for exiting low power consumption may be configured according to actual requirements and is not limited in the embodiment of the present application.

[0258] In a possible implementation, the second low power request message is used to exit the low power state entered by the process illustrated in FIG. 6 or 7 , the first low power request direction is unidirectional, and the second low power request direction is unidirectional.

[0259] In another possible implementation, the second low power request message is used to exit the low power state entered by the process illustrated in FIG. 6 or FIG. 7 . The first low power request direction is bidirectional, and the second low power request direction is unidirectional.

[0260] In another possible implementation, the second low power request message is used to exit the low power state entered by the process illustrated in FIG. 6 or 7 , the first low power request direction is bidirectional, and the second low power request direction is bidirectional.

[0261] S802: The second device receives a second low power consumption request message from the first device in the auxiliary link.

[0262] The second low power request message received by the second device in S802 is the second low power request message sent by the first device to the second device in S801, which will not be described in detail here.

[0263] S803: The second device sends response information corresponding to the second low power consumption request message to the first device in the auxiliary link.

[0264] The response information corresponding to the second low power request message is used to instruct the second device to confirm the second low power request message, that is, the second device agrees with the content requested by the second low power request message.

[0265] Exemplarily, when the target link (the link for exiting the low-power state requested by the second low-power request message) supports exiting the low-power state, the second device executes S803 and sends a response message corresponding to the second low-power request message to the first device. The embodiment of the present application does not limit the content and format of the response message and can be configured according to actual needs.

[0266] S804: The first device receives response information corresponding to the second low power consumption request message from the second device in the auxiliary link.

[0267] The response information corresponding to the second low power request message received by the first device in S804 , that is, the response information corresponding to the first low power request message sent by the second device to the first device in S803 , will not be described in detail here.

[0268] Through the solution provided in this application, in a scenario where wake-up frame wake-up is not supported, the low-power state is exited by transmitting a low-power request message through an auxiliary link, thereby achieving more flexible low-power state management.

[0269] Furthermore, based on the method for managing the low power consumption state illustrated in Figure 8, since the second device sends a response message of the second low power consumption request to the first device, indicating that the second device has agreed to the request to exit low power consumption, the link corresponding to the second low power consumption request can exit the low power consumption state.

[0270] In one possible implementation, the direction of the second low-power request is unidirectional. After S804, the sending link in the main link of the first device and the receiving link in the main link of the second device exit the low-power state. As shown in Figure 9, the method for managing the low-power state provided in the embodiment of the present application may also include S805 to S808.

[0271] S805: The sending link in the main link of the first device exits the low power consumption state.

[0272] Furthermore, for a channel to exit a low power consumption state, the power supply of the transmitter (TX) or receiver (RX) of the channel may be restored. The specific process of the channel exiting a low power consumption state is not described in detail in the embodiment of the present application.

[0273] S806: The receiving link in the main link of the second device exits the low power consumption state.

[0274] S807: After the sending link in the primary link of the first device exits the low power consumption state, the first device continues to send the first control frame to perform link recovery.

[0275] Specifically, in S807 , the first device continuously sends the first control frame in each channel of the transmission link of its primary link to perform link recovery.

[0276] The first control frame is used for channel training. Exemplarily, the first control frame may be a logical layer training sequence.

[0277] In one possible implementation, the first control frame includes a logical layer training sequence 0 (Control Frame, Training Sequence0, LLCF_TS0), a logical layer training sequence 1 (Control Frame, Training Sequence1, LLCF_TS1), and a logical layer training sequence 2 (Control Frame, Training Sequence2, LLCF_TS2) to perform complete channel training.

[0278] Among them, LLCF_TS0 is used for clock locking in the training phase; LLCF_TS1 is used for channel parameter tuning calculation in the training phase; LLCF_TS2 is used for sending and receiving confirmation of synchronization status. The embodiment of the present application does not limit the format and content of the first control frame.

[0279] In another possible implementation, the first control frame is LLCF_TS2. Continuously sending the first control frame for link recovery includes: continuously sending the first control frame to lock a channel; and after the channel is successfully locked, performing multi-channel alignment. That is, the first control frame is used for fast recovery.

[0280] Exemplarily, a specified number of first control frames is used to indicate that the channel is locked successfully.

[0281] S808. The second device continues to receive the first control frame.

[0282] Through the processes of S807 and S808, the sending link in the main link of the first device and the receiving link in the main link of the second device are restored, and enter a high-speed state (or high-speed transmission state, or service transmission state), that is, the main link for the first device to send data to the second device is restored.

[0283] Furthermore, if the direction of the second low-power request is bidirectional, then after S804, the sending link and receiving link in the main link of the first device and the sending link and receiving link in the main link of the second device both exit the low-power state. As shown in FIG9 , the method for managing the low-power state provided in the embodiment of the present application may also include S809 to S812.

[0284] S809: The sending link in the main link of the second device exits the low power consumption state.

[0285] S810: The receiving link in the main link of the first device exits the low power consumption state.

[0286] S811: After the sending link in the main link of the second device exits the low power consumption state, the second device continues to send the first control frame to recover the link.

[0287] S812: The first device continues to receive the first control frame.

[0288] Through the processes of S811 and S812, the sending link in the main link of the second device and the receiving link in the main link of the first device are restored, and enter a high-speed state (or high-speed transmission state, or service transmission state), that is, the main link for the first device to receive data from the second device is restored.

[0289] In another aspect, an embodiment of the present application provides a method for managing a low-power state, the method being used to exit a low-power state in which a receiving end does not support a control frame-based wake-up capability. The method can be applied to a data transmission system including a first device and a second device. For example, the method can be applied to the data transmission system illustrated in FIG1 or FIG2 . The link between the first device and the second device includes a primary link and an auxiliary link.

[0290] The method for managing a low-power state for exiting a low-power state provided in an embodiment of the present application can be applied after the process illustrated in Figure 6 or Figure 7 above, and is used to exit the low-power state entered by the process illustrated in Figure 6 or Figure 7 above, and the first low-power request direction is bidirectional. This method is similar to the process illustrated in Figure 8 or Figure 9 above, except that the request to exit low power is initiated by the second device. As shown in Figure 10, the method for managing a low-power state for exiting a low-power state provided in an embodiment of the present application may include:

[0291] S1001. A second device sends a third low power consumption request message to a first device in an auxiliary link.

[0292] The third low power request message includes a third low power request mode and a third low power request direction. The third low power request mode is to exit low power consumption; and the third low power request direction is bidirectional.

[0293] S1002: The first device receives a third low power consumption request message from the second device in the auxiliary link.

[0294] S1003: The first device sends response information corresponding to the third low power consumption request message to the second device in the auxiliary link.

[0295] S1004: The second device receives response information corresponding to the third low power consumption request message from the first device on the auxiliary link.

[0296] It should be noted that the process illustrated in FIG10 is of the same type as the process illustrated in FIG8 . For specific implementation, reference may be made to the process illustrated in FIG8 , and no further details will be given here.

[0297] Further, based on the schematic diagram of FIG10 , as shown in FIG11 , the method for managing a low power consumption state for exiting a low power consumption state provided in an embodiment of the present application may include S1005 to S1010 .

[0298] S1005: The sending link and the receiving link in the main link of the second device exit the low power consumption state.

[0299] S1006: The sending link and the receiving link in the main link of the first device exit the low power consumption state.

[0300] S1007: After the sending link of the second device in the main link exits the low power consumption state, the second device continues to send the first control frame to recover the link.

[0301] S1008. The receiving link in the main link of the first device continues to receive the first control frame.

[0302] S1009: After the sending link of the first device in the main link exits the low power consumption state, the first device continues to send the first control frame to recover the link.

[0303] S1010: A receiving link in a main link of a second device continues to receive a first control frame.

[0304] At this point, the sending link and receiving link in the main link of the first device, as well as the sending link and receiving link in the main link of the second device, have been restored and entered a high-speed state (or high-speed transmission state, or service transmission state), that is, the main link for the first device to send and receive data from the second device is restored.

[0305] In another aspect, embodiments of the present application provide another method for managing a low-power state for exiting a low-power state, the method being used to exit a low-power state in which a receiving end supports a control frame-based wake-up capability. The method can be applied to a data transmission system including a first device and a second device. For example, the method can be applied to the data transmission system illustrated in FIG1 or FIG2 .

[0306] Among them, in the low-power state corresponding to the low-power gear that the receiving end supports based on the control frame wake-up capability, the main link between devices supports data transmission, and data transmission between the two devices can be carried out in the main link.

[0307] Specifically, when the first device determines that its business requires more link transmission, it needs to restore some links in a low-power state. The TX end device of the link that needs to be restored (such as the first device, or the second device) can execute the method for managing the low-power state for exiting the low-power state provided in the embodiment of the present application.

[0308] In one possible implementation, the method for managing a low power state for exiting a low power state provided in an embodiment of the present application can be applied to a low power state entered by any scheme for entering a low power state, and is not limited to the process illustrated in Figures 6 or 7 above.

[0309] In another possible implementation, the method for managing a low power consumption state for exiting a low power consumption state provided in an embodiment of the present application can be applied after the process illustrated in Figure 6 or Figure 7 above, and can be used to exit the low power consumption state entered by the process illustrated in Figure 6 or Figure 7 above.

[0310] As shown in FIG12 , the method for managing a low power consumption state for exiting a low power consumption state provided in an embodiment of the present application may include:

[0311] S1201: A sending link in a primary link of a first device exits a low power consumption state.

[0312] S1202. The first device sends one or more second control frames to the second device.

[0313] The second control frame is used to wake up the transmitting end through the high-speed link line; different channel rates correspond to different second control frame payloads.

[0314] Exemplarily, the second control frame may be a logical layer electrical idle exit frame (Control Frame, Electrical Idle Exit, LLCF_EIE). The embodiment of the present application does not limit the content and format of the second control frame.

[0315] Exemplarily, the first device may send N_EIE second control frames to the second device, where N_EIE is the number of second control frames sent during link training.

[0316] S1203: The second device receives one or more second control frames from the first device.

[0317] S1204: The receiving link in the main link of the second device exits the low power consumption state.

[0318] S1205. The first device continues to send the first control frame to recover the link.

[0319] The second device completes link recovery with the first device by continuously receiving the first control frame.

[0320] Through the solution provided by the present application, for a low-power state that supports awakening by a wake-up frame, the first device can exit low power consumption by sending a wake-up frame; and configure different payloads of the second control frame for awakening at different channel rates, so that the other end can determine the channel rate based on the payload of the control frame, complete channel recovery more quickly based on the channel rate, exit the low-power state, and improve the efficiency of low-power management.

[0321] Furthermore, the content of the second control frame payload can be configured according to actual needs, which is not limited in the embodiments of the present application.

[0322] For example, at a channel rate of HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed at 0x0000_FFFF repeated four times. At a channel rate of HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed at 0x0000_0000_FFFF_FFFF repeated four times. At a channel rate of HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed at 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated four times. The channel rate is HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed to: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

[0323] Furthermore, the second control frame is used to wake up the unidirectional link. If the sending link of the main link of the second device also needs to be restored, as shown in Figure 13, the method for managing the low power consumption state for exiting the low power consumption state provided in an embodiment of the present application may include S1206 to S1210.

[0324] S1206. The sending link in the main link of the second device exits the low power consumption state.

[0325] S1207. The second device sends one or more second control frames to the first device.

[0326] S1208. The first device receives one or more second control frames from the second device.

[0327] S1209: The receiving link in the main link of the first device exits the low power consumption state.

[0328] S1210. The second device continues to send the first control frame to recover the link.

[0329] The first device completes link recovery with the second device by continuously receiving the first control frame.

[0330] The above embodiment describes the process of managing the low power consumption state. The following examples illustrate the contents involved in the above embodiment, but do not constitute specific limitations.

[0331] First, an example is given to illustrate the process of logical layer data transmission.

[0332] The logical layer main link (ML) uses two types of patterns to implement data processing and link management functions. The first type, LLB, uses the LLB as the basic unit to transmit transport layer data and logical layer management messages. The second type, LLCF, implements link management functions such as link training and status updates. LLB uses the full channel bandwidth for transmission and is evenly distributed across all enabled channels. LLCF uses independent channels for transmission to ensure the integrity of the LLCF pattern on a single channel.

[0333] Transport layer data and logic layer management messages need to be encapsulated into a data message structure, and the transport layer data and different management messages are distinguished through the data message type.

[0334] Logical Layer Data Packet (LLDP) encapsulates transport layer data. LLDP can only be transmitted over ML.

[0335] Logical layer management messages, including the Logical Layer Main Link Management Packet (LLMMP) and the Logical Layer Sideband Link Management Packet (LLSMP), are encapsulated and processed for logical layer management messages. LLMMP is transmitted over the ML, while LLSMP is transmitted over the SL. In scenarios where ML exists, ML is recommended for transmitting logical layer management messages.

[0336] As shown in Figure 14, a complete LLMMP structure is described. The entire data message is 8 bytes in total and consists of a logical layer packet header (LLPH), a logical layer packet payload (LLPP), and a cyclic redundancy check (CRC) code structure.

[0337] The LLPH field is fixed at 2 bytes in length. The LLPT field indicates the current data message type, and the LLMMP field is fixed at 0xF0. The Rsv field is reserved and is fixed at 0x0. The Logical Layer Management Message Type (LLMMT) field indicates the message type carried by the current LLMMP. The LLPP field is fixed at 4 bytes in length, and its content is determined by the logical layer management message to be transmitted. If the message length is less than 4 bytes, it is padded with reserved parameters, which are fixed at 0x0. The CRC field is fixed at 2 bytes and is filled with checksum information for all parameters in the Rsv, LLMMT, and LLPP fields of the current data message. The corresponding generating polynomial for the CRC is: g(x) = x16 + x12 + x5 + 1.

[0338] Figure 15 illustrates a complete LLSMP structure. The data packet has a variable length and consists of the LLPH, LLPP, and CRC structures. The LLPH is fixed at 2 bytes, with the Rsv and LLMMT fields consistent with the LLMMP. The Logical Layer Packet Length (LLPL) field indicates the current LLSMP message payload length. The LLPP length and content are determined by the logical layer management message being transmitted. The CRC is fixed at 2 bytes and contains checksum information for all parameters in the data packet except the CRC field.

[0339] In FIG14 and FIG15 , the CRC LS byte represents the least significant (LS), and the CRC MS byte represents the most significant (MS).

[0340] The low power management request message involved in this application is a logical layer management message, which can be encapsulated as LLMMP or LLSMP transmission. The low power management request message is illustrated below with an example.

[0341] The Low Power Request Message (LPRM) is a collection of low power request parameters, including entry / exit low power request, unidirectional / bidirectional low power request, and low power request gear (required when entering low power state, no such field when exiting low power state).

[0342] LPRM is used when the link is in service transmission state or LP3 low-power state (a low-power state in which the receiving end does not support wake-up frames). In service transmission state, when there is no service data or management message to be transmitted, a low-power entry request can be initiated. The entry request must include the low-power gear. In LP3 low-power state, when service data transmission needs to be restarted, an exit request can be initiated. The low-power gear corresponding to the exit request must be LP3. The current port negotiates with the peer end through LPRM to implement port link entry and exit low-power control.

[0343] LPRM requires a response except for LP0f. If the receiving end agrees to the low-power request, it must respond with an Ack to the LPRM; otherwise, it must respond with a Nack. LP0f does not require a response, forcing the other end to accept the LP0f low-power request. For more information about responses, refer to the following description of response information.

[0344] LPRM supports both ML and SL transmission. ML transmission is recommended for entering LPRM, and SL transmission is the only way to exit LPRM. The LLMMP format corresponding to ML transmission is shown in Table 1. The LLSMP format corresponding to SL transmission is shown in Table 2.

[0345] Table 1

[0346] Table 2

[0347] The response information is described with an example.

[0348] The acknowledgment message (Ack / Nack Message, Ack / Nack) is a set of responses to management messages.

[0349] Ack / Nack is used when a management message needs to be responded to. It is used to respond to the received information and feedback the current port's response or decision result to the corresponding information.

[0350] Ack / Nack does not require a response.

[0351] Ack / Nack can be transmitted via both ML and SL. The LLMMP format for ML transmission is shown in Table 3. The LLSMP format for SL transmission is shown in Table 4.

[0352] Table 3

[0353] Table 4

[0354] The following is an example of a link training start message.

[0355] The link training start message (TSM) is a collection of link training start flags, including the training start flags of all sending channels of the current port.

[0356] TSM is used to initiate link training. Application scenarios include: sending a TSM to initiate link training after port initialization in the initial link establishment scenario; sending a TSM to initiate link retraining in the event of an abnormal retraining scenario; and sending a TSM to initiate link recovery when exiting LP3 low-power scenarios. TSM is sent when initiating training or recovery; upon receiving a TSM, the receiver initiates training on the channel specified by the TSM.

[0357] Each channel message parameter is independent. If a channel is not enabled or does not exist, the corresponding message parameter is fixed to 0.

[0358] The TSM does not need to respond, but requires the other end to feed back a clock lock feedback message in tTSMResponse.

[0359] TSM supports both ML and SL transmission. The LLMMP format corresponding to ML transmission is shown in Table 5. The LLSMP format corresponding to SL transmission is shown in Table 6.

[0360] Table 5

[0361] Table 6

[0362] Next, an example description of the control frame is given.

[0363] Control frames are sent entirely on a single lane and are used to convey information such as link management and training sequences. The logical layer management message CFSLM indicates the insertion position of the control frame. Table 7 shows the structure of the control frame. Table 8 shows the contents of the control frame field.

[0364] Table 7

[0365] In the control frame structure, the contents of frame header 1, frame header 2, and frame header 3 are the same, forming a repetition code.

[0366] Unless otherwise specified, control frames (header + payload) are not scrambled or pre-coded.

[0367] Table 8

[0368] The frame type, checksum, payload length and description of the control frame involved in this application can be shown in Table 9 below.

[0369] Table 9

[0370] LLCF_TS0, used for clock locking during the training phase, with a payload of 0xAA of any length.

[0371] LLCF_TS1 is used for channel parameter tuning calculations during the training phase. The payload is a PRBS11 sequence of arbitrary length. Polynomial: G(x) = x 11 +x 2 +1, seed: 00110011001b.

[0372] LLCF_TS2 is used to confirm the synchronization status of transmission and reception. The length is fixed at 8 bytes. The payload is the bit flip (bit inversion) of the PRBS11 sequence. Polynomial: G(x) = x 11 +x 2 +1. Seed: 00110011001b.

[0373] The control frame electrical idle (LLCF_EI) is used to mark the end of the lane transmission, and the data thereafter should be discarded.

[0374] The logical layer data start (Control Frame Data Start, LLCF_DS) marks the starting position of a new logical block. The logical block data is transmitted immediately following LLCF_DS.

[0375] LLCF_EIE is used by the transmitter to wake up the channel through the high-speed link line. Different LLCF_EIEs should be sent at different rates:

[0376] At the single lane rate HS1 (2 Gbps / 4 Gbps), the payload length is 16B, and the payload is fixed at: 0x0000_FFFF_0000_FFFF_0000_FFFF_0000_FFFF, that is, 0x0000_FFFF is repeated four times in a row.

[0377] At a single lane rate of HS2 (6 Gbps / 8 Gbps), the payload length is 32 bytes, and the payload is fixed at 0x0000_0000_FFFF_FFFF repeated four times.

[0378] At a single lane rate of HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length is 64 bytes, and the payload is fixed at: 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated four times.

[0379] At a single lane rate of HS4 (20 Gbps / 24 Gbps), the payload length is 96 bytes, and the payload is fixed at: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF, repeated four times.

[0380] Pad logical layer control frame (LLCF_PAD) is used for padding.

[0381] The following is an example of power domains and low power levels.

[0382] The logic layer divides the power domain into VCC power and VSL power, as shown in Table 10. The VCC power is used to power the main business functions, and the VSL power is used to power the VCC power management logic, auxiliary link-related functions, physical layer calibration, equalization and other link training parameter storage registers, other special registers related to power management and facilitating LP3 fast wake-up.

[0383] Table 10

[0384] The low power consumption state involved in this application can be shown in Table 11.

[0385] Table 11

[0386] Among them, compared with power2, Power3 can shut down more functions of the analog transmitter and receiver to save power consumption.

[0387] The following example illustrates the design of the receiver based on LLCF_EIE wake-up.

[0388] To support the LLCF_EIE wake-up capability, the receiving link needs to design a related circuit that can sense low-amplitude signals, such as the V TX-DIFF-PP-IDLE .

[0389] Table 12

[0390] Figure 16 is a schematic diagram of the main link differential channel signal. The peak-to-peak value of the differential channel TX signal is shown in Figure 16 (a), and the main link differential channel signal schematic diagram shown in Figure 16 (b) is the differential channel signal V DIFF(t) Defined as the positive signal V D+(t) With the negative signal V D-(t) The voltage difference is: V DIFF(t) =V D+(t) -V D-(t) , differential channel TX signal peak-to-peak value VTX_DIFF-PP Defined as V TX_DIFF-PP =max(V DIFF )-min(V DIFF ).

[0391] The following is an example to illustrate link training and fast recovery.

[0392] The main link completes channel clock recovery and locking, channel equalization, channel locking, and multi-channel alignment through link training. The steps are described as follows:

[0393] Clock recovery and lock: The transmitter (TX channel) of each high-speed differential channel sends a special control frame LLCF_TS0 to the receiver (RX channel). The parameters selected by the transmitter (such as Swing parameters) support the receiver to complete clock lock.

[0394] Channel equalization: The transmitter of each high-speed differential channel sends a special control frame LLCF_TS1 to the receiver, selects appropriate equalization parameters (such as the transmitter selects appropriate FFE parameters), and improves the quality of the signal obtained by the receiver of each channel.

[0395] Channel locking: The transmitter of each high-speed differential channel sends a special control frame, LLCF_TS2, to the receiver to lock the data boundaries of each channel (such as being able to identify the start and end of the control frame), thereby achieving transmission and reception synchronization.

[0396] Multi-channel alignment: The transmitter of each high-speed differential channel sends a special control frame LLCF_DS to the receiver. After the receiver receives the LLCF_DS, if the skew between the LLCF_DS frames is less than the preset value, the receiver can receive data normally. The sending link or receiving link starts to receive high-speed service data and enters the high-speed link service transmission state (HS).

[0397] Fast recovery (Recover) is a fast training state. Compared with the complete link training process, the fast recovery process omits some training steps. For example, when exiting low power consumption, clock recovery and locking, channel equalization can be omitted, and training can be started directly from channel locking to enter the high-speed link service transmission state (HS).

[0398] The following is an example of the channel status management of the main link.

[0399] To maintain the main link status, this application defines a channel status management model, as shown in Figure 17.

[0400] Devices manage port status through a port management state machine. Each port in the Unified Multimedia Interconnection Protocol corresponds to a high-speed main link. Each port's high-speed main link consists of a transmit link (the link on the transmit side of the port, including all TX channels) and a receive link (the link on the receive side of the port, including all RX channels). A high-speed main link can contain 1 to 8 channels. The status of each link is managed by a transmitter link state machine (TXLKSM), a receiver link state machine (RXLKSM), and several lane state machines (Lane State Machines, LNSMs).

[0401] TXLKSM is the overall state machine for the port's transmit link, used to manage the overall state of the transmit link on the port. Each port has at most one TXLKSM.

[0402] RXLKSM is the overall state machine for the port receive link, used to manage the overall status of the receive link on the port. Each port has at most one RXLKSM.

[0403] LNSM is a channel state machine that manages the status of a channel on a port. Based on the channel's application mode, LNSM is divided into TX mode and RX mode, corresponding to LNSM(TX) and LNSM(RX) in Figure 17.

[0404] The LNSM in TX mode manages the status of a single TX channel on the current port. Each TX high-speed channel port corresponds to an LNSM (TX). The LNSM in RX mode manages the status of a single RX channel on the current port. Each RX high-speed channel port corresponds to an LNSM (RX).

[0405] The states and behaviors of the transmit link and receive link of a port are relatively independent and controlled by their respective link state machines. The power consumption and rate states of the transmit link and receive link can be different.

[0406] In the transmit link, the states and behaviors of different TX channels are relatively independent and controlled by their respective channel state machines. The rate states of all TX channels must remain consistent.

[0407] In the receive link, the states and behaviors of different RX channels are relatively independent and controlled by their respective channel state machines. The rate states of all RX channels must remain consistent.

[0408] The total number of channels on each port is not greater than 8, so the total number of LNSMs is not greater than 8.

[0409] Each port needs to report the overall port status based on the status of TXLKSM and RXLKSM.

[0410] LNSM manages the status of a single channel on the current port. This channel can operate in either TX or RX mode. The channel state transitions are shown in Figure 18, and a brief description of each channel state is shown in Table 13.

[0411] Table 13

[0412] Recovery can also be called a recovery state, and HS can also be called a high-speed state (or a high-speed transmission state, or a service transmission state).

[0413] The following describes the sending link status.

[0414] TXLKSM and LNSM(TX) are mutually dependent master-slave modules. TXLKSM performs link-level operations for multiple TX channels, while LNSM(TX) performs independent operations for a single TX channel.

[0415] In the Training, HS, Recovery, and LPx states of TXLKSM, the TXLKSM layer will initiate link-level operations (link entry / exit low power, link retraining, link recovery, multi-channel deskew, etc.) based on the overall status of the entire link and control LNSM (TX) to perform different operations.

[0416] The state transition of the sending link can be shown in Figure 19, and the description of each state of the sending link can be shown in Table 14.

[0417] Table 14

[0418] The following describes the receive link status.

[0419] RXLKSM and LNSM(RX) are mutually dependent master-slave modules. RXLKSM performs link-level operations for multiple RX channels, while LNSM(RX) performs independent operations for a single RX channel.

[0420] In the Training, HS, Recovery, and LPx states of RXLKSM, the RXLKSM layer will initiate link-level operations (link entry / exit low power, link retraining, link recovery, multi-channel deskew, etc.) based on the overall status of the entire link and control LNSM (RX) to perform different operations.

[0421] The state transition of the receiving link can be shown in Figure 20A, and the description of each state of the sending link can be shown in Table 15.

[0422] Table 15

[0423] The following describes the overall status of the port link.

[0424] The logic layer needs to provide real-time feedback on the overall link status for upper layer queries.

[0425] If the port has only a unidirectional TX channel link, the overall link status is the same as that of TXLKSM.

[0426] If the port has only the RX channel unidirectional link, the overall link status is the same as that of the RXLKSM.

[0427] For ports with bidirectional links, the link status report needs to be refreshed in combination with the TXLKSM and RXLKSM status. The refresh is based on the link status report mapping shown in Table 16 below.

[0428] Table 16

[0429] Next, the port link architecture is described.

[0430] The port link architecture supports both bidirectional and unidirectional link architectures. A bidirectional link architecture includes a set of transmit links and a set of receive links; a unidirectional link architecture includes only one set of transmit links or one set of receive links. The logical sublayer has different link architectures based on different port types and channel modes. Port types include: Main Downstream Port (MDP), Main Upstream Port (MUP), and Dual Role of Data (DRD); ​​and forward error correction (FEC) encoding modes include: Type-B and Type-C. Table 17 shows the port link architectures supported by the current protocol version.

[0431] Table 17

[0432] A Type-C MDP port has a total of four channels, supporting 4T0R, 3T1R, and 2T2R modes. 4T0R mode is a unidirectional link, supporting four TX_Link channels and no RX_Link. 3T1R mode is a bidirectional link, supporting three TX_Link channels and one RX_Link channel. 2T2R mode is a bidirectional link, supporting two TX_Link channels and two RX_Link channels. A Type-B MDP port has a total of eight channels, and its link architecture is similar to that of a Type-C MDP port. A Type-B MDP port supports 8T0R, 7T1R, 6T2R, 5T3R, and 4T4R modes. Different modes indicate different numbers of TX_Link and RX_Link channels in the architecture. For details, refer to the Type-C port link definition.

[0433] Among them, the 4T0R mode is a unidirectional link, that is, the aforementioned pure unidirectional transmission link.

[0434] Figure 20B shows the link architecture for a Type-C MDP port, consisting of a TX_Link and an RX_Link. The TX_Link consists of four transmit channels (TX Channel 0 to TX Channel 3), and the RX_Link consists of two receive channels (RX Channel 0 to RX Channel 1). Unidirectional link architectures support no receive channels. The paths corresponding to the dashed lines are enabled or disabled by configuring the channel mode. A total of four channels are enabled, supporting 4T0R, 3T1R, and 2T2R modes.

[0435] A Type-C MUP port has a total of four channels, supporting 0T4R, 1T3R, and 2T2R modes. 0T4R mode is a unidirectional link, supporting four RX_Link channels and no TX_Link. 1T3R mode is a bidirectional link, supporting three RX_Link channels and one TX_Link channel. 2T2R mode is a bidirectional link, supporting two RX_Link channels and two TX_Link channels. A Type-B MUP port has a total of eight channels, and its link architecture is similar to that of a Type-C MUP port. A Type-B MUP port supports 0T8R, 1T7R, 2T6R, 3T5R, and 4T4R modes. Different modes indicate different numbers of TX_Link and RX_Link channels in the architecture. For details, refer to the Type-C port link definition.

[0436] The scrambling code, also known as scramble, and the descrambling code, also known as unscramble, are used to independently scramble and descramble data on each channel. Precoding, also known as precoding, and unprecoding, also known as unprecoding, are used to independently precode and decode data on each channel. Control frame creation is also known as CF_Gen, and control frame parsing is also known as CF_Parse.

[0437] Figure 20C shows the link architecture corresponding to a Type-C MUP port, consisting of a TX_Link and an RX_Link. The TX_Link consists of two transmit channels, and the RX_Link consists of four receive channels. Unidirectional link architectures support no transmit channels. The paths corresponding to the dashed lines are enabled or disabled by configuring the channel mode. A total of four channels are enabled, supporting 0T4R, 1T3R, and 2T2R modes.

[0438] A Type-C DRD port has a total of four channels, supporting 4T0R, 3T1R, 2T2R, 1T3R, and 0T4R modes. 4T0R and 0T4R modes are unidirectional, while 3T1R, 2T2R, and 1T3R modes are bidirectional. For detailed architectures, refer to the MDP port architecture and MUP port architecture. A Type-B DRD port has a total of eight channels, and its link architecture is similar to that of a Type-C DRD port. A Type-B DRD port supports 8T0R, 7T1R, 6T2R, 5T3R, 4T4R, 3T5R, 2T6R, 1T7R, and 0T8R modes. Different modes indicate different numbers of TX_Link and RX_Link channels in the architecture. For details, refer to the definitions of Type-C MDP ports and Type-C MUP ports.

[0439] Figure 20D shows the link architecture corresponding to a Type-C DRD port, consisting of TX_Link and RX_Link. The TX_Link consists of four transmit channels, and the RX_Link consists of four receive channels. The paths corresponding to the dashed lines are enabled or disabled by configuring the channel mode. A total of four channels are enabled, supporting 4T0R, 3T1R, 2T2R, 1T3R, and 0T4R modes.

[0440] The following describes an example of a process in which a unidirectional link enters a low power consumption state.

[0441] As shown in FIG21 , the process of a unidirectional link entering a low power consumption state may include:

[0442] 1. Device A sends a unidirectional link entry LPRM request message to device B, requesting the link to enter LP0-LP2 low power consumption.

[0443] When the main link is working, device A preferentially sends LPRM through the transmission link of the main link ML. In the LPRM, LP_GEAR indicates the low power request gear (any one of LP0 to LP2), LP_MODE = 1b indicates entering low power, and LP_WAY = 0b indicates entering low power for a unidirectional link.

[0444] 2. Device B feeds back the Ack corresponding to LPRM to device A.

[0445] If device B sends back a NAck response to device A for LPRM, the process ends and neither device A nor device B enters low power consumption. The same applies to other low power consumption NACK processes, which will not be described in detail.

[0446] Furthermore, if the main link is a pure unidirectional link, that is, the main link of device A only includes a sending link, and the main link of device B only includes a receiving link, device B feeds back an ACK of LPRM through the auxiliary link.

[0447] 3. After all TX channels of device A have sent their service data, they send an LLCF_EI, and then all TX channels of device A enter a low-power state.

[0448] Device A sends an LLCF_EI to each TX channel. If device A only includes a transmit link, all TX channels of device A enter a low-power state, indicating that the transmit link and the overall link status of device A enter a low-power state.

[0449] All TX channels of device A refer to all channels in the transmit link of the main link of device A. All TX channels of device A entering the low power state means that all TX channels of device A enter the low power state indicated by LP_GEAR, which will not be described in detail later.

[0450] 4. After device B receives the LPRM sent by device A and receives LLCF_EI on all RX channels, all RX channels of device B enter a low power state (the low power state indicated by the low power request gear).

[0451] All RX channels of device B refer to all channels in the receive link of the main link of device B. All RX channels of device B entering the low power state means that all RX channels of device B enter the low power state indicated by LP_GEAR.

[0452] Furthermore, if device B only includes a receive link, all RX channels of device B enter low power consumption, that is, the receive link and the overall link state of device B enter a low power consumption state.

[0453] Furthermore, when device A or device B enters low power consumption, its port can retain relevant training information to support subsequent rapid recovery and exit from low power consumption. The retained training information may include: Swing parameters, FFE parameters, channel rate, etc. selected by the transmitter of each high-speed differential channel.

[0454] The following describes an example of the process of a port entering a low power consumption state.

[0455] As shown in Figure 22, the process of a port entering a low power state may include:

[0456] 1. Device A sends a low-power request LPRM to device B, indicating that its ports enter LP0 to LP3.

[0457] When the main link is operating, device A preferentially sends LPRM via the transmit link of the main link ML. In the LPRM, LP_GEAR indicates the low power request gear (any of LP0 to LP3), LP_MODE = 1b indicates entering low power, and LP_WAY = 1b indicates that the bidirectional link enters low power.

[0458] 2. Device B feeds back the Ack corresponding to LPRM to device A.

[0459] When the main link is working, device B preferably sends the Ack corresponding to the LPRM through the sending link of the main link ML.

[0460] Furthermore, if the main link is a pure unidirectional link, that is, the main link of device A only includes a sending link, and the main link of device B only includes a receiving link, device B feeds back an ACK of LPRM through the auxiliary link.

[0461] 3. After device A receives the Ack corresponding to LPRM, all TX channels send 4 LLCF_EIs after sending business data. Then, all TX channels of device A enter the low power state (the low power state indicated by the low power request gear).

[0462] Device A sends four LLCF_EIs to each TX channel.

[0463] All TX channels of device A enter the low power state, which means that all TX channels of device A enter the low power state indicated by LP_GEAR.

[0464] All TX channels of device A enter a low-power state, that is, the transmit link of device A enters a low-power state.

[0465] 4. After all RX channels of device B receive LLCF_EI, they send service data to all TX channels and then send four LLCF_EIs. Then all TX and RX channels of device B enter a low-power state.

[0466] All TX and RX channels of device B enter a low-power state, indicating that the transmit link, receive link, and overall link status of device B all enter a low-power state.

[0467] All TX and RX channels of device B enter the low power state, which means that all TX and RX channels of device B enter the low power state indicated by LP_GEAR.

[0468] 5. After all RX channels of device A receive LLCF_EI, all RX channels of device A enter a low power state.

[0469] All RX channels of device A enter the low-power state, indicating that the receive link of device A has entered the low-power state and the transmit link of device A has entered the low-power state. Therefore, the overall link state of device A enters the low-power state.

[0470] Furthermore, for purely unidirectional links, a low-power request can be initiated for the port to enter LP3 to save even more power. In this scenario, device A's port only includes a transmit link, and device B's port only includes a receive link. In this scenario, in step 2, device B feeds back the ACK corresponding to LPRM to device A via the auxiliary link. In step 4, after all Rx channels of device B receive LLCF_EI, all Rx channels of device B enter a low-power state. Since device A has no receive link and device B has no transmit link, there is no need to execute "all TX channels of device B enter low-power, and device B sends four LLCF_EIs after sending service data to all TX channels." Nor is step 5 necessary.

[0471] The following describes an example of a process of implementing a unidirectional link exiting a low power consumption state through a wake-up frame.

[0472] As shown in FIG23 , the unidirectional link exits the LP0-LP2 low power consumption state process, which may include:

[0473] 1. The sending link of device A exits low power consumption (corresponding to TXLKSM entering the recovery state), and after sending N_EIE LLCF_EIEs to device B, it continues to send LLCF_TS2 for link recovery.

[0474] All Tx channels of the transmit link of device A send LLCF_ELE and LLCF_TS2 to the Rx channels of device B.

[0475] The LLCF_ELE format is related to the lane rate. A port should select the LLCF_ELE format corresponding to the lane rate based on the recorded lane rates supported by the transmit and / or receive links.

[0476] Directly send LLCF_TS2 to enter the channel lock phase of link training, reducing the time to exit low power consumption.

[0477] 2. Device B senses that the receiving end is in a non-electrical idle state, and the receiving link of device B exits low power consumption (correspondingly, RXLKSM enters the recovery state).

[0478] The perception that the receiving end is in a non-electrical idle state refers to receiving LLCF_EI.

[0479] The following describes an example of a process of using a wake-up frame to enable a port to exit a low-power state.

[0480] As shown in FIG24 , the process of a port exiting the LP0 to LP2 low power consumption state may include:

[0481] 1. The sending link of device A exits low power consumption (corresponding to TXLKSM entering the recovery state), and after sending N_EIE LLCF_EIEs to device B, it continues to send LLCF_TS2 for link recovery.

[0482] 2. Device B senses that the transmitter is in a non-electrically idle state, and the receiving link of device B exits low power consumption (corresponding to RXLKSM entering the recovery state). After sending N_EIE LLCF_EIEs to device A, it continues to send LLCF_TS2 for link recovery.

[0483] Before sending N_EIE LLCF_EIEs to device B, the sending link of device B exits low power consumption (correspondingly, TXLKSM enters the recovery state).

[0484] Device A senses that the receiving end is in a non-electrical idle state, and the receiving link of device A exits low power consumption (corresponding to RXLKSM entering the recovery state).

[0485] The following describes an example of a process of enabling a port to exit a low power consumption state through a low power consumption request message.

[0486] As shown in Figure 25, the process of a port exiting the LP3 low power state may include:

[0487] 1. Device A sends a low-power consumption request LPRM to device B, requesting that the port exit LP3.

[0488] In LP3, because the primary link cannot perceive LLCF_EIE, device A sends LPRM to device B through the auxiliary link.

[0489] In LPRM, LP_MODE=0b indicates exiting low power consumption, and LP_WAY=1b indicates exiting low power consumption in a bidirectional link.

[0490] 2. After device B receives the LRRM, it feeds back the ACK corresponding to the LPRM to device A, and then the sending link and receiving link of device B exit low power consumption.

[0491] The exit of low power consumption from the transmit link and receive link of device B means that all TX channels and all RX channels of device B exit low power consumption.

[0492] Device B's sending and receiving links enter the Recovery state. Because the link has not yet recovered, Device B sends an ACK corresponding to LPRM through the auxiliary link.

[0493] 3. After device A receives the ACK, the sending link and receiving link of device A exit low power consumption.

[0494] The exit of low power consumption from the transmit link and receive link of device A means that all TX channels and all RX channels of device A exit low power consumption.

[0495] The sending and receiving links of device A enter the Recovery state.

[0496] 4. After device B completes the low-power exit, it continues to send LLCF_TS2 to recover the link, and then needs to send TSM to indicate that the corresponding channel can start resuming training.

[0497] Each TX channel of the transmit link of device B continuously sends LLCF_TS2 to the RX channel of device A for link recovery.

[0498] Because the sending link of device B has not yet entered the HS state, device B sends the TSM through the auxiliary link.

[0499] 5. After device A exits low power consumption, it continues to send LLCF_TS2 to recover the link. It then needs to send TSM to indicate that the corresponding channel can resume training.

[0500] Each TX channel of the transmit link of device A continuously sends LLCF_TS2 to the RX channel of device B for link recovery.

[0501] Because the sending link of device A has not yet entered the HS state, device A sends the TSM through the auxiliary link.

[0502] Furthermore, the process of the port exiting LP3 shown in the above figure can be initiated by device B. The process is similar to the above and will not be repeated here.

[0503] Furthermore, for a purely unidirectional link, a low-power consumption request for the port to exit LP3 can be initiated, which can be initiated by device A or device B.

[0504] For example, for a purely unidirectional link, device A initiates a low-power request for the port to exit LP3. The port of device A only includes a sending link, and the port of device B only includes a receiving link. There is no need to execute "device B's sending link exits low power consumption" in step 2, and there is no need to execute "device A's receiving link exits low power consumption" in step 3, and there is no need to execute step 4.

[0505] The above mainly introduces the solution provided by the embodiment of the present invention from the perspective of the working principle of the device. It can be understood that in order to realize the above functions, the computing device, etc. includes hardware structures and / or software modules corresponding to the execution of each function. It should be easy for those skilled in the art to realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0506] In the embodiments of the present invention, computing devices, etc., can be divided into functional modules according to the above-described method examples. For example, functional modules can be divided according to respective functions, or two or more functions can be integrated into a single processing module. The above-described integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the module division in the embodiments of the present invention is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used.

[0507] In the case of dividing the functional modules according to their respective functions, FIG26 illustrates an apparatus 260 for managing a low-power state provided in an embodiment of the present application. The apparatus 260 for managing a low-power state is used to implement the functions of the first device or device A in the above-mentioned method embodiment. As shown in FIG26 , the apparatus 260 for managing a low-power state may include a sending unit 2601 and a receiving unit 2602. The sending unit 2601 is used to execute the process S601 in Figure 6 or Figure 7, or to execute the process S801 in Figure 8 or Figure 9, or to execute the process S807 in Figure 9, or to execute the process S1003 in Figure 10 or Figure 11, or to execute the process S1009 in Figure 11, or to execute the process S1202 in Figure 12 or Figure 13, or to execute the process S1205 in Figure 13; the receiving unit 2602 is used to execute the process S603 in Figure 6 or Figure 7, or to execute the process S803 in Figure 8 or Figure 9, or to execute the process S812 in Figure 9, or to execute the process S1002 in Figure 10 or Figure 11, or to execute the process S1008 in Figure 11, or to execute the process S1208 in Figure 13. Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0508] Furthermore, as shown in FIG27 , the apparatus 260 for managing a low power consumption state provided in an embodiment of the present application may further include a management unit 2603 for controlling a link of a device to enter or exit a low power consumption state.

[0509] In the case of dividing the functional modules according to their respective functions, FIG28 illustrates another apparatus 280 for managing a low-power state provided in an embodiment of the present application. This apparatus 280 for managing a low-power state is used to implement the functions of the second device or device B in the above method embodiment. As shown in FIG28 , the apparatus 280 for managing a low-power state may include: a receiving unit 2801 and a sending unit 2802. The receiving unit 2801 is used to execute the process S602 in Figure 6 or Figure 7, or the process S802 in Figure 8 or Figure 9, or the process S808 in Figure 9, or the process S1004 in Figure 10 or Figure 11, or the process S1010 in Figure 11, or the process S1203 in Figure 12 or Figure 13; the sending unit 2802 is used to execute the process S602 in Figure 6 or Figure 7, or the process S802 in Figure 8 or Figure 9, or the process S811 in Figure 9, or the process S1001 in Figure 10 or Figure 11, or the process S1007 in Figure 11, or the process S1207 or S1210 in Figure 13. Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0510] Furthermore, as shown in FIG29 , the apparatus 280 for managing a low power consumption state provided in an embodiment of the present application may further include a management unit 2803 for controlling a link of a device to enter or exit a low power consumption state.

[0511] In the case of adopting an integrated unit, as shown in Figure 30, another device 300 for managing a low-power state provided in an embodiment of the present application is used to implement the functions of the first device or the second device in the above-mentioned embodiment. The device 300 for managing a low-power state includes a processing module 3001 and a communication module 3002. The processing module 3001 is used to control and manage the actions of the device 300 for managing a low-power state, and the communication module 3002 is used to communicate with other devices. For example, the processing module 3001 is used to control the communication module 3002 to interact with the device 300 for managing a low-power state and other devices. The device 300 for managing a low-power state may also include a storage module 3003 for storing program code and data of the device 300 for managing a low-power state.

[0512] The processing module 3001 may be the processor 5010 in the physical structure of the computing device 50 shown in FIG5 , and may be a processor or controller. For example, it may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processing module 3001 may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on. The communication module 3002 may be the communication interface 5040 in the physical structure of the computing device 50 shown in FIG5 . The communication module 3002 may be a communication port, or may be a transceiver, a transceiver circuit, or a communication interface. Alternatively, the communication interface may communicate with other devices through the aforementioned transceiver components. The transceiver components may be implemented by antennas and / or radio frequency devices. The storage module 3003 may be the memory 5030 in the physical structure of the computing device 50 shown in FIG5 .

[0513] As mentioned above, the device 260 for managing low power consumption state, the device 280 for managing low power consumption state, and the device 300 for managing low power consumption state provided in the embodiments of the present application can be used to implement the functions of the first device or the second device in the above-mentioned embodiments of the present application. For ease of explanation, only the parts related to the embodiments of the present application are shown. For specific technical details not disclosed, please refer to the embodiments of the present application.

[0514] On the other hand, an embodiment of the present application provides a data transmission system, including the above-mentioned device 260 for managing a low power consumption state and the device 280 for managing a low power consumption state.

[0515] As another form of this embodiment, a computer-readable storage medium is provided, on which instructions are stored. When the instructions are executed, the method for managing the low power consumption state in the above method embodiment is executed.

[0516] As another form of this embodiment, a computer program product containing instructions is provided. When the computer program product is run on a computer, the computer is caused to execute the method for managing a low power consumption state in the above method embodiment.

[0517] As another form of this embodiment, a chip is provided, comprising one or more interface circuits and one or more processors. The interface circuits are configured to receive signals from a memory of an electronic device and transmit the received signals to the processors, the signals comprising computer instructions stored in the memory. When the processors execute the computer instructions, the electronic device performs the operational steps of the method described in the first aspect or any possible implementation.

[0518] The embodiment of the present application further provides a chip system, which includes a processor for implementing the technical method of the embodiment of the present application. In one possible design, the chip system also includes a memory for storing the necessary program instructions and / or data of the embodiment of the present invention. In one possible design, the chip system also includes a memory for the processor to call the application code stored in the memory. The chip system can be composed of one or more chips, or can include chips and other discrete devices, which is not specifically limited in the embodiment of the present application.

[0519] Those skilled in the art will readily appreciate that, in conjunction with the various exemplary units and method steps described in the embodiments disclosed herein, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a hardware-driven manner by computer software depends on the specific application scenario and design constraints of the technical solution.

[0520] The above embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the process or function described in the embodiment of the present application of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that contains one or more available media sets. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be an SSD.

[0521] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for managing a low-power state, characterized in that, Applied to a first device or a chip in the first device, the method includes: Sending a first low-power request message to a second device, the first low-power request message including a first low-power request mode, a first low-power request direction, and a low-power request gear; the first low-power request mode is to enter the low-power state; the first low-power request direction includes unidirectional or bidirectional; Receiving response information corresponding to the first low-power request message from the second device.

2. The method according to claim 1, characterized in that, The link between the first device and the second device includes a main link and an auxiliary link. The main link is a unidirectional transmission link from the first device to the second device, and the auxiliary link is a bidirectional link; The receiving the response information from the second device includes: Receiving the response information from the second device via the auxiliary link.

3. The method according to claim 1 or 2, characterized in that, The method further includes: The transmission link in the main link of the first device enters the low-power state indicated by the low-power request gear.

4. The method according to claim 3, characterized in that, When the first low-power request direction is bidirectional, the method further includes: The receiving link in the main link of the first device enters the low-power state indicated by the low-power request gear.

5. The method according to any one of claims 1-4, characterized in that, The low-power request gear includes one or more of the following: A low-power gear where the receiving end does not support the ability to wake up based on a control frame; Or, A low-power gear where the receiving end supports the ability to wake up based on a control frame.

6. The method according to any one of claims 1-5, characterized in that, The first low-power request message is encapsulated as a logical layer main link management message or a logical layer auxiliary link management message for transmission.

7. The method according to any one of claims 1-6, characterized in that, When the low-power request gear is a low-power gear where the receiving end does not support the ability to wake up based on a control frame, and the link between the first device and the second device includes a main link and an auxiliary link, the method further includes: Sending a second low-power request message to the second device via the auxiliary link, the second low-power request message including a second low-power request mode and a second low-power request direction; the second low-power request mode is to exit the low-power state; the second low-power request direction includes unidirectional or bidirectional; Receiving response information corresponding to the second low-power request message from the second device via the auxiliary link.

8. The method according to claim 7, characterized in that, The method further includes: The transmission link in the main link of the first device exits the low-power state; After exiting the low-power state, continuously send a first control frame for link recovery.

9. The method according to claim 8, characterized in that, The method further includes: The receiving link in the main link of the first device exits the low-power state.

10. The method according to any one of claims 7-9, characterized in that, The first low-power request direction is unidirectional, and the second low-power request direction is unidirectional.

11. The method according to any one of claims 7-9, characterized in that, The first low-power request direction is bidirectional, and the second low-power request direction is unidirectional.

12. The method according to any one of claims 7-9, characterized in that, The first low-power request direction is bidirectional, and the second low-power request direction is bidirectional.

13. The method according to any one of claims 1-6, characterized in that, When the first low-power request direction is bidirectional, and the low-power request gear is a low-power gear where the receiving end does not support the ability to wake up based on a control frame, and the link between the first device and the second device includes a main link and an auxiliary link, the method further includes: On the auxiliary link, receive a third low-power request message from the second device, where the third low-power request message includes a third low-power request mode and a third low-power request direction; the third low-power request mode is to exit the low-power state; the third low-power request direction is two-way; On the auxiliary link, send response information corresponding to the third low-power request message to the second device.

14. The method according to claim 13, wherein The method further includes: The transmission link and the reception link in the primary link of the first device exit the low-power state; After exiting the low-power state, continuously send a first control frame for link recovery.

15. The method according to any one of claims 1-6, wherein The method further includes: The transmission link in the primary link of the first device exits the low-power state; Send one or more second control frames to the second device; the second control frame is used for the sender to wake up through the high-speed link line; different channel rates correspond to different second control frame payloads; Continuously send a first control frame for link recovery.

16. The method according to any one of claims 1-6 or 15, wherein The method further includes: Receive one or more second control frames from the second device, where the second control frame is used for the sender to wake up through the high-speed link line; different channel rates correspond to different second control frame payloads; The reception link in the primary link of the first device exits the low-power state.

17. The method according to claim 15 or 16, wherein Channel rate HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed as: 0x0000_FFFF continuously repeated 4 times; Channel rate HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed as: 0x0000_0000_FFFF_FFFF repeated 4 times; Channel rate HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed as: 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated 4 times; Channel rate HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed as: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

18. The method according to claim 8 or 14 or 15, wherein The first control frame is the logical layer training sequence 2LLCF_TS2, and the LLCF_TS2 is used for transceiver acknowledgment synchronization status.

19. The method according to claim 8 or 14 or 15 or 18, wherein The continuously sending the first control frame for link recovery includes: Continuously send the first control frame for channel locking; After successful channel locking, perform multi-channel alignment.

20. The method according to claim 8 or 14 or 15 or 18 or 19, wherein A specified number of the first control frames are used to indicate successful channel locking.

21. A method for managing a low-power state, wherein Applied to the second device or a chip in the second device; the method includes: Receive a first low-power request message from the first device, where the first low-power request message includes a first low-power request mode, a first low-power request direction, and a low-power request gear; the first low-power request mode is to enter the low-power state; the first low-power request direction includes one-way or two-way; Send response information corresponding to the first low-power request message to the first device.

22. The method according to claim 21, wherein The link between the first device and the second device includes a primary link and an auxiliary link; the primary link is a one-way transmission link from the first device to the second device, and the auxiliary link is a two-way link; Sending the response information corresponding to the first low-power request message to the first device includes: Send the response information through the auxiliary link.

23. The method according to claim 21 or 22, wherein The method further includes: The receiving link in the primary link of the second device enters the low-power state indicated by the low-power request gear.

24. The method according to claim 23, wherein When the first low-power request direction is two-way, the method further includes: The sending link in the primary link of the second device enters the low-power state indicated by the low-power request gear.

25. The method according to any one of claims 21 - 24, wherein The low-power request gear includes one or more of the following: A low-power gear where the receiving end does not support the ability to wake up based on a control frame; Or, A low-power gear where the receiving end supports the ability to wake up based on a control frame.

26. The method according to any one of claims 21 - 25, wherein The first low-power request message is encapsulated as a logical layer primary link management message or a logical layer auxiliary link management message for transmission.

27. The method according to any one of claims 21 - 26, wherein When the low-power request gear is a low-power state where the receiving end does not support the ability to wake up based on a control frame, and the link between the first device and the second device includes a primary link and an auxiliary link, the method further includes: Receive a second low-power request message from the first device on the auxiliary link, where the second low-power request message includes a second low-power request mode and a second low-power request direction; the second low-power request mode is to exit the low-power state; the second low-power request direction includes one-way or two-way; Send response information corresponding to the second low-power request message to the first device on the auxiliary link.

28. The method according to claim 27, wherein The method further includes: The receiving link in the primary link of the second device exits the low-power state.

29. The method according to claim 28, wherein The method further includes: The sending link in the primary link of the second device exits the low-power state; After exiting the low-power state, continuously send a first control frame for link recovery.

30. The method according to any one of claims 27 - 29, wherein The first low-power request direction is one-way, and the second low-power request direction is one-way.

31. The method according to any one of claims 27 - 29, wherein The first low-power request direction is two-way, and the second low-power request direction is one-way.

32. The method according to any one of claims 27 - 29, wherein The first low-power request direction is two-way, and the second low-power request direction is two-way.

33. The method according to any one of claims 21 - 26, wherein When the first low-power request direction is two-way, the low-power request gear is a low-power state where the receiving end does not support the ability to wake up based on a control frame, and the link between the first device and the second device includes a primary link and an auxiliary link, the method further includes: On the auxiliary link, a third low-power request message is sent to the first device. The third low-power request message includes a third low-power request mode and a third low-power request direction. The third low-power request mode is to exit the low-power state, and the third low-power request direction is two-way. On the auxiliary link, response information corresponding to the third low-power request message from the first device is received.

34. The method according to claim 33, wherein The method further includes: The transmit link and the receive link in the primary link of the second device exit the low-power state. After exiting the low-power state, a first control frame is continuously sent for link recovery.

35. The method according to any one of claims 21 - 26, wherein The method further includes: One or more second control frames from the first device are received. The second control frames are used for the sender to wake up through the high-speed link line. Different channel rates correspond to different second control frame payloads. The receive link in the primary link of the second device exits the low-power state.

36. The method according to any one of claims 21 - 26 or 35, characterized in that, The method further includes: The transmit link in the primary link of the second device exits the low-power state. One or more of the second control frames are sent to the first device. A first control frame is continuously sent for link recovery.

37. The method according to claim 35 or 36, characterized in that, For channel rate HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed as: 0x0000_FFFF repeated continuously 4 times. For channel rate HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed as: 0x0000_0000_FFFF_FFFF repeated 4 times. For channel rate HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed as: 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated 4 times. For channel rate HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed as: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

38. The method according to claim 29 or 34 or 36, characterized in that, The first control frame is the logical layer training sequence 2LLCF_TS2, and the LLCF_TS2 is used for transceiver confirmation synchronization status.

39. The method according to claim 29 or 34 or 36 or 38, characterized in that, The continuously sending the first control frame for link recovery includes: Continuously sending the first control frame for channel locking. After successful channel locking, multi-channel alignment is performed.

40. The method according to claim 29 or 34 or 36 or 38 or 39, characterized in that, A specified number of the first control frames are used to indicate successful channel locking.

41. An apparatus for managing a low - power state, characterized in that, Applied to the first device or a chip in the first device, the apparatus includes: A sending unit, configured to send a first low-power request message to a second device. The first low-power request message includes a first low-power request mode, a first low-power request direction, and a low-power request gear. The first low-power request mode is to enter the low-power state. The first low-power request direction includes one-way or two-way. A receiving unit, configured to receive response information corresponding to the first low-power request message from the second device.

42. The apparatus according to claim 41, characterized in that, The link between the first device and the second device includes a primary link and an auxiliary link. The primary link is a unidirectional transmission link from the first device to the second device, and the auxiliary link is a bidirectional link. Specifically, the receiving unit is configured to: Receive the response information from the second device via the auxiliary link.

43. The apparatus according to claim 41 or 42, characterized in that, The apparatus further includes a management unit, configured to: Control the transmission link in the primary link of the first device to enter the low-power state indicated by the low-power request gear.

44. The apparatus according to claim 43, characterized in that, The first low-power request direction is bidirectional. The management unit is further configured to: Control the receiving link in the primary link of the first device to enter the low-power state indicated by the low-power request gear.

45. The apparatus according to any one of claims 41 - 44, characterized in that, The low-power request gear includes one or more of the following: A low-power gear where the receiving end does not support the ability to wake up based on a control frame; Or, A low-power gear where the receiving end supports the ability to wake up based on a control frame.

46. The device according to any one of claims 41 - 45, characterized in that, The first low-power request message is encapsulated as a logical layer primary link management message or a logical layer auxiliary link management message for transmission.

47. The device according to any one of claims 41 - 46, characterized in that, The low-power request gear is a low-power gear where the receiving end does not support the ability to wake up based on a control frame. The link between the first device and the second device includes a primary link and an auxiliary link. The sending unit is further configured to: send a second low-power request message to the second device via the auxiliary link. The second low-power request message includes a second low-power request mode and a second low-power request direction. The second low-power request mode is to exit the low power state. The second low-power request direction includes unidirectional or bidirectional. The receiving unit is further configured to: receive response information corresponding to the second low-power request message from the second device via the auxiliary link.

48. The device according to claim 47, characterized in that, The apparatus further includes a management unit, configured to: control the transmission link in the primary link of the first device to exit the low-power state. The sending unit is further configured to: continuously send a first control frame for link recovery after exiting the low-power state.

49. The device according to claim 48, characterized in that, The management unit is further configured to: Control the receiving link in the primary link of the first device to exit the low-power state.

50. The device according to any one of claims 47 - 49, characterized in that, The first low-power request direction is unidirectional, and the second low-power request direction is unidirectional.

51. The device according to any one of claims 47 - 49, characterized in that, The first low-power request direction is bidirectional, and the second low-power request direction is unidirectional.

52. The device according to any one of claims 47 - 49, characterized in that, The first low-power request direction is bidirectional, and the second low-power request direction is bidirectional.

53. The device according to any one of claims 41 - 46, characterized in that, The first low-power request direction is bidirectional. The low-power request gear is a low-power gear where the receiving end does not support the ability to wake up based on a control frame. The link between the first device and the second device includes a primary link and an auxiliary link. The receiving unit is further configured to: receive a third low-power request message from the second device via the auxiliary link. The third low-power request message includes a third low-power request mode and a third low-power request direction. The third low-power request mode is to exit the low power state. The third low-power request direction is bidirectional. The sending unit is further configured to: in the auxiliary link, send response information corresponding to the third low-power request message to the second device.

54. The device according to claim 53, characterized in that, The device further includes a management unit configured to: control the sending link and the receiving link in the primary link of the first device to exit the low-power state; The sending unit is further configured to: after exiting the low-power state, continuously send a first control frame for link recovery.

55. The device according to any one of claims 41 - 46, characterized in that, The device further includes a management unit configured to: the sending link in the primary link of the first device exits the low-power state; The sending unit is further configured to: send one or more second control frames to the second device; the second control frame is used for the sender to wake up through the high-speed link line; different channel rates correspond to different second control frame payloads; The sending unit is further configured to: continuously send a first control frame for link recovery.

56. The device according to any one of claims 41 - 46 or 55, characterized in that, The receiving unit is further configured to: receive one or more second control frames from the second device, the second control frame is used for the sender to wake up through the high-speed link line; different channel rates correspond to different second control frame payloads; The device further includes a management unit configured to control the receiving link in the primary link of the first device to exit the low-power state.

57. The device according to claim 55 or 56, characterized in that, Channel rate HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed as: 0x0000_FFFF continuously repeated 4 times; Channel rate HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed as: 0x0000_0000_FFFF_FFFF repeated 4 times; Channel rate HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed as: 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated 4 times; Channel rate HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed as: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

58. The device according to claim 48 or 54 or 55, characterized in that, The first control frame is a logical layer training sequence 2LLCF_TS2, and the LLCF_TS2 is used for transceiver confirmation synchronization status.

59. The device according to claim 48 or 54 or 55 or 58, characterized in that, The sending unit is specifically configured to: Continuously send a first control frame for channel locking; After successful channel locking, perform multi-channel alignment.

60. The device according to claim 48 or 54 or 55 or 58 or 59, characterized in that, A specified number of the first control frames are used to indicate successful channel locking.

61. A device for managing a low-power state, characterized in that, Applied to the second device or a chip in the second device; the device includes: A receiving unit configured to receive a first low-power request message from the first device, the first low-power request message includes a first low-power request mode, a first low-power request direction, and a low-power request gear; the first low-power request mode is to enter the low-power state; the first low-power request direction includes unidirectional or bidirectional; A sending unit, configured to send response information corresponding to the first low-power request message to the first device.

62. The device according to claim 61, characterized in that, The link between the first device and the second device includes a primary link and an auxiliary link; the primary link is a unidirectional transmission link from the first device to the second device, and the auxiliary link is a bidirectional link; specifically, the sending unit is configured to: Send the response information through the auxiliary link.

63. The device according to claim 61 or 62, characterized in that, The apparatus further includes a management unit, configured to: Control the receiving link in the primary link of the second device to enter the low-power state indicated by the low-power request gear.

64. The device according to claim 63, characterized in that, The first low-power request direction is bidirectional, and the management unit is further configured to: Control the sending link in the primary link of the second device to enter the low-power state indicated by the low-power request gear.

65. The device according to any one of claims 61-64, characterized in that, The low-power request gear includes one or more of the following: A low-power gear in which the receiving end does not support the ability to wake up based on a control frame; Or, A low-power gear in which the receiving end supports the ability to wake up based on a control frame.

66. The device according to any one of claims 61-65, characterized in that, The first low-power request message is encapsulated as a logical layer primary link management message or a logical layer auxiliary link management message for transmission.

67. The device according to any one of claims 61-66, characterized in that, The low-power request gear is a low-power state in which the receiving end does not support the ability to wake up based on a control frame, and the link between the first device and the second device includes a primary link and an auxiliary link; The receiving unit is further configured to: receive, on the auxiliary link, a second low-power request message from the first device, where the second low-power request message includes a second low-power request mode and a second low-power request direction; the second low-power request mode is to exit the low-power state; The second low-power request direction includes unidirectional or bidirectional; The sending unit is further configured to: send, on the auxiliary link, response information corresponding to the second low-power request message to the first device.

68. The device according to claim 67, wherein The apparatus further includes a management unit, configured to: Control the receiving link in the primary link of the second device to exit the low-power state.

69. The device according to claim 68, wherein The management unit is further configured to: cause the sending link in the primary link of the second device to exit the low-power state; The sending unit is further configured to: continuously send a first control frame for link recovery after exiting the low-power state.

70. The device according to any one of claims 67-69, wherein The first low-power request direction is unidirectional, and the second low-power request direction is unidirectional.

71. The device according to any one of claims 67-69, wherein The first low-power request direction is bidirectional, and the second low-power request direction is unidirectional.

72. The device according to any one of claims 67-69, wherein The first low-power request direction is bidirectional, and the second low-power request direction is bidirectional.

73. The device according to any one of claims 61-66, wherein The first low-power request direction is bidirectional, the low-power request gear is a low-power state in which the receiving end does not support the ability to wake up based on a control frame, and the link between the first device and the second device includes a primary link and an auxiliary link; The sending unit is further configured to: send, on the auxiliary link, a third low-power request message to the first device, where the third low-power request message includes a third low-power request mode and a third low-power request direction; the third low-power request mode is to exit the low-power state; The third low-power request direction is bidirectional; The receiving unit is further configured to: receive, on the secondary link, response information corresponding to the third low-power request message from the first device.

74. The device according to claim 73, wherein The apparatus further includes a management unit configured to: exit the low-power state for the sending link and the receiving link in the primary link of the second device; The sending unit is further configured to: continuously send a first control frame for link recovery after exiting the low-power state.

75. The device according to any one of claims 61-66, wherein The receiving unit is further configured to: receive one or more second control frames from the first device, where the second control frames are used for the sender to wake up through a high-speed link line; different channel rates correspond to different second control frame payloads; The apparatus further includes a management unit configured to: control the receiving link in the primary link of the second device to exit the low-power state.

76. The device according to any one of claims 61-66 or 75, wherein The apparatus further includes a management unit configured to: control the sending link in the primary link of the second device to exit the low-power state; The sending unit is further configured to: send one or more of the second control frames to the first device; The sending unit is further configured to: continuously send a first control frame for link recovery.

77. The device according to claim 75 or 76, wherein For channel rate HS1 (2 Gigabits Per Second (Gbps) / 4 Gbps), the payload length of the second control frame is 16 bytes, and the payload is fixed as: 0x0000_FFFF repeated continuously 4 times; For channel rate HS2 (6 Gbps / 8 Gbps), the payload length of the second control frame is 32 bytes, and the payload is fixed as: 0x0000_0000_FFFF_FFFF repeated 4 times; For channel rate HS3 (10 Gbps / 12 Gbps / 16 Gbps), the payload length of the second control frame is 64 bytes, and the payload is fixed as: 0x0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF repeated 4 times; For channel rate HS4 (20 Gbps / 24 Gbps), the payload length of the second control frame is 96 bytes, and the payload is fixed as: 0x0000_0000_0000_0000_0000_0000_FFFF_FFFF_FFFF_FFFF_FFFF_FFFF repeated 4 times.

78. The device according to claim 69 or 74 or 76, wherein The first control frame is a logical layer training sequence 2LLCF_TS2, and the LLCF_TS2 is used for transceiver confirmation synchronization status.

79. The device according to claim 69 or 74 or 76 or 78, whereinThe sending unit is specifically configured to continuously send a first control frame for channel locking; perform multi-channel alignment after successful channel locking.

80. The device according to claim 69 or 74 or 76 or 78 or 79, characterized in that, A specified number of the first control frames are used to indicate successful channel locking.

81. A computing device, characterized in that, The computing device includes a memory and at least one processor, where the memory is used to store a set of computer instructions; when the processor executes the set of computer instructions, it performs the operation steps of the method according to any one of claims 1-40 above.

82. A chip, characterized in that, Comprising one or more interface circuits and one or more processors; the interface circuits are configured to receive signals from a memory of an electronic device and send the signals to the processors, the signals including computer instructions stored in the memory; when the processors execute the computer instructions, the electronic device is caused to perform the operations of the method according to any one of claims 1-40.

83. A data transmission system, characterized in that, The data transmission system includes a data sending device and a data receiving device, the data sending device includes a device for managing a low-power state according to any one of claims 41-60, and the data receiving device includes a device for managing a low-power state according to any one of claims 61-80.

84. A computer-readable storage medium, characterized in that, Comprising: Computer software instructions; when the computer software instructions are run on a computer, the computer is caused to perform the operation steps of the method according to any one of claims 1-40 above.

85. A computer program product, characterized in that, The computer program product includes a software program, when the software program is executed by a computer or a processor, the computer or the processor is caused to perform the operation steps of the method according to any one of claims 1-40 above.

Images