Remote wake-up processing method, device and system and storage medium

By monitoring the wake-up signal using a USB hub and physical layer transceiver while the target device is in sleep mode, the problem of accidental wake-up due to power failure of USB peripherals is solved, and accurate wake-up via remote wake-up signal is achieved.

CN121387384APending Publication Date: 2026-01-23PHYTIUM TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202511517026.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-10-22
Publication Date
2026-01-23

AI Technical Summary

Technical Problem

In remote wake-up scenarios, the power failure of a USB peripheral may accidentally trigger a wake-up signal, leading to the problem of the device being woken up unintentionally.

Method used

After the target device enters sleep mode, the wake-up signal of the USB peripheral is monitored through the USB hub and physical layer transceiver to ensure that the wake-up signal is acquired and processed only after the board is powered down, so as to avoid false detection.

Benefits of technology

This effectively avoids false wake-up signals caused by power loss of USB peripherals, ensuring the accuracy and reliability of remote wake-up signals.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121387384A_ABST
    Figure CN121387384A_ABST
Patent Text Reader

Abstract

The invention provides a remote wakeup processing method, device and system and a storage medium, the method is applied to a main processor in a target device, the target device further comprises a USB controller, a USB bus, a USB physical layer transceiver and a USB hub, the main processor is connected with the USB controller, the USB physical layer transceiver is connected with the USB controller, and the USB physical layer transceiver is connected with the USB hub. The USB controller is connected with at least one USB peripheral sequentially through a USB physical layer transceiver and a USB concentrator by adopting a USB bus, and the method comprises the following steps: responding to sleep operation for target equipment, controlling each USB peripheral to be in a suspended state, switching the USB controller to be in a sleep state, executing board-level power-off operation in the sleep state, and switching the USB peripheral to be in a power-off state after the board-level power-off operation is executed in the sleep state. And acquiring a wake-up signal for the target equipment, which is transmitted by any USB peripheral through the USB concentrator and the USB physical layer transceiver, so as to wake up the target equipment. It is ensured that remote wake-up is achieved based on the wake-up signal after the board level is powered off, and the problem of false alarm of the remote wake-up signal is solved.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, in particular to a remote wake-up processing method, device, system and storage medium. BACKGROUND

[0002] In a remote wake-up scenario, a USB controller usually wakes up a USB peripheral, or the USB peripheral wakes up a device, for example, when the device is in a sleep operation, the target device can be woken up by a USB keyboard. To use the remote wake-up function, the USB peripheral needs to support the remote wake-up function, and in the setting of the configuration descriptor, the USB peripheral reports the remote wake-up capability to the USB controller.

[0003] In the related art, when the USB controller has been set to a sleep operation (STOP) state, from the perspective of saving power, the USB peripheral that does not support the remote wake-up function is powered off first, but at this time, the power-off action of the USB peripheral may trigger the green HUB to report a wake-up signal, thereby mistakenly waking up the device. SUMMARY

[0004] Therefore, the embodiments of the present application provide a remote wake-up processing method, device, system and storage medium to solve the problem of false reporting of a remote wake-up signal.

[0005] In a first aspect, the embodiments of the present application provide a main processor applied to a target device, the target device further comprising a USB controller, a USB bus, a USB physical layer transceiver and a USB hub, wherein the main processor is connected to the USB controller, the USB controller is connected to at least one USB peripheral through the USB bus, the USB physical layer transceiver and the USB hub in sequence, and the method comprises: In response to a sleep operation of the target device, controlling each USB peripheral to be in a suspended state, and switching the USB controller to a sleep state; In the sleep state, after performing a board-level power-off operation, acquiring a wake-up signal for the target device transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver to wake up the target device.

[0006] In an optional embodiment, the acquiring, in the sleep state, after performing a board-level power-off operation, of a wake-up signal for the target device transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver comprises: In the sleep state, performing a board-level power-off operation, and controlling a wake-up detection unit to start after the board-level power-off; The wakeup detection unit monitors the wakeup signal transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver to the target device.

[0007] In an optional embodiment, after the board-level power-down operation is performed in the sleep state, the wakeup signal transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver to the target device is acquired, including: In the sleep state, the wakeup detection unit is started, and the signal reporting state of the wakeup detection unit is set to the disabled state; After the board-level power-down operation is performed, the signal reporting state of the wakeup detection unit is switched to the enabled state; The wakeup detection unit monitors the wakeup signal transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver to the target device.

[0008] In an optional embodiment, in response to the sleep operation of the target device, the USB peripherals are controlled to be in the suspended state, including: In response to the sleep operation, the USB controller is controlled to stop sending a start-of-frame packet to the USB peripherals, so that the USB bus is in the idle state; In response to the USB bus being in the idle state, the USB peripherals are controlled to be in the suspended state.

[0009] In an optional embodiment, in response to the sleep operation, the USB controller is controlled to stop sending a start-of-frame packet to the USB peripherals, so that the USB bus is in the idle state, including: In response to the sleep operation, the USB controller is controlled to complete the execution of the ongoing request, and the USB controller is controlled to stop sending a start-of-frame packet to the USB peripherals, so that the USB bus is in the idle state.

[0010] In an optional embodiment, in the sleep state, after the board-level power-down operation is performed by the main processor, the wakeup signal transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver to the target device is acquired, including: In the sleep state, after the board-level power-down operation is performed, the wakeup signal transmitted by a target USB peripheral of the at least one USB peripheral through the USB hub and the USB physical layer transceiver to the target device is acquired, the target USB peripheral being a USB peripheral supporting remote wakeup.

[0011] In an optional implementation, the sleep operation for the target device comprises the sleep operation input through the user operation interface.

[0012] In a second aspect, the embodiments of the present application further provide an electronic device, comprising: a main processor, a USB controller, a USB physical layer transceiver and a USB hub, wherein the main processor is connected with the USB controller, the USB controller is connected with at least one USB peripheral device through the USB hub and the USB physical layer transceiver in sequence by using a USB bus. The main processor is configured to execute the method in any one of the first aspect.

[0013] In a third aspect, the embodiments of the present application further provide a remote wake-up processing system, comprising: at least one USB peripheral device and the electronic device in the second aspect.

[0014] In a fourth aspect, the embodiments of the present application further provide a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is configured to execute the method in any one of the first aspect when executed by a processor.

[0015] The present application provides a remote wake-up processing method, device, system and storage medium, wherein the method is applied to a main processor, the main processor is connected with a USB controller respectively, the USB controller is connected with at least one USB peripheral device through a USB hub and a USB physical layer transceiver in sequence by using a USB bus, and the method comprises the following steps: in response to a sleep operation for a target device, controlling each USB peripheral device to be in a suspended state, and switching the USB controller to a sleep state, in the sleep state, after performing a board-level power-down operation, acquiring a wake-up signal for the target device transmitted by any USB peripheral device through the USB hub and the USB physical layer transceiver, so as to wake up the target device. Thus, it is ensured that the remote wake-up is realized based on the wake-up signal after the board-level power-down, and the problem of false alarm of the remote wake-up signal is solved. BRIEF DESCRIPTION OF DRAWINGS

[0016] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some of the embodiments of the present application, and therefore should not be considered as a limitation to the scope. For those skilled in the art, other related drawings can also be obtained without creative labor.

[0017] Figure 1 A schematic diagram for data packet transmission of a USB system; Figure 2 A schematic diagram for an existing remote wake-up process; Figure 3Flowchart of remote wake-up processing method provided by an embodiment of the present application Figure 1 ; Figure 4 Flowchart of remote wake-up processing method provided by an embodiment of the present application Figure 2 ; Figure 5 Flowchart of remote wake-up processing method provided by an embodiment of the present application Figure 3 ; Figure 6 Flowchart of remote wake-up processing method provided by an embodiment of the present application Figure 4 ; Figure 7 Specific remote wake-up processing architecture provided by an embodiment of the present application Figure 8 Another remote wake-up processing architecture provided by an embodiment of the present application Figure 9 Structure of electronic device provided by an embodiment of the present application Figure 10 Structure of remote wake-up processing device provided by an embodiment of the present application DETAILED DESCRIPTION

[0018] In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the accompanying drawings can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of the present application.

[0019] First, the related concepts involved in the present application are described: SE0 state: when both D+ and D- data lines are driven to low level, it is called SE0 state. Among them, D+ and D- data lines are the channels for data transmission between host and peripheral.

[0020] J state: for full-speed devices, when D+ data line is high level and D- data line is low level, it is called J state. This is an idle state or one of the states in data transmission.

[0021] Suspend: a power saving mode, if the device does not receive any bus activity for more than 3ms, it must enter suspend state.

[0022] Reset: Forces the device to return to a known initial state.

[0023] In a USB system, under normal conditions, the USB controller periodically sends Start of Frame (SOF) packets to the USB peripheral via the root hub. If the USB peripheral is a full-speed device, an SOF packet is sent every 1 millisecond; if it's a high-speed device, an SOF packet is sent every 125 microseconds. According to the USB protocol, if the USB bus remains idle for more than 3 milliseconds, the USB peripheral treats this as a suspend signal, requiring the device to enter a suspend state within 10 milliseconds. The USB bus being in an idle state means that the USB controller stops sending SOF packets, or that the USB controller does not initiate a request to the USB peripheral. In the suspend state, the USB peripheral needs to provide voltage to the pull-up resistors of D+ / D- to maintain the idle state. For high-speed USB 2.0 devices, there are some additional requirements: 1. After receiving the hang-up signal, the high-speed device should switch to full-speed mode within 0.125 milliseconds. That is, remove the terminating resistor used for high-speed communication and reconnect the 1.5K pull-up resistor on the D+ data line to make the D+ data line high.

[0024] 2. The high-speed device detects the status of the data line within the following 100~875 microseconds. If the status is a full-speed J signal (D+=1, D-=0, that is, the D+ data line is high and the D- data line is low), it means that the USB controller has issued a suspend signal. If the status is an SE0 signal (D+=0, D-=0), it means that the USB controller has driven the data line D+ from high level to 0, which is a reset signal (the reset signal will last for at least 10 milliseconds).

[0025] Figure 1 This is a diagram illustrating data packet transmission in a USB system, such as... Figure 1 As shown, the USB controller stops sending SOF at point a, and the USB peripheral is in SE0 state. Point b is the 3-millisecond time point. In the following 125 microseconds, the device removes the termination resistor and suspends a 1.5K pull-up resistor. If the USB controller sends a Suspend signal at this time, the USB controller will not drive the D+ data line, causing the D+ data line to be pulled high, forming a full-speed J signal.

[0026] Within 100-875 microseconds after point c, the USB peripheral will check the USB controller behavior again. If it is still a Suspend signal, the USB peripheral will enter a low-power suspend state.

[0027] If the USB peripheral device suspends the 1.5K pull-up resistor at point C, due to the driving effect of the USB controller on the D+ line, the D+ line cannot be pulled high and remains in the SE0 state. The detection of the USB peripheral device within 100-875 microseconds after point C still finds the SE0 state. After 10 milliseconds, it can be judged that it is a reset signal, and the device reset operation is performed.

[0028] When the device is in the suspended state, any activity (non-idle signal) on the USB bus can wake up / resume the device, thereby exiting the low-power mode. Similarly, the USB peripheral device can also wake up the host, such as using a USB keyboard to wake up the host when the computer is in standby. This function is called remote wake-up.

[0029] Because the device handles full-speed signals when it is suspended, when the USB controller needs to exit the suspended state of the USB peripheral device, it needs to first send a full-speed K signal with a duration of more than 20 ms. The USB peripheral device wakes up within 1.3 microseconds after the end of the K signal, and the USB controller needs to send a SOF packet within 3 milliseconds to maintain the normal high-speed signal mode. Otherwise, the USB peripheral device will enter the suspended state again.

[0030] Figure 2 The existing remote wake-up process is shown in the schematic diagram as shown in Figure 2 When the sleep operation starts, the USB peripheral device enters the suspended state, and the USB controller changes from the working (RUN) state to the sleep operation (STOP) state. At this time, the wake-up detection unit starts to work, and the power management unit performs the board-level power-down operation, thereby completing the entire sleep process. However, when the USB controller is set to the STOP state, from the perspective of saving power, the USB peripheral devices that do not support remote wake-up function will be powered off first when the board is powered down, such as the camera being powered off first. At this time, the power-off action of the camera will trigger the USB hub (green HUB) and the USB physical layer transceiver (USB-PHY) to report a wake-up signal, thereby causing the wake-up detection unit to mistakenly detect a remote wake-up signal and mistakenly wake up the target device.

[0031] The USB controller is used to handle the high-level part of the USB protocol, such as managing data transmission requests, handling endpoints, interacting with the system bus, etc. The USB physical layer transceiver is used to handle the physical signals at the bottom of the USB protocol, such as converting the parallel data of the USB controller into a serial data stream and sending it out, and converting the received serial data stream into parallel data and sending it to the USB controller. The USB hub is used to expand the number of USB-A or USB-C interfaces, and it complies with the hub specification of the USB protocol. There is an upstream port connected to the electronic device, and multiple downstream ports for users to connect USB peripheral devices.

[0032] Referring toFigure 2 P0 between the USB controller and the USB physical layer transceiver indicates that the USB controller and the USB physical layer transceiver belong to the same power domain, i.e., the normal voltage core domain P0, which is controlled by the power management unit.

[0033] Based on this, after the board-level power-off operation is performed when the USB controller is in the sleep state, the wake-up signal transmitted by any USB peripheral device through the USB hub and the USB physical layer transceiver for the target device is acquired to wake up the target device. Thus, it is ensured that the remote wake-up is realized based on the wake-up signal after the board-level power-off, and the problem of false reporting of the remote wake-up signal is solved. After the board-level power-off is completed, the USB peripheral device is in a power-off state, so the wake-up signal that is falsely detected due to the power-off action of the USB peripheral device will not be used as a real wake-up signal to wake up the target device.

[0034] Figure 3 Flowchart of the remote wake-up processing method provided by the embodiment Figure 1 The execution subject of the embodiment can be a main processor in the target device, which can be a central processing unit (CPU), a microcontroller unit (MCU), etc.

[0035] The target device further includes a USB controller, a USB bus, a USB physical layer transceiver (USB-PHY), and a USB hub (e.g., a green link HUB). The main processor is connected to the USB controller, and the USB controller is connected to at least one USB peripheral device through the USB hub, the USB physical layer transceiver, and the USB bus in sequence.

[0036] The at least one USB peripheral device can include a camera, a keyboard, a mouse, a USB flash disk, etc.

[0037] As shown in Figure 3 The method can include the following steps. S101, in response to a sleep operation for a target device, controlling each USB peripheral device to be in a suspended state, and switching a USB controller to a sleep state.

[0038] In an optional embodiment, the sleep operation for the target device includes a sleep operation input through a user operation interface.

[0039] The target device provides a user operation interface, such as a main interface of a computer, etc. The sleep operation input through the user operation interface can be a selection operation on a sleep operation control, which can be a click operation, a long press operation, a double-click operation, etc.

[0040] Alternatively, in some embodiments, the sleep operation for the target device can also be a sleep operation input through a voice.

[0041] Of course, the above examples are only exemplary implementations of the sleep operation for the target device, and the specific implementation of the sleep operation is not particularly limited in the present embodiment.

[0042] In response to the sleep operation for the target device, the USB peripherals are controlled to be in a suspended state, in which the USB peripherals are in a power saving mode, and the USB controller is switched to a sleep state.

[0043] S102, in the sleep state, after performing the board-level power-down operation, obtaining a wake-up signal for the target device transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver to wake up the target device.

[0044] In the sleep state, the board-level power-down operation is performed, which means that the main system of the target device and its related core circuit are turned off to enter a low-power state (such as shutdown, sleep operation, deep sleep, etc.).

[0045] It should be noted that the board-level power-down operation can be performed based on a preset priority order, for example, USB peripherals that do not support remote wake-up function are preferentially powered down, for example, since the camera is identified as not supporting remote wake-up function, the power supply to the camera is preferentially cut off, and then the power supply to the core components is cut off, and the board-level power-down is formally completed.

[0046] Among them, the wake-up signal for the target device can be a wake-up signal triggered by any USB peripheral, for example, a key operation input through a keyboard triggers the generation of a wake-up signal for the target device, or a moving operation or a clicking operation input through a mouse triggers the generation of a wake-up signal for the target device.

[0047] When performing the board-level power-down, the power-down action for the USB peripheral will generate a false detection wake-up signal, but the false detection wake-up signal will not be used as a wake-up signal for waking up the target device, but after performing the board-level power-down, the wake-up signal for the target device will be transmitted to the main processor through the USB hub and the USB physical layer transceiver in sequence, so that the main processor wakes up the target device based on the wake-up signal.

[0048] In some embodiments, the power management unit can be implemented by a separate hardware entity, the main processor can control the power management unit to perform the board-level power-down operation, the main processor receives the wake-up signal for the target device through the power management unit, and controls the power management unit to perform the board-level power-up operation to wake up the target device.

[0049] In some embodiments, the power management unit can control the power supply domain P0 to supply power to the USB controller and the USB physical layer transceiver at the same time.

[0050] In some embodiments, the power management unit can also be integrated in the main processor as a functional module of the main processor.

[0051] In an optional implementation, after the board-level power-down operation is performed in the sleep state, the step S102 of acquiring the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver can include: After the board-level power-down operation is performed in the sleep state, the step S102 of acquiring the wake-up signal for the target device transmitted by the target USB peripheral through the USB hub and the USB physical layer transceiver can include:

[0052] The at least one USB peripheral includes two types, one type is a USB peripheral supporting remote wake-up, and the other type is a USB peripheral not supporting remote wake-up. The wake-up signal for the USB controller is input through the target USB peripheral and is transmitted to the main processor through the USB hub and the USB physical layer transceiver in sequence, so that the main processor wakes up the target device based on the wake-up signal.

[0053] In the remote wake-up processing method provided in the embodiment, the wake-up signal that is falsely detected when the board-level power-down operation is performed is ignored, and the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver is acquired only after the board-level power-down operation is performed. The wake-up signal is the real wake-up signal for waking up the target device. The detection of the wake-up signal is more reliable, and the false wake-up problem in some scenarios is repaired.

[0054] Figure 4 Flowchart of the remote wake-up processing method provided in the embodiment Figure 2 As shown in Figure 4 In an optional implementation, after the board-level power-down operation is performed in the sleep state, the step S102 of acquiring the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver can include: S201. In sleep mode, perform board-level power-down operation, and control the wake-up detection unit to start after board-level power-down.

[0055] S202. Monitor the wake-up signal for the target device transmitted by any USB peripheral through the USB hub or USB physical layer transceiver via the wake-up detection unit.

[0056] In sleep mode, a board-level power-down operation is performed, and the wake-up detection unit is started after the board-level power-down. The wake-up detection unit in the started state is used to collect wake-up signals. When a wake-up signal for the target device is input through any USB peripheral, the wake-up detection unit monitors the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, so that the main processor wakes up the target device based on the wake-up signal.

[0057] In some embodiments, the wake-up detection unit can be implemented by a separate hardware entity, or it can be integrated into the main processor as a functional module of the main processor.

[0058] In the remote wake-up processing method provided in this embodiment, the wake-up detection unit is started after the board is powered down. By delaying the start time of the wake-up detection unit, it is made to start working only after the board is powered down. Therefore, when a false wake-up signal is generated when the board is powered down, since the wake-up detection unit has not yet started, there will be no situation where the target device is falsely woken up based on the false wake-up signal, thus solving the problem of false alarm of remote wake-up signal.

[0059] Figure 5 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 3 ,like Figure 5 As shown, in an optional embodiment, step S102 above, after performing a board-level power-down operation in sleep mode, acquiring a wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, may include: S301. In sleep mode, start the wake-up detection unit and set the signal reporting status of the wake-up detection unit to disabled.

[0060] The signal reporting status of the wake-up detection unit is used to indicate whether the wake-up detection unit reports a wake-up signal for the target device to the main processor.

[0061] In sleep mode, the wake-up detection unit is activated and its signal reporting status is set to disabled. The disabled status is used to instruct the wake-up detection unit to prohibit reporting wake-up signals for the target device to the main processor. In other words, the signals collected by the wake-up detection unit from the start-up state to the board-level power-down completion stage will be ignored, discarded, and not reported to the main processor, and thus the target device will not be woken up based on the signal.

[0062] S302. After performing the board-level power-down operation, switch the signal reporting status of the wake-up detection unit to the start status.

[0063] After performing the board-level power-down operation, the signal reporting status of the wake-up detection unit is switched to the start status. The start status indicates that the wake-up detection unit is allowed to report the wake-up signal for the target device to the main processor. In other words, the wake-up signal collected by the wake-up detection unit in the start status can be used to wake up the target device.

[0064] S303: Monitor the wake-up signal for the target device transmitted by any USB peripheral through the USB hub or USB physical layer transceiver via the wake-up detection unit.

[0065] When the wake-up detection unit is in the start state, a wake-up signal for the target device is input through any USB peripheral. The wake-up detection unit monitors the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, so that the main processor wakes up the target device based on the wake-up signal.

[0066] In the remote wake-up processing method provided in this embodiment, the working time of the wake-up detection unit remains unchanged, but the wake-up signal for the target device is reported to the main processor only after the board is powered down. That is to say, for the wake-up signal that is falsely detected when the board is powered down, the wake-up detection unit can collect it but will not report it to the main processor. By ignoring the falsely detected wake-up signal, there will be no situation where the target device is falsely woken up based on the falsely detected wake-up signal, thus solving the problem of false alarm of remote wake-up signal.

[0067] Figure 6 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 4 ,like Figure 6 As shown, in an optional implementation, step S101 above, which controls each USB peripheral to be in a suspended state in response to a sleep operation for the target device, may include: S401, in response to sleep operation, controls the USB controller to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state.

[0068] S402, in response to the USB bus being in an idle state, controlling each USB peripheral to be in a suspended state.

[0069] In response to the sleep operation, the USB controller is controlled to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state, and in response to the USB bus being in an idle state for a preset time length, each USB peripheral is controlled to be in a suspended state.

[0070] In some embodiments, the preset time length may, for example, be 3 milliseconds. If the USB bus is still in an idle state after 3 milliseconds, it is considered to be a suspension signal, the USB peripheral removes its terminal resistance, and suspends the pull-up resistance. If the USB controller does not drive the D+ data line of the USB peripheral, the D+ data line of the USB peripheral is pulled high, forming a full-speed J signal. The USB peripheral detects again whether the USB controller drives the D+ data line of the USB peripheral. If not, the USB peripheral enters a suspended state.

[0071] In an optional implementation, the step S401 of controlling the USB controller to stop sending frame start packets to each USB peripheral in response to the sleep operation, so that the USB bus is in an idle state, can include: In response to the sleep operation, the USB controller is controlled to complete the execution of the ongoing request, and the USB controller is controlled to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state.

[0072] In normal operation, there can be a data transmission request being executed on the USB bus. The data transmission request may, for example, be a request of the USB controller to write data to a U disk, a request of a mouse to report movement data to the USB controller, or a request of a camera to transmit video data to the USB controller.

[0073] In response to the sleep operation, the USB controller is controlled to complete the execution of the ongoing request, and the USB controller is controlled to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state. That is, after ensuring that all data transmissions have been processed, the USB controller will stop all active bus activities, which can avoid data corruption and hardware damage.

[0074] On the basis of the above embodiments, Figure 7 A specific remote wake-up processing architecture is provided for the embodiments of the present application.

[0075] In Figure 7 In the architecture shown, the execution steps include the following steps: Step one, start the sleep operation.

[0076] Step two, the USB controller starts to execute the sleep operation.

[0077] Step 3: The USB controller first completes the request that is being executed, and then controls the USB bus to be idle, allowing the USB peripheral to enter a suspended state.

[0078] Step 4: Change the USB controller status from working state to sleep operation state.

[0079] Step 5: The power management unit module performs a board-level power-down operation to complete the sleep process.

[0080] Step 6: The wake-up detection unit module starts working, allowing the wake-up detection unit to report wake-up signals to the power management unit.

[0081] Figure 8 This is a schematic diagram of another remote wake-up processing architecture provided in an embodiment of this application. Figure 8 In the architecture shown, the execution steps include the following: Step 1: Start the sleep process.

[0082] Step 2: The USB controller begins the sleep operation.

[0083] Step 3: The USB controller first completes the request that is being executed, and then controls the USB bus to be idle, allowing the USB peripheral to enter a suspended state.

[0084] Step 5: Change the USB controller status from working state to sleep operation state.

[0085] Step 6: The wake-up detection unit module starts working, and the wake-up detection unit module is prohibited from reporting information.

[0086] Step 7: The power management unit module performs a board-level power-down operation to complete the sleep process.

[0087] Step 8: Allow the wake-up detection unit module to report the wake-up signal to the power management unit.

[0088] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The device can be implemented using the aforementioned target device.

[0089] like Figure 9 As shown, the electronic device 50 may include: a main processor 501, a USB controller 502, a USB physical layer transceiver 503, and a USB hub 504. The main processor 501 and the USB controller 502 are connected. The USB controller 502 is connected to at least one USB peripheral via a USB bus through the USB physical layer transceiver 503 and the USB hub 504 in sequence. The main processor 501 is used to execute the above-mentioned related method steps.

[0090] In some embodiments, the power management unit 505 and the wake-up detection unit 506 can be implemented by separate hardware entities. The device may also include the power management unit 505 and the wake-up detection unit 506. The main processor 501, the USB controller 502, the USB physical layer transceiver 503 and the wake-up detection unit 506 can be integrated on a system on a chip (SOC). The power management unit 505, the wake-up detection unit 506 and the USB controller 502 are respectively communicatively connected to the main processor 501.

[0091] This application also provides a remote wake-up processing system, which may include at least one USB peripheral and the aforementioned electronic device.

[0092] Based on the same inventive concept, this application also provides a remote wake-up processing device corresponding to the remote wake-up processing method. Since the principle of the device in this application is similar to the remote wake-up processing method described above in this application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0093] Figure 10 This is a schematic diagram of the structure of a remote wake-up processing device provided in an embodiment of this application. This device can be integrated into an electronic device.

[0094] like Figure 10 As shown, the device may include: Control module 601 is used to control each USB peripheral to be in a suspended state and switch the USB controller to a sleep state in response to a sleep operation for the target device; The acquisition module 602 is used to acquire, after performing a board-level power-down operation in sleep mode, any USB peripheral transmitting a wake-up signal for the target device through the USB hub or USB physical layer transceiver, so as to wake up the target device.

[0095] In an optional implementation, the acquisition module 602 is specifically used for: In sleep mode, a board-level power-down operation is performed, and the wake-up detection unit is activated after the board-level power-down is completed. The wake-up detection unit monitors the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver.

[0096] In an optional implementation, the acquisition module 602 is specifically used for: In sleep mode, the wake-up detection unit is activated and the signal reporting status of the wake-up detection unit is set to disabled. After performing the board-level power-down operation, the signal reporting status of the wake-up detection unit is switched to the start state; The wake-up detection unit monitors a wake-up signal transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver to the target device.

[0097] In an optional embodiment, the control module 601 is specifically configured to: In response to the sleep operation, control the USB controller to stop sending a frame start packet to each USB peripheral, so that the USB bus is in an idle state. In response to the USB bus being in the idle state, control each USB peripheral to be in a suspended state.

[0098] In an optional embodiment, the control module 601 is specifically configured to: In response to the sleep operation, control the USB controller to complete the execution of the ongoing request, and control the USB controller to stop sending a frame start packet to each USB peripheral, so that the USB bus is in an idle state.

[0099] In an optional embodiment, the acquisition module 602 is specifically configured to: In the sleep state, after performing a board-level power-down operation, acquire a wake-up signal transmitted by a target USB peripheral through the USB hub and the USB physical layer transceiver to the target device, the target USB peripheral being a USB peripheral supporting remote wake-up.

[0100] In an optional embodiment, the sleep operation on the target device includes a sleep operation input through a user operation interface.

[0101] The description of the processing procedure of each module in the apparatus and the interaction procedure between the modules can refer to the related description in the above method embodiments, and will not be described in detail here.

[0102] The embodiment of the present application further provides a computer readable storage medium, and the computer readable storage medium stores a computer program. When the computer program is run by a processor, the above method is executed.

[0103] In the embodiment of the present application, the computer program run by the processor can also execute other machine readable instructions to execute the method as described in other embodiments, and the specific method steps and principles are described in the embodiments, and will not be described in detail here.

[0104] In the embodiments of the present application, it should be understood that the disclosed apparatus and method can be implemented in other manners. The embodiments described above are merely exemplary, for example, the division of the units is only a logical function division, and there can be another division manner in actual implementation; for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, and electrical, mechanical or other forms.

[0105] The units described as separate components can or can not be physically separate, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments.

[0106] In addition, each functional unit in the embodiments of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0107] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that make contributions to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0108] It should be noted that: similar reference numerals and letters in the following drawings represent similar items, and therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. In addition, the terms "first", "second", "third" and the like are only used to distinguish descriptions, and cannot be understood as indicating or implying relative importance.

[0109] Finally, it should be noted that the above-described embodiments are merely specific embodiments of the present application, which are used to illustrate the technical solutions of the present application, but not to limit the same. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those skilled in the art that any skilled person in the art can still modify or easily think of changes to the technical solutions recorded in the foregoing embodiments, or make equivalent replacements to some of the technical features, within the technical scope disclosed by the present application. The modifications, changes or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. All should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for remote wake-up processing, the method comprising: The application relates to a main processor applied to a target device, wherein the target device further comprises a USB controller, a USB bus, a USB physical layer transceiver and a USB hub; the main processor is connected with the USB controller; the USB controller is connected with at least one USB peripheral device through the USB bus, the USB physical layer transceiver and the USB hub in sequence; and the method comprises the following steps: In response to a sleep operation of the target device, the USB peripherals are controlled to be in a suspended state, and the USB controller is switched to a sleep state; In the sleep state, after a board-level power-off operation is performed, a wake-up signal transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver is acquired to wake up the target device.

2. The method of claim 1, wherein, The step of acquiring the wake-up signal in the sleep state after the board-level power-off operation is performed comprises the following steps: In the sleep state, a board-level power-off operation is performed, and after the board-level power-off, a wake-up detection unit is controlled to be started; The wake-up signal transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver is monitored through the wake-up detection unit.

3. The method of claim 1, wherein, The step of acquiring the wake-up signal in the sleep state after the board-level power-off operation is performed comprises the following steps: In the sleep state, a wake-up detection unit is started, and a signal reporting state of the wake-up detection unit is set to a prohibited state; After the board-level power-off operation is performed, the signal reporting state of the wake-up detection unit is switched to a started state; The wake-up signal transmitted by any USB peripheral through the USB hub and the USB physical layer transceiver is monitored through the wake-up detection unit.

4. The method of claim 1, wherein, The step of controlling the USB peripherals to be in the suspended state in response to the sleep operation of the target device comprises the following steps: In response to the sleep operation, the USB controller is controlled to stop sending a start-of-frame packet to the USB peripherals, so that the USB bus is in an idle state; In response to the idle state of the USB bus, the USB peripherals are controlled to be in the suspended state.

5. The method of claim 4, wherein, The step of controlling the USB controller to stop sending the start-of-frame packet to the USB peripherals in response to the sleep operation, so that the USB bus is in the idle state, comprises the following steps: In response to the sleep operation, the USB controller is controlled to complete an ongoing request, and the USB controller is controlled to stop sending the start-of-frame packet to the USB peripherals, so that the USB bus is in the idle state.

6. The method of claim 1, wherein, The step of acquiring the wake-up signal in the sleep state after the board-level power-off operation is performed comprises the following steps: In the sleep state, after a board-level power-off operation is performed, a wake-up signal for a target device transmitted by a target USB peripheral device from the USB hub and the USB physical layer transceiver is acquired, the target USB peripheral device being a USB peripheral device supporting remote wake-up.

7. The method of claim 1, wherein, The sleep operation for the target device includes the sleep operation input by the user operation interface.

8. An electronic device, comprising: The sleep operation for the target device includes the sleep operation input by the user operation interface. The main processor, the USB controller, the USB physical layer transceiver, and the USB hub are connected in sequence through a USB bus. The main processor is configured to execute the method in any one of claims 1-7.

9. A remote wake-up processing system, comprising: The sleep operation for the target device includes the sleep operation input by the user operation interface. The sleep operation for the target device includes the sleep operation input by the user operation interface.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and the computer program is executed by the main processor to execute the method in any one of claims 1-7.

Citation Information

Patent Citations

  • Chip control method and device and slave equipment

    CN118656315A

  • Wake-up method and device and storage medium

    CN120179297A

  • Wake-up method, computer, wake-up system, integrated circuit and storage medium

    CN120457413A

  • Universal serial bus (USB) remote wakeup

    US20100049881A1

  • Sleep wake-up method, electronic device, bluetooth peripheral, and storage medium

    WO2024109259A1